gander: record approved design restart policy and implementation plan

BUILD-LOG.md

@@ -5174,3 +5174,9 @@ Before: managed project/thread verbs had no Console conversation area. After: fi
 2026-10-20 04:44:54 UTC | Row 178 round 2 preparation | Before: Dewey C1 five render guards lacked killing tests. Added independent refusal fixtures, a temporary uid+1 id stub with cleanup, and empty loopback proof case; activation ordering recorded in r2 BUILD. Product unchanged; syntax/text preflight only, no test or mutant execution. Pending row 181 rebase and Sage slot.
 
 2026-10-20 05:10:34 UTC | Row 178 #1676 round 2 verified | Before: C1 render refusals lacked killing tests and row 181 base was pending. Rebased onto 931651f2d, kept all COUNTED/count code and tests, appended T178 tail; added independent owner/collision/absolute/charset/header and empty-loopback proof tests. Four files singly 156/156, all 24 mutants killed, metadata and sandbox fixture probes pass; scratch sweep empty. Packet agents/rocko/work/queue-178/r2/, candidate 9300a670, inventory d0dcde7b (59/59), scan 58 files no findings; in-review revs 2166-2167, expected no-token request failure. No live actions or commits.
+
+2026-10-20 19:09:44 UTC | Gander row 196 #1694 design phase | Before: tester TCP reaches every local uid and human proofs do not bind the socket peer. After: design draft at agents/gander/work/queue-196/DESIGN.md inventories listeners, proposes private tester HTTP and SO_PEERCRED binding, aligns the per-request principal contract with Morgana and Gizmoduck, and lists migration, tests, mutants and same-uid limits. Python versus other credential options and Console provenance require Duckworth ruling. Documentation only. No product code, suite, live probe, secret access or deployment.
+
+2026-10-20 19:16:20 UTC | Gander row 196 #1694 design r2 | Before: Duckworth r1 requested concurrent helper-fd evidence (B1) and selected O1 with interpreter, proof-only and image conditions. After: design adds eight concurrent genuine proof processes plus a racing copier, M20 swapped socket and post-helper socket survival, root-owned system ELF pinning and activation evidence, safe gid validation, cap traffic without helpers, and unchanged P19 R2 text. Mos accepted socket-only tester access (mos-1015 via sage-1363); any authenticated browser relay is a separate row. Documentation coverage checks passed. No product code, suites or live action.
+
+2026-10-20 19:21:19 UTC | Gander row 196 #1694 design approval and N5 | Before: Duckworth approved r2 (duckworth-0009, cb6d840df) with a nonblocking interpreter-upgrade note. After: r3 chooses startup safety revalidation, appends actual interpreter identity to bus/peercred-starts.jsonl and retains old activation evidence. Operator re-pin uses the next reviewed copy, respecting already-active refusal. Added task-by-task PLAN.md for inline implementation and independent manifest review. Documentation checks passed. No product code, suites or live action.

agents/README.md

@@ -16,6 +16,12 @@ 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 |
+| 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/duckworth/README.md

@@ -0,0 +1,7 @@
+# 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

@@ -0,0 +1,8 @@
+# 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/gander/work/queue-196/DESIGN.md

