6 Commits

Include renames

Author	SHA1	Message	Date
mos-dt-0andClaude Opus 5	b705a4dae9	docs(remediation): sharpen D-8 — the conformance harness must itself be conformance-tested ... Per Mos. Two requirements, both load-bearing: RM-02: the gate registry must SELF-VERIFY that every registered case demonstrably runs and demonstrably fails on a known-bad input. Presence in the registry is not evidence. A check is not trusted until it has been shown to fail. This is mutation testing / negative control at the registry level — the conformance harness must itself be conformance-tested. RM-55 inherits the same recursion: the harness must be observed red before its green means anything. Reviewer disclosure: rev-974 could have silently substituted a working fixture and reported AC2 PASS, and nothing would have caught it. The 'if a check is unrunnable, say so rather than silently substituting' clause is what makes a PASS mean anything, and must appear in every reviewer brief this mission issues. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>	2026-07-31 17:28:35 -05:00
mos-dt-0andClaude Opus 5	f8b65463ab	docs(remediation): bank D-8 — a pre-registered check that was not runnable as written ... PR #1025's AC2 fixture (mkdir -p apps/*/venv/lib) does not do what it claims when the glob is unmatched. rev-974 ran it exactly as written, caught the defect, re-ran the intended assertion at an explicit path, and DISCLOSED the substitution rather than silently reporting PASS. Pre-registration protects a check from being retrofitted to the implementation. It does not make the check correct. An unverified gate appeared inside the mechanism built to catch unverified gates. Requirement added to RM-02: the registry must self-verify that every registered case actually runs and can actually fail — presence in the registry is not evidence. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>	2026-07-31 17:25:56 -05:00
3 people	fb3221af27	docs(remediation): D-7 reaper doctrine into RM-50; adopt board-roll for the LIVE board ... D-7 resolution recorded. Mos verified attribution independently and reaped ~5.2G of dead-session scratch as lead coordinator. The finding is the gap it exposed: the authority to reap exists, the deterministic reaper does not. Two doctrine points now binding on RM-50: (1) 'agents should tidy up' is instructions-are-not-enforcement wearing another hat — a reaper must own it; (2) refusing to unilaterally delete another session's scratch was correct, and the fix is mechanically-decidable ownership/liveness, not braver deletion. Reaper requirements specified: mechanical liveness (not mtime alone), age threshold, dry-run, audit event per reap — never a heuristic sweep, which would reintroduce the P-WORKFLOW-001 auto-sync failure in a more destructive form. Board restructured into an explicit BOARD-ROLL zone and rolled with the framework's own board-roll.sh (8432B -> 8014B, D-1 archived to BOARD-LEDGER.md) rather than hand-trimmed. The tool exists precisely to stop coordinators hand-trimming; using it is the dogfood. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>	2026-07-31 17:25:04 -05:00
3 people	910b6f4166	docs(remediation): status — decisions ruled, RM-01 in flight ... Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>	2026-07-31 17:25:04 -05:00
3 people	1324385bba	docs(remediation): apply Mos rulings on D-1/D-2/D-3; bank D-7 tmpfs ENOSPC ... D-1 RULED — corrected wire-in target is a new production Node TaskExecutor on the LIVE dispatch path (packages/mosaic launch + packages/coord) that Coord/Forge/live dispatch submit through. The Python rail is deleted, not ported. RM-21/26/27/52 updated. D-2 — Jason-pending and explicitly NON-blocking. Binding meanwhile: the DB spine must not be a single-point hard-stop; degraded mode + rollback artifact become design requirements on RM-12/13/23/36/53. This reverses the earlier recommendation to pre-commit 'no DB means the fleet stops'. D-3 — RM-03 HOLD; PR #1023 marked SUPERSEDED-PENDING-JASON; RM-02/RM-55 proceed independently since conformance assertion is not the gate-6 fix itself. RM-03 now carries BOTH queue-guard defects: wrong exit on unknown, and evaluating branch=main rather than the branch being pushed. D-7 — shared 30G /tmp hit 100% ENOSPC, degrading two seats. ~5.2G of it is session scratch dead for 8-9 days; this session's own footprint is 88K. Same missing capability as P-FLEET-001 stale-session GC, applied to disk. Folded into RM-50, and RM-01 gains artifacts-off-shared-tmp acceptance criteria. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>	2026-07-31 17:25:04 -05:00
3 people	ba98f88891	docs(remediation): reconciled execution backlog from two independent decompositions ... TASK-1 complete. planner-opus (robustness, 38 tasks/8 dissents) and planner-sol (pragmatic, 25 tasks/10 defers/7 dissents) each decomposed the 4-build plan without seeing the other's work. Both decomps are committed alongside the reconciliation so the disagreements stay auditable rather than being flattened into a consensus. Reconciled into 58 tasks across P0-P5 (docs/remediation/TASKS.md): - 7 independent convergences, treated as settled because neither planner could see the other. The headline: BOTH reject the charter's wire-in point (mosaic_orchestrator.py::run_single_task) because that controller is disabled and references a dispatcher absent from this checkout — wiring it would produce a stranded executor, the same built-but-unwired disease one layer up. - 7 genuine disagreements ADJUDICATED, not averaged. The cost estimates are ~18x apart; rather than split the difference, the plan adopts sol's scope with opus's rigor and treats the first-dogfood gate as a hard budget checkpoint. - 3 decisions escalated (wire-in point, rollback artifact + availability trade, queue-guard ownership vs parked PR #1023). No task blocked on them is dispatched. Keystone dogfood case recorded (TASKS.md 1a): merged PR #868 shipped a file failing pnpm format:check, then an unrelated PR reformatted it as a side effect, so main went green and the gate's failure to fire left no trace. Detection must therefore be per-merge-commit against that commit's own tree. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>	2026-07-31 17:25:04 -05:00