stack/packages/queue/tests/fixtures/queue-marked.md

QUEUE — the one task list

Read this first. One row per piece. The table between the markers is rendered from docs/plans/queue.json, and scripts/mosaic queue is its only writer. Don't edit the table by hand: queue verify and the commit hook refuse a table that isn't the render. packages/queue/README.md has the verbs.

How to find your next thing:

• A seat: run scripts/mosaic queue next. It names the row to resume, review or start, or says there is nothing; if nothing, say so on the board and stop.
• Jason: rows in state waiting-on-jason, and parked rows to reopen.
• Sage, project lead (Jason's ruling 2026-09-26): changes the queue with scripts/mosaic queue and commits queue.json with QUEUE.md through scripts/queue-commit.sh. CURRENT.md is the narrative log; the queue wins if they disagree.

States: queued (brief exists, not accepted) → briefed → in-progress → in-review → waiting-on-jason → done. blocked returns to the state it left. parked rows wait for Jason to reopen them. A required row can't be parked, and only Jason clears the flag. after names the rows a piece waits for.

Gaps found while working go to docs/plans/DEFERRED.md, not here.

Pieces (in order)

Lead: Sage from 2026-09-26 (Jason's ruling); Darkwing is a collaborating seat. Jason is preparing the target for the next phase; until it arrives, the priority below stands.

Current priority: Sage's goal order from the 2026-09-27 goals review (close what is open, queue as data, Gate E), ratified by Jason 2026-09-27. Earlier: row 6, after Jason accepted row 18. His newer standing continuation instruction supplies the start; the earlier row-18-only priority is complete. Jason requires automatic continuation to the next authorized item after each accepted iteration; no routine next-step prompt. Explicit dependencies and protected-action gates remain. Use the five internal agents, not fleet seats. No ~/.mosaic changes or live fleet migration. Row 6 closed 2026-09-27 (lead decision 29), which clears rows 9-13 to proceed; it does not authorize publication/access changes.

#	Piece	Owner	Issue	State	Gate	Brief
1	Control board MVP (scanner + page)	darkwing	#1503	done 2026-09-27 (Sage, lead decision 29): D-001 MVP delivered, Gate A passed 2026-09-12, attention status operator-accepted (row 22), relaunch activity, attribution and Host guard landed; #1503 closed; cross-harness board work belongs to Gate E (row 5)	A passed 2026-09-12	plan page, top
2	Seat registration and mosaic seat task	darkwing	#1504	done 2026-09-13	B passed 2026-09-12	plan page, Step 3
3	Reply-from-board (piece 2 on the plan page)	darkwing	#1505	done 2026-09-12	C passed 2026-09-12	plan page, "Piece 2: reply-from-board"
4	Ledger (piece 3 on the plan page)	darkwing	#1506	done 2026-09-13	D: 18.9 human messages per closed issue, week of 2026-09-06	plan page, "Piece 3: ledger"
5	WebUI first screen on the Console design (piece 4 on the plan page)	dewey; filbert reviews	#1507	CHAT-00/01/01C contracts published (370823b3, 28d4e98a, b023841c); CHAT-02 done: backend a5beb6d9, Console c9e771cf, live check passed 2026-09-26; CHAT-03 brief approved and pinned 2026-09-27 (BRIEF.md 1ef15ac0, rescoped to Gate E, lead decisions 30 to 33; Filbert r3 approve, Rocko blocker closed, Filbert scope check pass); source author named by Sage after queue A2 lands; CHAT-04..08 not chartered; Gate E blocked	E: all-seat interactive demonstration then Jason workday ruling; live cutover separately approved	2026-09-13_webui-session-chat.md, CHAT-00..08
6	Darkwing on point: darkwing assigns and gates filbert's work (piece 5 on the plan page)	darkwing; filbert authors pilot; darkwing/dewey review	#1511 code phase; #1512 pilot	done 2026-09-27 (Sage, lead decision 29): #1511 and #1512 landed in af4203ca (pushed) and are closed; Gate F not passed: the ledger counts 2 human messages in filbert's T3 thread during #1512 (one is Jason's 09-26 seat takeover) and its first 11 days predate the T3 source; Gate G (row 9) now carries the zero-human-message test	F: filbert's item closes with zero human messages from Jason; code phase does not claim Gate F	2026-09-15_relaunch-activity.md; 2026-09-14_task-attribution.md; plan page Piece 5
7	Weekly ledger run and rails number	sage (lead decision 27); Jason reads	—	recurring, every Monday; 09-13..19: 47.7, 09-20..26: 33.0 human messages per closed issue	under 10 human messages per closed issue for the week of 2026-09-13	packages/ledger/README.md
8	Fleet seats (~/.mosaic) onto mosaic launch	unassigned	—	parked by current owner direction; no ~/.mosaic changes during internal bootstrap	Jason's call	none yet
9	Queue as data: docs/plans/queue.json, mosaic queue is the only writer	darkwing; filbert reviews	#1508	required; A1 (journal, lock, CLI, verify) committed 34a72af9 2026-09-27, Filbert approved; A2 (migration, render, dispatch) in progress, then genesis and hook install by Sage	G: a fresh seat told only "run mosaic queue next and do it" starts its piece with zero human messages	2026-09-13_queue-as-data.md, Piece A
10	Seats read the queue, not CURRENT.md (AGENTS.md cadence, seat context files)	coordinator	#1508	required; AGENTS.md lines done 2026-09-13, rest after row 9	verified by Gate G	2026-09-13_queue-as-data.md, Piece B
11	Brief template docs/plans/BRIEF-TEMPLATE.md; queue add refuses a missing brief	darkwing	#1508	required; template committed with A1 (34a72af9); queue add refusal lands with A2	two briefs accepted by Jason with no scope question	2026-09-13_queue-as-data.md, Piece C
12	Reviews as issue comments posted by queue move ID in-review, not files in docs/plans/reviews/	darkwing	#1508	required; after row 9	one review round with no new file under reviews/	2026-09-13_queue-as-data.md, Piece D
13	Ledger "queue" section: issue/row/seat drift printed with the weekly number	darkwing; filbert reviews	#1508	required; after row 9	first run Monday 2026-09-21, zero violations or every one moved same day	2026-09-13_queue-as-data.md, Piece E
14	Discord connector pilot: Sage answers in Shared Signals (chat only, no tools, no repo writes)	coordinator; Filbert or orch-01 seat reviews	#1509	done: rev-code-02 APPROVE 26170 (round 9), committed 786e379c; pilot steps 1-8 done with private receipts, Gate H passed (Jason, 2026-09-13: replies read as Sage); connector left running for MVP iteration	H: offline suite green, eight-step live pilot with private receipts, then Jason says the reply reads as Sage	2026-09-13_discord-connector-pilot.md
15	Discord connector: eyes reaction on every admitted message as a read receipt (MVP iteration 1)	coordinator	#1509	done: committed 93d6b624, live check passed 19:21 UTC (turn record receipt ok, Jason: test is successful), receipt mvp1-read-receipt-20260913T192158Z.json in the private evidence dir; rest.react best effort, reaction placed at admission before the engine runs, outcome in the turn record, no reaction on drops or refusals; scripts/test-discord.sh 28/28 (90 node tests)	Jason sees the reaction on a live message	2026-09-13_discord-connector-pilot.md section 11
16	Repository-native development bootstrap: five internal agents, Darkwing coordination	darkwing; filbert reviews	#1510	source approved by internal Filbert, exact R1 receipt 26204; six offline tests independently pass in both copies; 24 config tests and five no-effect checks are author evidence	source approved; Researcher live response passed 26216; existing native Rocko lock preserved, no new Rocko model test; no MVP acceptance/publication	2026-09-13_internal-development-bootstrap.md
17	Discord connector: systemd user service with a supervised pre-start (recover, exit 3 never retried) (MVP iteration 2)	coordinator	#1509	done, operator-verified by Jason 2026-09-13 (all four steps): scripts/test-discord.sh 40/40 (95 node tests); Sage seat migrated 19:35 UTC, SIGKILL recovered in 16 s with the dead lock cleared, brake held (exit 3, no restart), released and READY; receipt mvp2-service-unit-*.json in the private evidence dir. First cut (ExecStartPre) looped and was replaced by run --supervised before any traffic	the Sage connector runs under mosaic-discord@shared-signals, survives a kill with a clean restart, and stays down behind discord.sh stop	2026-09-13_discord-connector-pilot.md section 11
18	Control board row for the Discord connector (MVP iteration 3): discovery from binding files, liveness from run.lock, reply refused	darkwing (Jason's ruling 2026-09-13); coordinator answers connector-side questions	#1509	done for bounded local delivery; Jason accepted visual test (parfait), R3 26257 reviewed, 322 tests and live 409 refusal verified; no publication or live connector state transitions claimed	a Sage (discord) row on the board shows live, offline and braked correctly, and reply from the board is refused	2026-09-14_discord-board-row.md; original pilot section 11
19	Discord connector: binding reload without a restart (reload verb, SIGHUP, systemctl --user reload); channels, users, limits and guildName apply in place, identity, engine and context stay fixed, an invalid file is refused and the old binding kept (MVP iteration 4)	coordinator	#1509	done: caaef941; live 00:03 UTC: reload applied Carmen's entry with no restart, unknown key refused by the CLI (exit 2), fixed key refused in the process with the binding kept, systemctl --user reload applied; suite 41/41 (101 node tests); receipt mvp4-5-reload-carmen-*.json	edit the binding, run scripts/discord.sh reload shared-signals, the change applies with no restart, a broken edit is refused and journaled	2026-09-13_discord-connector-pilot.md section 11
20	Discord connector: per-user channel allowlist in the binding and Carmen enrolled (all listed rooms except #sage-admin) (MVP iteration 5)	coordinator	#1509	done: caaef941 (users[].channels allowlist, channel-not-for-user drop); Carmen enrolled live by reload 00:03 UTC; her first message is the remaining check	Carmen gets a reply in #general and silence in #sage-admin; Jason unchanged	2026-09-13_discord-connector-pilot.md section 11
21	Discord connector: read-only tools for the Discord Sage through a Mosaic pi extension confined to declared roots (MVP iteration 6)	coordinator; reviewer per Q12	#1509	approved: rev-code-02 round 2 verdict 26276 (tree 43f0329b); committed locally; live check in #sage-admin with Jason next; Jason ruled R1–R7 2026-09-14 (roots docs/ and agents/sage/, Carmen included)	Sage answers a question from a file under a declared root with the reads in the turn record; a read outside the roots is refused and recorded	2026-09-14_discord-readonly-tools.md
22	Board attention status: completed replies idle, explicit human input waiting	darkwing; filbert reviews	#1503	source approved, receipt 26248; reviewer 193 per copy, author union 213 pass; actual Researcher scan idle	operator accepted full targeted status sequence: explicit request waiting, Seen hides attention but preserves waiting, completion returns idle; broader MVP/cross-harness acceptance and publication separate	2026-09-13_board-attention-status.md
23	Discord connector: writes confined to the shared-signals root plus web fetch and search for the Discord Sage (MVP iteration 7)	coordinator; reviewer per Q12	#1509	done 2026-09-27 (Sage, lead decision 29): committed and pushed 1685deb4; live turns wrote vault/Businesses/naming.md with web_search and web_fetch in the turn record; the outside-root refusal rests on the offline suite, not a live turn	Sage writes a naming shortlist into the repository from #ideas with the write and web calls in the turn record; a write outside the root is refused	2026-09-16_discord-write-and-web-tools.md
24	Discord connector: git verbs (status, commit, pull ff-only, push) for the Discord Sage on the shared-signals root, seat identity through the existing credential helper (MVP iteration 8)	coordinator; reviewer per Q12	#1509	done 2026-09-27 (Sage, lead decision 29): committed and pushed 1949ed8d; live-configured 2026-09-18, never used from Discord; records now go through row 25 and SetSpark cutover freezes vault/, so first real use is the check and a failure opens a new issue	Sage commits and pushes a decision file from #ideas; GitHub shows Sage as author with a Requested-by trailer; no token in any record	2026-09-16_discord-git-tools.md
25	Discord connector: SetSpark record client for the Discord Sage, fixed verbs against setspark-api, connector-verified approvals (MVP iteration 9)	coordinator; reviewer per Q12	#1509	done 2026-09-26: committed and pushed 43d7574d, live check passed (DEC-010, request 2, approved by button at 21:38:58Z, lead decision 19); approver rule enforced by the service since shared-signals cc74d92 (lead decisions 24 and 28)	Sage creates one work item from #sage-admin and the API shows it with revision 1; a proposal is approved by the Approve button and the audit row carries Sage's key id and Jason's Discord id separately; rev-code-02 approves on #1509	2026-09-20_discord-setspark-client.md

Start message for row 6, sent from the board to darkwing: "Read docs/plans/QUEUE.md, then the plan page section "Piece 5: darkwing on point", and execute it. Start with the first assignment for filbert. Report at Gate F or when blocked."

Parked (not in order, needs Jason to reopen)

Item	Why parked	Where
Registry increment 3 (headless identity-env leak)	#1500 closed on increment 2; Jason has not asked for 3	CURRENT.md, "#1500 increment 2 (historical)"
Auth/provider/harness registry review	Paused for owner alignment	docs/plans/2026-09-03_auth-provider-harness-registry.md
CI runners, second real adapter, push automation	Deferred by owner 2026-09-03	docs/plans/ROADMAP.md, "Explicitly deferred"
Console features outside the refined session-chat brief, including Fresh creation and model switching	Deferred by WEBUI Q1; required history/control/stop now belong to row 5, not this parked item	2026-09-13_webui-session-chat.md
Open gaps from the MVP work	Fixed only when a gate needs them	DEFERRED.md, "Open"

Log of table changes

Frozen at genesis. Since then the log in docs/plans/queue.json records every change; the entries below are history.

• 2026-09-13 — created; rows 1 to 8 taken from CURRENT.md, DEFERRED.md and the plan page.

• 2026-09-13 — rows 9 to 13 added (#1508): the process itself becomes data with one writer and ledger checks. Jason: "I want this iron-clad." Required, not parked; rule: these rows cannot be moved to parked, only to done.

• 2026-09-13 — dewey: WebUI row advanced to Jason-owned Gate E after Filbert approval, exact committed-tree 208/208 and remote-verified ea00ec66 publication. No other row changed.

• 2026-09-13 — rows 9 to 13 now point at the plan page 2026-09-13_queue-as-data.md (pieces A to E, Gate G).

• 2026-09-13 — dewey: Jason feedback blocks WebUI Gate E pending refinement; project/session chat navigation, two-way conversation and relative activity age required. Durable #1507 comment 26082; no implementation begun.

• 2026-09-13 — coordinator: row 14 added (Discord connector pilot for Sage on Shared Signals), briefed, unassigned, waiting on Jason for decisions D1-D7. No other row changed.

• 2026-09-13 — coordinator: row 14 moved to in progress (#1509) after Jason ruled Q1-Q27 through ms-grill-me. No other row changed.

• 2026-09-13 — coordinator: row 14 moved to in review; package, suite, wrapper, DISCORD-USER.md draft and README written, offline and existing suites green. No other row changed.

• 2026-09-13 — coordinator: row 14 stays in review; rev-code-02 round two findings (26121) fixed, round three requested. No other row changed.

• 2026-09-13 — coordinator: row 14 stays in review; rev-code-02 round three finding (26123, stale reclaim race) fixed by failing closed plus unlock, round four requested. No other row changed.

• 2026-09-13 — coordinator: row 14 stays in review; rev-code-02 round four finding (26132, unlock restore race) fixed with a STOP quiescence gate, round five requested. No other row changed.

• 2026-09-13 — coordinator: row 14 stays in review; rev-code-02 round five findings (26150, boot identity and unlock wording) fixed, round six requested. No other row changed.

• 2026-09-13 — coordinator: row 14 stays in review; rev-code-02 round six finding (26158, legacy record and unreadable record must refuse) fixed, round seven requested. No other row changed.

• 2026-09-13 — coordinator: row 14 stays in review; rev-code-02 round seven finding (26165, malformed identity strings must refuse) fixed, round eight requested. No other row changed.

• 2026-09-13 — coordinator: row 14 stays in review; rev-code-02 round eight finding (26168, noncanonical start digits must refuse) fixed, round nine requested. No other row changed.

• 2026-09-13 — coordinator: row 14 moved to in pilot; approved 26170, committed 786e379c (no push), check passed, connector running. No other row changed.

• 2026-09-13 — coordinator: row 14 done; Gate H passed, Jason ruled the replies read as Sage. Connector stays up; MVP improvements come as new rows. No other row changed.

• 2026-09-13 — coordinator: row 15 added and done (Discord read receipt, Jason's request after the pilot); committed after suites green. No other row changed.

• 2026-09-13 — coordinator: row 15 moved to in verification; committed 93d6b624, connector running the new code, waiting for Jason's live message to show the reaction. No other row changed.

• 2026-09-13 — coordinator: row 15 done; live reaction confirmed by Jason and by the turn record. No other row changed.

• 2026-09-13 — coordinator: rows 14–15 pushed on Jason's authorization (788515dc..dc5902aa to origin/refactor). No other row changed.

• 2026-09-13: Darkwing recorded Jason's repository-native development priority as row 16, #1510. Darkwing coordinates the five internal agents; row 8 is held with no ~/.mosaic changes. CHAT-01C row 5 access text corrected to current push:true but Git HTTP 403. R1 26201 sent to default-socket Filbert for independent source review. Other owners' rows preserved.

2026-09-13: #1510 internal Filbert APPROVE AS SOURCE for exact R1, manifest SHA256 23a27014ce6f04ce8187d8495b2efe62b814c3c7d041b027f99b1ec4d490709d. Both verdict and subsequent nine-file hash supplement agree with frozen candidate. Darkwing persisted attributed approval and all nine pins through verified Darkwing API identity, receipt 26204. Filbert independently passed six fake-engine tests in working and frozen copies; five no-effect startup checks and config 24/24 remain author evidence. No live interoperability, publication or user acceptance claimed. Reviewed source/charter left unchanged; prior owners retain their edits.

• 2026-09-13 — coordinator: row 17 added, in verification (Discord service unit, iteration 2 on Jason's "proceed as suggested"). No other row changed.
• 2026-09-13 — coordinator: row 17 done; the Sage connector runs under systemd, kill and brake checks passed live. No other row changed.
• 2026-09-13 — coordinator: row 18 added, briefed; board-side work in darkwing's package, owner for Jason to rule. No other row changed.
• 2026-09-13 — coordinator: rows 17–18 pushed (dc5902aa..90cb31f5 to origin/refactor) under the jarvis git identity on Jason's authorization. No other row changed.
• 2026-09-13 — coordinator: row 18 assigned to darkwing by Jason ("darkwing should build the board row"). Coordinator no longer holds a Discord row in progress. No other row changed.
• 2026-09-13 — coordinator: row 17 operator check passed (Jason: all tests successfully verified, 21:29 UTC). No other row changed.
• 2026-09-13 — coordinator: rows 19 (binding reload) and 20 (per-user channels, Carmen) added on Jason's "proceed in order"; row 19 in progress. No other row changed.
• 2026-09-13 — coordinator: rows 19–20 done (caaef941, live reload 00:03 UTC, Carmen enrolled); Carmen's first message pending as the operator check. No other row changed.
• 2026-09-14 — coordinator: row 21 (read-only tools) briefed on Jason's "let's move to tools"; Carmen's test deferred by Jason; waiting on D1–D3 in the brief. No other row changed.
• 2026-09-14 — coordinator: row 21 rulings in (brief section 7); building the extension, engine settle change and binding key.

2026-09-14T00:09:08.161174+00:00 | Darkwing | #1503 board attention correction, row 21 | Jason approved idle for completed replies and waiting only for explicit human-input requests after reporting screenshot step-5 failure. New tests reproduced two failures before scanner correction. Phase entry recorded after implementation, not represented as an earlier entry. Working and frozen four-package suites now pass 144 tests each. Read-only actual Researcher scan returns alive:true, idle, waitingOnYou:false at lastActivity 2026-09-13T21:19:57.102Z. Explicit Input needed first-line convention, precedence and Seen lifecycle documented/tested; downstream fixture change acknowledged by Dewey. R1 26247 posted/read back as Darkwing and sent to internal Filbert, application verdict pending. No running-board restart, home launcher edit, agent restart or publication.

2026-09-14T13:08:27.885681+00:00 | Darkwing | Queue collision correction | Git c4fc8e7d and index independently confirmed Discord read-only tools already owned row 21. Restored that committed row verbatim, moved Darkwing attention status to row 22, updated active CURRENT/charter/row1 cross-references. Historical row-21 attention mentions now refer to row 22; append-only logs and frozen review snapshots not rewritten. Unique ordered IDs 1-22 verified. No staging, commit, source/service changes or changes to coordinator-owned tools brief. Row21 newer work status remains coordinator-owned; no status inferred from this restoration. Incoming source label unverified has no established return address; acknowledgment routing unresolved.

• 2026-09-14 — coordinator: row 21 rulings in (brief section 7), built and approved by rev-code-02 (26276); suite 48/48, 116 node tests; committed locally, live check next. No other row changed.
• 2026-09-16 — coordinator: row 23 added and briefed (Discord writes and web, Jason: "A + web"); Discord profile Q16 line replaced by Jason's word and Sage restarted. No other row changed.
• 2026-09-16 — coordinator: row 23 part 1 (write_file, edit_file confined to roots marked write: true; extension renamed tools.mjs) built and pinned for rev-code-02 round 1; Discord Sage's stale pi session archived and the service restarted so old Q16 refusals stop repeating.
• 2026-09-16 — coordinator: row 24 (git verbs for the Discord Sage) briefed at Jason's word; row 23 writes enabled live in the private binding ahead of the review verdict, web tools built and under test.
• 2026-09-16 — coordinator: row 23 part 2 (web_fetch, web_search via SearXNG, src/web.mjs) built; engine test busy/settled race fixed in the test; suite 52/52, node 128; round 2 pinned on #1509 comment 26358 for rev-code-02. Row 24 still waits on D5–D7.
• 2026-09-16 — coordinator: row 23 part 3 live (SearXNG container mosaic-searxng on 127.0.0.1:8888, binding web key, restart); Jason's first web turn worked end to end but exposed a live defect: a second message during a turn was sent as a pi follow-up and lost the first answer. Engine now holds it until pi settles. Suite 52/52, node 129; round 3 pinned as #1509 comment 26361; service restarted with the fix. Row 24 rulings D5–D7 recorded.
• 2026-09-17 — coordinator: shared-signals-05 briefed the new id registry and file lock protocol (jetrich/shared-signals 8f0d946); folded into the row 24 brief section 6 (validate before commit, reserve_id tool, per-write clone lock, explicit-path staging). No row changed.
• 2026-09-18 — coordinator: row 23 pushed on Jason's word ("push as well"): refactor 90cb31f5..1685deb4, seven commits, identity jarvis. Row 24 built and under test: four git verbs plus reserve_id, package credential helper (the fleet helper cannot serve github.com), requester in the envelope, explicit-path staging; suite 58/58, node 143; review requested from rev-code-02 on #1509.
• 2026-09-18 — coordinator: Jason's decision, relayed by the SetSpark record-system coordinator (thread 8543de4b, confirmed by Jason as acting on his authority): record authority moves from the Git vault to NocoDB (structured records) plus Outline (prose) on VM 1022, Pocket ID identity. This session is Sage's client: an HTTP tool module with fixed verbs, a fine-grained token from a 0600 file, output caps and one journal entry per call, built after that coordinator's plan is reviewed. Row 24 git verbs stay live until cutover; the vault becomes a read-only mirror after. Verb list and audit columns sent to the coordinator. No row change yet; a row 25 brief follows their plan.
• 2026-09-20 — coordinator: SetSpark plan v3 reviewed (Phase 2 rules, Phase 3 verbs); all eight objections from the v2 review adopted; answered "phase 3 ok" with two non-blocking notes. Write target is setspark-api at api.setspark.io; row 25 brief waits on the accepted plan.
• 2026-09-20 — coordinator: plan v3.1 committed on shared-signals main (361380c). Approval flow for row 25: open_approval_request on proposal post; the connector resolves the Approve button or an exact "approve" reply, checks the required-approver list, and submits request id, author id and message id. REF-045 conflict cleared by the REF-047 renumber (9287d49); row 24 live check unblocked. Phase 3 code waits on Jason's go.
• 2026-09-20 — coordinator: Jason's go for phase 3 relayed (plan v3.2, shared-signals 55b2515). Row 25 part 2a built: setspark.mjs (config, key read per call, HTTP core, refusal rendering), approvals.mjs (ledger, reply and button resolution), connector posts the request message with the button, binds it, submits approvals, retries unknown ones on start. Tests 157 node, suite 62. Part 2b waits on stack/api/openapi.json. Contract needs (open without a message, bind, add_approval with request id, author id, message id) sent to the coordinator and adopted, with bound_message_id added on add_approval and a request_stale code; openapi.json being regenerated.
• 2026-09-20 — coordinator: contract committed (shared-signals a5425a2). Row 25 part 2b built: eight model verbs (record_list, record_get, record_create, record_update, resolve_id, open_approval_request, get_approval_request, create_document; get_counters left out), the connector's api client (bind, add_approval with kind button or reply, get), the envelope's author and message ids read by the extension for the write keys. Coordinator's ruling on button evidence: the connector posts a confirmation line and submits its url and text as source_url and statement; a reply is its own evidence. Node 162, suite 63. Next: rev-code-02 review on #1509, then a local commit.
• 2026-09-26 — sage (lead): Jason made Sage the project lead and Darkwing a collaborating seat. Rows 23–25 states reconciled with git: 1685deb4, 1949ed8d and 43d7574d are all on origin/refactor (the last two pushed today at Jason's word); each row's live check is still open. No other row changed.
• 2026-09-26 — dewey: row 5 State corrected to git; b023841c (CHAT-01C) is on origin/refactor, so the held-publication and HTTP 403 text was stale. CHAT-02..08 held pending Jason via Sage. No other row changed.
• 2026-09-26 — darkwing: row 6 State updated. #1511 and #1512 committed locally in af4203ca at Sage's ruling, on the serial acceptance evidence; the concurrency-only engine failures are filed against #1509. No other row changed.
• 2026-09-26 — sage: row 5 State: CHAT-02 landed (backend a5beb6d9, Console c9e771cf) and passed its live check through the restarted WebUI. CHAT-03 waits for Jason. No other row changed.
• 2026-09-26 — sage (lead): row 5 State: Jason approved CHAT-03. Dewey writes the brief; Filbert and Rocko review; the source author slot waits for Darkwing after A1/A2. No other row changed.
• 2026-09-27 — sage (lead): rows 9 and 11 State: queue A1 committed (34a72af9) with the brief template; A2 in progress. No other row changed.
• 2026-09-27 — sage (lead): row 5 State: CHAT-03 source work waits after brief r3 for a rescope against Gate E. Row 7: Sage runs the ledger each Monday. Weeks 09-13..19 and 09-20..26 came to 47.7 and 33.0 human messages per closed issue, against a target under 10. See docs/plans/2026-09-27_goals-review.md, lead decision 27. No other row changed.
• 2026-09-27 — sage (lead): rows 1, 6, 23, 24 and 25 done (lead decision 29). #1503, #1509 and #1511 closed with evidence comments. Gate F recorded as not passed; Gate G carries its test. No other row changed.
• 2026-09-27 — sage (lead): priority line: Jason ratified the goals review (north star and goal order). No row changed.
• 2026-09-27 — sage (lead): row 5 State: CHAT-03 brief pinned at 1ef15ac0 after the scope check. Source author named after A2. No other row changed.