@@ -0,0 +1,332 @@
+# Row 196: the human boundary across uids and humans
+
+Gander, 2026-10-20. Revision 3, recording approved r2 and N5. Gitea #1694, P19 333.
+Base: `96f243faf`, branch `gander/row196`. Design approval latest-by 2026-10-22, landing
+latest-by 2026-10-24 and before federation R3. This document authorizes no live action.
+
+## 1. Outcome and authority
+
+Other Linux users must not reach the tester's data or writes. A bus human proof must describe
+the process that actually connected. Console user calls must also pass the human walk and
+come directly from this bus tree's Console. Row 193 and federation R3 use that one verifier.
+
+This is not isolation from a hostile process on the instance's own uid. Keeping the human
+terminal CLI means that an unmarked process on that uid still has the owner's authority.
+Process ancestry cannot prove that a process was never an agent. Sections 4 and 8 state this
+limit without treating it as an enforcement guarantee.
+
+Inputs: COMMON at `53bb59462`, the row brief at `96f243faf`, Q175 sections 1, 6 and 8,
+federation r2 at `60b9b112a` section 3.6, Duckworth's B1-B5 at `b402197ff`, row 190's
+DESIGN.md and the row 190b brief. Q175-Q178 and the MVP plan set the order. Row 190b is on
+hold pending the host decision. This row does not assume that a separate uid is already live.
+
+Sage's `sage-1343` accepts the design direction and requires Duckworth to rule on the peer
+credential implementation. `sage-1345` keeps the control board inventory-only. Morgana's
+`morgana-0003` supplies the principal contract in section 4. Sage registers this session.
+Mos accepted removal of direct tester browser access in mos-1015, relayed by sage-1363.
+Agents test through the private socket. Any later browser view is an authenticated relay
+behind SSO, designed and reviewed in its own row. This row adds no relay.
+
+## 2. Inventory from code, not a live probe
+
+"Same uid" includes untrusted local processes. "Other uid" excludes root, which is outside
+this boundary. SSO below means Q175 is active on that instance, not merely installed.
+
+| Entry | Same uid today | Other uid today | Effect of SSO and this row |
+|---|---|---|---|
+| Main Console, default 7332, bare serve default 7330 | Loopback reads. With preview/send, matching Host, header and origin can write as owner | Same TCP reach and header forgery | Q175 SSO verifies login and refuses non-public Host except GET /healthz. This row does not change public ingress |
+| Tester TCP, default installation 7333, optional per instance | Reads and the tester instance, route, name and chat writes | Identical reach, no uid check | Q175 deliberately leaves tester separate. This row replaces TCP with a private filesystem Unix socket |
+| `<dataRoot>/bus/broker.sock` | Connects, then needs cap or proof. Claimed human PID is not the socket peer | Normally refused by bus/ 0700 and socket 0600 | SSO changes nothing. Add peer uid and PID binding, retain file checks |
+| Human wrapper to tree's human-cli.mjs | Owner if CLI path, nonce and ancestry pass. Agent ancestors refuse | Cannot connect to protected socket, and proof uid refuses | Preserve terminal owner path, add peer binding. SSO does not authenticate terminal users |
+| Tester CLI to broker.sock | Tester if its proof passes and bus.tester is exactly true. T3 agents are allowed, managed runs are not | Filesystem modes normally refuse | Same tester policy, plus peer binding. No owner/user upgrade |
+| `<dataRoot>/bus-host/launch.sock` | Requires run cap and launcher checks | bus-host/ 0700, socket 0600 | No human proof endpoint. Unchanged |
+| `<dataRoot>/bus-host/git.sock` | Git capability protocol and broker authorization | bus-host/ 0700, socket 0600 | No human proof endpoint. Unchanged |
+| Discord connector | Outbound Discord gateway/REST, no inbound local listener. Local process could tamper with same-uid files/process | No local port to call. File separation depends on uid and modes | Existing guild, user, channel, bot and webhook checks remain. Discord is not a new bus human transport |
+| Row 190 additions | Separate configs, roots, unit names, wrappers and Console ports, on one uid | Console/tester TCP still reachable | Adds no new class of listener. Row 196 derives its socket per dataRoot. Row 190 alone supplies no hostile-process isolation |
+| Control board, default 7331 | Unauthenticated transcript/board reads, POST /api/reply and /api/seen after request checks | Same loopback reach. A local client can supply matching request headers | Independent development service, outside instance SSO. Inventory only per sage-1345. Its fix needs another row |
+
+Evidence: `packages/webui/src/{cli,serve,bus}.mjs`, `packages/bus/src/{server,runtime,human,
+tester,store}.mjs`, `packages/cli/src/{launcher,git-socket,transport}.mjs`,
+`packages/discord/src/{gateway,authorize}.mjs`, `packages/control-board/src/serve.mjs`.
+Store checks bus/ with `safe(directory,true)`, including owner, symlink and mode checks.
+The dataRoot check itself does not require 0700 today. Do not describe that as a checked mode.
+
+## 3. D1: private tester HTTP socket
+
+Add `serve --tester-socket`, a boolean selecting `<dataRoot>/console/tester.sock`. No arbitrary
+path or new system config field. Create console/ as 0700. Refuse a symlink, wrong owner,
+non-directory or any group/other bits on an existing console/. Refuse a pre-existing socket
+or other entry rather than deleting it blindly. A stale socket needs an operator's diagnosis.
+Refuse a path longer than Linux's 107-byte pathname capacity before binding.
+
+Bind HTTP on the Unix path, set socket mode 0600, then verify type, owner and mode before
+declaring ready. The private parent covers the bind-to-chmod interval. Cleanup only the owned
+device/inode, as broker.sock does. Never open a TCP compatibility bridge or an abstract socket.
+Readiness failure closes the main listener too, rather than leaving a partially started Console.
+
+The tester handler keeps its fixed principal, header/cookie refusals and exact write list.
+Use a fixed logical origin `http://mosaic-tester.invalid` for URL and same-origin checks. It
+does not resolve that name. Clients send that Host and Origin plus the existing Fetch Metadata
+when required. A Host string is not authentication. Unix socket access supplies that boundary.
+The main listener still refuses x-mosaic-tester. No tester /auth route exists.
+
+`bus.tester` remains Jason's switch. Socket reach never enables tester authority by itself.
+Turning it off must refuse every tester bus call. This row adds no user or owner capability
+to the tester. Tester reads retain today's scope, including any local Console reads that are
+not bus calls. This row does not turn bus.tester into a separate HTTP read switch.
+
+### Consumers and migration paths
+
+| Consumer of 7333 | New path |
+|---|---|
+| Agent tester HTTP tools and curl probes in authorized window packets | `curl --unix-socket <dataRoot>/console/tester.sock http://mosaic-tester.invalid/...`, with the fixed Origin for writes. Add one repository helper for bounded tester HTTP requests so callers do not copy path/origin logic |
+| `scripts/mosaic ... --tester` | Already uses TESTER_CLI and broker.sock, not TCP. Keep its verbs, output and switch |
+| Browser tester page in row 176 and later window checks | Ordinary browsers cannot navigate a Unix HTTP socket. Replace automated tester HTTP checks with the socket helper. Browser visual QA uses scratch fixtures only. No local TCP relay is added |
+| `webui-service.sh` render/install and installed unit | Carry --tester-socket for new copies. Refuse a target without support. Units running old copies retain their old flags until a window |
+| `stack-release.sh` activate, plan, rehearsal and rollback | Add --tester-socket. Replace inherited --tester-port N only when explicitly requested. Refuse incompatible inherited flags before stopping units. Plan names the transport and every dropped pair. Rehearsal uses a scratch socket |
+| Gate/window Console checks, including agents' console-check scripts | Extend checks to use scratch Unix HTTP and expect no tester TCP bind. Sage owns live packet updates, including Q175 phase 2's old --tester-port 7333 instructions |
+| `docs/TOOLS.md`, webui/cli/bus READMEs and examples | Document socket invocation, fixed origin, loss of direct browser navigation and per-instance path. Historical window receipts stay unchanged |
+
+Repository search found no non-test hardcoded 7333 caller in tools/ or the harness code. The
+active windows and external seat commands still need Sage's consumer audit before re-pin.
+The build manifest will record the full search, rather than treating this draft as that audit.
+
+## 4. D2: one verified principal per bus request
+
+Internal interface: `verifyPrincipal(request, connection) -> {kind,business,id}` or refusal.
+Kinds are owner, user and tester. The connection metadata is supplied by the trusted server,
+never deserialized from JSON. No role or authority is returned. The broker looks up live policy.
+
+1. Read and validate the bounded envelope first. For human, tester and user proofs, read Linux
+   SO_PEERCRED on that accepted Unix connection before dispatch. Require a valid peer PID
+   and the bus uid. Refuse unavailable credentials, unsupported platform and errors. Cap
+   traffic keeps its capability protocol behind the validated 0700 directory and 0600 socket.
+2. Require exactly one cap, human, tester or future user envelope. Human/tester/user proof.pid
+   must equal the kernel peer PID. Verify startTime, nonce and CLI path against that process.
+   Keep the second process read after the walk. Missing, changed or exited processes refuse.
+3. Owner terminal: run the full existing human walk. Map the business to businesses[b].human.
+   No supplied human id, role or uid selects the principal. Keep today's terminal invocation.
+4. Tester: run verifyTester, retaining its deliberate difference from the human walk. An agent
+   seat may be tester. A managed-run marker or registered managed ancestor refuses. Then check
+   bus.tester. The full human walk must never be weakened to admit a session user.
+5. Session user: use the full human walk with the path-bound user-cli entry and its own nonce
+   variable, MOSAIC_BUS_USER_NONCE. Parameterize the nonce reader without admitting a human
+   or tester nonce as a user proof. Require its immediate parent to be the same tree's resolved webui/src/cli.mjs,
+   argv[2] `serve`. Check parent uid, startTime and ppid again before binding. Both child and
+   parent remain alive for the call. A different checkout or wrapper parent refuses.
+6. For user calls, the Console puts its mapped access-file user id in the verified proof's
+   user field, as federation 3.6 specifies. The id comes only from claims Q175 verified for
+   this request's live session, never from an identity cached past that session. It never
+   takes that id from a form field or verb
+   args. Return kind user, proof.business and proof.user as id only after the provenance
+   checks. R3 then validates that mapping and the live grant. Bad access.json denies users,
+   not the terminal owner. The verifier does not implement access-file policy.
+7. Owner Console calls keep the verified Q175 owner subject path. Under SSO only a subject
+   in console.sso.subjects reaches owner bus calls. They use human-cli and the same peer/walk
+   checks. A terminal owner still needs no SSO token. No anonymous main-listener fallback.
+
+The bus verifies which process supplied the session identity. It relies on that Console's
+Q175 implementation to have verified OIDC. It does not independently verify an ID token in
+this option. A provider/sub field alone, from another process, is not enough.
+
+The Console must spawn user-cli directly with its nonce already in the launch environment.
+It must not use human-cli's existing self-respawn pattern, which makes the CLI's parent a CLI.
+Apply the same initial-nonce spawn to Console human calls for consistent tests. Terminal
+human-cli can retain its self-respawn since no Console-parent condition applies there.
+Never strip agent markers from inherited environments to make a walk pass.
+
+The server binds an internal cap for this request, dispatches, and disconnects in every
+success/error/timeout path, including asynchronous task and web calls. It never returns the
+cap or a reusable principal handle. A proof copied by another process has a different kernel
+peer PID and fails. One verified CLI may make only its one request on its one connection.
+The session may hold s.user for that request. No PID or principal cache survives the connection.
+
+### Fit with rows 193 and R3
+
+Row 196 owns peer metadata, proof/walk verification and the internal principal interface.
+It supplies the Console provenance verifier and tests before R3 adds user-cli and user sessions.
+R3 owns access.json mapping and the bindUser integration, using this interface. It must not
+add a second ancestry implementation. Row 193 adds viewer and share policy to the same live
+grant check. An owner id is the business human. A user id is the access-file id, with stored
+owner string `user:<id>`. Neither row takes role from the proof.
+
+No live grant, unknown subject, duplicate owner/user mapping and invalid access file all
+deny user binding through R3's policy. Per-request authorization, access.reload and the
+30-second recheck remain R3's responsibility. Share visibility uses that check in row 193.
+Binding provenance is not a grant and never widens one. R3's user dispatch must run before
+names falls through to #agent. R3 must not land before this contract and its tests are green.
+Gizmoduck's gizmoduck-0015 and Gander's gander-0007 agree on this split. R3 keeps the reserved
+user-name mutant. Row 196 tests kind separation even if a user id resembles the owner name.
+
+### OIDC alternative
+
+The bus could verify the signed ID token itself and map its issuer/sub. That reduces reliance
+on the Console's subject assertion, but requires JWKS/provider handling, nonce or challenge
+binding, replay handling, login and logout/session lifetimes in the bus. Reusing an ID token
+on every request either creates a replay credential or expires a Console session with the
+token. A bus-issued session needs a separate lifecycle design. It also leaves the terminal
+owner and hostile same-uid limit intact. Recommend the Console provenance contract for this
+slice. Duckworth approved this option in duckworth-0006, with the live-session condition above
+and the requirement to carry section 8 R2 into P19 333 word for word.
+
+## 5. D3: obtaining kernel credentials, O1 approved with conditions
+
+All options must bind the accepted connection, not a PID a caller picked. None gets a silent
+fallback to the current proof. Sage required this comparison. Duckworth selected O1 in
+duckworth-0006, with the interpreter, proof-only and image conditions below. O4 remains the
+fallback if Python is unavailable, and needs a revised build manifest before use.
+
+| Option | What it proves and costs | Recommendation |
+|---|---|---|
+| O1 Python stdlib helper on inherited accepted socket | Node passes the accepted net.Socket as fd 3 using documented spawn stdio stream passing. Python socket(fileno=3) reads SO_PEERCRED and returns only pid,uid,gid on stdout. No socket reads, no shell, no credential values. Adds Python to bus hosts and any future bus image, with a process per admitted proof connection. Copies carry the helper and depend on the system interpreter | Selected by Duckworth, with conditions below |
+| O2 /proc/net/unix plus inode and /proc/PID/fd scans | The table identifies Unix socket entries, not an authenticated peer PID for each accepted connection. Finding a process holding an inode is racy, may have several holders and can be unreadable. The server endpoint's inode is not the client's inode | Reject as a replacement for SO_PEERCRED. No claimed proof PID may choose the scan target |
+| O3 plain Node fd passing or abstract sockets | A private inherited IPC channel can authenticate a child that this parent spawned. The bus did not spawn the independently started Console or terminal CLI. Moving the bus into the Console's child tree changes lifecycle and ownership. An abstract name supplies no filesystem mode boundary and no peer uid check by itself. Node's public net API supplies no SO_PEERCRED accessor | Reject as a drop-in. A larger bus-spawned transport design could use fd capabilities, but is outside this slice |
+| O4 small compiled helper or Node-API addon | Calls getsockopt directly, with no Python runtime. A helper can use the same inherited fd. Adds compiler/build closure and platform artifacts to stack-copy and containers. An addon also needs a supported way to obtain the accepted socket fd and Node version coverage | Viable alternative if Python is refused. Prefer a small helper over undocumented Node handles |
+
+For O1, pin the system interpreter `/usr/bin/python3`, resolving its system symlink to an
+absolute ELF binary. Require root ownership and no group/other write on that executable and
+its path components. Refuse scripts, PATH shims and any resolved path under an OS account's
+home, including /home and /root. A pyenv shim can choose an interpreter before -I -S applies.
+No PATH lookup, caller-selected interpreter or helper. Invoke the resolved binary with
+`-I -S`, a minimal environment and the absolute helper path in the same pinned copy.
+
+Activation preflight records the interpreter's resolved path, version and file identity/hash
+in its gate evidence. The bus validates and pins the resolved executable at each startup
+before opening broker.sock. The activation gate must report the same interpreter used by
+that bus. Missing, unsafe or changed resolution during that activation refuses it, never
+falling back to PATH. No secret values are recorded. Test system-owned interpreter checks
+through injected metadata.
+
+N5 decision: a later bus restart repeats the safety/version/support checks and accepts a
+safe system interpreter installed by an OS upgrade. It does not compare against an old
+activation hash. Before opening the listener, append a startup receipt with timestamp,
+copy path, resolved interpreter path, version and file identity/hash to
+`<dataRoot>/bus/peercred-starts.jsonl` (0600 in the checked 0700 bus directory). Refuse an
+unsafe receipt file or failed append. Never edit the old activation evidence. The startup
+receipt identifies the binary now in use, so the old receipt remains a historical fact.
+If an upgraded interpreter fails the checks, startup fails closed until a safe supported
+system interpreter is restored by the operator. There is no shim or O4 auto-fallback.
+
+Operator re-pin after an interpreter change: in the next authorized window, prepare the
+next reviewed copy with `scripts/stack-copy.sh copy NEW`, then run
+`scripts/stack-release.sh activate NEW BUSINESS --tester-socket` with that instance's existing
+flags and selector, first with --plan. NEW must differ from the active copy because activate
+refuses already-active. Record the interpreter in the new activation evidence and compare it
+with the bus startup receipt. A routine OS update alone does not authorize a re-pin or unit
+restart. A bus restart does not rewrite config, pointer or activation history.
+
+Preflight helper and SO_PEERCRED support too. The helper lives under packages/bus/src so
+stack-copy's closure includes it. Copies remain immutable. Document Python >=3.10 on bus
+hosts. Today's Containerfile builds the worker image and runs run-agent.sh, not the bus.
+It needs no Python change for this row. A future bus-host image must explicitly include
+the pinned system Python or use reviewed O4. No install through the node_modules symlink.
+
+Pause each proof connection while reading credentials. Limit outstanding helpers
+to 16, timeout to one second, output to one strict JSON record of at most 256 bytes. Refuse
+nonzero exit, extra output, malformed integers, missing fd and timeout. Validate pid, uid and
+gid as safe integers, pid >=2 and uid/gid >=0. Only pid and uid select the principal. gid is
+validated but grants no authority. Kill and reap helpers on shutdown. Cap envelopes never
+spawn this helper. Reading the proof envelope first is sound because SO_PEERCRED describes
+the peer at connect time. Keep the accepted Socket object owned by its connection closure,
+not a shared current-fd variable. Only the helper's duplicate fd is closed when it exits.
+
+References: [Node stdio stream passing](https://nodejs.org/api/child_process.html#optionsstdio),
+[Node Unix socket support](https://nodejs.org/api/net.html#ipc-support),
+[Python socket and getsockopt](https://docs.python.org/3/library/socket.html),
+[Linux Unix credentials and permissions](https://man7.org/linux/man-pages/man7/unix.7.html),
+[Linux proc network table fields](https://man7.org/linux/man-pages/man5/proc_pid_net.5.html).
+These support the APIs. The connection-binding behavior still needs T2 on supported Node versions.
+
+## 6. Migration and rollback
+
+No config schema or store schema changes. Old copies and units keep working until each
+instance re-pins. No new verifier is loaded into a running old broker. Do not pair a new
+Console with an old bus and call it protected. Same-tree paths intentionally refuse mixtures.
+
+The authorized window must pin bus, Console and human wrapper to one candidate. New tools
+offer `activate ID BUSINESS --tester-socket`. Plan must show the old tester-port pair removed
+and the new socket flag added, and tell Jason that direct tester browser navigation is lost.
+Mos accepted that change in mos-1015 (sage-1363). Agents test through the socket. A later
+authenticated browser relay behind SSO belongs to its own row. Without the explicit
+conversion, a candidate that no longer
+serves tester TCP refuses inherited --tester-port before stopping anything. New serve refuses
+--tester-port with a migration error. It never silently changes that flag's meaning.
+
+Rollback to a copy lacking --tester-socket drops tester enablement and reports it, as today's
+tools drop unsupported flags. It does not turn the socket back into TCP. The old main Console
+and owner CLI can run with their known old limits. A failed activation's recovery may restore
+the old saved unit, including its TCP listener. Report that recovery as restoration of the old
+security state, never as a hardened deployment. After rollback, R3 and second-human access are
+not accepted until prerequisites are restored. Older operator tools cannot manage the new
+flag safely. The window must use the reviewed candidate tool blob for rollback as well.
+
+The Q173 window supplies real uid-denial evidence and the final consumer audit. No second uid,
+live socket, unit, config or secret is touched in this row's tests. Row 190b or a separate host
+still owns cross-instance file isolation. It is not replaced by SSO or this socket change.
+
+## 7. Acceptance tests and mutants
+
+All fixtures use scratch roots and ephemeral sockets, no live 7332/7333, public origin or
+provider. No real second uid. Foreign uid checks use injected metadata and name that limit.
+Use short TMPDIR paths so the longest Unix socket path stays under 108 bytes.
+
+| Test | Required evidence | Mutant killed |
+|---|---|---|
+| T1 private tester | HTTP over scratch socket reads and writes as tester only. parent 0700, socket 0600. No tester TCP listen. Wrong Host/origin and auth cookies refuse | M1 bind loopback TCP as well, M2 remove socket mode check, M3 accept owner cookie |
+| T2 real peer binding | At least 8 concurrent proof connections from distinct scratch client processes, each with its own live proof, plus a copier racing one live CLI. Barrier the helpers so connections overlap. Each genuine call must bind its own peer PID and pass, the copier must refuse. Repeat on Node 24 and 26. A lower-level helper fixture exchanges bytes both ways on the accepted socket after the helper exits, and each real bus call receives its response after helper exit. Helper failure cases all refuse | M4 use proof.pid as peer PID, M5 continue after helper error, M20 give the helper another pending connection's socket |
+| T3 uid/path refusal | Inject foreign peer uid, wrong file owner/modes, symlink parent, existing socket and long path. Inject interpreter script, user-owned ELF, home path, writable ancestor and missing executable. Refuse before dispatch, no repaired paths. Unsafe pid/uid/gid and extra helper output refuse | M6 ignore uid, M7 accept unsafe parent |
+| T4 ancestry | Agent env, binary and registered launch above owner/user refuse. Missing/reused PID, changed parent and cycles refuse. Clean terminal owner works | M8 omit walk, M9 omit identity re-read |
+| T5 Console parent | Direct CLI child from exact tree Console fixture works. Same CLI under shell, other copy, wrapper, agent ancestor or CLI respawn refuses | M10 remove direct-parent check, M11 accept any Console basename |
+| T6 principal shape | No human id or role from request body. Exactly one proof. No returned cap. Disconnect on synchronous and async failure, timeout and close. Tester agent allowed, managed tester refused | M12 accept extra identity, M13 omit disconnect, M14 use tester walk for user |
+| T7 consumer migration | Render/plan/activate/rehearse fixture carries socket flag in unit and pointer. Explicit conversion removes port. Unsupported/inherited mismatch refuses before unit calls. Rollback disables unsupported tester, never opens TCP | M15 keep inherited tester port, M16 restore TCP on downgrade |
+| T8 gates and identity | bus.tester false refuses tester calls. SSO owner/user wiring uses only claims verified for that request's live session. Expired/logged-out or replaced session cannot reuse an earlier mapped id. User kind never becomes owner from its id. R3 integration maps subject, denies missing/invalid grants and owner overlap, broken access file leaves terminal owner working | M17 bypass tester switch, M18 turn user kind into owner by id |
+| T9 isolation limits | Two scratch instances have different sockets and matching tree paths. Foreign-uid stand-in refuses. Record that no real uid boundary was exercised | M19 choose default instance socket |
+| T10 interpreter and cap path | Activation evidence records the same pinned root-owned system ELF that the bus uses. Scripts, home paths and unsafe owners/modes refuse. Simulated OS replacement followed by startup accepts a safe replacement and appends its actual identity without changing the old receipt, refuses an unsafe replacement or unsafe/unwritable receipt. Cap calls complete without invoking the helper, proven with a helper spy that fails if called | M21 bypass interpreter safety, M22 invoke helper for cap traffic, M23 retain stale interpreter identity after restart |
+
+Tests for new policy stay in the bus, WebUI and CLI packages. R3 provides the real user/grant
+half of T8 in its candidate, with its own gate. This row tests the shared verifier's user
+provenance without shipping placeholder user access. Mutants run on scratch copies,
+restore the original bytes and verify hashes. Two failures in a gate run stop and are reported.
+Single test files run freely. Ask Sage for the slot before any suite. Final acceptance is
+Duckworth's approved manifest plus Sage's bus, WebUI, CLI and scripts/test-*.sh gate.
+
+## 8. Closure, limits and review decisions
+
+R1. Same uid remains trusted OS authority. A hostile process may detach, clear its markers,
+modify argv, read same-uid pipes or capabilities, edit policy files, or interfere with the
+Console where host policy permits. SO_PEERCRED proves the connecting process identity at
+connection time. It does not prove human intent, protect memory, or track a socket passed to
+another process. Ordinary agent children fail the walk. Hostile detached agents are not
+claimed contained. Separate uids narrow cross-instance reach, not reach within one instance.
+
+R2. The Console provenance option trusts verified code and process metadata, not an independent
+bus-side OIDC exchange. That trade must be approved, not hidden behind the phrase zero trust.
+
+R3. A Unix tester endpoint removes direct browser navigation. No bridge is in this design.
+The 7331 development board remains a separately reported reachability and impersonation risk.
+
+P19 333 can record the following after the implementation gate and authorized re-pin:
+"Tester ingress is private to the instance uid. Bus human proofs are tied to the actual
+Unix peer and retain the human walk. Session-user calls require the same-tree Console as
+direct parent. Q175 phase 2 separately protects main Console ingress with verified OIDC.
+Hostile processes on the instance uid, root, and the independent development control board
+remain outside these guarantees. Cross-instance file isolation requires the uid/host gate."
+
+Duckworth requires that P19 333 also carry R2 word for word:
+"The Console provenance option trusts verified code and process metadata, not an independent
+bus-side OIDC exchange. That trade must be approved, not hidden behind the phrase zero trust."
+
+Do not mark the historical task fully closed on a design or commit. Closure needs live
+Q175 phase 2, this row's re-pin and the recorded residual accepted through Mos. A promise of
+hostile same-uid isolation would require separate OS authority for agents and a new design.
+
+Review receipt: duckworth-0006, notes at `86be181a2:agents/duckworth/work/row196/REVIEW.md`.
+Q1 selects O1 with the conditions incorporated in section 5. Q2 approves Console provenance
+with the live-session and unchanged P19 R2 conditions. B1 adds concurrent T2, M20 and socket
+survival checks. N2's detached-Console limit remains in R1. N3's gid validation and N4's
+operator window warning are included. Mos's tester-access ruling is recorded above. No
+product code begins before design approval.
+Duckworth approved revision 2 in duckworth-0009, review at
+`cb6d840df:agents/duckworth/work/row196/REVIEW-r2.md`. N5 permits either restart policy.
+Revision 3 selects safety revalidation with a new append-only startup receipt, and gives the
+operator a re-pin path that respects the existing already-active refusal.

agents/gander/work/queue-196/PLAN.md

@@ -0,0 +1,121 @@
+# Row 196 Human Boundary Implementation Plan
+
+> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox syntax for tracking.
+
+**Goal:** Bind human proofs to their actual Unix peers and make tester HTTP private to the instance uid.
+
+**Architecture:** The bus reads kernel credentials through a pinned system Python helper only for proof envelopes. One principal verifier keeps the human walk and supplies Console provenance for federation R3. Tester HTTP moves to a private filesystem socket. Release tools migrate the flags explicitly.
+
+**Tech Stack:** Linux, Node 24 and 26, Python >=3.10 standard library, existing Node test runner and shell release tools.
+
+**Spec:** `agents/gander/work/queue-196/DESIGN.md`, approved r2 at 5fe259f16, with N5 restart policy added in r3.
+
+## Global Constraints
+
+- Work in the existing gander/row196 worktree. Plain node_modules symlink. No new package dependency.
+- No live files, credentials, listeners, units, second uid or external authentication service.
+- Helpers: proof envelopes only, at most 16 concurrent, one second timeout, 256-byte strict output.
+- Root-owned system Python ELF at resolved /usr/bin/python3, never PATH or a home/shim path.
+- console/ 0700, tester.sock 0600, Unix pathname at most 107 bytes.
+- One principal and transient cap per request. R3 owns user access policy and user-cli integration.
+- Mos accepted socket-only tester access. No TCP relay or control-board change.
+- Single test files run freely. Ask Sage before any suite. Stop and report two failures in a gate run.
+- Commit code only after applicable suites pass. Sage owns the final gate and manifest queue moves.
+
+## Review Focus
+
+- Connection overlap and disconnect: helpers must retain the correct Socket object and release capacity on every exit.
+- OS interpreter replacement: restart records the actual safe binary, while old receipts remain unchanged.
+- Long or unsafe instance paths: refuse before binding or stopping any service.
+- Rollback/recovery: distinguish intentional tester disablement from restoration of an old saved TCP unit.
+- CLI nonce respawn and session expiry: direct-parent provenance must survive correct Console spawning and refuse stale identity.
+
+## Task 1: kernel credentials and interpreter evidence
+
+Files: create `packages/bus/src/peercred.mjs`, `packages/bus/src/peercred.py`,
+`packages/bus/src/interpreter.mjs`; tests in `packages/bus/tests/peercred.test.mjs` and
+`packages/bus/tests/interpreter.test.mjs`, with subprocess fixtures under `packages/bus/fixtures/`.
+
+Interfaces: `inspectInterpreter()` returns a validated immutable record of path, version,
+device, inode and sha256. `recordInterpreterStart(directory, record)` appends the actual startup
+identity safely. `createPeerReader({interpreter})` returns `{read(socket),close()}`. read resolves
+to `{pid,uid,gid}` from that exact socket, or refuses. Test-only injected OS/process operations
+do not become product flags or environment overrides.
+
+- [ ] Write interpreter safety, receipt replacement and cap-independent helper tests (T3/T10).
+- [ ] Run each new test file alone and record the expected missing-module failures.
+- [ ] Implement system interpreter validation and startup receipt append with no-follow, owner/type/mode checks.
+- [ ] Write T2's eight-process barrier plus racing copier, wrong-fd case and post-helper socket exchange.
+- [ ] Implement fd-3 helper, strict result validation, bounded async reader and helper shutdown.
+- [ ] Run `node --test packages/bus/tests/interpreter.test.mjs` and separately `node --test packages/bus/tests/peercred.test.mjs`.
+- [ ] Confirm process/socket cleanup, eight distinct kernel PIDs, copier refusal and original receipt preservation.
+
+## Task 2: principal provenance and bus dispatch
+
+Files: modify `packages/bus/src/{human,tester,server,runtime}.mjs`, create
+`packages/bus/src/principal.mjs`, add `packages/bus/tests/principal.test.mjs`, and extend
+`packages/bus/tests/human.test.mjs`. Extend server/runtime test files after inspecting their fixtures.
+
+Interfaces: `verifyPrincipal(request, {peer,...trustedPathsAndProcessReaders})` returns
+`{kind,business,id}`. Human maps to the business human, tester to tester, user to its verified
+Console proof id. No roles or grants. Server obtains peer metadata from Task 1 only after
+envelope validation and only for proofs. Existing cap dispatch never invokes the helper.
+Future user binding stays refused without R3's trusted integration.
+
+- [ ] Write T4/T5/T6/T8 process-table tests, including changed ancestry, distinct nonce namespaces and kind confusion.
+- [ ] Run the focused new file and confirm expected failure before implementing the verifier.
+- [ ] Parameterize the nonce/path portion of the existing human walk and retain all marker/binary/launch checks.
+- [ ] Wire peer metadata, interpreter startup receipt and one-request cleanup into runtime/server.
+- [ ] Test cap requests with a failing helper spy (M22), and test async refusal/close cleanup.
+- [ ] Run each affected bus test file alone. Record any base fixture changes needed for real peer identity.
+
+## Task 3: tester Unix HTTP and Console nonce spawning
+
+Files: modify `packages/webui/src/{cli,serve,bus}.mjs`, create
+`packages/webui/src/tester-socket.mjs` and `packages/cli/src/tester-http.mjs`; add focused
+`packages/webui/tests/tester-socket.test.mjs` and `packages/cli/tests/tester-http.test.mjs`.
+Extend existing WebUI transport tests.
+
+Interfaces: `startTesterSocket({dataRoot,...handlerOptions})` owns the private listener and
+cleanup. `testerRequest({dataRoot,method,path,body})` uses the fixed logical origin and bounded
+Unix HTTP. Console human child spawning supplies its initial nonce, preserving agent markers.
+R3 reuses that spawn pattern for its user-cli.
+
+- [ ] Write T1/T3/T9 socket permission, unsafe-path, wrong-origin and instance separation tests.
+- [ ] Confirm the new focused files fail, then implement --tester-socket and refusal of --tester-port.
+- [ ] Keep tester principal, write allowlist and cookie/header refusals intact. Add no browser relay.
+- [ ] Write and implement the initial-nonce Console spawn test and the helper request timeout test.
+- [ ] Run each new or changed test file alone, verifying cleanup and no tester TCP bind.
+
+## Task 4: release migration and operator evidence
+
+Files: modify `scripts/{webui-service,stack-release}.sh`, inspect
+`scripts/stack-copy.sh` closure, extend `packages/cli/tests/stack-release.test.mjs` and its
+render fixtures. Update `docs/TOOLS.md` and package READMEs with the implementation.
+
+Interfaces: `activate ID BUSINESS --tester-socket` explicitly replaces inherited tester-port
+flags. Pointer and unit argv agree. Candidate support and interpreter preflight run before
+any unit stop. Activation gate evidence records the same interpreter as the bus startup receipt.
+
+- [ ] Write T7 explicit conversion, inherited mismatch and unsupported-target refusal fixtures.
+- [ ] Run only the affected test file, then implement flag rendering, plan output and rollback disabling unsupported tester.
+- [ ] Preserve old-copy recovery behavior and report restored old security state accurately.
+- [ ] Add rehearsal scratch socket and T10 interpreter gate identity comparison.
+- [ ] Verify same-copy activation refusal is preserved. Document N5's next-reviewed-copy re-pin path.
+- [ ] Run the affected file alone, shell syntax checks, and inspect remaining tester-port references by purpose.
+
+## Task 5: mutants, approved suites and manifest
+
+Files: add the row's mutation runner and receipts under `agents/gander/work/queue-196/`.
+Append BUILD-LOG phase receipts. No SESSIONS or queue file edits.
+
+- [ ] Exercise M1-M23 against isolated scratch copies. Record killer test, restored hash and cleanup for each.
+- [ ] Run focused tests on Node 24 and 26, including the concurrent T2 case and socket lifetime checks.
+- [ ] Send Sage the scope and estimated duration, obtain the suite slot, then run approved bus/WebUI/CLI suites.
+- [ ] Let Sage own the scripts/test-*.sh gate. Stop on the repository's two-failure rule.
+- [ ] Build the exact changed-path manifest with acceptance evidence, search results, limits and consumer audit.
+- [ ] Commit/push the verified candidate only after applicable suites pass. Send Duckworth and Sage path, commit and hashes for manifest review.
+
+Execution stays with Gander in this worktree. No new agent delegation. Duckworth reviews
+the manifest independently. Push is only to gander/row196. No merge, re-pin or deployment
+is authorized by this plan.

agents/honker/README.md

@@ -0,0 +1,7 @@
+# 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

@@ -0,0 +1,7 @@
+# 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

@@ -0,0 +1,7 @@
+# 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/q175-sso/DESIGN.md

@@ -1,8 +1,42 @@
 # Q175 design: the Console verifies SSO itself (Vikunja #412)
 
-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`.
+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.
 
 ## The ruling this implements
 
@@ -22,7 +56,9 @@ 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`.
+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.
 
 - `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
@@ -45,41 +81,73 @@ 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`. |
+| `/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/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 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`.
+   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`.
 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.
+   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.
 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)`, 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`.
+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.
 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)` 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 `/`.
+   `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 `/`.
 
 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
@@ -103,34 +171,78 @@ 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 and logout
+### 3. Sessions, cookies, Host and logout
 
-- 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.
+- 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.
 - 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. 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.
+- 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.
 - 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=https://mosaic.woltje.com/auth/signed-out&client_id=...`.
+  303s to `end_session_endpoint?id_token_hint=...&post_logout_redirect_uri=<publicOrigin>/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
@@ -151,38 +263,54 @@ No secret value goes in this file. The client secret is a slot reference.
 }
 ```
 
-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.**
+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`.
 
-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.
+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.
 
-`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.
+`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.
 
-Startup checks for each provider, all fail-closed (the Console doesn't start, and the message names the
-provider and the check):
+Config checks, run at start without the network. Any failure refuses the start, and the message names the
+provider and the check:
 
-- `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.
+- `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.
 - `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}`.
 
-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.
+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.
 
 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.
@@ -190,13 +318,48 @@ 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
-   the business file. `--sso` cannot be combined with `--auth-header`, `--allow-user` or `--proof-*`. Under
+   config.json. `--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. Nothing live changes until the re-pin.
+   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).
 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 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.
+   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.
 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.
@@ -211,13 +374,15 @@ 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 an entry named `tester`.
+- `subjects` validation refuses a `name` of `tester` or `human`.
 
 ### 7. Point 5, the proxy-forwarded token
 
@@ -225,7 +390,9 @@ 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, aud (the proxy provider's client id), exp and subject list.
+- 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).
 - 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).
 
@@ -237,9 +404,11 @@ 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).
 
-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.
+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.
 
 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
@@ -249,11 +418,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). 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). 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.
 
 Refusals Mos named:
 
