You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Replacement for stalled issue #356: fence duplicate-closeout redispatch after refill/top-up mismatch #380
Replacement work for stalled issue #356 and blockers sgt-acceptance-1775022704-d829bc00 / sgt-acceptance-1775037090-5552e67c.
Task:
Stop refill/top-up from redispatching duplicate-closed continuation lanes after control-plane or live-query mismatch. Preserve canonical successor binding across duplicate-closeout lineage, prefer fresh materially different successors after duplicate cleanup, and prevent watchdog fallback from resurrecting the killed confidence-lift family (#1088/#1092/#1095).
[sgt-mayor] Recovered stalled-worker fallout for this issue. There were no recoverable artifacts from polecat sgt-61f8c178, and the normal GraphQL-backed redispatch path was blocked by exhausted GraphQL quota. Verified via REST that #380 remains open and authorized, then re-dispatched replacement work on polecat sgt-036f3c65 (sgt/sgt-036f3c65).
[sgt-mayor] Recovered stalled-worker fallout for #380 by promoting the surviving branch into replacement PR #391: #391
Investigation:
stalled polecat sgt-61f8c178 did produce a durable git commit (a5e17a1) but never opened a PR before witness marked it stalled
replacement polecat sgt-036f3c65 also produced a durable commit (cbe4373) but the worker again exited without PR creation
GraphQL-backed gh pr/issue view paths were still rate-limited during recovery, so REST was used to verify issue state, push sgt/sgt-036f3c65, and open the PR directly
Activity
Fence superseded duplicate lane redispatch for #380
codejeet commentedon Apr 1, 2026
[sgt-mayor] Recovered stalled-worker fallout for this issue. There were no recoverable artifacts from polecat
sgt-61f8c178, and the normal GraphQL-backed redispatch path was blocked by exhausted GraphQL quota. Verified via REST that #380 remains open and authorized, then re-dispatched replacement work on polecatsgt-036f3c65(sgt/sgt-036f3c65).Fence stale duplicate closeout redispatch (#380)
codejeet commentedon Apr 1, 2026
[sgt-mayor] Recovered stalled-worker fallout for #380 by promoting the surviving branch into replacement PR #391: #391
Investigation:
sgt-61f8c178did produce a durable git commit (a5e17a1) but never opened a PR before witness marked it stalledsgt-036f3c65also produced a durable commit (cbe4373) but the worker again exited without PR creationgh pr/issue viewpaths were still rate-limited during recovery, so REST was used to verify issue state, pushsgt/sgt-036f3c65, and open the PR directlyValidation:
bash test_plan_tick_duplicate_closeout_successor_refresh.shbash test_sweep_stale_plan_task_skip.shFence stale duplicate closeout redispatch (#380) (#391)