docs(records): Jason's walkthrough rulings, Sage moved to SetSpark, CHAT-02 go
Jason ruled on seven open items (20:27Z-20:45Z): seat Gitea tokens read in place, one Discord restart after 6b with row 25 live, row 8 limited to the dev seats, DYOR in dyor-stack-v4 with Sage moved to SetSpark, skills/aws-* excluded locally, no second WebUI return defect, and go on CHAT-02 only. Sage persona files name SetSpark as its business work. Darkwing's SOUL drops harness names that were wrong for T3. DEFERRED adds the slash-prefix paste hazard and the board Host/Origin gap, and moves the ledger T3 item to Done. Dewey's approved CHAT-02 brief (636b0fac) and Filbert's review are recorded. Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
+15
-6
@@ -105,12 +105,20 @@ at every gate. Started 2026-09-12 during the control board MVP.
|
||||
nodes. Launch, observe, stop, full transcript navigation, command palette and
|
||||
other screens are absent. Existing palette/appearance switches remain on the
|
||||
single page. Revisit only with a new brief. (2026-09-13 UTC, #1507)
|
||||
- **Ledger counts T3 agent messages as human.** `messageKind` classifies a
|
||||
prompt that opens with the T3 header `[from: x (…) -> to: …]` as human, so
|
||||
the weekly number in Table 2 rises once development runs in T3. Rocko
|
||||
reproduced it read-only, and Filbert confirmed it. The Gate G audit (#1508 R5) does not rely on
|
||||
this count. Fix it before the next weekly number is quoted. (2026-09-26 UTC,
|
||||
#1506)
|
||||
|
||||
- **Board send can turn into a Pi slash command.** `tools/tmux`
|
||||
`send-message.sh` pastes onto whatever is already in Pi's composer without
|
||||
clearing it. On Jason's 2026-09-26 20:10:57Z send, a leftover "/" landed in
|
||||
front of the agent-send header. Pi read it as plain text that time, but the
|
||||
same path could run a board reply as a slash command. Belongs to CHAT-03I/B3.
|
||||
No tools/tmux change until that piece. Found by Dewey in the CHAT-02 brief
|
||||
evidence. (2026-09-26, #1507)
|
||||
- **Control board checks the bind address but not Host or Origin.** After a
|
||||
DNS rebind, a web page could read `/api/board` and POST `/api/reply`, which
|
||||
pastes text into a live seat pane. The WebUI server already checks both.
|
||||
Not tested against a browser, so the exposure is unproven. Dewey writes the
|
||||
guard as its own small change before CHAT-02, and Rocko reviews it.
|
||||
(2026-09-26, #1507, found by Dewey)
|
||||
|
||||
## Queue
|
||||
|
||||
@@ -121,3 +129,4 @@ Moved to `docs/plans/QUEUE.md` on 2026-09-13. This file holds only gaps.
|
||||
- Ledger (piece 3, #1506): shipped cd0aa5fb, Gate D written 2026-09-12 (18.9 human messages per closed issue).
|
||||
- Relaunched seat shows the old last message (darkwing, Step 3 log, 2026-09-12): closed by #1512 relaunch activity, af4203ca. Filbert authored it; Darkwing and Dewey reviewed. The live board restart and Gate F remain separate.
|
||||
- Sage launcher hook uncommitted (2026-09-12): closed by the agents/sage launch files commit, Dewey review R1 revise, R2 approve (`agents/dewey/work/sage-launch-review-2026-09-26.md`), launcher test now covers sage.
|
||||
- Ledger counts T3 agent messages as human (2026-09-26, #1506): fixed in ef0020ad (Darkwing 6a, Filbert reviewed). `messageKind` now counts a T3 header as agent and the control-board sender as board. It changes no current count, because no source the ledger reads has a T3 header yet. That waits for the T3 thread source (Gate F).
|
||||
|
||||
Reference in New Issue
Block a user