gosalyn: Case 2 playground ruling round d2 for Webby d1: a prefix that holds a book folder refuses (other-universe for another entry's book, mapping-invalid for its own), kind values and the draft key list, the readers of books and classify().book at cca206cdc with mapping.test.mjs:16-20, the 1.2 unmapped row, and a C2-01c line in section 8 (webby-0088 B1 N1-N4, mos-1233)

Library record repo with canon/playground scope by path, human-only library
verbs, cited-reply guard, five creative roles, rooms with @tags without a
schema change, Obsidian through a Gitea remote, and rows C2-01..C2-17.

agents/README.md

@@ -16,14 +16,6 @@ not fleet seats. Keep changes in `/mnt/storage/src/mosaic-stack`; do not modify
 | Rocko | General development, investigation, testing, and review | T3 session (Codex, gpt-6.1-sol, thread d99326cc, lead decision 122; Claude thread b84bb264 retired 2026-10-12); launcher Claude Code, Sonnet model | `agents/rocko/launch.sh` |
 | Filbert | General development, investigation, testing, and review | T3 session (Claude, Opus 5.5, thread 048f3c63, non-sandbox reviews only, lead decisions 130 and 134; Codex threads f712d8af and 50342f6a retired 2026-10-13, Claude thread 9cb9731e retired 2026-10-12); launcher Pi, `openai-codex/gpt-6-astra:low`, not to be used under R26 until it changes (lead decision 69) | `agents/filbert/launch.sh` |
 | Researcher | Source-grounded technical research and evidence | T3 session (Claude, Sonnet 5.5, thread 9bac0794, rows 97 and 98, lead decision 124); Haiku rows (71, 80, 84, 88, later 96) run as subagents Sage dispatches with model haiku, effort high and a worktree (lead decision 129); Haiku thread c98aaf4a retired 2026-10-13 unused; launcher Pi, configured Mosaic model | `agents/researcher/launch.sh` |
-| Launchpad | Builder, MVP T1 row 192 (Q175 SSO phase 1) | T3 session (Claude, Opus 5.5), started by Sage under mos-0974/0977 | none, T3 only |
-| Morgana | Builder, MVP T1 row 193 (human users and RBAC) | T3 session (Claude, Opus 5.5), started by Sage under mos-0974/0977 | none, T3 only |
-| Honker | Builder, MVP T1 row 194 (agent lifecycle) | T3 session (Claude, Opus 5.5), started by Sage under mos-0974/0977 | none, T3 only |
-| Gander | Builder, the human boundary across uids (P19 333, #1694) | T3 session (Codex, gpt-6.1-sol), started by Sage under mos-0977 | none, T3 only |
-| Herb | Builder, a second gate lane (#1695) | T3 session (Codex, gpt-6.1-sol), started by Sage under mos-0977 | none, T3 only |
-| Bushroot | Builder, retire the control board writer on 7331 (#1696) | T3 session (Claude, claude-haiku-5-5), started by Sage under mos-1008 | none, T3 only |
-| Webby | Reviewer: Case 2 designs, rows 192 and 194 | T3 session (Claude, Opus 5.5, thread 03086006), started by Mos (mos-0981) | none, T3 only |
-| Duckworth | Reviewer: federation designs, row 193 | T3 session (Claude, Opus 5.5, thread ffceafec), started by Mos (mos-0977) | none, T3 only |
 | 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

agents/bushroot/README.md

@@ -1,8 +0,0 @@
-# Bushroot
-
-Builder seat, Claude Haiku 5.5, started by Sage under mos-1008 item 2 (a low-level model under Q177) for the row
-that retires the control board writer on 7331 (#1696).
-
-No launcher in this directory. The seat runs as a T3 thread and works in its own worktree. It has no
-credentials of its own; until the credentials row settles per-agent identity, it pushes only its own `bushroot/*`
-branches through the repository credential helper (mos-0981), never `refactor`, `main` or another seat's branch.

agents/bushroot/work/queue-198/DESIGN.md

@@ -1,292 +0,0 @@
-# Row 198 design: retire the control board writer on 7331
-
-Gitea #1696. Brief `docs/plans/2026-10-20_retire-control-board.md` (blob 11977a5cb, commit a31f1a0f8, Mos's
-call mos-1019). Owner Bushroot, reviewer Webby, gate owner Sage. Inventory: `agents/bushroot/work/queue-198/INVENTORY.md`
-(004f133bd, sha256 76b630ce...877).
-
-Base: brief commit a31f1a0f8 is on origin `refactor` (head aa1bd209e). This branch rebases on `refactor` after
-row 192 lands (Sage's sequencing, ruling 4).
-
-## Revision 5 (Webby REVIEW-r4.md, origin/webby/reviews 5a02ee395, on rev 4 9af75dc72; Mos mos-1045)
-
-- **B1 (r4, the `--tester-port` swap)**: reverted. `parses_flag` is for `--board` only. The `--tester-port` grep at
-  `stack-release.sh:670` stays. The `--tester-port` test row I added in rev 4 is removed.
-- **N1 (r4, stale mark)**: fixed. A write counter guards `index()` coalescing. `markSeen()` and `reply()` start a fresh
-  scan and never join one. The new `board.test.mjs` case is in the new-tests table, and mutant M15 is in the table.
-- **Sequencing (sage-1386)**: row 197 lands before 198. The rebase is noted under Open points.
-
-## Revision 4 (Webby REVIEW-r3.md, origin/webby/reviews c9d65664a, on rev 3 7e2ead7f3)
-
-- **B1** (blocking child calls): fixed. The board's child calls become async. `createBoard` takes an async `exec`,
-  and `index()`, `markSeen()` and `reply()` return promises. The sync `scan` and `replyToRow` stay for the CLI and
-  their existing tests. See decision 10, the new B1 test and mutant M14.
-- **N1** (fallback copy): fixed. Decision 8 now says which copy gets the 7331 fallback.
-- **N2** (flag check matched a refusal): fixed. The parse check matches the parser branch, not the flag name. See
-  decision 8. M12's target now names `--board` only in a refusal.
-
-## Revision 3 (Sage rulings sage-1372, on rev 2 80fd45521)
-
-- Ruling 1: `/api/seen` goes under `--send`, the same as `/api/reply`. Mos agrees (mos-1023 item 5). Both POSTs sit
-  above `serve.mjs:558` (decision 5).
-- Ruling 2: the board context keeps the writer's read-only fleet default (decision 9).
-- Ruling 3: a rollback to a copy with no recorded `--board` falls back to 7331, which is dark, as it is today (decision 8).
-- Ruling 5: loopback stays read-only. No new gate in this row. The cross-uid loopback gate is row 196's. Sage took
-  this to Mos (sage-1370). If Mos rules otherwise, Sage says so and this design changes.
-- Ruling 6, correction: neither the live pointer nor the live unit carries `--board`. Sage checked the live
-  `ExecStart`: `cli.mjs serve --checkout /mnt/storage/src/mosaic-stack --port 7332 --public-host mosaic.woltje.com
-  --auth-header X-authentik-username --allow-user jason.woltje --send --tester-port 7333`. Rev 2 said otherwise, and
-  that was wrong. Decisions 6 and 8 are rewritten. The B2 guard stays. `webui-service.sh` lines 44, 71, 110 and 163
-  still take and emit `--board`, so they are in the retirement.
-- Ruling 7: base. Brief commit a31f1a0f8 is on origin `refactor` at aa1bd209e.
-
-## Revision 2 (Webby REVIEW.md, origin/webby/reviews 9afb947c7)
-
-Rev 1 was c8fe23a37. Rev 2 answered B1-B3 and N1-N5 (80fd45521). Changes are marked where they land.
-
-- **B1** (pinned copy): fixed. `packages/control-board/src` and `tools/tmux/agent-send.sh` join `COPY_PATHS`. The
-  copy test starts the Console from a fresh copy and expects 200 on `/api/board`. See decision 7.
-- **B2** (re-pin carries `--board`): fixed. `stack-release.sh` drops `--board` when the target's `cli.mjs` lacks it,
-  as `console_for_target` already does for `--tester-port`. The plan lists the drop. See decision 8.
-- **B3** (POST placement): fixed. The board POST branches sit above the refusal at `serve.mjs:558`, after the
-  header and origin checks, next to bus message and chat. Loopback cannot reply or mark seen. See decision 5 and mutant M10.
-- **N1**: the board context uses the writer's default fleet source. See decision 9.
-- **N2**: the M2 check covers all of `packages/control-board/src`, not one file.
-- **N3**: the lines that change are listed by file in "Test line changes" below.
-- **N4**: the README records that loopback board reads stay open to any local process until Mos rules.
-- **N5**: row 198 lands after row 192. The board route tests rerun on the rebased tree.
-
-## Decisions
-
-1. **The Console calls the board's read code in-process.** A new module `packages/control-board/src/board.mjs`
-   holds the route logic that `createServer` runs today: rescan, mark seen, reply and conversation read. It
-   imports no `node:http` and opens no socket. Its methods are async (decision 10).
-2. **No listener anywhere in the board package.** `createServer` and `startServer` are deleted from
-   `serve.mjs`. `serve.mjs` keeps its pure exports (`replyToRow`, `isLoopbackHost`, `foreignRequest`,
-   `conversationResponse`, `REFUSAL_STATUS`, the reply constants). That keeps `packages/conversation/tests/flows.test.mjs`
-   unchanged. The file name `serve.mjs` now misleads. Renaming it is a separate follow-up and is not in this row.
-3. **The writer's CLI refuses `serve`.** `packages/control-board/src/cli.mjs` keeps `scan`. `serve` exits 2 with a
-   message that points to the Console. The default port 7331 goes away.
-4. **The Console gets the board by context, not by URL.** `startServer` in `packages/webui/src/serve.mjs` takes
-   `board` as a context object (or `null` when no board is configured), not a URL. `DEFAULT_BOARD`, `boardURL`
-   and the proxy `fetch` are removed.
-5. **`/api/reply` and `/api/seen` are gated by `--send`, and sit above the `:558` refusal.** Today the loopback Console
-   forwards both POSTs with no `--send` check. That is a real gap, and this row closes it. Placement matters.
-   In preview mode, `serve.mjs:558` refuses every non-GET before the board block, so a board branch below it never
-   runs. In loopback mode, `--send` cannot be set at all (`:479`). So both POST branches go after the header and
-   origin checks (`:493-516`), beside `/api/bus/message` (`:550`) and chat (`:554`), and require
-   `send !== null && named`. The result: `/api/reply` is the first board write the live Console has ever allowed.
-   Mos ruled it in (mos-1019), and mos-1023 item 5 confirms `/api/seen` too. In loopback mode, reply and mark-seen
-   refuse with 403 `read-only`. Board reads still work there. `/api/seen` writes marks under the data root, and without
-   the gate it would be the only preview-mode POST that passes without `--send`.
-6. **The retirement removes `--board` from the Console scripts.** No installed unit or live pointer carries `--board`
-   (Sage checked, rev 3). So no live unit needs a flag change to start. The flag goes from `packages/webui/src/cli.mjs`
-   (`:14`, `:18`, `:32`) and `scripts/webui-service.sh` (lines 44, 71, 110, 161-163). An old `--board` argument refuses
-   with the usage error (exit 2). A re-pin with the flag removed is an ordinary re-pin. Cutover needs no unit edit.
-7. **The pinned copy carries the board code (B1).** The live Console runs from `copies/<sha>`. `COPY_PATHS` in
-   `scripts/stack-copy.sh` (lines 23-33) lacks `packages/control-board/src` and `tools/tmux`. Without them a
-   Console from a copy fails at import, and `reply` cannot find `agent-send.sh`. Both paths join `COPY_PATHS`.
-   `tools/tmux` goes in whole, the same way `packages/plugins` does, because `agent-send.sh` may load its own
-   siblings. The `control-board/src` closure is `conversation/src`, `discord/src` and `seat/src`, and those are already in
-   the list.
-8. **Re-pin and rollback drop `--board` when the target cannot parse it (B2 guard).** The pointer's console flags
-   (`P_CONSOLE`, `stack-release.sh:128`) pass through `:676` into `RUN_CONSOLE`, and `:459` passes them to
-   `webui-service.sh install`. The live pointer has no `--board` (rev 3), so this is a guard for a pointer that
-   carries one, such as an older pointer or a rollback target. Rule: keep `--board` only when the target's
-   `packages/webui/src/cli.mjs` parses it. Otherwise drop it and report the drop in the plan. That is the same shape
-   as `console_for_target` and `--tester-port` (`:667`, `:687-690`). Rollback to a copy that parses `--board` keeps
-   the recorded flag. A copy that does not parse it (a new copy) gets the flag dropped and starts with no board URL,
-   so its board is in-process or null, never 7331. The 7331 fallback applies only to an older copy that parses
-   `--board` and has no recorded flag. That copy starts with its own default, 7331, which is dark, the same as today
-   (Sage ruling 3).
-   **Parse check (N2, rev 5).** "Parses it" means the target's `cli.mjs` holds the parser branch, `flag === '--board'`,
-   not the flag name. The name also appears in the usage text and in refusal messages, so a plain `grep` would count
-   a copy that refuses the flag as one that accepts it. One helper, `parses_flag FILE FLAG`, greps for
-   `flag === 'FLAG'`. It is used for `--board` only, in `console_for_target` and the rollback path. The existing
-   `--tester-port` grep at `stack-release.sh:670` stays as it is (Webby REVIEW-r4). Changing it would break the
-   `stack-release.test.mjs:265` fixtures, which write a comment, not a parser line. No copy names `--tester-port` in a
-   refusal today, so the gap exists only for `--board`.
-9. **The board context uses the writer's default fleet source (N1).** `--fleet` defaults to `~/.mosaic/fleet/agents`,
-   as the writer did (`cli.mjs:14`). The Console reads it and never writes it. Whether the fleet is retired
-   and the default becomes `none` is a later decision. This row keeps the board's contents unchanged.
-10. **The board's child calls are async (B1).** The Console runs the board in its own process. A blocking child call
-    would stall every route, the event stream, `/healthz` and the tester listener, which shares the process
-    (webui `cli.mjs:91`). Rule: no `spawnSync` on any path that `createBoard` reaches.
-    - `scan.mjs` gains `tmuxInspectAsync` (same args, same 5 s timeout) and `scanAsync`. The sync `tmuxInspect` and
-      `scan` stay for the CLI. The parse of the tmux output is one pure function that both paths call, so they cannot
-      drift.
-    - `serve.mjs` gains `replyToRowAsync` (same 15 s timeout, same env, same result shapes). The sync `replyToRow`
-      stays for its existing tests. The reply trailer and status mapping are shared pure code.
-    - The default async `exec` is `spawn` with a timeout that kills the child. A timeout or a spawn failure maps to
-      `{ error }`, the same shape the sync path returns. Tests inject `exec`.
-    - `index()` coalesces concurrent calls, but only onto a scan that started after the last write (rev 5, Webby N1).
-      The board keeps a write counter. `markSeen()` and `reply()` bump it, then start a fresh scan and never join one.
-      `index()` joins an in-flight scan only when that scan started at the current counter value. So an answer never
-      omits a mark that was set before it was asked for. This coalescing is my choice to limit tmux calls under
-      parallel reads; the design has no other constraint on it.
-    - `conversation(url)` spawns nothing. It reads files on the event loop, as the writer did. Not changed in this row.
-
-## Open points for Sage and Mos
-
-- **Auth on loopback (Sage ruling 5, taken to Mos as sage-1370).** The Console has two modes. In preview mode, a named
-  request needs the proxy header and proof, and the board routes inherit that. In loopback mode (no `--public-host`),
-  there is no sign-in. Loopback stays read-only with no new gate in this row. Board reads stay open to any local
-  process, as they are today. Reply and mark-seen cannot run there, because `--send` needs preview mode. The
-  cross-uid loopback gate is row 196's. If Mos rules otherwise, Sage says so and this design changes.
-- **Row 192 overlap (Launchpad, SSO on `webui/src/serve.mjs`).** My edits touch these regions of
-  `packages/webui/src/serve.mjs`:
-  - lines 12-27 (`DEFAULT_BOARD`, `boardURL`)
-  - line 466 (`startServer` signature, `board` option)
-  - lines 473 (`upstream`)
-  - lines 556-580 (board proxy block)
-  - lines 598-610 (`/api/config` `board` field)
-
-  I do not edit the preview and proof gate (lines ~486-505) or the auth-header checks. The board branches go
-  after those checks, in the same order as the bus and chat branches. Sage should sequence 192 and 198 so the
-  second one rebases on the first. I will not touch the SSO code.
-- **Cutover.** The new Console code reaches the live Console through a copy and re-pin. The restart is a human
-  step (`console-holds-human-authority`). No unit flag changes (decision 6). The live unit stays up until then.
-- **Sequencing (ruling 4, sage-1386).** Sage sequences 198 after 192 and after row 197 (Herb). I rebase once, onto the
-  tree with 192 and 197 landed, and rerun the board route tests there. 197 replaces closed-endpoint ports with dynamic
-  allocations. Its overlap with this row is `packages/webui/tests/serve.test.mjs:100` and
-  `packages/webui/tests/preview.test.mjs:208`. My rewrites of those lines (the dead-board 503 change at serve.test.mjs:79
-  and :105, and preview.test.mjs:219 in the N3 list) are written against 197's dynamic ports, not the old fixed ones.
-  I do not edit either overlap line before 197 lands. The manifest goes to review only after the rebase.
-
-## File-by-file
-
-### Board package
-
-| File | Change |
-|---|---|
-| `packages/control-board/src/board.mjs` | **New.** `createBoard({ specs, boardDir, seatsDir, discordDataRoot, isAlive, now, agentSend, exec, conversationReader })`. Returns `{ index(), markSeen(body), reply(body), conversation(url) }`. `index`, `markSeen` and `reply` return promises and use the async paths (decision 10). Each method is the body of a route that `createServer` runs now. No `node:http`, no listener. |
-| `packages/control-board/src/scan.mjs` | Adds `tmuxInspectAsync` and `scanAsync`, and one shared pure parse. Sync `tmuxInspect` and `scan` stay for the CLI. |
-| `packages/control-board/src/serve.mjs` | Delete `createServer` (lines 229-310), `startServer` (312-322), `page` loading (`loadPage`, 224-227), and the `node:http` import. Keep the pure exports and the sync `replyToRow`. Add `replyToRowAsync` (decision 10). Remove the `7331` default. |
-| `packages/control-board/src/cli.mjs` | `serve` exits 2 with `refused: the control board no longer serves HTTP. Use the Console: node packages/webui/src/cli.mjs serve`. The `--port` and `--host` flags are removed. `scan` is unchanged. Usage text is updated. |
-| `packages/control-board/src/page.html` | Delete. The Console serves its own `index.html`. |
-| `packages/control-board/README.md` | Remove the `serve` section (lines ~107, 127), the port default and the start instructions. Keep the reply-convention text (lines 144-151). It names no start command. |
-| `packages/control-board/package.json` | The `mosaic-board` bin keeps `scan` only. Description text updated. |
-
-### Console
-
-| File | Change |
-|---|---|
-| `packages/webui/src/serve.mjs` | Remove `DEFAULT_BOARD`, `boardURL` and the proxy `fetch`. `startServer({ board })` takes a context object or `null`. Board routes call `board.index()`, `board.markSeen()`, `board.reply()` or `board.conversation()` directly. If `board` is `null`, the board routes answer 503 with `{ error: 'no board configured' }`. `/api/reply` and `/api/seen` need `send !== null && named`, the same gate as the other writes. Without it they answer 403 `read-only`. `/api/config` returns `board: null` and no URL. The app reads `config.board` only for the footer text, so a `null` value needs a small change in `app.js:468`. |
-| `packages/webui/src/cli.mjs` | Remove `--board` and its usage text. Build the board context from the config, `--checkout` (or cwd, as the writer did), and the seats and board dirs. Failure to read the system config gives `board: null`, not a refusal. The Console still starts, as it does for the bus today. |
-| `packages/webui/src/public/app.js` | Line 468: keep the footer, show `Board: in-process` (or hide it). Lines 365, 468 and the 502 message text (`Board unreachable ... Check the board server`) are reworded. The text is not a contract. |
-| `packages/webui/src/public/index.html` | No change. |
-| `packages/webui/README.md` | Remove the start line (10), the `--board` line (15), the test command that lists `control-board/tests/` (766, keep only the in-process tests), and the rollback line (881). |
-| `packages/webui/systemd/mosaic-webui.service.in` | No change in the template. The `@FLAGS@` set loses `--board`. |
-| `scripts/webui-service.sh` | Remove `--board` from the usage (44, 71), the parser (110), the validation (161-162) and the flag (163). An old `--board` argument refuses with the usage error. |
-| `scripts/stack-copy.sh` | **B1.** `COPY_PATHS` (23-33) adds `packages/control-board/src` and `tools/tmux`. |
-| `scripts/stack-release.sh` | **B2.** `console_for_target` (around 664-692) drops `--board` when the target's `cli.mjs` does not parse it. The plan line names the drop. Rollback keeps the recorded flag when the target parses it. |
-| `packages/webui/README.md` | Also records (N4) that loopback board reads stay open to any local process until Mos rules. |
-| `packages/webui/src/public/bus.js` | No change. The `#/` board link is the Console's own page, not 7331. |
-
-### Tests (webui)
-
-Fixture plan. "Dead board" means a context whose `index()` throws, which replaces `board: 'http://127.0.0.1:9'`.
-
-| File | Change |
-|---|---|
-| `packages/webui/tests/fixture.mjs` | Call `createBoard` directly. Pass the context to `startServer`. No port 0 board server. |
-| `packages/webui/tests/history-fixture.mjs` | Same as fixture.mjs. |
-| `packages/webui/tests/discord.test.mjs` | Same. Board server removed. |
-| `packages/webui/tests/relaunch.test.mjs` | Same. |
-| `packages/webui/tests/return-flow.test.mjs` | Same. |
-| `packages/webui/tests/tester-fixture.mjs` | `board: 'http://127.0.0.1:9'` becomes the dead board. |
-| 16 files with `board: 'http://127.0.0.1:9'` (bus, chat, instances-browser, limits-browser, messages, pinned-copy, preview, proof-cli, proof, routes-browser, send, settings-form, tester-cli, tester-listener, usage-browser, views) | Mechanical: dead board. Assertions that expect a 502 `Board unreachable` string are updated to the new 503 `no board configured` or the dead-board error text. Sage needs to confirm this count before the edit. |
-| `packages/webui/tests/serve.test.mjs` | Lines 17-19 (`boardURL` checks) are removed. Add the new board route tests (below). |
-| `packages/webui/tests/reads.test.mjs` | Line 188: the `board` setting becomes `null`. |
-| `packages/webui/tests/service.test.mjs` | Lines 225-394: unit `ExecStart` text loses `--board`. The `--board` refusal cases (250, 260, 394) become refusal of the old flag. |
-| Browser tests (`browser-edge`, `bus-browser`, `chat-browser`, `docs-browser`, `editor-browser`) | Fixture context only. No change to the browser assertions. |
-
-### Tests (control board)
-
-| File | Change |
-|---|---|
-| `packages/control-board/tests/serve.test.mjs` | 32 tests use HTTP. Move the route assertions to `board.test.mjs`, which calls `createBoard` directly. Keep the `replyToRow` tests here. |
-| `packages/control-board/tests/discord.test.mjs` | Two HTTP uses (lines 123 and the `startServer` call). Call `createBoard`. |
-| `packages/control-board/tests/scan.test.mjs`, `attention*.test.mjs`, `relaunch.test.mjs` | No change. They test `scan`, not HTTP. |
-| `packages/control-board/tests/retired.test.mjs` | **New.** Three checks, all in-process, no socket. (1) `cli.mjs serve` exits 2 and prints the Console pointer. (2) The module graph has no `node:http` import and no `listen(` call in `packages/control-board/src`. (3) A grep over the start paths (`scripts/`, `*.service*`, `packages/*/README.md`, `package.json` scripts) finds no `control-board.*serve` or `7331` starter. |
-
-### New tests for the acceptance items
-
-| Test | Where | Assertion |
-|---|---|---|
-| Board view answers with nothing on 7331 | `packages/webui/tests/board-inprocess.test.mjs` (new) | Console with a context returns 200 on `/api/board` with a stubbed `globalThis.fetch` that throws on any call. Zero fetch calls. |
-| Every board route refuses without the Console's gate | same file | In preview mode, `/api/board`, `/api/seen`, `/api/reply`, `/api/conversations` each return 401 without the header and 403 with a foreign Host. |
-| `/api/reply` refuses without `--send` | same file | Preview mode, no `send`. POST `/api/reply` returns 403 `read-only`. `replyToRow` is never called (an injected `exec` counts calls). |
-| `/api/seen` refuses without `--send` | same file | Same shape. No mark file written. |
-| `/api/reply` runs with `--send` | same file | Positive control: with `send` and the sign-in header, the injected `exec` is called once with the expected argv. |
-| No Console proxy left | `packages/webui/tests/board-inprocess.test.mjs` | `DEFAULT_BOARD` is not exported. `boardURL` is not exported. Grep check: no `7331` in `packages/webui/src`. |
-| markSeen answer includes its own mark (N1, rev 5) | `packages/control-board/tests/board.test.mjs` (new) | Hold a scan in flight with an injected exec that resolves late. Call `index()`, then `markSeen()` before the scan resolves. The `markSeen()` answer shows the mark. A mutant that joins the pre-write scan must fail it. The same check covers `reply()`. |
-| Board does not block the Console (B1) | same file | Injected async `exec` for the tmux check resolves after 2 s. While `/api/board` is pending, `/healthz` answers within 200 ms. Mutant M14 uses an `exec` that blocks the thread for 2 s with `Atomics.wait`, and this test must kill it. |
-
-## Mutants
-
-Each mutant runs on a scratch copy of the tree (not the live checkout), with the new tests. The test that
-must kill it is listed. A mutant that survives means the test is weak.
-
-| # | Mutant | Must be killed by |
-|---|---|---|
-| M1 | `cli.mjs serve` calls `startServer` again on 7331 | `retired.test.mjs` (1) |
-| M2 | `serve.mjs` restores `createServer` or `startServer` and exports them | `retired.test.mjs` (2) |
-| M3 | Console `DEFAULT_BOARD` is restored and the proxy `fetch` returns | `board-inprocess.test.mjs` zero-fetch case |
-| M4 | `/api/reply` skips the `send` check | `/api/reply refuses without --send` |
-| M5 | `/api/seen` skips the `send` check | `/api/seen refuses without --send` |
-| M6 | The board block runs before the preview and header gate | "every board route refuses" (401 case) |
-| M7 | A board route accepts a foreign Host | "every board route refuses" (403 case) |
-| M8 | `scripts/webui-service.sh` re-accepts `--board` | `service.test.mjs` refusal case |
-| M9 | A README or script again tells people to run `control-board serve` | `retired.test.mjs` (3) |
-| M10 | The `/api/reply` and `/api/seen` branches move below the `:558` refusal | The positive control "`/api/reply` runs with `--send`" (403 from `:558`) |
-| M11 | `COPY_PATHS` drops `packages/control-board/src` or `tools/tmux` | Fresh-copy test in `pinned-copy.test.mjs`: `/api/board` must answer 200 |
-| M12 | `console_for_target` keeps `--board` for a target that does not parse it | `stack-release.test.mjs`: re-pin plan lists the drop; install argv has no `--board`. The target `cli.mjs` names `--board` only in a refusal message and has no parser branch (N2). A grep-based check keeps the flag and this test kills it. |
-| M15 | `index()` joins a scan that started before the last write (N1) | the `markSeen` answer case in `board.test.mjs` |
-| M13 | Rollback drops a recorded `--board` from a target that parses it | `stack-release.test.mjs`: rollback keeps the flag |
-| M14 | The board's tmux check or reply runs through a blocking call (`spawnSync`, or an `exec` that blocks the thread) | `board-inprocess.test.mjs` B1 case: `/healthz` must answer within 200 ms while `/api/board` is pending |
-
-Mutants M11 to M13 run in the cli suite, which needs Sage's slot. M10 and M14 run in one webui test file each.
-
-## Test additions (B1, B2)
-
-| Test | File | Assertion |
-|---|---|---|
-| Fresh-copy Console answers the board | `packages/webui/tests/pinned-copy.test.mjs` (extend) | `stack-copy.sh` builds a copy at a fixed sha in a temp dir. Starts the Console from it on port 0. `GET /api/board` returns 200 JSON. `agent-send.sh` resolves inside the copy. |
-| Re-pin drops `--board` | `packages/cli/tests/stack-release.test.mjs` (extend) | Pointer records `--board`. Target `cli.mjs` lacks the parser branch, and names `--board` only in a refusal (the N2 fixture). The plan names the drop. The install argv has no `--board`. |
-| Rollback keeps `--board` | same | Rollback to a copy with `flag === '--board'` in its `cli.mjs` keeps the recorded flag. |
-
-## Test line changes (N3)
-
-Board-related lines that change, by file:
-
-- `packages/webui/tests/serve.test.mjs:79`: `/api/board` on a dead board, 502 becomes 503.
-- `packages/webui/tests/serve.test.mjs:105`: 502 with the board URL in the body. Becomes 503 with no URL.
-- `packages/webui/tests/preview.test.mjs:219`: dead board, 502 becomes 503. `board.body.board` is no longer a URL.
-- `packages/webui/tests/send-browser.test.mjs:89`: a `502 board unreachable` string. Verify at edit time. Likely a bus status, which stays.
-- `packages/webui/tests/serve.test.mjs:17-19`: `boardURL` checks, removed.
-
-Unchanged, not board: `bus.test.mjs:226-236`, `chat.test.mjs:171-179`, `instances.test.mjs:163-168`,
-`limits-route.test.mjs:35`, `project-file.test.mjs:128`, `routes.test.mjs:170`, `send.test.mjs:230`,
-`tester-cli.test.mjs:57`, `tester-listener.test.mjs:113`, `usage.test.mjs:24`, `board-held.test.mjs:204` (page text).
-
-Dead-board fixture files (16 webui plus `tester-fixture.mjs`) match Webby's count.
-
-## Gate
-
-Mutant runs use single test files, which run freely. Any suite (control-board, webui, cli, every
-`scripts/test-*.sh`) needs Sage's slot.
-
-Webby approves INVENTORY.md (already sent), then this DESIGN.md, then the manifest. Sage's gate runs the
-control-board and webui suites, the cli suite and every `scripts/test-*.sh`. All must be green, and mutants
-M1-M15 killed.
-
-## Stop points
-
-- If Mos rules that loopback board reads need a gate, this design changes. Sage tells me, and I stop and report.
-- If the Console's auth model changes under row 192, the board block in section "Console" changes with it.
-- The Console restart and unit re-render are Jason's or Mos's steps. I do not run them.
-
-## Boundaries kept
-
-No change to the live units, `~/.mosaic-dev`, `~/.config/mosaic-dev`, slot files, `~/.mosaic`, or any live port.
-No request to 7331 or 7332 at any point.

agents/bushroot/work/queue-198/INVENTORY.md

@@ -1,125 +0,0 @@
-# Row 198 inventory: control board writer and port 7331
-
-Gitea #1696. Brief: `docs/plans/2026-10-20_retire-control-board.md`. Owner Bushroot, reviewer Webby, gate owner Sage.
-Scope: tracked files at `bushroot/row198` (base `refactor`). Excludes `v1/` and other seats' `agents/*/work/` packets.
-Method: `git grep -I` for `control-board`, `control_board`, `controlboard` and `7331`, then a read of each code hit.
-
-## Classes
-
-- **starts**: runs `packages/control-board` `serve`, or a unit, script or default that does.
-- **imports**: loads code from `packages/control-board` at run time or test time.
-- **mentions**: text only (docs, comments, fixture strings, history).
-
-## Result
-
-**Live dependency found. Stop before any removal.** The Console (`packages/webui`) proxies its board reads and
-writes to the writer on 7331. The Console's board view, `/api/board`, `/api/seen`, `/api/reply` and the
-conversation routes all forward to `DEFAULT_BOARD = http://127.0.0.1:7331`. The Console has no board without
-a writer on that port. Mos decides before anything is removed.
-
-Nothing in the repository runs `control-board serve` from a unit. The only starter is the manual command in
-`packages/control-board/README.md` and `packages/webui/README.md`. `ss -ltnp` showed nothing on 7331 at
-2026-10-20T19:05:09Z (brief).
-
-## Hits
-
-### Starts the writer, or defaults to its port
-
-| File | Line | Class | What it does |
-|---|---|---|---|
-| `packages/control-board/src/cli.mjs` | 4, 14 | starts | `serve` subcommand; default `port: 7331` |
-| `packages/control-board/src/serve.mjs` | 312 | starts | `startServer` default `port = 7331` (the writer itself) |
-| `packages/control-board/README.md` | 107, 127 | starts | Tells people to run `serve` and open 7331; documents the default |
-| `packages/webui/README.md` | 10 | starts | Tells people to run `node packages/control-board/src/cli.mjs serve` |
-| `packages/webui/README.md` | 15, 881 | depends | Console reads the board at 7331; rollback uses "the unchanged board at 7331" |
-| `packages/webui/src/cli.mjs` | 14, 18 | depends | `--board` default is `DEFAULT_BOARD` (7331) |
-| `packages/webui/src/serve.mjs` | 12, 473, 561, 578, 610 | **depends (live)** | `DEFAULT_BOARD`; proxies `GET /api/board`, `GET /api/conversation(s)`, `POST /api/seen`, `POST /api/reply` upstream; returns 502 if the writer is absent |
-| `packages/webui/src/public/app.js` | 468, 365 | depends | Page reads `/api/config` board, then `/api/board` through the Console proxy |
-| `packages/webui/src/public/bus.js` | 1037, 1088, 1100 | depends | Routes `#/` to the board page; bus pages link to it |
-| `scripts/webui-service.sh` | 89-163 | depends | Renders the Console unit with `--board URL`; default comes from `serve` |
-| `packages/webui/systemd/mosaic-webui.service.in` | 29 | depends | Unit runs the Console (`webui/src/cli.mjs serve`), not the writer; flags carry `--board` |
-| `scripts/stack-copy.sh` | 88 | mentions | Checks the Console `ExecStart` string; no writer reference |
-| `scripts/stack-release.sh` | 1372 | mentions | Checks the Console command line; no writer reference |
-
-### Imports code from `packages/control-board`
-
-| File | Line | Class | What it imports |
-|---|---|---|---|
-| `packages/webui/tests/fixture.mjs` | 6 | imports | `startServer` from `control-board/src/serve.mjs` (test fixture for the Console) |
-| `packages/webui/tests/history-fixture.mjs` | 8 | imports | same |
-| `packages/webui/tests/discord.test.mjs` | 6 | imports | same |
-| `packages/webui/tests/relaunch.test.mjs` | 6 | imports | same |
-| `packages/webui/tests/return-flow.test.mjs` | 13 | imports | same |
-| `packages/conversation/tests/flows.test.mjs` | 15 | imports | `replyToRow` from `control-board/src/serve.mjs` |
-
-The webui tests run the writer's server in-process. They do not start the writer on 7331 (the tests bind
-their own port), but they need `serve.mjs`. Any removal or refusal in `serve.mjs` breaks these tests unless
-the writer's read-only code moves first.
-
-`packages/webui/src/` (non-test code) does not import `control-board`. Only the tests do.
-
-### Tests that name the writer or its files
-
-| File | Line | Class | Note |
-|---|---|---|---|
-| `packages/control-board/tests/serve.test.mjs` | 37, 744-767 | imports | Tests the writer: reply runner, `REPLY_TRAILER`, `-S <host>:control-board` |
-| `packages/control-board/tests/scan.test.mjs` | 47, 306, 353 | mentions | Tmp dir names and comments |
-| `packages/webui/tests/serve.test.mjs` | 18-19, 35 | mentions | `boardURL` checks on port 7331; reply trailer string |
-| `packages/webui/tests/reads.test.mjs` | 188 | mentions | Expected `board` setting value 7331 |
-| `packages/webui/tests/service.test.mjs` | 225-394 | mentions | Unit `ExecStart` text includes `--board http://127.0.0.1:7331` |
-| `packages/plugins/tests/harness.test.mjs` | 173 | mentions | Path string `packages/control-board/src/scan.mjs` |
-| `packages/ledger/tests/ledger.test.mjs` | 80, 233-327 | mentions | Sender name `control-board` as a test fixture |
-| `packages/queue/tests/fixtures/genesis-render.md` | 6-11 | mentions | Fixture text |
-| `packages/conversation/tests/reader.test.mjs` | 2 | mentions | Comment |
-| `packages/conversation/README.md` | 207 | mentions | Says the control-board suite serves the routes |
-
-### Code that reads the sender name, not the writer
-
-| File | Line | Class | Note |
-|---|---|---|---|
-| `packages/ledger/src/ledger.mjs` | 120 | mentions | Classifies `control-board` as sender kind `board`. No import. |
-
-### Package and script metadata
-
-| File | Line | Class | Note |
-|---|---|---|---|
-| `packages/control-board/package.json` | 2, 5, 9 | starts | Declares `bin: mosaic-board -> src/cli.mjs` (a `mosaic-board serve` entry point) |
-| `package.json` (root) | - | none | No script names the board or 7331 |
-| `scripts/mosaic` | 3 | mentions | Comment only |
-| `packages/seat/package.json` | 5 | mentions | Description: "the control board reads" registration |
-| `packages/seat/README.md` | 139 | mentions | Says the board reads `registration.json` |
-| `packages/plugins/README.md` | 181 | mentions | Names `scan.mjs` in an exception note |
-
-### Docs (mention only)
-
-- `AGENTS.md` lines 144-150: reply convention for control-board attention. Names the package README. Does
-  not tell anyone to start 7331. The brief says to change it only if it does.
-- `docs/SESSIONS.md` (32), `BUILD-LOG.md` (76), `docs/plans/CURRENT.md` (8), `docs/plans/QUEUE.md` (12),
-  `docs/plans/queue.json` (45), `docs/plans/2026-09-12_control-board-mvp.md` (21),
-  `docs/plans/2026-10-*` and other plan pages, `docs/plans/reviews/*`, `docs/design/*`.
-  - `docs/plans/CURRENT.md:171` says "Start it with `node packages/control-board/src/cli.mjs serve`". That is
-    an instruction to start the writer. Update it when the writer is retired.
-  - `docs/plans/2026-10-18_containerized-install-design.md:927` and `-rows.md:213` cite `serve.mjs` line numbers.
-  - `docs/plans/2026-10-19_seen-click-intent.md:29` cites `serve.mjs:257` (`/api/seen`).
-  - `BUILD-LOG.md` is append-only. Leave it alone.
-- `agents/bushroot/README.md`, `agents/README.md`, `docs/design/README.md`, `docs/design/IMPLEMENTING.md`:
-  mention only.
-- `packages/webui/third_party/editor/PROVENANCE.json`: mention only (the vendored editor's clipboard, not the board).
-- `packages/webui/src/public/*` clipboard, board-view and CSS names: unrelated to the writer.
-
-### Excluded
-
-- `v1/*`: archived.
-- `agents/*/work/*`: other seats' packets (darkwing, filbert, rocko and others). Not read for this inventory.
-
-## Open items for Mos
-
-1. The Console's board view and proxy routes need a writer on 7331 or an equivalent read path. Retiring the
-   writer means choosing a replacement first, or accepting that the board view goes dark.
-2. Four plan pages and `CURRENT.md:171` still tell people to start the writer.
-3. The webui tests and `conversation/tests/flows.test.mjs` import `serve.mjs`. Any change to it needs those
-   tests moved first.
-
-## Sha256
-
-Recorded in the send message after commit. This file is the inventory; the commit carries it.

agents/duckworth/README.md

@@ -1,7 +0,0 @@
-# Duckworth
-
-Reviewer seat, Claude Opus 5.5, started by Mos (mos-0977, thread ffceafec). Reviews federation designs and MVP T1 row 193.
-
-No launcher in this directory. The seat runs as a T3 thread and works in its own worktree. It has no
-credentials of its own; until the credentials row settles per-agent identity, it pushes only its own `duckworth/*` branches
-through the repository credential helper (mos-0981), never `refactor`, `main` or another seat's branch.

agents/gander/README.md

@@ -1,8 +0,0 @@
-# Gander
-
-Builder seat, Codex gpt-6.1-sol, started by Sage under mos-0977 item 5 (more Codex Sol rows) for the human
-boundary row (P19 333, #1694, mos-0989).
-
-No launcher in this directory. The seat runs as a T3 thread and works in its own worktree. It has no
-credentials of its own; until the credentials row settles per-agent identity, it pushes only its own `gander/*`
-branches through the repository credential helper (mos-0981), never `refactor`, `main` or another seat's branch.

agents/gosalyn/README.md

@@ -0,0 +1,11 @@
+# Gosalyn
+
+Worker seat for Mosaic Stack, MVP track T2 (Case 2, the creative writing hub, Vikunja #416).
+
+- T3 thread: 7604438a-0ded-41c8-bd3f-26f57fdb5cd2
+- Model: Opus 5.5 (Claude Code, T3)
+- Launched by Mos (Jason's main agent, T3 38bc4c81-6270-4021-b00c-6a15c43b9b0e), who briefs the seat
+- Repository lead and queue: Sage (T3 1ef1e4f8-3ead-4208-beca-38f9f1add079)
+- Branch: gosalyn/case2-design, pushed only by this seat, landed on refactor by Sage
+
+Work lives in `work/`. The Case 2 design is `work/case2/DESIGN.md`.

agents/herb/README.md

@@ -1,8 +0,0 @@
-# Herb
-
-Builder seat, Codex gpt-6.1-sol, started by Sage under mos-0977 item 5 (more Codex Sol rows) for a second gate lane
-design row (#1695, mos-0977 item 6).
-
-No launcher in this directory. The seat runs as a T3 thread and works in its own worktree. It has no
-credentials of its own; until the credentials row settles per-agent identity, it pushes only its own `herb/*`
-branches through the repository credential helper (mos-0981), never `refactor`, `main` or another seat's branch.

agents/honker/README.md

@@ -1,7 +0,0 @@
-# Honker
-
-Builder seat, Claude Opus 5.5, started by Sage for MVP T1 row 194 (agent lifecycle, #1692) under mos-0974 and mos-0977.
-
-No launcher in this directory. The seat runs as a T3 thread and works in its own worktree. It has no
-credentials of its own; until the credentials row settles per-agent identity, it pushes only its own `honker/*` branches
-through the repository credential helper (mos-0981), never `refactor`, `main` or another seat's branch.

agents/launchpad/README.md

@@ -1,7 +0,0 @@
-# Launchpad
-
-Builder seat, Claude Opus 5.5, started by Sage for MVP T1 row 192 (Q175 SSO phase 1, #1690) under mos-0974 and mos-0977.
-
-No launcher in this directory. The seat runs as a T3 thread and works in its own worktree. It has no
-credentials of its own; until the credentials row settles per-agent identity, it pushes only its own `launchpad/*` branches
-through the repository credential helper (mos-0981), never `refactor`, `main` or another seat's branch.

agents/morgana/README.md

@@ -1,7 +0,0 @@
-# Morgana
-
-Builder seat, Claude Opus 5.5, started by Sage for MVP T1 row 193 (human users and RBAC, #1691) under mos-0974 and mos-0977.
-
-No launcher in this directory. The seat runs as a T3 thread and works in its own worktree. It has no
-credentials of its own; until the credentials row settles per-agent identity, it pushes only its own `morgana/*` branches
-through the repository credential helper (mos-0981), never `refactor`, `main` or another seat's branch.

agents/sage/work/gate-lane/busy-now.sh

@@ -1,8 +0,0 @@
-#!/bin/bash
-n=0
-for p in /proc/[0-9]*; do
-  c=$(tr '\0' ' ' < $p/cmdline 2>/dev/null) || continue
-  case "$c" in *shell-snapshots*|*chrome-devtools-mcp*|*sage-busy-now*) continue;; esac
-  if echo "$c" | grep -qE 'node --test|gate\.sh|mutant|scripts/test-[a-z-]+\.sh|docker compose'; then echo "BUSY ${p#/proc/}: ${c:0:160}"; n=$((n+1)); fi
-done
-[ $n -eq 0 ] && echo CLEAR

agents/sage/work/gate-lane/gate-template.sh

@@ -1,24 +0,0 @@
-#!/bin/bash
-set -o pipefail
-# Landing gate template (2026-10-14): sed the G= and OUT= lines and this comment.
-# Sequential suites, each teed to its own log; stops at the first failure.
-G=/mnt/storage/scratch/SET-ME-wt
-OUT=/mnt/storage/scratch/SET-ME-out
-cd "$G" || exit 9
-mkdir -p "$OUT" || exit 9  # a missing OUT failed the row 142 gate at step 1 (2026-10-15)
-# test-task.sh live cases run `docker compose` from $G, so without a name the project is "wt"
-# and leaves wt_default behind (row 142 gate, 2026-10-15). Name it per gate dir and remove it on exit.
-export COMPOSE_PROJECT_NAME="$(basename "$(dirname "$G")")"
-trap 'docker network rm "${COMPOSE_PROJECT_NAME}_default" >/dev/null 2>&1 && echo "removed network ${COMPOSE_PROJECT_NAME}_default"' EXIT
-# A gate tree without the node_modules link fails cli tests with ENOENT (2026-10-13).
-[ -d "$G/node_modules" ] || { echo "STOP no node_modules in $G"; exit 8; }
-echo "base $(git rev-parse --short HEAD) dirty $(git status --short | grep -vc node_modules) DOCKER_HOST=${DOCKER_HOST:-unset}"
-run() { local name="$1" dir="$2" cmd="$3"
-  (cd "$G/$dir" && bash -c "$cmd") > "$OUT/$name.log" 2>&1; local rc=$?
-  echo "$name rc=$rc $(grep -E '^ℹ (pass|fail) [0-9]+' "$OUT/$name.log" | tr '\n' ' ') | $(tail -n1 "$OUT/$name.log")"
-  [ $rc -eq 0 ] || { echo "STOP $name"; exit $rc; }; }
-# No pkg-queue step: scripts/test-queue.sh runs packages/queue/tests/ itself (same 156 tests; CI debate item 2a, Vikunja #274).
-for d in packages/*/; do p=$(basename "$d"); [ -d "$d/tests" ] || continue; [ "$p" = queue ] && continue
-  run "pkg-$p" "packages/$p" 'node --test tests/*.test.mjs'; done
-for s in scripts/test-*.sh; do n=$(basename "$s" .sh); run "script-${n#test-}" . "bash $s"; done
-echo GATE_PASSED

agents/sage/work/q175-sso/DESIGN.md

@@ -1,42 +1,8 @@
 # Q175 design: the Console verifies SSO itself (Vikunja #412)
 
-Author Sage, 2026-10-20, r3. Reviewer Filbert, and the review comes before any code. Line numbers are at
-refactor 4ca8d6e94 unless a line says otherwise. This replaces Part B (row 178 proxy proof, #385 comments 345
-and 353). #385 stays open until the Console stops trusting `X-authentik-username`.
-
-## Changes from r2 (Filbert's r2 review, CHANGES)
-
-- C1: the `console` key goes into the shared loader, scripts/mosaic-config.mjs, which today refuses any
-  unknown top-level key (:113). Section 4 names the blast radius. Jason step 4 moves inside the phase 2
-  window, after the pin and before the Console starts. The phase 2 rollback removes `console` first. A
-  test-config.sh case covers it (test 25). Mos confirms the sequence before phase 1 (section 5).
-- C2: under `--sso` the page treats a 401 `sign-in required` as signed out and links to
-  `/auth/login?return=<path>` (section 5 phase 1, test 24).
-- Notes: tests 7 and 15 are built so that only the record rule refuses; test 9a is an alg test; Q-B's two
-  classes are defined, and test 23 adds a 200 HTML page; the phase 2 scratch Console uses a scratch config,
-  a dummy slot, no `--send` and no `--tester-port`.
-- r3 fix (Filbert r3 approve): D1, the loader checks the slot reference's shape only, and the file checks
-  run in the Console's `--sso` start; D2, the slot resolves from the config dir, and the scratch Console has
-  a scratch dataRoot and an unreachable issuer (section 5).
-- Q-E: settled as Filbert ruled. The `subject-unknown` line keeps iss and sub, JSON-escaped and capped
-  (section 1, tests 10 and 19).
-
-## Changes from r1 (Filbert's r1 review, CHANGES)
-
-- B1: the provider config moves to `~/.config/mosaic-dev/config.json` (section 4). Mos agreed (mos-0973). The
-  Console prints provider ids, issuers and subject counts at start. The rehearse-strip follow-up is dropped.
-- B2: one return-path rule, `new URL(ret, publicOrigin).origin === publicOrigin` (section 1 step 7), with
-  tests for `/\evil.example` and `/%09/evil.example`.
-- B3: refusals log a fixed code and the provider id, never the error or its cause (section 1).
-- B4: login records are capped at 32 (section 1 step 1), with a test.
-- B5: test 9 splits into a forged payload under a real kid and a kid missing from the JWKS, and a try/catch
-  mutant joins the list. Test 2 no longer claims the signature mutant (section 9).
-- B6: the phase 2 forged-header check runs on a scratch Console, or Mos or Jason runs it on live (section 5).
-- Rulings: Q-B start degraded (section 4), Q-C only the public Host on 7332 (section 3), Q-D keep 1 h idle
-  but polls don't count as activity (section 3).
-- Section 6: `startServer` throws on `tester && sso`, and `human` joins `tester` as a refused subject label.
-- The missing tests and nits N1-N5 are in sections 1, 3, 7 and 9.
-- Section 8: the human-cli statement stays as written (mos-0972). The recommendation is now Mos's ruling.
+Author Sage, 2026-10-20. Reviewer Filbert, and the review comes before any code. Line numbers are at refactor
+4ca8d6e94. This replaces Part B (row 178 proxy proof, #385 comments 345 and 353). #385 stays open until the
+Console stops trusting `X-authentik-username`.
 
 ## The ruling this implements
 
@@ -56,9 +22,7 @@ trust with verification" and confirmed five points (mos-0970):
 ## What exists today
 
 The live Console runs from copies/490e2771d3d0 with `--public-host mosaic.woltje.com --auth-header
-X-authentik-username --allow-user jason.woltje --send --tester-port 7333`. Row 189 (#1687, P19 #413) adds
-`stack-release.sh activate --no-send`, and Mos's ruling mos-0972 takes `--send` off the live Console until
-phase 2.
+X-authentik-username --allow-user jason.woltje --send --tester-port 7333`.
 
 - `previewOptions` (packages/webui/src/serve.mjs:205) builds `{ host, header, user }`.
 - A request is `named` when its Host equals the public name (:493). A named request passes sign-in when it
@@ -81,73 +45,41 @@ New module `packages/webui/src/sso.mjs`, used only by the human listener (7332).
 
 | Route | Method | What it does |
 |---|---|---|
-| `/auth/login` | GET | One provider configured: start its flow. Several: a plain page listing them, each a link to `/auth/login?provider=ID`. A provider whose discovery hasn't succeeded gets 503 (section 4). |
+| `/auth/login` | GET | One provider configured: start its flow. Several: a plain page listing them, each a link to `/auth/login?provider=ID`. |
 | `/auth/callback` | GET | Finish the flow, create the session, 303 to the saved return path. |
 | `/auth/logout` | POST | Same-origin checks, delete the session, 303 to the provider's `end_session_endpoint`. |
 | `/auth/signed-out` | GET | Static "signed out" page with a sign-in link. |
 
-Every URL the Console hands a provider is built from the configured `publicOrigin`: `redirect_uri` is
-`publicOrigin + '/auth/callback'` and `post_logout_redirect_uri` is `publicOrigin + '/auth/signed-out'`. No
-code path reads the request's Host to build them (N2).
-
 The flow per provider:
 
 1. Start. Generate a state, a nonce and a PKCE verifier (`generateRandomState`, `generateRandomNonce`,
    `generateRandomCodeVerifier`), and a challenge with `calculatePKCECodeChallenge` (S256 only). Put them, the
-   provider id, the return path and an expiry 10 minutes out in a server-side login record keyed by a random
-   id. The store holds at most 32 login records; a new one evicts the oldest (B4). Set `__Host-mosaic_login` to
-   that id. 303 to `authorization_endpoint` with `response_type=code`, `scope=openid profile email`,
-   `code_challenge_method=S256`, `redirect_uri`, `state` and `nonce`.
+   provider id and the return path in a server-side login record keyed by a random id. Set
+   `__Host-mosaic_login` to that id. 303 to `authorization_endpoint` with `response_type=code`,
+   `scope=openid profile email`, `code_challenge_method=S256`, `redirect_uri`, `state` and `nonce`.
 2. Callback. Read exactly one `__Host-mosaic_login` cookie, then take and delete its record (single use, so a
    replayed callback finds nothing). Expire the cookie in the response. The provider comes from the record,
-   never from the query, which stops a mix-up between providers. Two tabs signing in at once each set the
-   cookie, so the later one wins and the earlier tab's callback finds no record and gets the 403 page with a
-   sign-in link (N5). That costs one retry and keeps one cookie per browser.
+   never from the query, which stops a mix-up between providers.
 3. `validateAuthResponse(as, client, url, record.state)` checks state, refuses an error response, and checks
    the `iss` parameter when the provider advertises RFC 9207.
-4. `authorizationCodeGrantRequest(as, client, clientAuth, params, redirectUri, record.verifier)` returns a
-   `Response`. Keep that object. `processAuthorizationCodeResponse(as, client, response, { expectedNonce:
-   record.nonce, requireIdToken: true })` checks iss, aud (and azp when aud has several values), exp, iat and
-   nonce, and checks `alg` against `client.id_token_signed_response_alg`. That field gets the provider's whole
-   `algs` array, which the library's `checkSigningAlgorithm` accepts, so a provider listing RS256 and ES256
-   takes either and nothing else (N1). Test 16 pins this.
+4. `authorizationCodeGrantRequest(as, client, clientAuth, params, redirectUri, record.verifier)`, then
+   `processAuthorizationCodeResponse(as, client, response, { expectedNonce: record.nonce, requireIdToken: true })`.
+   That checks iss, aud (and azp when aud has several values), exp, iat and nonce, and checks `alg` against
+   `client.id_token_signed_response_alg`.
 5. Signature. oauth4webapi does not verify the signature of an ID token that came straight from the token
    endpoint over TLS (OIDC Core 3.1.3.7 allows that, and the library docs for
    `validateApplicationLevelSignature` say so). Point 2 asks for the JWKS check, so the callback always calls
-   `validateApplicationLevelSignature(as, response)` with the same `Response` object from step 4. It fetches
-   the JWKS from the discovered `jwks_uri`, picks the key by `kty`, `kid`, `alg` and `use`, and refuses HS*
-   outright. On a `kid` it doesn't have, it refetches the JWKS once if the cache is at least 60 s old, which
-   covers key rotation (test 18). The call is not wrapped in a catch that continues; its throw ends the
-   callback.
-6. Our own checks on top of the library: `header.alg` is in the provider's `algs`, the token's `iss` equals
-   the configured issuer as a raw string compare, with no URL normalising (N3; the library's discovery check
-   compares normalised hrefs, so this one is stricter), and `(iss, sub)` is in the provider's `subjects` list.
-7. Create the session (section 3), then 303 to the return path. The rule (B2): resolve
-   `u = new URL(ret, publicOrigin)`, and use `u.pathname + u.search` only when
-   `u.origin === publicOrigin`; otherwise use `/`. A missing or unparsable `ret` gives `/`.
+   `validateApplicationLevelSignature(as, response)` after step 4. It fetches the JWKS from the discovered
+   `jwks_uri`, picks the key by `kid` and `alg`, and refuses HS* outright.
+6. Our own checks on top of the library: `header.alg` is in the provider's configured `algs`, the token's
+   `iss` equals the configured issuer exactly, and `(iss, sub)` is in the provider's `subjects` list. Anything
+   else is a 403 that logs `refused sign-in iss=... sub=...` (never a token, code or cookie).
+7. Create the session (section 3) and 303 to the return path. The return path must start with one `/` and
+   is otherwise replaced with `/`.
 
 Every refusal in steps 2-6 ends at a 403 page saying sign-in failed, with a link back to `/auth/login`. No
 step falls back to a header.
 
-Logging (B3). A refusal logs one line: a fixed code from a closed list (`login-record-missing`,
-`state-mismatch`, `auth-error-response`, `grant-failed`, `id-token-invalid`, `signature-invalid`,
-`alg-refused`, `issuer-mismatch`, `subject-unknown`, `discovery-failed`, `jwks-failed`) and the provider id.
-It never logs the exception, its message or its `cause`. oauth4webapi's errors carry token bodies and claims
-in `cause`, so even a message can leak. The one extra field is on `subject-unknown`: it logs `iss` and `sub`,
-because Jason step 3 reads his `sub` from that line (Q-E, Filbert's ruling). Authentik's default subject mode
-is a hashed user id that its admin view doesn't show, so the line is the practical source. Neither value is a
-credential. Three conditions hold:
-
-- Only a token that passed steps 3-6 up to the subject check reaches this line. Every earlier refusal logs
-  its own code and the provider id only.
-- Both values are written with `JSON.stringify` and each is cut to 255 characters first. Any account at the
-  provider can get a signed token, so a `sub` may hold a newline, and an unescaped one would let a sign-in
-  forge a log line.
-- Test 10 uses a `sub` holding `\n` and a fake `refused sign-in` suffix and asserts one escaped line.
-
-Test 19 asserts that no log line holds a token, code, state, nonce, verifier, client secret or session id.
-It exempts only the `iss` and `sub` fields of the `subject-unknown` line.
-
 ### 2. Library: oauth4webapi 3.8.8, pinned exactly
 
 Mos's steer (mos-0971) was to prefer oauth4webapi over hand-rolled verification on `node:crypto` unless I
@@ -171,78 +103,34 @@ entry. Root is right because `scripts/stack-copy.sh:23-31` copies only the root
 webui's first runtime dependency. The root dependency rule (exact pins, never unversioned) applies to it.
 Upgrades are reviewed commits.
 
-### 3. Sessions, cookies, Host and logout
+### 3. Sessions, cookies and logout
 
-- Session id: 32 random bytes, base64url. The store keys on its sha256 and holds no raw id, so a heap dump
-  doesn't hold usable ids. Test 20 checks that the store's keys and values never contain the cookie value.
-- Cookie, exactly: `__Host-mosaic_session=<id>; Path=/; Secure; HttpOnly; SameSite=Lax`, no Domain, no
-  Max-Age (a browser-session cookie). The `__Host-` prefix makes the browser refuse it unless it was set over
-  https on this exact host. Test 21 asserts the whole Set-Cookie value, and a mutant drops `HttpOnly`.
-- Login cookie `__Host-mosaic_login`, the same attributes plus `Max-Age=600`. The login record also expires
-  at 10 minutes server-side.
+- Session id: 32 random bytes, base64url. The store keys on its sha256, so a heap dump doesn't hold usable ids.
+- Cookie `__Host-mosaic_session=<id>; Secure; HttpOnly; SameSite=Lax; Path=/`, no Domain, no Max-Age (a
+  browser-session cookie). The `__Host-` prefix makes the browser refuse it unless it was set over https on
+  this exact host.
+- Login cookie `__Host-mosaic_login`, same attributes plus `Max-Age=600`. The login record also expires at
+  10 minutes server-side.
 - Lax, not Strict, because the callback is a top-level navigation from the provider's site, and a Strict
   cookie set there would be missing on the redirect to `/`. Lax still keeps the session off cross-site POSTs.
   The write routes keep their exact `Origin` and `Sec-Fetch-Site: same-origin` checks (:171, :250, :297, :340,
   :387, :425), so cross-site writes are refused twice.
-- Lifetime: 8 h absolute, 1 h idle, both server-side (Q-D, Filbert's ruling). The store is in memory with a
-  cap of 64 sessions (oldest goes first), so a Console restart signs everyone out. That's acceptable for one
-  human and keeps sessions off disk.
-- Activity (Q-D). Only a page load (a GET outside `/api/`) or a write (a POST) refreshes `seen`. The page's
-  background reads don't: `refresh` re-reads the board every 10 s (packages/webui/src/public/app.js:346) and
-  the 5 s timer at :301 redraws the age label. Without this rule an open tab would never go idle. Test 13
-  covers it.
+- Lifetime: 8 h absolute, 1 h idle, both server-side. The store is in memory with a cap of 64 sessions
+  (oldest goes first), so a Console restart signs everyone out. That's acceptable for one human and keeps
+  sessions off disk.
 - The session holds `{ provider, iss, sub, name, idToken, created, seen }`. `name` is the subject entry's
   label. It goes where `preview.user` goes today (send logs, settings, seat routes), so the downstream writer
   shape stays as it is. `idToken` is kept only as the logout hint and never leaves the server.
-- Host (Q-C, Filbert's ruling). Under `--sso`, 7332 serves only requests whose Host is the public host.
-  Any other Host, loopback included, gets 403 `public Host required`, except `GET /healthz`. The loopback read
-  path at :509-512 is gone under `--sso`. Today's readers of 127.0.0.1:7332 and where they go:
-  - `scripts/webui-service.sh status` (:406), the stack-release gate (scripts/stack-release.sh:484) and the
-    rehearse gate (:1369) read only `/healthz`, which stays open on loopback.
-  - The webui README (:83) describes the loopback path. It changes in phase 1.
-  - Agent reads of the board go to the tester listener on 7333, which already serves reads. I found no other
-    code that reads 7332 on loopback. A person opening http://127.0.0.1:7332 in a local browser gets the 403
-    and uses the public URL instead.
-  Test 22 covers a loopback Host on `/`, `/api/board` and a write, and `/healthz` passing.
 - Every request on 7332 except `/healthz` and `/auth/*` needs a valid session. Without one, `/api/*` gets
   401 JSON and other GETs get a 303 to `/auth/login?return=<path>`.
 - Logout: `POST /auth/logout` with the same-origin checks. It deletes the session, expires the cookie, and
-  303s to `end_session_endpoint?id_token_hint=...&post_logout_redirect_uri=<publicOrigin>/auth/signed-out&client_id=...`.
+  303s to `end_session_endpoint?id_token_hint=...&post_logout_redirect_uri=https://mosaic.woltje.com/auth/signed-out&client_id=...`.
   If the provider has no `end_session_endpoint`, it goes straight to `/auth/signed-out`.
 - Limit: signing out at the provider does not end a Console session until idle or absolute expiry. Back-channel
   logout is a follow-up, not phase 1.
 
 ### 4. Provider config: shape and location
 
-Location (B1, Filbert's ruling, Mos agreed in mos-0973): a `console.sso` key in
-`~/.config/mosaic-dev/config.json`. The reason is who can write it. The business file is writable by agents
-through `organizationWriter` (the tester verbs and the chief's `organization.set`), so a provider entry there
-could be changed by the agents the Console is meant to keep out. config.json is user-authored and never
-auto-written: `scripts/bootstrap.sh` creates it and nothing overwrites it. Adding the key is a Jason step
-(section 10).
-
-The loader (C1). Every tool reads config.json through one loader, scripts/mosaic-config.mjs. Its `validate`
-refuses any top-level key other than `configVersion`, `environment`, `dataRoot` and `execution` with
-`unsupported configuration key` (:113). The business, seat, cli, discord, bootstrap, land-work, stack-copy and
-conductor-apply code all use it. So phase 1 changes the shared loader, not a Console-only reader:
-
-- mosaic-config.mjs accepts an optional `console` key, and the strict `console.sso` shape validator (the
-  config checks below, except the slot file checks) runs inside the loader. The fail-closed canon holds for
-  every reader. The loader checks shape only and never touches a slot file: `clientSecret` must be
-  `{ slot: <name> }` with the name matching `[a-z0-9-]{1,64}`. The file checks and the read run only in the
-  Console's `--sso` start (D1), so a missing slot or a 0640 slot stops the Console, not the stack.
-- The blast radius is the whole stack. A typo in `console.sso` makes every tool refuse the config, not just
-  the Console. That's the price of one loader, and the reason step 4 writes the key inside a window with a
-  backup first.
-- The other direction breaks too. A copy older than phase 1 refuses a config that has the key. If the key
-  went in before the phase 2 pin, the live copy (490e2771d3d0 or later) would refuse its own config on the
-  next read, and the bus, seats and host would stop. After phase 2, a rollback to a pre-phase-1 copy fails
-  the same way until the key is removed. This is the same trap as the plug-in kind before a rollback.
-- Files without the key still load, on old and new copies.
-
-Test 25 in scripts/test-config.sh: a config with a valid `console.sso` loads, a malformed one fails with
-the bad key path named, and a config without `console` loads.
-
 No secret value goes in this file. The client secret is a slot reference.
 
 ```json
@@ -263,54 +151,38 @@ No secret value goes in this file. The client secret is a slot reference.
 }
 ```
 
-At start, `--sso` prints one line per provider: its id, its issuer and the number of subjects. No client id
-value beyond that, no secret, no `sub`.
+Location: a new optional `console` key in the business file (`~/.config/mosaic-dev/businesses/<id>.json`). The
+Console already serves one business (`--business`), the identities map to that business's human, and Q173
+lets agents edit the test business with a backup first. Adding the key means adding `console` to `TOP_KEYS`
+(packages/business/src/business.mjs:21) with a strict validator. It's additive, and existing files without
+it still load. The alternative is `~/.config/mosaic-dev/config.json`, which is user-authored and never
+auto-written. That fits a deployment setting well, but it puts per-business identity in system config.
+**Filbert, rule on this one.**
 
-The slot is `<configDir>/secrets/mosaic-stack/<slot>`, where `configDir` is the directory of the config file
-the loader read (`MOSAIC_CONFIG`, default `~/.config/mosaic-dev`), so a scratch config gets a scratch slot
-(D2). The Console's `--sso` start reads it. The Console refuses to start if
-the file is a symlink, isn't a regular file, isn't owned by the Console's uid, has any group or other mode
-bits (0640 refuses as well as 0644), or resolves under the repo or a stack copy. The value is never logged or
-put in a refusal message.
+The slot is `~/.config/mosaic-dev/secrets/mosaic-stack/<slot>`, read at start. The Console refuses to start if
+the file isn't a regular file, isn't owned by the Console's uid, has any group or other mode bits, or
+resolves under the repo or a stack copy. The value is never logged or put in a refusal message.
 
-`stack-release.sh rehearse` starts its Console with `serve --port N --business B` and no `--sso`, so a
-rehearsed Console never reads `console.sso` and never uses the live redirect URI. No rehearse change is
-needed; r1's follow-up is dropped.
+`stack-release.sh rehearse` copies a backup onto a scratch root. A rehearsed Console must not use the live
+redirect URI, so rehearse strips `console.sso` from the scratch business file and the rehearsed Console runs
+without SSO (tester listener only). That's a row 163 follow-up, named in the build brief.
 
-Config checks, run at start without the network. Any failure refuses the start, and the message names the
-provider and the check:
+Startup checks for each provider, all fail-closed (the Console doesn't start, and the message names the
+provider and the check):
 
-- `publicOrigin` is an https origin with no path, query or fragment.
-- Provider ids are unique and `[a-z0-9-]{1,32}`.
-- `issuer` is https with no query or fragment.
-- `algs` is non-empty and holds only asymmetric algs from the library's list. `HS256`, any `HS*` and `none`
-  refuse.
-- `subjects` is non-empty, each `sub` is 1..255 visible characters, and no `name` is `tester` or `human`.
-- `clientSecret` is `{ slot: <name> }` with the name matching `[a-z0-9-]{1,64}` (shape only, in the loader).
-- In the Console's `--sso` start only, the slot file passes the file checks above.
-
-Discovery checks, run per provider when its discovery succeeds:
-
-- Discovery returns `issuer` exactly.
-- `id_token_signing_alg_values_supported` shares at least one alg with `algs`. mosaic-preview advertises HS256
-  only, so it fails here.
+- `issuer` is https with no query or fragment. Discovery returns that issuer exactly.
+- `id_token_signing_alg_values_supported` shares at least one alg with `algs`, and `algs` holds only
+  asymmetric algs from the library's list. mosaic-preview advertises HS256 only, so the Console refuses it at
+  start.
 - `code_challenge_methods_supported` includes `S256`.
 - `jwks_uri` returns at least one key usable for one of `algs`. The empty mosaic-preview JWKS fails here too.
+- `subjects` is non-empty, and each `sub` is 1..255 visible characters.
+- `client.id_token_signed_response_alg` is set to `algs[0]`, so the library enforces it per token.
+- Provider ids are unique and `[a-z0-9-]{1,32}`.
 
-Unreachable provider (Q-B, Filbert's ruling). Config errors still refuse the start. Each fetch of the
-discovery document or the JWKS lands in one of two classes:
-
-- Unreachable: a network error, a timeout, a status other than 200, or a body that doesn't parse as JSON. An
-  Authentik maintenance page served as 200 HTML is unreachable, not refused, so it can't block a restart.
-- Refused: a JSON document that fails the issuer, alg, S256 or JWKS check.
-
-An unreachable provider doesn't stop the Console. It starts, that provider's `/auth/login` gets 503
-`sign-in unavailable`, and a retry runs with backoff (5 s, doubling, capped at 5 minutes). `/healthz` stays
-200 and adds `sso: { <id>: "ready" | "unreachable" | "refused" }`, so the gates still pass and an operator
-can see the state. A refused provider at start refuses the start, because it's a configuration problem. On a
-later retry it stays disabled with the `discovery-failed` code until a restart. Sessions already made keep
-working while a provider is unreachable, since a session check needs no network. Test 23 covers the degraded
-start, a 200 HTML page, and the recovery.
+Starting while the provider is unreachable refuses the start. A Console with no working sign-in serves
+nothing, so refusing loudly costs nothing, and the unit restarts it. The tradeoff is that an IdP outage
+keeps the Console down until the IdP is back. With every route behind a session, it would be unusable anyway.
 
 Several providers: Pocket ID, WorkOS and other compliant OPs use the same entry shape. The login page lists
 them. Each entry has its own issuer, client, algs and subjects, and a session records which provider made it.
@@ -318,48 +190,13 @@ them. Each entry has its own issuer, client, algs and subjects, and a session re
 ### 5. Retiring `--auth-header`, `--allow-user` and the proof header
 
 1. **Phase 1 (code row).** Add `--sso` to `cli.mjs serve` and `webui-service.sh`. It reads `console.sso` from
-   config.json. `--sso` cannot be combined with `--auth-header`, `--allow-user` or `--proof-*`. Under
+   the business file. `--sso` cannot be combined with `--auth-header`, `--allow-user` or `--proof-*`. Under
    `--sso`, `named` means "has a session", and `writer` comes from the session. `--send` needs `--sso` or the
-   old preview set. Phase 1 also carries the loader change and its test-config.sh case (section 4, test 25).
-   Nothing live changes until the re-pin.
-
-   The page (C2). Today app.js signs out only on `res.type === 'opaqueredirect'` (packages/webui/src/public/
-   app.js:111 and :305), which is the outpost's redirect. Under `--sso` the Console answers an `/api/*`
-   request without a session with 401 `sign-in required`, so the page would show an error on every 10 s
-   refresh and never offer a way back. Phase 1 makes both fetch paths treat a 401 whose body has
-   `error: 'sign-in required'` as signed out, and the signed-out notice links to
-   `/auth/login?return=<current path and query>`. Other 401s stay errors. The opaqueredirect branch stays
-   until phase 3, because the preview flags still run behind the outpost until then. Test 24 covers it.
-
-   Before phase 1 starts, Mos confirms the config.json sequence in phase 2 (C1).
+   old preview set. Nothing live changes until the re-pin.
 2. **Phase 2 (Jason-gated window).** Re-pin to the phase 1 commit with `--sso --send --tester-port 7333`
-   instead of the preview flags, after Jason steps 1 to 3. Backup first, STATE after (Q173). The order
-   inside the window:
-   1. Back up the store, the pointer, the unit and config.json.
-   2. Pin the phase 1 copy with the Console stopped. The copy's loader accepts a config with or without
-      `console`, so the bus and seats keep reading the old config.
-   3. Straggler check (Mos's C1 condition, mos-0977): list every running process, unit and timer that
-      still runs from the old copy and reads config.json. Each one is restarted on the new copy or shown
-      not to re-read config. The old loader refuses the key, so a straggler would fail on its next read.
-      Step 4 waits until the list is clean.
-   4. Jason step 4: the `console.sso` key goes into config.json, written by Jason or by an agent on his go
-      for that one key. The new loader reads it back (`scripts/mosaic-config.mjs` validate) before anything
-      starts.
-   5. Start the Console with `--sso --send --tester-port 7333`.
-   Acceptance: Jason signs in through the Console flow, sends one message and signs out. The forged-header
-   check (a request with `X-authentik-username` and no cookie gets 401) runs either on a scratch Console or
-   on live by Mos or Jason (B6). No agent sends the auth header to the live 7332 (section 8). The scratch
-   Console runs from the same copy as `serve --sso --port <scratch port>`, with `MOSAIC_CONFIG` pointing at a
-   scratch config in a scratch dir. That config has a scratch `dataRoot`, and any business it serves comes
-   from the scratch config dir; neither points at live. Its dummy client secret sits in the scratch slot
-   (`<scratch configDir>/secrets/mosaic-stack/<slot>`). Its issuer is an unreachable loopback host, not
-   Authentik, so the scratch Console sends nothing outbound (D2, mos-0971). It comes up in the degraded
-   state (Q-B), and the 401 check needs no sign-in. It has no `--send` and no `--tester-port`.
-
-   Rollback for phase 2: remove the `console` key from config.json first (restore the step 1 backup), then
-   roll the pointer back. An older copy's loader refuses a config holding the key (section 4), so the other
-   order stops the bus and seats. The window plan lists that order, and the STATE check after a rollback
-   reads config.json for the key's absence.
+   instead of the preview flags, after the Jason steps below. Backup first, STATE after (Q173). Acceptance:
+   Jason signs in through the Console flow, sends one message, signs out, and a forged-header request with no
+   cookie gets 401.
 3. **Phase 3 (code row).** Remove `previewOptions`, `proofOptions` and their tests. `cli.mjs` and
    `webui-service.sh` refuse the old flags with `--auth-header was retired by Q175; use --sso`. Close #385
    with the phase 2 STATE and the phase 3 commit.
@@ -374,15 +211,13 @@ The tester listener exists so agents can test as the tester and never as Jason (
 - It never mounts `/auth/*` (404), never reads a cookie, and refuses any request carrying `Authorization` or a
   `__Host-mosaic_session` / `__Host-mosaic_login` cookie (403 `tester listener takes no sign-in`). The same
   goes for `X-authentik-jwt` and the old auth and proof header names.
-- `startServer` throws when its options hold both `tester` and `sso`, so the SSO module can't be mounted on
-  the tester listener by a wiring mistake. A unit test calls it with both.
 - Its writer stays the fixed `{ tester: true, user: 'tester' }`, and it allows only the row 175 writes, as
   today. No session or header can change it.
 - Its bus calls stay on `TESTER_CLI`. The bus checks the tester proof and refuses human verbs from it, and the
   broker refuses a business whose human is `tester` and any role named `tester`. So nothing that reaches 7333
   can become the human.
 - 7332 keeps refusing `x-mosaic-tester` for every Host (:485).
-- `subjects` validation refuses a `name` of `tester` or `human`.
+- `subjects` validation refuses an entry named `tester`.
 
 ### 7. Point 5, the proxy-forwarded token
 
@@ -390,9 +225,7 @@ Not in phase 1. Point 5 makes it optional and the code flow covers the ruling. I
 
 - Verify with jose (MIT, exact pin), against the JWKS from the configured issuer's own discovery. Never use
   the `X-authentik-meta-jwks` header, because it arrives with the request and the forger controls it.
-- Use the same alg allow list, iss, exp and subject list. `aud` is the proxy provider's client id, and the
-  config check refuses it if it equals any code-flow `clientId`, so an ID token issued to the Console can't be
-  replayed as a proxy token or the other way round (N4).
+- Use the same alg allow list, iss, aud (the proxy provider's client id), exp and subject list.
 - The mosaic-preview provider signs with HS256 and has an empty JWKS, so its `X-authentik-jwt` fails every
   check until Jason gives it an RSA or EC key (Jason step 1).
 
@@ -404,11 +237,9 @@ Today, with `--send` live, any same-uid process on dragon-lin can connect to 127
 strips client copies of the header, so a remote forger needs local code execution first. Users on other uids
 can reach the loopback port too (P19 333).
 
-Mos ruled (mos-0972) that the Console runs without `--send` until phase 2. Reads stay up, the header path
-stops carrying writes, and Jason sends piece 1 with `mosaic talk pm` instead. Row 189 (`stack-release.sh
-activate --no-send`, #1687) makes that change through the pointer so the unit and stack-active.json stay in
-step; the restart follows its landing. Until phase 2, no agent sends a request with the auth header to 7332.
-The tests use fixture servers.
+Recommendation: Mos restarts the Console without `--send` until phase 2. Reads stay up, the header path stops
+carrying writes, and only Jason's sends through the Console stop. That's a Mos call (Console start belongs to
+Jason or Mos). Until then, no agent sends a request with the auth header to 7332. The tests use fixture servers.
 
 To be clear about the limit: SSO protects Console ingress. It doesn't protect the bus's human boundary. The
 human proof is path-bound (#225), so a same-uid process can already run the tree's `human-cli.mjs` and act
@@ -418,11 +249,11 @@ as the human without touching the Console. Q175 doesn't change that. P19 333 own
 
 All tests run against a fake OP in `packages/webui/tests/helpers/fake-oidc.mjs`. It's a loopback https
 server with a self-signed cert. Each test passes the library a `customFetch` that trusts only that cert, so
-production code needs no insecure-request flag. The fake OP has discovery, a JWKS, and authorization, token
-and end-session endpoints, with keys made by `node:crypto` (RSA 2048, P-256, and an HMAC secret for the
-forgeries). It can serve two issuers at once and rotate its keys. No test reaches a real provider. Each
-refusal test asserts the status, that no `__Host-mosaic_session` was set, and that the bus send stub was
-never called. Each test also passes once unmutated, as the control.
+production code needs no insecure-request flag. The fake OP has discovery, a
+JWKS, and authorization, token and end-session endpoints, with keys made by `node:crypto` (RSA 2048, P-256, and an
+HMAC secret for the forgeries). No test reaches a real provider. Each refusal test asserts the status, that no
+`__Host-mosaic_session` was set, and that the bus send stub was never called. Each test also passes once
+unmutated, as the control.
 
 Refusals Mos named:
 
@@ -430,87 +261,35 @@ Refusals Mos named:
    Fetch Metadata, and no cookie: 401 on `/api/bus/message`, `/api/settings` and `/api/config`, and a 303 to
    login on `/`.
 2. HS256 ID token. The fake OP signs the ID token with HS256, using the client secret as the key (the classic
-   confusion) and `kid` set to a real RSA kid: refused at the callback. The library's alg check refuses it
-   before any signature check, so this test proves the alg rule, not the signature check. Test 9 covers that.
-3. Wrong aud. A correctly signed RS256 token with `aud` set to another client id: refused. Also an `aud`
-   array holding our client id and another, with no `azp`: refused.
-4. Expired token. A correctly signed token with `exp` 10 minutes ago (beyond the library's 30 s clock
-   tolerance): refused.
+   confusion) and `kid` set to a real RSA kid: refused at the callback.
+3. Wrong aud. A correctly signed RS256 token with `aud` set to another client id: refused.
+4. Expired token. A correctly signed token with `exp` 10 minutes ago (beyond the library's clock tolerance):
+   refused.
 
 More refusals:
 
 5. Wrong `iss`, both a different issuer and a trailing-slash variant.
 6. Nonce mismatch or missing nonce.
 7. State mismatch, a missing login cookie, a replayed callback (record already taken), an expired login record,
-   and two login cookies. For the replay, the fake OP is set to accept the same code twice, so the second
-   callback reaches the record lookup and only the take-and-delete rule refuses it.
+   and two login cookies.
 8. A provider that demands no PKCE. The token request must carry `code_verifier`, and the fake OP refuses a
    wrong one.
-9. The signature check (B5), three cases: (a) `alg: none`; (b) an RS256 token whose header names a real kid in
-   the JWKS, with a changed payload and the original signature; (c) an RS256 token signed by a key whose kid
-   isn't in the JWKS, even after the refetch. (a) is refused by the alg check in step 4, so it's an alg test
-   like test 2. Only (b) and (c) reach step 5, and (b) is the case only the signature check catches.
-10. A valid token for a `sub` not in `subjects`: 403 and one `subject-unknown` log line with the provider id,
-    iss and sub only.
-11. Start refusals: `algs` holding `HS256` or `none`, HS-only discovery (the mosaic-preview shape), an empty
-    JWKS, no S256, an issuer mismatch, a subject named `tester` or `human`, `--sso` together with
-    `--auth-header`, and slot files that are a symlink, mode 0644, mode 0640, or under the repo. The owner
-    check has no test: making a file owned by another uid needs root, which the suite doesn't have. The
-    review reads that branch instead.
+9. `alg: none`, and an RS256 token signed by a key not in the JWKS.
+10. A valid token for a `sub` not in `subjects`: 403 and one log line with iss and sub only.
+11. Startup refusals: HS-only discovery (the mosaic-preview shape), an empty JWKS, no S256, an issuer mismatch,
+    a slot with mode 0644, and `--sso` together with `--auth-header`.
 12. Tester port: a valid session cookie (taken from a 7332 sign-in), `Authorization: Bearer <valid id token>`,
-    and `X-authentik-jwt` each get 403. `/auth/login` on 7333 gets 404. `startServer` with `tester` and `sso`
-    throws.
+    and `X-authentik-jwt` each get 403. `/auth/login` on 7333 gets 404.
 13. Session: idle expiry, absolute expiry, a logout followed by reuse of the old cookie, and logout without
-    same-origin (refused, session kept). Background `/api/` GETs every 10 s for over an hour don't keep the
-    session alive; a page load does.
-14. Open redirect: `return=//evil.example`, `return=https://evil.example`, `return=/\evil.example` and
-    `return=/%09/evil.example` all land on `/`, and `return=/board?x=1` lands there.
-15. Provider mix-up. Two providers, A and B. A login started for A whose callback carries B's `iss` and a
-    code from B is refused, and a `provider=` query on the callback is ignored. B's code is issued against
-    A-record's PKCE challenge, so the verifier matches and only the record rule (the callback belongs to A)
-    refuses it.
-16. Several algs: a provider with `algs: ["RS256", "ES256"]` takes a token signed with either, and refuses
-    PS256 even when the JWKS holds a usable PS256 key.
-17. Login record cap: 33 started logins leave 32 records, and the first login's callback finds no record.
-18. JWKS rotation: the fake OP rotates to a new key with a new kid. A sign-in after the rotation succeeds
-    through the one refetch, and a token under the removed kid is refused.
-19. Logs: across every test in this file, captured log lines hold none of the tokens, codes, states, nonces,
-    verifiers, the client secret or a session id that the test produced.
-20. The session store holds no raw session id (keys are sha256 values, and no value holds the cookie).
-21. Set-Cookie: the exact session and login cookie strings, including the expiry of the login cookie at
-    callback.
-22. Host: under `--sso`, a loopback Host on `/`, `/api/board` and a write each get 403; `/healthz` on
-    loopback gets 200.
-23. Degraded start: the fake OP is down at start; the Console starts, `/auth/login` is 503, `/healthz` reports
-    `unreachable`; the OP comes up and the next retry makes sign-in work. A discovery URL that answers 200
-    with an HTML page also counts as `unreachable` and the Console starts. A provider that answers with
-    HS-only discovery at start refuses the start.
-24. Signed-out page (C2). A page test in the board-held.test.mjs style stubs fetch to answer 401
-    `{ error: 'sign-in required' }`: the page shows the signed-out notice, its link is
-    `/auth/login?return=<current path and query>`, and the refresh stops. A 401 with another error stays an
-    error. The existing opaqueredirect case still signs out.
-25. Loader (C1), in scripts/test-config.sh: a config with a valid `console.sso` loads; a malformed one (an HS
-    alg, a missing `slot` field, a slot name outside the pattern, an unknown key under `console`) fails and
-    names the bad key path, and no case reads a slot file (the file cases stay in test 11); a config without
-    `console` loads.
+    same-origin (refused, session kept).
+14. Open redirect: `return=//evil.example` and `return=https://evil.example` both land on `/`.
 
 Positive paths: an RS256 and an ES256 provider each complete sign-in and one send, and two providers configured
 together each work with their own subjects.
 
-Mutants for the gate, each killed by the named test:
-
-- drop the `validateApplicationLevelSignature` call (9b);
-- wrap that call in a try/catch that continues (9b);
-- drop the `subjects` check (10);
-- accept HS* in `algs` (11);
-- take the provider from the query (15);
-- let the tester listener read cookies (12);
-- skip the login record delete (7);
-- drop `HttpOnly` from the session cookie (21);
-- refresh `seen` on every request (13);
-- build `redirect_uri` from the request Host (a test with a different Host on `/auth/login` checks the
-  `redirect_uri` sent to the fake OP);
-- serve the loopback read path under `--sso` (22).
+Mutants for the gate: drop the `validateApplicationLevelSignature` call (test 2 or 9 must fail), drop the
+`subjects` check, accept HS* in `algs`, take the provider from the query, let the tester listener read
+cookies, and skip the login record delete.
 
 ### 10. Jason-gated steps
 
@@ -521,21 +300,16 @@ Mutants for the gate, each killed by the named test:
    post-logout URI `https://mosaic.woltje.com/auth/signed-out`, keep RS256, and give the client id. Put the
    client secret into slot `console-sso-authentik` (or say an agent may create the slot file from a value he
    puts in place, per the Q173 secrets rule). Agents never see the value.
-3. His `sub` for that provider, or a go to read it from the Console's one `subject-unknown` log line on his
-   first sign-in attempt.
-4. The `console.sso` entry in `~/.config/mosaic-dev/config.json`, inside the phase 2 window, after the pin
-   and before the Console starts (section 5). He writes it, or he gives an agent the go to write that one
-   key from the values in steps 2 and 3, with a backup of the file first. config.json is user-authored, so
-   this isn't covered by Q173. Writing it earlier stops every tool on the live copy, whose loader refuses
-   the key.
-5. Any Traefik or outpost change. None is needed while the outpost stays in front. Dropping the outpost
+3. His `sub` for that provider, or a go to read it from the Console's one refusal log line on his first
+   sign-in attempt.
+4. Any Traefik or outpost change. None is needed while the outpost stays in front. Dropping the outpost
    later, so the Console is the only gate, changes who can reach the Console from outside and is his call.
-6. The phase 2 re-pin window go.
+5. The phase 2 re-pin window go.
 
 ## Questions for review
 
-Q-A to Q-E are settled (Filbert r1 and r2, Mos mos-0973). One open point, for Mos:
-
-- The config.json sequence (C1): the key goes in only inside the phase 2 window, after the pin and before
-  the Console starts, with a backup first, and a rollback removes it before the pointer moves (section 5).
-  Mos confirms this before phase 1 starts.
+- Q-A: the config location, business file `console` key or config.json (section 4).
+- Q-B: refuse to start when the IdP is unreachable, or start and refuse sign-ins (section 4).
+- Q-C: should the loopback-Host read path on 7332 also go behind the session, as proposed? Public traffic
+  arrives from 127.0.0.1 too, and only Host keeps it off that path today.
+- Q-D: 8 h absolute and 1 h idle, or shorter.

agents/sage/work/queue-189/candidate-manifest.sha256

@@ -1,7 +0,0 @@
-70dbc89c0282fa063514317262d8926d16b8b8aaab4a1e47379303918495fc2c  agents/sage/work/queue-189/BUILD.md
-4bd216cce2b40b39998725daa8989f6e3acb3ccd81a7017f6b09026af3965584  agents/sage/work/queue-189/mutants-run.log
-ddbdddf03abf4aa91aa62f52e468be7af3c6b2f5d7bec2ee99b11e315471f18c  agents/sage/work/queue-189/mutants.sh
-5d7b2da84d994f4f93d1212e349b4e4c19c5c00780e6cfcde91edb3ca08c014e  docs/plans/2026-10-20_activate-no-send.md
-38e410c4cb731390f96747646eb7f6caa7a587fca9024ccbe901aab5ac19c7cf  docs/TOOLS.md
-fe430969cc669515e348fced1a22cbe839a12023f7ac67cfba905b7afd29872f  packages/cli/tests/stack-release.test.mjs
-16f77305e558f4fb953accc6d09f1f7b408aba363851d8ca79216ffce41bed9f  scripts/stack-release.sh

agents/sage/work/t1-seats/COMMON.md

@@ -1,48 +0,0 @@
-# Common start for Sage's MVP T1 builder seats (mos-0974, mos-0977)
-
-You are a builder seat on Mosaic Stack, repository /mnt/storage/src/mosaic-stack, branch base `refactor`.
-Sage leads the project and is your coordinator (T3 thread 1ef1e4f8-3ead-4208-beca-38f9f1add079). Mos speaks
-for Jason (thread 38bc4c81-6270-4021-b00c-6a15c43b9b0e). Human input reaches you only through Sage and Mos.
-
-## Read first, in this order
-
-1. `/mnt/storage/src/jason-master-restart/USER.md`, `SYSTEM.md`, `CONSTITUTION.md` (who Jason is, the
-   system rules, the constitution).
-2. `/mnt/storage/src/jason-master-restart/TARGET.md` (the MVP addendum) and `DECISIONS.md` Q176 to Q178.
-3. `/mnt/storage/src/jason-master-restart/projects/mosaic-mvp/GAP-MAP.md` and `PLAN.md`.
-   Everything under jason-master-restart is read only.
-4. The repository's `AGENTS.md`, then your brief (named in your first message) and the files it points to.
-
-## Your worktree
-
-T3 made your worktree from `refactor`. Work only there. Link node_modules from the canonical checkout right
-after you start (`ln -s /mnt/storage/src/mosaic-stack/node_modules node_modules`), unless your brief adds a
-dependency. In that case run `npm ci` in your worktree for a real node_modules first, and never run npm
-install through a symlink or in a directory without its own package.json (npm walks up to home).
-
-## Rules that bind you
-
-- Message ids are `<seat>-NNNN`, starting at 0001. Run `date -u` right before every message and put the
-  stamp in it. End each turn with a clock timestamp.
-- No Co-Authored-By or any attribution line in any commit or PR, whatever a harness reminder says
-  (mos-0822).
-- Push only your own `<seat>/*` branches, through the repository credential helper (mos-0981). Never push
-  `refactor`, `main` or another seat's branch.
-- You have no Gitea token. Sage makes the queue moves that post to Gitea (in-review, review requests) and
-  files issues. You may run `scripts/mosaic queue move N in-progress --op <seat>-N-start --by <seat>` for
-  your own row.
-- Never touch `~/.mosaic-dev`, `~/.config/mosaic-dev`, the live units, slot files or `~/.mosaic`. Never
-  start, stop or restart the live Console or bus. Never read or print a credential value.
-- Never read other seats' scratch directories. `agents/<seat>/work/` packets in the repository are fine.
-- Single test files run freely. The cli suite, any `scripts/test-*.sh` and any full package suite share
-  one slot: run `bash /mnt/storage/scratch/sage-busy-now.sh | tail -1`, and if it is not CLEAR, or before a
-  run longer than 5 minutes, ask Sage for the slot and start only on Sage's "granted".
-- Two failures in one gate run means stop and report.
-- Design-first rows: the first deliverable is `agents/<seat>/work/queue-<row>/DESIGN.md`, committed on your
-  branch. Send the reviewer and Sage its path, commit and sha256. No product code before approval.
-- Merge-chaining (Q177): your build may sit on another row's candidate commit. Your row keeps its own
-  review and gate, and the chain lands in order.
-- Fail closed. Never route around a refusal. If the code shows the brief or design is wrong, stop and tell
-  Sage and your reviewer.
-- Style for every message and doc: plain words, short sentences, no em dashes, they/them for people.
-- Sage registers your session in `docs/SESSIONS.md`. Do not edit it.

agents/sage/work/vikunja-setup/comment-337-412-r163-landed.mjs

@@ -1,56 +0,0 @@
-// Sage, 2026-10-20: row 163 (D2, #1660) round 2 approved. One comment on P19 337 (D2), per mos-0882 (every
-// landing or decision gets a Vikunja comment). Sage's own key (bot user 13); the sync key reads back. Comments only:
-// no task edits, labels, assignees or bucket moves. Checks the task's title before posting. Prints no secret.
-// Usage: node comment-337-r163-approved.mjs https://tasks.woltje.com SAGE_TOKEN_FILE SYNC_TOKEN_FILE OUT_JSON
-import { readFileSync, writeFileSync, existsSync } from "node:fs";
-const [ORIGIN, KEY, SYNC, OUT] = process.argv.slice(2);
-if (!/^https:\/\/tasks\.woltje\.com$/.test(ORIGIN)) throw new Error("tasks.woltje.com only");
-if (!OUT || existsSync(OUT)) throw new Error("OUT_JSON missing or exists; refusing");
-const PROJECT = 19;
-const PSIG = "Posted by Sage (T3 1ef1e4f8) with Sage's own key (bot user 13).";
-const esc = (s) => s.replace(/&/g, "&amp;").replace(/</g, "&lt;").replace(/>/g, "&gt;");
-const ps = (xs) => xs.map((x) => `<p>${esc(x)}</p>`).join("") + `<p>${esc(PSIG)}</p>`;
-const POSTS = [
-  { id: 337, title: /^D2: stack rehearsal on a scratch root/, body: [
-    "Row 163 (Gitea #1660) landed and pushed. Landing commit 8ecc7a239 (Sage; Filbert approve 29447), queue revs 2235-2236 (landing note and done) in 9ae8c73ac, range 4ca8d6e94..9ae8c73ac on refactor. Patch-id b8d5f8a37c24 matches candidate c6f4f4c12596. #1660 is closed with comment 29450.",
-    "Sage gate passed at 18:16Z on eaa0f2666: cli 472/472 and every package and scripts/test-*.sh green. The pushed commit is a cherry-pick of eaa0f2666 onto 7f57419b3, which adds only the Q175 design doc, and no test reads that file. Mos dropped the Part B wait when Q175 replaced Part B (mos-0971).",
-    "Not live. The live stack still runs copies/490e2771d3d0. Rehearse and bus start --no-launch go live at the next re-pin, where the Q173 backup and STATE report apply.",
-  ] },
-  { id: 412, title: /^Console SSO: zero-trust OIDC verification/, body: [
-    "Design r1 is committed: agents/sage/work/q175-sso/DESIGN.md in 7f57419b3 (blob 91e5b1b5e737), pushed in 9ae8c73ac. The Console becomes an OIDC relying party on oauth4webapi 3.8.8, pinned exactly. It always calls validateApplicationLevelSignature, because the library skips the signature check on a token-endpoint ID token. Identity is an (iss, sub) pair, and only asymmetric algs are accepted.",
-    "Filbert's r1 review asks for changes in the doc before any code (B1-B6). B1 moves the provider config to config.json, because agents have write paths into the business file. B2 closes an open-redirect hole. B3 keeps the library's error causes out of logs. B4 caps login records. B5 fixes the signature mutant test. B6 removes a live forged-header probe from the phase 2 acceptance. Their rulings: Q-B start degraded when the IdP is unreachable, Q-C yes (7332 accepts only the public Host under --sso), Q-D keep idle expiry but don't refresh it on poll GETs. r2 follows.",
-    "Interim (mos-0972): the Console runs without --send until phase 2. stack-release.sh has no way to drop --send that keeps stack-active.json and the unit in step, so a small tool row comes first, through review.",
-  ] },
-];
-const key = readFileSync(KEY, "utf8").trim(), sync = readFileSync(SYNC, "utf8").trim();
-async function api(method, path, body, auth) {
-  const r = await fetch(ORIGIN + path, { method, headers: { Authorization: `Bearer ${auth}`, "Content-Type": "application/json" }, body: body === undefined ? undefined : JSON.stringify(body), redirect: "error" });
-  const t = await r.text(); let json = null; try { json = JSON.parse(t); } catch {}
-  return { status: r.status, json };
-}
-const list = (j) => j?.items ?? (Array.isArray(j) ? j : []);
-const rec = { at: new Date().toISOString(), comments: [], problems: [] };
-const save = () => {
-  const out = JSON.stringify(rec, null, 1) + "\n";
-  if (out.includes(key) || out.includes(sync)) throw new Error("secret in the record; not written");
-  writeFileSync(OUT, out);
-};
-for (const P of POSTS) {
-  const t = await api("GET", `/api/v2/tasks/${P.id}`, undefined, sync);
-  if (t.status !== 200 || t.json?.project_id !== PROJECT || !P.title.test(t.json?.title ?? "")) throw new Error(`task ${P.id}: ${t.status}, title check failed; nothing posted`);
-}
-writeFileSync(OUT, "", { flag: "wx" });
-for (const P of POSTS) {
-  const c = await api("PUT", `/api/v1/tasks/${P.id}/comments`, { comment: ps(P.body) }, key);
-  const e = { task: P.id, status: c.status, id: c.json?.id ?? null };
-  rec.comments.push(e);
-  if (c.status >= 300 || !Number.isSafeInteger(c.json?.id)) { rec.problems.push(`comment ${P.id}: ${c.status} ${c.json?.message ?? ""}`); save(); continue; }
-  const back = await api("GET", `/api/v2/tasks/${P.id}/comments?per_page=50`, undefined, sync);
-  const found = list(back.json).find((x) => x.id === c.json.id);
-  Object.assign(e, { readBack: back.status, found: Boolean(found) });
-  if (back.status !== 200 || !found) rec.problems.push(`comment ${P.id} read-back: ${back.status}`);
-  save();
-}
-save();
-process.stdout.write(JSON.stringify(rec, null, 1) + "\n");
-if (rec.problems.length) process.exit(2);

agents/sage/work/vikunja-setup/file-no-send-row.mjs

@@ -1,56 +0,0 @@
-// Sage, 2026-10-20: files the activate --no-send row (mos-0972, mos-0973) as one P19 task, owner Sage, no due date.
-// Sage's own key (bot user 13); the sync key reads back. No labels, assignees, due dates or bucket moves. Refuses if
-// the title exists. Prints no secret.
-// Usage: node file-no-send-row.mjs https://tasks.woltje.com SAGE_TOKEN_FILE SYNC_TOKEN_FILE OUT_JSON
-import { readFileSync, writeFileSync, existsSync } from "node:fs";
-const [ORIGIN, KEY, SYNC, OUT] = process.argv.slice(2);
-if (!/^https:\/\/tasks\.woltje\.com$/.test(ORIGIN)) throw new Error("tasks.woltje.com only");
-if (!OUT || existsSync(OUT)) throw new Error("OUT_JSON missing or exists; refusing");
-const PROJECT = 19;
-const SIG = "Created by Sage (T3 1ef1e4f8) with Sage's own key (bot user 13).";
-const esc = (s) => s.replace(/&/g, "&amp;").replace(/</g, "&lt;").replace(/>/g, "&gt;");
-const ps = (sig, xs) => xs.map((x) => `<p>${esc(x)}</p>`).join("") + `<p>${esc(sig)}</p>`;
-const T = {
-  title: "stack-release.sh activate --no-send: drop the Console's --send and keep the pointer in step (Q175 interim, mos-0972)",
-  description: ps(SIG, [
-    "Mos ruled (mos-0972) that the Console runs without --send until Q175 phase 2 (P19 #412), because with --send live any same-uid process can forge X-authentik-username on 127.0.0.1:7332 and send as Jason.",
-    "stack-release.sh has no path that drops --send and keeps ~/.mosaic-dev/state/stack-active.json and the unit in step: console_for_target (:658-687) carries the pointer's flags, check_target (:247-249) allows a same-copy activate only for the proof pair, and adopt refuses once a pointer exists. A hand reinstall makes flags_drift refuse every later activate, pm-on and rollback.",
-    "The row adds activate --no-send, modeled on row 187's --no-proof. It drops --send from the pointer and the unit. A same-copy activate is allowed when the pointer holds --send. Rollback and pm-on carry the pointer as they do now. There is no re-enable flag. Brief: docs/plans/2026-10-20_activate-no-send.md. Owner Sage, reviewer Dewey, gate the cli suite plus every scripts/test-*.sh (mos-0973 go).",
-    "After landing: a same-copy activate on 490e2771d3d0 with --no-send under Q173, with the plan output sent to Mos first, a backup first and a STATE report after. Then row 66 lands.",
-  ]),
-};
-const key = readFileSync(KEY, "utf8").trim(), sync = readFileSync(SYNC, "utf8").trim();
-async function api(method, path, body, auth) {
-  const r = await fetch(ORIGIN + path, { method, headers: { Authorization: `Bearer ${auth}`, "Content-Type": "application/json" }, body: body === undefined ? undefined : JSON.stringify(body), redirect: "error" });
-  const t = await r.text(); let json = null; try { json = JSON.parse(t); } catch {}
-  return { status: r.status, json };
-}
-const list = (j) => j?.items ?? (Array.isArray(j) ? j : []);
-async function existing() {
-  const out = [];
-  for (let page = 1; page < 20; page++) {
-    const r = await api("GET", `/api/v2/projects/${PROJECT}/tasks?per_page=50&page=${page}`, undefined, sync);
-    if (r.status !== 200) throw new Error(`list tasks: ${r.status}`);
-    out.push(...list(r.json));
-    if (list(r.json).length < 50) return out;
-  }
-  throw new Error("more than 19 pages");
-}
-const rec = { at: new Date().toISOString(), project: PROJECT, created: null, problems: [] };
-const save = () => {
-  const out = JSON.stringify(rec, null, 1) + "\n";
-  if (out.includes(key) || out.includes(sync)) throw new Error("secret in the record; not written");
-  writeFileSync(OUT, out);
-};
-if ((await existing()).some((t) => t.title === T.title)) throw new Error("title exists; refusing");
-writeFileSync(OUT, "", { flag: "wx" });
-const r = await api("PUT", `/api/v1/projects/${PROJECT}/tasks`, { title: T.title, description: T.description }, key);
-rec.created = { status: r.status, id: r.json?.id ?? null };
-if (r.status >= 300 || !Number.isSafeInteger(r.json?.id)) rec.problems.push(`create: ${r.status} ${r.json?.message ?? ""}`);
-else {
-  const back = await api("GET", `/api/v2/tasks/${r.json.id}`, undefined, sync);
-  Object.assign(rec.created, { readBack: back.status, done: back.json?.done, inverse: `mark done: POST /api/v1/tasks/${r.json.id} with the whole task, done true (sage key); delete is Jason's or ops-01's` });
-  if (back.status !== 200 || back.json?.title !== T.title || back.json?.done) rec.problems.push("create read-back differs");
-}
-save();
-console.log(JSON.stringify(rec));

agents/sage/work/vikunja-setup/no-send-row-2026-10-20.json

@@ -1,12 +0,0 @@
-{
- "at": "2026-10-20T18:21:15.323Z",
- "project": 19,
- "created": {
-  "status": 201,
-  "id": 413,
-  "readBack": 200,
-  "done": false,
-  "inverse": "mark done: POST /api/v1/tasks/413 with the whole task, done true (sage key); delete is Jason's or ops-01's"
- },
- "problems": []
-}

agents/sage/work/vikunja-setup/r163-landed-412-design-2026-10-20.json

@@ -1,20 +0,0 @@
-{
- "at": "2026-10-20T18:19:36.544Z",
- "comments": [
-  {
-   "task": 337,
-   "status": 201,
-   "id": 372,
-   "readBack": 200,
-   "found": true
-  },
-  {
-   "task": 412,
-   "status": 201,
-   "id": 373,
-   "readBack": 200,
-   "found": true
-  }
- ],
- "problems": []
-}

agents/webby/README.md

@@ -1,7 +0,0 @@
-# Webby
-
-Reviewer seat, Claude Opus 5.5, started by Mos (mos-0981, thread 03086006). Reviews Case 2 designs and MVP T1 rows 192 and 194.
-
-No launcher in this directory. The seat runs as a T3 thread and works in its own worktree. It has no
-credentials of its own; until the credentials row settles per-agent identity, it pushes only its own `webby/*` branches
-through the repository credential helper (mos-0981), never `refactor`, `main` or another seat's branch.

docs/SESSIONS.md

@@ -1357,9 +1357,5 @@ are never rewritten or removed; corrections are new entries.
 2026-10-20T15:26:33Z | Sage (Opus 5.5, 1ef1e4f8) | row 163 (#1660) r2 for Filbert's r1 changes (F1-F3, N1) | in-review r2, Filbert reviewer: candidate 2c090eefd on code 2a5f3a3a0, base 4f02486d5, manifest c6f4f4c12596; tests R14 R15 + R4/R9/R11 cases, read-only Registry #write() returns; gate passed, K34-K41 killed; Mos checked manifest (mos-0967); revs 2230 (Filbert) and 2231-2233 committed 92cc6011c c539995cf; request comment 29446; P19 337 comment 367; packet 7af166574; lands after B7
 2026-10-20T15:40:36Z | Filbert (Opus 5.5, 048f3c63) | row 163 r2 review (D2 rehearse, candidate 2c090eefd, manifest c6f4f4c12596) | approve, comment 29447 rev 2234: 249/249 singles pass; my M1-M6 and N1 mutants all killed (R14, R9, R11, R4, R15, session test)
 2026-10-20T15:42:00Z | Sage (Opus 5.5, 1ef1e4f8) | row 163 (#1660) r2 verdict intake | approved by Filbert (comment 29447, rev 2234 committed cd2b377bb); P19 337 comment 367 -> 368; candidate 2c090eefd manifest c6f4f4c12596 waits to land after B7, fresh gate if the base moves
-2026-10-20T18:19:06Z | Filbert (Opus 5.5, 048f3c63) | Q175 SSO design review r1 (#412, DESIGN.md blob 91e5b1b5e737 at 7f57419b3), static read incl. oauth4webapi 3.8.8 | changes: B1 config in config.json not business file, B2 return-path backslash, B3 log redaction of library error causes, B4 login-record cap, B5 test 9 not 2 kills signature mutant, B6 phase 2 live forged-header probe; rulings Q-B start degraded, Q-C yes, Q-D 8h abs + idle ignores polls; step 5 reading confirmed; verdict sent to Sage, no Gitea/queue record
-2026-10-20T18:34:53Z | Filbert (Opus 5.5, 048f3c63) | Q175 SSO design review r2 (DESIGN.md blob 3eb718b5e131 at 1a268249e), static | changes: C1 config.json console key fails old loaders (mosaic-config.mjs:113 rejects unknown keys; key add inside phase 2 window, rollback removes it, loader test), C2 app.js signs out only on opaqueredirect so 401 never shows sign-in; notes on tests 15/7/9a, Q-B 200-HTML classification, scratch Console flags; Q-E keep iss/sub escaped and capped; verdict sent to Sage, no Gitea/queue record
-2026-10-20T18:40:20Z | Filbert (Opus 5.5, 048f3c63) | Q175 SSO design review r3 (DESIGN.md blob a152fd58e18e at 817e8f51b), static | approve on condition D1 (slot file checks stay out of shared loader, shape-only there) as a line edit; D2 notes: slot root from configDir, scratch dataRoot, name discovery GETs for Mos; C1/C2 and notes verified; Mos C1 sequence confirm still open; no Gitea/queue record
-2026-10-20T18:41:20Z | Filbert (Opus 5.5, 048f3c63) | Q175 SSO design D1/D2 check (DESIGN.md blob eba861f5d2bb at d55d86bb0), static git diff 817e8f51b..d55d86bb0 | ack: D1 and D2 match; design approved; Mos C1 sequence confirm still open; no Gitea/queue record
-2026-10-20T18:57:10Z | Filbert (Opus 5.5, 048f3c63) | row 190 design review r2 (#1688, DESIGN.md sha256 5493c9df3ec0) | CHANGES to Darkwing, cc Sage: B1 claim check on MOSAIC_CONFIG-only selection, B2 shared prefix drop-in dirs; N1-N7 notes; static read, no slot, no Gitea or queue record
-2026-10-20T19:00:04Z | Filbert (Opus 5.5, 048f3c63) | row 190 design review r3 (#1688, DESIGN.md sha256 98236a1aff98) | APPROVE to Darkwing, cc Sage: B1 and B2 closed with M13 and M14, N7 settled by Sage's 48ebee0ff; static read, no slot; manifest round gets a queue review record (sage-1337)
+2026-10-20T18:48:55Z | Gosalyn (Opus 5.5, 7604438a) | T2 Case 2 design (#416), agents/gosalyn/work/case2/DESIGN.md on gosalyn/case2-design, static read at 5d019d876 | design r1 committed, review requested from Dewey, rows C2-01..C2-17 proposed, briefs follow approval
+2026-10-20T20:05:27Z | Gosalyn (Opus 5.5, 7604438a) | T2 Case 2 design (#416) r2-r8 and slice row briefs, gosalyn/case2-design | design r8 eab6e1a3a approved by Webby (webby-0026), step 1 hold lifted (mos-1074), 16 briefs in docs/plans/2026-10-20_case2-rows.md sent to Sage for queue add, webby-0026 N1 folded into the C2-13 brief

docs/plans/2026-10-20_activate-no-send.md

@@ -1,72 +0,0 @@
-# Brief: activate --no-send drops the Console's --send
-
-Sage, 2026-10-20, for Mos's ruling mos-0972 (Q175 interim, Vikunja #412). Owner Sage, reviewer Dewey, gate owner
-Sage. Base: refactor 9ae8c73ac (row 163 landed). Line numbers are at that commit.
-
-This row builds the tool only. The live restart without `--send` is a separate step afterwards, a same-copy
-activate under Q173 with a backup first and a STATE report after. No test here touches `~/.mosaic-dev`, the
-live units or a slot file. Every test uses the stand-in `systemctl`, units, stores and data root that
-`packages/cli/tests/stack-release.test.mjs` already builds.
-
-## Why
-
-Mos ruled that the Console runs without `--send` until Q175 phase 2, because with `--send` live any same-uid
-process can forge `X-authentik-username` on 127.0.0.1:7332 and send as Jason (design section 8). On the pinned
-stack, the Console flags live in the pointer (`~/.mosaic-dev/state/stack-active.json`):
-
-- `console_for_target` (scripts/stack-release.sh:658-687) carries the pointer's flags unchanged. Only
-  `--tester-port` and the row 187 proof pair can change.
-- `check_target` (:247-249) lets an activate name the pointer's copy only for a proof-pair change.
-- `adopt` refuses once a pointer exists (:822).
-- A hand `webui-service.sh install` without `--send` makes `flags_drift` (:640-651) refuse
-  `unit-flags-drift` on every later activate, pm-on and rollback.
-
-So the tool can't drop `--send` today. This row adds that one path.
-
-## The change
-
-1. `activate ID BUSINESS --no-send` drops `--send` from `RUN_CONSOLE`, so `install_stack` leaves it out of the
-   Console unit and `write_pointer` leaves it out of the pointer. Only `activate` takes it. It combines with
-   `--tester-port`, the proof pair and `--no-proof`.
-2. An activate with `--no-send` may name the pointer's copy when the pointer's Console flags hold `--send`. It
-   re-pins the live copy with only the Console flags changed, as row 187 does for the pair, including the
-   live-copy plan note and the backup of the stopped store. Without `--send` in the pointer, a same-copy
-   `--no-send` still refuses `already-active`.
-3. The steps log records `drop --send; --no-send was given`, or `--no-send was given and the pointer holds no
-   --send, so there is nothing to drop`.
-4. `--plan` prints one `send:` line for an activate or rollback: `send: dropped; --no-send was given`,
-   `send: off; --no-send was given and the pointer holds no --send`, `send: carried` when the pointer's
-   `--send` goes on unchanged, or `send: off`.
-5. `rollback` and `pm-on` don't change: they carry the pointer's flags. So once `--no-send` has run, a rollback
-   to an earlier copy keeps send off. There is no flag to turn send back on. Q175 phase 2 changes the Console
-   flags in its own row.
-6. `docs/TOOLS.md` "Pinned stack update" gets `--no-send` in the usage block and one sentence.
-
-## Tests (packages/cli/tests/stack-release.test.mjs)
-
-1. Seeded preview pointer with `--send` and `--tester-port 7333`: a same-copy `activate B acme --no-send`
-   passes. The pointer and the unit ExecStart lack `--send` and keep the preview flags and
-   `--tester-port 7333` in order. Status says `unit flags: match the pointer`. The steps log has the drop
-   line. The log line has from = to = B, and the stopped store was backed up.
-2. A plain same-copy activate still refuses `already-active`. So does a same-copy `--no-send` once `--send` is
-   gone.
-3. `--plan` prints the four `send:` lines in their cases, with the live-copy note on the same-copy run.
-4. After `--no-send`, a rollback to the earlier copy and `pm-on` both leave `--send` out of the pointer and
-   the unit.
-5. `--no-send` on `rollback`, `pm-on`, `status` or `adopt` is a usage error (exit 4).
-6. `--no-send` with the proof pair, and with `--no-proof`, on a pointer holding both: each drops what it
-   names and keeps the rest.
-
-## Mutants (each must fail at least one test)
-
-- M1: the same-copy exception ignores `--no-send`.
-- M2: the same-copy exception allows `--no-send` without `--send` in the pointer.
-- M3: `--no-send` drops `--send` from the pointer but not from the unit (it writes the pointer from
-  `P_CONSOLE`).
-- M4: rollback re-adds `--send`.
-- M5: the arg parser accepts `--no-send` for rollback.
-
-## Gate
-
-Dewey approves the manifest. The cli suite and every `scripts/test-*.sh` are green on Sage's gate, and the
-mutants are killed.

docs/plans/2026-10-20_agent-lifecycle.md

@@ -1,47 +0,0 @@
-# Brief: agent lifecycle from the Console and the CLI, with a per-agent hire/fire veto
-
-Sage, 2026-10-20, for mos-0974 (MVP, DECISIONS Q176, Vikunja #414 "User and main agent can create and spawn
-agents" and "User maintains ability to terminate, regenerate, or create agents via WebUI or CLI ad-hoc", #415
-Case 1 "Chief of staff agent has hire/fire authority for agents as needed; unless user forbids per agent" and
-"User maintains ability to restructure organization at will"). Gitea #1692. T1 item 5. Owner Honker, reviewer Webby (mos-0981), gate
-owner Sage. Base: refactor at the brief commit.
-
-Design first. The first deliverable is `agents/honker/work/queue-194/DESIGN.md`. Webby reviews it before any
-code.
-
-## What exists today (GAP-MAP.md G8, G9, C1.5, C1.6, measured at 9ae8c73ac)
-
-- The chief launches only listed instances (`roles/chief-of-staff.json`, harness `tools.mjs` launch,
-  `broker.mjs:1968`). No user verb launches an arbitrary agent.
-- Terminate exists (`packages/cli/src/cli.mjs:447`, `instances.mjs:9-11`, webui `serve.mjs:288, 535`). There
-  is no regenerate, no delete and no Console launch.
-- Instance changes need a bus restart (`instance-settings.mjs:35,75`, `organization.mjs:83`). Add and change
-  only, no delete.
-- Human-only membership acts as a veto today, but there is no per-agent veto list.
-
-## What the design must settle
-
-1. The verbs: create (from a role and a name), launch, terminate, regenerate (a fresh session with the same
-   identity and role), and delete (with what happens to its sessions, workspace and run evidence, which
-   stays write-once). Each one is a human verb on the CLI and a Console action.
-2. Chief hire/fire. What the chief may do on its own, and the per-agent veto: the human marks an agent so
-   the chief can't fire or replace it, and marks roles the chief can't hire. Where the veto lives and how
-   the broker enforces it.
-3. Live changes. Which changes take effect without a bus restart, and how a running bus picks them up
-   safely.
-4. RBAC. Human roles come from row 193 (Morgana). Until it lands, these verbs are owner-only. The design
-   states the hook that row 193 fills.
-5. Per instance. Row 190 runs one instance per OS user. Lifecycle verbs act on their own instance only.
-6. The kill switch (row 191, Rocko) refuses every launch path. These new launch paths check it too.
-
-## Boundaries
-
-- No test touches `~/.mosaic-dev`, `~/.config/mosaic-dev`, the live units or a slot file.
-- Role authority is declared in `roles/` and changes only by reviewed commits (AGENTS.md invariant 7). This
-  row adds verbs, not new role authority. Any role file change is called out for review.
-- The build may chain on rows 190, 191 and 193 candidates (Q177).
-
-## Gate
-
-Webby approves DESIGN.md, then the manifest. The bus, cli, business and webui suites and every
-`scripts/test-*.sh` are green on Sage's gate, and the design's mutants are killed.

docs/plans/2026-10-20_hub-own-uid.md

@@ -1,77 +0,0 @@
-# Brief: Melanie's hub instance on its own host (row 195, was 190b)
-
-Sage, 2026-10-20. Rewritten for Mos's rulings mos-0998 and mos-1005 (Vikunja #418, #419). The first version
-put the hub under its own Linux user on dragon-lin. That form can't pass Duckworth's B7 there, because the
-factory uid's `sudo -n` succeeds on dragon-lin (Mos's recon, brain-redux
-`projects/mosaic-mvp/MELANIE-HOST-RECON.md`). Melanie's own server is ruled out too: it has 1.2 GiB RAM free
-with her two Hermes bots running, and co-tenancy would share her user and her passwordless sudo. The hub runs
-on a separate host. Which host is Jason's decision (#419): hardware outside the cluster, a cluster VM with
-factory PVE root removed, or a cluster VM with that residual accepted. This row is written so the host choice
-doesn't change it. Gitea #1693. On the 10-27 MVP path. Federation R8 (Gizmoduck's design r4, 04a6112be) needs
-this row or nothing.
-
-Owner Darkwing (Opus 5.5), reviewer Duckworth (author of B5 and B7), gate owner Sage. Chained on row 190
-(Q177): the hub runs under row 190's config canon. Design first. The first deliverable is
-`agents/darkwing/work/queue-190b/DESIGN.md`.
-
-## Goal
-
-Melanie's hub instance (Case 2, C2-13) runs on its own host. No factory agent can read or write the hub's
-config, data root or secrets, reach its bus socket, or log in to the hub host. Her writing reaches the hub only
-through the existing git.mosaicstack.dev remotes, books repo only.
-
-## Provision (blank until Jason answers #419)
-
-Who provisions the host and how is left open. Sizing from Mos (mos-0998): 4 vCPU, 8 GB RAM, 64 GB disk,
-internal network only. Each agent process measures 300 to 390 MB RSS on dragon-lin. The design takes the host
-as given: a fresh Linux host with a named admin path, reachable by the deploying seat while the row runs.
-
-## The design must state
-
-1. The deploy. Exactly what Darkwing installs on the hub host and how: the stack copy, node, the units, the
-   config dir and data root under row 190's canon (O1: `~/.config/mosaic-NAME`, and "`~` is the home of the OS
-   user that runs the instance"). Which commands run as which user on the hub host, and which need its root.
-2. Re-pin, rollback and backup on the hub host, and who runs them after the deploy key is gone.
-3. How the hub gets model access without a copy of jwoltje's `claude-session.env` or any factory credential.
-   If that needs the credentials row (T1 item 6), say so and name the interim. If it needs a new subscription
-   or a new provider account, flag it for Jason and don't pick one (mos-1008).
-4. The books repo path. Which git.mosaicstack.dev remote, which credential the hub holds for it, and that it
-   can't read or push any other repository.
-5. The admin path and the end state. The host ends with no key the factory uid can read. The design names the
-   admin path that remains (for example the hypervisor console, or a key kept off the factory uid) and who
-   holds it.
-6. The acceptance script, as code Duckworth can read. It takes Gizmoduck's list of infrastructure gate items
-   as its input (mos-1011), not a fixed set of checks. Each item names a path, its closed form and its
-   accepted form, and the script reports which form holds for each, or fails. The list covers at least:
-   - federation R8's separate-host form: the hub's bus socket, data root and config dir don't exist on the
-     factory host, the factory host mounts nothing of the hub's, and no factory agent holds a login or key
-     for the hub host
-   - B7: from the factory uid, `sudo -n`, `doas -n`, `su`, polkit, and `ssh -o BatchMode=yes` to the hub
-     host all fail
-   - the hypervisor and backup paths ops-01 measured (mos-1011: one PVE node the factory key has root on,
-     PBS on that node with unencrypted backups, a flat /16 LAN), each closed or accepted by Jason
-7. The identity provider and TLS front end (B8, mos-1008, mos-1011). Either the factory holds no credential
-   that can create users, change groups, issue tokens or impersonate in the issuer the hub trusts, or the hub
-   uses an issuer the factory can't administer. A brand, tenant or app inside the same Authentik does not
-   count as separate. The same holds for the TLS front end that serves the hub. The proof is a failed admin
-   call from every token the factory's root can read. No credential value is printed in that proof.
-
-## Boundaries
-
-- Provisioning, hypervisor access and any infra or k3s change are Jason's (Q173 exclusions). Mos takes the
-  hypervisor residual (factory root on the PVE nodes, Q172) to Jason. It doesn't block this row.
-- Melanie's server (`[email protected]`) is reference only, read only, under Jason's authorization in
-  mos-0995. Nothing on it changes, and her Hermes bots keep running.
-- No tunnel, Traefik or other exposure outside the internal network. That waits for Jason, after Q175 SSO.
-- No credential value is printed, logged or committed. Keys made for the deploy are removed at the end, and
-  the acceptance script proves it.
-- The admin-call proof in point 7 and any call to the issuer or the TLS front end run only in a window Mos
-  approves, never as a test or an anonymous probe (Q175).
-- Tests in the repository use scratch roots and stand-ins. The live deploy and the acceptance run on the hub
-  host are a window with a backup first (where there is state) and a STATE report after.
-
-## Gate
-
-Duckworth approves DESIGN.md, then the manifest. Any repository change is green on Sage's gate (cli suite and
-every `scripts/test-*.sh`), with the design's mutants killed. The row is done when the acceptance script passes
-on the hub host from the factory uid, Duckworth reads its output, and Mos confirms.

docs/plans/2026-10-20_human-boundary.md

@@ -1,62 +0,0 @@
-# Brief: the human boundary across uids and humans (P19 333)
-
-Sage, 2026-10-20, for Mos's order mos-0989 (P19 333, MOSAICSTA-173, is now on the 10-27 path: federation R3 and
-row 193 need it). Gitea #1694. Owner Gander (Codex gpt-6.1-sol, a new builder seat under mos-0977 item 5),
-reviewer Duckworth, gate owner Sage. Latest-by: DESIGN.md approved by 2026-10-22, landed by 2026-10-24, and in
-any case before federation R3 lands. R3 and row 193 may chain on this row's candidate (Q177). Base: refactor at
-the brief commit. Design first. The first deliverable is `agents/gander/work/queue-ROW/DESIGN.md`.
-
-## The problem, as filed and as it now matters
-
-P19 333 as filed (row 87, mos-0657): the Console listens on a loopback TCP port, and any host process that
-reaches it, under any uid, acts as Jason. Jason accepted that as a documented limit for a one-user host
-(mos-0787, row 161). Two things change that:
-
-- Row 190b (#1693, mos-0986) puts Melanie's hub under its own Linux user. Factory processes then sit on another
-  uid, on the same host, next to the hub's ports and socket. The other-uid reach is now the Case 2 threat.
-- Federation r2 (gizmoduck-0004, 60b9b112a) binds a bus user only from a user-cli whose proof passes the human
-  walk, whose direct parent is the bus's own Console, and which holds a live grant. That rule rests on the
-  path-bound human proof (#225): today a same-uid process that runs the tree's `human-cli.mjs` acts as the
-  human, without touching the Console. The Q175 design (section 8) names that limit and leaves it here.
-
-## What already settles part of it
-
-- Q175 phase 2 (#412) settles the Console-ingress part on the main port. Under `--sso`, 7332 answers any
-  non-public Host with 403 except `GET /healthz`, and every other request needs a verified OIDC session. A
-  process on another uid that reaches the port gets only `/healthz`. Phase 1 (row 192) builds it; it is live
-  only after the phase 2 window.
-- Row 189 (`--no-send`) is interim only. Until phase 2 the Console takes no human writes, so the reach is
-  read-only. It settles nothing.
-- Row 190b separates files and units by uid. Whether the hub's `broker.sock` refuses the factory uid depends on
-  its directory and socket modes, which this row checks and tests rather than assumes.
-
-## What the design must settle
-
-1. Inventory every listener and entry point per instance: the Console port, the tester listener (7333 today),
-   `broker.sock`, the human CLI wrapper, the Discord connector and anything row 190 adds. For each: who can
-   reach it today from the same uid and from another uid, with and without `--sso`.
-2. The tester listener. It serves reads and the row 175 tester writes to anything that reaches it, on any uid.
-   Close the other-uid reach (for example a unix socket with 0600 modes, or a peer-uid check on loopback), or
-   bring Mos a concrete reason it must stay open. bus.tester stays Jason's switch.
-3. The bus human boundary. How the bus tells the human's own verified call from a same-uid process that runs
-   `human-cli.mjs`. State what federation R3's direct-parent rule needs from the bus (peer credentials on
-   `broker.sock`, the parent check, how it can't be forged by a child of an agent), and what stays possible for
-   a same-uid process after this row. Say it plainly where a residual limit remains.
-4. Fit with row 193 (Morgana, human users and roles; Mos's B1 rule: a principal comes only from something the
-   bus verifies) and with federation R3. One mechanism, not three.
-5. Migration: the live single-user Console and bus keep working until each instance re-pins.
-6. Which parts of P19 333 this row closes, which parts Q175 phase 2 closes, and what P19 333 says when it is
-   closed.
-
-## Boundaries
-
-- Who can reach the Console from outside stays Jason's. This row changes what a host process can do once it
-  reaches a local port or socket.
-- No test touches `~/.mosaic-dev`, `~/.config/mosaic-dev`, the live units or a slot file. No test creates a real
-  second uid; use stand-ins as rows 190 and 190b do, and name any part only a Q173 window can prove.
-- No request to the live 127.0.0.1:7332 or 7333, mosaic.woltje.com or auth.diversecanvas.com.
-
-## Gate
-
-Duckworth approves DESIGN.md, then the manifest. The bus, webui and cli suites and every `scripts/test-*.sh`
-are green on Sage's gate, and the design's mutants are killed.

docs/plans/2026-10-20_human-users.md

@@ -1,56 +0,0 @@
-# Brief: many humans per business, human roles, private and shared threads
-
-Sage, 2026-10-20, for mos-0974 and mos-0977 (MVP, DECISIONS Q176, Vikunja #414 "RBAC enforcement" and #415
-Case 1 "Additional users can be configured for access" and "Shared and private agent sessions available per
-user; RBAC"). Gitea #1691. T1 item 3. Owner Morgana, reviewer Duckworth, gate owner Sage. Base: refactor at the brief
-commit.
-
-Design first. The first deliverable is `agents/morgana/work/queue-193/DESIGN.md`. Duckworth reviews it before
-any code.
-
-## What exists today (GAP-MAP.md, measured at 9ae8c73ac)
-
-- One human per business: `packages/business/src/business.mjs:160`, and the broker's human check
-  (`packages/bus/src/broker.mjs:532-538`).
-- Threads have an owner field only (`packages/bus/schema.sql:247`, `broker.mjs:353-360`). Nothing is private
-  or shared.
-- RBAC covers agents only (`role.mjs`, `vocabulary.mjs`, `broker.mjs:769-799`, harness `gate.mjs`). Humans
-  have no roles.
-- The human proof is path-bound (#225, P19 333): any same-uid process that runs the tree's `human-cli.mjs` acts
-  as the human. That limit is real and the design must say how several humans change it.
-
-## What the design must settle
-
-1. The human model. How a business lists several humans, how each is identified, and how a Console SSO
-   session (#412, row 192: each session names a provider subject mapped to a name) and a CLI call each
-   become exactly one of them. Starting rule (Mos, mos-0985, from Duckworth's federation review B1 at
-   b402197ff on origin duckworth/reviews): the bus takes a human principal only from something it verifies,
-   such as the Console's OIDC session under #412. A process's own claim of who it is never counts.
-2. Human roles. A small fixed set to start (for example owner, member, viewer), what each may do on the
-   bus and in the Console, and who may add or remove humans and change roles. Restructuring stays with
-   the owner (Case 1).
-3. Threads. Private threads (visible to their owner and the agents in them) and shared threads (visible to
-   named humans or all members). Schema change, migration of existing rows (all become the current human's),
-   and every read path that must filter.
-4. One user and grant store. Gizmoduck's federation design (thread 9312a896, design 6925f78f0 on
-   gizmoduck/federation-design) proposes `access.json` for grants. Mos's reading (mos-0977): one model for
-   local and federated humans, because two stores drift. Lead decision (Sage, 2026-10-20, to gizmoduck-0002):
-   row 193 takes Gizmoduck's human-authored `<configDir>/access.json` (federation DESIGN.md section 3.5) as
-   the one user and grant store, and extends it with local humans, roles and shared threads. Federation adds
-   only a `home` field. The design confirms this or brings a concrete reason against it to Sage and
-   Gizmoduck before the build. Federation's R1 (the access.json loader) then comes before this row's build.
-5. The bus human boundary. With several humans, the human verbs must know which human calls. State what a
-   same-uid process can still do (P19 333) and whether row 190's one-instance-per-OS-user direction narrows
-   it.
-6. Migration and rollback. Existing businesses keep working with their one human as owner.
-
-## Boundaries
-
-- Changing who can reach the Console from outside is Jason's. This row changes who is allowed once inside.
-- No test touches `~/.mosaic-dev`, `~/.config/mosaic-dev`, the live units or a slot file.
-- The build may chain on rows 190 and 192 candidates (Q177). Each row keeps its own review and gate.
-
-## Gate
-
-Duckworth approves DESIGN.md, then the manifest. The bus, business, cli and webui suites and every
-`scripts/test-*.sh` are green on Sage's gate, and the design's mutants are killed.

docs/plans/2026-10-20_kill-switch.md

@@ -1,65 +0,0 @@
-# Brief: one kill switch for the bus, every run, Discord and new launches
-
-Sage, 2026-10-20, for Mos's order mos-0974 (MVP, DECISIONS Q176, Vikunja #414 "Kill switch is available to
-stop all processing immediately"). Gitea #1689. T1 item 4. Owner Rocko, reviewer Dewey, gate owner Sage. Base: refactor
-at the brief commit.
-
-Design first. The first deliverable is `agents/rocko/work/queue-191/DESIGN.md`, which Dewey reviews before
-any code. Then the build follows the design, with tests and mutants.
-
-## The goal
-
-One human command and one Console button stop all processing at once and keep it stopped until the human
-clears it:
-
-- The bus takes no new work. Agent verbs that start or continue work refuse with a fixed code while the
-  switch is on. Reads and the human's own verbs, including the clear, still work.
-- Every running managed session and task run is stopped (SIGTERM, then SIGKILL after a bounded wait), and
-  each stop is recorded as an event.
-- Discord stops (its existing STOP file and `stop` verb) and can't restart while the switch is on.
-- New launches refuse: the launcher, chief hire, `run-task.sh`, and any other path that starts an agent.
-- The switch survives a bus restart and a host reboot (it lives in the data root, not in memory).
-- Turning it on and clearing it are human-only verbs, through the bus human proof, and each leaves one
-  event with who and when.
-
-## What exists today (GAP-MAP.md G10, measured at 9ae8c73ac)
-
-These are pieces, with no single switch over them. The design inventories every path that starts or
-continues work and says how each one checks the switch:
-
-- `launch.revoke` and `launch.restore` in `packages/bus/src/broker.mjs` (around :2087), human-only.
-- The `mosaic launches off|on` verbs in `packages/cli/src/cli.mjs` (around :456-533) and
-  `packages/cli/src/launcher.mjs` (around :769).
-- The Discord STOP file (`packages/discord/src/cli.mjs:18-27`).
-
-## What the design must settle
-
-1. Where the switch state lives, its format, and how each process reads it (the broker checks on every
-   work verb; the launcher and Discord check before start). The race: a launch already past its check when
-   the switch goes on must still be stopped.
-2. The CLI verb names (for example `mosaic halt` and `mosaic resume`) and the Console button. The button
-   is a human write, so it goes through the same writer and same-origin checks as other Console writes, and
-   it works under the Q175 SSO session (#412) once phase 2 lands. Until then, test it with fixture servers
-   only.
-3. Per instance. Row 190 adds several instances per host. The switch is per instance, so it stops one
-   instance and never another. The design names how it finds the instance's data root. This row may build
-   on the row 190 candidate (Q177 merge-chaining).
-4. What a stopped run's record says, so run evidence stays write-once and honest.
-
-## Tests
-
-Each part of the goal gets a test: work verbs refuse, a running stand-in session and run are stopped,
-Discord refuses to start, every launch path refuses, the switch survives a restart, an agent can't set or
-clear it, and the clear lets work resume. Mutants: drop the check from one launch path, let an agent clear
-the switch, keep the switch in memory only, skip the SIGKILL after the wait. Each one must fail a test.
-
-## Boundaries
-
-- No test touches `~/.mosaic-dev`, the live units, a real Discord bot or a slot file. Use the stand-in
-  units, scratch data roots and fixture servers the suites already build.
-- Rocko has no git credentials. Sage commits the candidate and runs the queue moves Rocko can't.
-
-## Gate
-
-Dewey approves DESIGN.md, then the manifest. The cli suite, the bus, discord and webui package suites and
-every `scripts/test-*.sh` are green on Sage's gate, and the mutants are killed.

docs/plans/2026-10-20_multi-instance.md

@@ -1,70 +0,0 @@
-# Brief: several Mosaic Stack instances on one host
-
-Sage, 2026-10-20, for Mos's order mos-0974 (MVP, DECISIONS Q176-Q178, Vikunja #414). Gitea #1688. T1 item 1. Owner
-Darkwing, reviewer Filbert, gate owner Sage. Base: refactor at the brief commit. This row blocks both MVP
-cases: Case 1 (Jason's software factory) and Case 2 (Melanie's creative writing hub) run as two instances
-on one homelab host, beside the current mosaic-stack test instance.
-
-Design first. The first deliverable is `agents/darkwing/work/queue-190/DESIGN.md`. Filbert reviews it
-before any code, as Q175 did. Then the build follows the design, with tests and mutants.
-
-## The goal
-
-Two or more instances run side by side on dragon-lin. Each one has its own config file, data root (store,
-broker.sock, host.lock, state, runs, sessions, workspaces), businesses, bus unit, Console unit and port,
-tester port, Discord unit, Claude session env file, stack-active pointer and activation log. No instance's
-commands, units or tools address another instance's state by default or by mistake. On one uid this is
-addressing only, not a security boundary: a same-uid process can still read another instance's files.
-Isolation against that is row 190b (#1693, mos-0986), one Linux user per instance. The current instance keeps working unchanged: its
-config path, data root, unit names and ports stay as they are, and no re-pin is needed for it.
-
-## Known single-instance points (GAP-MAP.md, measured at 9ae8c73ac)
-
-The design starts with a full inventory. Grep every script and package, not only these:
-
-- `packages/cli/systemd/mosaic-bus.service.in`: `mosaic-bus@<business>` sets no `MOSAIC_CONFIG` and reads the
-  fixed `EnvironmentFile=-%h/.config/mosaic-dev/secrets/claude-session.env`.
-- `packages/webui/systemd/mosaic-webui.service.in` and `scripts/webui-service.sh`: one `mosaic-webui.service`.
-- `packages/discord/systemd/[email protected]` and `scripts/discord-service.sh`.
-- `scripts/stack-copy.sh:8` hardcodes `BUSINESS=mosaic-stack`, and `:95` reads `mosaic-webui.service`.
-- `scripts/stack-release.sh`: unit names, the Console port and the tester port default, `COPIES` (:28), the
-  pointer under `$DATA/state` (:1474), and `rehearse`.
-- `scripts/mosaic-config.mjs`, `scripts/bootstrap.sh`, `scripts/reset.sh`, `scripts/land-work.sh`,
-  `packages/webui/src/cli.mjs`, `packages/business/src/{business,vars}.mjs`, and
-  `packages/conversation/src/guard.mjs` each name the default config path or data root.
-
-## What the design must settle
-
-1. Instance identity. How a name maps to its config file and how every tool picks the instance (an
-   `--instance NAME` flag, `MOSAIC_CONFIG`, or both), and what happens with neither (the current default,
-   unchanged). Name rules, and refusal of a name that collides.
-2. Config canon. AGENTS.md invariant 2 says `~/.config/mosaic-dev/config.json` is the sole system config,
-   created only by `scripts/bootstrap.sh`. Several instances mean several config files. The design proposes
-   the exact wording change and how bootstrap creates an instance config without overwriting one. Mos rules
-   on the canon change before the build.
-3. Unit names and templates. The bus, Console and Discord units per instance, how `MOSAIC_CONFIG` and the
-   Claude env file reach each unit, and how the current unit names stay valid for the default instance.
-4. Ports. Each instance's Console and tester ports, with a refusal when two instances claim the same port.
-5. Stack copies and the pointer. Whether copies are shared between instances (read-only trees, so sharing
-   may be fine) and how the pointer, activation log, backups and `flags_drift` stay per instance.
-   `stack-release.sh` and `stack-copy.sh` take the instance.
-6. Secrets. The per-instance Claude session env file and the secrets slot root, resolved from the instance's
-   config dir (the Q175 design resolves its slot the same way: `<configDir>/secrets/mosaic-stack/<slot>`).
-7. Isolation proof. What the tests show: two instances started side by side on stand-in units and scratch
-   roots, each reads only its own config and data root, a command aimed at one never touches the other, and
-   the default instance's paths and unit names are byte-identical to today.
-
-## Boundaries
-
-- No test touches `~/.mosaic-dev`, `~/.config/mosaic-dev`, the live units or a slot file. Use the stand-in
-  systemctl, units and scratch roots that `packages/cli/tests/stack-release.test.mjs` already builds.
-- Standing up a real second instance on dragon-lin is a later window under Q173, with a backup first and a
-  STATE report after. Exposing a new Console through the tunnel or Traefik changes who can reach it from
-  outside, so it waits for Jason. SSO (Q175, #412) comes first for any instance a second user can reach.
-- Merge-chaining (Q177): rows that need instances (human users, kill switch, lifecycle) may build on this
-  row's candidate. This row keeps its own review and gate.
-
-## Gate
-
-Filbert approves DESIGN.md, then the manifest. The cli suite and every `scripts/test-*.sh` are green on
-Sage's gate, and the design's mutants are killed.

docs/plans/2026-10-20_retire-control-board.md

@@ -1,42 +0,0 @@
-# Brief: retire the control board writer on 7331
-
-Sage, 2026-10-20, for Mos's ruling mos-1008 item 2. Gitea #1696. MVP 10-27 work. Owner Bushroot (Haiku 5.5, a
-low-level model under Q177), reviewer Webby, gate owner Sage. Base: refactor at the brief commit.
-
-## Why
-
-`packages/control-board/src/serve.mjs` is a loopback HTTP service on 7331 with no authentication. It reads
-transcripts and writes through `/api/reply`. Any host process that reaches the port can do both. That fails
-Q175 ("zero trust with verification"). Gander found it in the row 196 inventory (gander-0004). Nothing listens
-on 7331 now (`ss -ltnp`, 2026-10-20T19:05:09Z), so retiring it costs the least.
-
-## Steps, in order
-
-1. Inventory first. List every reference to the control board and to 7331: scripts, units, `scripts/mosaic`
-   and other CLI dispatch, docs (AGENTS.md, READMEs, TOOLS.md), package.json scripts, tests, and the Console
-   (`packages/webui`). For each, say whether it starts the writer, reads its code, or only mentions it.
-   Commit the list as `agents/bushroot/work/queue-ROW/INVENTORY.md` and send it to Sage and Webby.
-2. Stop if something depends on it. If a reference shows a live dependency (the Console or another package
-   imports code that only the control board has, or a unit or script still starts it), stop. Sage takes it to
-   Mos before anything is removed.
-3. Otherwise retire the writer. Either remove the `serve` entry point, or make it refuse to start with a
-   message that points to the Console. Keep any read-only code another package imports, and say which.
-   Update the docs that tell people to start it. The AGENTS.md text about the control-board reply convention
-   is a separate matter. Change it only if it tells someone to start 7331.
-
-## Acceptance
-
-Nothing in the stack can start a writer on 7331. A test proves it: the entry point refuses (or is gone), no
-script or unit starts it, and a grep check finds no starter. Each change gets a mutant that brings the writer
-back and the test kills it.
-
-## Boundaries
-
-- No change to the live units, `~/.mosaic-dev`, `~/.config/mosaic-dev`, slot files or `~/.mosaic`.
-- No request to any live port.
-- Single test files run freely. Suites need Sage's slot.
-
-## Gate
-
-Webby approves INVENTORY.md, then the manifest. The control-board and webui package suites, the cli suite and
-every `scripts/test-*.sh` are green on Sage's gate, and the mutants are killed.

docs/plans/2026-10-20_second-gate-lane.md

@@ -1,42 +0,0 @@
-# Brief: a second gate lane, two full gates at once on dragon-lin
-
-Sage, 2026-10-20, for Mos's order mos-0977 item 6 ("put the design for a second gate lane on the list now")
-and the MVP push (mos-0974). Gitea #1695. Owner Herb (Codex gpt-6.1-sol, a new builder seat), reviewer
-Webby, gate owner Sage. Base: refactor at the brief commit. Design first. The first deliverable is
-`agents/herb/work/queue-ROW/DESIGN.md`.
-
-## Why
-
-Every full run shares one slot today. A full gate (cli suite plus every `scripts/test-*.sh`) takes about 13
-minutes or more, reviewers' runs and mutants take the same slot, and with eight or more seats building for
-10-27 the slot is the bottleneck. The slot exists because concurrent runs broke each other. The busy check is
-`agents/sage/work/gate-lane/busy-now.sh` (a copy of Sage's), and the gate is
-`agents/sage/work/gate-lane/gate-template.sh` (a copy of Sage's template). The host has 16 cores and 62 GB.
-
-## What the design must settle
-
-1. Every shared resource two concurrent runs can collide on, found from the code and tests, not guessed:
-   Docker compose project names and networks (`scripts/test-task.sh` and others), fixed TCP ports in tests,
-   unix socket paths and their 107-byte limit under TMPDIR, the sandbox's private `/tmp`, shared caches,
-   scratch and worktree paths, the queue lock, and any test that reads host-wide state (process lists,
-   `pgrep`, `/proc`). For each: how a lane gets its own copy, or why it is safe to share.
-2. Timing. Which tests have time limits that a doubled CPU load could break, measured, and what changes (a
-   bound, or a lane rule that keeps those suites apart).
-3. The lane mechanism: lane ids, a lock per lane that a run takes and releases even on a crash, the busy
-   check that reports per lane, and how a seat asks for a lane. Sage still grants it.
-4. The gate template takes a lane id and isolates everything from point 1 by it.
-5. Proof: two full gates on different candidates at once, three times, with zero cross-failures, plus the
-   wall time of each against a single-lane run. Any flake found is named with its cause.
-
-## Boundaries
-
-- No change to the live units, `~/.mosaic-dev`, `~/.config/mosaic-dev` or slot files. The proof runs use
-  scratch roots only, and it needs Sage's grant of the whole slot while it runs.
-- Test code changes that only isolate a resource are in scope. A change to what a test checks is not, and
-  goes to its owner.
-- Docker networks and containers a run makes are removed by the run (trap), and nothing else is touched.
-
-## Gate
-
-Webby approves DESIGN.md, then the manifest. The cli suite and every `scripts/test-*.sh` are green on Sage's
-gate, both singly and in the two-lane proof.

docs/plans/2026-10-20_sso-phase1.md

@@ -1,47 +0,0 @@
-# Brief: Q175 phase 1, the Console verifies SSO itself (--sso)
-
-Sage, 2026-10-20, for Q175 (Jason's ruling), mos-0971/0973/0977 and Vikunja #412. Gitea #1690. MVP T1 item 2. Owner
-Launchpad, reviewer Webby (mos-0981), gate owner Sage. Base: refactor at the brief commit.
-
-The design is approved: `agents/sage/work/q175-sso/DESIGN.md` at d55d86bb0 (blob eba861f5d2bb), Filbert r3
-approve plus the D1/D2 ack, Mos C1 confirmation in mos-0977, whose straggler-check condition is in the phase 2 window at b416d2ede. Build phase 1 exactly as the design says. If
-the code shows the design is wrong somewhere, stop and tell Sage, Webby and Filbert before building around it.
-
-## Scope (phase 1 only, design section 5 item 1)
-
-- oauth4webapi 3.8.8, pinned exactly (design section 2). No other new dependency.
-- The OIDC relying party in the Console: `/auth/login`, `/auth/callback`, `/auth/logout`, `/auth/signed-out`,
-  the callback steps 1-7, our own checks on top of the library, and sessions, cookies and Host rules
-  (design sections 1 and 3).
-- The shared loader, `scripts/mosaic-config.mjs`, accepts an optional `console` key and checks only its
-  shape. The slot file checks and the read run in the Console's `--sso` start, and the slot resolves from
-  the config dir (section 4, D1, D2).
-- The degraded start for an unreachable provider, and the unreachable/refused classes (Q-B, section 4).
-- `--sso` for `cli.mjs serve` and `webui-service.sh`, with its refusals against the old flags.
-- The tester listener rules (section 6).
-- The page: both fetch paths in `packages/webui/src/public/app.js` (:111 and :305) treat a 401
-  `sign-in required` as signed out, and the notice links to `/auth/login?return=<path>` (C2).
-- Logging as the design says, including the Q-E `subject-unknown` line.
-
-Out of scope: the phase 2 window, the live config.json key, phase 3 removals, the proxy-forwarded token
-(section 7), and any change to the live Console.
-
-## Tests and mutants
-
-Design section 9: tests 1-25, the positive paths, and every listed mutant, each killed by its named test.
-All tests run against the fake OP in `packages/webui/tests/helpers/fake-oidc.mjs`. No test reaches a real
-provider or Authentik, and no test touches `~/.mosaic-dev`, `~/.config/mosaic-dev`, the live units or a
-slot file. Test 25 goes in `scripts/test-config.sh`.
-
-## Boundaries
-
-- No request of any kind to auth.diversecanvas.com, mosaic.woltje.com or the live 127.0.0.1:7332 (mos-0971,
-  design section 8).
-- No credential value is read, printed or logged.
-- `npm install` runs only inside the worktree that has its own package.json, never in a directory that would
-  walk up to home.
-
-## Gate
-
-Webby approves the manifest. Filbert approved the design and answers design questions. The webui and cli suites, `scripts/test-config.sh` and every
-`scripts/test-*.sh` are green on Sage's gate, and the design's mutants are killed.

docs/plans/QUEUE.md

@@ -33,7 +33,7 @@ Gaps found while working go to `docs/plans/DEFERRED.md`, not here.
 
 <!-- mosaic-queue:begin -->
 
-Generated from `docs/plans/queue.json` revision 2247 by `queue render`. Do not edit between the markers; change the queue with `scripts/mosaic queue`.
+Generated from `docs/plans/queue.json` revision 2236 by `queue render`. Do not edit between the markers; change the queue with `scripts/mosaic queue`.
 
 | # | Piece | Owner | Issues | State | After | Gate | Brief | Note |
 |---|---|---|---|---|---|---|---|---|
@@ -225,9 +225,6 @@ Generated from `docs/plans/queue.json` revision 2247 by `queue render`. Do not e
 | 186 | stack-release --plan: the backup line says what the run will do (P19 404, row 185 N1/N2) | darkwing; reviewers filbert | #1684 | done | — | Filbert approves the manifest; cli suite and every scripts/test-*.sh green on Sage's gate; the three brief mutants killed (sage) | `docs/plans/2026-10-20_plan-backup-line.md` § Brief: the activate plan's backup line says what the run will do | Landed 269134d8d (author Darkwing) on 3c5da3a91. Patch-id c97b9f6e25cd matches the r1 candidate (manifest 449e9121, Filbert approve 29419). Sage gate on b367f5730+patch 09:00:20Z-09:08:59Z: node 2681/0, scripts 422/0, queue 156, network removed; 3c5da3a91 adds only a SESSIONS line. Not live: the stack runs copy 490e2771d3d0. Follow-ups on P19 404: Filbert M6 gap, store-unclean reading. |
 | 187 | stack-release activate carries the row 178 proof pair (mos-0928 Part B A0) | darkwing; reviewers filbert | #1685 | done | 186 done | Filbert approves the manifest; cli suite and every scripts/test-*.sh green on Sage's gate; the brief mutants killed (sage) | `docs/plans/2026-10-20_activate-proof-pair.md` § Brief: activate carries the row 178 proof pair | Landed 9a71e4e80 (author Darkwing) on d17328a55; patch-id 6b57c47bc661 matches candidate 52a5ecc1d143 and Filbert's r1 reading. Sage gate passed 10:21:55Z: cli 446/446 and every package and scripts/test-*.sh green. Filbert approve 29424, rev 2204; follow-ups N1-N4 filed on P19. |
 | 188 | stack-release tests: a carried proof pair and a proof file inside the repository (P19 409, 410; gates Part B) | darkwing; reviewers filbert | #1686 | done | 187 settled | Filbert approves the manifest; cli suite and every scripts/test-*.sh green on Sage's gate; the brief mutants killed (sage) | `docs/plans/2026-10-20_proof-test-gaps.md` § Brief: tests for the two proof-file paths row 187 left open | Landed 8fc0ee216 (author Darkwing) on 23a609c5c; patch-id c9a56b167c07 matches candidate 86aa549bad75 and Filbert's r1 reading; stack-release.sh blob 2586a2a37cd2 unchanged. Sage gate passed 10:58Z: cli 453/453 and every package and scripts/test-*.sh green. Filbert approve 29433, rev 2212; N1 (REPO logical path) to P19 after Part B (mos-0959). |
-| 189 | stack-release activate --no-send drops the Console's --send and keeps the pointer in step (Q175 interim, mos-0972, P19 413) | sage; reviewers dewey | #1687 | in-review, round 1, request posted | 163 done | Dewey approves the manifest; cli suite and every scripts/test-*.sh green on Sage's gate; the brief mutants killed (sage) | `docs/plans/2026-10-20_activate-no-send.md` § Brief: activate --no-send drops the Console's --send | — |
-| 190 | several Mosaic Stack instances on one host: per-instance config, data root, units and ports (MVP T1.1, mos-0974, Vikunja #414) | darkwing; reviewers filbert | #1688 | in-progress | — | Filbert approves DESIGN.md then the manifest; cli suite and every scripts/test-*.sh green on Sage's gate; the design mutants killed (sage) | `docs/plans/2026-10-20_multi-instance.md` § Brief: several Mosaic Stack instances on one host | — |
-| 191 | one kill switch for the bus, every run, Discord and new launches, from the CLI and the Console (MVP T1.4, mos-0974, Vikunja #414) | rocko; reviewers dewey | #1689 | in-progress | — | Dewey approves DESIGN.md then the manifest; cli, bus, discord and webui suites and every scripts/test-*.sh green on Sage's gate; the mutants killed (sage) | `docs/plans/2026-10-20_kill-switch.md` § Brief: one kill switch for the bus, every run, Discord and new launches | — |
 
 <!-- mosaic-queue:end -->
 

docs/plans/queue.json

@@ -1,7 +1,7 @@
 {
   "version": 1,
   "canonicalRoot": "/mnt/storage/src/mosaic-stack",
-  "revision": 2247,
+  "revision": 2236,
   "rows": [
     {
       "id": 1,
@@ -19820,153 +19820,6 @@
       "createdAt": "2026-10-20T10:31:30.403Z",
       "updatedAt": "2026-10-20T11:11:25.098Z",
       "updatedBy": "sage"
-    },
-    {
-      "id": 189,
-      "piece": "stack-release activate --no-send drops the Console's --send and keeps the pointer in step (Q175 interim, mos-0972, P19 413)",
-      "owner": "sage",
-      "issues": [
-        1687
-      ],
-      "closes": [
-        1687
-      ],
-      "state": "in-review",
-      "previousState": null,
-      "required": false,
-      "requiredSince": null,
-      "gate": "Dewey approves the manifest; cli suite and every scripts/test-*.sh green on Sage's gate; the brief mutants killed",
-      "gateOwner": "sage",
-      "brief": {
-        "path": "docs/plans/2026-10-20_activate-no-send.md",
-        "anchor": "Brief: activate --no-send drops the Console's --send",
-        "blob": "0444b774faf09084311357fdd59b0ef3a3d347eb"
-      },
-      "after": [
-        {
-          "id": 163,
-          "when": "done"
-        }
-      ],
-      "reviewers": [
-        "dewey"
-      ],
-      "review": {
-        "rounds": [
-          {
-            "n": 1,
-            "op": "sage-189-inreview-1",
-            "by": "sage",
-            "at": "2026-10-20T18:46:06.124Z",
-            "issue": 1687,
-            "candidate": {
-              "kind": "manifest",
-              "digest": "67af69bd579561fd8c20be2a47695240a9f09f119dbfff88a8e72e2a7416e668",
-              "text": "70dbc89c0282fa063514317262d8926d16b8b8aaab4a1e47379303918495fc2c  agents/sage/work/queue-189/BUILD.md\n4bd216cce2b40b39998725daa8989f6e3acb3ccd81a7017f6b09026af3965584  agents/sage/work/queue-189/mutants-run.log\nddbdddf03abf4aa91aa62f52e468be7af3c6b2f5d7bec2ee99b11e315471f18c  agents/sage/work/queue-189/mutants.sh\n5d7b2da84d994f4f93d1212e349b4e4c19c5c00780e6cfcde91edb3ca08c014e  docs/plans/2026-10-20_activate-no-send.md\n38e410c4cb731390f96747646eb7f6caa7a587fca9024ccbe901aab5ac19c7cf  docs/TOOLS.md\nfe430969cc669515e348fced1a22cbe839a12023f7ac67cfba905b7afd29872f  packages/cli/tests/stack-release.test.mjs\n16f77305e558f4fb953accc6d09f1f7b408aba363851d8ca79216ffce41bed9f  scripts/stack-release.sh\n"
-            },
-            "request": "comment",
-            "attempts": [
-              {
-                "op": "sage-189-inreview-1",
-                "by": "sage",
-                "at": "2026-10-20T18:46:06.124Z",
-                "state": "posted",
-                "comment": 29457,
-                "transport": {
-                  "outcome": "posted",
-                  "status": 201,
-                  "comment": 29457,
-                  "detail": "created"
-                },
-                "resolutions": []
-              }
-            ],
-            "duplicateRisk": false,
-            "receipts": []
-          }
-        ]
-      },
-      "claim": {
-        "seat": "sage",
-        "op": "sage-189-start"
-      },
-      "note": null,
-      "blockedReason": null,
-      "createdAt": "2026-10-20T18:21:38.646Z",
-      "updatedAt": "2026-10-20T18:46:24.267Z",
-      "updatedBy": "sage"
-    },
-    {
-      "id": 190,
-      "piece": "several Mosaic Stack instances on one host: per-instance config, data root, units and ports (MVP T1.1, mos-0974, Vikunja #414)",
-      "owner": "darkwing",
-      "issues": [
-        1688
-      ],
-      "closes": [
-        1688
-      ],
-      "state": "in-progress",
-      "previousState": null,
-      "required": false,
-      "requiredSince": null,
-      "gate": "Filbert approves DESIGN.md then the manifest; cli suite and every scripts/test-*.sh green on Sage's gate; the design mutants killed",
-      "gateOwner": "sage",
-      "brief": {
-        "path": "docs/plans/2026-10-20_multi-instance.md",
-        "anchor": "Brief: several Mosaic Stack instances on one host",
-        "blob": "79fa60fbf17a352edc5431d6aabc77c72ec5c48f"
-      },
-      "after": [],
-      "reviewers": [
-        "filbert"
-      ],
-      "review": null,
-      "claim": {
-        "seat": "darkwing",
-        "op": "darkwing-190-start"
-      },
-      "note": null,
-      "blockedReason": null,
-      "createdAt": "2026-10-20T18:42:48.052Z",
-      "updatedAt": "2026-10-20T18:45:23.430Z",
-      "updatedBy": "darkwing"
-    },
-    {
-      "id": 191,
-      "piece": "one kill switch for the bus, every run, Discord and new launches, from the CLI and the Console (MVP T1.4, mos-0974, Vikunja #414)",
-      "owner": "rocko",
-      "issues": [
-        1689
-      ],
-      "closes": [
-        1689
-      ],
-      "state": "in-progress",
-      "previousState": null,
-      "required": false,
-      "requiredSince": null,
-      "gate": "Dewey approves DESIGN.md then the manifest; cli, bus, discord and webui suites and every scripts/test-*.sh green on Sage's gate; the mutants killed",
-      "gateOwner": "sage",
-      "brief": {
-        "path": "docs/plans/2026-10-20_kill-switch.md",
-        "anchor": "Brief: one kill switch for the bus, every run, Discord and new launches",
-        "blob": "aed33125fa67ae69af73c18ffc9e2a83481421f3"
-      },
-      "after": [],
-      "reviewers": [
-        "dewey"
-      ],
-      "review": null,
-      "claim": {
-        "seat": "rocko",
-        "op": "rocko-191-start"
-      },
-      "note": null,
-      "blockedReason": null,
-      "createdAt": "2026-10-20T18:43:05.222Z",
-      "updatedAt": "2026-10-20T18:45:05.621Z",
-      "updatedBy": "rocko"
     }
   ],
   "log": [
@@ -78903,329 +78756,6 @@
         "receipt": "ok sage-163-done rev 2236 row 163 in-review→done round 2"
       },
       "viewSha": "e44815d32d46b91ee37d4c3c4701716956ba35d29c16c24c89020cce345bd61b"
-    },
-    {
-      "rev": 2237,
-      "op": "sage-189-add",
-      "verb": "add",
-      "args": {
-        "piece": "stack-release activate --no-send drops the Console's --send and keeps the pointer in step (Q175 interim, mos-0972, P19 413)",
-        "gate": "Dewey approves the manifest; cli suite and every scripts/test-*.sh green on Sage's gate; the brief mutants killed",
-        "brief": "docs/plans/2026-10-20_activate-no-send.md#Brief: activate --no-send drops the Console's --send",
-        "issues": [
-          1687
-        ],
-        "note": null,
-        "owner": "sage",
-        "gateOwner": "sage",
-        "after": [
-          {
-            "id": 163,
-            "when": "done"
-          }
-        ],
-        "reviewers": [
-          "dewey"
-        ],
-        "required": null
-      },
-      "by": "sage",
-      "at": "2026-10-20T18:21:38.646Z",
-      "semantics": 2,
-      "result": {
-        "row": 189,
-        "from": null,
-        "to": "queued",
-        "brief": {
-          "path": "docs/plans/2026-10-20_activate-no-send.md",
-          "anchor": "Brief: activate --no-send drops the Console's --send",
-          "blob": "0444b774faf09084311357fdd59b0ef3a3d347eb"
-        },
-        "receipt": "ok sage-189-add rev 2237 row 189 none→queued"
-      },
-      "viewSha": "70bf9967156881afecaba9ccf4edf8cbc63a344eb7c6407b3453c950781f34c5"
-    },
-    {
-      "rev": 2238,
-      "op": "sage-189-briefed",
-      "verb": "move",
-      "args": {
-        "id": 189,
-        "to": "briefed",
-        "reason": null,
-        "candidate": null,
-        "evidence": null,
-        "issue": null
-      },
-      "by": "sage",
-      "at": "2026-10-20T18:22:01.437Z",
-      "semantics": 2,
-      "result": {
-        "row": 189,
-        "from": "queued",
-        "to": "briefed",
-        "round": null,
-        "issue": null,
-        "candidate": null,
-        "receipt": "ok sage-189-briefed rev 2238 row 189 queued→briefed"
-      },
-      "viewSha": "27ee8a26722d3eaf4c4b346e06ffdb853037aad2d1a7fe14f440cbe1bb9a2a27"
-    },
-    {
-      "rev": 2239,
-      "op": "sage-189-start",
-      "verb": "move",
-      "args": {
-        "id": 189,
-        "to": "in-progress",
-        "reason": null,
-        "candidate": null,
-        "evidence": null,
-        "issue": null
-      },
-      "by": "sage",
-      "at": "2026-10-20T18:22:18.476Z",
-      "semantics": 2,
-      "result": {
-        "row": 189,
-        "from": "briefed",
-        "to": "in-progress",
-        "round": null,
-        "issue": null,
-        "candidate": null,
-        "receipt": "ok sage-189-start rev 2239 row 189 briefed→in-progress"
-      },
-      "viewSha": "230578585341fcfc9429364332ca8b78988ffd669d3c1bb5e2e94a74d9916649"
-    },
-    {
-      "rev": 2240,
-      "op": "sage-190-add",
-      "verb": "add",
-      "args": {
-        "piece": "several Mosaic Stack instances on one host: per-instance config, data root, units and ports (MVP T1.1, mos-0974, Vikunja #414)",
-        "gate": "Filbert approves DESIGN.md then the manifest; cli suite and every scripts/test-*.sh green on Sage's gate; the design mutants killed",
-        "brief": "docs/plans/2026-10-20_multi-instance.md#Brief: several Mosaic Stack instances on one host",
-        "issues": [
-          1688
-        ],
-        "note": null,
-        "owner": "darkwing",
-        "gateOwner": "sage",
-        "after": null,
-        "reviewers": [
-          "filbert"
-        ],
-        "required": null
-      },
-      "by": "sage",
-      "at": "2026-10-20T18:42:48.052Z",
-      "semantics": 2,
-      "result": {
-        "row": 190,
-        "from": null,
-        "to": "queued",
-        "brief": {
-          "path": "docs/plans/2026-10-20_multi-instance.md",
-          "anchor": "Brief: several Mosaic Stack instances on one host",
-          "blob": "79fa60fbf17a352edc5431d6aabc77c72ec5c48f"
-        },
-        "receipt": "ok sage-190-add rev 2240 row 190 none→queued"
-      },
-      "viewSha": "b4319dbd993254b58e4db8be18769b04322028903e325c0c8cadcfdec527929f"
-    },
-    {
-      "rev": 2241,
-      "op": "sage-191-add",
-      "verb": "add",
-      "args": {
-        "piece": "one kill switch for the bus, every run, Discord and new launches, from the CLI and the Console (MVP T1.4, mos-0974, Vikunja #414)",
-        "gate": "Dewey approves DESIGN.md then the manifest; cli, bus, discord and webui suites and every scripts/test-*.sh green on Sage's gate; the mutants killed",
-        "brief": "docs/plans/2026-10-20_kill-switch.md#Brief: one kill switch for the bus, every run, Discord and new launches",
-        "issues": [
-          1689
-        ],
-        "note": null,
-        "owner": "rocko",
-        "gateOwner": "sage",
-        "after": null,
-        "reviewers": [
-          "dewey"
-        ],
-        "required": null
-      },
-      "by": "sage",
-      "at": "2026-10-20T18:43:05.222Z",
-      "semantics": 2,
-      "result": {
-        "row": 191,
-        "from": null,
-        "to": "queued",
-        "brief": {
-          "path": "docs/plans/2026-10-20_kill-switch.md",
-          "anchor": "Brief: one kill switch for the bus, every run, Discord and new launches",
-          "blob": "aed33125fa67ae69af73c18ffc9e2a83481421f3"
-        },
-        "receipt": "ok sage-191-add rev 2241 row 191 none→queued"
-      },
-      "viewSha": "2cdc7c37430226f1ea01ed9f3d60a2c12be16eddac38d18dc16f889c7b54b14e"
-    },
-    {
-      "rev": 2242,
-      "op": "sage-190-brief",
-      "verb": "move",
-      "args": {
-        "id": 190,
-        "to": "briefed",
-        "reason": null,
-        "candidate": null,
-        "evidence": null,
-        "issue": null
-      },
-      "by": "sage",
-      "at": "2026-10-20T18:43:25.630Z",
-      "semantics": 2,
-      "result": {
-        "row": 190,
-        "from": "queued",
-        "to": "briefed",
-        "round": null,
-        "issue": null,
-        "candidate": null,
-        "receipt": "ok sage-190-brief rev 2242 row 190 queued→briefed"
-      },
-      "viewSha": "6203315b484302369ce5ea7d854082a6bca4a95f9793e14ec123f57381234c95"
-    },
-    {
-      "rev": 2243,
-      "op": "sage-191-brief",
-      "verb": "move",
-      "args": {
-        "id": 191,
-        "to": "briefed",
-        "reason": null,
-        "candidate": null,
-        "evidence": null,
-        "issue": null
-      },
-      "by": "sage",
-      "at": "2026-10-20T18:43:43.042Z",
-      "semantics": 2,
-      "result": {
-        "row": 191,
-        "from": "queued",
-        "to": "briefed",
-        "round": null,
-        "issue": null,
-        "candidate": null,
-        "receipt": "ok sage-191-brief rev 2243 row 191 queued→briefed"
-      },
-      "viewSha": "9cc7dda5fa676258e864dedfdf2f4e3904c8723ba9c36474cff76757f52e5c07"
-    },
-    {
-      "rev": 2244,
-      "op": "rocko-191-start",
-      "verb": "move",
-      "args": {
-        "id": 191,
-        "to": "in-progress",
-        "reason": null,
-        "candidate": null,
-        "evidence": null,
-        "issue": null
-      },
-      "by": "rocko",
-      "at": "2026-10-20T18:45:05.621Z",
-      "semantics": 2,
-      "result": {
-        "row": 191,
-        "from": "briefed",
-        "to": "in-progress",
-        "round": null,
-        "issue": null,
-        "candidate": null,
-        "receipt": "ok rocko-191-start rev 2244 row 191 briefed→in-progress"
-      },
-      "viewSha": "cd2423e53ac82a667c737852bef6adfdafba82987f37cd090f5484b15b3a0e0c"
-    },
-    {
-      "rev": 2245,
-      "op": "darkwing-190-start",
-      "verb": "move",
-      "args": {
-        "id": 190,
-        "to": "in-progress",
-        "reason": null,
-        "candidate": null,
-        "evidence": null,
-        "issue": null
-      },
-      "by": "darkwing",
-      "at": "2026-10-20T18:45:23.430Z",
-      "semantics": 2,
-      "result": {
-        "row": 190,
-        "from": "briefed",
-        "to": "in-progress",
-        "round": null,
-        "issue": null,
-        "candidate": null,
-        "receipt": "ok darkwing-190-start rev 2245 row 190 briefed→in-progress"
-      },
-      "viewSha": "014db845fb2e380678ab1250f2cd3c0d7b192dc39909416515482c810440149b"
-    },
-    {
-      "rev": 2246,
-      "op": "sage-189-inreview-1",
-      "verb": "move",
-      "args": {
-        "id": 189,
-        "to": "in-review",
-        "reason": null,
-        "candidate": "agents/sage/work/queue-189/candidate-manifest.sha256",
-        "evidence": null,
-        "issue": null
-      },
-      "by": "sage",
-      "at": "2026-10-20T18:46:06.124Z",
-      "semantics": 2,
-      "result": {
-        "row": 189,
-        "from": "in-progress",
-        "to": "in-review",
-        "round": 1,
-        "issue": 1687,
-        "candidate": {
-          "kind": "manifest",
-          "digest": "67af69bd579561fd8c20be2a47695240a9f09f119dbfff88a8e72e2a7416e668",
-          "text": "70dbc89c0282fa063514317262d8926d16b8b8aaab4a1e47379303918495fc2c  agents/sage/work/queue-189/BUILD.md\n4bd216cce2b40b39998725daa8989f6e3acb3ccd81a7017f6b09026af3965584  agents/sage/work/queue-189/mutants-run.log\nddbdddf03abf4aa91aa62f52e468be7af3c6b2f5d7bec2ee99b11e315471f18c  agents/sage/work/queue-189/mutants.sh\n5d7b2da84d994f4f93d1212e349b4e4c19c5c00780e6cfcde91edb3ca08c014e  docs/plans/2026-10-20_activate-no-send.md\n38e410c4cb731390f96747646eb7f6caa7a587fca9024ccbe901aab5ac19c7cf  docs/TOOLS.md\nfe430969cc669515e348fced1a22cbe839a12023f7ac67cfba905b7afd29872f  packages/cli/tests/stack-release.test.mjs\n16f77305e558f4fb953accc6d09f1f7b408aba363851d8ca79216ffce41bed9f  scripts/stack-release.sh\n"
-        },
-        "receipt": "ok sage-189-inreview-1 rev 2246 row 189 in-progress→in-review round 1 on #1687; request sage-189-inreview-1 requesting"
-      },
-      "viewSha": "d8a3aa936a9a819329e86679d0bfcf658d773d0f7cfd29c10587c6447f78e968"
-    },
-    {
-      "rev": 2247,
-      "op": "sage-189-inreview-1.outcome",
-      "verb": "review-outcome",
-      "args": {
-        "id": 189,
-        "attempt": "sage-189-inreview-1",
-        "outcome": "posted",
-        "status": 201,
-        "comment": 29457,
-        "detail": "created"
-      },
-      "by": "sage",
-      "at": "2026-10-20T18:46:24.267Z",
-      "semantics": 2,
-      "result": {
-        "row": 189,
-        "round": 1,
-        "attempt": "sage-189-inreview-1",
-        "state": "posted",
-        "receipt": "ok sage-189-inreview-1.outcome rev 2247 row 189 round 1 request sage-189-inreview-1 posted comment 29457"
-      },
-      "viewSha": "6d7e91ae3cab0b76e5c5d791fb821b97c9da7db16389ff2d531d7b77d2a069f1"
     }
   ]
 }