control board: Gate C passed, #1505 closed, next action waits for the ledger brief (#1503)

Co-Authored-By: Claude Fable 5.1 <[email protected]>

docs/SESSIONS.md

@@ -224,3 +224,4 @@ are never rewritten or removed; corrections are new entries.
 - 2026-09-12 — darkwing (Claude Code, coordinator) — #1504 follow-up on two defects the professor session reported and this session verified: the darkwing launch test leaked fixture registrations into the real data root (flock spawn without the fixture config; fixed and guarded so a leak fails), and a refused launch left a dead-pid record the board honoured (scanner now probes the pid; stale records are shown but do not override). Fleet launchers marked not planned per Jason. Board 90/90, seat 15/15, launch scripts 5/5. Committed and pushed to refactor.
 - 2026-09-12 — darkwing (Claude Code, coordinator) — Control board: model per row (#1503) on Jason's ask: readSession tracks model/provider from the latest model_change entry or assistant turn; page shows the model under the agent name and a Model detail row. Live check on a scratch board: all 42 real rows named a model. Board 91/91. Committed and pushed to refactor.
 - 2026-09-12 — darkwing (Claude Code, coordinator) — Control board piece 2, reply-from-board (#1505, brief by Jason): `POST /api/reply` runs `tools/tmux/agent-send.sh` for one registered, live seat and returns the exit code and streams; the page has a reply box in registered live rows' detail with delivered/failed receipts. Live check on a scratch tmux session through the real agent-send.sh: delivered, then a failure receipt with the tool's stderr. Board 98/98. Gate C first exchange ("pizza?") delivered and read back within one scan; the seat's send-back to control-board was refused as expected, so every board message now ends with a fixed trailer (Jason's ruling via the professor session). Committed and pushed to refactor.
+- 2026-09-12 — darkwing (Claude Code, coordinator) — Gate C pass for reply-from-board (#1505) verified against Jason's log commit 4f830680 and filbert's session log; CURRENT.md moved to waiting for the ledger brief; #1505 closed with a comment. Committed and pushed to refactor.

docs/plans/CURRENT.md

@@ -43,15 +43,13 @@ stdout and stderr; the page shows `delivered` or `failed` with the stderr.
 No send-keys, queue, history or broadcast; no change to `packages/seat` or
 `agent-send.sh`. Board suite 98/98.
 
-Gate C's first exchange happened 2026-09-12 ("pizza?" to darkwing:
-delivered, read back within one scan; the seat's send-back to
-`control-board` was refused as expected, so every board message now ends
-with a fixed trailer telling the seat to answer in its own session).
+Gate C passed 2026-09-12 on 867619dc (logged by Jason at 4f830680):
+"pizza?" from the board to filbert arrived with the trailer, the seat
+answered in its own session with no send attempt, and the row showed the
+answer on the next scan. #1505 is closed.
 
-Next action: Jason confirms Gate C on the trailer build (restart the board
-on 7331, answer a `waiting` seat, the row turns `working` with the reply
-as its newest user message and the seat answers in its own session).
-Record the pass or the failure in the plan page and here. Then the WebUI on Dewey's Console design absorbs
+Next action: wait for Jason's brief for the ledger script (the professor
+session relays it when he calls it; do not start it unasked). Then the WebUI on Dewey's Console design absorbs
 the board as its first screen. Close #1503 when Jason says the page answers "who
 is waiting on me" without him opening a terminal. Out of scope until he
 asks: auth or provider registry, roster schema changes, hooks/plugins, comms,