Add control board status scanner and MVP plan (#1503)
Step 1 of the control board MVP (decision MOSAIC-STACK-D-001): a plan page, Gitea #1503, and packages/control-board, which reads each agent's newest pi session log plus tmux liveness and writes one status file per agent under <dataRoot>/board/. 23/23 tests; independent review approved after three fixes (length stopReason as error, unknown liveness state, secrets-boundary test). CURRENT.md now points at step 2, the page. Co-Authored-By: Claude Fable 5.1 <[email protected]>
This commit is contained in:
@@ -1926,3 +1926,20 @@ Exact independently approved11255dd4 source committed/pushed at3daee5ad89dc6a006
|
||||
## 2026-09-12 — #1500 owner acceptance and closure
|
||||
|
||||
Jason reran the two-test fixture demonstration himself on the canonical checkout at 5abbabb7: 2/2 pass. Taken as owner acceptance of the fixture-only increment (source 3daee5ad, Filbert manifest 11255dd4); receipt docs/plans/reviews/2026-09-12_m20-increment2-owner-acceptance.md. The 2026-09-11 "file not found" attempt was a pre-cutover shell whose cwd followed the retired v1 copy, not a checkout defect. Records-only change; no source, suite, live-service or production-refresh effect. Increment 3, launcher integration and the identity-env leak fix remain separately gated.
|
||||
|
||||
## 2026-09-12 — Control board MVP step 1 (#1503)
|
||||
|
||||
Before: #1500 closed; CURRENT.md asked for a re-plan against Jason's MVP
|
||||
decision MOSAIC-STACK-D-001 (one page: running agent sessions across projects,
|
||||
status, and who is waiting on him). No status data existed anywhere.
|
||||
|
||||
After: plan page `docs/plans/2026-09-12_control-board-mvp.md`; Gitea #1503;
|
||||
new package `packages/control-board` (scanner + CLI, ESM, no dependencies).
|
||||
Suites: control-board 23/23; registry 69/69 unchanged. Live scan writes
|
||||
`~/.mosaic-dev/board/` with 42 agent status files (15 waiting, 3 error,
|
||||
24 offline). Independent review approved after three corrections recorded in
|
||||
`docs/plans/reviews/2026-09-12_control-board-step1-review.md`.
|
||||
|
||||
Corrections during the phase: pi `stopReason: "length"` was initially treated as
|
||||
"working" (now "error"); an unrunnable tmux check was initially treated as alive
|
||||
(now "unknown"). Registry increment 3 stays parked. Next: step 2, the web page.
|
||||
|
||||
Reference in New Issue
Block a user