@@ -261,35 +430,87 @@ 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.
-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.
+   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.
 
 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.
+   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.
 8. A provider that demands no PKCE. The token request must carry `code_verifier`, and the fake OP refuses a
    wrong one.
-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`.
+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.
 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.
+    and `X-authentik-jwt` each get 403. `/auth/login` on 7333 gets 404. `startServer` with `tester` and `sso`
+    throws.
 13. Session: idle expiry, absolute expiry, a logout followed by reuse of the old cookie, and logout without
-    same-origin (refused, session kept).
-14. Open redirect: `return=//evil.example` and `return=https://evil.example` both land on `/`.
+    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.
 
 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: 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.
+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).
 
 ### 10. Jason-gated steps
 
@@ -300,16 +521,21 @@ cookies, and skip the login record delete.
    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 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
+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
    later, so the Console is the only gate, changes who can reach the Console from outside and is his call.
-5. The phase 2 re-pin window go.
+6. The phase 2 re-pin window go.
 
 ## Questions for review
 
-- 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.
+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.

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

@@ -0,0 +1,7 @@
+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

@@ -0,0 +1,48 @@
+# 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

@@ -0,0 +1,56 @@
+// 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

@@ -0,0 +1,56 @@
+// 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

@@ -0,0 +1,12 @@
+{
+ "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

@@ -0,0 +1,20 @@
+{
+ "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

@@ -0,0 +1,7 @@
+# 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,3 +1357,9 @@ 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)

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

@@ -0,0 +1,72 @@
+# 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

@@ -0,0 +1,47 @@
+# 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

@@ -0,0 +1,46 @@
+# Brief: Melanie's hub instance under its own Linux user (row 190b)
+
+Sage, 2026-10-20, from Darkwing's draft (agents/darkwing/work/queue-190b/BRIEF-DRAFT.md) for Mos's ruling
+mos-0986 (2026-10-20T18:53:48Z) on row 190 R1. Mos ruled a separate uid per instance a hard precondition of
+federation R8 (mos-0984, mos-0985) and of Case 2 row C2-13. The finding was federation review B5
+(duckworth-0001): on one uid any factory agent can read, write and control Melanie's hub directly, and SSO and
+RBAC don't stop a local process with filesystem access. On the 10-27 MVP path. Gitea #1693.
+
+Owner Darkwing (Opus 5.5), reviewer Duckworth (author of B5; mos-0981 keeps new work off Filbert and Dewey),
+gate owner Sage. Merge-chained on row 190 (Q177): it builds on row 190's candidate and keeps its own review and
+gate. Design first. The first deliverable is `agents/darkwing/work/queue-190b/DESIGN.md`.
+
+## Goal
+
+Melanie's hub instance runs under its own Linux user. No process of the factory instance can read or write the
+hub's config, data root or secrets, or control the hub's units. That covers the bus, role seats and their
+sessions, task runs, the Discord connector and the Console.
+
+## The design must state
+
+1. How operators (Mos, Sage, Jason) deploy, re-pin and roll back the hub. Which commands they run, as which
+   user, and what each one needs.
+2. Each root step Jason runs: useradd, the home and its modes, `loginctl enable-linger`, and any sudoers rule,
+   with the exact command lines.
+3. How the hub reaches the Claude proxy and gets its session env without sharing jwoltje's
+   `claude-session.env`.
+4. Whether real isolation needs the factory instance's seats to run apart from the operators' uid. If yes, say
+   so plainly with its cost. Don't design around it.
+
+It must also cover the copies (shared read-only trees under jwoltje's home, or the hub's own), the human CLI
+wrapper and human proof for the hub's Console, and how the stack-release pointer, log and backups work under
+the second user.
+
+## Boundaries
+
+- Row 190 lands first, as designed: one uid, scratch two-instance tests without root.
+- No agent runs a root step. Every one goes to Jason as an exact command list.
+- No real hub user, unit or data root is created in this row's tests. Tests use scratch roots and stand-ins as
+  row 190 does. Anything that needs a second real uid is a Q173 window with a backup first and a STATE report
+  after.
+- No tunnel or Traefik exposure. That waits for Jason, after Q175 SSO.
+
+## Gate
+
+Duckworth approves DESIGN.md, then the manifest. The cli suite and every `scripts/test-*.sh` are green on
+Sage's gate. The design's mutants are killed.

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

@@ -0,0 +1,62 @@
+# 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

@@ -0,0 +1,56 @@
+# 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

@@ -0,0 +1,65 @@
+# 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

@@ -0,0 +1,70 @@
+# 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_sso-phase1.md

@@ -0,0 +1,47 @@
+# 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 2236 by `queue render`. Do not edit between the markers; change the queue with `scripts/mosaic queue`.
+Generated from `docs/plans/queue.json` revision 2247 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,6 +225,9 @@ Generated from `docs/plans/queue.json` revision 2236 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": 2236,
+  "revision": 2247,
   "rows": [
     {
       "id": 1,
@@ -19820,6 +19820,153 @@
       "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": [
@@ -78756,6 +78903,329 @@
         "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"
     }
   ]
 }