docs(records): Sage lead handover, rows 23-25 state, row 8 stub, BUILD-LOG rebuilt on HEAD

Records Jason's 2026-09-26 ruling: Sage leads the project, Darkwing is a
collaborating seat, development stays in T3, and the old ~/.mosaic fleet is
being retired. The lead role adds no push, merge or deploy authority.

- QUEUE rows 23-25 show their commits and pushes; row 8 links a parked stub
  brief listing the rulings Jason must make before fleet seats move.
- Shared records from Darkwing (rows 6, 16, 18, 22, #1511, #1512) and Dewey
  (row 5) that were waiting on one owner for the shared files.
- DEFERRED: T3 headers counted as human in the ledger (#1506), #1509 engine
  test leak and busy gap, #1512 re-run outcome.
- BUILD-LOG.md rebuilt as HEAD plus the uncommitted entries; the working copy
  had dropped the row 23-25 entries. Diff against HEAD is additions only.

All eight suites green. Not pushed.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

AGENTS.md

@@ -47,19 +47,106 @@ green at every step. Not production software — a proven foundation.
 9. **Append-only logs**: BUILD-LOG.md (phases), `activation-log.jsonl`,
    `.pruned.log`, docs/SESSIONS.md. Corrections are new entries, never edits.
 
+## Autonomous operation within an agreed plan
+
+Autonomy starts after alignment, not before it. For a new substantial assignment,
+recover the applicable mission, goal, task, `CURRENT.md` state, and prior owner
+decisions, then work with the user to establish a plan of action: the intended
+outcome, acceptance evidence, boundaries, and any gated actions. Recommend a
+concrete plan instead of presenting an open-ended menu. A direct request or
+existing approved plan that already settles those points is sufficient alignment;
+do not ask for ceremonial reconfirmation.
+
+Once the plan is established, carry it to verified completion without prompting
+for routine decisions or permission to take the next in-scope step. Authorization
+persists for the life of that assignment unless the user changes or revokes it.
+Treat mid-session user input as steering: incorporate it, update the plan or
+tracking record when needed, and continue.
+
+### Decide and continue
+
+- Resolve naming, implementation approach, layout, and similar non-breaking
+  choices from, in order: repository invariants and role policy, the approved
+  plan and acceptance criteria, established repository conventions, then the
+  smallest reversible option. Record a consequential choice and its tradeoff.
+- Perform the in-scope investigation, edits, tests, documentation, and tracking
+  needed for end-to-end acceptance. Do not ask whether to add obviously required
+  tests or documentation.
+- Diagnose failures and retry or remediate within the agreed scope. Fix a defect
+  when it blocks acceptance or is local to files already being changed; otherwise
+  record a bounded follow-up without expanding the assignment.
+- Resolve minor ambiguity in favor of the mission, goal, north star, and prior
+  owner decisions. State the assumption in the completion report.
+- Never stop merely to ask whether to proceed, which routine option to use, or
+  whether to execute the next step already contained in the plan.
+
+### Re-align or stop only at a real boundary
+
+Finish all independent work first, then ask one focused question only when:
+
+1. Two plausible readings materially change the outcome and the choice is costly
+   to reverse.
+2. The next action would exceed the agreed scope or authority, introduce an
+   unapproved breaking public/API/schema/data/policy change, or alter a security
+   boundary.
+3. Credentials or access are missing and no in-scope path remains.
+4. The action is destructive, irreversible, production-affecting, incurs spend,
+   or communicates externally on the user's behalf without explicit authority.
+5. Objectives or owner decisions genuinely conflict and repository evidence
+   cannot resolve them.
+6. A fail-closed policy refusal or another agent's overlapping ownership prevents
+   safe progress. Diagnose and report it; never route around it.
+
+Repository gates still apply. In particular, a successful implementation or a
+broad request to “finish” does not by itself authorize push, merge, deployment,
+release, production changes, policy/role expansion, or access to secrets. Perform
+such an action only when the established plan explicitly includes it. If blocked,
+report the exact boundary, what is complete, the recommended resolution, and the
+specific action that will resume; do not use “waiting for confirmation” as a
+substitute for a real blocker.
+
 ## Session protocol (mandatory)
 
 - **Register** your session in `docs/SESSIONS.md` — one append-only line
   (date, actor, scope, outcome). Never rewrite or remove entries.
 - **Cadence**: read `docs/plans/QUEUE.md` first; your next piece is the first
-  row you own that is briefed, in progress or in review, nothing else. Open only
-  the brief that row links to. Execute it fully (implement → test → verify against acceptance criteria → commit →
-  push → close issue) → move your QUEUE.md row → register in SESSIONS.md.
+  row you own that is briefed, in progress or in review, unless Jason has named
+  an explicit current priority in that queue. Open only
+  the brief that row links to. Execute it through every authorized stage (implement → test → verify against acceptance
+  criteria; commit, push, or close only when the established plan authorizes
+  each) → move your QUEUE.md row → register in SESSIONS.md.
 - "next" means one action. A batch mandate ("run the queue") repeats the
-  loop until green or blocked. Blocked means stop and report, never improvise.
+  loop until green or truly blocked under the boundary rules above.
 - Substantial work gets a Gitea issue and a BUILD-LOG phase entry
   (before/after, with corrections recorded honestly).
 
+## Internal development bootstrap
+
+Jason's current direction is repository-native development in
+`/mnt/storage/src/mosaic-stack`. Sage leads the project (Jason's ruling,
+2026-09-26) and coordinates coding, review and research through Darkwing, Dewey,
+Filbert, Rocko, Researcher and any further seats Jason launches under `agents/`.
+Darkwing is a collaborating agent seat, not the coordinator. Development sessions
+run in T3 for now. Work moves to the new stack; the old `~/.mosaic` fleet is being
+retired, and a fleet seat acting outside Jason's instructions is the failure this
+transition exists to prevent.
+Do not assign new development work to fleet seats during this bootstrap phase.
+Do not modify `~/.mosaic` launchers, provisioning or other state, or stop/migrate
+live fleet processes as part of this work. Preserve existing work and histories.
+Use the repository bootstrap/configuration and launch entry points; missing
+configuration still fails closed. This changes development coordination, not
+managed worker role policy or deployment authority. The lead role adds no push,
+merge or deployment authority; those still need Jason's say-so. See
+`agents/README.md` for the internal roster.
+
+For control-board attention, start a completed reply with `Input needed: ` and
+one specific nonempty request only when Jason must provide a decision or input.
+Put that line at column zero, before other text. Do not use it for routine
+completion or a wait on another agent. Ordinary completed replies are idle.
+Use code fences or blockquotes when showing this convention as an example.
+The signal is advisory status, never permission for a protected action. Seen
+acknowledges a request; it does not resolve it. See `packages/control-board/README.md`.
+
 ## Role model
 
 - **Conductor**: a system-scoped role — not an agent, not a daemon. Holds

BUILD-LOG.md

@@ -2241,6 +2241,84 @@ QUEUE and CURRENT now name Jason-owned Gate E, Monday 2026-09-14. Issue stays
 open. No live-seat exchange, deployment, unrelated staging or new queue execution.
 Receipt: docs/plans/reviews/2026-09-13_webui-publication.md.
 
+## 2026-09-13 — Session-chat refinement and owner confirmation (#1507)
+
+Jason reported the board-only Console cannot satisfy his workflow. Before:
+Gate E was waiting on the original workday test. After: Q1-Q22 refined through
+ms-grill-me, prior accepted foundation decisions recovered, and an 11-task
+protocol/implementation/publication/cutover graph written in
+docs/plans/2026-09-13_webui-session-chat.md. Filbert and Darkwing planning
+findings were incorporated, including private remote implementation, separate
+publication, complete input fencing and preserved fleet dependency ordering.
+Jason confirmed shared understanding and bounded CHAT-00 preparation in this
+session; durable issue comment 26093. Darkwing received CHAT-00 charter/execution
+request via agent-send rc 0; application acknowledgement pending. Filbert received
+correction-closure review request rc 0. No runtime code, live migration or other
+queue work started. Original ea00ec66 approval remains bounded to old scope.
+
+## 2026-09-13 — CHAT-00 protocol preparation charter (#1507)
+
+Before: expanded WebUI behavior agreed but engine/security contracts unverified.
+Jason confirmation 26093 authorizes bounded preparation; charter 26094 names
+Darkwing author, Filbert independent reviewer, docs/plans/chat-00 research
+artifacts and synthetic offline fixtures only. No runtime package, credential,
+private-session, live fleet, launch, policy or historical-contract edits.
+Deliverable chat-00/README.md will distinguish source evidence, proposals and
+implementation blockers. Q22 ordering retained; separate #1508 research stopped.
+
+CHAT-00 after investigation: docs/plans/chat-00 research candidate records Pi
+0.85.1 docs/types, observed Claude 2.1.270 version/help, pinned official Python
+SDK 0.2.152 source and official documentation retrieval hashes. Claude print
+trust/settings behavior and native tool isolation require further proof.
+48 synthetic/source checks pass; none tests engine/native/live enforcement.
+Rocko independent architecture review and four accepted qualifications recorded;
+Filbert exact-candidate review requested in #1507 comment 26099, agent-send
+rc 0, application acceptance unknown. Reviewer reply is the wake path; no timer.
+No source runtime, private data, policy, credentials or live seats changed.
+
+CHAT-00 closeout: Filbert APPROVED bounded research only in #1507 comment
+26100; all four exact hashes reverified. Q21-authorized research-only publication
+370823b354400a73425b4180e07747d97ff87e7a remote verified; committed research copy
+with existing pinned dependencies passes 48/48. No shared uncommitted planning
+or logs included in publication. B1-B6 remain; no runtime/security certification.
+Receipt and proposed, inactive CHAT-01 contract-only charter are comment 26102.
+Owner authorization is the next boundary; no engine probe or other queue start.
+
+## 2026-09-13 — CHAT-01 bounded contract drafting (#1507)
+
+Before: CHAT-00 research approved/published, no actionable draft record/operation
+contract. Jason approved the proposed bounded next step; charter 26103 names
+Darkwing author, Filbert independent reviewer, Dewey UI-contract consumer review.
+Only docs/plans/chat-01 draft/schema/synthetic checks plus scoped tracking.
+No runtime, historical-contract, auth, role, fleet, live or other queue work.
+
+CHAT-01 candidate #1507 comment 26105: 17 closed record variants and nine
+commands. Checks pass: 92 shape, 206 required-field omissions, 58 state/reference,
+7 queue, 4 page, 1 synthetic stream example; also pass in a clean four-file copy.
+Initial calendar-negative fixture caught absent optional RFC3339 validation;
+explicit UTC calendar checker fixed the defect with no dependency installation.
+CHAT-00 source/research regression remains 48/48. Filbert/Dewey/Rocko review
+requests dispatched via agent-send exit 0, Rocko acknowledged; responses pending.
+No engines, native protocols, auth, private history, actual races or live effects
+were tested. Review replies own the wake; no timer or other queue work.
+
+CHAT-01 R1 correction receipt: Filbert REQUEST CHANGES 26106, Rocko 16
+architecture findings via agent-send, Dewey REQUEST CHANGES 26108. Consolidation
+26107. R1 is not approved. R2 first correction pass adds typed proof/payload/
+native-decision records, private composer and confirmation commands, recovery
+control, multi-connection transfer, Interrupt reconciliation and Force stop
+escalation. Offline checks pass 80 shapes / 296 omissions / 66 reference cases /
+10 lifecycle sequences; CHAT-00 remains 48/48. This is WIP, not a pinned candidate.
+README reconciliation, Dewey UI1-UI4 dispositions and model consistency remain.
+Author self-check still needs per-item queue cancellation, immutable edit admission
+lineage, full frozen operation digest linkage and readback/cursor scope coverage.
+No native authentication, stream reconstruction, actual supervisor or runtime
+proof follows from these passing models. No publication or engine work.
+Provenance correction: R2 edits began before Dewey final read-back despite the
+stated R1 collection freeze. Dewey reviewed initial pinned R1 only; Darkwing
+acknowledged this sequencing error. All four R2 files require fresh complete pins
+and renewed independent review; changed working bytes inherit no approval.
+
 ## 2026-09-13 — Discord connector pilot, candidate built (#1509)
 
 Before: brief `docs/plans/2026-09-13_discord-connector-pilot.md` with Q1-Q27
@@ -2384,6 +2462,126 @@ Live check, 19:21 UTC: Jason sent a message in #sage-admin, the eyes reaction
 appeared on it before the reply, the turn record carries `receipt.ok` true,
 and a 0600 receipt sits in the private evidence directory. Row 15 done.
 
+
+CHAT-01 R2 correction checkpoint, 2026-09-13: 24 proposed record variants,
+20 bounded commands. Corrected per-item queue cancellation and all-or-none
+snapshot validation, immutable edited admissions/full frozen digest checks,
+public currentView, exact approval intent and unsupported forms, stable
+message/block/fragment/final-part addressing and snapshot watermark rules.
+Author checks pass 89 shapes, 316 required omissions, 70 reference cases, ten
+named lifecycle sequences plus additional queue/bootstrap/multipart regressions;
+CHAT-00 48/48, whitespace and node syntax green. Clean four-file copy at
+/tmp/chat-01-r2-frozen-3dymeauy matches hashes in posted/read-back request 26117.
+Filbert/Dewey/Rocko re-review dispatched rc 0, application acceptance initially
+unknown; Rocko subsequently acknowledged. Candidate frozen through all responses.
+Explicit proposed CHAT-01C/CHAT-03I/CHAT-03D companion dependencies block missing
+readback/content, authenticated message handoff and non-permission dialog APIs;
+reviewer acceptance requested rather than declaring these workflows implemented.
+No native/runtime/security/durability proof or live/publication effect. All
+independent ready author work complete for this candidate; peer replies own wake.
+
+CHAT-01 R2 independent verdicts: Filbert REQUEST CHANGES 26119, Dewey REQUEST
+CHANGES 26120, both read back. Author reproduced expired/foreign-conversation/
+expiry-equality cursors incorrectly observing, browser disconnect alone blocking
+admitted scheduler dispatch, and role-less NEW final events accepted while added
+user/assistant role is rejected. No candidate edits. Both reviewers explicitly
+accept bounded companion gates; Filbert closes R1 F1-F3, Dewey UI1/UI3/UI4.
+Acknowledgments dispatched rc 0. Rocko verdict remains the only collection wait;
+then one consolidated cursor/scheduler/role correction and new exact review.
+
+CHAT-01 R3, 2026-09-13: all R2 findings collected before changing the candidate.
+Rocko confirmed R1 blocking closures and companion acceptance, then reproduced
+corrupt-payload control deadlock, active revocation with only destructive exit,
+and disconnected scheduler refusal without disposition. R3 corrections include
+recovery-failed and dispatch-refused outcomes/events, non-destructive revocation
+proof/reopening, disconnected durable dispatch once, complete cursor expiry/scope,
+explicit NEW content roles, current receipt outcomes, superseded predecessor stops,
+native decision evidence, stop-context confirmation hashes and second-actor privacy.
+Author verification: 98 shapes, 322 omissions, 76 references, 17 lifecycle
+sequences plus regressions; syntax/whitespace green; CHAT-00 48/48. Same results
+from independent four-file snapshot /tmp/chat-01-r3-frozen-kk94phw4. Unmediated
+ingress assertion removed from lifecycle count; remaining modelling limitations
+are explicit, not security proof. Exact review request 26124 posted/read-back
+verified; Filbert/Dewey/Rocko requests dispatched rc 0, acceptance unknown.
+R3 files frozen for all three replies; R2 archive unchanged. No publication,
+engine, private state, policy change, runtime or other queue action.
+
+CHAT-01 bounded delivery completed, 2026-09-13: Filbert 26126 and Dewey 26127
+read-back verified, Rocko exact recovery/scheduler/composition approval received
+via agent-send and recorded with three non-blocking follow-ups in 26128. All
+three approvals name 26124 hashes. Q21 publication 28d4e98ad8b406ca84b30170558bee22402f1e55
+contains ONLY four CHAT-01 files. Pre-commit hashes/index and source checks green;
+committed copy byte-identical to reviewed snapshot passes 98/322/76/17 plus
+regressions. CHAT-00 48/48. Push succeeded; exact refs/heads/refactor verified.
+No CI/native/runtime/security certification claimed. Publication receipt 26131
+posted/read-back verified; Dewey/Filbert notified via agent-send rc 0. Shared
+uncommitted records and all other owners' files excluded from this commit.
+#1507 remains open. CHAT-01C next contract-only charter proposed in 26131,
+not active without owner approval; other companion/B1-B6/Q22/live gates retained.
+No engines, credentials, policy, deployment or other queue task started.
+
+## 2026-09-13 — CHAT-01C contract-only authoring and exact review (#1507)
+
+Before: owner approved proposal 26131; private readback/content and refused-input
+recovery remained blocked companion contracts. Attribution correction confirmed:
+seat credentials authenticate as darkwing (104), no minting needed. No legacy
+Jason-identity issue mutation used for this phase, no history/config rewrite.
+After: four draft files authored with closed private operations/projections,
+actor/scope/source/expiry-bound snapshots, verified byte ranges, bounded literal
+UTF-8 preview, confirmation restoration and explicit refused-input recovery from
+CHAT-01 frozen payloads. No dispatched/unknown replay. Nine closed examples and
+106 omission/extra-field refusals plus state regressions pass. Clean four-file
+snapshot /tmp/chat-01c-r1-frozen-yvsfowd1 passes; published CHAT-01 and CHAT-00
+regressions green, base files untouched. Exact review request 26137 posted and
+read-back verified with actual author darkwing. Filbert and Dewey dispatched
+rc 0, application acceptance unknown; peer replies own wake, no pane polling.
+R1 frozen pending both verdicts. No endpoints, native engines, live access,
+policy, deployment or other queue work. No authentication/durability/UI proof
+claimed from the supplied synthetic authority facts and idealized transactions.
+
+CHAT-01C R1 independent REQUEST CHANGES received in full from Filbert and Dewey
+via agent-send, then R2 corrections performed. Filbert F1/current confirmation
+terminal state and F2/colon-key collision; Dewey C-UI1/frozen queue content and
+causal joins, C-UI2/live confirmation stop/state overlay and C-UI3/receiving upload
+progress. All accepted and regression-tested. Attributed review persistence
+requested from orch-01 per Filbert, rc 0, no Jason-default issue mutations.
+R2 adds scoped current overlays, canonical tuple keys, bounded immutable input
+projections/availability, receiving byte counts and local-file matching semantics.
+Checks green: eleven closed examples/187 omission-extra refusals plus model cases,
+clean copy /tmp/chat-01c-r2-frozen-lujze3oe, base CHAT-01 and CHAT-00 regressions.
+Exact closure request 26149 posted/read-back under actual darkwing; both reviewers
+dispatched rc 0. Four files frozen through both replies, R1 archive unchanged.
+No runtime/native/authentication/durability/UI proof, publication or other queue work.
+
+CHAT-01C R2 closure/publication attempt: exact Filbert and Dewey APPROVE AS
+BOUNDED DRAFT received via agent-send and persisted with attribution as actual
+darkwing in 26152. Reviewed hashes and clean copy rechecked. Local commit
+b023841c8a44d08677dc388043997eb4277b0545 contains only four reviewed files;
+author/committer both Darkwing <darkwing@mosaicstack.dev>, verified against
+agent API email. Shared defaults/index contents and other dirty work preserved.
+Committed-copy checks green 11 examples/187 omission-extra plus models/baselines.
+NOT PUBLISHED: push using seat credentials and disabled default helper failed.
+Remote reconciled unchanged at 28d4e98a; darkwing repo permissions push:false,
+pull:true, admin:false; refactor unprotected. No unchanged retry or Jason fallback.
+Access/authorized publisher-route resolution requested from orch-01 rc 0, with
+exact commit/approval/owner-authority references. Blocker 26154 posted/read-back
+as darkwing. No role bypass, history rewrite, live/runtime or other queue action.
+
+CHAT-01C access update: Jason granted repository membership; verified darkwing
+API push:true. Reviewed commit/hash checks pass, but new seat-authenticated push
+failed HTTP 403. Remote unchanged at 28d4e98a; dry-run and read-only receive-pack
+discovery also return 403 Forbidden. Token scope/smart-HTTP authorization remains
+unresolved, not asserted as diagnosed. orch-01 notified rc 0; no Jason fallback
+or further unchanged write retries.
+
+## 2026-09-13: internal development bootstrap, #1510
+
+Jason authorized repo-native Darkwing coordination and source setup for Darkwing, Dewey, Filbert, Rocko and Researcher. No ~/.mosaic launcher/provisioning changes, live fleet migration or engine launch. This phase entry is recorded after initial implementation/checks, not claimed as a pre-implementation entry. Before: Researcher had only managed agent.json and a fleet persona. After: added native launcher, context, README, existing session-validation behavior, and the Researcher test roster. Shared team guidance changed only in scoped sections; other authors' edits preserved.
+
+Verification: node --test scripts/test-darkwing-launch.mjs scripts/test-rocko-launch.mjs passed six tests in working and frozen copies; scripts/test-config.sh passed 24; all five real --check calls passed without TUI/auth/model requests. R1 frozen at /tmp/internal-team-r1-i9t21yzr, exact manifest in CANDIDATE.sha256 and issue #1510 comment 26201, posted/read back as Darkwing. Default-socket internal Filbert review request dispatched rc 0, application acceptance pending. Source state is in review, not deployed or user accepted. Existing external provisioning request to orch-01 was superseded with the new no-home-directory-write boundary, dispatched rc 0; no claim that receipt was acknowledged.
+
+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 — Discord service unit (#1509, QUEUE row 17)
 
 Before: the Sage connector ran in a tmux window; a crash or a reboot left a
@@ -2411,6 +2609,8 @@ supervised run as the main process and re-verified: SIGKILL recovered in
 16 s with the dead lock cleared, brake held with no restart, released and
 READY. The Sage seat now runs under the unit; the tmux session is gone.
 
+2026-09-13: Darkwing #1510 owner-authorized live smoke. Researcher started natively and returned RESEARCHER_NATIVE_SMOKE_OK, recorded session entry/hash in agents/darkwing/work/internal-development-bootstrap/live-smoke.json, authenticated issue receipt 26216. Rocko duplicate startup refused: existing native Claude PID 3707667 has repo cwd, native context and Sonnet, on mosaic-fleet socket. No new Rocko model test, no existing process restart/migration, no home launcher/provisioning edits. Only newly created dead default-socket test pane removed. Source approval remains 26204; no full MVP acceptance or publication claimed.
+
 ## 2026-09-13 — Discord binding reload and per-user channels (#1509, QUEUE rows 19–20)
 
 Before: the binding was read once at start, so a ceiling, channel or user
@@ -2444,6 +2644,46 @@ revert applied with no differences; `systemctl --user reload` applied.
 Carmen's own first message is the remaining check. Her id is only in the
 binding file.
 
+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-14T00:12:52.493853+00:00 | Darkwing | #1503 attention R1 source approved by internal Filbert, verdict and nine pins persisted/read back in 26248. Reviewer independently passed 193 tests in each copy across board/seat/mosaic/WebUI; author 144 included ledger instead of mosaic. Five-package union now 213/213. No source drift. Next boundary is controlled replacement of listening backend PID 1265952 on 127.0.0.1:7331, awaiting owner authorization; existing agents remain untouched. No runtime fix or operator acceptance claimed yet.
+
+2026-09-14T00:21:09.242655+00:00 | Darkwing | #1503 owner-approved backend-only restart | Old PID 1265952 exited gracefully; replacement 3204655 healthy on 127.0.0.1:7331 with unchanged command/config. Live API now returns Researcher idle, waitingOnYou:false at original screenshot timestamp. Five agent PID/start identities unchanged. Evidence restart.json and restart-verification.json under agents/darkwing/work/board-attention; authenticated receipt 26249. Operator visual retest pending; no broader MVP acceptance, home launcher changes or publication.
+
+2026-09-14T00:31:46.602431+00:00 | Darkwing | #1503 targeted attention correction | Jason: "idle is confirmed". Operator visual acceptance recorded for Researcher completed-response idle status after live receipt 26249. Broader MVP/cross-harness acceptance and publication not inferred.
+
+2026-09-14T00:42:07.429237+00:00 | Darkwing | #1503 targeted status lifecycle operator accepted | Jason confirmed all five steps: explicit Input needed request sent, waiting/attention shown, Seen hides attention while waiting remains, TEST_COMPLETE reply requested, idle restored. Complements earlier ordinary-completion idle acceptance. No broader MVP/cross-harness acceptance or publication inferred.
+
+2026-09-14T00:52:54.277747+00:00 | Darkwing | #1509 row 18 actual start and continuation correction | Jason requires automatic continuation after accepted iterations. Prior assistant said it was continuing but ended without action; that was a violation, now acknowledged. Queue/current reconciled. Filbert acknowledged sole implementation ownership of scoped board/WebUI source; Darkwing independently reviews and Dewey acknowledged read-only UX review. Charter docs/plans/2026-09-14_discord-board-row.md. Independent baseline returned 200 and called fake transport once for a connector with forged native registration; no real send. Acceptance checklist and reply-baseline.json under agents/darkwing/work/discord-board. Kickoff entry recorded after dispatch/baseline, not claimed as before author work. Await exact candidate/tests by existing agent-send return route; no timeout armed. No unrelated queue start, source overlap, live connector/home change or publication.
+
+2026-09-14T00:59:49.989111+00:00 | Darkwing | #1509 row 18 author checkpoint received | Filbert reports connector discovery/identity/brake/refusal/dynamic discovery and minimal rendering implemented; six-package working suite 320/320 including Chromium fixture, prior attention fixtures preserved. Author-reported only; exact frozen candidate and second run pending. Acknowledged via default-socket agent-send rc 0. Next gate is immutable handoff for Darkwing backend and Dewey UX independent review. No source approval, live change or completion inferred.
+
+2026-09-14T01:12:24.257643+00:00 | Darkwing | #1509 row18 R1 independent review | Frozen nine/inherited pins verified; 320 serialized tests independently passed. Dewey approved scoped UX with three Chromium tests and retained limitations. Backend CHANGES REQUIRED R1-B1: uid1000 temporary journal containing STOP, mode000, produces braked:false instead of unknown. Evidence r1-backend-review.json. Author handoff and both verdicts read-back persisted as Darkwing in 26255. Filbert acknowledged bounded R2 correction; next wake exact candidate via agent-send. Two author concurrent frozen timeouts remain unresolved/not green. No source approval, live services/home edits or publication.
+
+2026-09-14T01:20:54.024167+00:00 | Darkwing | #1509 row18 R2 review | Nine working/frozen pins, two-file delta and inherited assets independently verified; serialized union 321/321. R1-B1 closed. Dewey exact R2 scoped UX approved with seven targeted tests and prior limits. Newly found R2-B2: canonical synthetic Discord routing envelope author/message IDs become public Task metadata; reproduction r2-envelope-review.json. Missed in R1 review, recorded honestly. Filbert acknowledged bounded fixed-task correction and regression, R3 pending via agent-send. Attributed author/reviewer receipts read back as Darkwing in 26256. No source approval, live observation/restart or publication. Concurrent R1 timeouts remain unresolved/not green.
+
+2026-09-14T01:30:57.305468+00:00 | Darkwing | #1509 row18 exact R3 source approvals and read-only live check | Darkwing verified nine working/frozen pins, inherited assets, three-file delta and 322/322 serialized tests; Dewey approved exact R3 with eight targeted tests and retained evidence limits. Both review findings closed. Author and both approvals read-back persisted as Darkwing in 26257. Authorized read-only actual shared-signals observation finds alive/idle, not braked, canonical owner matching systemd MainPID, safe fixed Task and no registration; r3-live-observation.json. Next gate is owner-approved backend-only restart then visual test; no connector/STOP/binding/home changes, backend restart or publication. Concurrent R1 timeouts remain unresolved/not green, now in DEFERRED.
+
+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-14T13:52:23.718141+00:00 | Darkwing | #1509 row18 owner-approved backend replacement | Verified exact R3 working pins; old backend PID3204655 exited gracefully, replacement3769124 healthy on 7331. Live shared-signals row idle/live/not braked, fixed safe Task, actual reply POST refused409 with explicit connector error. Five agent pane PID/start identities and connector systemd PID/start identity unchanged. Evidence backend-restart.jsonl and backend-live-verification.json under agents/darkwing/work/discord-board. No connector/STOP/binding/home changes. Await operator visual confirmation, then continue to next ready authorized item without routine prompt.
+
+2026-09-14T14:07:30.352051+00:00 | Darkwing | Row18 accepted; row6 code phase started | Jason answered parfait to the live Discord-row visual test. Bounded local delivery accepted; no publication or live brake/offline transition claimed. Following the newer standing automatic-continuation mandate, starting next already-briefed row6 under existing Piece5 plan, preserving row6-before-#1508 ordering and no home/fleet changes. #1511 created/read back as Darkwing; charter docs/plans/2026-09-14_task-attribution.md. Rocko native repo context/lock independently verified for source authoring; Filbert backend review, Dewey UX review. This code phase precedes Filbert's specified stale-relaunch assignment; GateF not yet claimed or backdated. Kickoff recorded before author dispatch.
+
+2026-09-14T14:09:36.358711+00:00 | Darkwing | #1511 actual continuation checkpoint | Rocko acknowledged sole native source ownership; Filbert and Dewey acknowledged independent review lanes. Missing --by reproduced through isolated CLI refusal, exit4, no live config/registration accessed; evidence agents/darkwing/work/task-attribution/baseline.json. Queue/current now point to row6 code phase; row18 operator acceptance recorded. Await exact author handoff through agent-send, no timeout armed. Source reviews precede any integration; no live or publication authority inferred.
+
+2026-09-14T14:25:14.147717+00:00 | Darkwing | #1511 R1 review gate | All 15 author pins matched frozen/working files; manifest 0185cc65c973f6d89c394e2e9fba67fccd794b8ad2be2720a8bb3700b2b018a3. Filbert source-backend approval, Dewey REQUEST CHANGES R1-U1 null/unknown inspector conflation. Both lanes collected before author correction dispatch. Rocko assigned bounded R2 UI/test fix plus inaccurate privacy-syntax prose correction. Reviews persisted agents/darkwing/work/task-attribution/r1-review.md; independent overlay141 and launcher6 logs read back green. Darkwing added only missing --by flag to TOOLS usage, exact owned patch reverse-checked and sent for Filbert review. Queue/current updated; no combined approval, live change, GateF or publication.
+
+2026-09-14T14:31:54.546546+00:00 | Darkwing | #1511 R2 source approved, protected test pending | Filbert and Dewey exact source approvals persisted in agents/darkwing/work/task-attribution/r2-review.md, R1-U1/comment findings closed; TOOLS owned patch approved separately. Darkwing combined serialized344/344 exit0; all15 working pins reverified afterward. Old-reader rejection of new field reproduced synthetically; no live records touched. Proposed backend-only restart and one Rocko task-metadata visual test awaits Jason, envelope agents/darkwing/work/task-attribution/live-test-envelope.md. No publication, GateF, Filbert behavior assignment or live acceptance claimed.
+
+2026-09-15T00:14:24.283987+00:00 | Darkwing | #1511 authorized backend update; target mismatch blocks test write | Old3769124 gracefully exited, new3414098 healthy, reviewed page byte-identical; API new attribution fields verified. Five agent pane identities, connector identity and every registration byte unchanged. Rocko target mismatch found before mutation: dead registered185602 versus native3707667, missing discovery directory and no row; existing DEFERRED Claude gap updated. No identity repair/relaunch or attribution write. Verified Filbert registration matches its native profile lock/cwd/tmux; requesting only test-target substitution. Receipts agents/darkwing/work/task-attribution/backend-restart.jsonl and backend-live-verification.json. No publication, operator acceptance or GateF claimed.
+
+2026-09-15T00:37:06.191367+00:00 | Darkwing | #1511 Filbert live attribution ready for visual test | Jason authorized target substitution and confirmed Claude console integration remains separate. Native Filbert record/lock/cwd/tmux matched; original record backed up privately outside repo. Reviewed CLI set only authorized task metadata; live API taskSource registration and taskSetBy darkwing verified. Other registration bytes and agent/connector/backend identities unchanged. No Rocko change. Receipt agents/darkwing/work/task-attribution/live-test.jsonl. Await operator visual confirmation; no publication, GateF or behavior assignment claimed.
+
+2026-09-15T00:45:55.295300+00:00 | Darkwing | #1511 operator confirmed; #1512 kickoff | Screenshot and pasted inspector confirm set by darkwing with caller-claim wording. Bounded attribution delivery accepted, publication remains separate. Next prescribed Piece5 Filbert assignment chartered in docs/plans/2026-09-15_relaunch-activity.md; #1512 created/read back as authenticated Darkwing. Filbert source author, Darkwing backend review, Dewey UX review. No GateF claim.
+
+2026-09-15T00:47:20.173732+00:00 | Darkwing | #1512 actual continuation verified | Filbert source ownership and Dewey UX review acknowledged. Independent isolated newer-launch/old-reply baseline reproduced, agents/darkwing/work/relaunch-activity/baseline.json. Accepted bounded presentation-only notice rule: positive row and PID liveness, valid strictly newer launch; retain history/state/Seen/attribution/reply semantics. Await exact frozen candidate via agent-send. #1511 table and inspector confirmation persisted in live-test.jsonl; publication and GateF remain separate.
+
 ## 2026-09-14 — Discord read-only tools (#1509, QUEUE row 21)
 
 Before: the Discord Sage ran pi with `--no-tools`; every answer came from
@@ -2606,3 +2846,29 @@ the frozen hashes were re-verified afterwards. No file was lost.
 Not done: the private binding change (keyFile at Sage's minted key), the
 live check in #sage-admin, the push. Outline collections are empty, so
 `create_document` answers 503 until BizOps creates them.
+
+2026-09-15T01:02:43.256672+00:00 | Darkwing | #1512 R1 source review and test hold | Exact seven-file manifest47769fada74c5684dd0ca32c41cea9dcf60e039f5a07657546e17a240af13e9d verified before/after. Darkwing backend and Dewey scoped UX approve source, Dewey8 targeted tests. First frozen full serialized run failed inherited Discord tool-turn case then timed out120s; diagnostic single case passed with force-exit, not acceptance. Later full TAP with15s test deadline and no force-exit passes351/351. Earlier failure unresolved; integration held, Rocko dispatched read-only inherited engine/fixture diagnosis. Scope/logs in agents/darkwing/work/relaunch-activity/r1-review.md. No source edits, live changes, publication or GateF claim.
+
+2026-09-15T01:15:49.697152+00:00 | Darkwing | #1512 diagnosis confirmed, provenance corrected | Rocko reported test busy/settled race plus success-only cleanup hang, timeout-log test race, and separate engine followUp-after-timeout concern. Darkwing independently reproduced controlled50ms event split failure with finally cleanup, exit1/148ms, no stress load; read refused-streaming fixture evidence. Row21 owner orch-01 notified through verified named socket; source ownership untouched. Filbert supplied append-only provenance correction: actual archive content1ac812d3, not stale HANDOFFc4fc label. Correction hash and89 dependency pins independently verified and copied outside R1; seven source pins unchanged. Provenance hold resolved, integration awaits owner engine/test disposition. Records agents/darkwing/work/relaunch-activity/engine-diagnosis.md and r1-provenance-correction.json. No live incident/change, publication, operator acceptance or GateF claim.
+
+## 2026-09-26: Sage lead handover and shared-records commit
+
+Before: the shared records (AGENTS.md, agents/README.md, QUEUE, CURRENT,
+DEFERRED, SESSIONS, BUILD-LOG) carried uncommitted edits from Jason, Darkwing,
+Dewey and Sage, and the working BUILD-LOG.md was missing the 133 HEAD lines
+committed with rows 23 to 25 (1685deb4, 1949ed8d, 43d7574d). After: Jason's
+2026-09-26 ruling is recorded (Sage leads, Darkwing collaborates, development
+stays in T3, the old fleet is being retired), QUEUE rows 23 to 25 show their
+commits and pushes, row 8 has a parked stub brief
+(`docs/plans/2026-09-26_fleet-seats-onto-mosaic-launch.md`), and DEFERRED
+carries the T3-header ledger miscount and the #1509 engine defects.
+
+Correction recorded: BUILD-LOG.md was rebuilt as HEAD plus the uncommitted
+entries in their existing order, with the restored row 23 to 25 entries placed
+before two Darkwing 2026-09-15 lines that were already at the end. Checked
+with a diff against HEAD: 244 lines added, none removed. The other shared
+files lose HEAD lines only where a row was deliberately edited.
+
+Evidence: all eight suites green on the working tree (config 24, task 90,
+foundation 43, conductor 17, release 14, auth 15, discord 63,
+extension-package 18). Not pushed.

agents/README.md

@@ -2,14 +2,21 @@
 
 These are interactive host development agents working in the canonical
 checkout. They do not create managed fleet registrations or change role policy.
-Darkwing leads development and coordinates assignments, review, and integration.
+Sage leads the project and coordinates assignments, review, and integration
+(Jason's ruling, 2026-09-26). Development sessions run in T3 for now.
+For the current bootstrap phase, direct coding, review and research use Darkwing,
+Dewey, Filbert, Rocko, Researcher and further seats Jason launches from this repository's `agents/` directory,
+not fleet seats. Keep changes in `/mnt/storage/src/mosaic-stack`; do not modify
+`~/.mosaic` launchers/provisioning or migrate/stop live fleet processes.
 
 | Agent | Responsibility | Runtime | Launch from repository root |
 | --- | --- | --- | --- |
-| Darkwing | Development team lead and hands-on engineering | Pi, configured Mosaic model | `agents/darkwing/launch.sh` |
+| Darkwing | Hands-on engineering; collaborating seat under Sage | Pi, configured Mosaic model | `agents/darkwing/launch.sh` |
 | Dewey | Frontend design, UX, accessibility, and UI implementation | Pi, configured Mosaic model | `agents/dewey/launch.sh` |
 | Rocko | General development, investigation, testing, and review | Claude Code, Sonnet model | `agents/rocko/launch.sh` |
 | Filbert | General development, investigation, testing, and review | Pi, `openai-codex/gpt-6-astra:low` | `agents/filbert/launch.sh` |
+| Researcher | Source-grounded technical research and evidence | Pi, configured Mosaic model | `agents/researcher/launch.sh` |
+| Sage | Project lead: coordination, review, integration; earlier DYOR strategy records retained | T3 session (Claude Code); Pi launcher `zai/glm-5.3:high` retained | `agents/sage/launch.sh` |
 
 Each script supports `--check` and `--fresh`. Normal launches resume the agent's
 own conversation; a first launch starts one. See each agent's README for
@@ -26,4 +33,10 @@ its own supplied flags or the system defaults.
 
 All agents follow repository governance and current user direction. Team
 leadership does not add deployment or push authority. Coordinate overlapping
-work with Darkwing and preserve other sessions' changes.
+work with Sage and preserve other sessions' changes.
+
+Before 2026-09-26 Sage worked only on DYOR strategy and sat outside the
+development queue. Jason then made Sage the project lead and Darkwing a
+collaborating seat. A separate fleet Sage seat under `~/.mosaic` is being
+decommissioned; it does not speak for this seat. Whether the DYOR strategy work
+continues is Jason's call. Joe retains DYOR engineering.

docs/SESSIONS.md

@@ -237,12 +237,50 @@ are never rewritten or removed; corrections are new entries.
 - 2026-09-13 — filbert, native Pi — WEBUI-1507-R1 independent review APPROVED for manifest 509f20e53292d5731c866d84c73cfaf539a89104b38b12a43260075ee7c3cb4d. All 21 hashes verified; separate baseline-plus-candidate copy passed WebUI 6/6 and combined 208/208 including Chromium, 330 contrast samples and five widths. Four fresh screenshots inspected. Verdict: docs/plans/reviews/2026-09-13_webui-verdict.md. No source edits or publication; Gate E remains Jason-owned.
 
 - 2026-09-13 UTC — dewey — #1507 source published ea00ec66, exact remote verified, exact committed-tree tests 208/208 after Filbert APPROVED manifest 509f20e5. Scoped tracking records Gate E ready for Jason Monday; issue open, no deployment or unrelated source edits.
+
+- 2026-09-13 UTC — dewey — Recorded Jason WebUI acceptance feedback in #1507 comment 26082 after inspecting both supplied screenshots. QUEUE/CURRENT now hold Gate E for session-chat refinement and activity age. Existing publication evidence preserved; no code, backend, transport or fleet changes.
+
+- 2026-09-13 UTC — darkwing — #1507 planning/ownership review in issue comment 26088, delivered to Dewey via agent-send exit 0, application acceptance unknown. Supported packages/conversation separation and proposed backend ownership; required foundation tool-isolation disposition, all-ingress fencing, per-seat cutover/auth scope, and explicit fleet/#1508 ordering resolution. Ordinary Interrupt recommendation awaits Jason. No implementation, live work, global queue changes, commit or push.
+
+- 2026-09-13 UTC — dewey — #1507 ms-grill-me Q1-Q19 recorded in issue comments, assembled docs/plans/2026-09-13_webui-session-chat.md with dependency-ordered tasks and recovered foundation decisions. Filbert/Darkwing planning corrections incorporated. Q20 Interrupt, Q21 expanded publication, Q22 fleet ordering and final shared-understanding confirmation remain; no implementation or live effects.
+
+- 2026-09-13 UTC — dewey — #1507 Jason confirmed Q1-Q22 and assembled plan, authorized bounded CHAT-00 preparation; issue comment 26093. Darkwing charter/execution request and Filbert plan-closure request dispatched rc 0. Scoped tracking released to Darkwing for CHAT-00; no runtime/live effects.
+- 2026-09-13 UTC — darkwing — CHAT-00 owner confirmation 26093 verified; charter 26094 posted and Dewey notified via agent-send rc 0. Bounded protocol/contract research and synthetic fixture artifacts under docs/plans/chat-00 only; WebUI tracking handoff acknowledged. No new subagent, runtime implementation, live effects or other queue start.
+- 2026-09-13 UTC — rocko — #1507 CHAT-00 independent architecture review (Jason steering comment 26097): read plan 4c436f4c s3-5, RUNTIME.md s1-5, charter 26094, pinned Pi 0.85.1 docs and claude 2.1.270 help only. Findings (rpc.md pin drift, Pi/Claude tool-isolation conflicts, single-writer and all-ingress proof gates, decomposition) sent to darkwing via agent-send rc 0 for posting. No source edits, launches, private state or fleet inspection.
+- 2026-09-13 UTC — darkwing — CHAT-00 research candidate 26099, four artifact hashes pinned, 48 synthetic/source checks pass; Rocko architecture review reconciled and Filbert exact-candidate review requested by agent-send rc 0. Runtime/Claude compatibility/security/access/cutover remain unverified. No publication or other queue start; waiting on reviewer reply.
+- 2026-09-13 UTC — darkwing — CHAT-00 independent APPROVED 26100, four hashes reverified; research-only publication 370823b3 remote verified and committed-copy 48/48. Closeout/proposed inactive CHAT-01 charter 26102; scoped WebUI tracking awaits owner authorization. Other dirty planning and logs preserved uncommitted; no runtime, credentials, live state or other queue work.
+- 2026-09-13 UTC — darkwing — CHAT-01 bounded contract drafting approved by Jason through control-board, active charter 26103; author Darkwing, Filbert independent review, Dewey UI semantics review. Draft artifacts/fixtures under docs/plans/chat-01; no runtime/live/security exception or #1503 acceptance inferred.
+- 2026-09-13 UTC — darkwing — CHAT-01 four-file draft candidate pinned in review request 26105; schema/reference checks pass in checkout and clean copy, CHAT-00 48/48. Filbert exact review, Dewey UI semantics, Rocko architecture requested through agent-send rc 0; no source runtime/live/security claims. WebUI tracking in review, other rows preserved.
+- 2026-09-13 UTC — rocko — #1507 CHAT-01 independent adversarial review (charter 26103): verified pinned four-file candidate hashes, read README/schema/fixtures/check.mjs, ran offline checker only (PASS). Sixteen draft-contract findings (recovery-control claim unreachable, revoked controller retained, interrupt fence has no exit, pending approval not re-projected on takeover, dispatch predicate shape, dedup digest includes connection, message/launch ingress absent, stop proof is world flag not record) sent to darkwing via agent-send rc 0. No candidate edits, new files, engines, or private state.
+
+- 2026-09-13 UTC — dewey — CHAT-01 pinned R1 UI semantics read-only review REQUEST CHANGES, #1507 comment 26108. Initial four hashes verified; checker passes reproduced as synthetic evidence only. Gaps: safe client bootstrap, stream/part reconstruction, approval intent/forms and composer lifecycle. No candidate edits; final hash check detected schema/fixtures changing, so verdict limited to initial R1 and Darkwing asked for fresh R2 pins.
 - 2026-09-13 UTC — coordinator (Claude) — Discord connector pilot planning: recovered Sage's private shared-signals records (setup receipts, direction memo, research packet), wrote brief docs/plans/2026-09-13_discord-connector-pilot.md, added QUEUE row 14 briefed/unassigned. No code, no listener, no Discord write, no credential read. Waiting on Jason for D1-D7.
+- 2026-09-13 UTC — darkwing — CHAT-01 R1 requested changes, consolidated 26107; R2 first draft correction checks 80/296/66 plus ten synthetic lifecycle sequences, CHAT-00 48/48. R2 WIP and not ready for review; README/UI/model reconciliation remains. Acknowledged edits starting before Dewey final hash read-back; no R1 approval inherited, no runtime/live/publication.
 - 2026-09-13 UTC — coordinator (Claude) — Discord connector pilot build (#1509, QUEUE row 14): wrote packages/discord (binding, authorize, gateway, rest, engine-pi, journal, context, connector, cli), scripts/discord.sh, scripts/test-discord.sh (28 checks, 74 node tests), agents/sage/DISCORD-USER.md draft, README, TOOLS.md section; brief section 10 records build choices. Existing suites green (config 24, auth 15, release 14, conductor 17, foundation 43, seat, ledger). Defects found and fixed before commit: two engine attribution bugs (offline tests), ceiling in-flight count (code-review subagent), and rev-code-02's four findings in #1509 comment 26114 (reconcile window refresh, context path escape, ceiling across a crash, pid claim and identity). Filbert deferred (26111). Review requested; no listener, no Discord write, no token read, no push.
+- 2026-09-13 UTC — darkwing — autonomous CHAT-01 R2 corrections carried through clean-copy verification and exact review request 26117; 89/316/70/10 plus queue/bootstrap/multipart regressions, CHAT-00 48/48. Filbert/Dewey/Rocko dispatched rc 0, Rocko acknowledged; four files frozen for peer verdicts. No owner action needed now, no runtime or other queue start.
+
+- 2026-09-13 UTC — dewey — CHAT-01 frozen R2 UI re-review REQUEST CHANGES for new-message role metadata, issue #1507 comment 26120. Four hashes match before/after; synthetic checker 89/316/70/10 plus regressions rerun. Prior UI gaps corrected/dispositioned; CHAT-01C/03D/03I accepted as explicit blockers, not scope exclusions. No candidate edits or runtime effects.
+- 2026-09-13 UTC — darkwing — read back/reproduced R2 findings 26119/26120, acknowledged Filbert/Dewey via agent-send rc 0. Cursor binding, durable scheduler after browser disconnect and NEW-message role fixes accepted; candidate remains frozen for Rocko verdict. No runtime or publication.
+- 2026-09-13 UTC — rocko — #1507 CHAT-01 R2 adversarial re-review (charter 26103, request 26117): four pins verified equal in checkout and frozen snapshot, offline checker PASS 89/316/70/10, 16 probe sequences run against a scratchpad copy of the model. Verdict REQUEST CHANGES bounded: R1 F1-F4/F7/F9/F11 confirmed corrected; new blocking N1 (corrupt payload blocks all control transfer) and N2 (revocation fence has no non-destructive exit), N3 dispatch-refusal disposition, ten non-blocking items; CHAT-01C/03I/03D companion dispositions accepted. Sent to darkwing via agent-send rc 0. No candidate edits, new repo files, engines, or private state.
 - 2026-09-13 UTC — coordinator (Claude) — Discord connector pilot review round two (#1509, QUEUE row 14): rev-code-02 comment 26121 kept the pid claim open (publication window) and found a memory-only ceiling notice and a duplicate admission across the thread lookup. Fixed all three: `run.lock` directory ownership with a four-process race test, `notices.jsonl` with a same-day restart test, id reservation with a held-lookup test. `scripts/test-discord.sh` 28/28 (80 node tests). Round three posted; files frozen for review. No listener, no Discord write, no token read, no push.
+- 2026-09-13 UTC — darkwing — CHAT-01 R3 consolidated corrections after all R2 reviews; 98/322/76/17 plus regressions pass in checkout and frozen clean copy, CHAT-00 48/48. Exact closure review 26124 read-back verified; Filbert/Dewey/Rocko dispatched rc 0. Four files frozen, peer replies own wake; no runtime/publication/other queue work.
+- 2026-09-13 UTC — rocko — #1507 CHAT-01 R3 closure review (charter 26103, request 26124): four pins verified equal in checkout and frozen snapshot, checker PASS 98/322/76/17, CHAT-00 48/48, R2->R3 diff read, R2 probes re-run plus nine composed sequences, 150 runtime-produced records schema-valid. Verdict APPROVE AS BOUNDED DRAFT on the exact R3 hashes for recovery/scheduler/composition scope; N1-N4/N6/N8/N10/N12 verified closed, N5/N7/N9/N11/N13 explicit limits; three tracked follow-ups (dispatched-unconsumed disposition to CHAT-02, dispatch-refused readback to CHAT-01C, observer-revocation fixture). Sent to darkwing via agent-send rc 0. No candidate edits, new repo files, engines, or private state.
+
+- 2026-09-13 UTC — dewey — CHAT-01 frozen R3 UI closure APPROVE AS BOUNDED DRAFT, #1507 comment 26127, exact four hashes in 26124 matched snapshot. UI2-R2 role attribution closed; checker 98/322/76/17 plus regressions and independent role refusal probes pass. Companion/all-seat gates retained; no candidate/runtime edits.
 - 2026-09-13 UTC — coordinator (Claude) — Discord connector pilot review round three (#1509, QUEUE row 14): rev-code-02 comment 26123 reproduced a three-party stale-reclaim race. Removed automatic reclaim; `run` fails closed on a stale lock and a new `unlock` command clears a verified-dead owner. Stale handoff and changed-under-unlock tests added. `scripts/test-discord.sh` 28/28 (82 node tests). Round four posted; files frozen. No listener, no Discord write, no token read, no push.
+- 2026-09-13 UTC — darkwing — CHAT-01 four-file bounded draft independently approved by Filbert/Dewey/Rocko and published 28d4e98a; remote/hash/committed-copy verification green 98/322/76/17 plus regressions, CHAT-00 48/48. Receipt 26131, follow-ups 26128. Next CHAT-01C charter proposed only; #1507/runtime/live gates remain open. Other dirty files excluded.
 - 2026-09-13 UTC — coordinator (Claude) — Discord connector pilot review round four (#1509, QUEUE row 14): rev-code-02 comment 26132 showed unlock's restore path can still leave two owners. Replaced it with a `STOP` quiescence gate: unlock writes `STOP` first, claims re-check `STOP` after publishing and release themselves. Four-party schedule test added. `scripts/test-discord.sh` 28/28 (82 node tests). Round five posted; files frozen. No listener, no Discord write, no token read, no push.
+- 2026-09-13 UTC — darkwing — Jason approved CHAT-01C with performing-agent attribution correction. Verified CHAT-01 commit author/committer Jason and API login jason.woltje; halted further issue mutations under that identity, no history/config/credential changes. Local CHAT-01C charter README authored; private readback/recovery contracts next. Agent-authenticated API route remains needed for issue recording.
+
+2026-09-13 | sage | isolated operator-authorized workspace work | author verification complete; independent review pending; no framework implementation changed.
+- 2026-09-13 UTC — darkwing — CHAT-01C authored and verified through exact R1 review 26137, posted/read-back as darkwing using seat credentials. Nine closed examples/106 omissions-extra plus private readback/range/preview/recovery state cases and baseline regressions green in checkout/clean copy. Filbert/Dewey dispatched rc 0; candidate frozen, no owner input needed. No runtime/live/publication yet.
+
+- 2026-09-13 UTC — dewey — CHAT-01C R1 read-only UI review REQUEST CHANGES delivered to Darkwing via agent-send (application acceptance unknown), request #1507/26137. Exact snapshot /tmp/chat-01c-r1-frozen-yvsfowd1 matches checkout. C-UI1 missing immutable queue content/target/request correlation for restart/edit; C-UI2 stale stop/consumed confirmation remains confirmed through snapshot; C-UI3 receiving upload lacks authoritative append offset/restart flow. Independent probes /tmp/dewey-chat01c-ui-probes.mjs reproduce; 9/106 and baseline 98/322/76/17 plus 48 checks pass, synthetic only. No candidate/runtime edits; no Jason-default issue credentials used.
+- 2026-09-13 UTC — darkwing — CHAT-01C R2 corrections after full Filbert/Dewey findings; eleven examples/187 omission-extra cases plus models and baselines green, independent clean copy verified. Exact closure request 26149 posted as darkwing; Filbert/Dewey dispatched rc 0, candidate frozen. Attributed R1 receipt routed to orch-01 as requested. No runtime/publication.
+
+- 2026-09-13 UTC — dewey — CHAT-01C R2 UI closure APPROVE AS BOUNDED DRAFT sent to Darkwing for #1507/26149, exact four pins in agent-send receipt; snapshot /tmp/chat-01c-r2-frozen-lujze3oe byte-matches checkout. C-UI1/2/3 closed; frozen checker 11/187 plus cases and independent /tmp/dewey-chat01c-r2-closure.mjs probes pass. No candidate/runtime edits or Jason-default issue actions; all later acceptance gates retained.
 - 2026-09-13 UTC — coordinator (Claude) — Discord connector pilot review round five (#1509, QUEUE row 14): rev-code-02 comment 26150 accepted the `STOP` gate and found the owner record lacked a boot identity plus a false promise in the unlock text. Owner record now {pid, start, boot}, three-way identity check, unreadable identity refuses everything, unlock text says use `stop`. `scripts/test-discord.sh` 28/28 (83 node tests). Round six posted; files frozen. No listener, no Discord write, no token read, no push.
+- 2026-09-13 UTC — darkwing — CHAT-01C R2 both reviewers approved, receipts 26152; local b023841c agent-authored/committed and committed-copy verified. Seat-authenticated push refused, remote unchanged, API push:false confirmed. Blocker 26154; orch-01 access/publisher-role resolution requested rc 0, no Jason fallback. No runtime action.
 - 2026-09-13 UTC — coordinator (Claude) — Discord connector pilot review round six (#1509, QUEUE row 14): rev-code-02 comment 26158 found that a live pid with a pre-boot-id record was treated as a mismatch, so `unlock` cleared a lock under a running connector, and that an unparseable owner record read as absent. Both now refuse everything until the pid is dead; unreadable records are never removed. Legacy-upgrade test with a live child plus an invalid-record control. `scripts/test-discord.sh` 28/28 (85 node tests). Round seven posted; files frozen. No listener, no Discord write, no token read, no push.
 - 2026-09-13 UTC — coordinator (Claude) — Discord connector pilot review round seven (#1509, QUEUE row 14): rev-code-02 comment 26165 found that malformed start or boot strings in a parseable record read as a positive mismatch. Identity values now have a checked syntax; a malformed value under a live pid is "unknown" and refuses everything. Six live-child controls plus a syntax table. `scripts/test-discord.sh` 28/28 (87 node tests). Round eight posted; files frozen. No listener, no Discord write, no token read, no push.
 - 2026-09-13 UTC — coordinator (Claude) — Discord connector pilot review round eight (#1509, QUEUE row 14): rev-code-02 comment 26168 found leading-zero and above-2^64 start strings still compared as a mismatch. Start ticks now require the canonical unsigned decimal form /proc prints. Boundary table entries and three more live-child controls. `scripts/test-discord.sh` 28/28 (87 node tests). Round nine posted; files frozen. No listener, no Discord write, no token read, no push.
@@ -250,10 +288,96 @@ are never rewritten or removed; corrections are new entries.
 - 2026-09-13 UTC — coordinator (Claude) — Discord connector pilot steps 2-8 (#1509, QUEUE row 14): Jason drove the messages; nine turns answered, kill and restart without duplicate, second account dropped silently, token request refused in text, ceiling line posted once and turn refused, answered again after restore. Receipts private. Gate H awaits Jason's ruling. No push.
 - 2026-09-13 UTC — coordinator (Claude) — Discord connector pilot closed (#1509, QUEUE row 14): Jason ruled Gate H passed, replies read as Sage. DISCORD-USER.md wording corrected (unlisted senders are dropped silently, not refused with a reply). Records committed and pushed on Jason's authorization; connector left running for MVP iteration.
 - 2026-09-13 UTC — coordinator (Claude) — Discord read receipt (#1509, QUEUE row 15): eyes reaction on every admitted message at admission, best effort, outcome in the turn record; REST `react` plus connector and REST tests. `scripts/test-discord.sh` 28/28 (90 node tests). Committed; connector restarted to pick it up. Push on Jason's say-so.
+- 2026-09-13 UTC — darkwing — owner repo access verified push:true; scoped publication still refused by Git receive-pack HTTP 403, remote unchanged. Read-only diagnosis sent to orch-01 for token/smart-HTTP authorization. No fallback identity or blind retries.
 - 2026-09-13 UTC — coordinator (Claude) — Discord read receipt live check (#1509, QUEUE row 15): reaction confirmed on a live message at 19:21 UTC, turn record receipt ok true, private evidence receipt written, row 15 done. Committed; push on Jason's say-so.
+- 2026-09-13 UTC | darkwing | #1510 repo-native team bootstrap under owner authorization | Researcher native source added; six isolated launcher tests, 24 config checks and five real no-effect startup checks passed. Exact R1 26201 sent to internal Filbert, review pending. No live engines, fleet migration or ~/.mosaic writes; unrelated work 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 UTC — coordinator (Claude) — Discord service unit (#1509, QUEUE row 17): `run --supervised` and `recover`, exit 3 for brakes, `scripts/discord-service.sh`, systemd user unit; suite 40/40 (95 node tests); Sage seat migrated from tmux to `mosaic-discord@shared-signals`, kill and brake checks passed live. Committed; push on Jason's say-so.
 - 2026-09-13 UTC — coordinator (Claude) — Discord binding reload and per-user channels (#1509, QUEUE rows 19–20): `reload`/SIGHUP with fixed keys refused, `reloads.jsonl`, user `channels` allowlist; suite 41/41, 101 node tests; Carmen enrolled live by reload at 00:03 UTC, her first message pending; row 18 assigned to darkwing by Jason.
+
+2026-09-13: Darkwing #1510 owner-authorized live smoke. Researcher started natively and returned RESEARCHER_NATIVE_SMOKE_OK, recorded session entry/hash in agents/darkwing/work/internal-development-bootstrap/live-smoke.json, authenticated issue receipt 26216. Rocko duplicate startup refused: existing native Claude PID 3707667 has repo cwd, native context and Sonnet, on mosaic-fleet socket. No new Rocko model test, no existing process restart/migration, no home launcher/provisioning edits. Only newly created dead default-socket test pane removed. Source approval remains 26204; no full MVP acceptance or publication claimed.
+
+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-14T00:12:52.493853+00:00 | Darkwing | #1503 attention R1 source approved by internal Filbert, verdict and nine pins persisted/read back in 26248. Reviewer independently passed 193 tests in each copy across board/seat/mosaic/WebUI; author 144 included ledger instead of mosaic. Five-package union now 213/213. No source drift. Next boundary is controlled replacement of listening backend PID 1265952 on 127.0.0.1:7331, awaiting owner authorization; existing agents remain untouched. No runtime fix or operator acceptance claimed yet.
+
+2026-09-14T00:21:09.242655+00:00 | Darkwing | #1503 owner-approved backend-only restart | Old PID 1265952 exited gracefully; replacement 3204655 healthy on 127.0.0.1:7331 with unchanged command/config. Live API now returns Researcher idle, waitingOnYou:false at original screenshot timestamp. Five agent PID/start identities unchanged. Evidence restart.json and restart-verification.json under agents/darkwing/work/board-attention; authenticated receipt 26249. Operator visual retest pending; no broader MVP acceptance, home launcher changes or publication.
+
+2026-09-14T00:31:46.602431+00:00 | Darkwing | #1503 targeted attention correction | Jason: "idle is confirmed". Operator visual acceptance recorded for Researcher completed-response idle status after live receipt 26249. Broader MVP/cross-harness acceptance and publication not inferred.
+
+2026-09-14T00:42:07.429237+00:00 | Darkwing | #1503 targeted status lifecycle operator accepted | Jason confirmed all five steps: explicit Input needed request sent, waiting/attention shown, Seen hides attention while waiting remains, TEST_COMPLETE reply requested, idle restored. Complements earlier ordinary-completion idle acceptance. No broader MVP/cross-harness acceptance or publication inferred.
+
+2026-09-14T00:52:54.277747+00:00 | Darkwing | #1509 row 18 actual start and continuation correction | Jason requires automatic continuation after accepted iterations. Prior assistant said it was continuing but ended without action; that was a violation, now acknowledged. Queue/current reconciled. Filbert acknowledged sole implementation ownership of scoped board/WebUI source; Darkwing independently reviews and Dewey acknowledged read-only UX review. Charter docs/plans/2026-09-14_discord-board-row.md. Independent baseline returned 200 and called fake transport once for a connector with forged native registration; no real send. Acceptance checklist and reply-baseline.json under agents/darkwing/work/discord-board. Kickoff entry recorded after dispatch/baseline, not claimed as before author work. Await exact candidate/tests by existing agent-send return route; no timeout armed. No unrelated queue start, source overlap, live connector/home change or publication.
+
+2026-09-14T00:59:49.989111+00:00 | Darkwing | #1509 row 18 author checkpoint received | Filbert reports connector discovery/identity/brake/refusal/dynamic discovery and minimal rendering implemented; six-package working suite 320/320 including Chromium fixture, prior attention fixtures preserved. Author-reported only; exact frozen candidate and second run pending. Acknowledged via default-socket agent-send rc 0. Next gate is immutable handoff for Darkwing backend and Dewey UX independent review. No source approval, live change or completion inferred.
+
+- 2026-09-14 UTC — dewey — #1509 row18 R1 scoped UX APPROVE sent to Darkwing/Filbert; nine-file manifest 5c92acc90d202727d790f3fb8d74387db1c9e5c3e43d4f4b56b40e5ae503a56a verified in /tmp/discord-board-r1-KbMrGQWF. Independently reran frozen discord/browser/browser-edge Chromium tests 3/3 PASS, 330 contrast samples. Identity, brake/liveness separation, absent connector Reply and ordinary controls accepted; test-claim limits communicated. No source/live edits, screenshot visual review or live observation. Backend review and operator gates remain.
+
+2026-09-14T01:12:24.257643+00:00 | Darkwing | #1509 row18 R1 independent review | Frozen nine/inherited pins verified; 320 serialized tests independently passed. Dewey approved scoped UX with three Chromium tests and retained limitations. Backend CHANGES REQUIRED R1-B1: uid1000 temporary journal containing STOP, mode000, produces braked:false instead of unknown. Evidence r1-backend-review.json. Author handoff and both verdicts read-back persisted as Darkwing in 26255. Filbert acknowledged bounded R2 correction; next wake exact candidate via agent-send. Two author concurrent frozen timeouts remain unresolved/not green. No source approval, live services/home edits or publication.
+
+- 2026-09-14 UTC — dewey — #1509 row18 R2 exact-pin UX APPROVE sent to Darkwing; manifest ea643060fa8b6af0d182c01c0dc20ba04e4bd02ec099e42c50ccb0392dff6d11/all nine hashes verified, seven paths including both UIs unchanged from R1. Frozen non-root STOP regression/control-board Discord and Chromium integration 7/7 PASS. Prior UX evidence limits retained; no source/live edits.
+
+2026-09-14T01:20:54.024167+00:00 | Darkwing | #1509 row18 R2 review | Nine working/frozen pins, two-file delta and inherited assets independently verified; serialized union 321/321. R1-B1 closed. Dewey exact R2 scoped UX approved with seven targeted tests and prior limits. Newly found R2-B2: canonical synthetic Discord routing envelope author/message IDs become public Task metadata; reproduction r2-envelope-review.json. Missed in R1 review, recorded honestly. Filbert acknowledged bounded fixed-task correction and regression, R3 pending via agent-send. Attributed author/reviewer receipts read back as Darkwing in 26256. No source approval, live observation/restart or publication. Concurrent R1 timeouts remain unresolved/not green.
+
+- 2026-09-14 UTC — dewey — #1509 row18 R3 exact-pin UX APPROVE sent to Darkwing; manifest 254403b89c0a2330da53e8dbad1cbeba3b1b06cf4f3efddc18451e04cb78f6de/all nine hashes verified. Only README/scanner/Discord test differ from R2; fixed connector Task accepted, both UIs unchanged. Independent frozen targeted suites 8/8 PASS. Prior evidence/live limits retained; no source/live edits.
+
+2026-09-14T01:30:57.305468+00:00 | Darkwing | #1509 row18 exact R3 source approvals and read-only live check | Darkwing verified nine working/frozen pins, inherited assets, three-file delta and 322/322 serialized tests; Dewey approved exact R3 with eight targeted tests and retained evidence limits. Both review findings closed. Author and both approvals read-back persisted as Darkwing in 26257. Authorized read-only actual shared-signals observation finds alive/idle, not braked, canonical owner matching systemd MainPID, safe fixed Task and no registration; r3-live-observation.json. Next gate is owner-approved backend-only restart then visual test; no connector/STOP/binding/home changes, backend restart or publication. Concurrent R1 timeouts remain unresolved/not green, now in DEFERRED.
+
+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-14T13:09:35.891133+00:00 | Darkwing | queue collision acknowledgment route | agent-send to default socket =unverified failed rc 1, invalid resolved pane identity. Correction is verified; delivery is not claimed. Actual coordinator socket/session required for a routed acknowledgment. Row18 backend approval gate unchanged.
+
+2026-09-14T13:52:23.718141+00:00 | Darkwing | #1509 row18 owner-approved backend replacement | Verified exact R3 working pins; old backend PID3204655 exited gracefully, replacement3769124 healthy on 7331. Live shared-signals row idle/live/not braked, fixed safe Task, actual reply POST refused409 with explicit connector error. Five agent pane PID/start identities and connector systemd PID/start identity unchanged. Evidence backend-restart.jsonl and backend-live-verification.json under agents/darkwing/work/discord-board. No connector/STOP/binding/home changes. Await operator visual confirmation, then continue to next ready authorized item without routine prompt.
+
+2026-09-14T14:07:30.352051+00:00 | Darkwing | Row18 accepted; row6 code phase started | Jason answered parfait to the live Discord-row visual test. Bounded local delivery accepted; no publication or live brake/offline transition claimed. Following the newer standing automatic-continuation mandate, starting next already-briefed row6 under existing Piece5 plan, preserving row6-before-#1508 ordering and no home/fleet changes. #1511 created/read back as Darkwing; charter docs/plans/2026-09-14_task-attribution.md. Rocko native repo context/lock independently verified for source authoring; Filbert backend review, Dewey UX review. This code phase precedes Filbert's specified stale-relaunch assignment; GateF not yet claimed or backdated. Kickoff recorded before author dispatch.
+
+2026-09-14T14:09:36.358711+00:00 | Darkwing | #1511 actual continuation checkpoint | Rocko acknowledged sole native source ownership; Filbert and Dewey acknowledged independent review lanes. Missing --by reproduced through isolated CLI refusal, exit4, no live config/registration accessed; evidence agents/darkwing/work/task-attribution/baseline.json. Queue/current now point to row6 code phase; row18 operator acceptance recorded. Await exact author handoff through agent-send, no timeout armed. Source reviews precede any integration; no live or publication authority inferred.
+- 2026-09-14 rocko (Claude Code, native agents/rocko) — #1511 row 6 code phase, taskSetBy attribution: seat CLI --by > MOSAIC_AGENT_NAME > unknown, optional bounded registration field (version 1 unchanged), scanner row taskSetBy tied to taskSource=registration, both board presentations; 15 files frozen (snapshot /tmp/task-attribution-r1-frozen-sRoqqr5m) and handed to darkwing for Filbert/Dewey review. Suites: seat 19/19, control-board 115/115, webui 7/7, rocko/darkwing launch suites rc0. Isolated fixtures only; no seat record, launcher, connector, tracking, commit, push or private state touched.
+
+- 2026-09-14 UTC — dewey — #1511 R1 UX REQUEST CHANGES sent to Darkwing on 15-file manifest 0185cc65c973f6d89c394e2e9fba67fccd794b8ad2be2720a8bb3700b2b018a3. WebUI inspector conflates null/inapplicable setter with legacy registered unknown; preserve scanner distinction and add browser coverage. Frozen/working pins verified before/after; matching working-tree Chromium suites 3/3 and 330 contrast samples pass. No source/live edits; test dependency and visual limits reported.
+- 2026-09-14 rocko (Claude Code, native agents/rocko) — #1511 row 6 R2: bounded correction of Dewey R1-U1 (WebUI inspector shows null attribution as not applicable, legacy registration keeps unknown; browser/edge/Discord assertions added) and Filbert's nonblocking seat.mjs comment fix; 5 files changed, 10 pins inherited from R1; frozen /tmp/task-attribution-r2-frozen-3PqORMJP, R1 snapshot preserved. Suites: seat 19/19, control-board 115/115, webui 7/7, launch suites rc0. No commits, push, tracking, live or seat-record changes.
+
+2026-09-14T14:25:14.147717+00:00 | Darkwing | #1511 R1 review gate | All 15 author pins matched frozen/working files; manifest 0185cc65c973f6d89c394e2e9fba67fccd794b8ad2be2720a8bb3700b2b018a3. Filbert source-backend approval, Dewey REQUEST CHANGES R1-U1 null/unknown inspector conflation. Both lanes collected before author correction dispatch. Rocko assigned bounded R2 UI/test fix plus inaccurate privacy-syntax prose correction. Reviews persisted agents/darkwing/work/task-attribution/r1-review.md; independent overlay141 and launcher6 logs read back green. Darkwing added only missing --by flag to TOOLS usage, exact owned patch reverse-checked and sent for Filbert review. Queue/current updated; no combined approval, live change, GateF or publication.
+
+- 2026-09-14 UTC — dewey — #1511 R2 scoped UX APPROVE sent to Darkwing; 15-file manifest d4c963952b3f2b0e1c99133b3fe3fefa4c1883b79a009dc1f8d20ef58b46ca16 verified against frozen/working bytes and after tests. R1-U1 null-versus-unknown distinction closed with transition/Discord browser assertions; matching working-tree Chromium 3/3 and 330 contrast samples pass. No source/live edits; dependency and visual evidence limits retained.
+
+2026-09-14T14:31:54.546546+00:00 | Darkwing | #1511 R2 source approved, protected test pending | Filbert and Dewey exact source approvals persisted in agents/darkwing/work/task-attribution/r2-review.md, R1-U1/comment findings closed; TOOLS owned patch approved separately. Darkwing combined serialized344/344 exit0; all15 working pins reverified afterward. Old-reader rejection of new field reproduced synthetically; no live records touched. Proposed backend-only restart and one Rocko task-metadata visual test awaits Jason, envelope agents/darkwing/work/task-attribution/live-test-envelope.md. No publication, GateF, Filbert behavior assignment or live acceptance claimed.
+
+2026-09-15T00:14:24.283987+00:00 | Darkwing | #1511 authorized backend update; target mismatch blocks test write | Old3769124 gracefully exited, new3414098 healthy, reviewed page byte-identical; API new attribution fields verified. Five agent pane identities, connector identity and every registration byte unchanged. Rocko target mismatch found before mutation: dead registered185602 versus native3707667, missing discovery directory and no row; existing DEFERRED Claude gap updated. No identity repair/relaunch or attribution write. Verified Filbert registration matches its native profile lock/cwd/tmux; requesting only test-target substitution. Receipts agents/darkwing/work/task-attribution/backend-restart.jsonl and backend-live-verification.json. No publication, operator acceptance or GateF claimed.
+
+2026-09-15T00:37:06.191367+00:00 | Darkwing | #1511 Filbert live attribution ready for visual test | Jason authorized target substitution and confirmed Claude console integration remains separate. Native Filbert record/lock/cwd/tmux matched; original record backed up privately outside repo. Reviewed CLI set only authorized task metadata; live API taskSource registration and taskSetBy darkwing verified. Other registration bytes and agent/connector/backend identities unchanged. No Rocko change. Receipt agents/darkwing/work/task-attribution/live-test.jsonl. Await operator visual confirmation; no publication, GateF or behavior assignment claimed.
+
+2026-09-15T00:45:55.295300+00:00 | Darkwing | #1511 operator confirmed; #1512 kickoff | Screenshot and pasted inspector confirm set by darkwing with caller-claim wording. Bounded attribution delivery accepted, publication remains separate. Next prescribed Piece5 Filbert assignment chartered in docs/plans/2026-09-15_relaunch-activity.md; #1512 created/read back as authenticated Darkwing. Filbert source author, Darkwing backend review, Dewey UX review. No GateF claim.
+
+2026-09-15T00:47:20.173732+00:00 | Darkwing | #1512 actual continuation verified | Filbert source ownership and Dewey UX review acknowledged. Independent isolated newer-launch/old-reply baseline reproduced, agents/darkwing/work/relaunch-activity/baseline.json. Accepted bounded presentation-only notice rule: positive row and PID liveness, valid strictly newer launch; retain history/state/Seen/attribution/reply semantics. Await exact frozen candidate via agent-send. #1511 table and inspector confirmation persisted in live-test.jsonl; publication and GateF remain separate.
+
+2026-09-15T00:50:52.971177+00:00 | Darkwing | Team availability steering | Jason reports Rocko is available again after exhausting usage; the usage notice was not seen. Availability is owner-reported, not a runtime/quota probe. Recorded missed notice as unverified DEFERRED follow-up for Claude console integration. #1512 ownership unchanged: Filbert authors, Darkwing backend review, Dewey UX review. No reassignment, restart or new source scope.
+
 - 2026-09-14 UTC — coordinator (Claude) — Discord read-only tools (#1509, QUEUE row 21): `tools` binding key, host pi extension `list_dir`/`read_file`/`search` confined to declared roots, engine settles on `agent_end`, tool calls in the turn record; rev-code-02 round 2 APPROVE (26276) after four round 1 findings were fixed; suite 48/48, 116 node tests; committed locally, not pushed; live check in #sage-admin next.
+
+- 2026-09-15 UTC — dewey — #1512 R1 scoped UX APPROVE sent to Darkwing/Filbert on seven-file manifest 47769fada74c5684dd0ca32c41cea9dcf60e039f5a07657546e17a240af13e9d; frozen candidate/inherited hashes verified. Targeted frozen tests 8/8 PASS including both-page relaunch transition at 320px and ordinary/edge/Discord regressions, 330 contrast samples. Historical-error source-only and screenshot/live/Gate F limits communicated; no source/live edits.
+
+2026-09-15T01:02:43.256672+00:00 | Darkwing | #1512 R1 source review and test hold | Exact seven-file manifest47769fada74c5684dd0ca32c41cea9dcf60e039f5a07657546e17a240af13e9d verified before/after. Darkwing backend and Dewey scoped UX approve source, Dewey8 targeted tests. First frozen full serialized run failed inherited Discord tool-turn case then timed out120s; diagnostic single case passed with force-exit, not acceptance. Later full TAP with15s test deadline and no force-exit passes351/351. Earlier failure unresolved; integration held, Rocko dispatched read-only inherited engine/fixture diagnosis. Scope/logs in agents/darkwing/work/relaunch-activity/r1-review.md. No source edits, live changes, publication or GateF claim.
+- 2026-09-15 rocko (Claude Code, native agents/rocko) — #1512 read-only diagnosis of inherited Discord engine failure: reproduced deterministically (relay delaying agent_settled) and naturally under CPU contention; engine.test.mjs asserts busy between agent_end and agent_settled, and success-only engine.stop() leaks fake pi and hangs the file. Inherited from HEAD~1, independent of Filbert's candidate. Also found a row-21 engine followUp race after client timeout (coordinator-owned, reported only). Scratch fixtures only, no source/test/live edits; report sent to darkwing. Told orch-01 its row 21 R1 findings were already closed (26276, 1ac812d3).
+
+2026-09-15T01:15:49.697152+00:00 | Darkwing | #1512 diagnosis confirmed, provenance corrected | Rocko reported test busy/settled race plus success-only cleanup hang, timeout-log test race, and separate engine followUp-after-timeout concern. Darkwing independently reproduced controlled50ms event split failure with finally cleanup, exit1/148ms, no stress load; read refused-streaming fixture evidence. Row21 owner orch-01 notified through verified named socket; source ownership untouched. Filbert supplied append-only provenance correction: actual archive content1ac812d3, not stale HANDOFFc4fc label. Correction hash and89 dependency pins independently verified and copied outside R1; seven source pins unchanged. Provenance hold resolved, integration awaits owner engine/test disposition. Records agents/darkwing/work/relaunch-activity/engine-diagnosis.md and r1-provenance-correction.json. No live incident/change, publication, operator acceptance or GateF claim.
+
+2026-09-15 | Sage | OpenProject prefreeze coordination, no Mosaic queue work | Reconciled author/reviewer arithmetic and backup gaps; requested generated evidence and orch oversight; no deployment; private checkpoint PREFREEZE-DISPOSITION-2.json.
+
+2026-09-16 | Sage | Owner-approved OpenProject test deployment coordination | Recorded Jason yes against reviewed bundle; activated assigned author/orchestrator/reviewer by agent-send; review/CI/GitOps/runtime gates retained; no live changes by Sage.
+2026-09-17T02:04:23.049189+00:00 | Sage | Assigned private Shared Signals naming research, no Mosaic queue work | Saved 50 evaluated names and dated source evidence in local commit b668ac1813dbaa4f7448b466a6c2ccb5ec17c6a7. Prospective tree validates 44 records; candidate/source audit passed. GitHub publication blocked by authentication. Concurrent unstructured naming note preserved, broader worktree validation not green. No purchases, outreach, UI or OpenProject execution.
 2026-09-17T02:05:47Z | coordinator (Claude, #1509) | Row 23 Discord writes + web tools: built, round 3 pinned (comment 26361), SearXNG live on loopback, engine held-prompt defect fixed live; row 24 git verbs briefed with D5–D7 ruled | in review, uncommitted, no push
 2026-09-18T12:46:17Z | coordinator (Claude, #1509) | Row 23 pushed (90cb31f5..1685deb4); row 24 git verbs, package credential helper, vault protocol and requester envelope built, suite 58/58, node 143, review requested from rev-code-02 | in review, uncommitted, no push
 2026-09-21T00:20:45Z | coordinator (Claude, #1509) | Row 25 SetSpark client: part 2b built against shared-signals a5425a2 (eight model verbs, connector api client, button evidence by confirmation message per the coordinator), suite 63/63, node 162, review candidate frozen (aggregate 09140edc, tree 7872d8c5); Gitea 503 at post time, review request queued | in review, uncommitted, no push
+2026-09-26T19:30:22Z | Darkwing (Claude, T3 thread 7525c8e4) | ms-communications gains T3 threads as the temporary development channel beside tmux (Jason, 2026-09-26); docs/guides/T3-AGENT-COMMS.md adapted to this repository (status, thread lookup, reply rules, record locations); unslop-check clean on both | uncommitted, no push
+2026-09-26T19:30:35Z | Sage (lead, T3 Claude Code) | Alignment and lead handover | Jason made Sage the project lead and Darkwing a collaborating seat; the fleet Sage seat is being decommissioned. All seven suites green (config 24, task 90, foundation 43, conductor 17, release 14, auth 15, discord 63). Pushed 1685deb4..43d7574d to origin/refactor at Jason's word (jarvis identity). AGENTS.md, agents/README.md, agents/sage/CONTEXT.md and QUEUE rows 23-25 updated, uncommitted. Target for the next phase pending from Jason.
+2026-09-26T19:32:06Z | Filbert (T3 Claude Code, thread 9cb9731e) | Took over Pi session 01a0967c (last active 2026-09-15); recovered state, no work started | Row 6 #1512 R1 seven-file candidate source-approved (Darkwing, Dewey), integration held on inherited engine test disposition; provenance corrected to 1ac812d3. Reporting to Sage (thread 1ef1e4f8). No source edits.
+
+2026-09-26T19:36:21Z | Rocko (Codex, T3 takeover) | Prepared takeover of Claude Code session 0422f20f-4d8c-43fe-b429-a2730cc1ab9d under Sage, T3 thread 1ef1e4f8-3ead-4208-beca-38f9f1add079 | Recovered prior transcript, QUEUE/CURRENT, role context, git state and durable review/diagnosis. Prior session ended with no open assignment; #1511 R2 approved, #1512 read-only diagnosis delivered. Sage has assigned current #1512 rerun to Darkwing. Historical /tmp R2 and R1 snapshots and Rocko diagnostic scratch directory are absent; durable repository receipts remain. Shared changes preserved; no source edits, tests, live actions, commit or push. Ready for assignment.
+
+2026-09-26T19:39:19Z | Dewey (T3 Claude Code, thread 84fb346c) | Took over Pi session 01a0981a (last active 2026-09-15) under Sage; tree manifest, row 5 recovery, live WebUI check | Manifest at agents/dewey/work/tree-manifest-2026-09-26.md (uncommitted). b023841c confirmed on origin/refactor; row 5 and CURRENT text stale. WebUI PID 1266267 serves the working tree; 8/8 webui tests pass. Gate E blocked on Jason (seat scope, priority, charters). No source edits, commit or push. Reported to Sage (thread 1ef1e4f8).
+
+2026-09-26T19:47:57Z | Dewey (T3 Claude Code, thread 84fb346c) | Sage rulings 1-3: row 5 text, D-002 records and subset proposal, return-flow regression and relative Age | QUEUE row 5 State and one log line; CURRENT row-5 paragraph corrected; wui TASKS/README/DESIGN/DECISIONS/HISTORY reconciled to D-002; subset proposal in tree manifest section 6. Console candidate agents/dewey/work/return-flow-age (app.js 26be54e1, new return-flow test); webui 9/9; the fixture reproduces the misleading pending display only, and the live cause is still unproven. Sent to Filbert for review. Uncommitted; no push.
+- 2026-09-26T19:50:06Z | Darkwing (Claude, T3 thread 7525c8e4) | row 6: tree manifest for Sage review, #1512 R1 re-run against 21e3e908 (serial 397/397 x4; default concurrency 395/397 x2 from #1509 engine tests, also on clean HEAD) | reported to Sage over T3, uncommitted, no push
+
+2026-09-26T19:56:50Z | Dewey (T3 Claude Code, thread 84fb346c) | Return-flow and Age candidate R1->R2 | Filbert R1 revise (baseline statement, clear-once test); R2 approved source-only (app.js d1a51646, test a598c0d4, patch c640b601). Webui 9/9. Reported to Sage; integration after #1512 is Sage's. Disclosed two brief in-tree mutation edits to the live-served app.js, since restored. Uncommitted; no push.

docs/plans/2026-09-26_fleet-seats-onto-mosaic-launch.md

@@ -0,0 +1,41 @@
+# Row 8: fleet seats onto `mosaic launch` (stub brief)
+
+State: parked. Owner: unassigned. Issue: none yet. Written by Sage (lead) on
+2026-09-26 so the queue can carry the row under the mandatory-brief rule
+(#1508 J3, J9). This stub authorizes no work.
+
+## Why the row exists
+
+The old estate runs seats from `~/.mosaic/fleet/agents/<seat>/` under the
+npm-global `mosaic` CLI and the `mosaic-fleet` tmux socket. The new stack
+launches seats from `agents/<name>/launch.sh` in this checkout and registers
+them for the control board (row 2, #1504).
+
+On 2026-09-26 Jason said the work MUST move to the new stack, because a fleet
+seat (the fleet Sage) was acting outside his instructions. That makes the
+retirement a stated goal. It does not make this row active.
+
+## What is known
+
+- Development seats (Sage, Darkwing, Dewey, Filbert, Rocko) run in T3 for now.
+  T3 threads set no `MOSAIC_AGENT_NAME` and write no registration.
+- Fleet seats still live on the `mosaic-fleet` socket, including orch-01,
+  rev-code-01, rev-code-02, jarvis and joe.
+- The Discord Sage runs as `mosaic-discord@shared-signals`, a new-stack
+  service, and is not a fleet seat.
+- AGENTS.md forbids changes to `~/.mosaic` launchers, provisioning or live
+  fleet processes during the internal bootstrap.
+
+## Before this row can leave parked
+
+Jason must rule on:
+
+1. Which fleet seats move, which are retired and in what order.
+2. Whether a moved seat runs under a Pi launcher, T3 or both.
+3. How seat credentials move. Seat tokens live under
+   `~/.mosaic/fleet/agents/<seat>/secrets/`. Secrets never enter this
+   repository (canon invariant 3).
+4. Lifting the AGENTS.md bootstrap restriction on `~/.mosaic` changes.
+
+A full brief replaces this stub once he rules. Until then, `queue next`
+never returns this row.

docs/plans/CURRENT.md

@@ -12,6 +12,153 @@ update this file to the next action). No ambiguity, no re-planning.
 
 ## Next action
 
+Current owner priority: #1512, QUEUE row 6 prescribed Filbert relaunch-activity pilot.
+Filbert acknowledged sole source ownership; Darkwing reviews backend and Dewey
+acknowledged UX review. Charter: `2026-09-15_relaunch-activity.md`.
+Darkwing created/read back #1512 as authenticated Darkwing, set the owning native
+seat's task through Piece5 step3 with identity preserved, and independently
+reproduced old assistant text still presented after a newer live registration
+in an isolated fixture. Evidence: `agents/darkwing/work/relaunch-activity/baseline.json`.
+R1 arrived with seven pinned source files. Darkwing approved backend/source;
+Dewey approved scoped UX with eight frozen targeted tests. Darkwing's first full
+serialized run failed an inherited Discord engine tool-turn test then hung120s.
+A later full frozen TAP run with a15s test deadline passed351/351 without force-exit.
+Rocko diagnosed a test busy/settled-event race and success-only cleanup hang;
+Darkwing independently reproduced the busy assertion with a 50ms event split and
+finally cleanup. A separate timeout-log timing flaw and a potential engine
+followUp-after-timeout defect were also reported. The latter belongs to row21;
+no live incident is claimed. orch-01 was notified on its verified named socket.
+Evidence: `agents/darkwing/work/relaunch-activity/engine-diagnosis.md`.
+Darkwing verified 31 frozen Discord dependency files match commit1ac812d3.
+Filbert confirmed his archive used moving HEAD and the old HANDOFF label was wrong.
+He supplied an append-only correction outside R1; Darkwing verified its hash and
+all89 frozen dependency pins. Local copies are `r1-provenance-correction.json`
+and `r1-dependencies.sha256` under the relaunch-activity work directory.
+Provenance hold resolved; original R1 and all seven source pins remain unchanged.
+2026-09-26: 1685deb4 fixed the engine test race. A re-run of the frozen candidate
+against 21e3e908 passed the serial acceptance command 397/397 three times.
+Failures that only show when tests run concurrently are #1509 engine tests and
+reproduce on clean HEAD (`relaunch-activity/rerun-2026-09-26.md`). Sage ruled that
+#1512 integrates on the serial evidence. #1511 and #1512 are committed locally in
+af4203ca with rows 18 and 22, and not pushed. The engine defects are a DEFERRED
+entry against #1509. #1512 closes after Sage's records commit. The board restart
+that shows #1512 live and the Gate F live assignment both wait on Jason.
+Next for Darkwing: the #1506 ledger fix for T3 headers (Filbert reviews), then
+the #1509 engine test and `busy` fixes (Rocko reviews, source only).
+No live action, publication, operator acceptance or GateF claim.
+Standing owner mandate: after each accepted iteration, automatically execute the
+next ready authorized item, without a routine next-step prompt. Existing scope,
+review, access, acceptance and protected-operation gates still apply.
+
+Jason accepted row 18 with "parfait". The newer standing continuation instruction
+supplies the start for the next already-briefed row 6, replacing its historical
+Sunday start-message scheduling, without waiving dependencies or protected gates.
+Rocko's existing native repository context was verified and he acknowledged sole
+source ownership under `2026-09-14_task-attribution.md`. Filbert and Dewey both
+acknowledged independent review ownership. Darkwing reproduced the current CLI
+refusing --by with exit 4 using no live configuration or registration.
+Evidence: `agents/darkwing/work/task-attribution/baseline.json`.
+R1 arrived and all 15 working/frozen pins matched. Filbert approved backend source,
+reporting independent 141/141 working/overlay tests and six launcher checks.
+Dewey requested R1-U1: WebUI inspector conflates null/inapplicable attribution
+with legacy registered unknown. Both lanes returned before Rocko received the
+bounded R2 correction, including a misleading privacy-syntax comment correction.
+Review record: `agents/darkwing/work/task-attribution/r1-review.md`.
+Darkwing added only the missing --by usage flag to dirty `docs/TOOLS.md`, preserving
+other changes; that additive documentation also requires independent review.
+R2 has now passed both exact source review lanes. R1-U1 and the comment finding
+are closed; Filbert also approved the separate TOOLS usage patch. Darkwing ran
+344/344 broader serialized tests. Evidence and limits:
+`agents/darkwing/work/task-attribution/r2-review.md`.
+Old strict-v1 readers reject the new field, independently reproduced with synthetic
+records. No live setter write may precede the authorized reader update.
+Jason authorized that envelope with yes. On 2026-09-15, backend PID 3769124
+exited gracefully; replacement 3414098 is healthy and serves the exact reviewed
+board page. API exposes the new attribution field; two legacy registered rows
+show unknown and non-registration tasks have null attribution.
+The Rocko write was blocked before mutation: its registration names dead PID
+185602, actual native lock owner is 3707667, and its discovery directory is
+absent, so there is no Rocko board row. This existing Claude-board gap remains
+separate; no identity repair or discovery expansion was attempted.
+All registration bytes, five agent pane identities and connector identity stayed
+unchanged. Receipts: `agents/darkwing/work/task-attribution/backend-restart.jsonl`
+and `backend-live-verification.json`.
+Jason authorized Filbert instead and confirmed Claude console integration is
+not yet implemented. Filbert's native registration identity was reverified;
+the authorized task update passed live API verification at 2026-09-15T00:36Z:
+task '#1511 task attribution user test', source registration, setter darkwing.
+Only task/taskSetBy/updatedAt changed; identity fields and startedAt were preserved.
+All other registrations and agent/connector/backend identities stayed unchanged.
+Original registration is backed up privately outside the repository. Receipt:
+`agents/darkwing/work/task-attribution/live-test.jsonl`.
+Jason supplied the table screenshot and inspector text confirming darkwing with
+'as claimed by the caller, not verified'. Bounded local attribution delivery is
+operator-confirmed. Publication remains separate. The standing continuation mandate
+now advances the prescribed Filbert assignment above, after this local acceptance.
+Gate F is not claimed or backdated. #1508 still depends on row 6 completion.
+
+## Completed bounded row 18 delivery
+
+Actual start: Filbert acknowledged sole implementation ownership under
+`2026-09-14_discord-board-row.md`; Darkwing independently reviews backend/privacy
+and Dewey acknowledged read-only UX review. Darkwing prepared acceptance checks
+and reproduced the missing reply refusal with a synthetic connector plus forged
+registration: current handler returned 200 and called fake transport once, with
+zero real sends. Evidence: `agents/darkwing/work/discord-board/reply-baseline.json`.
+Exact R3 source approvals from Darkwing and Dewey are persisted in 26257.
+Nine working/frozen pins and three-file R2 delta independently verified; full
+serialized suite 322/322 passed, plus Dewey's eight targeted tests. R1-B1 and
+R2-B2 closed: inaccessible STOP is unknown and connector Task is fixed safe
+metadata, not a routing envelope. Prior attention/UI assets are preserved.
+Read-only live observation after approval found shared-signals alive/idle,
+not braked, owner matching systemd MainPID, fixed Task and no registration.
+Evidence: `agents/darkwing/work/discord-board/r3-live-observation.json`.
+Owner approved the backend-only restart. Old PID 3204655 exited gracefully;
+replacement PID 3769124 is healthy on 7331. Live API now shows the shared-signals
+connector idle/live/not braked with safe Task metadata; actual connector reply
+POST was refused with 409 before transport. All five agent pane identities and
+the connector service PID/start identity are unchanged. Evidence:
+`agents/darkwing/work/discord-board/backend-live-verification.json`.
+Jason accepted the operator visual test with "parfait". This bounded local row
+delivery is complete, without publication or live brake/offline transition claims.
+No connector service/binding/STOP/home changes. Concurrent R1 timeouts remain unresolved/not green and
+are recorded in DEFERRED.md; no general transcript redaction or broader runtime
+conformance claimed. Standing continuation has advanced to row 6 above. Filbert
+remains the row-18 source author; frozen R3 evidence remains unchanged.
+
+Prior accepted correction: #1503, QUEUE row 22, board attention status correction.
+Jason passed internal-team checks 1-4 and reported Researcher's false waiting
+status in step 5. He approved ordinary completion becoming idle and reserving
+waiting for explicit human-input requests. Filbert approved exact R1, receipt
+26248. Author 144 and reviewer 193 covered different package sets; the combined
+five-package author rerun passes 213 tests. Read-only actual Researcher scan
+returns idle and waitingOnYou:false. Owner approved backend-only restart, now
+completed and live-verified in receipt 26249: old PID 1265952 exited gracefully,
+replacement PID 3204655 is healthy on loopback 7331. Live API shows Researcher
+idle/not waiting at the original screenshot activity timestamp. All five agent
+process identities are unchanged. Jason confirmed both targeted tests: ordinary
+completion shows idle; an explicit input request shows waiting, Seen removes it
+from attention without resolving waiting, and the subsequent completion returns
+to idle. The full targeted status sequence is operator accepted. This is not
+broader MVP/cross-harness acceptance or publication; do not resume another queue
+item by inference. Brief: `2026-09-13_board-attention-status.md`.
+
+Prior bootstrap checkpoint: #1510, QUEUE row 16. Darkwing coordinates direct coding,
+review and research through the five repository-native agents. Keep source
+changes in `/mnt/storage/src/mosaic-stack`; no `~/.mosaic` launcher/provisioning
+changes and no live fleet stop or migration. Researcher's missing native entry
+and recovery files are added. Six isolated launcher tests and all five real
+`--check` runs pass without launching engines. Internal Filbert approved exact R1
+as source; attributed receipt 26204, independently rerunning six tests in both
+working and frozen copies. Source setup is approved. Owner-authorized live smoke passed for Researcher,
+which returned the exact expected model response, receipt 26216. Rocko startup
+correctly refused an existing native lock; its running repository-native Sonnet
+process is on the mosaic-fleet socket and was left intact, not retested with a
+model prompt. No existing sessions restarted, home launchers modified or broader
+MVP/user acceptance or publication claimed. Brief: `2026-09-13_internal-development-bootstrap.md`.
+The historical MVP queue and CHAT-01C publication gate below remain separate;
+this direction does not resume #1508 or authorize external provisioning.
+
 Gaps found and not fixed go to `docs/plans/DEFERRED.md`, one line each; check it at every gate.
 
 Jason decided on 2026-09-12 (MOSAIC-STACK-D-001) that the MVP is the control
@@ -74,12 +221,74 @@ Filbert APPROVED WEBUI-1507-R1, manifest 509f20e5; all 21 hashes reverified.
 Committed-tree regressions 208/208 include six WebUI tests, Chromium at
 320..2560px and 330 passing rendered contrast samples. Receipt:
 `reviews/2026-09-13_webui-publication.md`.
-Next action for this piece: Jason runs Gate E on Monday 2026-09-14. Start
-`node packages/webui/src/cli.mjs serve` with the existing board on 7331, then
-open http://127.0.0.1:7330/. Reply to a registered repo seat, check its answer,
-use Seen/Unsee, and record any need to return to the board page or terminal.
-Keep #1507 open pending Jason's end-of-day ruling. No deployment or user
-acceptance is inferred from tests; no timer or other queued work started.
+Jason's 2026-09-13 feedback supersedes readiness for the workday test: Gate E
+is blocked on refinement. He needs project/session navigation in the left
+sidebar and independent two-way chat interfaces, not dashboard cards and an
+inspector send box. He reports the return flow is missing in actual use; this
+needs reproduction. The current inspector's latest assistant text is not a
+conversation history. Restore relative activity age too; board `ageSeconds`
+is time since last activity, not session lifetime. Durable feedback and
+screenshot descriptions: #1507 comment 26082.
+Refined brief and decomposition: `2026-09-13_webui-session-chat.md`, CHAT-00..08.
+Jason settled Q1-Q22: all seats, full chat/tools/attachments/native approvals,
+enforced controller transfer, durable drafts/queue, interrupt/force-stop and
+explicit recovery. Old accepted foundation requirements were recovered rather
+than re-invented. Jason confirmed shared understanding and authorized bounded CHAT-00 preparation
+on 2026-09-13. CHAT-00 charter is #1507 comment 26094; research deliverable
+`chat-00/README.md` is independently APPROVED by Filbert in comment 26100.
+Four exact research files published at 370823b3, remote identity verified;
+48 synthetic/source checks also pass from the committed research copy.
+Jason approved CHAT-01 contract drafting; active bounded charter is comment
+26103. R1 request 26105 received REQUEST CHANGES in 26106/26107/26108.
+All R2 verdicts were collected before R3 edits. Filbert 26119, Dewey 26120
+and Rocko via agent-send requested changes and accepted the named companion
+gates. R3 fixes cursor binding, disconnected-browser scheduler authority and
+visible dispatch refusal, NEW message roles, corrupt-queue recovery without
+control deadlock, and non-destructive revocation reconciliation. It also tests
+current retry dispositions, superseded stops, native resolution evidence,
+stop-context confirmations and second-actor draft privacy.
+R3 exact review 26124 is APPROVED AS BOUNDED DRAFT by Filbert 26126,
+Dewey 26127 and Rocko via agent-send, recorded with follow-ups in 26128.
+Only the four reviewed files published at 28d4e98ad8b406ca84b30170558bee22402f1e55;
+remote ref verified, committed copy byte-identical to reviewed snapshot and
+checks green: 98 shapes, 322 omissions, 76 reference cases, 17 lifecycle
+sequences plus regressions; CHAT-00 48/48. Receipt 26131 read back. Shared
+dirty planning/logs and other owners' files were excluded from the commit.
+CHAT-01 bounded delivery is complete, not runtime/security/all-seat acceptance.
+Jason approved CHAT-01C proposal 26131 with performing-agent attribution.
+Darkwing authored the four `chat-01c/` contract/model files and froze R1 for
+review in 26137, posted and read back as actual Gitea darkwing, account 104.
+Seat credentials at the operator-specified location work; no minting needed.
+Never use the legacy helper's default Jason identity. Future Git commits use
+explicit performing-agent author/committer and seat-authenticated publication,
+without changing shared config or rewriting published history.
+R1 findings were corrected and both Filbert and Dewey APPROVED exact R2
+through agent-send; attributed receipts persisted as darkwing in 26152.
+Candidate request 26149, clean copy /tmp/chat-01c-r2-frozen-lujze3oe. Eleven
+closed examples/187 omission-extra cases and models/base regressions pass.
+Locally committed b023841c8a44d08677dc388043997eb4277b0545 with verified author
+AND committer Darkwing <darkwing@mosaicstack.dev>; only four reviewed files.
+Committed-copy checks pass. Published: Dewey confirmed on 2026-09-26 that
+b023841c is on origin/refactor (`git branch -r --contains`). The HTTP 403
+blocker (26154) is resolved. From 2026-09-26, pushes go through Sage with the
+jarvis identity, and each push needs Jason's word. CHAT-02..08 are not
+chartered. They are held until Jason rules, through Sage, on what "all seats"
+means with the fleet retiring, on row 5's priority against row 6 and #1508,
+and on charters and backend authors. Only small Console fixes are approved
+now (return-flow regression, relative Age; Filbert reviews). No runtime work
+or other queue item has started.
+CHAT-03I/03D, B1-B6/Q22 and #1507 acceptance remain open. Carry Rocko R3-1
+native dispatched-input reconciliation into CHAT-02, R3-2 into CHAT-01C and
+R3-3 observer-revocation coverage into a later fixture revision, per 26128.
+No peer reviews remain pending for CHAT-01. No other queue/runtime/live start.
+Rocko architecture findings are incorporated with accepted evidence corrections.
+Actual Claude protocol compatibility, tool isolation, access and cutover remain
+unverified; no runtime implementation or live cutover yet. Q20 cancels ordinary-Interrupt
+follow-ups into drafts; Q21 authorizes reviewed/green scoped refactor publication;
+Q22 preserves piece-5/#1508/fleet ordering. Dependent fleet work remains held. Darkwing/Filbert planning corrections are
+incorporated, including explicit remote implementation and publication gates. Live one-seat cutover requires separate
+Jason approval after both harness fixtures and exact rollback plan. Keep #1507
+open; original tests are not new-scope approval. No code or live effects started.
 Darkwing closed #1506 (Gate D written, comment 26067) and
 #1504 (registration shipped, Gate B passed, comment 26069) on 2026-09-13 UTC.
 Darkwing holds for piece 5 (darkwing on point; brief on the plan page, section "Piece 5") until Jason sends the start message, planned Sunday 2026-09-13. #1503 stays open until Jason rules on "who is waiting on me".
@@ -374,3 +583,5 @@ git history + Gitea issues.
 - 2026-09-16 (coordinator, #1509 row 23): part 3 live: SearXNG container `mosaic-searxng` (image searxng/searxng:latest, settings in the data root, formats html and json, limiter off) on 127.0.0.1:8888; binding `tools.web` added (backup in the sage evidence dir); check ok; service restarted. Jason's first turn in #sage-admin searched, fetched who.is, listed the folder and wrote `vault/Businesses/naming.md`. Defect seen in the same exchange: his second message during the turn went to pi as a follow-up, pi folded it into the same run, the first answer was never posted and the second failed as settled-without-turn. Fixed in `engine-pi.mjs` (held prompts, one run each), fake pi now models real follow-up semantics, suite 52/52 node 129, round 3 pinned (comment 26361, aggregate e30c2319, tree dbd2ce9a), service restarted with the fix. Row 24 rulings: D5 seat identity with `[email protected]`, D6 push every commit (Jason: not pushing means stale data), D7 rev-code-02.
 - 2026-09-18 (coordinator, #1509 rows 23–24): row 23 committed as 1685deb4 and pushed (`90cb31f5..1685deb4`) at Jason's word. Row 24 built: `src/git.mjs` (git_status, git_commit with explicit paths, seat author and `Requested-by:` trailer, push after every commit per D6, git_pull ff-only, git_push one branch; guard for branch, detached head, in-progress operations and conflicts; index must be empty so Jason's terminal work is never swept), `bin/git-credential.mjs` (the package's own helper: `get` over https from the 0600 token file, since `git-credential-mosaic` serves only the Gitea hosts and the global config routes github.com to Jason's `gh`), git children run with no host config; vault protocol (`protocol: "vault"`): per-write clone lock, `check` and `validate_vault.py` before a commit, `reserve_id`; the connector writes `requester="<server name>"` into the envelope and the extension reads it on `before_agent_start`. Suite 58/58, node 143. Review requested from rev-code-02; binding change and live check follow the verdict.
 - 2026-09-20 (coordinator, #1509 row 25): part 2b built against shared-signals a5425a2. Eight fixed verbs for the model (record_list, record_get, record_create, record_update, resolve_id, open_approval_request, get_approval_request, create_document), the connector's own client for bind and add_approval, the envelope's author and message ids read by the extension for per-turn write keys. Button evidence per the SetSpark coordinator: the connector posts a confirmation line and submits its url and text; a reply is its own evidence. Sage's key is minted (id sage-3ff47150, file outside the repo, never read here). Suite 63/63, node 162. Review candidate frozen for rev-code-02 (aggregate 09140edc, tree 7872d8c5); Gitea answered 503 when the request was posted, so the post is queued and retried. Slip: a stray `git stash` during doc checks stashed the tree for under a minute; popped at once and verified, 44 files back, tests green.
+
+- 2026-09-26 (sage, lead): Jason's ruling: Sage leads the project, Darkwing is a collaborating seat, more seats to follow, development stays in T3 for now. The fleet Sage seat that took Invoice Ninja coordination outside Jason's instructions is being decommissioned; moving work onto the new stack is the fix. Suites all green. Rows 24 and 25 pushed (1685deb4..43d7574d). Open: about 11 days of uncommitted agent work in the tree (row 16 launch files, row 22, #1512, WUI evidence), 23 untracked aws-* skill directories in skills/ from 2026-09-21, and Jason's target for the next phase.

docs/plans/DEFERRED.md

@@ -8,23 +8,65 @@ at every gate. Started 2026-09-12 during the control board MVP.
 
 ## Open
 
+- **Inherited Discord engine test intermittency during #1512 review.** Frozen
+  serialized run recorded a tool-turn engine assertion failure and then timed
+  out at 120s. A later full TAP run with a 15s test deadline passed 351/351.
+  Rocko isolated the busy/settled-event test race and missing failure cleanup;
+  Darkwing independently reproduced the event-split assertion. Rocko also reported
+  a timeout-log test race and a separate engine followUp-after-timeout defect.
+  No live incident established. Row21 owner orch-01 notified; no Discord source
+  takeover. Not assumed identical to earlier concurrent hangs.
+  Integration held pending owner disposition; logs and scope in
+  `agents/darkwing/work/relaunch-activity/r1-review.md`. (2026-09-15)
+  Outcome 2026-09-26: 1685deb4 fixed the busy/settled race and the engine no
+  longer sends a follow-up (held prompts). A re-run of the frozen candidate
+  against 21e3e908 passed the serial acceptance command 397/397 three times.
+  Two engine failures remain when tests run concurrently, and they reproduce on
+  clean HEAD without the #1512 files, so they are #1509's (entry below). Sage
+  ruled that #1512 integrates on the serial evidence; it landed in af4203ca.
+  Record: `agents/darkwing/work/relaunch-activity/rerun-2026-09-26.md`.
+
+- **Discord engine: leaked fake pi on a failed test, and a timeout gap in
+  `busy`.** (a) `engine.test.mjs:100` reads the fake's `commands.jsonl` 20 ms
+  after the second prompt and gets ENOENT under load. The test stops the engine
+  outside `finally`, so the fake pi child outlives it and the test file never
+  exits. Six other tests in the file also stop outside `finally`. This is one
+  confirmed cause of the concurrent hangs in the entry below. (b) In
+  `engine-pi.mjs`, `busy` is `state.busy || pending.some((t) => !t.done)`. If a
+  turn times out before its `agent_start` is read, the turn is marked done while
+  `state.busy` is still false. The next prompt then goes straight to pi, which
+  refuses it ("agent is streaming"). It fails closed, and production timeouts
+  are long enough to make it rare. Seen twice in two default-concurrency runs,
+  and once in three on clean HEAD. Fix in source and tests only; the live
+  connector does not restart for this without Jason's word. Rocko reviews.
+  (2026-09-26, #1509, Darkwing)
+
+- **Combined concurrent test hangs need isolation.** Row18 R1 frozen six-package runs timed out at 120s/60s, with logs in `/tmp/discord-board-r1-KbMrGQWF/TESTS-first-timeout.txt` and `TESTS-second-timeout.txt`. Serialized R3 independently passes 322/322. Cause and default-concurrency stability remain unverified; investigate separately without changing connector behavior or calling interrupted runs green. (2026-09-14, #1509)
+
 - **Registration has no "set by" field.** `mosaic seat task` records the
   task and `updatedAt` but not who set it, so a human session and the
   orchestrator look the same on the board. One-line record change; rides
   with the orchestrator assignment piece. (2026-09-12, #1504)
+- **Usage-limit notice was missed.** Jason reports Rocko exhausted usage without
+  Jason seeing the notice, and is now available again. Investigate where the
+  notice appeared and what operator notification is missing as part of Claude
+  console integration. User-reported, not independently reproduced; no root
+  cause established. Keep outside #1512's relaunch-display scope. (2026-09-15)
 - **Claude Code seats register but get no board row.** Rocko has no Pi
   session log, and rows come only from Pi logs. Needs a second row source
   or a Claude-side log reader. (2026-09-12, darkwing's #1504 report)
+  2026-09-15 #1511 live-test preflight reconfirmed no Rocko row: expected
+  `.pi/state/rocko/sessions` discovery directory absent. Its existing repo
+  registration names dead PID 185602, while the verified native lock owner is
+  3707667. No registration repair, discovery expansion or relaunch performed;
+  test write refused before mutation. Evidence:
+  `agents/darkwing/work/task-attribution/backend-live-verification.json`.
 - **Fleet seats (`~/.mosaic`) stay on the old launchers.** No registration,
   no board reply, no `seat task`. Moving them is the stress test and comes
   after the WebUI and fleet launch work. (Jason, 2026-09-12)
 - **Sage launcher hook is uncommitted.** `agents/sage/` is untracked; the
   registration guard was added by hand to match the other four. Commit with
   the sage directory. (2026-09-12)
-- **Relaunched seat shows the old last message.** Pi resumes the newest log,
-  so the row's activity stays stale until the first message; only the
-  registration's `startedAt` shows the relaunch. Refinement: "relaunched at
-  X, no messages since". (darkwing, Step 3 log, 2026-09-12)
 - **Comms skill has no rule for senders without a pane.** The board trailer
   covers it today; if another pane-less sender appears, put the rule in
   `skills/ms-communications` instead of a second trailer. (2026-09-12, #1505)
@@ -66,6 +108,12 @@ 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)
 
 ## Queue
 
@@ -74,3 +122,4 @@ Moved to `docs/plans/QUEUE.md` on 2026-09-13. This file holds only gaps.
 ## Done
 
 - 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.

docs/plans/QUEUE.md

@@ -10,7 +10,7 @@ How to find your next thing:
 - **A seat**: the first row where Owner is you and State is `in progress`,
   `in review` or `briefed`. If there is none, you have nothing; say so on the
   board and stop.
-- **Coordinator (Claude session)**: update this table at every gate, before
+- **Sage, project lead** (Jason's ruling 2026-09-26; Darkwing before that): update this table at every gate, before
   anything else is written. CURRENT.md is the narrative log; this table wins
   if they disagree.
 
@@ -24,16 +24,28 @@ 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 owner priority: row 6, the next already-briefed coordination item 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. Rows 9-13 still depend on row 6;
+this does not waive those dependencies or authorize publication/access changes.
+
 | # | Piece | Owner | Issue | State | Gate | Brief |
 |---|-------|-------|-------|-------|------|-------|
-| 1 | Control board MVP (scanner + page) | darkwing | #1503 | Jason: rule whether the page answers "who is waiting on me" without a terminal; then close #1503 and mark MOSAIC-STACK-D-001 completed | A passed 2026-09-12 | plan page, top |
+| 1 | Control board MVP (scanner + page) | darkwing | #1503 | targeted status correction fully operator accepted in row 22; broader MVP ruling remains separate | 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 | Jason: use WebUI Monday and give Gate E ruling; ea00ec66 published, Filbert approved, committed-tree 208/208 | E: Jason works Monday 2026-09-14 from the WebUI without the terminal | plan page, "Piece 4: WebUI first screen (Console)" |
-| 6 | Darkwing on point: darkwing assigns and gates filbert's work (piece 5 on the plan page) | darkwing | none yet | briefed; Jason: send the start message from the board on Sunday 2026-09-13 | F: filbert's item closes with zero human messages from Jason | plan page, "Piece 5: darkwing on point" |
+| 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..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 | #1511 and #1512 committed locally in af4203ca (with rows 18 and 22), not pushed; #1512 re-run against 21e3e908 passed the serial acceptance command 397/397 three times; failures under concurrency are #1509 engine tests, reproduced on clean HEAD, filed in DEFERRED; #1512 closes after Sage's records commit; board restart for live #1512 and the Gate F live assignment wait on Jason | 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 | Jason | — | recurring, end of Monday 2026-09-14 | 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 | — | queued; not before row 6 is done | Jason's call | none yet |
+| 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; starts when row 6 is done, before row 8 | 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; with row 9 | two briefs accepted by Jason with no scope question | `2026-09-13_queue-as-data.md`, Piece C |
@@ -41,14 +53,16 @@ Gaps found while working go to `docs/plans/DEFERRED.md`, not here.
 | 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 | briefed; assigned to darkwing, not started | a Sage (discord) row on the board shows live, offline and braked correctly, and reply from the board is refused | `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` |
-| 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 | in review: parts 1 and 2 (writes, web fetch and search) built 2026-09-16, suite 52/52, node 128; round 3 pinned for rev-code-02 on #1509 comment 26361 (supersedes rounds 1–2; adds the engine held-prompt fix); part 3 done live 2026-09-17 (SearXNG container on loopback, binding web key, restart; first live turn searched, fetched and wrote vault/Businesses/naming.md); Jason ruled D1–D4 2026-09-16 (SearXNG, Jason and Carmen write, any https host, rev-code-02) | 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-18: built (src/git.mjs, bin/git-credential.mjs, extension params, envelope requester, context paragraph, vault protocol via reserve_id and per-write locks); suite 58/58, node 143; rev-code-02 APPROVED round 1 (#1509 comment 26375, tree 82ab962f); D5 mechanism changed: the fleet helper declines github.com, so the package ships its own credential helper reading the 0600 seat token file; binding change and live check next | 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 | in progress 2026-09-20: Jason's go relayed by the SetSpark coordinator (plan v3.2, shared-signals 55b2515); part 2a built (config, key read per call, HTTP core, approval ledger, Approve button and `approve` reply resolution, bind and approval submission with restart retry); part 2b built against shared-signals a5425a2 (eight model verbs, connector client, button evidence by confirmation message); node 162 pass, suite 63 passed; rev-code-02 APPROVED round 1 (#1509 comment 26467, tree 7872d8c5); binding change and live check next | 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` |
+| 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 | committed and pushed 1685deb4 (2026-09-18); operator check pending. Earlier: parts 1 and 2 (writes, web fetch and search) built 2026-09-16, suite 52/52, node 128; round 3 pinned for rev-code-02 on #1509 comment 26361 (supersedes rounds 1–2; adds the engine held-prompt fix); part 3 done live 2026-09-17 (SearXNG container on loopback, binding web key, restart; first live turn searched, fetched and wrote vault/Businesses/naming.md); Jason ruled D1–D4 2026-09-16 (SearXNG, Jason and Carmen write, any https host, rev-code-02) | 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 | committed 1949ed8d, pushed 2026-09-26; binding change and live check pending. Earlier: done 2026-09-18: built (src/git.mjs, bin/git-credential.mjs, extension params, envelope requester, context paragraph, vault protocol via reserve_id and per-write locks); suite 58/58, node 143; rev-code-02 APPROVED round 1 (#1509 comment 26375, tree 82ab962f); D5 mechanism changed: the fleet helper declines github.com, so the package ships its own credential helper reading the 0600 seat token file; binding change and live check next | 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 | rev-code-02 approved round 1 (#1509 comment 26467); committed 43d7574d, pushed 2026-09-26; live check pending. Earlier: in progress 2026-09-20: Jason's go relayed by the SetSpark coordinator (plan v3.2, shared-signals 55b2515); part 2a built (config, key read per call, HTTP core, approval ledger, Approve button and `approve` reply resolution, bind and approval submission with restart retry); part 2b built against shared-signals a5425a2 (eight model verbs, connector client, button evidence by confirmation message); node 162 pass, suite 63 passed; next: rev-code-02 review on #1509, local commit | 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
@@ -62,7 +76,7 @@ Gate F or when blocked."
 | 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 screens beyond the first (launch, observe, stop, transcript, palette) | Needs a new brief after Gate E | DEFERRED.md |
+| 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
@@ -72,6 +86,9 @@ Gate F or when blocked."
 
 - 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.
@@ -88,6 +105,10 @@ Gate F or when blocked."
 - 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.
@@ -97,6 +118,12 @@ Gate F or when blocked."
 - 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.
@@ -105,7 +132,11 @@ Gate F or when blocked."
 - 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.