control board: park D05/registry-3/new seats and add the mid-tool-call working rule (#1503)

Co-Authored-By: Claude Fable 5.1 <[email protected]>
2026-09-12 09:25:32 -05:00
parent bf1391a424
commit bf641e220a
1 changed files with 21 additions and 0 deletions
@@ -150,3 +150,24 @@ sat above a table showing 13 rows. The header now reads "fleet (13 of 38)"
 while a checkbox hides something and falls back to "fleet (38)" when nothing
 is hidden. The note under the table stays: the header says how many, the
 note says why. One static test.
 **2026-09-12 — Parked until the board passes its gate.** Jason's ruling:
 nothing else starts until he has used the board in place of cycling tmux.
 Parked, not cancelled, and not to be resumed by inertia:
 - Dewey's dashboard mockup selection (task D05, `agents/dewey/work/wui/`).
  It gets chosen against a board Jason has used, not before.
 - Registry increment 3 (already parked above; restated so it stays parked).
 - New seat directories. The roster is frozen at its current seats until the
  rails pass condition is written (phase C of the 48-hour plan).
 **2026-09-12 — Rule: a seat mid-tool-call is `working`, never `waiting`.**
 Added as an acceptance rule, not a fix log entry, because it is the second
 way the top section can lie (the first was the dead-session case above).
 If the newest session-log entry is an assistant message that contains a
 tool call, or a tool result with no assistant text after it, the state is
 `working` even if the last text the agent printed looks like a question.
 `waiting` requires the last entry to be an assistant message whose content
 is text only and whose turn has ended. Verify with one live seat caught
 mid-tool-call and one that has finished a turn; add a fixture test for
 each so the rule cannot regress silently.