6 Commits

Include renames

Author	SHA1	Message	Date
mos-dt-0andClaude Opus 5	bb962dc25d	docs(remediation): status — decisions ruled, RM-01 in flight ... Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>	2026-07-31 17:19:48 -05:00
mos-dt-0andClaude Opus 5	cee54db527	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:19:30 -05:00
mos-dt-0andClaude Opus 5	b6d6abf125	docs(remediation): board — PRs #1025/#1026 open, review dispatched, D-6 queue-guard finding ... Third independent live instance of the inert-gate class this session: the mandated ci-queue-wait.sh returned exit 0 on state=unknown while guarding a push. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>	2026-07-31 17:13:39 -05:00
3 people	0e9e9246bf	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:09:58 -05:00
3 people	e80cebe7f0	docs(remediation): board reflects actual state + 4 dogfood findings from startup ... Corrects the premature "DISPATCHED" planner line (per Mos): both planners are now dispatched for real on GUARANTEED-clean context, not requested-clean. Records Mos rulings: mission.json is retired-rail residue (do not invest); gate-16 holds on interim mos-dt-0 since rev-974 reviews; remote-control path is Mos-relay. Captures 4 live failure classes observed while standing this seat up (D-1..D-4), including an agent that silently ignored an in-message context reset — direct evidence for the postmortem thesis that instructions are not enforcement. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>	2026-07-31 17:09:58 -05:00
3 people	21d5878515	docs(remediation): mission charter + kickstart + live board for the postmortem remediation ... 15/15 proposals decided (13 accept, 2 modify). Collapses to 4 builds + hygiene on one PG spine + choke-point service. Durable mission record for the mos-remediation project orchestrator; compaction-survival resume in KICKSTART.md. Co-Authored-By: Claude Opus 4.8 <[email protected]> Claude-Session: https://claude.ai/code/session_018XCrpMFmCAXbtSQtQAhDth	2026-07-31 17:09:58 -05:00