5 Commits

Include renames

Author	SHA1	Message	Date
mos-dt-0andClaude Opus 5	75dfe2fa75	docs(remediation): bank D-11 — identity drift + seat capability opacity at dispatch ... RM-01's seat was briefed to export MOSAIC_GIT_IDENTITY; its commits are authored as the generic mosaic-coder fallback, so git history cannot say which seat did the work. P-WRAPPER-001 reproduced on our own delivery. Separately, nothing at dispatch time revealed the seat lacked a credential for the target provider — discovered only when it failed mid-task after ~$9 and 69% context. get_gitea_token behaved correctly by refusing to borrow another slot's token; the dispatch-time information simply did not exist. RM-50 gains per-seat capability declaration + pre-dispatch check; RM-04 gains identity-binding verified by an exit-asserting test rather than assumed from an export in a brief. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>	2026-07-31 17:56:34 -05:00
mos-dt-0andClaude Opus 5	409bf23e6a	docs(remediation): bank D-10 — the queue guard's failure modes are inverted ... Same required gate, both directions wrong: fails OPEN on state=unknown (5 meaningless greens this session, wrong branch too), and fails CLOSED on credential resolution, hard-blocking a worker's completed work. The identical command succeeded from that worker's own worktree in another shell, so the checkout was fine. A gate that waves through unchecked work and blocks ready work has its failure modes backwards. Availability failures must degrade to a loud, audited CANNOT_ASSERT; correctness failures must block. Also the Pi-brick shape: a gate whose unavailability prevents recovery from it. RM-03 extended to a third requirement: distinguish CANNOT_ASSERT from ASSERTED_NOT_READY, both registered with must-fail controls, neither exiting 0 silently. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>	2026-07-31 17:52:42 -05:00
mos-dt-0andClaude Opus 5	31c3191305	docs(remediation): rolling-branch resume pointer + D-9 interim comms rule ... KICKSTART resume now points at origin/remediation/state for the live board, per Mos's cadence ruling: every tick is pushed to the rolling branch immediately (durable per-tick, no per-tick main PR); main carries periodic snapshots only. Reading the board from main would silently yield a stale tick, so the step warns explicitly. D-9 hardened: comms/v1 must use file/stdin transport, never argv interpolation. Standing interim rule until then — agent-send -f for any body with special characters, never -m. Mandatory in every worker brief alongside the D-8 clause. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>	2026-07-31 17:50:26 -05:00
mos-dt-0andClaude Opus 5	6a067174ed	docs(remediation): bank D-9 — comms path shell-interprets message bodies ... agent-send.sh -m with backticks executes them as command substitution: the recipient got a mangled body plus a shell error, and the send still reported success. Same class as the known pr-create.sh backtick bug — two tools in the comms path treating a message body as shell input. The failure mode is the mission's own pattern: silent corruption with a success receipt. Requirement on RM-40/RM-42: comms/v1 must carry payloads verbatim with no shell interpretation at any hop, with a byte-identical round-trip test (backticks, command substitution, quotes, newlines) registered under RM-02 including a must-fail control. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>	2026-07-31 17:48:17 -05:00
mos-dt-0andMos	01e966f36d	docs(remediation): mission charter + reconciled execution backlog (#1026) ... Co-authored-by: mos-dt-0 <[email protected]>	2026-07-31 22:47:03 +00:00