[tourbut]

Summary

Initial GitHub issue backlog polling sent an epoch date filter and returned no issues in erden-godot. After intake recovery, busy coor processing also let its 90-second lease expire and the hook blocked even status/disable. Version 1.2.1 repairs intake, bounded lease renewal and safe owner controls. Coor keeps its foreground wait active and distinguishes the local queue from GitHub issue counts.

backlog enabled
  initial cursor → unfiltered issue pages → durable queue
  advanced cursor → same one-second overlap → deduplicated updates
busy coor → verified identity + recent native activity → bounded lease renewal
expired lease → owner status/disable only; product commands remain fenced

Evidence

• Before: actual tourbut/erden-godot API query with the epoch date filter returned [] while issues feat: FullOps 0.3.1 공통 개발 규칙과 회귀 검사 추가 #1/보드 산출물 선택 시 설계서 등 원천 문서를 열람할 수 있도록 지원 #4 were open. The new regression failed on the original source.
  After: no-date query returns all five issues, including open feat: FullOps 0.3.1 공통 개발 규칙과 회귀 검사 추가 #1/보드 산출물 선택 시 설계서 등 원천 문서를 열람할 수 있도록 지원 #4. The full issue-mode regression and six update checks pass, covering initial and subsequent query paths. Generated distribution matches source; final required CI validates packaging and portability.
• Before: switching to new-issues-only mode before the first backlog poll retained the epoch cursor and admitted historical issues; the transition regression failed.
  After: reactivation advances both the cursor and creation cutoff, preserving existing jobs while rejecting old issues with recent updates and accepting new issues. The issue-mode suite passes.
• The current owner can run the fixed poll once using its existing lease, then continue its foreground wait. The old watcher reads the advanced cursor on its next poll. No impersonation, alternate coordinator, credential changes, or queue-state rewrites are needed.
• Live recovery confirmed: the original coor collected five issues, held tracking issue feat: FullOps 0.3.1 공통 개발 규칙과 회귀 검사 추가 #1 pending 보드 산출물 선택 시 설계서 등 원천 문서를 열람할 수 있도록 지원 #4, and started handling 보드 산출물 선택 시 설계서 등 원천 문서를 열람할 수 있도록 지원 #4 under its existing lease.
• Before: busy coor handling outlived the lease and could neither wait nor query status. Focused regressions reproduced missing background renewal and expired-owner control rejection.
  After: watcher renewal reuses wait's identity/fencing checks. Native renewal never exceeds the last terminal activity plus 90 seconds; stale/missing/future activity cannot extend it. Owner status/disable accepts only the trusted Python script and exact command form. Lease, incarnation and command-spoofing regressions pass.
• A received attempt that stopped before dispatch can be explicitly reconciled with --not-dispatched after auditing its receipts and termination. This requires no local dispatch intent and an explicitly empty complete task/worker listing; it preserves the attempt/history and requires a fresh owner receipt. Default absent-task reconciliation still rejects inference from absence alone. The restart path and rejection of dispatch intent/unknown fleet are covered.

Merge Danger

Door: two-way.

Blast Radius: automation. The first approved backlog scan reads the full existing issue list; pagination, author allowlist, duplicate prevention, lease validation and draft-PR scope are preserved. New-issues-only reactivation advances its cutoff. Independent renewal requires current identity and bounded activity, never revives expired leases, and preserves SessionEnd fencing. Installation does not enable automatic mode. Existing Codex sessions need a safe stop, plugin update and explicitly enabled fresh session for the complete fix.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-09T07:55:24.641981Z	b2c6352	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b2c6352ad8

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".