gosalyn: C2-01 packages/library, mapping, scope, commit reader with R1-R7, link resolver, renderItems, library survey (row 212, #416)

agents/README.md

@@ -16,6 +16,17 @@ not fleet seats. Keep changes in `/mnt/storage/src/mosaic-stack`; do not modify
 | Rocko | General development, investigation, testing, and review | T3 session (Codex, gpt-6.1-sol, thread d99326cc, lead decision 122; Claude thread b84bb264 retired 2026-10-12); launcher Claude Code, Sonnet model | `agents/rocko/launch.sh` |
 | Filbert | General development, investigation, testing, and review | T3 session (Claude, Opus 5.5, thread 048f3c63, non-sandbox reviews only, lead decisions 130 and 134; Codex threads f712d8af and 50342f6a retired 2026-10-13, Claude thread 9cb9731e retired 2026-10-12); launcher Pi, `openai-codex/gpt-6-astra:low`, not to be used under R26 until it changes (lead decision 69) | `agents/filbert/launch.sh` |
 | Researcher | Source-grounded technical research and evidence | T3 session (Claude, Sonnet 5.5, thread 9bac0794, rows 97 and 98, lead decision 124); Haiku rows (71, 80, 84, 88, later 96) run as subagents Sage dispatches with model haiku, effort high and a worktree (lead decision 129); Haiku thread c98aaf4a retired 2026-10-13 unused; launcher Pi, configured Mosaic model | `agents/researcher/launch.sh` |
+| Launchpad | Builder, MVP T1 row 192 (Q175 SSO phase 1) | T3 session (Claude, Opus 5.5), started by Sage under mos-0974/0977 | none, T3 only |
+| Morgana | Builder, MVP T1 row 193 (human users and RBAC) | T3 session (Claude, Opus 5.5), started by Sage under mos-0974/0977 | none, T3 only |
+| Honker | Builder, MVP T1 row 194 (agent lifecycle) | T3 session (Claude, Opus 5.5), started by Sage under mos-0974/0977 | none, T3 only |
+| Gander | Builder, the human boundary across uids (P19 333, #1694) | T3 session (Codex, gpt-6.1-sol), started by Sage under mos-0977 | none, T3 only |
+| Herb | Builder, a second gate lane (#1695) | T3 session (Codex, gpt-6.1-sol), started by Sage under mos-0977 | none, T3 only |
+| Bushroot | Builder, retire the control board writer on 7331 (#1696) | T3 session (Claude, claude-haiku-5-5), started by Sage under mos-1008 | none, T3 only |
+| Megavolt | Builder, MVP T1 item 6 (agent credentials and git identity, #1697) | T3 session (Claude, Opus 5.5), started by Sage under mos-0974/0977 | none, T3 only |
+| Quackerjack | Builder, federation R5 and R2 (#414) | T3 session (Claude, claude-haiku-5-5), started by Sage under mos-1023 | none, T3 only |
+| Gizmoduck | Federation design (#414) and builder of FED R1 | T3 session (Claude, Opus 5.5, thread 9312a896) | none, T3 only |
+| Webby | Reviewer: Case 2 designs, rows 192 and 194 | T3 session (Claude, Opus 5.5, thread 03086006), started by Mos (mos-0981) | none, T3 only |
+| Duckworth | Reviewer: federation designs, row 193 | T3 session (Claude, Opus 5.5, thread ffceafec), started by Mos (mos-0977) | none, T3 only |
 | Sage | Project lead: coordination, review, integration; earlier DYOR strategy records retained | T3 session (Claude Code); Pi launcher `zai/glm-5.3:high` retained | `agents/sage/launch.sh` |
 
 Each script supports `--check` and `--fresh`. Normal launches resume the agent's

agents/bushroot/README.md

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

agents/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/gizmoduck/README.md

@@ -0,0 +1,9 @@
+# Gizmoduck
+
+Design and builder seat, Claude Opus 5.5, a T3 thread (9312a896). Author of the federation design
+(`agents/gizmoduck/work/federation/DESIGN.md` on `gizmoduck/federation-design`, #414). Builds FED R1, the
+access.json loader and validator, under Mos's order mos-1023 item 1.
+
+No launcher in this directory. The seat works in its own worktree and has no credentials of its own; until
+the credentials row settles per-agent identity, it pushes only its own `gizmoduck/*` branches through the
+repository credential helper (mos-0981), never `refactor`, `main` or another seat's branch.

agents/gosalyn/README.md

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

agents/herb/README.md

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

agents/honker/README.md

@@ -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/honker/work/queue-194/PRD-1.7-DRAFT.md

@@ -0,0 +1,158 @@
+# PRD 1.7 draft: the chief of staff's hire and fire authority, the coder's push to its fork, and agent
+# host access through the credential store
+
+Draft by Honker for row 194 (#1692), under Mos's ruling mos-1017 (through Sage, sage-1365). Not approved.
+It changes nothing until Jason approves it as a `prd.approve` decision in the Console. Sage opens that
+decision and sends Mos its id. Base: `docs/prd/mosaic-stack.md` version 1.6 at 53bb59462.
+
+## What it changes
+
+Row 194 adds `role.hire` and `role.fire` to the vocabulary, and row 199 adds `git.push.remote`. Under
+REQ-WAIT-3 all three are hard waits, so today Jason resolves every hire, every fire and every push to a
+remote. This version routes hire and fire for the chief of staff within fixed bounds, so the chief hires
+and fires as needed and the user's per-agent forbid still holds. It routes `git.push.remote` for the coder
+only (Mos, mos-1028 item 3). It adds agent host access with sudo through the credential store for
+agents with a grant (Q183, Q184, Vikunja #424, due 2026-10-27). One `prd.approve` decision covers it all
+(Vikunja #420).
+
+When this version lands, a reviewed commit:
+
+1. adds `role.hire`, `role.fire` and `git.push.remote` to `ROUTED` in
+   `packages/business/src/vocabulary.mjs` and in `packages/bus/src/broker.mjs`.
+2. adds `role.hire` and `role.fire` to `roles/chief-of-staff.json` withinRole, and `git.push.remote` to
+   `roles/coder.json` withinRole. No other role file gets `git.push.remote`.
+3. switches the broker's check on `instance.hire` and `instance.fire` from a cited decision to the
+   `reason` form, as `role.end` works for REQ-ROLE-2, and makes `publish`'s `decision` optional for a
+   within-role class (row 199 D9 step 1).
+4. states, for a `git.push.remote` with no decision, where the source commit comes from: the latest work
+   commit the bus recorded for the coder's task. The check still matches it against the work ref tip and
+   the push sends it by oid (row 199, duckworth-0022 N9).
+5. adds the host credential grant check and the host access it allows (REQ-CRED-3, Vikunja #424).
+
+Every other check stays as rows 194 and 199 build it. Filling `hireable` stays a separate reviewed role
+file commit in `roles/`.
+
+## Text for the PRD
+
+Status line, appended to the current paragraph:
+
+> Version 1.7 routes the chief of staff's hire and fire actions and the coder's push to its own fork,
+> and adds agent host access through the credential store, approved by Jason in decision
+> <prd.approve decision id>.
+
+Source, a new bullet above "Version 1.6 source":
+
+> - Version 1.7 source, TARGET.md line 66: "Chief of staff agent has hire/fire authority for agents as
+>   needed; unless user forbids per agent". And Jason through Mos (mos-1067), DECISIONS Q183, in part: "I will
+>   still want to allow infra agent(s) on my .53 instance to access other servers, etc. However, not all
+>   agents will need to have that access. I envision a credential store within Mosaic Stack that works
+>   as some sort of variable for the agent to call. The system will enforce access to the credentials to
+>   keep the agents sandboxed with proper security. I need to be able to trust my agents with assisting
+>   me. This will require sudo access to several systems. If we can utilize the credential store in
+>   Mosaic Stack and allow agents to perform their jobs with NOPASSWD sudo on various machines, I am a
+>   happy man." DECISIONS Q184, on whether that is in place by 10-27: "Q5: by 10.27"
+
+Under "Added in version 1.2", after REQ-COS-2:
+
+> Added in version 1.7:
+>
+> - **REQ-COS-3.** The chief of staff hires and fires role instances without a decision each time. Hiring
+>   adds a role instance to the organization file and lists it for launch. Firing ends the instance's
+>   runs and removes it from the launch list. It stays in the organization file. Only the user deletes
+>   an instance. These actions are `role.hire` and `role.fire`. They leave the hard waits and route
+>   under this requirement, within these bounds:
+>   - The chief acts only in its own organization.
+>   - The chief hires only role definitions that need no credentials, until a later version adds
+>     credentialed roles.
+>   - The chief hires only the role kinds its role file lists. Changing that list is a reviewed commit.
+>   - The chief hires only a role whose every action is on a fixed list of plain work actions: sending
+>     messages, writing records, asking for review, updating its assigned tasks, and the scope and
+>     working-push actions of an assigned task. A role holding any other action, such as launch, end,
+>     organization, naming, hire, review verdict or merge authority, or any action added later, is never
+>     hired. So the chief never hires a chief, never picks its own reviewers or merge gate, and the author
+>     is never the reviewer. This holds whatever the role file's list says. Adding to that list is a PRD
+>     change.
+>   - The chief may set a hired instance's model and narrow its limits, and nothing else about it.
+>   - The user can forbid per agent. The user marks an instance so the chief can't fire it, end its runs
+>     or change its model, and marks role kinds the chief can't hire. Only the user changes these marks, through the
+>     WebUI or the CLI.
+>   - The kill switch stops every hire and fire while it is on.
+>   - Every hire and fire is logged with the chief's instance, its run and the reason.
+
+Under "Landing", after REQ-LAND-1:
+
+> Added in version 1.7:
+>
+> - **REQ-LAND-2.** A coder pushes its own work to its own fork. The action is `git.push.remote`.
+>   - What it pushes: one commit, by its oid, never a ref name. That commit is the latest work commit the
+>     bus recorded for the coder's task, and the coder made that push. A decision that authorizes a push
+>     names that commit, and it doesn't authorize any other.
+>   - Where it lands: only the branch `refs/heads/<its Gitea user>/<branch>`. The host builds that
+>     name, the agent never does. A push never forces.
+>   - Which remote: the agent's own fork of the project's upstream. The business file names the upstream,
+>     and the host never contacts it. For each push the host builds the fork's address over https from
+>     the upstream's host, port and repository name and the agent's own Gitea user. The history check,
+>     the push and the credential match all use that address. So the agent's own user owns the receiving
+>     repository on every push, and the agent never names it.
+>   - The host refuses an upstream on a host or port other than the agent's Gitea, and an upstream the
+>     agent's own user owns. It refuses a fork that is missing, empty or doesn't share the project's
+>     history. Gitea's push-to-create stays off, so a push never creates a repository.
+>   - Who may: the action routes under REQ-DEC-2 and is granted within-role to the coder role only. No
+>     other role file grants it.
+>   - Before version 1.7 the action was a hard wait under REQ-WAIT-3, so each push needed a decision
+>     the human resolved, and that decision named the commit.
+>
+>   Every push is logged with the remote, the ref, the commit and, when one was given, the decision.
+
+Under "Credentials", after REQ-CRED-2:
+
+> Added in version 1.7:
+>
+> - **REQ-CRED-3.** An agent with a grant can run commands with sudo on another host. The agent asks
+>   for the host credential by name. The stack checks that a grant exists for that agent and that host
+>   before the credential is used. The agent never sees the key or any other secret value (REQ-CRED-1,
+>   REQ-VAR-2). An agent without a grant for that host is refused. Not every agent gets a grant. Who
+>   grants a host credential, and how, is set by the #424 design, which Jason approves.
+
+REQ-WAIT-3, appended:
+
+> `role.hire` and `role.fire` were added as hard waits and route under REQ-COS-3 since version 1.7.
+> `git.push.remote` was added as a hard wait and routes under REQ-LAND-2 since version 1.7.
+
+## Notes for the reviewer and for Mos
+
+- REQ-COS-1 (1.2) already says the chief "hires and terminates role instances". REQ-COS-3 gives that
+  sentence its actions and bounds. It doesn't widen REQ-COS-1.
+- The forbid now names what r3 called "replace": ending a kept instance's run with a reason and changing
+  its model (webby-0010 N2). A user-resolved decision still ends a kept run (row 194 D2.4).
+- The fixed list is `HIRE_ALLOWED` in row 194 D2.3, an allowlist since r4 (webby-0010 B1). r3's text
+  named the refused authorities instead, which let merge-gate and any later action through.
+- The kill switch is row 191's. If row 191 hasn't landed when this version is approved, the bound still
+  holds through row 194's chain on its candidate.
+- REQ-LAND-2 follows row 199's design r6 (4d3007ec9 on megavolt/row199, approved by Duckworth in
+  duckworth-0027: D9 to D11, D9a, D9c, Q-M1 and Q-M2, and the oid binding from mos-1034 item 5) and
+  Megavolt's wording in megavolt-0005, megavolt-0008 and megavolt-0014, through Sage (sage-1377,
+  sage-1380, sage-1387). The fork bullet answers duckworth B5 and B6 and webby-0011 N1. Commit-email
+  checks, the refusal codes and the URL parse rules (D9c) are host checks with tests in row 199, not
+  bounds, so they stay out of the text (megavolt-0008).
+- Once the routing lands and the decision is optional for the within-role class, the commit is the task's
+  latest recorded push at check time. It is still checked against the work ref tip and pushed by oid, so
+  the binding holds without a decision (megavolt-0008). Step 4 of "When this version lands" puts that in
+  the routing commit (duckworth-0022 N9, sage-1387).
+- REQ-LAND-2 and REQ-COS-3 meet at the coder. Coder declares Gitea credentials, so REQ-COS-3's
+  credentials bound keeps the chief from hiring one until a later version lifts it. `git.push.remote` isn't
+  on REQ-COS-3's fixed list either, so a coder holding it stays unhireable until a PRD version adds it
+  (row 194 D2.3).
+- Adding to the fixed action list is a PRD change (mos-1035 item 3, sage-1395). The role file's
+  `hireable` list stays a reviewed commit in `roles/`.
+- The credentials bound names no row number, so the text doesn't go stale when row 199 lands. A later
+  version lifts it.
+- REQ-CRED-3 states only what Jason said in Q183 and Q184 (sage-1422). It names the outcome and the
+  check, not how the stack reaches the host. Proxying the ssh and a signing socket are both designs, and
+  the #424 design picks one (duckworth-0038 B1).
+- Open point: Q183 doesn't say who grants host access or how, so the text leaves it open and defines no
+  mechanism. The #424 design settles it, Jason approves that design, and Duckworth reviews it because it
+  gives agents sudo on hosts (Q184, Mos's reading, duckworth-0038 B2). The build is row 210 (#1707,
+  owner Gizmoduck), a new row on top of row 199 (megavolt-0019, sage-1430).
+- This draft follows the PRD's own style: plain words, no semicolons in new sentences, and the status
+  paragraph never edited in place except to append.

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/megavolt/README.md

@@ -0,0 +1,8 @@
+# Megavolt
+
+Builder seat, Claude Opus 5.5, started by Sage under mos-0974 and mos-0977 item 5 for MVP T1 item 6, the
+credential store per agent with its own git identity (#1697).
+
+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 `megavolt/*`
+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/quackerjack/README.md

@@ -0,0 +1,10 @@
+# Quackerjack
+
+Builder seat, Claude Haiku 5.5 at high effort, started by Sage under mos-1023 item 1 and Q177 for federation
+rows R5 (`mosaic access list, grant, revoke`) and R2 (the `federation` config key), per Gizmoduck's design
+section 7 (#414).
+
+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
+`quackerjack/*` branches through the repository credential helper (mos-0981), never `refactor`, `main` or
+another seat's branch.

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

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

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

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

agents/sage/work/gate-lane/timing-g189.md

@@ -0,0 +1,36 @@
+# Row 189 gate timing (for row 197, Herb)
+
+Sage, 2026-10-20T19:25:04Z. Gate on 0c177e9ef (base 0217b71c8), one lane. The slot was mine. Seats may have run single test files at the same time, which the slot rules allow, and I did not record that.
+Start 2026-10-20T19:09:37Z, end 2026-10-20T19:20:36Z. Total wall time: 659 s.
+
+Wall time per suite is the gap between one suite's log mtime and the one before it (the first suite starts at start.txt), so it includes node start-up. node's duration_ms is listed where the suite prints it. Scripts print no duration.
+
+| Suite | Wall s | duration_ms s | Ended (UTC) |
+|---|---|---|---|
+| pkg-bus | 3 | 3.8 | 19:09:40 |
+| pkg-business | 3 | 2.2 | 19:09:43 |
+| pkg-cli | 388 | 388.5 | 19:16:11 |
+| pkg-control-board | 1 | 0.8 | 19:16:12 |
+| pkg-conversation | 35 | 35.4 | 19:16:47 |
+| pkg-discord | 3 | 2.6 | 19:16:50 |
+| pkg-harness | 12 | 11.6 | 19:17:02 |
+| pkg-ledger | 13 | 13.5 | 19:17:15 |
+| pkg-mosaic | 3 | 2.3 | 19:17:18 |
+| pkg-plugins | 0 | 0.3 | 19:17:18 |
+| pkg-project | 1 | 1.2 | 19:17:19 |
+| pkg-runs | 1 | 0.8 | 19:17:20 |
+| pkg-seat | 6 | 6.2 | 19:17:26 |
+| pkg-tasks | 1 | 1.2 | 19:17:27 |
+| pkg-webui | 58 | 57.9 | 19:18:25 |
+| script-auth | 1 | - | 19:18:26 |
+| script-conductor | 5 | - | 19:18:31 |
+| script-config | 2 | - | 19:18:33 |
+| script-discord | 8 | - | 19:18:41 |
+| script-extension-package | 1 | - | 19:18:42 |
+| script-foundation | 40 | - | 19:19:22 |
+| script-land-work | 11 | - | 19:19:33 |
+| script-queue | 21 | - | 19:19:54 |
+| script-release | 11 | - | 19:20:05 |
+| script-task | 31 | - | 19:20:36 |
+
+Source: /mnt/storage/scratch/sage-g189/out/*.log mtimes and gate.log. The cli suite is about 59% of the run, and webui plus conversation add about 14%.

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/BUILD.md

@@ -0,0 +1,86 @@
+# Row 189: `stack-release.sh activate --no-send`
+
+Gitea #1687. Vikunja P19 #413 (Q175 interim, #412). Brief: docs/plans/2026-10-20_activate-no-send.md.
+Rulings: mos-0972 (the Console runs without `--send` until Q175 phase 2), mos-0973 (go; Sage builds,
+Dewey reviews; gate is the cli suite plus every scripts/test-*.sh). Base: def2e7932 (refactor, the
+brief commit on 9ae8c73ac).
+
+## What it does
+
+`activate ID BUSINESS --no-send` drops `--send` from `RUN_CONSOLE` in a new `send_for_target`, which
+`console_for_target` calls after `proof_for_target`. `install_stack` renders the unit from
+`RUN_CONSOLE` and `write_pointer` writes the pointer from it, so both lose the flag and `flags_drift`
+stays quiet afterwards. Only `activate` takes the flag; the parser sends every other op to usage
+(exit 4).
+
+`check_target` lets a `--no-send` activate name the pointer's copy only when the pointer's Console
+flags hold `--send`. That run is a live-copy re-pin, the same path row 187 uses for the proof pair:
+the plan prints the live-copy note, the run stops both units, backs up the stopped store and starts
+them again. A plain same-copy activate, or a same-copy `--no-send` once `--send` is gone, still
+refuses `already-active`.
+
+`--plan` prints one `send:` line after the `proof:` line, for activate and rollback:
+
+- `send: dropped; --no-send was given`
+- `send: off; --no-send was given and the pointer holds no --send`
+- `send: carried` (the pointer's `--send` goes on unchanged)
+- `send: off`
+
+The steps log gets `drop --send; --no-send was given`, or `--no-send was given and the pointer holds no
+--send, so there is nothing to drop`.
+
+Rollback and pm-on carry the pointer's flags as they are, so once `--no-send` has run, nothing adds
+`--send` back. There is no re-enable flag (mos-0973). Q175 phase 2 changes the Console flags in its
+own row.
+
+docs/TOOLS.md: `[--no-send]` in the usage block and one paragraph after the proof paragraph.
+
+## Tests (packages/cli/tests/stack-release.test.mjs, T55)
+
+1. Seeded preview pointer with `--send --tester-port 7333`: a same-copy `activate B acme --no-send`
+   passes. The pointer and the unit ExecStart lack `--send` and keep the other flags in order, status
+   says the unit flags match, the steps log has the drop line, the log line has from = to = B and the
+   backup sum equals the stopped store's, and the units stop and start in order.
+2. Plain same-copy activate, with `--tester-port` and with `--no-proof`, refuses `already-active`. So does
+   a same-copy `--no-send` once `--send` is gone, and on a pointer that never held it.
+3. The four `send:` lines, the live-copy note on the same-copy plan only, and the Console line right
+   after `send:` without `--send`. The run on a pointer with no `--send` logs the nothing-to-drop line
+   and no drop line.
+4. After `--no-send` on C1, a rollback to B leaves `--send` out of the pointer and the unit, the steps
+   log never names `--send`, and status matches. pm-on after `activate --pm-after-harness --no-send`
+   keeps it off.
+5. `--no-send` on rollback (with and without `--plan`), pm-on, status, adopt and rehearse is a usage
+   error with the usage text, nothing written, started or logged. The usage text shows `[--no-send]`.
+6. A pointer holding both the proof pair and `--send`: the plans for `--no-proof`, `--no-send` and both
+   name what each drops and carries. `--no-send` keeps the pair, `--no-send` with a new pair replaces it,
+   `--no-proof` keeps `--send`, and both together leave neither. Status matches after each.
+
+`planTail` gains `'send: off'` after `'proof: off'`, because every plan now prints the line. T36 takes
+`out.slice(-n)` around `planTail`, so its four slice counts grow by one.
+
+## Mutants
+
+mutants.sh in this packet, run on the candidate. Each mutates scripts/stack-release.sh and runs T55
+plus T1 and T2.
+
+- M1: the same-copy exception ignores `--no-send`.
+- M2: the same-copy exception allows `--no-send` without `--send` in the pointer.
+- M3: with `--no-send`, the pointer is written from `P_CONSOLE`, so it keeps `--send` while the unit
+  drops it.
+- M4: rollback re-adds `--send`.
+- M5: the parser accepts `--no-send` for rollback.
+
+Results: mutants-run.log, all five killed (M1 5 failures, M2 2, M3 7, M4 2, M5 2).
+
+## Deviations from the brief
+
+- The brief's line numbers were taken before row 163 landed. The candidate corrects them to the
+  9ae8c73ac lines (check_target :249-256, flags_drift :646-657, console_for_target :664-693, adopt
+  :828).
+- Test 5 also covers rehearse and `rollback --plan`, which the brief did not list.
+
+## Outbound calls
+
+None. The change edits an array before the existing unit render and pointer write. Every test uses
+the stand-in systemctl, units, stores and data root the file already builds; no test touches
+`~/.mosaic-dev`, the live units or a slot file.

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/queue-189/mutants-run.log

@@ -0,0 +1,5 @@
+M1 KILLED fail=5
+M2 KILLED fail=2
+M3 KILLED fail=7
+M4 KILLED fail=2
+M5 KILLED fail=2

agents/sage/work/queue-189/mutants.sh

@@ -0,0 +1,34 @@
+#!/usr/bin/env bash
+# Row 189 mutants M1-M5: each mutates scripts/stack-release.sh in the sage-b189 worktree, runs T55 and
+# the plan-tail tests, and restores the file from a checked backup.
+set -uo pipefail
+WT=/mnt/storage/scratch/sage-b189
+OUT=/mnt/storage/scratch/sage-b189-mut/out
+S=$WT/scripts/stack-release.sh
+mkdir -p "$OUT" || exit 1
+cp -p "$S" "$OUT/stack-release.sh.orig" || { echo "backup failed"; exit 1; }
+ORIG=$(sha256sum "$S" | cut -d' ' -f1)
+[ "$(sha256sum "$OUT/stack-release.sh.orig" | cut -d' ' -f1)" = "$ORIG" ] || { echo "backup differs"; exit 1; }
+restore() { cp -p "$OUT/stack-release.sh.orig" "$S"; [ "$(sha256sum "$S" | cut -d' ' -f1)" = "$ORIG" ] || { echo "RESTORE FAILED"; exit 1; }; }
+trap restore EXIT
+
+mutate() {
+    case "$1" in
+        M1) sed -i '/{ \[ "\$NO_SEND" = 1 \] && \[\[ " \${P_CONSOLE\[\*\]} " == \*" --send "\* \]\]; } ||/d' "$S" ;;
+        M2) sed -i 's/{ \[ "\$NO_SEND" = 1 \] && \[\[ " \${P_CONSOLE\[\*\]} " == \*" --send "\* \]\]; } ||/{ [ "$NO_SEND" = 1 ]; } ||/' "$S" ;;
+        M3) sed -i 's/^    write_pointer "\$TO" "\$RUN_PM" "\$RUN_PENDING" "\$P_CLAUDE" "\$T_SCHEMA" "\${RUN_CONSOLE\[@\]}"$/    if [ "$NO_SEND" = 1 ]; then write_pointer "$TO" "$RUN_PM" "$RUN_PENDING" "$P_CLAUDE" "$T_SCHEMA" "${P_CONSOLE[@]}"; else write_pointer "$TO" "$RUN_PM" "$RUN_PENDING" "$P_CLAUDE" "$T_SCHEMA" "${RUN_CONSOLE[@]}"; fi/' "$S" ;;
+        M4) sed -i 's/^        SEND_PLAN="send: off"$/        SEND_PLAN="send: off"; [ "$OP" != rollback ] || RUN_CONSOLE+=(--send)/' "$S" ;;
+        M5) sed -i 's/--no-send) \[ "\$OP" = activate \] || usage;/--no-send) { [ "$OP" = activate ] || [ "$OP" = rollback ]; } || usage;/' "$S" ;;
+    esac
+}
+
+for m in M1 M2 M3 M4 M5; do
+    restore
+    mutate "$m"
+    if [ "$(sha256sum "$S" | cut -d' ' -f1)" = "$ORIG" ]; then echo "$m NOT-APPLIED"; continue; fi
+    bash -n "$S" || { echo "$m SYNTAX"; continue; }
+    diff "$OUT/stack-release.sh.orig" "$S" > "$OUT/$m.diff"
+    (cd "$WT" && TMPDIR=/mnt/storage/scratch/t189 timeout 900 node --test --test-reporter=tap --test-name-pattern='T55|T1 |T2 ' packages/cli/tests/stack-release.test.mjs) > "$OUT/$m.log" 2>&1
+    fails=$(awk '/^# fail /{print $3}' "$OUT/$m.log")
+    if [ "${fails:-0}" -gt 0 ]; then echo "$m KILLED fail=$fails"; else echo "$m SURVIVED"; fi
+done

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

docs/TOOLS.md

@@ -368,7 +368,7 @@ reports checkout or copy identity and refactor drift, and writes nothing.
 ```
 scripts/stack-release.sh adopt BUSINESS
 scripts/stack-release.sh activate ID BUSINESS [--pm | --pm-after-harness] [--migrate] [--tester-port N]
-    [--proof-header NAME --proof-file PATH | --no-proof] [--timeout S] [--plan]
+    [--proof-header NAME --proof-file PATH | --no-proof] [--no-send] [--timeout S] [--plan]
 scripts/stack-release.sh pm-on BUSINESS [--timeout S]
 scripts/stack-release.sh rollback BUSINESS [--restore ACTIVATION [--events N]] [--timeout S] [--plan]
 scripts/stack-release.sh status BUSINESS
@@ -480,6 +480,14 @@ copies. It checks the file with `stat` and `realpath` and never reads the value.
 or `off`. On the live copy it also notes that the run re-pins the pointer's copy
 and only the Console flags change.
 
+`activate ... --no-send` (row 189, mos-0972) drops `--send` from the pointer's
+Console flags and the unit, so the Console serves reads and no human sends. It
+may name the live copy while the pointer holds `--send`; once `--send` is gone a
+same-copy `--no-send` refuses `already-active`. Later activates, `pm-on` and
+rollbacks carry the pointer, so send stays off. No flag puts `--send` back.
+`--plan` prints one `send:` line: `dropped`, `off` with or without the
+`--no-send` note, or `carried`.
+
 #### A target past c216f47db: the PM after the harness kind
 
 From c216f47db on, the bus launches the PM only with a `harness` kind in the

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

@@ -0,0 +1,73 @@
+# 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. The candidate corrects them;
+the first draft took them before row 163.
+
+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:664-693) carries the pointer's flags unchanged. Only
+  `--tester-port` and the row 187 proof pair can change.
+- `check_target` (:249-256) lets an activate name the pointer's copy only for a proof-pair change.
+- `adopt` refuses once a pointer exists (:828).
+- A hand `webui-service.sh install` without `--send` makes `flags_drift` (:646-657) 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-credentials.md

@@ -0,0 +1,57 @@
+# Brief: a credential store per agent, own git identity, pushes to a remote
+
+Sage, 2026-10-20, for mos-0974 (MVP T1 item 6) and the MVP plan
+(`jason-master-restart/projects/mosaic-mvp/PLAN.md` item 6, GAP-MAP G11 and G13; TARGET.md: "credentials store
+available for all agents; secrets protected with RLS equivalent" and "Agent uses own credentials for git and
+other actions"). Gitea #1697. Owner Megavolt (Opus 5.5, a new builder seat), reviewer Duckworth, gate owner
+Sage. Base: refactor at the brief commit. Design first. The first deliverable is
+`agents/megavolt/work/queue-ROW/DESIGN.md`.
+
+This row draws a security boundary. Sage reviews the design's authority model, and Mos rules on it before any
+code is written.
+
+## What exists today (GAP-MAP, measured at 9ae8c73ac)
+
+- G11. Credential references exist per instance for Gitea and Vikunja only
+  (`packages/business/src/credentials.mjs`, `packages/bus/src/credentials.mjs`, `vocabulary.mjs:103`). One
+  Claude env file is shared by every seat.
+- G13. Agents use their own Vikunja token (`packages/tasks/src/adapter.mjs`). Git goes through the host
+  socket (`packages/cli/src/git-socket.mjs`). Gitea tokens are loaded but never used.
+- The development repository's helper (`scripts/git-credential-mosaic.mjs`, wired in `.git/config` for
+  git.mosaicstack.dev) pushes as one identity. Until this row lands, seats push only their own `<seat>/*`
+  branches through it (mos-0981).
+
+## What the design must settle
+
+1. The store. Where each agent's credentials live, per instance, under the row 190 config canon. File modes,
+   ownership and the read path. Which process may read which entry, and how the bus enforces that (the "RLS
+   equivalent"). A process asking for another agent's entry is refused and logged.
+2. Kinds. Gitea (git over HTTPS, and the API), Vikunja, and the model provider. Say which kinds 10-27 needs
+   and which wait. The model provider entry must not copy jwoltje's `claude-session.env`. If it needs a new
+   provider account or subscription, flag it for Jason and don't pick one.
+3. Git identity and push. Each agent commits with its own name and email and pushes with its own token to a
+   remote it is granted. Which refs an agent may push (its own branches, never the default branch or another
+   agent's), and where that's enforced: the Gitea side (branch protection, token scopes) and our side. How
+   this fits the host git socket, or replaces it.
+4. Lifecycle. Issue, rotate (`rotateBy`, `expires`), revoke and delete, and what row 194 (agent lifecycle) calls
+   when an agent is hired or fired. A fired agent's credentials stop working at once.
+5. Who does what. Creating a Gitea user or token, or any account outside the fleet, is Jason's (Q173
+   exclusions). The design lists each such step as a command or UI action for Jason. Agents never mint
+   accounts.
+6. Migration. Today's seats (jarvis helper, seat tokens) keep working until each moves. The mos-0981 push
+   rule ends only when Mos says so.
+7. What this row closes in G11 and G13, and what stays open.
+
+## Boundaries
+
+- No credential value is read, printed, logged or committed. Tests use fake tokens in scratch roots and a
+  fake Gitea.
+- No change to `~/.mosaic-dev`, `~/.config/mosaic-dev`, the live units, slot files, `~/.mosaic` or the live
+  `.git/config` of the canonical checkout.
+- No request to git.mosaicstack.dev, tasks.woltje.com or any provider from a test.
+
+## Gate
+
+Duckworth approves DESIGN.md, Mos rules on the authority model, then Duckworth approves the manifest. The bus,
+business, cli and tasks suites and every `scripts/test-*.sh` are green on Sage's gate, and the design's
+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_case2-rows.md

@@ -0,0 +1,955 @@
+# Case 2 slice rows: the creative writing hub (#416, T2)
+
+Gosalyn, 2026-10-20 (from `date -u`), for sage-1329. Every section follows `docs/plans/BRIEF-TEMPLATE.md`.
+The design they build is `agents/gosalyn/work/case2/DESIGN.md` on `gosalyn/case2-design`. Webby
+approved r5 at e1635308b in webby-0021, with notes at dba33aaf6. r6 and r7 change only sections 9 and 10
+and C2-13's row (mos-1057, Q183, webby-0023), and that diff is with Webby. Below, "the design" means that
+file, with its section number. A builder follows the design and doesn't reopen a decision in it. A
+departure goes to Sage before the build continues.
+
+These are the slice rows from design 9.2, plus C2-11a, which the design starts in the first wave. The
+other rows (C2-02, C2-03b, C2-09b, C2-10c, C2-11b, C2-15 to C2-19) get briefs when a seat is free for
+them. Owners and models come from design section 8 (Q177, Q178). Where the design names only a model,
+Sage picks the seat. The reviewers are my proposals, and Sage can change any of them with `queue set`.
+Sage owns every gate.
+
+Base: `refactor` at ae3c36f24. The design cites 9ae8c73ac. `git diff --stat 9ae8c73ac ae3c36f24 --
+packages adapters roles scripts` touches only `scripts/stack-release.sh` and its test, and no cited line
+is in either.
+
+Order (design 8, "Parallel waves"):
+1. Start now: C2-01, C2-08, C2-11a.
+2. On C2-01's candidate: C2-04, C2-05a, C2-06, C2-12. On C2-08's: C2-09a, C2-10a, C2-20.
+3. Then C2-03a and C2-07. Then C2-05b, C2-10b and C2-13.
+4. Last: C2-14.
+
+A row whose parent hasn't landed builds on the parent's candidate and rebases onto its landing (Q177).
+
+Rules every row keeps:
+- No test touches `~/.mosaic-dev`, `~/.config/mosaic-dev`, a live unit, a slot file, Melanie's books
+  repo, git.mosaicstack.dev or any Discord server. Tests use scratch roots, scratch config dirs and a
+  local bare repo the test builds in her layout's shape: spaces and capitals in folder names, a `.canvas`
+  file and an unmapped top-level note.
+- No row reads her text. Fixtures are made up. A marker string in a fixture body stands in for her
+  text wherever a test checks that output holds none.
+- No credential value in any output, test, log or message (CONSTITUTION gate 13). Tests use a fixture
+  token file with a made-up value.
+- No live stack change. Nothing here re-pins, restarts or activates anything. C2-13's run on the host
+  needs Jason's go (design 10).
+- Before in-review, grep `packages/*/tests` and `scripts/test-*.sh` for each changed path and for any
+  64-hex pin of it, and run every changed or touched test file on its own. Suites need Sage's slot.
+- A refusal code named in the design is the code the row ships. A new code goes to Sage first.
+
+---
+
+## C2-01 packages/library: mapping, scope, reader, resolver, R-rules, renderItems, survey
+
+### Problem
+
+Nothing in the stack reads a writing repo by a mapping of folders to books, types, canon and playground.
+`packages/project/src/read.mjs:19-26` reads blobs from a record repo but accepts executables (`:21`) and
+knows no scope. Design 1.1 to 1.3 and 7.4 set out what Case 2 needs, and every later row builds on it.
+
+### Owner and reviewer
+
+- Owner: Gosalyn, Opus 5.5.
+- Reviewer: Webby, who reviewed the design.
+- After: none.
+
+### Files owned
+
+- `packages/library/` (new): `package.json`, `src/mapping.mjs`, `src/scope.mjs`, `src/reader.mjs`,
+  `src/links.mjs`, `src/problems.mjs`, `src/render.mjs`, `src/survey.mjs`, `src/index.mjs`, `tests/*.test.mjs`,
+  `tests/fixtures/`, `README.md`.
+- `scripts/stack-copy.sh`: add `packages/library/src` to `COPY_PATHS`. Without it the live copy has no
+  library code, and no test catches the gap today.
+- `packages/cli/tests/stack-copy.test.mjs`: add `packages/library/src/index.mjs` to the list at `:37`.
+- `scripts/mosaic` or `packages/cli/src`: only the dispatch line for `library survey`.
+
+### What ships
+
+- The mapping schema of design 1.1, including `library-playground-outside-book` and the rule that no
+  playground prefix holds another. Business file loading wires it in C2-04, so here it is a pure
+  validator.
+- The scope rule of design 1.2. Only `.md` files are playground or canon.
+- The commit reader of design 1.3: `git ls-tree -r -z` and `cat-file` on a commit, never a working tree,
+  through the same `git()` and `gitEnv()` as `packages/project`. R1 to R7 as problems with path and line.
+- The link resolver, in the order 1.3 gives: repo root, `vaultPrefix/` stripped, relative to the linking
+  file, then shortest path. `appears_in` and `relationships` wikilinks are read as links.
+- `renderItems(body)` (7.4), one pure function for the item kinds and the three notices.
+- `library survey <repo> [--mapping <file>]`, which prints folder names, file counts, front matter key
+  sets and link-form counts, and never text.
+
+Tests: one case per R-rule and per resolver step. A link into another repo resolves to nothing. An
+`appears_in` wikilink is indexed. `renderItems` has a snapshot for each kind and each notice. The survey
+prints names, counts, key sets and link-form counts, and a marker string in a fixture body never
+appears in its output. The stack-copy test lists the new path. The library tests and
+`packages/cli/tests/stack-copy.test.mjs` pass.
+
+### Out of scope
+
+Business file loading and consumer skips (C2-04), sync (C2-03a), the index and queries (C2-05a), the
+guard (C2-06). The survey run on the host is design 10 step 7, after the token slot exists.
+
+### Gate
+
+Webby approves the manifest. The library tests and the cli suite are green on Sage's gate, along with
+every `scripts/test-*.sh`.
+
+---
+
+## C2-08 creative roles, persona file and block, M1, M2, M6, M10, prompt passed by file
+
+### Problem
+
+The stack has no role that may only read and answer in cited items, no way to carry Bean's and Chet's
+personas, and several paths by which a non-human actor could change a creative instance (design 4, B3).
+Both adapters pass the whole prompt on the command line (`adapters/claude/adapter.sh:79`, `:82`,
+`adapters/pi/adapter.sh:106`, `:121`), so any local user can read it in `/proc/<pid>/cmdline`.
+
+### Owner and reviewer
+
+- Owner: an Opus 5.5 seat that Sage picks.
+- Reviewer: Webby.
+- After: none.
+
+### Files owned
+
+- `roles/companion.json`, `.md`, `roles/ideas.*`, `roles/research.*`, `roles/proofreader.*`,
+  `roles/fact-checker.*`, `roles/continuity.*` (new).
+- `packages/business/src/vocabulary.mjs`: `THREAD_DEFINITIONS`, `END_PROTECTED` as `THREAD_DEFINITIONS`,
+  `CREATIVE_DEFINITIONS`, `CREATIVE_KINDS`, `CREATIVE_TOOLS`.
+- `packages/business/src/role.mjs` (M1), `vars.mjs` (`persona.name`, `persona.sha256` in `REGISTRY`),
+  `launch-settings.mjs` (the `instances` and `models` checks and the `setRoutes` branch),
+  `instance-settings.mjs` (the creative branch).
+- `packages/bus/src/broker.mjs`: M6 `decision-not-allowed` only.
+- `packages/harness/src/bundle.mjs`: the persona file read and checks, the fenced block in `prompt()`, and
+  the `webPlan` refusal.
+- `packages/harness/src/tools.mjs`: `raise_decision` left out for creative definitions.
+- `adapters/claude/adapter.sh`, `adapters/pi/adapter.sh`, `adapters/README.md` (`:89`, `:107`).
+- Tests in `packages/business/tests`, `packages/bus/tests`, `packages/harness/tests`.
+
+### What ships
+
+Design 4, 5.1 (M1, M2, M6, M10) and 5.3:
+- The six role files, version 2, with the tools, authority, messaging and network of the design 4 table.
+- The constants. `THREAD_DEFINITIONS` replaces `THREAD_DEFINITION` only where it means "may hold a
+  thread", and that use is C2-09a's. The `assistants` lines at `launch-settings.mjs:140`, `:186` and
+  `:191`, and `tools.mjs:186`, stay `THREAD_DEFINITION`.
+- The persona file at `<configDir>/personas/<business>/<instance>.md`, read with `O_NOFOLLOW`. The
+  bundle refuses a non-regular file, another uid's, any group or other bit, more than 8,000 characters,
+  a digest off the var (`persona-mismatch`), and `</persona-file>` or a line starting `# ` or `## `
+  (`persona-invalid`). The block goes between the contract and "## This session", fenced as in design 4.
+- One actor rule on all five write paths (design 4): a write that touches a `CREATIVE_DEFINITIONS`
+  instance is accepted only when its actor is the business file's `human`, otherwise
+  `organization-creative-human-only`. The `instances` key of `limits.set` and `organization.set` refuses
+  a creative instance for every actor with `organization-creative-instance`.
+- Both adapters pass the prompt file, not its text. Claude uses `--system-prompt-file`. Pi gets the path
+  as `--system-prompt`, and its adapter checks `[ -r ]` first and refuses otherwise, because pi 0.85.1
+  uses the path string itself as the prompt when the file is missing or unreadable
+  (`resource-loader.js:21`, `:24-27`, `:30`).
+
+Tests, all named in the design 8 C2-08 row:
+- Role, gate and messaging tests. A creative raise is refused and no decision row appears.
+  `harness-builtin` is refused for `research` and `companion`. `scripts/test-config.sh` passes.
+- Persona vars are refused at other layers, when malformed and on a non-creative definition. Each
+  persona file refusal above has a test. A prompt snapshot pins contract, persona, session, in that
+  order.
+- M10:
+  - Each path refuses with the file unchanged, and the human's `instances.set` and `routes.set` on
+    `bean` work.
+  - The human's `limits.set` change to Bean's `launch.models` key works, next to the chief of staff's
+    `organization.set` refusal of the same change.
+  - Tester cases run through the broker with a bound tester session, and chief of staff cases with a
+    role session.
+  - A mutant without the `models` check fails.
+  - No `instances` read, `changes.jsonl` line or adapter argv holds a marker string from a fixture
+    persona.
+- Adapter tests in `claude-session.test.mjs` and `pi-session.test.mjs`: argv holds the prompt path and no
+  marker from the prompt. Pi's adapter refuses a missing prompt file and an unreadable one.
+- Business file, `.history` and `changes.jsonl` modes after an `instances.set` write.
+
+### Out of scope
+
+Thread creation per instance and the launcher (C2-09a), the lookup tools (C2-05b), the cited-reply guard
+(C2-06). Checking the host's claude for `--system-prompt-file` is C2-13's precheck. If the C2-20 dry run
+finds heading lines in a real persona, the fence rule changes in a follow-up to this row, reviewed,
+before the import (design 9.1).
+
+### Gate
+
+Webby approves the manifest. The business, bus and harness suites, `scripts/test-config.sh` and every
+`scripts/test-*.sh` are green on Sage's gate, and the `models` mutant is killed.
+
+---
+
+## C2-11a editor wikilink node, after measuring whether [[ round-trips
+
+### Problem
+
+The Console's editor opens a file in visual mode only if `roundTrip(text) === text`
+(`packages/webui/src/public/bus.js:919-920`). Its commonmark rules (`packages/webui/editor/model.mjs:119-120`)
+have no wikilink rule, and nobody has measured whether the serializer escapes `[[`. If it does, every
+note with a wikilink opens in Source.
+
+### Owner and reviewer
+
+- Owner: Rocko, gpt-6.1-sol.
+- Reviewer: Filbert.
+- After: none.
+
+### Files owned
+
+`packages/webui/editor/model.mjs`, the editor's bundle output if the build commits one, and
+`packages/webui/tests/` editor test files.
+
+### What ships
+
+First a test that measures today's behaviour on `[[a]]`, `[[a|b]]`, `[[a#h]]`, in a list item, and next to
+front matter, with the result recorded in the manifest. Then a wikilink node that keeps each form byte
+for byte. `roundTrip` tests cover plain, labelled, heading, in a list, and next to front matter.
+
+### Out of scope
+
+Library pages and saving (C2-11b), link clicking to open a target (C2-11b), any `documentPath` change.
+
+### Gate
+
+Filbert approves the manifest. The webui suite is green on Sage's gate, along with every
+`scripts/test-*.sh`.
+
+---
+
+## C2-04 the library entry in the business file, consumer skips, M9, mirror, library.file and library.status
+
+### Problem
+
+The business file accepts only `root` and `repo` per project (`packages/business/src/business.mjs:186-187`),
+and several consumers assume every project has a root (design 2.1). Nothing stops an organization write
+from changing `projects`, and nothing creates a mirror.
+
+### Owner and reviewer
+
+- Owner: Rocko, gpt-6.1-sol.
+- Reviewer: Filbert.
+- After: C2-01.
+
+### Files owned
+
+- `packages/business/src/business.mjs`, `organization.mjs` (M9 in `organizationWriter.write`, `:177`),
+  `project.mjs`, `cli.mjs`, `resolve.mjs`, `instance-settings.mjs` (only the skip at `:142`).
+- `packages/seat/src/checkout.mjs` (`:310`, `:319`), `packages/cli/src/launcher.mjs` (`:353`).
+- `packages/project/src/paths.mjs` (the overlap loop at `:41-44`, and the mirror path).
+- `packages/bus/src/broker.mjs`: `library.file` and `library.status` only.
+- `packages/webui/src/cli.mjs`: dispatch lines for the two verbs.
+- Tests in the matching `tests/` directories.
+
+### What ships
+
+The `kind: "library"` entry of design 1.1, validated by C2-01's schema. Each consumer in design 2.1
+skips it, with its own test. M9: `organization-projects-protected` for any organization write whose
+`projects` differ from the file's in canonical JSON. The bare mirror is created at the `projectRepo` path
+with no remote in its config. `library.file` (read at the served commit) and `library.status` (reads the
+sync state, empty until C2-03a) are human only, refused from an agent session with `human-required`
+(M4).
+
+Tests: business file tests. One test per consumer skip. A launcher test that the workspace has no clone.
+The M9 test calls `write` directly, once with a changed playground prefix and once with a changed hybrid
+entry, and the file and `changes.jsonl` are unchanged. Each verb from an agent session refuses.
+
+### Out of scope
+
+Fetching (C2-03a). Bus writes (C2-02). The Console's library pages (C2-11b).
+
+### Gate
+
+Filbert approves the manifest. The business, seat, cli, project, bus and webui suites are green on Sage's
+gate, along with every `scripts/test-*.sh`.
+
+---
+
+## C2-05a lookup index and queries
+
+### Problem
+
+Agents need typed lookups over her repo that keep universes apart and default to canon (design 3). The
+reader from C2-01 has no index or query layer.
+
+### Owner and reviewer
+
+- Owner: a Haiku 5.5 subagent at high effort, dispatched by Sage (lead decision 129).
+- Reviewer: Filbert.
+- After: C2-01.
+
+### Files owned
+
+`packages/library/src/index-build.mjs`, `packages/library/src/query.mjs`, their exports in
+`packages/library/src/index.mjs`, and `packages/library/tests/` query test files.
+
+### What ships
+
+An index per commit (types, names, links, backlinks), cached in memory by commit id. Queries for find, get,
+search, manuscript and universe, with the arguments and result shapes in the design 3 table. `universe`
+is required. Results never leave it, except a hybrid's declared sources minus exclusions. Every result
+carries `scope`. Unmapped files never appear. `links_out` and `links_in` drop other-universe and unmapped
+targets. Results page under `REPLY_CAP` (`packages/harness/src/tools.mjs:271-280`) and are never cut.
+
+Tests: isolation, scope labels on every query, unmapped files never returned, paging under `REPLY_CAP`,
+and a rebuild time on a 3,000-file fixture recorded in the manifest.
+
+### Out of scope
+
+Broker verbs and typed tools (C2-05b). Hybrid entries in the business file (C2-15). The query code takes
+hybrids as a shape, and its tests use a hand-built hybrid mapping.
+
+### Gate
+
+Filbert approves the manifest. The library suite is green on Sage's gate, along with every
+`scripts/test-*.sh`.
+
+---
+
+## C2-06 the cited-reply guard, the page store and the three notices
+
+### Problem
+
+Today a creative agent's free text would reach her as a stored message. Jason's ruling says agents never
+write prose for her and always refer to the source (Q176). Design 5.2 puts one guard in the broker before
+every agent-to-human message in a library business.
+
+### Owner and reviewer
+
+- Owner: an Opus 5.5 seat that Sage picks.
+- Reviewer: Webby.
+- After: C2-05a.
+
+### Files owned
+
+- `packages/library/src/guard.mjs` and its export.
+- `packages/bus/src/broker.mjs`: the pre-check on `message.send` to `human`, and the page store beside the
+  web verbs (`:1516`, `:1521`).
+- `packages/bus/src/web.mjs`, only if the page store needs the fetched text passed out.
+- Tests in `packages/library/tests` and `packages/bus/tests`.
+
+### What ships
+
+The guard as design 5.2 sets it out: the JSON body, the M5 limits, the checks and refusal codes of the
+5.2 table, and the three notices. It runs before the insert, outside the SQL transaction, as
+`#requestProject` does (`broker.mjs:1378-1430`). It doesn't look at the sender's definition to decide
+whether to run. The page store keeps the last 20 broker fetches per session, 200 KB each, in memory,
+dropped when the session ends.
+
+Tests: one pass and one refusal for each check in M5 and 5.2, each limit refused one past its boundary
+and accepted at it. Each goes through the runner's RESULT path and through `send_message`, and once
+with a non-creative sender in a library business. The `messages` count is unchanged on each refusal.
+
+### Out of scope
+
+The runner retry and the runner's notices (C2-07). The Console's rendering (C2-10b). Any classifier of
+prose. The idea-text residual is Jason's or Melanie's to accept (design 5.1, 10 step 8).
+
+### Gate
+
+Webby approves the manifest. The library, bus and harness suites are green on Sage's gate, along with
+every `scripts/test-*.sh`.
+
+---
+
+## C2-12 the setup sheet for Melanie and the survey run sheet
+
+### Problem
+
+Melanie keeps writing in Obsidian, and she needs to know what the agents read, how a playground folder
+works, what changes for Bean and Chet, and two surprises (design 7.1, N2, N4). Whoever runs the survey
+on the host needs exact steps.
+
+### Owner and reviewer
+
+- Owner: gpt-6-luna.
+- Reviewer: Webby.
+- After: C2-01.
+
+### Files owned
+
+`docs/case2/SETUP-SHEET.md` and `docs/case2/SURVEY-RUN.md` (new).
+
+### What ships
+
+The setup sheet in plain words:
+- Which folders the agents read, and that a folder named in `playground` is her playground.
+- How to add a graph colour group for that path in her own vault.
+- That moving a note into a book folder makes it canon, so agents may cite it as fact.
+- That a short link to a name that also exists in another of her repos can point somewhere else for the
+  agents, and that a full-path link avoids this.
+- What changes for Bean and Chet: short cited items, no passages (design 4).
+
+The survey run sheet gives the exact `library survey` command with C2-01's real flags, and states what
+the output holds: names and counts only.
+
+### Out of scope
+
+Sending it to her. Design 10 step 7 makes that Jason's call.
+
+### Gate
+
+Doc only. Webby approves it against C2-01's real flags. Before landing, grep `packages/*/tests` and
+`scripts/test-*.sh` to confirm no test reads either file.
+
+---
+
+## C2-09a one thread per creative instance
+
+### Problem
+
+`thread.create` picks the single `assistant` instance and refuses more than one
+(`packages/bus/src/broker.mjs:2331-2334`). The same rule sits in `#threaded` (`:290-291`) and the launcher
+(`packages/cli/src/launcher.mjs:135`, `:236-238`). So she can't open a thread with Bean beside one with
+Chet.
+
+### Owner and reviewer
+
+- Owner: Rocko, gpt-6.1-sol.
+- Reviewer: Dewey.
+- After: C2-08.
+
+### Files owned
+
+`packages/bus/src/broker.mjs` (`#threaded`, `thread.create`), `packages/cli/src/launcher.mjs`,
+`packages/webui/src/public/bus.js` and `serve.mjs` (the new-thread control only), and tests in
+`packages/bus/tests`, `packages/cli/tests` and `packages/webui/tests`.
+
+### What ships
+
+Design 6, C2-09a: `#threaded` and the launcher read `THREAD_DEFINITIONS`. `thread.create` takes
+`instance`, which must be a `THREAD_DEFINITIONS` instance. With no `instance` and exactly one such
+instance, today's behaviour holds. With more than one, it refuses `thread-instance-ambiguous`. The
+Console's new-thread control lists thread instances by `persona.name` or instance name and passes the
+one she picks. No schema change.
+
+Tests: a creative instance's thread starts a run, `thread.create` with `instance` binds it, and two thread
+instances with no `instance` still refuse.
+
+### Out of scope
+
+Rooms and @tags (C2-09b, C2-10c).
+
+### Gate
+
+Dewey approves the manifest. The bus, cli and webui suites are green on Sage's gate, along with every
+`scripts/test-*.sh`. Watch for hash pins on `bus.js` and `broker.mjs`
+(`packages/bus/tests/channel-proof.test.mjs` pins a webui file).
+
+---
+
+## C2-10a no raw session view (M7) and no raw Discord engine (M8)
+
+### Problem
+
+The Console's conversation view shows a model's raw text from session files
+(`packages/conversation/src/reader.mjs:225-240`, `events.mjs:58`, `:82`), so a refused answer would still
+show. The Discord connector posts its engine's output and the broker never sees it
+(`packages/discord/src/connector.mjs:381-387`).
+
+### Owner and reviewer
+
+- Owner: a Haiku 5.5 subagent at high effort, dispatched by Sage.
+- Reviewer: Filbert.
+- After: C2-08.
+
+### Files owned
+
+`packages/conversation/src/reader.mjs`, `packages/discord/src/cli.mjs` (`check` and `run` only), and
+tests in `packages/conversation/tests` and `packages/discord/tests`.
+
+### What ships
+
+M7 and M8 as design 5.1 states them. On a business with a library project, `catalogue()` leaves creative
+sessions out and `open()` refuses them with `conversation-not-listed`. `discord check` and `discord run`
+refuse a binding whose engine isn't `mosaic-bus` with `discord-engine-not-allowed`, and also refuse a
+`mosaic-bus` binding with `tools`.
+
+Tests: a creative session file under the root isn't listed and won't open by id, and an assistant session
+still lists. Both Discord verbs refuse on a library business, and a pi binding on a business without a
+library still checks clean.
+
+### Out of scope
+
+The relay engine itself (C2-18).
+
+### Gate
+
+Filbert approves the manifest. The conversation and discord suites and `scripts/test-discord.sh` are
+green on Sage's gate, along with every `scripts/test-*.sh`. No test reaches a Discord server.
+
+---
+
+## C2-20 Bean and Chet persona import, with a count-only dry run
+
+### Problem
+
+Bean's and Chet's personas live in her two Hermes profiles on 10.1.1.54. The hub needs each one as a
+0600 persona file with its digest in the business file (design 4), and nothing should read her memory,
+sessions or messages to get them (design 9.1).
+
+### Owner and reviewer
+
+- Owner: Gosalyn, Opus 5.5. The script runs only under Jason's go, by whoever he names.
+- Reviewer: Webby.
+- After: C2-08.
+
+### Files owned
+
+`scripts/case2-persona-import.mjs` (new), `packages/cli/tests/case2-persona-import.test.mjs` (new) and its
+fixture tree.
+
+### What ships
+
+A script that reads only the persona definition of each of the two Hermes profiles. It confirms profile
+to name from each profile's own configured name, prints the pairing, and stops if a profile names
+neither Bean nor Chet. Per-channel prompts are listed by name and size only. It writes each persona to
+a 0600 staging file. A second step, run as `<user>`, installs it at
+`<configDir>/personas/<business>/<instance>.md` and prints `persona.name` and `persona.sha256`.
+Otherwise it prints names, byte counts and sha256 only. `--dry-run` writes nothing and prints only counts
+of files, lines, and lines starting `# ` or `## `.
+
+Build note (gosalyn-0030, mos-1087). The dry run also counts lines that name a Hermes tool or channel,
+so Jason knows before the import whether a persona refers to things Bean and Chet won't have in
+Mosaic. The words come from a fixed list in the script: the tool names in the hermes-agent checkout at
+df5700ebe, read from its code and not her profiles, plus `Hermes` and `Discord`. It prints one count
+per persona file and never the line, its number or the matched word. A nonzero count changes nothing
+in the import. It goes to Jason with the other counts.
+
+Tests, on fixture Hermes profile trees:
+- The right fields are taken.
+- Memory and session files are never opened, shown by a read trace on the fixture.
+- A profile with no persona field refuses, and a persona that fails C2-08's fence check refuses.
+- Output holds no persona text. Each written file is 0600 and its digest matches.
+- `--dry-run` writes nothing, and prints the right counts and no marker string for a fixture with two
+  heading lines.
+- `--dry-run` counts three lines that name a listed Hermes tool or channel in a fixture. Its output
+  holds none of the matched words.
+
+### Out of scope
+
+Running it. Design 10 step 6 and 9.1 make the dry run, the import and the pairing check Jason's go. If
+the dry run counts heading lines, the C2-08 follow-up changes the fence rule before the import, and her
+text is rewritten only if she says so through Jason.
+
+### Gate
+
+Webby approves the manifest. The test file runs green on its own and the cli suite is green on Sage's
+gate, along with every `scripts/test-*.sh`.
+
+---
+
+## C2-03a fetch-only sync
+
+### Problem
+
+The mirror from C2-04 holds nothing until something fetches her repo, safely and read-only, without the
+token ever reaching argv, config, logs or replies (design 7.2, CONSTITUTION gate 13).
+
+### Owner and reviewer
+
+- Owner: an Opus 5.5 seat that Sage picks.
+- Reviewer: Dewey.
+- After: C2-04.
+
+### Files owned
+
+`packages/library/src/sync.mjs`, `packages/library/bin/askpass` (new), `packages/bus/src/broker.mjs`
+(`library.sync`, the 60-second timer and the library lock), `packages/webui/src/cli.mjs` (dispatch line),
+and tests in `packages/library/tests` and `packages/bus/tests`. If the helper sits outside
+`packages/library/src`, add its path to `COPY_PATHS` in `scripts/stack-copy.sh`.
+
+### What ships
+
+Design 7.2's slice:
+- `syncCommand(kind, url)`: its argv is `SAFE`, exactly one `-c protocol.https.allow=always`, `-C
+  <mirror>`, then the command. Its env is `gitEnv()` plus `GIT_ASKPASS` naming a helper outside the
+  mirror, which reads the `library-gitea` slot.
+- An `https://` URL only.
+- The served ref `refs/heads/served`, and `library-diverged`, held until a human `library.sync --accept
+  <commit>`.
+- The sync state file, written atomically inside the mirror, and the 60-second timer.
+- `library.sync`, human only. A test reaches a local bare repo only through the module parameter that
+  replaces `syncCommand`.
+
+Tests: the C2-03a tests in design 7.2. A mutant that sets `protocol.allow=always` fails the argv test.
+
+### Out of scope
+
+Push and every bus write (C2-03b, C2-02). Creating the token slot, which is design 10 step 4.
+
+### Gate
+
+Dewey approves the manifest. The library and bus suites are green on Sage's gate, along with every
+`scripts/test-*.sh`, and the mutant is killed. A search of the test run's output for the fixture token
+finds nothing.
+
+---
+
+## C2-07 runner retry on a guard refusal, and the runner's notices
+
+### Problem
+
+When `message.send` refuses, the runner logs it and marks the message read, so the answer is lost
+(`packages/harness/src/runner.mjs:451-456`). Its empty and failed turn texts (`:449`) wouldn't pass the
+guard.
+
+### Owner and reviewer
+
+- Owner: a Haiku 5.5 subagent at high effort, dispatched by Sage.
+- Reviewer: Filbert.
+- After: C2-06.
+
+### Files owned
+
+`packages/harness/src/runner.mjs` and `packages/harness/tests/runner.test.mjs`.
+
+### What ships
+
+On a refusal with a guard code, a new turn in the same session with the code and reason, at most twice,
+then `{"items": [], "notice": "no-cited-answer"}`. In a library business, `no-answer` and `turn-failed`
+replace the two texts at `:449`. The failure reason stays in the run log.
+
+Tests: a fake harness answers free text, then a valid reply, and exactly one message is stored. An empty
+turn and a failed turn store the fixed notices.
+
+### Out of scope
+
+The guard itself (C2-06).
+
+### Gate
+
+Filbert approves the manifest. The harness suite is green on Sage's gate, along with every
+`scripts/test-*.sh`.
+
+---
+
+## C2-05b broker lookup verbs and typed tools
+
+### Problem
+
+The queries from C2-05a aren't reachable from an agent session. Design 3 and M3 call for typed tools
+that the broker re-checks on every call.
+
+### Owner and reviewer
+
+- Owner: Rocko, gpt-6.1-sol.
+- Reviewer: Dewey.
+- After: C2-05a, C2-03a.
+
+### Files owned
+
+`packages/bus/src/broker.mjs` (the lookup verbs), `packages/harness/src/tools.mjs` (the five typed tools),
+and tests in `packages/bus/tests` and `packages/harness/tests`.
+
+### What ships
+
+The five lookup tools of design 3, for every agent session in a business with a library project. Each
+read is at the served commit, and a read whose last fetch is older than 60 seconds syncs first. The
+verbs refuse `library-not-configured` in a business without a library and refuse a missing `universe`.
+The creative tool set is exact: the lookups and `send_message`, with no write tool and no
+`raise_decision`.
+
+Tests: broker verb tests and a snapshot of typed tool names per creative role (M3).
+
+### Out of scope
+
+The guard (C2-06). Write verbs (C2-02, C2-19).
+
+### Gate
+
+Dewey approves the manifest. The bus and harness suites are green on Sage's gate, along with every
+`scripts/test-*.sh`.
+
+---
+
+## C2-10b Console chat: cited items and the status line
+
+### Problem
+
+The Console would show a cited reply as raw JSON, and she can't see when the hub falls behind her repo
+(design 7.4).
+
+### Owner and reviewer
+
+- Owner: a Haiku 5.5 subagent at high effort, dispatched by Sage.
+- Reviewer: Dewey.
+- After: C2-06, C2-09a, C2-03a.
+
+### Files owned
+
+`packages/webui/src/public/bus.js`, its stylesheet, `packages/webui/src/serve.mjs` (a `library.status`
+route only), and tests in `packages/webui/tests`.
+
+### What ships
+
+Design 7.4. The chat view renders a cited reply through `renderItems`: each item's kind, text and cites,
+with a scope badge (canon, playground or web) and "changed since" when the file's last commit is newer
+than the cited one. Each notice shows its fixed line. A status line reads `library.status`: the served
+commit and its age, `library-diverged`, a fetch error, and the count of R-problems with a link to the
+list.
+
+Tests: webui tests for items, scope badges, notices, "changed since" and the status line.
+
+### Out of scope
+
+The room view (C2-10c), library pages (C2-11b). Her sign-in from her machine waits on SSO (#412) or
+Jason's interim ruling (design 10 step 5).
+
+### Gate
+
+Dewey approves the manifest. The webui suite is green on Sage's gate, along with every
+`scripts/test-*.sh`. Grep for hash pins on `bus.js` and `serve.mjs` before in-review.
+
+---
+
+## C2-13 install script and precheck for the host
+
+### Problem
+
+The hub runs on 10.1.1.54 as `mosaic` under `/srv/mosaic`, as `mosaic-stack.service` with
+`ProtectHome` (design 9, Q181). Nothing installs a library business there, or checks the host before it
+starts.
+
+### Owner and reviewer
+
+- Owner: Gosalyn, Opus 5.5. The script runs only under Jason's go, by him or his delegate (design 10).
+- Reviewer: Webby.
+- After: C2-04, C2-03a, C2-20.
+
+### Files owned
+
+`scripts/case2-install.sh`, `scripts/case2-precheck.sh` and `scripts/case2-unit.sh` (new), the template
+`packages/cli/systemd/mosaic-stack.service.in` (new), `packages/cli/tests/case2-install.test.mjs`
+(new), and one line of `packages/cli/README.md`: at `:713`, "nothing in the repository creates or reads
+it" changes to say that nothing creates it, that only the Case 2 precheck reads it, and that the
+precheck prints only variable names, never values (webby-0034 N2, webby-0035).
+
+### What ships
+
+The install does: bootstrap, release package and activate, the business file with the mapping, `bean`
+and `chet` with their persona vars and files, any specialists she picks, her human id, the token slot
+path. It runs as `<user>` through `sudo -u mosaic -H` from `localadmin`, and `mosaic` gets no key. It
+doesn't create `<user>` and writes no unit file. Root does those in design 10 steps 2a and 2c. Every
+host value is an input, so a later host move changes only inputs.
+
+Row 195 runs these scripts by input for Case 1 on 10.1.1.53 (darkwing to gosalyn, design at
+`agents/darkwing/work/queue-195/DESIGN.md` section 2). They don't copy them. So the install and the
+precheck take `--profile factory|library`, default `library`:
+- `library` is everything this brief lists.
+- `factory` skips the library mapping, the persona files and digests, the token slot, and
+  `library.sync` and `library.status`. It requires `bus.tester` on, because Case 1's acceptance uses the
+  tester.
+- `factory` refuses a business file that has a `kind: "library"` project, with
+  `profile-library-business`. So Case 2 can't reach a tester-on check through a wrong flag.
+- `library` refuses with `bus.tester` on, as before.
+
+`case2-unit.sh` is the 2c step. Root runs it from a root-owned checkout of the reviewed commit outside
+`/srv/mosaic`, never from the release, because `mosaic` can write the release. It does the following:
+- It renders the unit from the checkout's template, with the user, the home and the copy id as inputs.
+- It refuses unless `User=`, `Group=`, `ExecStart=`, `EnvironmentFile=` and the hardening lines match
+  fixed values. `EnvironmentFile=` is the line in `packages/cli/systemd/mosaic-bus.service.in:24`. The
+  copy id is the one part of `ExecStart=` that varies, so a re-pin to a new copy can re-render the
+  unit (row 195). It must be exactly 40 lowercase hex characters naming a copy that holds `scripts/mosaic`,
+  directly under `<home>/.local/share/mosaic-stack/copies`. That is the rule `copy_root` uses
+  (`scripts/stack-copy.sh:6`, `:20`). Anything else refuses before the render.
+- It refuses any `PermissionsStartOnly=`, and any `Exec*=` value whose leading run of prefix
+  characters (`@`, `-`, `:`, `+`, `!`) holds a `+` or `!`. systemd takes those prefixes in any order,
+  so `-+/srv/mosaic/x` runs as root even with `User=mosaic`. The named-line check doesn't read these
+  lines (webby-0026 N1, webby-0027, defence in depth).
+- It writes `/etc/systemd/system/mosaic-stack.service` as `root:root` 0644. It never uses
+  `systemctl link`, and it refuses a symlink at the unit path.
+- On a re-install, it refuses an installed unit that differs from the render.
+- It reads nothing from under `<user>`'s home.
+
+The precheck refuses unless all of these hold:
+- The config validates.
+- `sudo -n true` fails as `<user>`, and `id -G` prints exactly one entry, its primary group. A system
+  user always has one, so the check is for supplementary groups. `bus.tester` is not on.
+- The business file, `.history`, `changes.jsonl` and persona files have the modes in design 4, and
+  each persona digest matches.
+- The run root is 0700.
+- `XDG_DATA_HOME` is unset or is `<home>/.local/share`. `copy_root` reads the copies dir from it
+  (`scripts/stack-copy.sh:6`), and the unit fixes `<home>/.local/share`, so any other value would
+  put the copy where the unit refuses it (webby-0032 N2). A test sets it elsewhere and the precheck
+  refuses.
+- `node --version` is 24 or later, because every package's `engines` field says `>=24` (row 195: .53
+  has v22.22.2).
+- `bwrap --unshare-all --ro-bind / / true` exits 0 as `<user>`. Without it no session starts. Row 195
+  found no bwrap on .53, and `kernel.apparmor_restrict_unprivileged_userns=1`, and .54 may be the same.
+  On a refusal, the precheck prints the sysctl's value and whether `bwrap` is on PATH.
+- When some creative instance's harness is claude-code, one marker prompt run through the host's claude
+  with `--system-prompt-file` shows that it replaces the default prompt. The claude version is printed.
+  With design r9's model path, Bean and Chet run pi, so this check is skipped unless she adds a
+  claude-code specialist.
+- When an instance's provider is `zai`, `<configDir>/secrets/claude-session.env` exists, is a regular
+  file owned by `<user>` at 0600, and sets a nonempty `ZAI_API_KEY` (design 10 step 2d). It parses the
+  file the way systemd does, so the last assignment of a name wins (webby-0032 N3). A pi launch
+  has no credential check, so without this the first turn is where a missing key shows. The precheck
+  prints the name and never the value.
+- `library.sync` fetches her repo read-only, and `library.status` lists R-problems.
+- No Discord binding exists.
+
+It also prints free memory and verifies HOME is `/srv/mosaic`.
+
+Tests run against a scratch data root and a local bare repo. Each precheck refusal has a case. The
+claude check runs against a fake claude that appends rather than replaces, and that case refuses. With
+no claude-code instance the claude check doesn't run, and a test shows a missing claude passes. The key
+file refuses when missing, at 0644, a symlink, with `ZAI_API_KEY=` empty, and with `ZAI_API_KEY=x`
+followed by `ZAI_API_KEY=`. A search of the test
+output for the fixture key value finds nothing.
+`case2-unit.sh` runs against a scratch unit directory. These cases refuse:
+- an installed unit edited to `User=root`
+- an edited `ExecStart=`
+- a template with a hardening line removed
+- a template with the `EnvironmentFile=` line removed or pointing elsewhere
+- a symlink at the unit path
+- a template with `ExecStartPre=+/srv/mosaic/x`
+- a template with `ExecStartPre=-+/srv/mosaic/x`
+- a copy id that is short, uppercase, holds `/` or `..`, or names no directory
+
+Precheck cases for the new lines: a fake `node` printing v22 refuses, and a fake `bwrap` that exits 1
+refuses. `--profile factory` passes with the tester on and no library items, and refuses a business
+file with a library project. `--profile library` refuses with the tester on.
+A clean render writes a 0644 file. A test checks the script for `systemctl link`.
+
+### Out of scope
+
+Running it on the host. Design 10 steps 2 to 7 are Jason's. Step 1 no longer waits on #421 (Q183), and
+Mos lifted its hold (mos-1074). The root steps 2a and 2c are ops-01's, over ssh as `localadmin`,
+so the install waits on #423 step 1 and on nothing else in #423. The Gitea bot account and the token slot are steps 3 and 4. Stopping Hermes
+is step 9 and her choice.
+
+### Gate
+
+Webby approves the manifest. The test file and the cli suite are green on Sage's gate, along with every
+`scripts/test-*.sh`. The run on the host is a separate window with Jason's go.
+
+---
+
+## C2-14 end-to-end acceptance on a scratch root
+
+### Problem
+
+Each slice row tests its own part. Nothing yet shows the whole path from her push to a checked reply in
+the Console.
+
+### Owner and reviewer
+
+- Owner: an Opus 5.5 seat that Sage picks.
+- Reviewer: Dewey, who also runs the script.
+- After: every other slice row above.
+
+### Files owned
+
+`scripts/test-case2.sh` (new) and its fixtures.
+
+### What ships
+
+One script on a scratch data root and a bare repo in her layout. It syncs, asks a creative agent in its
+thread through a fake harness, and stores a reply whose cites verify. It refuses a playground cite on a
+`fact`, holds a force-push as `library-diverged`, and checks that the Console renders the reply as
+items.
+
+### Out of scope
+
+Any live host or real model call.
+
+### Gate
+
+Dewey runs the script and approves. It is green on Sage's gate with every `scripts/test-*.sh`.
+
+---
+
+## Brief: row A, ZAI_API_KEY in the session env allowlist
+
+### Problem
+
+For 10-27, Bean and Chet both run pi with provider `zai` on `glm-5.3` (Q186, mos-1090, sage-1469). Pi
+reads the zai key from `ZAI_API_KEY` (pi-ai `env-api-keys.js:89`, with `glm-5.3` in `dist/providers/data/zai.json`).
+`ENV_ALLOW` (`packages/seat/src/session.mjs:83-88`) doesn't hold that name, so `sessionEnv` (`:97-99`)
+drops it. A pi launch has no credential check (`packages/plugins/harness/pi/index.mjs:42`
+`countsAccount: false`, `packages/cli/src/launcher.mjs:299`), so today a zai role launches and fails at
+its first turn, as `packages/cli/README.md:439-444` says.
+
+### Owner and reviewer
+
+- Owner: a Haiku 5.5 subagent at high effort, dispatched by Sage (lead decision 129). Size XS.
+- Reviewer: Webby.
+- After: nothing. It doesn't wait on any Case 2 row.
+
+### Files owned
+
+`packages/seat/src/session.mjs`, `packages/seat/tests/session.test.mjs` and `packages/cli/README.md`.
+
+### What ships
+
+- `"ZAI_API_KEY"` joins the provider line of `ENV_ALLOW` (`session.mjs:86`), after `OPENROUTER_API_KEY`.
+  Nothing else in the list changes. `SESSION_CREDENTIALS` and `hasSessionCredential` (`:94-95`) don't
+  change. They are Claude Code's login sets, and a zai key isn't one.
+- `packages/cli/README.md`, after "A Pi session gets the same variables through the allowlist." (`:435`),
+  one sentence: a Pi session on provider `zai` logs in with `ZAI_API_KEY`, which the allowlist passes. Like
+  every allowlist variable, it reaches every session the host starts, Claude Code ones included, and a
+  shell inside any of them can read it. Where the README names `claude-session.env` ("Unit", `:711`),
+  "The file holds one line" becomes "The file holds one line per variable", followed by a sentence
+  saying it holds every session provider key, not only Claude's (webby-0032, webby-0034 N1). Leave
+  `:713`, "nothing in the repository creates or reads it", alone. C2-13 owns that line.
+- One test in `session.test.mjs`: `ENV_ALLOW` includes `ZAI_API_KEY`, and
+  `sessionEnv({ ZAI_API_KEY: "fixture-zai", ZAI_TOKEN: "t" }, run)` returns `ZAI_API_KEY` with the fixture
+  value and no `ZAI_TOKEN`. The existing allowlist test (`:51-59`) stays as it is.
+- One mutant: the same file with `"ZAI_API_KEY"` removed from `ENV_ALLOW`. The new test fails on it.
+
+### Out of scope
+
+Placing a key anywhere. The hub's own key on the Z.ai account is design 10 step 2d, and it is Jason's.
+Any pi launch or live check: running a pi role waits on #383. Chet's Codex login (row B, #428). A
+credential check for pi launches.
+
+### Gate
+
+Webby approves the manifest. The mutant is killed. The seat suite and the cli suite are green on
+Sage's gate with every `scripts/test-*.sh`.
+
+---
+
+## Brief: row B, a per-instance pi agent dir for Chet's Codex login (#428)
+
+### Problem
+
+After 10-27, Chet moves from Bean's Z.ai account to his own ChatGPT/Codex login (Q186). Pi's
+`openai-codex` provider logs in with OAuth and a refresh token, and keeps both in `auth.json` under
+`PI_CODING_AGENT_DIR` (pi `config.js:405-438`). A role session's `HOME` is the run's own, so pi never
+sees an agent dir from the host (`packages/cli/README.md:439-441`), and `ENV_ALLOW` doesn't pass
+`PI_CODING_AGENT_DIR`. So no env variable can carry this login. Each instance needs its own agent dir
+that survives runs, because a refresh rewrites the file.
+
+Chet's Hermes profile uses the same login today. Until Hermes stops, two clients would hold one
+refresh token. If a refresh by one revokes the other's, one of them drops out mid-session.
+
+### Owner and reviewer
+
+- Design: Gosalyn owns it (sage-1469). The build owner and reviewer are named when the design is
+  approved.
+- Starts after 10-27. Nothing in this row is built or tested before then.
+
+### Files owned
+
+None yet. The design names them.
+
+### What ships
+
+The design first. It settles where the dir lives and who can read it, how the launcher mounts it into
+the sandbox writable for one instance only, how a refresh write survives the run, what a shell in the
+session can read, and how a launch with no login refuses. Build rows follow from it.
+
+### Out of scope
+
+Bean's model path. Any change to row A. Any change to Hermes or her server.
+
+### Gate
+
+A live check, run with Jason's or Mos's go, showing that two clients on one ChatGPT login don't revoke
+each other's refresh tokens. Until that check passes, no build row for this design starts.

docs/plans/2026-10-20_federation-r1-r2-r5.md

@@ -0,0 +1,120 @@
+# Federation build rows R1, R2 and R5 (#414)
+
+Sage, 2026-10-20, for Mos's orders mos-1023 item 1, mos-1028 item 2 and mos-1034 item 1. The design is
+Gizmoduck's `agents/gizmoduck/work/federation/DESIGN.md` at a1daa3c07 on `gizmoduck/federation-design` (r4.9,
+sha256 a31cbebd070f9e3a5ca4ccb158b1747c6f5a83c3469855705b0026a581fb5c6a). Duckworth approved r4.5
+(duckworth-0012), r4.6, r4.7 (duckworth-0020) and r4.8 (duckworth-0021, 8a22d0897 on `duckworth/reviews`),
+and acked r4.9 (duckworth-0024). r4.7 applies Jason's Q181 hosts, r4.8 adds N22's R8 checks and r4.9 names who
+runs them. None of them changes R1, R2 or R5. Section 7's table
+sets each row's scope and test gate. Vikunja P19 #414. Seats push only their own `<seat>/*` branches
+(mos-0981).
+
+The other R rows are filed when their parents have candidates: R3 after R1 and row 196, R4 after R3, R5 and
+row 193's viewer level (193a, mos-1019), R6 after #412 phase 1, R1, R2 and R3, R7 after R1-R6 and row 190.
+R8 is a live window, not a code row. Its brief is the last section here.
+
+## Brief: FED R1, the access.json loader and validator
+
+Owner Gizmoduck, reviewer Duckworth, gate owner Sage. Base: refactor at this brief's commit. No parent.
+
+`packages/business/src/access.mjs`: the access.json loader and validator from DESIGN.md section 3.5, and the
+pure `covers`. Providers, peers and businesses come in as arguments. One read plus the file checks. The
+exported interface is what R5 and row 193a build against, so the manifest names it, and any change to it in
+review goes to Sage before it lands. Section 7 names `covers` but not the loader and validator exports or
+the context shape. Morgana's 193a (508ee4d61 on `morgana/row193a`) assumes `checkAccess(doc, {providers,
+peers, businesses})`, with `businesses` mapping an id to `{human, instances}`, throwing a `BusinessError` that
+names the key path. Use those names, or tell Morgana and Quackerjack yours before the manifest goes to
+Duckworth. Row 193a later widens the level check to `viewer` on R1's candidate (mos-1019).
+
+Tests, in `packages/business/tests/`: every rule in 3.5 refuses with the key path named. That covers a
+symlink, a non-regular file, another owner, group or other write, expiry, `*`, a grant disjoint from the given
+subjects, `human` and `tester` ids, any level other than `collaborator`, and a project entry that isn't a
+UUID. For `covers`: `*` and listed ids match, while an unlisted project, instance or business doesn't, an
+expired grant doesn't, and a level filter rejects another level. One mutant per refusal, each killed.
+
+Boundaries: no change to `~/.mosaic-dev`, `~/.config/mosaic-dev`, the live units or any live access.json. Tests
+use scratch roots. Single test files run freely, and suites need Sage's slot.
+
+Gate: Duckworth approves the manifest. The business suite and every `scripts/test-*.sh` are green on Sage's
+gate, and the mutants are killed.
+
+## Brief: FED R5, mosaic access list, grant and revoke
+
+Owner Quackerjack, reviewer Duckworth, gate owner Sage. Chained on R1 (Q177). The build starts now against
+R1's exported interface as the R1 manifest names it, and R5 lands after R1 and rebases onto R1's landing.
+
+`mosaic access list`, `grant` and `revoke`: human proof, atomic write, revision bump, a receipt line. The help
+text states the `instances` limit and the provider-removal order (DESIGN.md section 7, row R5). R4 later makes
+these verbs call `access.reload`, so R5 leaves no other reload path.
+
+Context (sage-1419). `ssoSubjects` is row 192's `console.sso.providers[].subjects` flattened to `{provider,
+sub}` pairs; the design's "`console.sso.subjects`" in 3.5 is shorthand for it. `providers` is the list of
+`providers[].id`, read through `loadSystem` and row 192's `checkConsole`. `peers` is `[]` until R2 lands, so a grant
+naming a peer home refuses. R5 rebases onto row 192's landing as well as R1's.
+
+Tests, in `packages/cli/tests/`: tester and agent callers are refused, a concurrent write refuses on a
+revision conflict, the receipt line is appended, and a bad grant is refused before anything is written. One
+mutant per refusal, each killed.
+
+Boundaries: no change to `~/.mosaic-dev`, `~/.config/mosaic-dev`, the live units or any live access.json. The
+human proof in tests uses the scratch stand-in pattern (a scratch bus verifies its own human-cli path).
+Single test files run freely, and suites need Sage's slot.
+
+Gate: Duckworth approves the manifest. The cli suite and every `scripts/test-*.sh` are green on Sage's gate,
+and the mutants are killed.
+
+## Brief: FED R2, the federation key in the system config
+
+Owner Quackerjack, reviewer Webby, gate owner Sage. Chained on row 192 (#412 phase 1). The build starts when
+row 192 has a candidate, on that candidate.
+
+A `federation` key in `scripts/mosaic-config.mjs` with the shape in DESIGN.md section 3. A config with no
+`federation` key still loads as it does today. This changes the config schema, so the manifest lists every
+reader of the key.
+
+Tests, in `scripts/test-config.sh`: a valid key loads, an unknown sub-key and a bad origin refuse, and a
+config without the key loads. One mutant per refusal, each killed.
+
+Boundaries: `~/.config/mosaic-dev/config.json` is user-authored and is not touched. Tests use scratch config
+dirs only.
+
+Gate: Webby approves the manifest. The cli suite and every `scripts/test-*.sh` are green on Sage's gate, and
+the mutants are killed.
+
+## Brief: FED R8, the hub window on 10.1.1.54
+
+A live window, not a code row (DESIGN.md section 7, row R8). The brief follows r4.11, b93f098f0 on
+`gizmoduck/federation-design` (sha256 1bcee8df0a3a8628a6646535b756c936ca6d9e7bcfa7e1dd2bf1d3f01715c8e6),
+which Duckworth acked with r4.10 (duckworth-0034). Mos closed design rounds there (mos-1072). Run by Jason and
+Mos. Nothing here authorizes a step on any host; each step waits for the window's go.
+
+What changed since r4.9 (DECISIONS Q182, Q183, mos-1055, mos-1063). R8 is a recorded acceptance. It starts
+with Jason's acceptance of the factory paths to .54 on record, quoted in section 8. The privilege and host
+checks still run, and each result goes into the R8 record with the name of whoever ran it. They report and
+don't refuse. The four functional checks named at the end of section 7's R8 row still stop R8 when they fail
+(mos-1066 item 1).
+
+Order (mos-1042 item 2). R8 runs after the Case 2 install on .54 (#416, due by 2026-10-27, Jason's latest-by
+date in Q176, mos-1069), after Bean and Chet are live in Case 2, and after both Hermes gateways on 10.1.1.54
+have stopped. Case 2 go-live doesn't wait on R8. The risk, stated for 10-27: federation between the two
+instances depends on Melanie's switch-over date.
+
+Entry checks, all before anything starts:
+- R7, #412 phase 2 and Jason's #419 answer, as section 7 lists.
+- The four hub user checks on 10.1.1.54 (N22, mos-1035 item 1): `sudo -l -U mosaic` grants nothing, `id
+  mosaic` shows only its own group, `~mosaic/.ssh/authorized_keys` is absent or empty, and no file under
+  `/etc/sudoers.d` names `mosaic`. An agent or Jason runs them as localadmin (mos-1055), and the output goes
+  into the R8 record with who ran them.
+- The factory privilege checks, the key fingerprint comparison and the section 8 privilege path table, each
+  as section 7's R8 row states them.
+
+Build notes:
+- N1 (Duckworth, duckworth-0034, mos-1072). A check that fails on a path Jason didn't name in Q182 or Q183 is
+  marked "not named in Q182 or Q183" in the record, not filed under the acceptance. Examples: a factory mount
+  of hub data, another agent on .54, a provider admin token. Mos takes each one to Jason.
+- N2 (Duckworth, doc-only). The Q183 and Q4 quotes in section 8 are excerpts. When the R8 record quotes them,
+  it marks each omission with "…" and checks the full text at DECISIONS.md:1535-1541 in jason-master-restart
+  (read only).
+
+Done when every entry check has its output recorded, Jason signs in to the hub and sends one message, Melanie
+revokes, and his next request is refused.

docs/plans/2026-10-20_force-push-guard.md

@@ -0,0 +1,81 @@
+# Brief: a pre-push hook that refuses force-pushes, and a busy check that fails on BUSY (#426)
+
+Sage, 2026-10-20, for Mos's order mos-1078 (Vikunja P19 #426) and its go mos-1083 item 1. Owner Rocko,
+reviewer Dewey, gate owner Sage. Base: refactor at this brief's commit. Starts after row 191.
+
+## Why
+
+Morgana force-pushed a seat branch on 2026-10-20 (morgana-0016). Mos took it to Jason. Force-push is a
+Q173 exclusion, and canon says never force-push, but nothing mechanical stops one. Mos: "Done means a
+force-push from a seat worktree is refused, with a test that shows it."
+
+Earlier the same day, a busy check chained as `| tail -1 &&` passed while the slot was BUSY. The script it
+called prints BUSY or CLEAR, but it exits 0 either way.
+
+The guard has two layers:
+- (a) Gitea protection with force-push off on seat branch patterns and on refactor, next and main. ops-01
+  sets it up, through Mos (mos-1082). That part isn't this row.
+- (b) The client hook below. It can be bypassed with `--no-verify`, so (a) is the real guard and (b) is the
+  early refusal.
+
+## What ships
+
+1. `scripts/git-hooks/pre-push` (new). For each ref line git passes on stdin:
+   - It refuses when the remote sha isn't all zeros and isn't an ancestor of the local sha (`git
+     merge-base --is-ancestor`). The refusal names the ref and both shas, and the hook exits 1.
+   - A new branch passes. A delete (local sha all zeros) is refused.
+   - Any failure of the check refuses too, for example an unknown remote object. The hook fetches nothing.
+     If the remote tip isn't present locally, it refuses and says to fetch first.
+2. Install, following `scripts/queue-commit.sh --install-hook`. Either add a `--install-push-hook` there or
+   ship a small `scripts/install-git-hooks.sh`, whichever fits the existing code better. Say which in BUILD.md.
+   - The install copies the hook into the common `.git/hooks`, which every seat worktree shares.
+   - It refuses when `core.hooksPath` is set (the husky trap, 2026-10-09). It refuses when an installed
+     pre-push differs from the repository copy, unless `--force-install` is given.
+   - It never edits the installed copy in place.
+3. `scripts/slot-busy.sh` (new), the shared busy check.
+   - It prints one BUSY line per matching process, or CLEAR.
+   - It exits 0 on CLEAR, 1 on BUSY and 2 on its own error.
+   - It matches `node --test`, `gate.sh`, `mutant`, `scripts/test-*.sh` and `docker compose` command lines.
+     It skips its own process and shell snapshots.
+   - It reads `/proc/<pid>/cmdline` and the cwd link only, never file contents under another seat's
+     directory.
+   - Usage in `docs/TOOLS.md`: `bash scripts/slot-busy.sh > LOG && gate`, with `set -o pipefail` in any
+     script that pipes it. Never `| tail -1 &&`.
+
+## Tests
+
+Add them to `scripts/test-land-work.sh` or a new `scripts/test-git-guard.sh` (say which). Run against a scratch
+bare remote and a scratch clone with a worktree, never against origin:
+- A rewritten branch pushed with `--force` from a worktree is refused, and the remote ref is unchanged.
+- A `+refspec` push is refused.
+- A fast-forward push passes.
+- A new branch passes.
+- A delete is refused.
+- A remote tip that's missing locally is refused.
+- The install refuses with `core.hooksPath` set, and refuses a differing installed hook.
+- `slot-busy.sh` exits 1 with a fake `node --test` process running (a sleeping stand-in with that argv),
+  and 0 without one.
+- `slot-busy.sh | tail -1 && false` doesn't apply here. The test runs `bash scripts/slot-busy.sh >/dev/null
+  && echo ran`, and asserts it doesn't print `ran` while BUSY.
+
+Mutants, each killed:
+- drop the ancestor check
+- treat an unknown remote object as passing
+- let a delete pass
+- install over a set `core.hooksPath`
+- `slot-busy.sh` exits 0 on BUSY
+
+## Boundaries
+
+- Install the hook in the canonical checkout only after landing, as its own step with Sage. Tests use
+  scratch repositories.
+- No push to origin from a test. No change to Gitea config. That's ops-01's.
+- Don't touch `~/.mosaic`, `~/.mosaic-dev` or `~/.config/mosaic-dev`.
+
+## Gate
+
+Dewey approves the manifest. The new or changed `scripts/test-*.sh` file and every other `scripts/test-*.sh`
+are green on Sage's gate, and the mutants are killed. Done when the hook is installed in the canonical
+checkout and a scripted force-push from a seat worktree to a scratch remote is refused there. ops-01's
+server proof (a refused force-push, plus a fast-forward push and a new branch that go through) is recorded
+in Vikunja #426 by Mos.

docs/plans/2026-10-20_host-credentials.md

@@ -0,0 +1,70 @@
+# Brief: agent host access with sudo through the credential store (#424)
+
+Sage, 2026-10-20, for Jason's rulings Q183 and Q184 relayed by Mos (mos-1056 item 3, mos-1067). Gitea #1707, Vikunja P19
+#424, due 2026-10-27 (Q184: "Q5: by 10.27"). Owner Gizmoduck (design and build), reviewer Duckworth, gate owner
+Sage. Chained on row 199's candidate (Q177): row 199 design r6 (4d3007ec9 on `megavolt/row199`, approved in
+duckworth-0027) is not reopened. This row lands after 199 and rebases onto its landing.
+
+## What Jason asked for
+
+Q183, through Mos: "I envision a credential store within Mosaic Stack that works as some sort of variable for
+the agent to call. The system will enforce access to the credentials to keep the agents sandboxed with proper
+security... If we can utilize the credential store in Mosaic Stack and allow agents to perform their jobs with
+NOPASSWD sudo on various machines, I am a happy man." Q183 also says not every agent needs that access.
+
+Mos's requirements (mos-1067 item 1):
+- An agent asks for a host credential by name.
+- The stack checks a grant for that agent and that host, and does the ssh and sudo for it.
+- The agent never sees the key or any secret value.
+- Only agents with a grant can do it.
+
+The PRD text is REQ-CRED-3, drafted by Honker for PRD 1.7 (sage-1422). If it misses 1.7 it goes into 1.8, and
+this row lands only after the version that holds it is approved.
+
+## What row 199 gives and what it doesn't (megavolt-0019)
+
+It builds on 199 as 199 stands: the store layout under `<configDir>/secrets/agents/<business>/<agent>/`, the
+lifecycle verbs and their `changes.jsonl` receipts, `useFor(session, service, fn)` with the D5 allowlist test,
+`assertClean` on every result, and the grant shape of `publish` (a list on the role entry, checked by the
+broker, plus a hard-wait action that isn't routed).
+
+This row's own changes:
+- A host kind in the closed kind set (vocabulary.mjs `SERVICES`, credentials.mjs, the broker's service check,
+  the CLI date flag, the remove regex), with a naming rule for one credential per host or per agent.
+- A per-kind value check. An OpenSSH private key fails today's `TOKEN` pattern.
+- Handing the key to ssh without the agent seeing it: an ssh-agent on a private socket, or a 0600 temp file
+  removed on every path, the way publish's one-shot helper works.
+- Pinned host keys per host, and no trust on first use.
+- The command boundary: what an agent may run under sudo, and how output returns without echoing the secret.
+  This is the main design work.
+- The executor: a ticket and a host op running in the bus child, the same split row 199 uses for publish
+  (Megavolt's deviation in 199's BUILD.md).
+
+## Steps
+
+1. DESIGN.md first, in `agents/gizmoduck/work/queue-ROW/`. It answers each item above, names the grant shape
+   (`roles.<agent>.hosts` and a `host.sudo` action, or a reasoned alternative), says who grants (Jason, through
+   a reviewed role change, unless REQ-CRED-3 says otherwise), and lists tests and mutants. Duckworth approves it
+   before code. Sage reads it too, because it gives agents sudo on hosts.
+2. Build on 199's candidate. Single test files run freely. Suites and mutant batches need Sage's slot.
+3. The live part is not this row. Putting a key in the store and granting a host is a separate window with
+   Jason or Mos, after landing.
+
+## Hosts
+
+The first targets are `localadmin` with NOPASSWD sudo on 10.1.1.53 and 10.1.1.54 (#423 step 1, applied by
+ops-01 at 20:05:47Z), and the servers agents already reach as localadmin (Q172). ops-01 owns the host side.
+Tests use scratch sshd fixtures on 127.0.0.1 or fakes, never a real host.
+
+## Boundaries
+
+- No change to `~/.mosaic-dev`, `~/.config/mosaic-dev`, slot files, the live units or `~/.mosaic`. No key is
+  read, copied or printed. No ssh to any real host from a test or a seat.
+- No widening of row 199's kinds or regex inside row 199. Both rows touch them, so this row rebases after 199
+  lands.
+
+## Gate
+
+Duckworth approves DESIGN.md, then the manifest. The bus, business and cli suites and every
+`scripts/test-*.sh` are green on Sage's gate, and the mutants are killed (one per refusal, plus one that leaks
+the key into the agent's output and one that skips the host key pin).

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

@@ -0,0 +1,66 @@
+# Brief: the Case 1 install on 10.1.1.53 (row 195)
+
+Sage, 2026-10-20, third version, for Darkwing's rewrite request and sage-1439. Gitea #1693.
+
+Why it changed:
+- The first two versions put Melanie's hub on its own Linux user, then on its own host, Jason's choice under
+  #419.
+- Q181 settled the hosts: Case 1 (Jason's software factory) runs on 10.1.1.53 and Case 2 (Melanie's hub) on
+  10.1.1.54.
+- Q182 and Q183 made the hub's privilege checks a recorded acceptance. They report and don't refuse
+  (federation R8, mos-1055, mos-1063, mos-1066).
+- The Case 2 install on .54 is Gosalyn's C2-13 plus its window (#416, due by 2026-10-27). It is not this row.
+
+This row now installs Case 1 on .53. On the 10-27 MVP path (mos-0974, T1 item 1).
+
+Owner Darkwing (Opus 5.5), reviewer Duckworth, gate owner Sage. Chained on row 190's candidate (the config
+canon) and on C2-13's candidate (the install script), Q177. It reuses C2-13's `case2-install.sh`,
+`case2-precheck.sh` and `case2-unit.sh` by input, not by copy. A gap in them goes to Gosalyn as a C2-13
+change, or into this row's manifest as a named, reviewed change to those files. Design first:
+`agents/darkwing/work/queue-195/DESIGN.md`.
+
+## Goal
+
+Jason's software factory runs on 10.1.1.53 as `mosaic` under `/srv/mosaic`, in the same unit form as Case 2
+(design 9, Q181). It uses row 190's config canon and the model account the factory uses today (Q185,
+mos-1081 item 1). No new provider account.
+
+## Provision
+
+- ops-01 runs the root steps over ssh as `localadmin`: `useradd mosaic`, `/srv/mosaic` and the unit through
+  `case2-unit.sh` from a root-owned checkout. #423 step 1 (localadmin with NOPASSWD sudo on .53 and .54) was
+  applied at 20:05:47Z (mos-1066, mos-1077), and nothing else in #423 gates this row.
+- #423 step 4 (jarvis sudo) waits until Case 1 is live on .53.
+- The host list comes from Q181. Agents may run read-only checks on .53 as `localadmin`.
+
+## The design must state
+
+1. The install as input values to C2-13's scripts: user, home, business file, roles, the human id, the
+   token slot path. Which commands run as `mosaic` through `sudo -u mosaic -H`, and which as root through
+   ops-01.
+2. Where Case 1 differs from Case 2: the factory roles in place of the library business, no library sync,
+   and any precheck item that doesn't apply, each with a reason.
+3. Model access through the existing factory account (Q185). Placing the credential on .53 is a step under
+   the Q173 secrets rule, done in the window. It is never copied by the script, and its value is never
+   printed.
+4. Re-pin, rollback and backup on .53, and who runs them.
+5. The acceptance checks, as code Duckworth can read. Each check names a path and gives it one of three
+   marks: closed, accepted under Q182 or Q183, or "not named in Q182 or Q183". An accepted path doesn't
+   fail the row. An unnamed one is reported to Mos, who takes it to Jason (the R8 N1 rule). The functional
+   checks fail the row when they fail: the unit runs as `mosaic`, the Console answers on its port on the
+   internal network only, and one tester message gets a reply.
+
+## Boundaries
+
+- Infra and k3s changes, exposure outside the internal network, and spend stay Jason's (Q173 exclusions).
+- No change to dragon-lin's `~/.mosaic-dev`, `~/.config/mosaic-dev`, its live units or `~/.mosaic`.
+- No credential value is printed, logged or committed.
+- Tests use scratch roots and stand-ins. Nothing in a test reaches .53.
+- The run on .53 is a window with Jason's or Mos's go, a backup first where state exists, and a STATE report
+  after.
+
+## Gate
+
+Duckworth approves DESIGN.md, then the manifest. Any repository change is green on Sage's gate (cli suite and
+every `scripts/test-*.sh`), with the design's mutants killed. The row is done when the window's acceptance
+run passes on .53, Duckworth reads its output, and Mos confirms.

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-build.md

@@ -0,0 +1,70 @@
+# Row 193 build rows: 193a, 193b1, 193b2, 193c and 193d (#1691)
+
+Sage, 2026-10-20, for Mos's go mos-1034 item 4. Row 193's design is Morgana's
+`agents/morgana/work/queue-193/DESIGN.md` at e2d161e2e on `morgana/row193` (r5, sha256
+dd7fcb419ed8510e9d8d74b569183386d0942af8b68eecc0bbb5e182e677b523), approved by Duckworth (duckworth-0018).
+Section 8 lists the tests and mutants, and section 9 the split. The brief behind them is
+`docs/plans/2026-10-20_human-users.md`. Vikunja P19 #414/#415, Gitea #1691.
+
+Owner Morgana for every row, reviewer Duckworth, gate owner Sage. Each row chains on its parent's candidate
+(Q177) and rebases onto the parent's landing. Seats push only their own `<seat>/*` branches (mos-0981).
+Single test files run freely, and suites and mutant batches need Sage's slot.
+
+Boundaries for every row: no change to `~/.mosaic-dev`, `~/.config/mosaic-dev`, the live units, slot files, any
+live access.json or `~/.mosaic`. No request to the live Console, mosaic.woltje.com or auth.diversecanvas.com.
+No user thread goes live before 193b1's message filter has landed (mos-1021 B2, FED R8).
+
+The owner-visible records are fixed by Mos (mos-1023 item 2) and named in one user sentence, which FED R6
+reuses word for word: "The business owner sees your thread's agent's decisions, inbox entries, claims, tasks
+and project files, but not your messages."
+
+## Brief: 193a, the access level check widened to viewer
+
+Chained on FED R1. Started early on `morgana/row193a` (508ee4d61) against R1's interface as the FED brief
+names it, with Sage's go (sage-1373). R1's level check accepts `viewer` and still refuses any other new
+level. Tests in `packages/business/tests/` (section 8, Business), with the four mutants in Morgana's
+BUILD.md. FED R4 chains on this row.
+
+Duckworth's N1 on R1 (duckworth-0033, sage-1417): with viewer added, `covers` called with no level would let a
+viewer grant cover a collaborator ask. This row makes `level` required in `covers`, with a test and a mutant that
+makes it optional again. R3 and R4 call `covers` with a level.
+
+Gate: Duckworth approves the manifest. The business suite and every `scripts/test-*.sh` are green on Sage's
+gate, and the mutants are killed.
+
+## Brief: 193b1, viewer verbs, board refusals and the message filter
+
+Chained on FED R3, FED R4 and row 196's verifier. The bus gets the viewer verb list, per-grant level
+checks, board reads refused to users, and the section 5.7 `trail` and `replies` filter with `#readable`
+owner-only. No schema change. The governance pin test names each item in the user sentence above. Bus tests
+and mutants 1, 3, 6, 10, 11 and 12 from section 8.
+
+Gate: Duckworth approves the manifest. The bus suite and every `scripts/test-*.sh` are green on Sage's gate,
+and the mutants are killed.
+
+## Brief: 193b2, thread shares (schema 3j)
+
+Chained on 193b1. `thread_shares`, the share verbs, the share rules of `#readable` and `#threadRead`, and the
+section 5.5 share filters. Schema 3i to 3j. The table is append-only, and row 181's restore guard and
+`COUNTED` include it. Bus tests for shares and the migration, and mutants 2, 4, 7, 8 and 9 from section 8.
+Going live needs a `--migrate` window with Jason. Sage takes it to Mos when this row is near.
+
+Gate: Duckworth approves the manifest. The bus suite, the cli suite and every `scripts/test-*.sh` are green on
+Sage's gate, and the mutants are killed.
+
+## Brief: 193c, mosaic access user verbs and --level viewer
+
+Chained on FED R5. `mosaic access user add/remove` and `grant --level viewer`, only where R5 lacks them. They
+refuse tester and agent callers, write a receipt line and call `access.reload` (section 8, CLI). If R5
+already has all of them, this row records that and closes with no code.
+
+Gate: Duckworth approves the manifest. The cli suite and every `scripts/test-*.sh` are green on Sage's gate,
+and the mutants are killed.
+
+## Brief: 193d, the Console's shared list, share controls and viewer read-only
+
+Chained on FED R6, row 192 and 193b2 (for share controls). A viewer has no composer or share control, and
+with each UI check removed the bus still refuses (section 8, Webui).
+
+Gate: Duckworth approves the manifest. The webui suite and every `scripts/test-*.sh` are green on Sage's
+gate, and the 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_retire-control-board.md

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

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

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

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

@@ -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/2026-10-20_stack-release-sso.md

@@ -0,0 +1,39 @@
+# Brief: stack-release.sh activates a Console with --sso (Q175 phase 2 prerequisite)
+
+Sage, 2026-10-20, for Launchpad's finding F3 on row 192 (launchpad-0001) and Q175 (#412). Gitea #1698. Owner
+Launchpad, reviewer Webby, gate owner Sage. Chained on row 192's candidate (Q177): it lands after row 192 and
+before the phase 2 window. Base: row 192's candidate.
+
+## Why
+
+The phase 2 window re-pins the Console to the phase 1 commit with `--sso --send --tester-port 7333`
+(`agents/sage/work/q175-sso/DESIGN.md`, section 5). `scripts/stack-release.sh` doesn't know `--sso` today.
+Its `proof_checks` (`:751`) requires `--public-host`, `--auth-header` and `--allow-user` whenever a proof pair is
+carried, and the pointer's Console flags still hold the forward-auth pair (`--auth-header X-authentik-username
+--allow-user jason.woltje`) that `--sso` refuses to start with. So the window can't run through the script, and
+a hand-edited pointer is not an option.
+
+## What the row does
+
+1. `activate ID BUSINESS --sso` writes Console flags with `--sso` and without `--auth-header`, `--allow-user`
+   and any proof pair, and `--plan` names each flag it drops and carries, in the style of row 189's `send:`
+   line. The design names the full flag set the phase 2 Console starts with and checks it against row 192's
+   refusals.
+2. Before anything stops, the script refuses a target copy whose Console doesn't support `--sso`, and refuses
+   when the config's `console` key or its slot file fails the checks row 192's `--sso` start runs. It reads
+   neither value and only uses the same stat and shape checks.
+3. Rollback from an `--sso` pointer to a pre-phase-1 copy follows the design's phase 2 rollback order (remove
+   the `console` key first). The script refuses a rollback that would start a Console on a config it can't
+   read, and says which step comes first.
+4. `docs/TOOLS.md` gets the flag.
+
+## Boundaries
+
+- No change to the live pointer, units, `~/.mosaic-dev` or `~/.config/mosaic-dev`. Tests use scratch roots
+  and seeded pointers, as rows 187 and 189 do.
+- No request to the live Console, mosaic.woltje.com or auth.diversecanvas.com.
+
+## Gate
+
+Webby approves the manifest. The cli suite and every `scripts/test-*.sh` are green on Sage's gate, and the
+mutants are killed (one per refusal, and one that keeps `--auth-header` in the written flags).

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 2361 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,29 @@ 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 | done | 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 | Landed ace27dc5e on refactor (cherry-pick of candidate d6116771f onto a4a42dbac). Gate GATE_PASSED on 0c177e9ef (base 0217b71c8), 2026-10-20T19:09:37Z-19:20:36Z, 25 suites rc=0. patch-id ce89378718f6 for both 0c177e9ef and ace27dc5e; range-diff differs only in the message. Landed manifest hashes to 67af69bd (Dewey approve 29485). Base drift 0217b71c8..a4a42dbac: 7 doc/README files, none on manifest paths, no test reads them. Brief re-pinned to blob 29a9e6d2d. |
+| 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-review, round 1, request posted | — | 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 | — |
+| 192 | Q175 phase 1: the Console verifies SSO itself (--sso), OIDC RP with oauth4webapi 3.8.8, no live change (MVP T1.2, #412) | launchpad; reviewers webby | #1690 | in-review, round 2, request posted | — | Webby approves the manifest; webui and cli suites, scripts/test-config.sh and every scripts/test-*.sh green on Sage's gate; design section 9 mutants killed (sage) | `docs/plans/2026-10-20_sso-phase1.md` § Brief: Q175 phase 1, the Console verifies SSO itself (--sso) | — |
+| 193 | many humans per business, human roles, private and shared threads, one access.json store (MVP T1.3, Vikunja #414/#415) | morgana; reviewers duckworth | #1691 | in-progress | — | Duckworth approves DESIGN.md then the manifest; bus, business, cli and webui suites and every scripts/test-*.sh green on Sage's gate; the mutants killed (sage) | `docs/plans/2026-10-20_human-users.md` § Brief: many humans per business, human roles, private and shared threads | — |
+| 194 | agent lifecycle from the Console and the CLI (create, launch, terminate, regenerate, delete) with a per-agent hire/fire veto (MVP T1.5, Vikunja #414/#415) | honker; reviewers webby | #1692 | in-progress | — | Webby approves DESIGN.md then the manifest; bus, cli, business and webui suites and every scripts/test-*.sh green on Sage's gate; the mutants killed (sage) | `docs/plans/2026-10-20_agent-lifecycle.md` § Brief: agent lifecycle from the Console and the CLI, with a per-agent hire/fire veto | — |
+| 195 | row 195: the Case 1 install on 10.1.1.53 as mosaic under /srv/mosaic, reusing C2-13's scripts by input under row 190's canon (Q181, Q182/Q183, Q185; ops-01 root steps under #423 step 1) | darkwing; reviewers duckworth | #1693 | briefed | 190 done | Duckworth approves DESIGN.md then the manifest; cli suite and every scripts/test-*.sh green on Sage's gate; the mutants killed (sage) | `docs/plans/2026-10-20_hub-own-uid.md` § Brief: the Case 1 install on 10.1.1.53 (row 195) | sage-1439: rewritten to Case 1 on .53 (f24f2cd40). Chains on C2-13's candidate too once C2-13 is queued. Darkwing starts DESIGN.md after row 190's mutants. |
+| 196 | the human boundary across uids and humans: Console, tester listener, broker.sock and the path-bound human proof (P19 333, before federation R3, mos-0989) | gander; reviewers duckworth | #1694 | in-progress | — | Duckworth approves DESIGN.md then the manifest; bus, webui and cli suites and every scripts/test-*.sh green on Sage's gate; the mutants killed (sage) | `docs/plans/2026-10-20_human-boundary.md` § Brief: the human boundary across uids and humans (P19 333) | — |
+| 197 | a second gate lane: two full gates at once on dragon-lin, design first (mos-0977 item 6) | herb; reviewers webby | #1695 | in-progress | — | Webby approves DESIGN.md then the manifest; cli suite and every scripts/test-*.sh green on Sage's gate, singly and in the two-lane proof (sage) | `docs/plans/2026-10-20_second-gate-lane.md` § Brief: a second gate lane, two full gates at once on dragon-lin | Order with row 198 (Sage, mos-1040 N1): 197 lands first. After B1 the shared tests are packages/webui/tests/serve.test.mjs:100 and preview.test.mjs:208. Row 198 rebases onto 197's landing before its manifest review. |
+| 198 | retire the control board writer on 7331 (unauthenticated loopback writer, Q175; mos-1008) | bushroot; reviewers webby | #1696 | in-progress | 192 done, 197 done | Webby approves INVENTORY.md then the manifest; control-board, webui and cli suites and every scripts/test-*.sh green on Sage's gate; the mutants killed (sage) | `docs/plans/2026-10-20_retire-control-board.md` § Brief: retire the control board writer on 7331 | Order with row 197 (Sage, mos-1040 N1): 197 lands first. Row 198 rebases onto 197's landing before its manifest review; shared tests are packages/webui/tests/serve.test.mjs:100 and preview.test.mjs:208. |
+| 199 | MVP T1 item 6: a credential store per agent, own git identity, pushes to a remote (G11, G13; mos-0974) | megavolt; reviewers duckworth | #1697 | in-progress | — | Duckworth approves DESIGN.md; Mos rules on the authority model; Duckworth approves the manifest; bus, business, cli and tasks suites and every scripts/test-*.sh green on Sage's gate; the mutants killed (sage) | `docs/plans/2026-10-20_agent-credentials.md` § Brief: a credential store per agent, own git identity, pushes to a remote | — |
+| 200 | stack-release.sh activate --sso for the Q175 phase 2 window (row 192 F3; chained on 192) | launchpad; reviewers webby | #1698 | in-review, round 2, request posted | — | Webby approves the manifest; cli suite and every scripts/test-*.sh green on Sage's gate; the mutants killed (sage) | `docs/plans/2026-10-20_stack-release-sso.md` § Brief: stack-release.sh activates a Console with --sso (Q175 phase 2 prerequisite) | — |
+| 201 | FED R1: access.json loader and validator, and covers (#414) | gizmoduck; reviewers duckworth | #1699 | in-review, round 1, request posted | — | Duckworth approves the manifest; business suite and every scripts/test-*.sh green on Sage's gate; the mutants killed (sage) | `docs/plans/2026-10-20_federation-r1-r2-r5.md` § Brief: FED R1, the access.json loader and validator | — |
+| 202 | FED R5: mosaic access list, grant and revoke (#414) | quackerjack; reviewers duckworth | #1700 | in-review, round 1, request posted | — | Duckworth approves the manifest; cli suite and every scripts/test-*.sh green on Sage's gate; the mutants killed (sage) | `docs/plans/2026-10-20_federation-r1-r2-r5.md` § Brief: FED R5, mosaic access list, grant and revoke | Chained on row 201's candidate (Q177), not its done: claimable now, lands after 201 and rebases onto its landing (Sage) |
+| 203 | FED R2: the federation key in the system config (#414) | quackerjack; reviewers webby | #1701 | briefed | — | Webby approves the manifest; cli suite and every scripts/test-*.sh green on Sage's gate; the mutants killed (sage) | `docs/plans/2026-10-20_federation-r1-r2-r5.md` § Brief: FED R2, the federation key in the system config | Chained on row 192's candidate (Q177): starts on 192's candidate, lands after 192 (Sage) |
+| 204 | 193a: access level check widened to viewer (#1691) | morgana; reviewers duckworth | #1702 | in-review, round 1, request posted | — | Duckworth approves the manifest; business suite and every scripts/test-*.sh green on Sage's gate; the mutants killed (sage) | `docs/plans/2026-10-20_human-users-build.md` § Brief: 193a, the access level check widened to viewer | Chained on row 201's candidate (Q177), not its done: claimable now, lands after 201 and rebases onto its landing (Sage) |
+| 205 | 193b1: viewer verbs, board refusals and the message filter (#1691; also after FED R3 and R4 when filed) | morgana; reviewers duckworth | #1703 | queued | 196 done | Duckworth approves the manifest; bus suite and every scripts/test-*.sh green on Sage's gate; the mutants killed (sage) | `docs/plans/2026-10-20_human-users-build.md` § Brief: 193b1, viewer verbs, board refusals and the message filter | — |
+| 206 | 193b2: thread shares, schema 3j (#1691; live needs a --migrate window with Jason) | morgana; reviewers duckworth | #1704 | queued | 205 done | Duckworth approves the manifest; bus suite, cli suite and every scripts/test-*.sh green on Sage's gate; the mutants killed (sage) | `docs/plans/2026-10-20_human-users-build.md` § Brief: 193b2, thread shares (schema 3j) | — |
+| 207 | 193c: mosaic access user verbs and --level viewer (#1691) | morgana; reviewers duckworth | #1705 | queued | 202 done | Duckworth approves the manifest; cli suite and every scripts/test-*.sh green on Sage's gate; the mutants killed (sage) | `docs/plans/2026-10-20_human-users-build.md` § Brief: 193c, mosaic access user verbs and --level viewer | — |
+| 208 | 193d: Console shared list, share controls and viewer read-only (#1691; also after FED R6 when filed) | morgana; reviewers duckworth | #1706 | queued | 192 done, 206 done | Duckworth approves the manifest; webui suite and every scripts/test-*.sh green on Sage's gate; the mutants killed (sage) | `docs/plans/2026-10-20_human-users-build.md` § Brief: 193d, the Console's shared list, share controls and viewer read-only | — |
+| 209 | FED R8: the hub window on 10.1.1.54, a recorded acceptance (#414, r4.11 b93f098f0; live window run by Jason and Mos, after the Case 2 install #416, Bean and Chet live and both Hermes gateways stopped) | sage; reviewers duckworth | — | queued | — | Every entry check's output is in the R8 record with who ran it; Jason signs in to the hub and sends one message, Melanie revokes, his next request is refused; Duckworth checks the record (sage) | `docs/plans/2026-10-20_federation-r1-r2-r5.md` § Brief: FED R8, the hub window on 10.1.1.54 | Stays queued until its entry gates near: Case 2 install on .54 (#416, by 2026-10-27), Bean and Chet live, both Hermes gateways on .54 stopped, R7, #412 phase 2, #419 answer. Filed per mos-1073 after duckworth-0034 (Sage) |
+| 210 | Agent host access with sudo through the credential store: grant per agent and host, the stack does ssh and sudo, the agent never sees the key (#1707, Vikunja #424, Q183/Q184, due 10-27; chained on row 199's candidate) | gizmoduck; reviewers duckworth | #1707 | in-progress | — | Duckworth approves DESIGN.md, then the manifest; bus, business, cli suites and every scripts/test-*.sh green on Sage's gate; the mutants killed (sage) | `docs/plans/2026-10-20_host-credentials.md` § Brief: agent host access with sudo through the credential store (#424) | Design runs before 199 lands (Q177 chain on 199's candidate). after cleared so Gizmoduck can claim; lands only after 199 and rebases onto it. |
+| 211 | Force-push guard: scripts/git-hooks/pre-push refuses non-fast-forward and delete pushes from every worktree, and scripts/slot-busy.sh exits 1 on BUSY (#1709, Vikunja #426, mos-1078/1083) | rocko; reviewers dewey | #1709 | briefed | — | Dewey approves the manifest; the new or changed scripts/test-*.sh and every other scripts/test-*.sh green on Sage's gate; the mutants killed; hook installed in the canonical checkout with a scripted refused force-push (sage) | `docs/plans/2026-10-20_force-push-guard.md` § Brief: a pre-push hook that refuses force-pushes, and a busy check that fails on BUSY (#426) | — |
 
 <!-- mosaic-queue:end -->
 

packages/cli/tests/stack-copy.test.mjs

@@ -34,7 +34,7 @@ export function setup(t, realPin=false){
 test('shared copy: npm ci, pushed reachability, readonly/existing copy, webui delegation',t=>{
  const s=setup(t),r=s.run('stack-copy.sh',['copy',s.id,'--copies',s.copies]);assert.equal(r.status,0,r.stderr);
  const copy=join(s.copies,s.id);assert.equal(statSync(copy).mode&0o777,0o555);
- for(const f of ['scripts/mosaic','adapters/pi/adapter.sh','packages/queue/src/cli.mjs','package.json','package-lock.json','packages/tasks/requirements.json','packages/project/src/index.mjs','packages/project/schemas/project.schema.json','packages/project/templates/north-star.md','packages/plugins/src/kinds.mjs','packages/plugins/src/loader.mjs'])assert.ok(existsSync(join(copy,f)),f);
+ for(const f of ['scripts/mosaic','adapters/pi/adapter.sh','packages/queue/src/cli.mjs','package.json','package-lock.json','packages/tasks/requirements.json','packages/project/src/index.mjs','packages/library/src/index.mjs','packages/project/schemas/project.schema.json','packages/project/templates/north-star.md','packages/plugins/src/kinds.mjs','packages/plugins/src/loader.mjs'])assert.ok(existsSync(join(copy,f)),f);
  const npm=join(s.bin,'npm');writeFileSync(npm,'#!/bin/sh\nexit 99\n');chmodSync(npm,0o755);
  const existing=s.run('webui-service.sh',['copy',s.id,'--copies',s.copies]);assert.equal(existing.status,0);assert.equal(existing.stdout,`exists: ${copy}\n`);unlinkSync(npm);
  git(s.repo,'update-ref','refs/remotes/origin/refactor',git(s.repo,'hash-object','-w','package.json'));

packages/cli/tests/stack-release.test.mjs

@@ -381,7 +381,7 @@ async function seed(e,{copy=B,pm=false,store='3g',pointer:how='adopt'}={}){
 const rolledBack=(code,to=B)=>`stack-release: ${code}; rolled back to ${to}, which passed the gate\n`;
 const planBackup=(e)=>`backup: the run backs up the stopped store to ${e.data}/backups/stack/<activation>/ before any migration`;
 const planNoBackup='backup: none; the run rolls back before the backup';
-const planTail=(e,to,pm=false)=>[`bus: scripts/bus-service.sh install --copy ${to} --copies ${COPIES}${pm?' --pm':''} --claude ${e.claude}`,'proof: off',`Console: scripts/webui-service.sh install --copy ${to} --copies ${COPIES} --port ${e.port} --business acme`,`CLI: scripts/stack-copy.sh wrapper ${to} --copies ${COPIES} --bin ${e.bin}`];
+const planTail=(e,to,pm=false)=>[`bus: scripts/bus-service.sh install --copy ${to} --copies ${COPIES}${pm?' --pm':''} --claude ${e.claude}`,'proof: off','send: off',`Console: scripts/webui-service.sh install --copy ${to} --copies ${COPIES} --port ${e.port} --business acme`,`CLI: scripts/stack-copy.sh wrapper ${to} --copies ${COPIES} --bin ${e.bin}`];
 
 // --- The T table ---
 
@@ -1030,17 +1030,17 @@ test('T36 --plan shows the pending state and lists the row 169 refusals it can s
   return r.out.split('\n');
  };
  let out=await quiet(0,'activate',C1,'acme','--pm-after-harness','--plan');
- assert.deepEqual(out.slice(-6),['pm: the bus starts without --pm and the PM stays pending; next: Jason\'s plugins set of harness, then pm-on',...planTail(e,C1),'']);
+ assert.deepEqual(out.slice(-7),['pm: the bus starts without --pm and the PM stays pending; next: Jason\'s plugins set of harness, then pm-on',...planTail(e,C1),'']);
  biz(e,HARNESS);
  out=await quiet(3,'activate',A,'acme','--pm-after-harness','--plan');
- assert.deepEqual(out.slice(-7),['pm: the bus starts without --pm and the PM stays pending; next: Jason\'s plugins set of harness, then pm-on',...planTail(e,A),`refuses unknown-kind-for-target: the business file names plug-in kind(s) harness, which ${A} does not know`,'']);
+ assert.deepEqual(out.slice(-8),['pm: the bus starts without --pm and the PM stays pending; next: Jason\'s plugins set of harness, then pm-on',...planTail(e,A),`refuses unknown-kind-for-target: the business file names plug-in kind(s) harness, which ${A} does not know`,'']);
  out=await quiet(3,'activate',C1,'acme','--pm-after-harness','--plan');
  assert.equal(out.at(-2),'refuses pm-after-harness-set: the business file already sets harness ["claude-code"]; use --pm');
  biz(e);assert.equal((await run(e,'activate',C1,'acme','--pm-after-harness')).code,0);
  out=await quiet(3,'activate',C,'acme','--plan');
- assert.deepEqual(out.slice(-7),['pm: the pointer is pending (activate --pm-after-harness); the bus runs without its PM',...planTail(e,C,true),`refuses pm-pending: ${PENDING_MSG}`,'']);
+ assert.deepEqual(out.slice(-8),['pm: the pointer is pending (activate --pm-after-harness); the bus runs without its PM',...planTail(e,C,true),`refuses pm-pending: ${PENDING_MSG}`,'']);
  out=await quiet(0,'rollback','acme','--plan');
- assert.deepEqual(out.slice(-6),['pm: the pointer is pending (activate --pm-after-harness); the bus runs without its PM',...planTail(e,B,true),'']);
+ assert.deepEqual(out.slice(-7),['pm: the pointer is pending (activate --pm-after-harness); the bus runs without its PM',...planTail(e,B,true),'']);
 });
 
 // Row 176 test 11: supported and older Console copies deliberately differ from the checkout.
@@ -1706,6 +1706,113 @@ test('T54 row 188: a carried pair gets the proof file checks, and a proof file i
  });
 });
 
+// Row 189 (#1687, mos-0972/0973): activate --no-send drops the pointer's --send; nothing turns it back on.
+const sendLines=(out)=>out.filter((l)=>l.startsWith('send:'));
+const noSend=(c)=>c.filter((x)=>x!=='--send');
+const LIVE_NOTE=`note: ${B} is the pointer's copy; the run re-pins it and only the Console flags change`;
+test('T55 row 189: activate --no-send drops --send, and rollback and pm-on carry it off',async(t)=>{
+ await t.test('test 1: a live-copy --no-send drops --send from the pointer and the unit, keeps the rest in order, logs the step and backs up the stopped store',async(t)=>{
+  const e=await mk(t),base=await seedPreview(e,undefined,['--send','--tester-port','7333']),want=noSend(base);
+  assert.deepEqual(want.slice(-2),['--tester-port','7333']);
+  const sum=createHash('sha256').update(readFileSync(e.store)).digest('hex'),n=calls(e).length;
+  let r=await prun(e,'activate',B,'acme','--no-send');assert.equal(r.code,0,r.out+r.err);
+  assert.equal(pointer(e).copy,B);assert.deepEqual(pointer(e).console,want);
+  assert.ok(conExec(e).endsWith(` --checkout ${repo} ${want.join(' ')}`),conExec(e));assert.doesNotMatch(conExec(e),/ --send( |$)/);
+  r=await prun(e,'status','acme');assert.equal(r.code,0,r.err);assert.match(r.out,/unit flags: match the pointer/);
+  assert.match(stepText(e),/Z drop --send; --no-send was given\n/);
+  const act=pointer(e).activation,l=logLines(e).at(-1);
+  assert.deepEqual([l.op,l.from,l.to,l.result,l.backup],['activate',B,B,'ok',act]);assert.equal(backupSum(e,act),sum);
+  assert.deepEqual(startsStops(e,n),[`stop ${CON}`,`stop ${BUS}`,`start ${BUS}`,`start ${CON}`]);
+  await noLeak(e);
+ });
+ await t.test('test 2: a plain live-copy activate still refuses already-active, and so does --no-send once --send is gone',async(t)=>{
+  const e=await mk(t);await seedPreview(e,undefined,['--send']);
+  await refused(e,['activate',B,'acme'],'already-active',`${B} is the pointer's copy`);
+  await refused(e,['activate',B,'acme','--tester-port','7333'],'already-active',`${B} is the pointer's copy`);
+  await refused(e,['activate',B,'acme','--no-proof'],'already-active',`${B} is the pointer's copy`);
+  const r=await prun(e,'activate',B,'acme','--no-send');assert.equal(r.code,0,r.out+r.err);
+  await refused(e,['activate',B,'acme','--no-send'],'already-active',`${B} is the pointer's copy`);
+  const g=await mk(t);await seedPreview(g);
+  await refused(g,['activate',B,'acme','--no-send'],'already-active',`${B} is the pointer's copy`);
+  for(const x of [e,g])await noLeak(x);
+ });
+ await t.test('test 3: --plan prints one send: line in each case, with the live-copy note on a same-copy run',async(t)=>{
+  const e=await mk(t),base=await seedPreview(e,undefined,['--send']);
+  let out=await planOnly(e,0,'activate',B,'acme','--no-send');
+  assert.deepEqual(sendLines(out),['send: dropped; --no-send was given']);
+  assert.deepEqual(out.filter((l)=>l.startsWith('note: ')),[LIVE_NOTE]);
+  assert.equal(out[out.indexOf('send: dropped; --no-send was given')+1],`Console: scripts/webui-service.sh install --copy ${B} --copies ${COPIES} ${noSend(base).join(' ')}`);
+  out=await planOnly(e,0,'activate',C1,'acme');
+  assert.deepEqual(sendLines(out),['send: carried']);assert.deepEqual(out.filter((l)=>l.startsWith('note: ')),[]);
+  assert.ok(out.find((l)=>l.startsWith('Console: ')).endsWith(' --send'));
+  assert.deepEqual(sendLines(await planOnly(e,0,'activate',C1,'acme','--no-send')),['send: dropped; --no-send was given']);
+  let r=await prun(e,'activate',C1,'acme','--no-send');assert.equal(r.code,0,r.out+r.err);
+  assert.deepEqual(pointer(e).console,noSend(base));assert.match(stepText(e),/Z drop --send; --no-send was given\n/);
+  assert.deepEqual(sendLines(await planOnly(e,0,'activate',B,'acme','--no-send')),['send: off; --no-send was given and the pointer holds no --send']);
+  assert.deepEqual(sendLines(await planOnly(e,0,'activate',B,'acme')),['send: off']);
+  assert.deepEqual(sendLines(await planOnly(e,0,'rollback','acme')),['send: off']);
+  r=await prun(e,'activate',B,'acme','--no-send');assert.equal(r.code,0,r.out+r.err);
+  assert.match(stepText(e),/Z --no-send was given and the pointer holds no --send, so there is nothing to drop\n/);
+  assert.doesNotMatch(stepText(e),/drop --send/);
+  await noLeak(e);
+ });
+ await t.test('test 4: after --no-send, a rollback to the earlier copy leaves --send out of the pointer and the unit',async(t)=>{
+  const e=await mk(t),base=await seedPreview(e,undefined,['--send']);
+  let r=await prun(e,'activate',C1,'acme','--no-send');assert.equal(r.code,0,r.out+r.err);
+  r=await prun(e,'rollback','acme');assert.equal(r.code,0,r.out+r.err);
+  assert.equal(pointer(e).copy,B);assert.deepEqual(pointer(e).console,noSend(base));assert.doesNotMatch(conExec(e),/ --send( |$)/);
+  assert.doesNotMatch(stepText(e),/--send/);
+  r=await prun(e,'status','acme');assert.equal(r.code,0,r.err);assert.match(r.out,/unit flags: match the pointer/);
+  await noLeak(e);
+ });
+ await t.test('test 4: pm-on after --no-send keeps --send off',async(t)=>{
+  const e=await mk(t),base=await seedPreview(e,{pm:true},['--send']);
+  let r=await prun(e,'activate',C1,'acme','--pm-after-harness','--no-send');assert.equal(r.code,0,r.out+r.err);
+  biz(e,HARNESS);
+  r=await prun(e,'pm-on','acme');assert.equal(r.code,0,r.out+r.err);
+  assert.equal(pointer(e).pm,true);assert.deepEqual(pointer(e).console,noSend(base));assert.doesNotMatch(conExec(e),/ --send( |$)/);
+  r=await prun(e,'status','acme');assert.equal(r.code,0,r.err);assert.match(r.out,/unit flags: match the pointer/);
+  await noLeak(e);
+ });
+ await t.test('test 5: --no-send on rollback, pm-on, status, adopt or rehearse is a usage error',async(t)=>{
+  const e=await mk(t);await seedPreview(e,undefined,['--send']);
+  const usageText=(await prun(e,'--help')).err,n=calls(e).length,logs=logLines(e).length,before=fp(e);
+  for(const args of [['rollback','acme','--no-send'],['rollback','acme','--plan','--no-send'],['pm-on','acme','--no-send'],['status','acme','--no-send'],['adopt','acme','--no-send'],
+   ['rehearse','acme','--backup','/tmp/x','--port','7400','--no-send']]){
+   const r=await prun(e,...args);assert.equal(r.code,4,args.join(' '));assert.equal(r.out,'');assert.equal(r.err,usageText);
+  }
+  assert.match(usageText,/\| --no-proof\] \[--no-send\]/);
+  assert.deepEqual(fp(e),before);assert.deepEqual(startsStops(e,n),[]);assert.equal(logLines(e).length,logs);
+  await noLeak(e);
+ });
+ await t.test('test 6: with both a pair and --send in the pointer, --no-send and --no-proof each drop what they name and keep the rest',async(t)=>{
+  const e=await mk(t),base=await seedPreview(e,undefined,['--send']),pre=noSend(base),f=await proofFile(e),g=await proofFile(e,'proof2.189',0o400);
+  let r=await prun(e,'activate',B,'acme',...pair(f));assert.equal(r.code,0,r.out+r.err);
+  assert.deepEqual(pointer(e).console,[...pre,...pair(f),'--send']);
+  let out=await planOnly(e,0,'activate',C1,'acme','--no-proof');
+  assert.deepEqual([...proofLines(out),...sendLines(out)],['proof: dropped; --no-proof drops header x-console-proof','send: carried']);
+  out=await planOnly(e,0,'activate',C1,'acme','--no-send');
+  assert.deepEqual([...proofLines(out),...sendLines(out)],['proof: carried, header x-console-proof','send: dropped; --no-send was given']);
+  out=await planOnly(e,0,'activate',B,'acme','--no-send','--no-proof');
+  assert.deepEqual([...proofLines(out),...sendLines(out)],['proof: dropped; --no-proof drops header x-console-proof','send: dropped; --no-send was given']);
+  r=await prun(e,'activate',C1,'acme','--no-send');assert.equal(r.code,0,r.out+r.err);
+  assert.deepEqual(pointer(e).console,[...pre,...pair(f)]);
+  r=await prun(e,'activate',C1,'acme','--no-send',...pair(g,'X-Proof-Two'));assert.equal(r.code,0,r.out+r.err);
+  assert.deepEqual(pointer(e).console,[...pre,...pair(g,'X-Proof-Two')]);
+  r=await prun(e,'status','acme');assert.equal(r.code,0,r.err);assert.match(r.out,/unit flags: match the pointer/);
+  const h=await mk(t),hbase=await seedPreview(h,undefined,['--send']),hpre=noSend(hbase),k=await proofFile(h);
+  r=await prun(h,'activate',B,'acme',...pair(k));assert.equal(r.code,0,r.out+r.err);
+  r=await prun(h,'activate',C1,'acme','--no-proof');assert.equal(r.code,0,r.out+r.err);
+  assert.deepEqual(pointer(h).console,[...hpre,'--send']);
+  r=await prun(h,'activate',C1,'acme','--no-send','--no-proof');assert.equal(r.code,0,r.out+r.err);
+  assert.deepEqual(pointer(h).console,hpre);assert.doesNotMatch(conExec(h),/--proof-| --send( |$)/);
+  const steps=stepText(h);
+  assert.match(steps,/Z --no-proof was given and the pointer holds no proof pair, so there is nothing to drop\n/);assert.match(steps,/Z drop --send; --no-send was given\n/);
+  r=await prun(h,'status','acme');assert.equal(r.code,0,r.err);assert.match(r.out,/unit flags: match the pointer/);
+  for(const x of [e,h])await noLeak(x);
+ });
+});
+
 // --- rehearse (D2, row 163; the brief's "Stack rehearsal on a scratch root") ---
 // Copies of their own in RCOPIES: the real scripts/mosaic, config loader, business loader, roles and
 // mosaic-config.mjs, with stand-ins for the bus host (cli.mjs), the Console, the Store and

packages/library/README.md

@@ -0,0 +1,128 @@
+# packages/library
+
+Reads a writing repo by a mapping of folders to books, types, canon and playground. This is Case 2
+row C2-01 (`docs/plans/2026-10-20_case2-rows.md`), built from design sections 1.1 to 1.3 and 7.4 in
+`agents/gosalyn/work/case2/DESIGN.md` on `gosalyn/case2-design`.
+It is pure code with no state. Business file loading (C2-04), sync (C2-03a), the index (C2-05a) and the
+guard (C2-06) build on it.
+
+## Mapping
+
+`checkMapping(entry, where, { fail })` checks a `kind: "library"` project entry and returns a
+deep-frozen copy. `where` names the entry in messages. `fail(code, message)` defaults to throwing a
+`LibraryError`. C2-04 passes its own so a business file refusal carries the file name.
+
+```json
+{
+  "kind": "library",
+  "remote": "https://git.example.invalid/her/books.git",
+  "branch": "main",
+  "vaultPrefix": "books",
+  "types": { "Characters": "character", "Places": "place", "Research": "research" },
+  "manuscript": ["Chapters"],
+  "universes": {
+    "harbor": { "name": "Harbor", "books": ["Book One"], "playground": ["Book One/Playground/"] }
+  }
+}
+```
+
+- `remote` is https with no credentials, query or fragment. `branch` is a plain ref name.
+- `vaultPrefix` is optional, one folder name.
+- `types` maps a folder name to `character`, `place`, `research`, `tracker` or `summary`.
+  `manuscript` lists folder names and shares none with `types`.
+- A universe has `name`, `books` and `playground`. A hybrid adds `kind: "hybrid"`, two or more
+  non-hybrid `sources`, `constraints` (each one `{ "exclude": ... }` or
+  `{ "pin": { "entity", "field", "value" } }`) and `notes`.
+
+Refusals:
+
+| Code | When |
+|---|---|
+| `library-playground-outside-book` | a playground prefix is not strictly inside a book of its own universe |
+| `library-mapping-invalid` | any other shape fault: unknown key, bad remote or branch, a book folder in two universes, a book folder that holds another, a playground prefix that holds another, an unknown hybrid source |
+
+## Scope
+
+`classify(mapping, path)` decides scope from the path alone. Only paths ending in lowercase `.md` are
+mapped. A path under a playground prefix is `playground`. Any other path under a book folder is
+`canon`. Everything else is `unmapped`. The type is the first folder after the book, or after the
+playground prefix: a `types` name, `manuscript`, or `null`.
+
+## Reader
+
+`readLibrary({ repo, commit, mapping })` reads one commit, never a working tree. `repo` may be a
+clone or a bare mirror. `commit` must be a full 40-hex id that names a commit, else `library-commit`.
+Git runs through `git()` and `gitBytes()` from `packages/project/src/git.mjs`, so the same safe config,
+environment and ceiling directory apply. A failed git call refuses `library-git`.
+
+It returns `{ commit, files, problems }`, deep-frozen and sorted. Each file has its path, scope,
+universe, book, type, numbered lines, `bodyLine`, parsed `frontmatter` or `null`, `frontmatterRaw`
+and `links`. Front matter `appears_in` and `relationships` wikilinks count as links.
+
+Problems carry `{ code, path, line, message }`:
+
+| Rule | Meaning | File indexed |
+|---|---|---|
+| R1 | not a regular `100644` blob of at most 1 MiB, or not UTF-8, or holds a NUL | no |
+| R2 | path is unmapped | no |
+| R3 | front matter not fully parsed, `line` is where parsing stopped | yes, front matter kept raw |
+| R4 | link resolves to no file or to more than one | yes, link dropped |
+| R5 | canon file links into the playground | yes |
+| R6 | canon file links into another universe, a hybrid's sources excepted | yes |
+| R7 | two paths differ only in case | no, neither |
+
+The front matter parser takes scalars, quoted strings, flow lists, block lists and wikilinks. Nested
+maps, anchors, block scalars and duplicate keys stop it with R3.
+
+## Links
+
+`resolver(paths, { vaultPrefix })` tries four steps in order, each with the target as written and
+then with `.md` added:
+
+1. `root`: the path from the repo root.
+2. `vault-prefix`: the same path with `vaultPrefix/` stripped.
+3. `relative`: relative to the linking file, never above the repo root.
+4. `shortest`: a target with no `/` that matches the base name of exactly one indexed file.
+
+It resolves only against indexed files. A link to a `.canvas` file or an attachment is R4. A link into
+another repo resolves to nothing. `extractLinks` skips fenced and inline code.
+
+## renderItems
+
+`renderItems(body, { scopeOf, changed })` turns a reply body into the plain text both channels show.
+It is pure. Item kinds are `fact`, `finding`, `correction` (with `from` and `to`), `question` and
+`idea`. Each cite is a path with commit, line range and quote, or a url with a quote.
+
+```
+1. Correction: Chapter 1 says grey.
+   From: "green eyes"
+   To: "grey eyes"
+   [canon] Book One/Characters/Mara Vell.md:9 @bbbbbbb "green eyes" (changed since)
+```
+
+A body of `{ "items": [], "notice": ... }` gives `No cited answer`, `No answer` or `The turn failed`.
+Any other shape gives the fixed line `This reply could not be shown.` and none of the body's text.
+
+## Survey
+
+```sh
+mosaic library survey <repo> [--mapping <file>]
+```
+
+It reads the repo's HEAD commit and prints folder names, file counts by extension, front matter key
+sets and link-form counts. It never prints file text, front matter values, file names or link targets.
+A key that is not a short identifier prints as `(other key)`, since it could be her words. With
+`--mapping` it adds scope counts, resolver step counts and problem counts by rule.
+
+Exit codes follow `packages/project`: 0 done, 2 the repo can't be read (`library-git`,
+`library-commit`), 3 a bad mapping, 4 usage. `scripts/mosaic` sends `library survey` here. Other
+library verbs will be bus verbs.
+
+## Tests
+
+```sh
+node --test packages/library/tests/
+```
+
+Fixtures are made-up repos built per test in a temp dir. A marker string stands in for her text, and
+the survey tests check that it never appears in output.

packages/library/package.json

@@ -0,0 +1,11 @@
+{
+  "name": "@mosaic/library",
+  "version": "0.1.0",
+  "private": true,
+  "type": "module",
+  "license": "UNLICENSED",
+  "exports": "./src/index.mjs",
+  "scripts": {
+    "test": "node --test tests/*.test.mjs"
+  }
+}

packages/library/src/index.mjs

@@ -0,0 +1,8 @@
+// packages/library: her writing repo read by a mapping (Case 2, design 1 and 7.4). See README.md.
+export { LibraryError, RULES, problem, sortProblems } from './problems.mjs';
+export { checkMapping, TYPES } from './mapping.mjs';
+export { classify } from './scope.mjs';
+export { extractLinks, parseWikilink, resolver, formOf } from './links.mjs';
+export { readLibrary, listTree, readTexts, parseFile, parseFrontMatter, headCommit, MAX_BLOB, LINK_FIELDS } from './reader.mjs';
+export { renderItems, KINDS, NOTICES, UNREADABLE } from './render.mjs';
+export { survey, formatSurvey, surveyMain } from './survey.mjs';

packages/library/src/links.mjs

@@ -0,0 +1,79 @@
+// Wikilinks and the link resolver of design 1.3. Links are [[target]], [[target|label]] and
+// [[target#heading]], with ![[...]] embeds read the same way. Links inside fenced code blocks and
+// inline code spans are not links, as in Obsidian.
+import { posix } from 'node:path';
+
+const WIKILINK = /(!?)\[\[([^\[\]\n]+?)\]\]/g;
+const MARKDOWN_LINK = /(?<!!)\[[^\[\]\n]*\]\(([^()\s]+)\)/g;
+const FENCE = /^\s{0,3}(`{3,}|~{3,})/;
+
+// One wikilink's parts, or null for text that isn't one.
+export function parseWikilink(text) {
+  const match = /^(!?)\[\[([^\[\]\n]+?)\]\]$/.exec(text);
+  return match ? parts(match[2], match[1] === '!') : null;
+}
+function parts(inner, embed) {
+  const bar = inner.indexOf('|');
+  const target = bar < 0 ? inner : inner.slice(0, bar);
+  const hash = target.indexOf('#');
+  return {
+    file: (hash < 0 ? target : target.slice(0, hash)).trim(),
+    heading: hash < 0 ? null : target.slice(hash + 1).trim(),
+    label: bar < 0 ? null : inner.slice(bar + 1),
+    embed,
+  };
+}
+// The form a link is counted under in the survey.
+export const formOf = link => link.markdown ? 'markdown' : link.embed ? 'embed' : !link.file ? 'self'
+  : link.label !== null ? 'label' : link.heading !== null ? 'heading' : 'plain';
+
+// Links in body lines. `lines` is [[number, text], ...]. Markdown links are returned only with
+// `markdown: true`, for the survey's counts. The resolver follows wikilinks only.
+export function extractLinks(lines, { markdown = false } = {}) {
+  const found = [];
+  let fence = null;
+  for (const [line, text] of lines) {
+    const open = FENCE.exec(text);
+    if (fence) { if (open && open[1][0] === fence[0] && open[1].length >= fence.length) fence = null; continue; }
+    if (open) { fence = open[1]; continue; }
+    const plain = text.replace(/(`+)[^`]*?\1/g, match => ' '.repeat(match.length));
+    for (const m of plain.matchAll(WIKILINK)) found.push({ ...parts(m[2], m[1] === '!'), line });
+    if (markdown) {
+      for (const m of plain.matchAll(MARKDOWN_LINK)) {
+        if (!/^[a-z][a-z0-9+.-]*:/i.test(m[1]) && !m[1].startsWith('#'))
+          found.push({ file: m[1], heading: null, label: null, embed: false, markdown: true, line });
+      }
+    }
+  }
+  return found;
+}
+
+// A resolver over the indexed paths. resolve(from, file) tries, in order: a path from the repo
+// root, the same path with `vaultPrefix/` stripped, a path relative to the linking file, and
+// Obsidian's shortest-path form, a base name that matches exactly one indexed file. Each step tries
+// the target as written and then with `.md` added. A target in another of her repos is not in the
+// index, so it resolves to nothing.
+export function resolver(paths, { vaultPrefix } = {}) {
+  const known = new Set(paths), byBase = new Map();
+  for (const path of known) {
+    const base = posix.basename(path);
+    for (const key of new Set([base, base.replace(/\.md$/, '')])) byBase.set(key, [...(byBase.get(key) ?? []), path]);
+  }
+  const hit = candidate => [candidate, `${candidate}.md`].find(c => known.has(c));
+  return function resolve(from, file) {
+    if (typeof file !== 'string' || !file) return { path: null, step: 'missing' };
+    let path = hit(file);
+    if (path) return { path, step: 'root' };
+    if (vaultPrefix && file.startsWith(`${vaultPrefix}/`) && (path = hit(file.slice(vaultPrefix.length + 1))))
+      return { path, step: 'vault-prefix' };
+    const relative = posix.normalize(posix.join(posix.dirname(from), file));
+    if (relative !== '..' && !relative.startsWith('../') && !relative.startsWith('/') && (path = hit(relative)))
+      return { path, step: 'relative' };
+    if (!file.includes('/')) {
+      const matches = byBase.get(file) ?? [];
+      if (matches.length === 1) return { path: matches[0], step: 'shortest' };
+      if (matches.length > 1) return { path: null, step: 'ambiguous', count: matches.length };
+    }
+    return { path: null, step: 'missing' };
+  };
+}

packages/library/src/mapping.mjs

@@ -0,0 +1,132 @@
+// The library project entry of a business file (design 1.1): her folders mapped onto universes,
+// books, type folders, manuscript folders and playground prefixes. A pure validator. Business file
+// loading wires it in C2-04, which passes its own `fail` so the refusal reads as a business file
+// problem. Agents can't write this entry (M9, C2-04).
+import { raise } from './problems.mjs';
+
+export const TYPES = Object.freeze(['character', 'place', 'research', 'tracker', 'summary']);
+const ID = /^[A-Za-z0-9][A-Za-z0-9._-]{0,63}$/;
+const BRANCH = /^[A-Za-z0-9][A-Za-z0-9._/-]{0,127}$/;
+const CONSTRAINT_KEYS = ['exclude', 'pin'];
+
+// A folder segment from her vault: spaces and capitals are fine, separators, control characters
+// and dot names are not.
+function segment(value) {
+  return typeof value === 'string' && value.length > 0 && value.length <= 255 && value !== '.' && value !== '..'
+    && !/[\/\\\u0000-\u001f\u007f]/.test(value) && value.trim() === value;
+}
+function folder(value) {
+  return typeof value === 'string' && value.length <= 1024 && value.split('/').every(segment);
+}
+const holds = (outer, inner) => inner.startsWith(outer.endsWith('/') ? outer : `${outer}/`);
+
+export function checkMapping(entry, where = 'library', { fail = raise } = {}) {
+  const bad = message => fail('library-mapping-invalid', `${where} ${message}`);
+  const object = (value, name) => {
+    if (value === null || typeof value !== 'object' || Array.isArray(value)) bad(`${name} must be an object`);
+  };
+  const only = (value, keys, name) => {
+    for (const key of Object.keys(value)) if (!keys.includes(key)) bad(`${name} has unknown key ${JSON.stringify(key)}`);
+  };
+  const list = (value, name, check, what) => {
+    if (!Array.isArray(value)) bad(`${name} must be a list`);
+    for (const item of value) if (!check(item)) bad(`${name} holds ${JSON.stringify(item)}, which is not ${what}`);
+    if (new Set(value).size !== value.length) bad(`${name} names an entry twice`);
+    return [...value];
+  };
+
+  object(entry, '');
+  only(entry, ['kind', 'remote', 'branch', 'vaultPrefix', 'universes', 'types', 'manuscript'], 'entry');
+  if (entry.kind !== 'library') bad('kind must be "library"');
+  let url;
+  try { url = new URL(entry.remote); } catch { bad('remote must be an https:// URL'); }
+  if (url.protocol !== 'https:' || url.username || url.password || url.search || url.hash || entry.remote.includes('\0'))
+    bad('remote must be an https:// URL with no credentials, query or fragment');
+  if (typeof entry.branch !== 'string' || !BRANCH.test(entry.branch) || entry.branch.includes('..')
+      || entry.branch.includes('//') || entry.branch.endsWith('/') || entry.branch.endsWith('.lock'))
+    bad('branch must be a plain branch name');
+  if (Object.hasOwn(entry, 'vaultPrefix') && !segment(entry.vaultPrefix)) bad('vaultPrefix must be one folder name');
+
+  object(entry.types, 'types');
+  for (const [name, type] of Object.entries(entry.types)) {
+    if (!segment(name)) bad(`types has ${JSON.stringify(name)}, which is not one folder name`);
+    if (!TYPES.includes(type)) bad(`types.${name} must be one of ${TYPES.join(', ')}`);
+  }
+  const manuscript = list(entry.manuscript, 'manuscript', segment, 'one folder name');
+  for (const name of manuscript) if (Object.hasOwn(entry.types, name)) bad(`manuscript folder ${JSON.stringify(name)} is also a type folder`);
+
+  object(entry.universes, 'universes');
+  if (!Object.keys(entry.universes).length) bad('universes must name at least one universe');
+  const universes = {}, bookOwner = new Map(), prefixes = [];
+  for (const [id, universe] of Object.entries(entry.universes)) {
+    const name = `universes.${id}`;
+    if (!ID.test(id)) bad(`universe id ${JSON.stringify(id)} is not a plain id`);
+    object(universe, name);
+    const hybrid = universe.kind === 'hybrid';
+    only(universe, hybrid ? ['kind', 'name', 'sources', 'books', 'playground', 'constraints', 'notes'] : ['name', 'books', 'playground'], name);
+    if (typeof universe.name !== 'string' || !universe.name.trim() || universe.name.length > 128 || /[\u0000-\u001f]/.test(universe.name))
+      bad(`${name}.name must be a short display name`);
+    const books = list(universe.books, `${name}.books`, folder, 'a folder path');
+    if (!hybrid && !books.length) bad(`${name}.books must name at least one book folder`);
+    for (const book of books) {
+      if (bookOwner.has(book)) bad(`book folder ${JSON.stringify(book)} is in two universes`);
+      bookOwner.set(book, id);
+    }
+    const playground = list(universe.playground ?? [], `${name}.playground`,
+      value => typeof value === 'string' && value.endsWith('/') && folder(value.slice(0, -1)), 'a folder path ending in /');
+    for (const prefix of playground) {
+      // Every playground file must have a universe and a book (1.1, B1).
+      if (!books.some(book => holds(book, prefix) && prefix !== `${book}/`))
+        fail('library-playground-outside-book', `${where} ${name}.playground ${JSON.stringify(prefix)} is not inside one of its books`);
+      prefixes.push(prefix);
+    }
+    const out = { name: universe.name, books, playground };
+    if (hybrid) {
+      out.kind = 'hybrid';
+      out.sources = list(universe.sources, `${name}.sources`, value => typeof value === 'string' && ID.test(value), 'a universe id');
+      if (out.sources.length < 2) bad(`${name}.sources must name two or more universes`);
+      if (!Array.isArray(universe.constraints ?? [])) bad(`${name}.constraints must be a list`);
+      out.constraints = (universe.constraints ?? []).map((constraint, i) => {
+        const at = `${name}.constraints[${i}]`;
+        object(constraint, at);
+        only(constraint, CONSTRAINT_KEYS, at);
+        if (Object.keys(constraint).length !== 1) bad(`${at} must hold exactly one of ${CONSTRAINT_KEYS.join(', ')}`);
+        if (Object.hasOwn(constraint, 'exclude')) {
+          if (!folder(constraint.exclude)) bad(`${at}.exclude must be a source path`);
+          return { exclude: constraint.exclude };
+        }
+        object(constraint.pin, `${at}.pin`);
+        only(constraint.pin, ['entity', 'field', 'value'], `${at}.pin`);
+        if (!folder(constraint.pin.entity) || typeof constraint.pin.field !== 'string' || !constraint.pin.field
+            || !['string', 'number', 'boolean'].includes(typeof constraint.pin.value))
+          bad(`${at}.pin needs an entity path, a field name and a scalar value`);
+        return { pin: { ...constraint.pin } };
+      });
+      if (Object.hasOwn(universe, 'notes') && (typeof universe.notes !== 'string' || universe.notes.length > 4000))
+        bad(`${name}.notes must be text of at most 4000 characters`);
+      if (Object.hasOwn(universe, 'notes')) out.notes = universe.notes;
+    }
+    universes[id] = out;
+  }
+  for (const [id, universe] of Object.entries(universes)) {
+    for (const source of universe.sources ?? []) {
+      if (!Object.hasOwn(universes, source) || universes[source].kind === 'hybrid')
+        bad(`universes.${id}.sources names ${JSON.stringify(source)}, which is not a non-hybrid universe`);
+    }
+  }
+  const books = [...bookOwner.keys()];
+  for (const a of books) for (const b of books) if (a !== b && holds(a, b)) bad(`book folder ${JSON.stringify(a)} holds book folder ${JSON.stringify(b)}`);
+  for (const a of prefixes) for (const b of prefixes) if (a !== b && holds(a, b)) bad(`playground ${JSON.stringify(a)} holds playground ${JSON.stringify(b)}`);
+  if (new Set(prefixes).size !== prefixes.length) bad('a playground prefix is listed twice');
+
+  return deepFreeze({
+    kind: 'library', remote: entry.remote, branch: entry.branch,
+    ...(Object.hasOwn(entry, 'vaultPrefix') ? { vaultPrefix: entry.vaultPrefix } : {}),
+    universes, types: { ...entry.types }, manuscript,
+  });
+}
+
+function deepFreeze(value) {
+  if (value && typeof value === 'object') { for (const item of Object.values(value)) deepFreeze(item); Object.freeze(value); }
+  return value;
+}

packages/library/src/problems.mjs

@@ -0,0 +1,27 @@
+// Errors and the R-rule problems of design 1.3. A problem never holds back a commit: it names a
+// path and, where there is one, a line, and the index leaves the file or link out.
+export class LibraryError extends Error {
+  constructor(code, message) { super(`${code}: ${message}`); this.code = code; }
+}
+export const raise = (code, message) => { throw new LibraryError(code, message); };
+
+export const RULES = Object.freeze({
+  R1: 'not a regular blob up to 1 MiB of UTF-8 text',
+  R2: 'path is unmapped',
+  R3: 'front matter not fully parsed',
+  R4: 'link resolves to no file or to more than one',
+  R5: 'canon file refers into the playground',
+  R6: 'canon file refers into another universe',
+  R7: 'paths differ only in case',
+});
+
+export function problem(code, path, line, message = RULES[code]) {
+  if (!Object.hasOwn(RULES, code)) raise('library-problem-code', `unknown problem code ${code}`);
+  return Object.freeze({ code, path, ...(Number.isSafeInteger(line) ? { line } : {}), message });
+}
+
+// Stable order for status output and tests: path, then line, then code.
+export function sortProblems(list) {
+  return [...list].sort((a, b) => a.path < b.path ? -1 : a.path > b.path ? 1
+    : (a.line ?? 0) - (b.line ?? 0) || (a.code < b.code ? -1 : a.code > b.code ? 1 : 0));
+}

packages/library/src/reader.mjs

@@ -0,0 +1,219 @@
+// The commit reader of design 1.3. It reads a commit of her repo, never a working tree: it lists the
+// tree with `git ls-tree -r -z` and reads blobs with `cat-file`, through the same bounded git()
+// and gitBytes() as packages/project, so hooks, protocols and the environment are fixed the same
+// way. Nothing in the repo is checked out or run (D7). Each R-rule is a problem, never a refusal
+// of the commit; the affected file or link is left out of the index.
+import { git, gitBytes } from '../../project/src/git.mjs';
+import { classify } from './scope.mjs';
+import { extractLinks, parseWikilink, resolver } from './links.mjs';
+import { LibraryError, problem, raise, sortProblems } from './problems.mjs';
+
+export const MAX_BLOB = 1024 * 1024;
+const MAX_LISTING = 32 * 1024 * 1024;
+const SHA = /^[0-9a-f]{40}$/;
+const ENTRY = /^([0-7]{6}) (blob|tree|commit) ([0-9a-f]{40}) +(-|\d+)\t(.+)$/s;
+export const LINK_FIELDS = Object.freeze(['appears_in', 'relationships']);
+const READERS = 8;
+
+async function local(promise, message) {
+  try { return await promise; } catch (e) { raise('library-git', `${message} (${e.code ?? 'error'})`); }
+}
+
+export async function headCommit(repo) {
+  return local(git(repo, ['rev-parse', '--verify', '--end-of-options', 'HEAD^{commit}']), 'repository has no readable HEAD commit');
+}
+
+// Every entry of the commit's tree: { mode, type, oid, size, path }. Sizes come from `-l`, so no
+// blob is opened to list it.
+export async function listTree(repo, commit) {
+  if (typeof commit !== 'string' || !SHA.test(commit)) raise('library-commit', 'expected a full commit id');
+  const kind = await local(git(repo, ['cat-file', '-t', commit]), 'commit is not in the repository');
+  if (kind !== 'commit') raise('library-commit', 'not a commit');
+  const bytes = await local(gitBytes(repo, ['ls-tree', '-r', '-z', '-l', '--full-tree', commit], MAX_LISTING), 'tree listing refused');
+  let text;
+  try { text = new TextDecoder('utf-8', { fatal: true }).decode(bytes); }
+  catch { raise('library-git', 'tree listing is not UTF-8'); }
+  const entries = text.split('\0');
+  if (entries.pop() !== '') raise('library-git', 'invalid tree listing');
+  return entries.map(entry => {
+    const m = ENTRY.exec(entry);
+    if (!m) raise('library-git', 'invalid tree listing');
+    return { mode: m[1], type: m[2], oid: m[3], size: m[4] === '-' ? null : Number(m[4]), path: m[5] };
+  });
+}
+
+// R1: only a 100644 blob up to 1 MiB of UTF-8 text without NUL is read.
+export const readable = entry => entry.mode === '100644' && entry.type === 'blob'
+  && Number.isSafeInteger(entry.size) && entry.size <= MAX_BLOB;
+
+// Text of each readable entry, by path. An entry whose bytes aren't UTF-8 text is missing from the
+// map, and the caller reports it under R1.
+export async function readTexts(repo, entries) {
+  const texts = new Map(), queue = [...entries];
+  const decoder = new TextDecoder('utf-8', { fatal: true, ignoreBOM: false });
+  const worker = async () => {
+    for (let entry = queue.shift(); entry; entry = queue.shift()) {
+      const bytes = await local(gitBytes(repo, ['cat-file', 'blob', entry.oid], MAX_BLOB), 'blob read refused');
+      let value;
+      try { value = decoder.decode(bytes); } catch { continue; }
+      if (!value.includes('\0')) texts.set(entry.path, value);
+    }
+  };
+  await Promise.all(Array.from({ length: READERS }, worker));
+  return texts;
+}
+
+const QUOTED = /^"(?:[^"\\]|\\.)*"$|^'(?:[^']|'')*'$/;
+const PLAIN_START = /^[^\s\[\]{}&*!|>%@`"'#,]/;
+function scalar(raw) {
+  const value = raw.trim();
+  if (parseWikilink(value)) return { ok: true, value };
+  if (QUOTED.test(value)) {
+    if (value[0] === "'") return { ok: true, value: value.slice(1, -1).replace(/''/g, "'") };
+    try { return { ok: true, value: JSON.parse(value) }; } catch { return { ok: false }; }
+  }
+  if (value === '' || value === '~' || value === 'null') return { ok: true, value: null };
+  if (!PLAIN_START.test(value) || /: |\s#/.test(value) || value.endsWith(':')) return { ok: false };
+  if (value === 'true' || value === 'false') return { ok: true, value: value === 'true' };
+  if (/^-?(0|[1-9]\d*)(\.\d+)?$/.test(value)) return { ok: true, value: Number(value) };
+  return { ok: true, value };
+}
+function flow(raw) {
+  const inner = raw.trim().slice(1, -1), items = [];
+  let current = '', quote = null;
+  for (const ch of inner) {
+    if (quote) { current += ch; if (ch === quote) quote = null; continue; }
+    if (ch === '"' || ch === "'") { quote = ch; current += ch; continue; }
+    if (ch === '[' || ch === ']' || ch === '{' || ch === '}') return { ok: false };
+    if (ch === ',') { items.push(current); current = ''; continue; }
+    current += ch;
+  }
+  if (quote) return { ok: false };
+  if (current.trim() || items.length) items.push(current);
+  const values = [];
+  for (const item of items) { const s = scalar(item); if (!s.ok || !item.trim()) return { ok: false }; values.push(s.value); }
+  return { ok: true, value: values };
+}
+function value(raw) {
+  const text = raw.trim();
+  if (text.startsWith('[') && !parseWikilink(text)) return text.endsWith(']') ? flow(text) : { ok: false };
+  return scalar(text);
+}
+
+// Front matter of design 1.3 (R3): scalars, quoted strings, flow lists and block lists of scalars or
+// wikilinks. Anything else, a nested map, a block scalar or an anchor for example, leaves the whole
+// front matter as raw text with one R3 problem at the line where parsing stopped.
+// Returns { frontmatter, raw, bodyLine, stop } with 1-based line numbers.
+export function parseFrontMatter(lines) {
+  if (lines[0]?.replace(/^/, '').trimEnd() !== '---') return { frontmatter: null, raw: null, bodyLine: 1, stop: null };
+  const close = lines.findIndex((text, i) => i > 0 && /^(---|\.\.\.)\s*$/.test(text));
+  if (close < 0) return { frontmatter: null, raw: null, bodyLine: 1, stop: 1 };
+  const raw = lines.slice(1, close).join('\n'), data = {};
+  let list = null;
+  for (let i = 1; i < close; i++) {
+    const text = lines[i], line = i + 1;
+    if (!text.trim() || /^\s*#/.test(text)) continue;
+    const item = /^(\s*)- (.*)$|^(\s*)-$/.exec(text);
+    if (item && list) {
+      const parsed = scalar(item[2] ?? '');
+      if (!parsed.ok) return { frontmatter: null, raw, bodyLine: close + 2, stop: line };
+      data[list].push(parsed.value);
+      continue;
+    }
+    const pair = /^([^\s:#\-][^:]*?|"[^"]+"|'[^']+')\s*:(?:\s+(.*))?$/.exec(text);
+    if (!pair) return { frontmatter: null, raw, bodyLine: close + 2, stop: line };
+    const key = pair[1].replace(/^(["'])(.*)\1$/, '$2');
+    if (Object.hasOwn(data, key) || key === '__proto__') return { frontmatter: null, raw, bodyLine: close + 2, stop: line };
+    if (pair[2] === undefined || !pair[2].trim()) {
+      const next = lines[i + 1];
+      if (i + 1 < close && /^\s*-( |$)/.test(next)) { data[key] = []; list = key; }
+      else { data[key] = null; list = null; }
+      continue;
+    }
+    list = null;
+    const parsed = value(pair[2]);
+    if (!parsed.ok) return { frontmatter: null, raw, bodyLine: close + 2, stop: line };
+    data[key] = parsed.value;
+  }
+  return { frontmatter: data, raw: null, bodyLine: close + 2, stop: null };
+}
+
+export const splitLines = text => text.replace(/^/, '').split('\n').map(l => l.endsWith('\r') ? l.slice(0, -1) : l);
+
+// One parsed file: its lines (all of them, numbered from 1), front matter and the links it holds.
+// Front matter links come from LINK_FIELDS values that are wikilinks; other values are names.
+export function parseFile(text, { markdown = false } = {}) {
+  const lines = splitLines(text);
+  const fm = parseFrontMatter(lines);
+  const numbered = lines.map((t, i) => [i + 1, t]);
+  const links = extractLinks(numbered.slice(fm.bodyLine - 1), { markdown });
+  if (fm.frontmatter) {
+    for (const field of LINK_FIELDS) {
+      const raw = fm.frontmatter[field];
+      const values = Array.isArray(raw) ? raw : raw === undefined || raw === null ? [] : [raw];
+      for (const v of values) {
+        const link = typeof v === 'string' ? parseWikilink(v.trim()) : null;
+        if (link) links.push({ ...link, field, line: frontMatterLine(lines, fm.bodyLine, field) });
+      }
+    }
+  }
+  return { lines: numbered, bodyLine: fm.bodyLine, frontmatter: fm.frontmatter, frontmatterRaw: fm.raw, stop: fm.stop, links };
+}
+function frontMatterLine(lines, bodyLine, field) {
+  const i = lines.slice(0, bodyLine - 1).findIndex(t => new RegExp(`^["']?${field}["']?\\s*:`).test(t));
+  return i < 0 ? undefined : i + 1;
+}
+
+// Read a commit under a checked mapping (mapping.mjs). Returns the indexed files and every
+// R1-R7 problem: { commit, files: [...], problems: [...] }, frozen, sorted by path.
+export async function readLibrary({ repo, commit, mapping }) {
+  if (!mapping || mapping.kind !== 'library') throw new LibraryError('library-mapping-invalid', 'expected a checked library mapping');
+  const entries = await listTree(repo, commit);
+  const problems = [], twins = new Set(), byLower = new Map();
+  for (const e of entries) byLower.set(e.path.toLowerCase(), [...(byLower.get(e.path.toLowerCase()) ?? []), e.path]);
+  for (const group of byLower.values()) if (group.length > 1) for (const path of group) twins.add(path);
+
+  const candidates = [];
+  for (const entry of entries) {
+    const where = classify(mapping, entry.path);
+    if (where.scope === 'unmapped') { problems.push(problem('R2', entry.path)); continue; }
+    if (twins.has(entry.path)) { problems.push(problem('R7', entry.path)); continue; }
+    if (!readable(entry)) { problems.push(problem('R1', entry.path)); continue; }
+    candidates.push({ entry, where });
+  }
+  const texts = await readTexts(repo, candidates.map(c => c.entry));
+  const files = [];
+  for (const { entry, where } of candidates) {
+    if (!texts.has(entry.path)) { problems.push(problem('R1', entry.path)); continue; }
+    const parsed = parseFile(texts.get(entry.path));
+    if (parsed.stop !== null) problems.push(problem('R3', entry.path, parsed.stop));
+    files.push({ path: entry.path, ...where, name: entry.path.split('/').pop().replace(/\.md$/, ''), ...parsed });
+  }
+
+  const resolve = resolver(files.map(f => f.path), { vaultPrefix: mapping.vaultPrefix });
+  const byPath = new Map(files.map(f => [f.path, f]));
+  for (const file of files) {
+    const kept = [];
+    for (const link of file.links) {
+      if (!link.file) continue;
+      const target = resolve(file.path, link.file);
+      if (!target.path) { problems.push(problem('R4', file.path, link.line)); continue; }
+      const to = byPath.get(target.path);
+      if (file.scope === 'canon') {
+        if (to.scope === 'playground') problems.push(problem('R5', file.path, link.line));
+        const sources = mapping.universes[file.universe].sources ?? [];
+        if (to.universe !== file.universe && !sources.includes(to.universe)) problems.push(problem('R6', file.path, link.line));
+      }
+      kept.push({ ...link, path: target.path, step: target.step });
+    }
+    file.links = kept;
+    delete file.stop;
+  }
+  files.sort((a, b) => a.path < b.path ? -1 : 1);
+  return deepFreeze({ commit, files, problems: sortProblems(problems) });
+}
+
+function deepFreeze(value) {
+  if (value && typeof value === 'object' && !Object.isFrozen(value)) { Object.freeze(value); for (const v of Object.values(value)) deepFreeze(v); }
+  return value;
+}

packages/library/src/render.mjs

@@ -0,0 +1,59 @@
+// renderItems(body): how a stored cited reply looks (design 7.4), shared by the Console chat (C2-10b)
+// and the Discord relay (C2-18). Pure: no git, no clock. The caller passes what it knows about cites.
+// The guard (C2-06) checks limits before a reply is stored. This only refuses to show a body that
+// doesn't have the reply shape, and then it shows a fixed line, never the body's text.
+export const KINDS = Object.freeze({ fact: 'Fact', finding: 'Finding', correction: 'Correction', question: 'Question', idea: 'Idea' });
+export const NOTICES = Object.freeze({ 'no-cited-answer': 'No cited answer', 'no-answer': 'No answer', 'turn-failed': 'The turn failed' });
+export const UNREADABLE = 'This reply could not be shown.';
+const SHA = /^[0-9a-f]{40}$/;
+
+const plain = value => value !== null && typeof value === 'object' && !Array.isArray(value);
+const line = n => Number.isSafeInteger(n) && n > 0;
+function cite(value, { scopeOf, changed }) {
+  if (!plain(value) || typeof value.quote !== 'string') return null;
+  if (Object.hasOwn(value, 'url')) {
+    if (typeof value.url !== 'string' || Object.hasOwn(value, 'path')) return null;
+    return { badge: 'web', url: value.url, ref: value.url, quote: value.quote, changed: false };
+  }
+  const { path, commit, lines } = value;
+  if (typeof path !== 'string' || !SHA.test(commit ?? '') || !Array.isArray(lines) || lines.length !== 2
+      || !line(lines[0]) || !line(lines[1]) || lines[1] < lines[0]) return null;
+  const badge = scopeOf?.(path);
+  const ref = `${path}:${lines[0] === lines[1] ? lines[0] : `${lines[0]}-${lines[1]}`} @${commit.slice(0, 7)}`;
+  return { badge: badge === 'canon' || badge === 'playground' ? badge : null, path, commit, lines: [...lines], ref,
+    quote: value.quote, changed: changed?.({ path, commit }) === true };
+}
+const quoted = text => JSON.stringify(text);
+
+// body: the stored message body (a JSON string or the parsed object).
+// options.scopeOf(path) -> 'canon' | 'playground' | undefined, for the scope badge.
+// options.changed({path, commit}) -> true when the file's last commit is newer than the cited one.
+// Returns { kind: 'items', items, text } | { kind: 'notice', notice, text } | { kind: 'unreadable', text }.
+export function renderItems(body, options = {}) {
+  const unreadable = { kind: 'unreadable', text: UNREADABLE };
+  let value = body;
+  if (typeof body === 'string') { try { value = JSON.parse(body); } catch { return unreadable; } }
+  if (!plain(value) || !Array.isArray(value.items)) return unreadable;
+  const keys = Object.keys(value);
+  if (value.items.length === 0) {
+    if (keys.length !== 2 || !Object.hasOwn(NOTICES, value.notice)) return unreadable;
+    return { kind: 'notice', notice: value.notice, text: NOTICES[value.notice] };
+  }
+  if (keys.length !== 1) return unreadable;
+  const items = [];
+  for (const item of value.items) {
+    if (!plain(item) || !Object.hasOwn(KINDS, item.kind) || typeof item.text !== 'string' || !Array.isArray(item.cites)) return unreadable;
+    const correction = item.kind === 'correction';
+    if (correction && (typeof item.from !== 'string' || typeof item.to !== 'string')) return unreadable;
+    const cites = item.cites.map(c => cite(c, options));
+    if (cites.some(c => c === null)) return unreadable;
+    items.push({ kind: item.kind, label: KINDS[item.kind], text: item.text,
+      ...(correction ? { from: item.from, to: item.to } : {}), cites });
+  }
+  const text = items.map((item, i) => [
+    `${i + 1}. ${item.label}: ${item.text}`,
+    ...(item.kind === 'correction' ? [`   From: ${quoted(item.from)}`, `   To: ${quoted(item.to)}`] : []),
+    ...item.cites.map(c => `   ${c.badge ? `[${c.badge}] ` : ''}${c.ref} ${quoted(c.quote)}${c.changed ? ' (changed since)' : ''}`),
+  ].join('\n')).join('\n');
+  return { kind: 'items', items, text };
+}

packages/library/src/scope.mjs

@@ -0,0 +1,21 @@
+// The scope rule of design 1.2. Scope comes from the path alone (D2): no file content can change it.
+// Paths are repo-relative and compared exactly, case included (R7 handles case-only twins).
+const inside = (folder, path) => path.startsWith(folder.endsWith('/') ? folder : `${folder}/`);
+
+// { scope: 'playground' | 'canon', universe, book, type, folder } or { scope: 'unmapped' }.
+// `type` is the mapped type of the first folder under the book (canon) or under the playground
+// prefix (playground), 'manuscript' for a manuscript folder, else null. `folder` is that folder name.
+export function classify(mapping, path) {
+  if (typeof path !== 'string' || !path.endsWith('.md')) return { scope: 'unmapped' };
+  for (const [universe, entry] of Object.entries(mapping.universes)) {
+    const book = entry.books.find(b => inside(b, path));
+    if (!book) continue;
+    const prefix = entry.playground.find(p => inside(p, path));
+    const rest = path.slice((prefix ?? `${book}/`).length).split('/');
+    const folder = rest.length > 1 ? rest[0] : null;
+    const type = folder === null ? null : Object.hasOwn(mapping.types, folder) ? mapping.types[folder]
+      : mapping.manuscript.includes(folder) ? 'manuscript' : null;
+    return { scope: prefix ? 'playground' : 'canon', universe, book, type, folder };
+  }
+  return { scope: 'unmapped' };
+}

packages/library/src/survey.mjs

@@ -0,0 +1,126 @@
+// `mosaic library survey <repo> [--mapping <file>]` (design 1.1, 10 step 7). It prints what a mapping
+// needs: folder names, file counts by extension, front matter key sets and link-form counts. It
+// never prints file text, front matter values, file names or link targets. With a mapping it adds
+// scope counts, resolver step counts and R-problem counts by code. It reads the repo's HEAD commit
+// through the commit reader, never the working tree.
+import { readFileSync, realpathSync, statSync } from 'node:fs';
+import { resolve as resolvePath } from 'node:path';
+import { pathToFileURL } from 'node:url';
+import { checkMapping } from './mapping.mjs';
+import { classify } from './scope.mjs';
+import { formOf } from './links.mjs';
+import { headCommit, listTree, parseFile, readable, readLibrary, readTexts } from './reader.mjs';
+import { LibraryError, RULES } from './problems.mjs';
+
+export const USAGE = 'usage: mosaic library survey <repo> [--mapping <file>]';
+// Keys are printed only in the short identifier forms property names take. A key with spaces or of
+// any other shape could be a phrase of hers, so it is counted as one "(other key)".
+const KEY = /^[A-Za-z_][A-Za-z0-9_-]{0,31}$/;
+const OTHER_KEY = '(other key)';
+const FORMS = ['plain', 'label', 'heading', 'embed', 'self', 'markdown'];
+const STEPS = ['root', 'vault-prefix', 'relative', 'shortest'];
+const extension = path => /\.md$/.test(path) ? 'md' : /\.canvas$/.test(path) ? 'canvas' : /\.base$/.test(path) ? 'base' : 'other';
+
+// The survey as data. `mapping` is a checked mapping or undefined.
+export async function survey({ repo, commit, mapping }) {
+  const head = commit ?? await headCommit(repo);
+  const entries = await listTree(repo, head);
+  const folders = new Map();
+  for (const entry of entries) {
+    const slash = entry.path.lastIndexOf('/');
+    const name = slash < 0 ? '' : entry.path.slice(0, slash);
+    const counts = folders.get(name) ?? { md: 0, canvas: 0, base: 0, other: 0 };
+    counts[entry.type === 'blob' ? extension(entry.path) : 'other']++;
+    folders.set(name, counts);
+  }
+  const markdown = entries.filter(e => e.path.endsWith('.md'));
+  const texts = await readTexts(repo, markdown.filter(readable));
+  const keySets = new Map(), forms = Object.fromEntries(FORMS.map(f => [f, 0]));
+  const fields = { appears_in: { wikilink: 0, name: 0 }, relationships: { wikilink: 0, name: 0 } };
+  let noFrontMatter = 0, unparsed = 0;
+  for (const text of texts.values()) {
+    const file = parseFile(text, { markdown: true });
+    if (file.stop !== null) unparsed++;
+    else if (!file.frontmatter) noFrontMatter++;
+    else {
+      const set = [...new Set(Object.keys(file.frontmatter).map(k => KEY.test(k) ? k : OTHER_KEY))].sort().join(', ');
+      keySets.set(set, (keySets.get(set) ?? 0) + 1);
+      for (const field of Object.keys(fields)) {
+        const raw = file.frontmatter[field];
+        for (const v of Array.isArray(raw) ? raw : raw === undefined || raw === null ? [] : [raw])
+          fields[field][typeof v === 'string' && /^\s*!?\[\[[^\]]+\]\]\s*$/.test(v) ? 'wikilink' : 'name']++;
+      }
+    }
+    for (const link of file.links) if (!link.field) forms[formOf(link)]++;
+  }
+  const result = {
+    commit: head, entries: entries.length,
+    folders: [...folders].sort(([a], [b]) => a < b ? -1 : 1).map(([name, counts]) => ({ name, ...counts })),
+    markdown: { files: markdown.length, read: texts.size, noFrontMatter, unparsed },
+    keySets: [...keySets].sort(([a, x], [b, y]) => y - x || (a < b ? -1 : 1)).map(([keys, count]) => ({ keys, count })),
+    forms, fields,
+  };
+  if (mapping) {
+    const scopes = { canon: 0, playground: 0, unmapped: 0 };
+    for (const entry of entries) scopes[classify(mapping, entry.path).scope]++;
+    const library = await readLibrary({ repo, commit: head, mapping });
+    const steps = Object.fromEntries(STEPS.map(s => [s, 0]));
+    for (const file of library.files) for (const link of file.links) steps[link.step]++;
+    const problems = Object.fromEntries(Object.keys(RULES).map(code => [code, 0]));
+    for (const p of library.problems) problems[p.code]++;
+    steps.unresolved = problems.R4;
+    Object.assign(result, { scopes, indexed: library.files.length, steps, problems });
+  }
+  return result;
+}
+
+// Folder names are quoted as JSON strings, so no name can carry a control sequence to the terminal.
+export function formatSurvey(s) {
+  const out = [`commit ${s.commit}`, `entries ${s.entries}`, 'folders (direct children: md canvas base other)'];
+  for (const f of s.folders) out.push(`  ${f.name === '' ? '(root)' : JSON.stringify(f.name)} ${f.md} ${f.canvas} ${f.base} ${f.other}`);
+  out.push(`markdown ${s.markdown.files} files, ${s.markdown.read} read, ${s.markdown.noFrontMatter} without front matter, ${s.markdown.unparsed} with front matter not fully parsed`);
+  out.push('front matter key sets');
+  for (const k of s.keySets) out.push(`  ${k.count} [${k.keys}]`);
+  out.push(`body links ${FORMS.map(f => `${f} ${s.forms[f]}`).join(', ')}`);
+  for (const [field, c] of Object.entries(s.fields)) out.push(`field ${field} wikilink ${c.wikilink}, name ${c.name}`);
+  if (s.scopes) {
+    out.push(`scopes canon ${s.scopes.canon}, playground ${s.scopes.playground}, unmapped ${s.scopes.unmapped}; indexed ${s.indexed}`);
+    out.push(`resolved ${STEPS.map(st => `${st} ${s.steps[st]}`).join(', ')}, unresolved ${s.steps.unresolved}`);
+    out.push(`problems ${Object.entries(s.problems).map(([code, n]) => `${code} ${n}`).join(', ')}`);
+  }
+  return `${out.join('\n')}\n`;
+}
+
+// Exit codes as packages/project's CLI: 0 done, 2 the repo can't be read, 3 a bad mapping, 4 usage.
+export async function surveyMain(argv, io = { stdout: process.stdout, stderr: process.stderr }) {
+  const fail = (code, message) => { io.stderr.write(`library survey: ${message}\n`); return code; };
+  const [verb, ...rest] = argv;
+  if (verb !== 'survey') return fail(4, USAGE);
+  let repo, mappingFile;
+  for (let i = 0; i < rest.length; i++) {
+    if (rest[i] === '--mapping' && i + 1 < rest.length && mappingFile === undefined) mappingFile = rest[++i];
+    else if (!rest[i].startsWith('-') && repo === undefined) repo = rest[i];
+    else return fail(4, USAGE);
+  }
+  if (repo === undefined) return fail(4, USAGE);
+  let mapping;
+  if (mappingFile !== undefined) {
+    let entry;
+    try { entry = JSON.parse(readFileSync(mappingFile, 'utf8')); }
+    catch { return fail(3, `library-mapping-invalid: ${mappingFile} is not a readable JSON file`); }
+    try { mapping = checkMapping(entry, mappingFile); }
+    catch (e) { if (e instanceof LibraryError) return fail(3, e.message); throw e; }
+  }
+  const path = resolvePath(repo);
+  try { if (!statSync(path).isDirectory()) return fail(2, `library-git: ${repo} is not a directory`); }
+  catch { return fail(2, `library-git: ${repo} is not a directory`); }
+  try { io.stdout.write(formatSurvey(await survey({ repo: path, mapping }))); }
+  catch (e) { if (e instanceof LibraryError) return fail(2, e.message); throw e; }
+  return 0;
+}
+
+const entry = () => { try { return import.meta.url === pathToFileURL(realpathSync(process.argv[1])).href; } catch { return false; } };
+if (process.argv[1] && entry()) {
+  const code = await surveyMain(process.argv.slice(2));
+  if (code !== 0) process.exitCode = code;
+}

packages/library/tests/fixtures/mapping.json

@@ -0,0 +1,12 @@
+{
+  "kind": "library",
+  "remote": "https://git.example.invalid/writer/books.git",
+  "branch": "main",
+  "vaultPrefix": "books",
+  "universes": {
+    "harbor": {"name": "The Harbor", "books": ["Book One"], "playground": ["Book One/Playground/"]},
+    "second": {"name": "Second World", "books": ["Second World"]}
+  },
+  "types": {"Characters": "character", "Places": "place", "Research": "research", "Tracker": "tracker", "Summaries": "summary"},
+  "manuscript": ["Chapters"]
+}

packages/library/tests/helpers.mjs

@@ -0,0 +1,54 @@
+// A repo the test builds in her layout's shape: spaces and capitals in folder names, a .canvas file
+// and an unmapped top-level note. Bodies are made up; MARKER stands in for her text.
+import { mkdtempSync, rmSync, mkdirSync, writeFileSync, readFileSync, symlinkSync, chmodSync } from 'node:fs';
+import { tmpdir } from 'node:os';
+import { dirname, join } from 'node:path';
+import { execFileSync } from 'node:child_process';
+import { fileURLToPath } from 'node:url';
+import { checkMapping } from '../src/mapping.mjs';
+
+export const MARKER = 'MARKER-7f3a-HER-TEXT';
+export const FIXTURES = fileURLToPath(new URL('./fixtures/', import.meta.url));
+export const mappingEntry = () => JSON.parse(readFileSync(join(FIXTURES, 'mapping.json'), 'utf8'));
+export const mapping = (change = e => e) => checkMapping(change(mappingEntry()));
+
+export const git = (repo, ...args) => execFileSync('git', ['-c', 'user.name=fixture', '-c', '[email protected]',
+  '-c', 'commit.gpgsign=false', '-c', 'core.hooksPath=/dev/null', '-C', repo, ...args], { encoding: 'utf8' }).trim();
+
+export const BASE = {
+  'Book One/Characters/Mara Vell.md': [
+    '---', 'type: character', 'name: Mara Vell', 'appears_in: "[[Book One/Chapters/Chapter 01]]"',
+    'relationships:', '  - "[[Tomas]]"', '  - The Ferryman', '---', `Grey eyes. ${MARKER}`, ''].join('\n'),
+  'Book One/Characters/Tomas.md': ['---', 'type: character', 'name: Tomas', 'appears_in: ["[[Chapter 01]]"]', '---', MARKER, ''].join('\n'),
+  'Book One/Chapters/Chapter 01.md': [
+    '# One', `${MARKER} [[Mara Vell]] met [[Book One/Places/Harbor Town|the harbor]].`,
+    'See [[../Places/Harbor Town#Docks]] and [[books/Book One/Characters/Tomas]].',
+    '```', '[[Not A Link]]', '```', 'Inline `[[Not Either]]` and [a note](Notes.md).', ''].join('\n'),
+  'Book One/Places/Harbor Town.md': ['---', 'type: place', '---', `Salt. ${MARKER}`, ''].join('\n'),
+  'Book One/Playground/What If.md': ['---', 'name: What If', '---', `${MARKER} [[Mara Vell]]`, ''].join('\n'),
+  'Book One/Board.canvas': '{"nodes":[]}\n',
+  'Book One/Playground/Sketch.canvas': '{"nodes":[]}\n',
+  'Inbox Note.md': `${MARKER}\n`,
+  'Second World/Chapters/01.md': `# Elsewhere ${MARKER}\n`,
+};
+
+// repo({files, extra}) writes files (path -> text, or { link } / { mode, text }), commits, and
+// returns { repo, commit }.
+export function repo(t, files = BASE) {
+  const root = mkdtempSync(join(tmpdir(), 'library-'));
+  t.after(() => rmSync(root, { recursive: true, force: true }));
+  const dir = join(root, 'books');
+  mkdirSync(dir);
+  git(dir, 'init', '-q', '-b', 'main');
+  for (const [path, value] of Object.entries(files)) {
+    const file = join(dir, path);
+    mkdirSync(dirname(file), { recursive: true });
+    if (typeof value === 'object' && value.link) symlinkSync(value.link, file);
+    else if (typeof value === 'object' && value.bytes) writeFileSync(file, value.bytes);
+    else writeFileSync(file, typeof value === 'object' ? value.text : value);
+    if (typeof value === 'object' && value.mode) chmodSync(file, value.mode);
+  }
+  git(dir, 'add', '-A');
+  git(dir, 'commit', '-qm', 'fixture');
+  return { root, repo: dir, commit: git(dir, 'rev-parse', 'HEAD') };
+}

packages/library/tests/links.test.mjs

@@ -0,0 +1,50 @@
+import test from 'node:test';
+import assert from 'node:assert/strict';
+import { extractLinks, parseWikilink, resolver } from '../src/index.mjs';
+
+const PATHS = ['Book One/Characters/Mara Vell.md', 'Book One/Characters/Tomas.md', 'Book One/Places/Harbor Town.md',
+  'Book One/Chapters/Chapter 01.md', 'Book One/Places/Notes.md', 'Book One/Characters/Notes.md', 'Mara Vell.md'];
+const resolve = resolver(PATHS, { vaultPrefix: 'books' });
+const FROM = 'Book One/Chapters/Chapter 01.md';
+
+test('resolver step 1: a path from the repo root, with or without .md', () => {
+  assert.deepEqual(resolve(FROM, 'Book One/Places/Harbor Town'), { path: 'Book One/Places/Harbor Town.md', step: 'root' });
+  assert.deepEqual(resolve(FROM, 'Book One/Places/Harbor Town.md'), { path: 'Book One/Places/Harbor Town.md', step: 'root' });
+  // Root wins over shortest: Mara Vell.md at the root, not the character page.
+  assert.deepEqual(resolve(FROM, 'Mara Vell'), { path: 'Mara Vell.md', step: 'root' });
+});
+
+test('resolver step 2: the same path with vaultPrefix/ stripped', () => {
+  assert.deepEqual(resolve(FROM, 'books/Book One/Characters/Tomas'), { path: 'Book One/Characters/Tomas.md', step: 'vault-prefix' });
+  assert.deepEqual(resolver(PATHS)(FROM, 'books/Book One/Characters/Tomas'), { path: null, step: 'missing' });
+});
+
+test('resolver step 3: a path relative to the linking file, never above the repo root', () => {
+  assert.deepEqual(resolve(FROM, '../Places/Harbor Town'), { path: 'Book One/Places/Harbor Town.md', step: 'relative' });
+  assert.deepEqual(resolve('Book One/Places/Harbor Town.md', './Notes'), { path: 'Book One/Places/Notes.md', step: 'relative' });
+  assert.deepEqual(resolve(FROM, '../../../Book One/Places/Harbor Town'), { path: null, step: 'missing' });
+});
+
+test('resolver step 4: a base name that matches exactly one indexed file', () => {
+  assert.deepEqual(resolve(FROM, 'Tomas'), { path: 'Book One/Characters/Tomas.md', step: 'shortest' });
+  assert.deepEqual(resolve(FROM, 'Harbor Town.md'), { path: 'Book One/Places/Harbor Town.md', step: 'shortest' });
+  assert.deepEqual(resolve(FROM, 'Notes'), { path: null, step: 'ambiguous', count: 2 });
+  assert.deepEqual(resolve(FROM, 'Nobody'), { path: null, step: 'missing' });
+  // A partial path is not a base name.
+  assert.deepEqual(resolve(FROM, 'Places/Harbor Town'), { path: null, step: 'missing' });
+});
+
+test('a link into another of her repos resolves to nothing', () => {
+  assert.deepEqual(resolve(FROM, 'bean-brain/Journal/Today'), { path: null, step: 'missing' });
+  assert.deepEqual(resolve(FROM, '../bean-brain/Journal/Today'), { path: null, step: 'missing' });
+});
+
+test('wikilink forms, embeds, and links skipped inside code', () => {
+  assert.deepEqual(parseWikilink('[[A/B#Head|Label]]'), { file: 'A/B', heading: 'Head', label: 'Label', embed: false });
+  assert.deepEqual(parseWikilink('![[pic.png]]'), { file: 'pic.png', heading: null, label: null, embed: true });
+  assert.equal(parseWikilink('[[a]] and more'), null);
+  const lines = [[1, '[[One]] [[Two|2]] [[Three#H]] ![[Four]] [[#Self]]'], [2, '```js'], [3, '[[Fenced]]'], [4, '```'],
+    [5, 'Inline `[[Code]]` and [md](Five.md) and [web](https://example.invalid/x)']];
+  assert.deepEqual(extractLinks(lines).map(l => [l.file, l.line]), [['One', 1], ['Two', 1], ['Three', 1], ['Four', 1], ['', 1]]);
+  assert.deepEqual(extractLinks(lines, { markdown: true }).filter(l => l.markdown).map(l => l.file), ['Five.md']);
+});

packages/library/tests/mapping.test.mjs

@@ -0,0 +1,82 @@
+import test from 'node:test';
+import assert from 'node:assert/strict';
+import { checkMapping, classify, LibraryError } from '../src/index.mjs';
+import { mapping, mappingEntry } from './helpers.mjs';
+
+const refuses = (change, code, pattern) => assert.throws(() => checkMapping(change(mappingEntry())),
+  e => e instanceof LibraryError && e.code === code && (!pattern || pattern.test(e.message)));
+
+test('the fixture mapping checks and comes back frozen', () => {
+  const m = mapping();
+  assert.equal(m.universes.harbor.playground[0], 'Book One/Playground/');
+  assert.ok(Object.isFrozen(m.universes.harbor.books));
+  assert.throws(() => { m.types.Extra = 'place'; });
+});
+
+test('a playground prefix outside its universe books refuses library-playground-outside-book', () => {
+  refuses(e => { e.universes.harbor.playground = ['Second World/Playground/']; return e; }, 'library-playground-outside-book');
+  refuses(e => { e.universes.harbor.playground = ['Elsewhere/']; return e; }, 'library-playground-outside-book');
+  // The whole book as its playground would leave no canon: not inside the book.
+  refuses(e => { e.universes.harbor.playground = ['Book One/']; return e; }, 'library-playground-outside-book');
+});
+
+test('no playground prefix holds another, and no book folder holds another', () => {
+  refuses(e => { e.universes.harbor.playground = ['Book One/Playground/', 'Book One/Playground/Deep/']; return e; },
+    'library-mapping-invalid', /holds playground/);
+  refuses(e => { e.universes.second.books = ['Second World', 'Book One/Part Two']; return e; }, 'library-mapping-invalid', /holds book folder/);
+  refuses(e => { e.universes.second.books = ['Book One']; return e; }, 'library-mapping-invalid', /in two universes/);
+});
+
+test('shape refusals: kind, remote, branch, unknown keys, types, manuscript, folder names', () => {
+  refuses(e => ({ ...e, kind: 'code' }), 'library-mapping-invalid', /kind/);
+  refuses(e => ({ ...e, remote: 'http://git.example.invalid/x.git' }), 'library-mapping-invalid', /https/);
+  refuses(e => ({ ...e, remote: 'https://user:[email protected]/x.git' }), 'library-mapping-invalid', /credentials/);
+  refuses(e => ({ ...e, remote: '[email protected]:x.git' }), 'library-mapping-invalid', /https/);
+  refuses(e => ({ ...e, branch: 'main..x' }), 'library-mapping-invalid', /branch/);
+  refuses(e => ({ ...e, root: '/tmp' }), 'library-mapping-invalid', /unknown key "root"/);
+  refuses(e => { e.universes.harbor.extra = 1; return e; }, 'library-mapping-invalid', /unknown key/);
+  refuses(e => { e.types.Characters = 'villain'; return e; }, 'library-mapping-invalid', /types.Characters/);
+  refuses(e => { e.types['A/B'] = 'place'; return e; }, 'library-mapping-invalid', /one folder name/);
+  refuses(e => ({ ...e, manuscript: ['Characters'] }), 'library-mapping-invalid', /also a type folder/);
+  refuses(e => { e.universes.harbor.books = ['../Book One']; return e; }, 'library-mapping-invalid', /folder path/);
+  refuses(e => ({ ...e, vaultPrefix: 'a/b' }), 'library-mapping-invalid', /vaultPrefix/);
+  refuses(e => ({ ...e, universes: {} }), 'library-mapping-invalid', /at least one universe/);
+  refuses(e => { e.universes['bad id'] = e.universes.second; delete e.universes.second; return e; }, 'library-mapping-invalid', /plain id/);
+});
+
+test('a hybrid universe is a shape the query code can take (1.4), with sources that must exist', () => {
+  const hybrid = e => { e.universes.cross = { kind: 'hybrid', name: 'Crossover', sources: ['harbor', 'second'], books: ['Crossover'],
+    constraints: [{ exclude: 'second/Characters' }, { pin: { entity: 'Book One/Characters/Mara Vell.md', field: 'eyes', value: 'grey' } }],
+    notes: 'Set after book one.' }; return e; };
+  const m = checkMapping(hybrid(mappingEntry()));
+  assert.deepEqual(m.universes.cross.sources, ['harbor', 'second']);
+  refuses(e => { hybrid(e); e.universes.cross.sources = ['harbor', 'nowhere']; return e; }, 'library-mapping-invalid', /non-hybrid universe/);
+  refuses(e => { hybrid(e); e.universes.cross.sources = ['harbor']; return e; }, 'library-mapping-invalid', /two or more/);
+  refuses(e => { hybrid(e); e.universes.cross.constraints = [{ exclude: 'x', pin: {} }]; return e; }, 'library-mapping-invalid', /exactly one/);
+});
+
+test('a caller-supplied fail receives the code, as business file loading will pass it (C2-04)', () => {
+  const seen = [];
+  const fail = (code, message) => { seen.push(code); throw new Error(message); };
+  const entry = mappingEntry();
+  entry.universes.harbor.playground = ['Elsewhere/'];
+  assert.throws(() => checkMapping(entry, 'businesses/acme.json projects.books', { fail }), /businesses\/acme.json projects.books/);
+  assert.deepEqual(seen, ['library-playground-outside-book']);
+});
+
+test('scope comes from the path alone (design 1.2)', () => {
+  const m = mapping();
+  assert.deepEqual(classify(m, 'Book One/Characters/Mara Vell.md'),
+    { scope: 'canon', universe: 'harbor', book: 'Book One', type: 'character', folder: 'Characters' });
+  assert.deepEqual(classify(m, 'Book One/Chapters/Chapter 01.md'),
+    { scope: 'canon', universe: 'harbor', book: 'Book One', type: 'manuscript', folder: 'Chapters' });
+  assert.deepEqual(classify(m, 'Book One/Playground/What If.md'),
+    { scope: 'playground', universe: 'harbor', book: 'Book One', type: null, folder: null });
+  assert.deepEqual(classify(m, 'Book One/Playground/Characters/New.md'),
+    { scope: 'playground', universe: 'harbor', book: 'Book One', type: 'character', folder: 'Characters' });
+  assert.deepEqual(classify(m, 'Book One/Notes.md'), { scope: 'canon', universe: 'harbor', book: 'Book One', type: null, folder: null });
+  assert.equal(classify(m, 'Second World/Chapters/01.md').universe, 'second');
+  for (const path of ['Inbox Note.md', 'Book One/Board.canvas', 'Book One/Playground/Sketch.canvas', 'Book One/Board.base',
+    'Book One/cover.png', 'Book One/Upper.MD', 'Book Onex/a.md', 'book one/a.md', 'Elsewhere/Book One/a.md'])
+    assert.deepEqual(classify(m, path), { scope: 'unmapped' }, path);
+});

packages/library/tests/reader.test.mjs

@@ -0,0 +1,151 @@
+import test from 'node:test';
+import assert from 'node:assert/strict';
+import { writeFileSync } from 'node:fs';
+import { join } from 'node:path';
+import { readLibrary, parseFrontMatter, LibraryError, MAX_BLOB } from '../src/index.mjs';
+import { BASE, git, mapping, repo } from './helpers.mjs';
+
+const codes = (result, path) => result.problems.filter(p => p.path === path).map(p => p.code);
+const file = (result, path) => result.files.find(f => f.path === path);
+
+test('the fixture reads clean: every resolver step, appears_in and relationships wikilinks indexed', async t => {
+  const r = repo(t);
+  const result = await readLibrary({ repo: r.repo, commit: r.commit, mapping: mapping() });
+  assert.equal(result.commit, r.commit);
+  assert.deepEqual(result.files.map(f => [f.path, f.scope]), [
+    ['Book One/Chapters/Chapter 01.md', 'canon'], ['Book One/Characters/Mara Vell.md', 'canon'],
+    ['Book One/Characters/Tomas.md', 'canon'], ['Book One/Places/Harbor Town.md', 'canon'],
+    ['Book One/Playground/What If.md', 'playground'], ['Second World/Chapters/01.md', 'canon']]);
+  const chapter = file(result, 'Book One/Chapters/Chapter 01.md');
+  assert.deepEqual(chapter.links.map(l => [l.path, l.step, l.line]), [
+    ['Book One/Characters/Mara Vell.md', 'shortest', 2], ['Book One/Places/Harbor Town.md', 'root', 2],
+    ['Book One/Places/Harbor Town.md', 'relative', 3], ['Book One/Characters/Tomas.md', 'vault-prefix', 3]]);
+  const mara = file(result, 'Book One/Characters/Mara Vell.md');
+  assert.deepEqual(mara.frontmatter, { type: 'character', name: 'Mara Vell', appears_in: '[[Book One/Chapters/Chapter 01]]',
+    relationships: ['[[Tomas]]', 'The Ferryman'] });
+  assert.deepEqual(mara.links.map(l => [l.field, l.path, l.line]), [
+    ['appears_in', 'Book One/Chapters/Chapter 01.md', 4], ['relationships', 'Book One/Characters/Tomas.md', 5]]);
+  assert.deepEqual(file(result, 'Book One/Characters/Tomas.md').links.map(l => [l.field, l.path]),
+    [['appears_in', 'Book One/Chapters/Chapter 01.md']]);
+  assert.equal(mara.bodyLine, 9);
+  assert.equal(mara.lines[8][0], 9);
+  assert.equal(mara.type, 'character');
+  // Only the unmapped paths are problems: the top-level note and both .canvas files.
+  assert.deepEqual(result.problems.map(p => [p.code, p.path]), [
+    ['R2', 'Book One/Board.canvas'], ['R2', 'Book One/Playground/Sketch.canvas'], ['R2', 'Inbox Note.md']]);
+  assert.ok(Object.isFrozen(result.files[0].links));
+});
+
+test('R1: executables, symlinks, gitlinks, blobs over 1 MiB and non-UTF-8 text are not indexed', async t => {
+  const r = repo(t, { ...BASE,
+    'Book One/Places/Run.md': { text: 'x\n', mode: 0o755 },
+    'Book One/Places/Link.md': { link: 'Harbor Town.md' },
+    'Book One/Places/Big.md': 'x'.repeat(MAX_BLOB + 1),
+    'Book One/Places/Edge.md': 'y'.repeat(MAX_BLOB),
+    'Book One/Places/Latin.md': { bytes: Buffer.from([0x63, 0x61, 0x66, 0xe9, 0x0a]) },
+    'Book One/Places/Nul.md': 'a\0b\n' });
+  git(r.repo, 'update-index', '--add', '--cacheinfo', `160000,${r.commit},Book One/Places/Sub.md`);
+  git(r.repo, 'commit', '-qm', 'gitlink');
+  const result = await readLibrary({ repo: r.repo, commit: git(r.repo, 'rev-parse', 'HEAD'), mapping: mapping() });
+  for (const name of ['Run', 'Link', 'Big', 'Latin', 'Nul', 'Sub']) {
+    assert.deepEqual(codes(result, `Book One/Places/${name}.md`), ['R1'], name);
+    assert.equal(file(result, `Book One/Places/${name}.md`), undefined, name);
+  }
+  assert.ok(file(result, 'Book One/Places/Edge.md'), 'exactly 1 MiB is read');
+});
+
+test('R2: unmapped paths are reported and not indexed', async t => {
+  const r = repo(t);
+  const result = await readLibrary({ repo: r.repo, commit: r.commit, mapping: mapping() });
+  for (const path of ['Inbox Note.md', 'Book One/Board.canvas', 'Book One/Playground/Sketch.canvas']) {
+    assert.deepEqual(codes(result, path), ['R2']);
+    assert.equal(file(result, path), undefined);
+  }
+});
+
+test('R3: front matter not fully parsed stays raw, with the line where parsing stopped', async t => {
+  const r = repo(t, { ...BASE,
+    'Book One/Places/Nested.md': ['---', 'type: place', 'coords:', '  lat: 1', '---', 'Body [[Tomas]]', ''].join('\n'),
+    'Book One/Places/Block.md': ['---', 'summary: |', '  text', '---', ''].join('\n'),
+    'Book One/Places/Open.md': ['---', 'type: place', 'never closed', ''].join('\n') });
+  const result = await readLibrary({ repo: r.repo, commit: r.commit, mapping: mapping() });
+  const nested = file(result, 'Book One/Places/Nested.md');
+  assert.deepEqual(result.problems.filter(p => p.path === 'Book One/Places/Nested.md'), [{ code: 'R3', path: 'Book One/Places/Nested.md', line: 4, message: 'front matter not fully parsed' }]);
+  assert.equal(nested.frontmatter, null);
+  assert.equal(nested.frontmatterRaw, 'type: place\ncoords:\n  lat: 1');
+  assert.deepEqual(nested.links.map(l => l.path), ['Book One/Characters/Tomas.md'], 'still indexed by body');
+  assert.equal(result.problems.find(p => p.path === 'Book One/Places/Block.md').line, 2);
+  assert.equal(result.problems.find(p => p.path === 'Book One/Places/Open.md').line, 1);
+  assert.equal(file(result, 'Book One/Places/Open.md').bodyLine, 1);
+});
+
+test('front matter forms the reader accepts and refuses', () => {
+  const parse = text => parseFrontMatter(text.split('\n'));
+  assert.deepEqual(parse('---\na: plain words\nb: "quoted: yes"\nc: \'it\'\'s\'\nd: [x, "y z", 3]\ne:\n- one\n- "[[Two]]"\nf: [[Wiki]]\ng: true\nh:\n---').frontmatter,
+    { a: 'plain words', b: 'quoted: yes', c: "it's", d: ['x', 'y z', 3], e: ['one', '[[Two]]'], f: '[[Wiki]]', g: true, h: null });
+  for (const bad of ['a: {x: 1}', 'a: &anchor x', 'a: [x, [y]]', 'a: x: y', 'a: 1\na: 2', '  a: 1', 'a: "open', '- loose'])
+    assert.notEqual(parse(`---\n${bad}\n---`).stop, null, bad);
+  assert.deepEqual(parse('no front matter'), { frontmatter: null, raw: null, bodyLine: 1, stop: null });
+});
+
+test('R4: a link to no file, to more than one, or into another repo is reported and not followed', async t => {
+  const r = repo(t, { ...BASE,
+    'Book One/Research/Notes.md': 'a\n', 'Book One/Places/Notes.md': 'b\n',
+    'Book One/Chapters/Links.md': ['[[Nobody]]', '[[Notes]]', '[[bean-brain/Journal/Today]]', '[[Tomas]]', ''].join('\n') });
+  const result = await readLibrary({ repo: r.repo, commit: r.commit, mapping: mapping() });
+  assert.deepEqual(result.problems.filter(p => p.path === 'Book One/Chapters/Links.md').map(p => [p.code, p.line]), [['R4', 1], ['R4', 2], ['R4', 3]]);
+  assert.deepEqual(file(result, 'Book One/Chapters/Links.md').links.map(l => l.path), ['Book One/Characters/Tomas.md']);
+});
+
+test('R5: a canon file that refers into the playground is reported, and the link still goes by path', async t => {
+  const r = repo(t, { ...BASE, 'Book One/Places/Dock.md': 'See [[What If]].\n' });
+  const result = await readLibrary({ repo: r.repo, commit: r.commit, mapping: mapping() });
+  assert.deepEqual(codes(result, 'Book One/Places/Dock.md'), ['R5']);
+  assert.deepEqual(file(result, 'Book One/Places/Dock.md').links.map(l => l.path), ['Book One/Playground/What If.md']);
+  // The playground file links to canon: no problem, R5 is only about canon.
+  assert.deepEqual(codes(result, 'Book One/Playground/What If.md'), []);
+});
+
+test('R6: a canon file that refers into another universe is reported; a hybrid may refer into its sources', async t => {
+  const r = repo(t, { ...BASE, 'Book One/Places/Far.md': 'Like [[Second World/Chapters/01]].\n',
+    'Crossover/Chapters/A.md': 'From [[Mara Vell]] and [[Second World/Chapters/01]].\n' });
+  const hybrid = mapping(e => { e.universes.cross = { kind: 'hybrid', name: 'Cross', sources: ['harbor', 'second'], books: ['Crossover'] }; return e; });
+  const result = await readLibrary({ repo: r.repo, commit: r.commit, mapping: hybrid });
+  assert.deepEqual(codes(result, 'Book One/Places/Far.md'), ['R6']);
+  assert.deepEqual(file(result, 'Book One/Places/Far.md').links.map(l => l.path), ['Second World/Chapters/01.md']);
+  assert.deepEqual(codes(result, 'Crossover/Chapters/A.md'), []);
+});
+
+test('R7: two paths that differ only in case are both left out', async t => {
+  const r = repo(t, BASE);
+  writeFileSync(join(r.root, 'twin'), 'twin\n');
+  const blob = git(r.repo, 'hash-object', '-w', join(r.root, 'twin'));
+  git(r.repo, 'update-index', '--add', '--cacheinfo', `100644,${blob},Book One/Characters/tomas.md`);
+  git(r.repo, 'commit', '-qm', 'case twin');
+  const result = await readLibrary({ repo: r.repo, commit: git(r.repo, 'rev-parse', 'HEAD'), mapping: mapping() });
+  for (const path of ['Book One/Characters/Tomas.md', 'Book One/Characters/tomas.md']) {
+    assert.deepEqual(codes(result, path), ['R7'], path);
+    assert.equal(file(result, path), undefined);
+  }
+});
+
+test('the reader reads the commit, never the working tree, and refuses a bad commit id', async t => {
+  const r = repo(t);
+  writeFileSync(join(r.repo, 'Book One/Places/Harbor Town.md'), 'unsaved [[Nobody]]\n');
+  writeFileSync(join(r.repo, 'Book One/Places/Untracked.md'), 'x\n');
+  const result = await readLibrary({ repo: r.repo, commit: r.commit, mapping: mapping() });
+  assert.equal(file(result, 'Book One/Places/Harbor Town.md').lines[0][1], '---');
+  assert.equal(file(result, 'Book One/Places/Untracked.md'), undefined);
+  for (const commit of ['HEAD', r.commit.slice(0, 12), '0'.repeat(40), git(r.repo, 'rev-parse', 'HEAD^{tree}')])
+    await assert.rejects(readLibrary({ repo: r.repo, commit, mapping: mapping() }), e => e instanceof LibraryError, commit);
+  await assert.rejects(readLibrary({ repo: r.repo, commit: r.commit, mapping: {} }), /library-mapping-invalid/);
+});
+
+test('a bare mirror reads the same as the clone', async t => {
+  const r = repo(t);
+  const bare = join(r.root, 'mirror.git');
+  git(r.root, 'clone', '-q', '--bare', r.repo, bare);
+  const a = await readLibrary({ repo: r.repo, commit: r.commit, mapping: mapping() });
+  const b = await readLibrary({ repo: bare, commit: r.commit, mapping: mapping() });
+  assert.deepEqual(b, a);
+});

packages/library/tests/render.test.mjs

@@ -0,0 +1,80 @@
+import test from 'node:test';
+import assert from 'node:assert/strict';
+import { renderItems, UNREADABLE } from '../src/index.mjs';
+
+const A = 'a'.repeat(40), B = 'b'.repeat(40);
+const cite = (path, lines, quote, commit = A) => ({ path, commit, lines, quote });
+const options = {
+  scopeOf: path => path.includes('/Playground/') ? 'playground' : path.endsWith('.md') ? 'canon' : undefined,
+  changed: ({ path, commit }) => path === 'Book One/Characters/Mara Vell.md' && commit === A,
+};
+const render = items => renderItems(JSON.stringify({ items }), options);
+
+// One snapshot per item kind: the plain text both channels show.
+const SNAPSHOTS = {
+  fact: [{ kind: 'fact', text: 'Tomas is the ferryman.', cites: [cite('Book One/Characters/Tomas.md', [3, 3], 'the ferryman', B)] }],
+  finding: [{ kind: 'finding', text: 'Eye colour differs.', cites: [cite('Book One/Chapters/Chapter 01.md', [41, 41], 'her grey eyes'),
+    cite('Book One/Characters/Mara Vell.md', [9, 10], 'green eyes')] }],
+  correction: [{ kind: 'correction', text: 'Chapter 1 says grey.', from: 'green eyes', to: 'grey eyes',
+    cites: [cite('Book One/Characters/Mara Vell.md', [9, 9], 'green eyes', B)] }],
+  question: [{ kind: 'question', text: 'Is the harbor north of the town?', cites: [cite('Book One/Places/Harbor Town.md', [2, 4], 'the harbor', B)] }],
+  idea: [{ kind: 'idea', text: 'A storm could close the harbor.', cites: [cite('Book One/Playground/What If.md', [5, 5], 'a storm', B),
+    { url: 'https://example.invalid/tides', quote: 'spring tides' }] }],
+};
+const EXPECTED = {
+  fact: '1. Fact: Tomas is the ferryman.\n   [canon] Book One/Characters/Tomas.md:3 @bbbbbbb "the ferryman"',
+  finding: '1. Finding: Eye colour differs.\n   [canon] Book One/Chapters/Chapter 01.md:41 @aaaaaaa "her grey eyes"\n'
+    + '   [canon] Book One/Characters/Mara Vell.md:9-10 @aaaaaaa "green eyes" (changed since)',
+  correction: '1. Correction: Chapter 1 says grey.\n   From: "green eyes"\n   To: "grey eyes"\n'
+    + '   [canon] Book One/Characters/Mara Vell.md:9 @bbbbbbb "green eyes"',
+  question: '1. Question: Is the harbor north of the town?\n   [canon] Book One/Places/Harbor Town.md:2-4 @bbbbbbb "the harbor"',
+  idea: '1. Idea: A storm could close the harbor.\n   [playground] Book One/Playground/What If.md:5 @bbbbbbb "a storm"\n'
+    + '   [web] https://example.invalid/tides "spring tides"',
+};
+
+for (const kind of Object.keys(SNAPSHOTS)) {
+  test(`renderItems snapshot: ${kind}`, () => {
+    const out = render(SNAPSHOTS[kind]);
+    assert.equal(out.kind, 'items');
+    assert.equal(out.text, EXPECTED[kind]);
+    assert.equal(out.items[0].kind, kind);
+  });
+}
+
+test('renderItems numbers several items and takes a parsed body as well as a string', () => {
+  const items = [...SNAPSHOTS.fact, ...SNAPSHOTS.question];
+  const out = renderItems({ items }, options);
+  assert.equal(out.text, `${EXPECTED.fact}\n${EXPECTED.question.replace(/^1\./, '2.')}`);
+  assert.deepEqual(out.items[1].cites[0], { badge: 'canon', path: 'Book One/Places/Harbor Town.md', commit: B, lines: [2, 4],
+    ref: 'Book One/Places/Harbor Town.md:2-4 @bbbbbbb', quote: 'the harbor', changed: false });
+});
+
+test('without options a path cite has no badge and is never marked changed', () => {
+  assert.equal(renderItems({ items: SNAPSHOTS.finding }).text,
+    '1. Finding: Eye colour differs.\n   Book One/Chapters/Chapter 01.md:41 @aaaaaaa "her grey eyes"\n'
+    + '   Book One/Characters/Mara Vell.md:9-10 @aaaaaaa "green eyes"');
+});
+
+const NOTICE_SNAPSHOTS = { 'no-cited-answer': 'No cited answer', 'no-answer': 'No answer', 'turn-failed': 'The turn failed' };
+for (const [notice, text] of Object.entries(NOTICE_SNAPSHOTS)) {
+  test(`renderItems snapshot: notice ${notice}`, () => {
+    assert.deepEqual(renderItems(JSON.stringify({ items: [], notice }), options), { kind: 'notice', notice, text });
+  });
+}
+
+test('a body without the reply shape shows a fixed line and none of its text', () => {
+  const secret = 'free prose the guard would refuse';
+  const bodies = [secret, JSON.stringify(secret), '{"items": [], "notice": "other"}', JSON.stringify({ items: [], notice: 'no-answer', extra: secret }),
+    JSON.stringify({ items: [] }), JSON.stringify({ items: [{ kind: 'story', text: secret, cites: [] }] }),
+    JSON.stringify({ items: [{ kind: 'fact', text: secret }] }), JSON.stringify({ items: SNAPSHOTS.fact, prose: secret }),
+    JSON.stringify({ items: [{ kind: 'correction', text: secret, cites: [] }] }),
+    JSON.stringify({ items: [{ kind: 'fact', text: secret, cites: [cite('a.md', [2, 1], 'q')] }] }),
+    JSON.stringify({ items: [{ kind: 'fact', text: secret, cites: [{ path: 'a.md', commit: 'abc', lines: [1, 1], quote: 'q' }] }] }),
+    JSON.stringify({ items: [{ kind: 'fact', text: secret, cites: [{ url: 'https://x.invalid', path: 'a.md', quote: 'q' }] }] }),
+    null, 42, '[]'];
+  for (const body of bodies) {
+    const out = renderItems(body, options);
+    assert.deepEqual(out, { kind: 'unreadable', text: UNREADABLE }, String(body));
+    assert.ok(!JSON.stringify(out).includes(secret));
+  }
+});

packages/library/tests/survey.test.mjs

@@ -0,0 +1,82 @@
+import test from 'node:test';
+import assert from 'node:assert/strict';
+import { writeFileSync } from 'node:fs';
+import { join } from 'node:path';
+import { spawnSync } from 'node:child_process';
+import { fileURLToPath } from 'node:url';
+import { surveyMain } from '../src/index.mjs';
+import { BASE, FIXTURES, MARKER, repo } from './helpers.mjs';
+
+const ROOT = fileURLToPath(new URL('../../..', import.meta.url));
+async function run(args) {
+  let stdout = '', stderr = '';
+  const code = await surveyMain(args, { stdout: { write: s => { stdout += s; } }, stderr: { write: s => { stderr += s; } } });
+  return { code, stdout, stderr };
+}
+// Strings from the fixture that are text, values, file names or link targets: none may be printed.
+const NEVER = [MARKER, 'Grey eyes', 'The Ferryman', 'Mara Vell', 'Tomas', 'Harbor Town', 'What If', 'Inbox Note', 'Chapter 01',
+  'Sketch', 'Board', 'Not A Link', 'the harbor', 'Docks', 'character'];
+
+test('the survey prints folder names, counts, key sets and link-form counts, and never text', async t => {
+  const r = repo(t, { ...BASE, 'Book One/Places/Odd.md': ['---', `"${MARKER} key": 1`, '---', ''].join('\n') });
+  const out = await run(['survey', r.repo]);
+  assert.equal(out.code, 0, out.stderr);
+  assert.equal(out.stdout, [
+    `commit ${r.commit}`,
+    'entries 10',
+    'folders (direct children: md canvas base other)',
+    '  (root) 1 0 0 0',
+    '  "Book One" 0 1 0 0',
+    '  "Book One/Chapters" 1 0 0 0',
+    '  "Book One/Characters" 2 0 0 0',
+    '  "Book One/Places" 2 0 0 0',
+    '  "Book One/Playground" 1 1 0 0',
+    '  "Second World/Chapters" 1 0 0 0',
+    'markdown 8 files, 8 read, 3 without front matter, 0 with front matter not fully parsed',
+    'front matter key sets',
+    '  1 [(other key)]',
+    '  1 [appears_in, name, relationships, type]',
+    '  1 [appears_in, name, type]',
+    '  1 [name]',
+    '  1 [type]',
+    'body links plain 3, label 1, heading 1, embed 0, self 0, markdown 1',
+    'field appears_in wikilink 2, name 0',
+    'field relationships wikilink 1, name 1',
+    ''].join('\n'));
+  for (const s of NEVER) assert.ok(!out.stdout.includes(s), s);
+});
+
+test('with --mapping the survey adds scope, resolver step and problem counts', async t => {
+  const r = repo(t);
+  const out = await run(['survey', r.repo, '--mapping', join(FIXTURES, 'mapping.json')]);
+  assert.equal(out.code, 0, out.stderr);
+  const tail = out.stdout.trimEnd().split('\n').slice(-3);
+  assert.deepEqual(tail, [
+    'scopes canon 5, playground 1, unmapped 3; indexed 6',
+    'resolved root 2, vault-prefix 1, relative 2, shortest 3, unresolved 0',
+    'problems R1 0, R2 3, R3 0, R4 0, R5 0, R6 0, R7 0']);
+  for (const s of NEVER) assert.ok(!out.stdout.includes(s), s);
+});
+
+test('survey exit codes: usage 4, bad mapping 3, unreadable repo 2', async t => {
+  const r = repo(t);
+  for (const args of [[], ['scan', r.repo], ['survey'], ['survey', r.repo, '--mapping'], ['survey', r.repo, '--other'], ['survey', r.repo, r.repo]])
+    assert.equal((await run(args)).code, 4, args.join(' '));
+  const bad = join(r.root, 'bad.json');
+  writeFileSync(bad, JSON.stringify({ kind: 'library' }));
+  const refused = await run(['survey', r.repo, '--mapping', bad]);
+  assert.equal(refused.code, 3);
+  assert.match(refused.stderr, /library-mapping-invalid/);
+  writeFileSync(bad, 'not json');
+  assert.equal((await run(['survey', r.repo, '--mapping', bad])).code, 3);
+  assert.equal((await run(['survey', join(r.root, 'missing')])).code, 2);
+  assert.equal((await run(['survey', r.root])).code, 2, 'a directory that is not a repo');
+});
+
+test('scripts/mosaic library survey reaches the survey', t => {
+  const r = repo(t);
+  const out = spawnSync(join(ROOT, 'scripts/mosaic'), ['library', 'survey', r.repo], { encoding: 'utf8', timeout: 30000 });
+  assert.equal(out.status, 0, out.stderr);
+  assert.match(out.stdout, new RegExp(`^commit ${r.commit}\n`));
+  assert.ok(!out.stdout.includes(MARKER));
+});

scripts/mosaic

@@ -34,6 +34,12 @@ if [ "${1:-}" = business ]; then
   shift
   exec node "$REPO/packages/business/src/cli.mjs" "$@"
 fi
+# `mosaic library survey`: names and counts from a writing repo, never its text
+# (packages/library/README.md). Other library verbs are bus verbs.
+if [ "${1:-}" = library ] && [ "${2:-}" = survey ]; then
+  shift
+  exec node "$REPO/packages/library/src/survey.mjs" "$@"
+fi
 case "${1:-}" in
   usage|project|limits|inbox|decide|tasks|agents|trail|talk|stop|launches|bus|plugins|name|names|follow|threads|thread) exec node "$REPO/packages/cli/src/cli.mjs" "$@" ;;
 esac

scripts/stack-copy.sh

@@ -27,7 +27,7 @@ COPY_PATHS=(
  packages/conversation/src packages/discord/src packages/discord/bin packages/discord/extension packages/harness/src
  packages/seat/src packages/tasks/src packages/tasks/fields.json packages/tasks/requirements.json
  packages/webui/src packages/webui/README.md packages/cli/README.md
- packages/queue/src
+ packages/queue/src packages/library/src
  # Whole directory: every in-repo plug-in module ships with the copy (row 131).
  packages/plugins
 )

scripts/stack-release.sh

@@ -3,7 +3,7 @@
 # Moves the bus, the Console and the human CLI from the pointer's copy to another copy together,
 # behind a health gate, and puts the old stack back inside the same run when the gate fails.
 # Console tester listener flags follow target support (row 176, #1674); so does the row 178 proof
-# pair, which activate sets or drops (row 187, #1685).
+# pair, which activate sets or drops (row 187, #1685). activate --no-send drops --send (row 189, #1687).
 # Design and tests: agents/darkwing/work/queue-162/BUILD.md.
 #
 # Who runs it. Decision 96 (Mos, mos-0716) lets this script stop and start the live units under
@@ -30,13 +30,13 @@ BIN="$HOME/.npm-global/bin"
 UNIT_DIR="${XDG_CONFIG_HOME:-$HOME/.config}/systemd/user"
 CONSOLE_UNIT=mosaic-webui.service
 TIMEOUT=60 WANT_PM=0 AFTER_HARNESS=0 MIGRATE=0 PLAN=0 RESTORE="" EVENTS="" TESTER_PORT=""
-PROOF_HEADER="" PROOF_FILE="" NO_PROOF=0 R_BACKUP="" R_PORT=""
+PROOF_HEADER="" PROOF_FILE="" NO_PROOF=0 NO_SEND=0 R_BACKUP="" R_PORT=""
 
 usage() {
     cat >&2 <<'USAGE'
 usage: stack-release.sh adopt BUSINESS
        stack-release.sh activate ID BUSINESS [--pm | --pm-after-harness] [--migrate] [--tester-port N]
-           [--proof-header NAME --proof-file PATH | --no-proof] [--timeout S] [--plan]
+           [--proof-header NAME --proof-file PATH | --no-proof] [--no-send] [--timeout S] [--plan]
        stack-release.sh pm-on BUSINESS [--timeout S]
        stack-release.sh rollback BUSINESS [--restore ACTIVATION [--events N]] [--timeout S] [--plan]
        stack-release.sh status BUSINESS
@@ -85,6 +85,7 @@ parse_opts() {
             --proof-header) [ "$OP" = activate ] && [ $# -ge 2 ] && [ -n "$2" ] || usage; PROOF_HEADER="$2"; shift 2 ;;
             --proof-file) [ "$OP" = activate ] && [ $# -ge 2 ] && [ -n "$2" ] || usage; PROOF_FILE="$2"; shift 2 ;;
             --no-proof) [ "$OP" = activate ] || usage; NO_PROOF=1; shift ;;
+            --no-send) [ "$OP" = activate ] || usage; NO_SEND=1; shift ;;
             --migrate) [ "$OP" = activate ] || usage; MIGRATE=1; shift ;;
             --restore) [ "$OP" = rollback ] && [ $# -ge 2 ] && [[ "$2" =~ ^[0-9]{8}T[0-9]{6}Z-[0-9a-f]{12}(-[1-9])?$ ]] || usage; RESTORE="$2"; shift 2 ;;
             --backup) [ "$OP" = rehearse ] && [ $# -ge 2 ] && { [[ "$2" =~ ^[0-9]{8}T[0-9]{6}Z-[0-9a-f]{12}(-[1-9])?$ ]] || [[ "$2" =~ ^/[A-Za-z0-9/._+-]*$ ]]; } || usage; R_BACKUP="$2"; shift 2 ;;
@@ -244,14 +245,16 @@ target_schema() {
 in_chain() { local v; for v in "${T_CHAIN[@]}"; do [ "$v" != "$1" ] || return 0; done; return 1; }
 
 # The item 3 checks on the target copy, in order: copy, schema, already-active. An activate that
-# sets a proof pair, or drops the pointer's pair with --no-proof, may name the pointer's copy: it
-# re-pins the live copy with new Console flags (row 187, Part B's B3 and B-R1).
+# sets a proof pair, drops the pointer's pair with --no-proof, or drops the pointer's --send with
+# --no-send, may name the pointer's copy: it re-pins the live copy with new Console flags (row 187,
+# Part B's B3 and B-R1; row 189, mos-0972).
 check_target() {
     copy_exists "$TO" 2>/dev/null || refuse copy-missing "no copy $TO in $COPIES"
     copy_ok "$TO" 2>/dev/null || refuse copy-unreachable "$TO is not reachable from refactor and origin/refactor"
     target_schema "$TO" || refuse copy-schema-unknown "cannot read SCHEMA_VERSION and its chain from $COPIES/$TO/packages/bus/src/store.mjs"
     [ "$TO" != "$P_COPY" ] || [ -n "$PROOF_HEADER" ] ||
         { [ "$NO_PROOF" = 1 ] && [[ " ${P_CONSOLE[*]} " == *" --proof-header "* ]]; } ||
+        { [ "$NO_SEND" = 1 ] && [[ " ${P_CONSOLE[*]} " == *" --send "* ]]; } ||
         refuse already-active "$TO is the pointer's copy"
 }
 
@@ -690,6 +693,33 @@ console_for_target() {
         DROP_TESTER="--tester-port $inherited"
     fi
     proof_for_target
+    send_for_target
+}
+
+# Row 189 (mos-0972): --no-send drops --send from RUN_CONSOLE, so the unit and the pointer both lose
+# it; without the flag the pointer's --send goes on unchanged. Rollback and pm-on never take it, so
+# they carry the pointer as it is. Sets SEND_PLAN (the plan's send: line) and SEND_STEP.
+send_for_target() {
+    local had=0 i
+    local -a without_send=()
+    for ((i = 0; i < ${#RUN_CONSOLE[@]}; i++)); do
+        if [ "${RUN_CONSOLE[i]}" = --send ]; then had=1; else without_send+=("${RUN_CONSOLE[i]}"); fi
+    done
+    SEND_STEP=""
+    if [ "$NO_SEND" = 1 ]; then
+        RUN_CONSOLE=("${without_send[@]}")
+        if [ "$had" = 1 ]; then
+            SEND_PLAN="send: dropped; --no-send was given"
+            SEND_STEP="drop --send; --no-send was given"
+        else
+            SEND_PLAN="send: off; --no-send was given and the pointer holds no --send"
+            SEND_STEP="--no-send was given and the pointer holds no --send, so there is nothing to drop"
+        fi
+    elif [ "$had" = 1 ]; then
+        SEND_PLAN="send: carried"
+    else
+        SEND_PLAN="send: off"
+    fi
 }
 
 # Row 187: the row 178 proof pair in RUN_CONSOLE. A new pair replaces the pointer's and goes last;
@@ -943,6 +973,7 @@ plan() {
     echo "bus: scripts/bus-service.sh install --copy $TO --copies $COPIES$([ "$RUN_PM" = 0 ] || echo ' --pm') --claude $P_CLAUDE"
     [ -z "$DROP_TESTER" ] || echo "drop $DROP_TESTER; the target Console does not support it"
     echo "$PROOF_PLAN"
+    echo "$SEND_PLAN"
     echo "Console: scripts/webui-service.sh install --copy $TO --copies $COPIES${RUN_CONSOLE[*]:+ ${RUN_CONSOLE[*]}}"
     echo "CLI: scripts/stack-copy.sh wrapper $TO --copies $COPIES --bin $BIN"
     local r
@@ -956,6 +987,7 @@ run_steps() {
     capture || refuse capture-failed "could not write the rollback set $RS; nothing was stopped"
     [ -z "$DROP_TESTER" ] || say "drop $DROP_TESTER; the target Console does not support it"
     [ -z "$PROOF_STEP" ] || say "$PROOF_STEP"
+    [ -z "$SEND_STEP" ] || say "$SEND_STEP"
     trap 'after_fail signal' INT TERM HUP
     stop_both || rollback_in_run stop-timeout
     if [ -e "$STORE" ]; then
@@ -1478,7 +1510,7 @@ STORE="$DATA/bus/bus.sqlite"
 BUS_UNIT="mosaic-bus@$BUSINESS.service"
 FROM="" TO="" ACT="" RS="" POST="" BACKUP="" TAKEN="" RESTORED="" STEPS="" COUNT="" UNCLEAN="" FAIL=""
 STORE_SCHEMA="" START_EPOCH="" START_MS=0 GATE="" GATE_WHY="" S_CHANGED=""
-P_COPY="" P_PM=0 P_PENDING=0 P_SCHEMA="" P_CLAUDE="" P_CONSOLE=() RUN_PM=0 RUN_PENDING=0 RUN_CONSOLE=() DROP_TESTER="" PROOF_PLAN="" PROOF_STEP="" PLAN_REFUSE=()
+P_COPY="" P_PM=0 P_PENDING=0 P_SCHEMA="" P_CLAUDE="" P_CONSOLE=() RUN_PM=0 RUN_PENDING=0 RUN_CONSOLE=() DROP_TESTER="" PROOF_PLAN="" PROOF_STEP="" SEND_PLAN="" SEND_STEP="" PLAN_REFUSE=()
 R="" R_RC=0 R_EARLY=() R_BK="" R_HOST_PID="" R_CONSOLE_PID="" R_STARTED="" LIVE_CFG="" LIVE_BIZ=""
 case "$OP" in
     adopt) do_adopt ;;