forked from mosaicstack/stack
mos-dt-0andClaude Opus 5
08f706b675
D-50: #1032 carried review 66 APPROVED and a merge-gate GO both bound to78ec47cd, and by the time Jason approved the merge it reported mergeable=false. Verified from the provider: its head does not contain current mainf4fd5967. Two rules we already hold, neither wrong alone, combine badly — a verdict is commit-bound and voids when the head moves, and main drifts while a PR is held, so resolving the drift moves the head and voids the verdict that was waiting to be used. Holding it across the whole #1033 saga is what did it. The asymmetry worth noting: usually a head moves because the AUTHOR pushed, so the void follows from their action. Here nobody touched the PR — unrelated progress invalidated it — which is why it is easy to miss and needs a checklist line rather than vigilance. Mos's line: a GO has a shelf life, re-gate on main-drift. RM-63 files Jason's architecture as the mechanization of D-41/RM-50/RM-58/P-LIFECYCLE rather than a new island: durably-named systemd agent services with lanes, where restart triggers a continuation and the agent resumes its lane, combined with DB-centric task assignment on the PG spine for autonomous pickup. That is the enforcement surface D-41 proved missing — a managed service can be watched (token budget, which is D-49's mechanical ceiling monitor), restarted (rotation, retiring our manual respawns) and continued (rehydrate from the DB). It closes the f10-coder ceiling gap directly: Jason confirmed that ceiling was not mechanically flagged and must be. #1032 freshening dispatched to coder-mos1 — it authored the queue guard, so that context is an asset, and by D-49 it can still take a lane at 67%. Told to stop and flag on any SUBSTANCE conflict, because a queue-guard semantic resolved quietly re-breaks the very thing RM-03 fixes. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>