mosaicstack/stack

fix(rm-03): make CI queue guard fail on asserted non-readiness #1032

Merged

mos-dt-0 merged 5 commits from fix/rm-03-queue-guard into main

2026-08-01 18:55:27 +00:00

Author	SHA1	Message	Date
coder-mos1	868b9b871a	docs(rm-03): record review bypass remediation ci/woodpecker/pr/ci Pipeline was successful Details	2026-08-01 13:31:44 -05:00
coder-mos1	afa4927b7e	fix(rm-03): remove merge queue-guard bypass	2026-08-01 13:31:44 -05:00
coder-mos1	98872cd8f5	test(rm-03): prove merge queue bypass reaches provider	2026-08-01 13:31:44 -05:00
coder-mos1	cd65ccbfd7	docs(rm-03): record scope and checkpoint verification	2026-08-01 13:31:44 -05:00
coder-mos1	b238e0a8b1	wip(rm-03): rescue checkpoint of in-flight queue-guard work CHECKPOINT ONLY — not a deliverable, not reviewed, not complete. Committed by mos-remediation as TRANSPORT after the authoring seat (coder-mos1) became unable to act: its context window was exceeded at 102.6%/372k AND its overflow-recovery path failed ("Turn prefix summarization failed: servers overloaded"). The seat could not process instructions or commit its own work, leaving 28 modified files durable only on local disk. Authorship preserved as coder-mos1 — this is transport, not authorship. The work is the seat's; committing it is the only way to make it survive the rotation that must follow. Scope note, unresolved: this diff spans the queue-guard tools (9 files under framework/tools/git) AND 5 framework guides plus 11 agent templates. RM-03 was scoped to ci-queue-wait.sh and its tests. Whether the doc/template edits are consequential to the tri-state change or drive-by was queried and never answered — the seat was bricked before it could reply. That question stays open and must be resolved before any of this is reviewed; the wider edits may need splitting out. Direct instance of D-31: commit-then-rotate works, rotate-without-commit loses everything.	2026-08-01 13:31:44 -05:00