row 251: BUILD.md predicts part A's reds on e5e4b2e5a and records no rebase onto 6096b051b (sage-2084)

ssh-agent sets a key's death to whole seconds of CLOCK_BOOTTIME plus the lifetime and reaps on the
same whole seconds (OpenSSH 10.5p1 ssh-agent.c:1315, :1064, misc.c:1828), so -t 1 can end within
milliseconds of an add made late in a second. -t 2 keeps the key over 1 s; the sleep keeps its 1.5 s
margin past the 2 s ceiling. Both checks stay. host-run.mjs is unchanged: production adds with
timeout + 30. Evidence and the slot plan are in agents/darkwing/work/queue-251/BUILD.md.

AGENTS.md

@@ -25,10 +25,15 @@ green at every step. Not production software — a proven foundation.
 1. **Root is bootstrap-only.** First-class system configuration lives at the
    repository root; everything else gets a dedicated directory (`roles/`,
    `contracts/`, `missions/`, `tasks/`, `docs/`). Do not add new files to root.
-2. **Configuration**: `~/.config/mosaic-dev/config.json` is the sole system
-   config — created only by `scripts/bootstrap.sh`, never overwritten,
-   fail-closed on any problem. Repo-scoped role authority lives in
-   `roles/*.json` (versioned, reviewed commits only).
+2. **Configuration**: each stack instance has exactly one system config. The
+   default instance's is `~/.config/mosaic-dev/config.json`. Instance NAME's
+   is `~/.config/mosaic-NAME/config.json`, and its data root carries a marker
+   that names it. `~` is the home of the OS user that runs the instance. A
+   process reads only the config `MOSAIC_CONFIG` names, or the default's when
+   that is unset. Configs are created only by
+   `scripts/bootstrap.sh [--instance NAME]`, never overwritten, fail-closed on
+   any problem. Repo-scoped role authority lives in `roles/*.json`
+   (versioned, reviewed commits only).
 3. **Secrets** never enter the repository or container images; auth is
    runtime-only (read-only mount or environment variable).
 4. **Contracts** (`contracts/`) are immutable and image-baked. Missions and
@@ -177,8 +182,8 @@ Full reference — usage, fields, exit codes, safety notes:
 
 ## Data map (canon)
 
-- `~/.config/mosaic-dev/config.json` — system config (user-authored; never
-  auto-written).
+- `~/.config/mosaic-dev/config.json`, or `~/.config/mosaic-NAME/config.json`
+  per named instance: system config (user-authored; never auto-written).
 - `<dataRoot>` (from config; default `~/.mosaic-dev`):
   - `runs/` — write-once run evidence (`result.json`, snapshots, `stderr.txt`)
   - `sessions/` — pi JSONL session trees, one directory per named session

BUILD-LOG.md

@@ -5174,3 +5174,6 @@ Before: managed project/thread verbs had no Console conversation area. After: fi
 2026-10-20 04:44:54 UTC | Row 178 round 2 preparation | Before: Dewey C1 five render guards lacked killing tests. Added independent refusal fixtures, a temporary uid+1 id stub with cleanup, and empty loopback proof case; activation ordering recorded in r2 BUILD. Product unchanged; syntax/text preflight only, no test or mutant execution. Pending row 181 rebase and Sage slot.
 
 2026-10-20 05:10:34 UTC | Row 178 #1676 round 2 verified | Before: C1 render refusals lacked killing tests and row 181 base was pending. Rebased onto 931651f2d, kept all COUNTED/count code and tests, appended T178 tail; added independent owner/collision/absolute/charset/header and empty-loopback proof tests. Four files singly 156/156, all 24 mutants killed, metadata and sandbox fixture probes pass; scratch sweep empty. Packet agents/rocko/work/queue-178/r2/, candidate 9300a670, inventory d0dcde7b (59/59), scan 58 files no findings; in-review revs 2166-2167, expected no-token request failure. No live actions or commits.
+2026-10-21T01:28:05Z | Darkwing | row 232 #1734 installer I1 build, round 1 in review | Before: stack-release.sh managed only user units (systemctl --user), and stack-copy.sh had no bundle copy. After: --units external (adopt, activate, rollback --to, status, confirm, revert, gate --since, AWAITING-UNITS, stale-start, external-pm, --plan --expect-from) and stack-copy check --units external, copy --bundle FILE SHA, wrapper ID --create; user mode byte-identical to the base by test. First build 0af0c73c6 on 00d4cc1f6; rebased onto row 200 (cb5fdb064) as a0ffabc3f on darkwing/row232-r1; --sso refused under external (D9), row 200 config_checks run under external (D10). Gate on Sage's slot (sage-1618): cli 561/0, every scripts/test-*.sh green; 17/17 mutants killed. Results commit 84f1a91e6 (pushed, seat branch only). Manifest 7a3b4ea1 (9 paths), queue revs 2595-2596, request comment 29825, reviewer Filbert. Packet agents/darkwing/work/queue-232/BUILD.md.
+2026-10-21T04:50:44Z | Darkwing | row 233 #1735 installer I3 build, round 1 in review | Before: root had no upgrade driver for root-owned units and no host run sheet; stack-release.sh had no rehearse --backup last and no external plan refusals. After: scripts/stack-upgrade.sh upgrade and rollback (r6 A1-A5, A2f, R1-R4) with 20 tests, docs/guides/host-run-sheet.md, TOOLS.md lines, and on Sage's rulings stack-release.sh --backup last, BACKUP_STORE and the --plan refusals open-activation and migrate-required (3 tests). Base e65a3ab4d (row 232's landing). Gate on Sage's slot (sage-1704) on d99166ade: cli 616/0, every scripts/test-*.sh green, 1201/0 summed by awk; m1-m8 8/8 killed. Correction: the process sweep after the gate found an orphaned sleep 60 from the lock test's flock holder (N1); 08db6ac3f fixes it test only, Sage ruled the gate stands (sage-1707), rerun c0 20/0 and m1 killed with 0 left (sage-1708). Tip 1a1dc80ca (pushed, seat branch only). Manifest 464ce9eb (7 paths), queue revs 2644 and 2647, request comment 29901, reviewer Filbert. Packet agents/darkwing/work/queue-233/BUILD.md.
+2026-10-21T06:37:41Z | Darkwing | row 240 #1746 installer I4 build, round 1 in review | Before: root had no host check for the bwrap AppArmor profile, its pins or a boot unit, and stack-upgrade.sh exited 1 args-failed when the args move after A5 failed, while exit 1 means the old copy runs. After: scripts/case1-hostcheck.sh (seven items, --check, --enforce, --upstream), scripts/case1-pins.sh, mosaic-hostcheck.service and 16 tests; the args move failure exits 5 args-failed, documented in TOOLS.md and run sheet section 6 and tested; run sheet section 3 puts the pinned npm on PATH and names the bin/claude.exe --claude path; sections 8 and 10 have precheck lines. Verification: slot run r1 on 47ec9fe2f failed at the singles (the new N1 test's after hook threw ENOENT after the fixture cleanup removed the root); b45852daa drops the hook; r2 on b45852daa green: singles 16/0 and 21/0, c0 plus M1-M8 8/8 killed, cli 639/0, scripts 585/0. Candidate darkwing/row240-r3 ad1b23ab2 on c771a36f4, manifest 573ece95 (9 paths), revs 2694 and 2695, comment 29943.

adapters/README.md

@@ -75,7 +75,8 @@ session's workspace and its own process group. Same contract, plus:
 | `MOSAIC_POLICY_FILE`, `MOSAIC_TOOLS_FILE` | The bundle's gate policy and typed tools. |
 | `MOSAIC_TOOL_SOCKET` | The runner's tool socket, which the typed tools call. |
 | `MOSAIC_TURN_MARKER` | `pi`: the extension writes it at `agent_end`; a pi turn that exits 0 without it failed. |
-| `MOSAIC_EXTENSIONS` | `pi` only: extension files loaded with `-e`; a missing one exits 2. |
+| `MOSAIC_EXTENSIONS` | `pi` only: extension files loaded with `-e`; a missing one exits 2. The pi module names two: the gate and typed tools extension, then the unslop check's `tools/unslop-hook/extension.ts` (row 66). |
+| `MOSAIC_UNSLOP_LOG` | The unslop check's JSONL log, `<run>/unslop.jsonl`, which the runner sets for both adapters and reads after each turn (row 66). |
 | `MOSAIC_CLAUDE_SETTINGS`, `MOSAIC_CLAUDE_MCP_CONFIG` | `claude` only: the bundle's gate hook and MCP server; required. |
 | `MOSAIC_THINKING` | The route's thinking level (row 65), which the harness module's `levels()` already checked. `pi` passes `--thinking` (`off`, `minimal`, `low`, `medium`, `high`, `xhigh`, `max`) and omits it when unset, as for `run-task.sh` workers. `claude` passes `--effort` (`low`, `medium`, `high`, `xhigh`, `max`) and requires it; unset exits 2. |
 | `MOSAIC_CLAUDE_BIN` | `claude` only: absolute path of the CLI to run, from the host's environment (the bus unit pins it). Unset or empty runs `claude` from `PATH`; a relative path or a non-executable file exits 2. |
@@ -86,7 +87,8 @@ The layers each adapter relies on, and what they don't cover, are in
 ### A role's skills (row 64)
 
 A managed session's skills reach both adapters as text in the bundle's
-`prompt.md`, which they pass with `--system-prompt`. Neither adapter loads a
+`prompt.md`, which they pass as a file: `pi` with `--system-prompt <path>`
+and `claude` with `--system-prompt-file <path>` (row 213). Neither adapter loads a
 skill of its own: `pi` keeps `--no-skills`, since role sessions never get
 `MOSAIC_SKILLS`, and `claude` keeps `--disable-slash-commands` and
 `--restricted`. Sage chose this on 2026-10-19 from a probe, recorded in
@@ -104,5 +106,23 @@ skill of its own: `pi` keeps `--no-skills`, since role sessions never get
 
 The cost is prompt size: a role's skill text is in every turn, where the
 other routes load a skill when it's used. The bundle caps a role's skills at
-64 KiB together, since `claude` passes `prompt.md` as one argument and Linux
-caps one argument at 128 KiB.
+64 KiB together. The cap dates from when `claude` passed `prompt.md` as one
+argument, which Linux caps at 128 KiB; row 213 passes the file instead, so no
+local user reads the prompt in `/proc/<pid>/cmdline`. Pi 0.85.1 uses the path
+string itself as the prompt when the file is missing or can't be read, so the
+pi adapter exits 2 unless the path is a readable regular file.
+
+### The unslop check (row 66)
+
+Both adapters run the mechanical writing check from `tools/unslop-hook`,
+driven by one `lists.json`. `pi` loads it as its second `-e` extension.
+`claude` runs `claude-hook.js` from the bundle's `settings.json`: the Stop
+hook checks the turn's replies, and the UserPromptSubmit hook adds the
+correction notice as context on the next turn when the last reply had
+tells. Each hook command ends `; exit 0`, so neither blocks. Both log to
+`MOSAIC_UNSLOP_LOG`, and the runner adds a note for the operator to the
+next RESULT it sends (`packages/harness/README.md`, the runner). The
+harness modules mount the three files read-only at their own paths, and
+the manifest records their digests. `MOSAIC_UNSLOP_HOOK` and `UNSLOP_LISTS`
+aren't in the session environment's allowlist, so a managed session can't
+switch the check off or swap its lists.

adapters/claude/adapter.sh

@@ -27,6 +27,11 @@ need MOSAIC_CLAUDE_MCP_CONFIG
 for f in "$MOSAIC_SYSTEM_PROMPT_FILE" "$MOSAIC_CLAUDE_SETTINGS" "$MOSAIC_CLAUDE_MCP_CONFIG"; do
     [ -r "$f" ] || { echo "claude adapter: not readable: $f" >&2; exit 2; }
 done
+PROMPT_FILE=$MOSAIC_SYSTEM_PROMPT_FILE
+case "$PROMPT_FILE" in
+    /*) ;;
+    *) PROMPT_FILE="$(pwd)/$PROMPT_FILE" ;;
+esac
 [ "${MOSAIC_INTERACTIVE:-}" != "1" ] || { echo "claude adapter: interactive mode isn't supported" >&2; exit 2; }
 CLAUDE=claude
 if [ -n "${MOSAIC_CLAUDE_BIN:-}" ]; then
@@ -56,7 +61,10 @@ fi
 # Flags:
 #   -p                       one-shot: print the answer and exit
 #   --output-format text     stdout is the answer only
-#   --system-prompt          the generated prompt replaces the default
+#   --system-prompt-file     the generated prompt replaces the default, given
+#                            as a file so no local user reads it in
+#                            /proc/<pid>/cmdline (row 213); absolute, since
+#                            the cd above changed the working directory
 #   --effort                 the instance's thinking var (row 65; 2.1.302 takes
 #                            low, medium, high, xhigh, max)
 #   --restricted             no user/project/local settings files; --settings
@@ -76,10 +84,9 @@ fi
 #                            text in the system prompt (row 64)
 ALLOWED=mcp__mosaic
 [ -z "${MOSAIC_TOOLS:-}" ] || ALLOWED="$MOSAIC_TOOLS,mcp__mosaic"
-PROMPT_CONTENT="$(cat "$MOSAIC_SYSTEM_PROMPT_FILE")"
 "$CLAUDE" -p "$MOSAIC_REQUEST" \
     --output-format text \
-    --system-prompt "$PROMPT_CONTENT" \
+    --system-prompt-file "$PROMPT_FILE" \
     --model "$MOSAIC_MODEL" \
     --effort "$MOSAIC_THINKING" \
     --restricted \

adapters/pi/adapter.sh

@@ -8,7 +8,17 @@
 set -eu
 
 [ -n "${MOSAIC_SYSTEM_PROMPT_FILE:-}" ] || { echo "pi adapter: MOSAIC_SYSTEM_PROMPT_FILE is required" >&2; exit 2; }
-[ -r "$MOSAIC_SYSTEM_PROMPT_FILE" ] || { echo "pi adapter: system prompt not readable: $MOSAIC_SYSTEM_PROMPT_FILE" >&2; exit 2; }
+# Row 213 (C2-08): pi gets the prompt as a path, so no local user reads it in /proc/<pid>/cmdline.
+# Pi 0.85.1 reads --system-prompt as a file only when the path exists and reads, and otherwise
+# uses the path string itself as the prompt, without a warning for a missing file
+# (dist/core/resource-loader.js resolvePromptInput). So the path must be a regular readable
+# file here, and is made absolute before the cd below, since pi resolves it from its own cwd.
+PROMPT_FILE=$MOSAIC_SYSTEM_PROMPT_FILE
+case "$PROMPT_FILE" in
+    /*) ;;
+    *) PROMPT_FILE="$(pwd)/$PROMPT_FILE" ;;
+esac
+[ -f "$PROMPT_FILE" ] && [ -r "$PROMPT_FILE" ] || { echo "pi adapter: system prompt not readable: $MOSAIC_SYSTEM_PROMPT_FILE" >&2; exit 2; }
 # MOSAIC_AGENT_NAME is optional in headless mode (identity section is then
 # omitted); interactive launches always set it via scripts/agent.sh.
 
@@ -94,7 +104,8 @@ fi
 # All flags documented in the pi package README (CLI Reference):
 #   -p/--print     one-shot mode: print the response and exit (omitted in
 #                  interactive TUI mode)
-#   --system-prompt  replace the default prompt with the generated one
+#   --system-prompt  replace the default prompt with the generated one, given
+#                  as the file's absolute path (checked above), never its text
 #   --no-*         no ambient context/skills/extensions/templates/themes
 #   EXT_FLAGS      the explicitly provided extensions only (-e)
 #   SESSION_FLAGS  ephemeral | persistent | forked (per env)
@@ -103,7 +114,6 @@ fi
 #   --offline      no startup network operations (update checks/telemetry)
 #   --no-approve   ignore project-local .pi/ files (settings, SYSTEM.md)
 #                  whatever trust is saved for the workspace
-PROMPT_CONTENT="$(cat "$MOSAIC_SYSTEM_PROMPT_FILE")"
 set -- \
     --offline \
     --no-approve \
@@ -118,7 +128,7 @@ set -- \
     --provider "$PI_PROVIDER" \
     --model "$PI_MODEL" \
     $THINKING_FLAG \
-    --system-prompt "$PROMPT_CONTENT"
+    --system-prompt "$PROMPT_FILE"
 # One-shot mode appends -p and the request (both safely quoted);
 # interactive mode appends nothing - clean TUI.
 [ "$INTERACTIVE" = "1" ] || set -- "$@" -p "$MOSAIC_REQUEST"

agents/README.md

@@ -19,6 +19,12 @@ not fleet seats. Keep changes in `/mnt/storage/src/mosaic-stack`; do not modify
 | 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` |

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/darkwing/work/queue-195/BUILD.md

@@ -0,0 +1,161 @@
+# Row 195 build: `scripts/case1-accept.sh`
+
+Row 195 (#1693), the Case 1 install on 10.1.1.53. Design r7 at 5425ea2f3, approved by Duckworth
+(duckworth-0087, `agents/duckworth/work/row195/REVIEW-r7.md` at 58d930f89; Gitea 29962). Sage's go to build
+is sage-1817.
+
+## What this commit holds
+
+- `scripts/case1-accept.sh` (new, 100755): section 5's acceptance, F1-F11 and P1-P11.
+- `packages/cli/tests/case1-accept.test.mjs` (new): section 5's cases.
+- `docs/TOOLS.md`: the `case1-accept.sh` entry after the hostcheck entry.
+- This file.
+- `DESIGN.md`, doc-only fixes Sage named in sage-1817, with no new design round:
+  - Duckworth's N1. Section 1's human-id row cited `broker.mjs:245`; the check is `broker.mjs:321`.
+  - Row 226's state at :21 and :326. It said "unclaimed"; 226 is assigned to Gosalyn, briefed and not
+    started (sage-1814).
+  - :340 said I'd send the section 6 items to Gosalyn once 226 was claimed. I sent them on 2026-10-21
+    and Gosalyn acknowledged (gosalyn-0085), so the line now says that.
+
+Nothing else changes. No `case2-*.sh`, `stack-upgrade.sh`, `stack-release.sh`, `case1-hostcheck.sh` or run
+sheet edit, and nothing touches .53 (sage-1809).
+
+## Deviations from section 5, and choices it left open
+
+1. P4's mark is the single token `accepted Q182+Q183`. Section 5 lists `accepted Q182` and `accepted
+   Q183` as marks and gives P4 both. One line can carry one mark, and P4 is the only Q182 path, so the
+   count list has `accepted Q182+Q183` in place of `accepted Q182`.
+2. The test seam replaces `getent`. Under `--root`, the script reads `DIR/etc/passwd` and `DIR/etc/group`
+   with awk. Without it, the same helper calls `getent`. The groups of a user are its primary gid, then
+   each group whose member list names it, which is what `id -G` prints. So there is no fake `id`, and
+   the script never calls `id` for another user.
+3. P10 reads the port floor from `/proc/sys/net/ipv4/ip_unprivileged_port_start` rather than calling
+   `sysctl`, so the seam covers it the way hostcheck's item 7 is covered. There is no fake `sysctl`.
+4. There is no fake `bwrap`, `claude`, `node` or `hostcheck.sh` on PATH. The script runs each by the
+   absolute path the args file or the install names, so the test puts stubs at those paths under
+   `--root`, and the fake `sudo` runs the stack's user's commands from the tree.
+5. The args file must say `--profile factory` and name `--business`. Both are new refusals beyond
+   `stack-upgrade.sh`'s rules. A library file, or one for another business, would make F4 and F7
+   check the wrong thing. After `--`, `--port` and `--tester-port` must be numeric. The args file is the
+   only source of the ports.
+6. F8, F9 and F11 read file metadata as root: `stat`, `-L` and `find -maxdepth 1 -name '*.json'`. None
+   opens the credential. F9 parses `managed-settings.json` with the pinned node, run by root: that node
+   and that file are both root's own, installed by ops-01.
+7. F7 reads `launch.by` from `$HOME/.config/mosaic-dev/businesses/<id>.json` as the stack's user. That
+   path is `businessFilePath(id)` under the default config, which is what the unit uses. It doesn't load
+   the copy's `business.mjs` as `stack-release.sh`'s `plugins launchby` does. The user runs the whole
+   check and prints one line, and root accepts only `ok <instance> run <run>` (sage-1653: root doesn't
+   parse the user's output beyond a fixed pattern).
+8. F5 names a process claude when its argv0's basename or its `comm` starts with `claude`. The window
+   confirms this against a real role session. If the bwrap'd claude shows another name, F5 fails closed
+   and the fix is this match, not the label check.
+9. F3 and F5 run together. `talk` goes out in the background under `timeout 330`, and the `/proc` scan
+   repeats every half second until it finds a labelled pair or `talk` exits. F3's line prints first, then
+   F4, then F5, so the output keeps id order. F3 passes on exit 0 with the `sent` line and a reply line,
+   both counted on stdout only (`cli.mjs:395` and the `formatMessage` write); talk's error goes to stderr.
+12. `--claude` must match `^/[A-Za-z0-9/._+@-]+$`. The `@` is for `node_modules/@anthropic-ai/...`;
+    `stack-upgrade.sh` doesn't check `--claude` at all.
+10. F1 requires all four uids in `/proc/<MainPID>/status` (real, effective, saved, filesystem) to be the
+    user's.
+11. Evidence text the stack's user controls (talk's last line, the precheck's last line, F6's and F10's
+    `--version`) is cut to printable ASCII, one line, 200 bytes.
+
+## Tests
+
+`packages/cli/tests/case1-accept.test.mjs`, 22 tests. Every case builds a scratch host with every F check
+passing and every P check closed or accepted, then changes one thing:
+- all pass: exit 0, ids in order, each P mark, the count lines match the check lines, and the stand-in
+  credential's value appears nowhere;
+- each F check failing alone exits 1 with only its line failing;
+- F3 on exit 0 with only the `sent` line, and its evidence taking talk's stderr;
+- F1 on a failed unit and on `User=root`; F2 on healthz failing and on another pid holding the port;
+- F5 on `unpriv_bwrap (enforce)`, `bwrap//&unpriv_bwrap (complain)`, a trailing space on either label,
+  no bwrap of the user's, and passing on `comm` alone;
+- F6 on a stub that prints nothing and on a path outside `claude-<pin>`;
+- F7 on two live PM launches, a live one for another business, and no `launch.by`;
+- F8 on 0640, on another owner and on a symlink, never printing the credential;
+- F9 on a group-writable mode, another owner and a number for the flag;
+- F11 on one `*.json` under `discord/`, and passing on an empty directory;
+- each P check's unnamed mark, with the line count each fault makes: P6 one line per member, P9 one per
+  missing item; P2, P5, P10 and P11 in more than one way;
+- every P check unnamed at once still exits 0;
+- nine bad args files refuse with exit 2 before any command runs, each with its own refusal text;
+- usage errors, and a user's run without `--root`, exit 2;
+- every in-instance call goes through `sudo -u mosaic -H env PATH=<node dir>:/usr/local/bin:/usr/bin:/bin`,
+  read from the fake `sudo`'s argv, and root's other `sudo` calls are exactly `-l -U mosaic`,
+  `-l -U localadmin` and the jarvis bwrap probe;
+- the host check records `--check` and never `--enforce`.
+
+## Mutants
+
+Section 5's twelve, each one exact replacement in `scripts/case1-accept.sh`, run by
+`/mnt/storage/scratch/darkwing-195-out/mutants.py` in Sage's slot (sage-1865). All twelve were killed.
+After each one the script's bytes were restored, and the final sha256 matched (`d434f15ff638...`). The
+killers below are the tests that failed in each mutant's saved log.
+
+| # | Mutant | Killed by |
+|---|---|---|
+| 1 | F1 passes on a MainPID owned by root | each F alone |
+| 2 | F2 accepts a listener on 0.0.0.0 | each F alone |
+| 3 | F3 passes without a reply | each F alone; F3 exit 0 with no reply line |
+| 4 | F5 matches a substring | F5 labels (the trailing space) |
+| 5 | F6 skips the `--version` check | each F alone; F6 stub and path |
+| 6 | F8 skips the owner check | F8 0640, owner and symlink |
+| 7 | F11 ignores `discord/` | each F alone; F11 `*.json` |
+| 8 | P1 closes on any output | P unnamed; every P unnamed |
+| 9 | P5 maps to `closed` with jarvis in docker | P unnamed; every P unnamed; P2 and P5 names docker |
+| 10 | P9 drops the jarvis item | P unnamed; P9 per item |
+| 11 | P11 accepts any `Before=` | P unnamed; every P unnamed |
+| 12 | a P check's `unnamed` sets the exit to 1 | P unnamed; every P unnamed; P10 and P11; P2 and P5; P9 per item |
+
+Mutant 1 survived the F1 variants test (a failed unit, `User=root`), because those faults fail F1 on the
+unit's state and `User=`, not on the uid line. Each F alone covers the uid line.
+
+## Pre-slot read review
+
+Since every test run is slot work, a read-only subagent traced each case through the script before the
+first slot run, executing nothing. It found four defects, all fixed in this commit:
+- The `--claude` regex had no `@`, so every run refused the args file, the real .53 one included.
+- The fake `stat` logged the args-file call, so the bad-args test's "no command ran" check would fail.
+- The P5 and P6 faults each rewrote `etc/group` from the constant, so applying both lost P5's change.
+- F3 counted stderr into its line count, so a mutant dropping the exit check survived. F3 now counts
+  stdout only, and a `sent`-only case covers the line count.
+
+## Run environment
+
+The build commit ddf7dce6c sits on base 4ced5e63d (origin/refactor when it was pushed). It was first built
+on c515273db as 4a51d392c. Row 238 then changed `docs/TOOLS.md`, so I cherry-picked the three commits onto
+4ced5e63d as `darkwing/row195-b`. `git range-diff` shows all three identical. node v26.8.1 on dragon-lin,
+every run behind my busy check and Sage's, chained with `&&`.
+
+- Step 1, sage-1829 (07:41:54Z to 07:42:05Z), TMPDIR `/tmp/dw195`:
+  `node --test packages/cli/tests/case1-accept.test.mjs`, 22 pass, 0 fail, 11.0 s.
+- Step 2, sage-1865 (08:34:27Z to 08:36:21Z), TMPDIR `/mnt/storage/scratch/tmp/r195`: the twelve mutants
+  above, all killed.
+- Step 3, the gate (08:36:21Z to 08:47:06Z), same TMPDIR, `COMPOSE_PROJECT_NAME=darkwing-r195`:
+
+| Suite | Result |
+|---|---|
+| packages/cli (`node --test tests/*.test.mjs`) | 662 pass, 0 fail, 0 skipped |
+| test-auth.sh | 15 passed, 0 failed |
+| test-conductor.sh | 17 passed, 0 failed |
+| test-config.sh | 31 passed, 0 failed |
+| test-discord.sh | 78 passed, 0 failed |
+| test-extension-package.sh | 18 passed, 0 failed |
+| test-foundation.sh | 44 passed, 0 failed |
+| test-land-work.sh | 86 passed, 0 failed |
+| test-queue.sh | 156 node pass, 0 fail; 28 passed, 0 failed |
+| test-release.sh | 14 passed, 0 failed |
+| test-task.sh | 98 passed, 0 failed |
+
+Summed: 818 node tests passed with 0 failed, and 429 selftests passed with 0 failed. The compose network
+was removed afterwards, and the sweep found no process left in the worktree, the output directory or the
+TMPDIR. This file's results are a doc-only commit on top of the build, so nothing that ran has changed.
+
+## Correction to deviation 6 (follow-up, 2026-10-21)
+
+Deviation 6 says the node F9 runs is root's own. At 37171f65b the script didn't check that. F9 ran
+`--node` as root before F10's path check, so the header's "root itself only reads" was false
+(Duckworth's N1, `agents/duckworth/work/row195/REVIEW-m1.md` at 6afcee2a5). A host installed as designed
+was safe, because `case2-unit.sh` refused a non-root-owned `--node`. Row 245 carries the fix and its
+tests: `agents/darkwing/work/queue-245/BUILD.md`.

agents/darkwing/work/queue-195/DESIGN.md

@@ -0,0 +1,388 @@
+# Row 195 design: the Case 1 install on 10.1.1.53 (r7)
+
+Darkwing, 2026-10-21. Brief: `docs/plans/2026-10-20_hub-own-uid.md`, blob 45be7f09afc1, section "Brief: the
+Case 1 install on 10.1.1.53 (row 195)". Gitea #1693. Reviewer Duckworth, gate owner Sage. Branch
+`darkwing/row195-r7` on c515273db. r6 (b7239bb66 on `darkwing/row195`, approved duckworth-0055) is the base,
+carried unchanged as 7398b7dd7. The r6 text is in that commit and in b7239bb66.
+
+## Changes from r6
+
+Q187 (mos-1108) made install and upgrade product commands, and mos-1118 split r6 into the installer rows
+(`docs/plans/2026-10-20_installer-rows.md`). That brief says row 195 "shrinks to the factory profile's
+values and the Case 1 acceptance". So r7 is mostly a cut. What r6 designed now ships elsewhere:
+
+| r6 piece | Now | State |
+|---|---|---|
+| `stack-release.sh --units external`: `confirm`, `revert`, `gate`, `rollback --to`, external `adopt` and `status`; `stack-copy.sh check --units external` and bundle copies | row 232, I1 | landed |
+| `case1-repin.sh` (A1-A5, A2f, R1-R4) | `scripts/stack-upgrade.sh`, row 233, I3 | landed |
+| the host steps 2a, 2a', 2a'' and the window's root steps | `docs/guides/host-run-sheet.md` sections 1-10, row 233 | landed |
+| `case1-hostcheck.sh`, `case1-pins.sh`, `mosaic-hostcheck.service` (the drift stop, r6 B2) | row 240, I4 | landed c515273db |
+| the unit render, `--profile factory`, `--pm`, `--claude`, the factory serve flags, the precheck | row 230, C2-13a, I2 | landed |
+| the install as `mosaic`: bootstrap, business file, copy | row 226, C2-13b, I2, `scripts/case2-install.sh` | assigned to Gosalyn, briefed, not started |
+| `docs/guides/case1-install.md` | the host run sheet, plus section 6 of this file | |
+
+Other changes:
+
+- Claude moves under `/opt` (sage-1522, run sheet section 3). `--claude` is
+  `/opt/mosaic-stack/claude-<pin>/node_modules/@anthropic-ai/claude-code/bin/claude.exe`, root's, and root
+  installs and upgrades it. r6's `/srv/mosaic/.local/bin/claude` is gone. F6 reads the new path.
+- The args file is `/etc/mosaic-stack/dev.args` (run sheet section 7), not `case1-unit.args`. It holds
+  `--copy` too, and `stack-upgrade.sh` rewrites only that line, after confirm passes.
+- Both units are `WantedBy=multi-user.target` and start at boot (Q189, mos-1122). r6's "the Console has no
+  `[Install]`, root starts it by hand after a reboot" no longer holds.
+- The business id is stated, with the DEFERRED 240 N1 reasoning (sage-1809, sage-1813). Section 7.
+- The window can't run until row 226 lands. Sage added 226 to row 195's after list at rev 2718
+  (sage-1813). Section 6 lists what row 195 needs from 226's install.
+- The acceptance runs as root through ops-01, not as `localadmin`. `aa-status`, `sudo -l -U`,
+  `systemd-run --uid` and the hostcheck all need root. It gains four functional checks for items the run
+  sheet marks "precheck line missing" (F8-F11) and one host line (P11). Section 5.
+- The Discord row in section 2 changed. The precheck's "no Discord binding" line is C2-13b's and is
+  library-only, so for the factory it's F11 in the acceptance.
+
+What row 195 still builds: `scripts/case1-accept.sh` and its test (section 5). The rest of this file is
+inputs, the window order and the record the reviewer checks.
+
+## 0. What I checked on the host
+
+Read only, as `localadmin` over ssh, 2026-10-20 between 20:40Z and 21:51Z. Nothing in r7 touched .53
+(sage-1809). The window's first step re-reads these, since they can drift in a day: unattended-upgrades
+runs daily.
+
+| Item | 10.1.1.53 on 2026-10-20 | Needed |
+|---|---|---|
+| OS | Ubuntu 24.04.5, kernel 6.8.0-124, x86_64, 12 cores, 94 GiB, 217 GiB free on `/` | fits |
+| `mosaic` user, group, `/srv/mosaic` | absent | run sheet section 1 |
+| node | `/usr/local/bin/node` v22.22.2, root-owned | 24 or later, under `/opt` (run sheet section 2) |
+| claude | not on localadmin's PATH | under `/opt` (run sheet section 3) |
+| bwrap | absent; apt candidate `bubblewrap 0.9.0-1ubuntu0.3` | run sheet section 4 |
+| user namespaces | `kernel.apparmor_restrict_unprivileged_userns = 1`, apparmor 4.0.1, no bwrap profile loaded | run sheet section 4 |
+| profiles that name bwrap | none (`grep -rlw bwrap /etc/apparmor.d` exits 1) | hostcheck item 3 |
+| `fs.protected_hardlinks` | 1 | hostcheck item 6 |
+| `net.ipv4.ip_unprivileged_port_start` | 1024 | run sheet section 5 |
+| listeners below 1024 | 22 (sshd) and 53 (the resolver); 732 is free | the Console's port |
+| ports 7330-7333 | free | 7333 is the tester port |
+| `localadmin` | NOPASSWD sudo (#423 step 1, mos-1066, mos-1077) | ops-01's root path |
+| `jarvis` | groups sudo, docker, lxd, adm | #423 step 4 removes them (P5) |
+| unattended-upgrades | on, with the security pocket, which carries bubblewrap | the drift stop (row 240) |
+| journald | `SplitMode=uid` | the PM check reads `launches list`, not the journal (row 232) |
+
+## 1. The factory profile's values
+
+Instance `dev`, row 190's default (mos-1118 choice 4). `~` is `mosaic`'s home.
+
+| Input | Value | Who gives it |
+|---|---|---|
+| user | `mosaic`, primary group `mosaic` with no other member | fixed |
+| home | `/srv/mosaic`, 0700 | fixed |
+| config dir | `/srv/mosaic/.config/mosaic-dev` | row 190 |
+| data root | `/srv/mosaic/.mosaic-dev`, marker `{"instanceVersion":1,"name":"dev"}` | row 190 |
+| business | `mosaic-stack`, file `<configDir>/businesses/mosaic-stack.json` | fixed (section 7) |
+| profile | `factory` for `case2-install.sh`, `case2-unit.sh` and `case2-precheck.sh` | fixed |
+| roles | the factory set from `roles/`, with a chief that has a harness var | the go names the set (section 2) |
+| human id | Jason's, not `tester` (`broker.mjs:321`) | the go |
+| model credential | `<configDir>/secrets/claude-session.env`, `mosaic` 0600, one line `CLAUDE_CODE_OAUTH_TOKEN=...` | Jason places it (section 3) |
+| token slot path | none | section 2 |
+| node | `/opt/mosaic-stack/node-<v>/bin/node`, `<v>` 24 or later | the go names `<v>` and its sha256 |
+| claude | `/opt/mosaic-stack/claude-<pin>/node_modules/@anthropic-ai/claude-code/bin/claude.exe`, `<pin>` 2.1.304 unless the go names a newer one | the go |
+| PM | on (`--pm`) | fixed |
+| Console | `--port 732` on 127.0.0.1, with the unit's `CAP_NET_BIND_SERVICE` | fixed |
+| tester | `--tester-port 7333` on 127.0.0.1 (P10) | fixed |
+| board | none | fixed |
+| release | a git bundle of `refs/heads/refactor` and the 40-hex commit (run sheet section 6) | the go names both and the bundle's sha256 |
+
+The args file. `/etc/mosaic-stack/dev.args`, `root:root` 0644, one argument per line (run sheet section 7):
+
+```
+--profile
+factory
+--user
+mosaic
+--home
+/srv/mosaic
+--business
+mosaic-stack
+--copy
+<40-hex commit>
+--node
+/opt/mosaic-stack/node-<v>/bin/node
+--claude
+/opt/mosaic-stack/claude-<pin>/node_modules/@anthropic-ai/claude-code/bin/claude.exe
+--pm
+--
+--port
+732
+--business
+mosaic-stack
+--tester-port
+7333
+```
+
+`case2-unit.sh` takes exactly these before `--` (`scripts/case2-unit.sh:54`), and `stack-upgrade.sh`
+refuses `args-unreadable` on anything else (`scripts/stack-upgrade.sh:126-148`). The factory profile
+refuses the preview trio, `--send` and the proof pair (`case2-unit.sh:169`). .53 has no proxy, and Jason
+reaches the Console with `ssh -L` (sage-1451 Q3). Changing a serve flag is a re-install with its own go,
+not an upgrade.
+
+Why the port is 732 (r6, mos-1101 item 5). Role sessions share the host's network namespace
+(`packages/seat/src/sandbox.mjs:67`), so while the Console is down a session could bind a port above the
+floor and answer in its place. Below 1024 only the Console unit can bind, through its capability. The
+tester port can't go below 1024 (`packages/webui/src/cli.mjs:33`), so P10 records it.
+
+PATH for `mosaic`'s steps. `sudo -u mosaic -H` resets PATH to sudo's `secure_path`, which finds
+`/usr/local/bin/node`, v22. So every `mosaic` step runs as
+`sudo -u mosaic -H env PATH=/opt/mosaic-stack/node-<v>/bin:/usr/local/bin:/usr/bin:/bin ...`, the list
+`case2-unit.sh` renders as the units' PATH. `stack-upgrade.sh` builds it from the args file's `--node`.
+
+## 2. Where Case 1 differs from Case 2
+
+| Case 2 (library) | Case 1 (factory) | Reason |
+|---|---|---|
+| business file with the library mapping | `mosaic-stack` with no `library` key. The precheck refuses a library project under `factory` (`profile-library-business`, `case2-precheck.sh:127-128`) | the factory has no books repo |
+| `bean`, `chet`, persona vars and files, specialists | the factory roles from `roles/`, with a chief that has a harness var | the go names the set. I haven't read Jason's live business file and won't. The acceptance needs only the chief (F3); a chief with no harness var answers `no-route`. The human adds roles later with `instances.set`, no new row |
+| token slot `library-gitea` | none | the factory's per-agent git identity is row 199's credential store (Megavolt, #1697). Until it lands, git work stays on dragon-lin (Q182) |
+| `bus.tester` off | on; the precheck refuses it off under `factory` (`case2-precheck.sh:135`) | the acceptance and the Q173 test system need the tester |
+| persona modes and digests, `library.sync`, `library.status` | skipped | no persona files, no library (C2-13b brief, `factory` profile) |
+| `ZAI_API_KEY` in `claude-session.env` | not checked; the file holds `CLAUDE_CODE_OAUTH_TOKEN` | no instance has provider `zai` (run sheet section 9) |
+| no Discord binding (C2-13b, library only) | none either. F11 checks that `<dataRoot>/discord/` holds no binding | the factory's connector stays on dragon-lin. Two connectors on one bot token would split its events |
+| the claude marker prompt | runs, since the chief's harness is claude-code | |
+| serve flags: preview trio, `--send`, proof pair | `--port 732`, `--business mosaic-stack`, `--tester-port 7333` | no proxy on .53 |
+| bus: no `--pm`, no `MOSAIC_CLAUDE_BIN` | `--pm`, and `Environment=MOSAIC_CLAUDE_BIN=<--claude>` | the PM dispatches the factory's work; without the path the bus finds no claude on the unit's PATH |
+| Console proof file (run sheet section 9, .54) | none | no proof pair |
+
+All of these are inputs to the landed scripts. Row 230 implemented the four factory items r6 asked for
+(serve flags, `--pm`, `--claude`, row 190's tokens), and nothing in them hardcodes a Case 1 value.
+
+## 3. Model access
+
+Q185: Case 1 uses the account the factory uses today, the Claude subscription behind dragon-lin's
+`claude-session.env`. No script copies that file and none reads its value. In the window, Jason, or the
+person he names under the Q173 secrets rule, makes a credential for .53 from that account and writes it
+to `/srv/mosaic/.config/mosaic-dev/secrets/claude-session.env` as `mosaic`, mode 0600 (run sheet
+section 9). Nobody prints it. The check is `stat -c '%U %a %F' PATH` only (F8).
+
+The bus unit reads it through `EnvironmentFile=-` (`case2-unit.sh:243`). The leading `-` means a missing
+file doesn't stop the bus, so the chief's first launch would fail instead. The window places the file
+before the units start (section 6, W9), and the precheck's claude marker prompt then proves it works
+without printing it.
+
+Quota: the factory on dragon-lin and on .53 share one subscription. Q185's "use existing" accepts that.
+The pi harness stays off on .53 until P19 #383 settles (mos-0865). The business file names claude only.
+
+## 4. Upgrade, rollback and backup on .53
+
+All three are `scripts/stack-upgrade.sh` (row 233), run as root by ops-01 from `/root/mosaic-stack` at the
+reviewed commit. Usage, exits and the step log are in `docs/TOOLS.md`, "Root's upgrade driver", and run
+sheet section 6.
+
+| Action | Command | Who | Go |
+|---|---|---|---|
+| upgrade | `stack-upgrade.sh upgrade --instance dev --bundle /srv/mosaic/incoming/<sha>.bundle --sha <sha>` after run sheet section 6's per-upgrade lines | ops-01 | Mos per run; `--migrate` also needs Jason present (decision 96) |
+| rollback | `stack-upgrade.sh rollback --instance dev --to <copy> [--restore <ACT> [--events N]]` | ops-01 | Mos per run. Mos or Sage picks `<copy>` from `stack-release.sh status mosaic-stack --units external`, read as `mosaic`. The plan refuses unless it is the previous distinct copy |
+| backup of the store | A3's `backup_store` into `<dataRoot>/backups/stack/<ACT>`, inside every upgrade | the driver | the upgrade's |
+| rehearsal | `stack-release.sh rehearse` against the log's newest backup, before anything stops, on `--rehearse-port`, default 7339, which section 0 found free | the driver | the upgrade's |
+| backup of the VM | a PBS backup of VM 1008 before the install window and before any `--migrate` | ops-01 | the window's go (Q182, Q183: agents keep PBS) |
+
+Three .53 specifics:
+
+1. The first upgrade after install needs `--no-rehearsal` in its go. The install's adopt takes no backup,
+   so the log records none, the rehearsal exits 3 (`no-backup`), and the driver goes on only with the
+   flag (`stack-upgrade.sh:323-324`). Every later upgrade refuses the flag (`rehearsal-required`).
+2. Exit 5 (`args-failed`): the new stack is live and confirmed, but `dev.args` still names the old copy.
+   ops-01 moves the file the result line names into place with `mv -f`, and nothing else (run sheet
+   section 6).
+3. Exit 2 leaves both units stopped and the activation open. ops-01 sends Mos the exit and the last
+   lines of `/var/log/mosaic-stack/upgrade-dev.log`, and Jason or Mos settles it with `confirm` or `revert`
+   as on dragon-lin. A unit that doesn't stop within `--timeout` ends here on purpose (A2f's
+   `stale-start`, duckworth-0055 N1, now in run sheet section 6).
+
+The store backup doesn't hold the config dir or the credential. PBS backups of VM 1008 hold the whole disk,
+the credential included (P4). A restore swaps only the store and leaves `claude-session.env` in place.
+
+Re-install, for a serve flag or role change, is not an upgrade. It needs its own go and runs: stop the
+Console, then the bus; rewrite `dev.args` with the same `--copy`; `case2-unit.sh` with it; both units start
+again from the render. Row 230 N1 (webby-0046) holds here: a re-render with the units running leaves each on
+its old copy, so ops-01 stops both first. `stack-upgrade.sh` already stops both before it renders.
+
+## 5. Acceptance: `scripts/case1-accept.sh`
+
+New in this row. ops-01 runs it as root on .53, from `/root/mosaic-stack`:
+
+```
+case1-accept.sh --business mosaic-stack --args /etc/mosaic-stack/dev.args --claude-pin <pin> --node-pin <v>
+```
+
+It reads the user, home, node, claude and ports from the args file and refuses (exit 2) when that file
+fails `stack-upgrade.sh`'s rules. Every check inside the instance runs as
+`sudo -u mosaic -H env PATH=<node dir>:/usr/local/bin:/usr/bin:/bin`. It changes nothing on the host
+except what F3's message writes to the store. It prints one line per check, `<id> <path> <mark>
+<evidence>`, then a count of each mark. Marks: `closed`, `accepted Q182`, `accepted Q183`, `accepted
+mos-1096`, `accepted mos-1101`, and `unnamed`, which means "not named in Q182, Q183 or a Mos ruling".
+It exits 1 when any F check fails and 0 otherwise. A P check never changes the exit. Each `unnamed`
+line goes to Mos, who takes it to Jason (R8 N1). Duckworth reads the whole output.
+
+It prints no value from `claude-session.env` and never opens it.
+
+Functional checks. Any failure fails the row:
+
+| Id | Check | How |
+|---|---|---|
+| F1 | the units run as `mosaic` | for `[email protected]` and `mosaic-webui.service`: active, `User=mosaic`, and the uid in `/proc/<MainPID>/status` is `mosaic`'s |
+| F2 | the Console answers on 127.0.0.1:732 only | `curl -fsS http://127.0.0.1:732/healthz` succeeds, and `ss -Hltnp` shows 732 bound to 127.0.0.1 only, by the Console's MainPID. Jason reaches it with `ssh -L 7332:127.0.0.1:732 [email protected]`. A LAN listener waits for Q175 SSO (sage-1451 Q3) |
+| F3 | one tester message gets a reply | as `mosaic`: `mosaic talk chief <marker> --business mosaic-stack --tester --wait 300`. A stored reply to the marked message passes. The inbox shows decisions only, so it isn't used |
+| F4 | the precheck passes | `case2-precheck.sh --business mosaic-stack --profile factory` as `mosaic` exits 0 |
+| F5 | a role session runs under bwrap with the profile | while F3's reply is pending: a `/usr/bin/bwrap` process owned by `mosaic` has a claude child. Its `/proc/<pid>/attr/current` equals `bwrap (enforce)` and the child's equals `bwrap//&unpriv_bwrap (enforce)`, exact strings after the trailing newline is cut |
+| F6 | claude is the pin | the args file's `--claude` path sits under `/opt/mosaic-stack/claude-<pin>/`, and its `--version` as `mosaic` prints `<pin> (Claude Code)` |
+| F7 | the PM run is live | `launches list --json` as `mosaic` has exactly one live entry for the PM's instance (`launch.by`), the check `confirm` runs |
+| F8 | the credential's file | `stat -c '%U %a %F'` on `claude-session.env` reads `mosaic 600 regular file`, and it isn't a symlink. Run sheet section 9 marks this "precheck line missing" |
+| F9 | the autoupdater is off | `/etc/claude-code/managed-settings.json` is `root:root` 0644 and its `env.DISABLE_AUTOUPDATER` is `"1"`. Run sheet section 3 marks this "precheck line missing" |
+| F10 | node is the pin | the args file's `--node` is `/opt/mosaic-stack/node-<v>/bin/node` with `<v>` the `--node-pin`, and its `--version` prints `<v>`. Run sheet section 2 marks this "precheck line missing" |
+| F11 | no Discord binding | `/srv/mosaic/.mosaic-dev/discord/` is absent or holds no `*.json` (section 2) |
+
+Host paths. These report and never fail the row:
+
+| Id | Path | Mark | Evidence |
+|---|---|---|---|
+| P1 | `mosaic` has sudo | closed only when `sudo -l -U mosaic` prints "is not allowed to run sudo"; any other output is unnamed | the `sudo -l` result |
+| P2 | `mosaic` has supplementary groups or a key | closed when `id -G mosaic` is one entry and `~mosaic/.ssh/authorized_keys` is absent or empty | `id`, file state |
+| P3 | `localadmin` NOPASSWD sudo, reached with the dragon-lin key | accepted Q183 | `sudo -l -U localadmin` |
+| P4 | root on pve over VM 1008, and PBS backups that hold `/srv/mosaic` with the credential | accepted Q182 and Q183 | a fixed line; the script can't see pve |
+| P5 | `jarvis`, which runs Hermes, reaches `/srv/mosaic` through sudo, docker or lxd | closed when `jarvis` is in none of the three; unnamed otherwise. #423 step 4 removes all four groups before the install (mos-1091 4c) | `id jarvis` |
+| P6 | other members of sudo, docker, lxd | closed when sudo holds only `localadmin` and docker and lxd are empty; each other member is its own unnamed line | `getent group` lines |
+| P7 | a file under `/etc/sudoers.d` naming `mosaic` | closed when none | file names |
+| P8 | the Console or tester reachable from the LAN | closed when 732 and 7333 are bound to 127.0.0.1 only, each by the Console's MainPID, and nothing listens on 7331 | listener table |
+| P9 | a user namespace through `/usr/bin/bwrap` | accepted mos-1096 only while all eight hold, unnamed otherwise: hostcheck items 1 to 6, read from `/usr/local/lib/mosaic-stack/hostcheck.sh --check`'s own `ok N` lines (item 7 is P10's floor); `sudo -u jarvis /usr/bin/bwrap --version` fails with "Permission denied"; `getent group mosaic` lists no member and no other account has its gid. F5 adds the label of a real role session | the hostcheck lines and each item |
+| P10 | a session binds the tester port 7333 while the Console is down | accepted mos-1101 while the port floor is above 732 and 7333 is held by the Console's MainPID | the floor, the owner pid |
+| P11 | the boot check runs before the bus | closed when `mosaic-hostcheck.service` is enabled and `systemctl show -p Before` on it names `mosaic-bus@<business>.service` for the args file's business; unnamed otherwise (section 7) | the `Before=` value |
+
+P9 reads hostcheck's output, which root's own script prints, by matching `^ok [1-6] ` lines. It runs `--check` only,
+never `--enforce`, so the acceptance can't close bwrap.
+
+Tests, in `packages/cli/tests/case1-accept.test.mjs`. The script takes a test seam, `--root DIR`, for
+`/proc`, `/etc`, `/srv/mosaic` and `getent`, and refuses it when run as root, as the hostcheck does. Fake
+`systemctl`, `curl`, `ss`, `sudo`, `bwrap`, `sysctl`, `stat`, `claude`, `node` and `hostcheck.sh` on PATH.
+Nothing reaches .53 or dragon-lin's live state, and no test reads a real credential. Cases:
+- every check passing exits 0, with the counts matching the lines;
+- each F check failing alone exits 1 with its line;
+- F5 fails on `unpriv_bwrap (enforce)`, `bwrap//&unpriv_bwrap (complain)` and a trailing space;
+- F6 fails on a stub `claude.exe` that prints nothing and on a path outside `claude-<pin>`;
+- F8 fails on mode 0640, on another owner and on a symlink, and the stand-in credential's value never
+  appears in the output;
+- F11 fails on one `*.json` under `discord/`;
+- each P check in each of its marks: P1 with output that grants nothing but lacks the refusal text
+  (unnamed), P9 unnamed once for each item missing, P10 unnamed with the floor at 700 and with 7333 held
+  by another pid, P11 unnamed with `Before=` naming another business;
+- every P check `unnamed` still exits 0;
+- a bad args file refuses with exit 2 before any check;
+- every in-instance call goes through `sudo -u mosaic -H env PATH=<node dir>:...`, read from the fake
+  `sudo`'s recorded argv;
+- the hostcheck fake records `--check` and never `--enforce`.
+
+Mutants, each killed by a named case:
+1. F1 passes on a MainPID owned by root.
+2. F2 accepts a listener on 0.0.0.0.
+3. F3 passes without a reply.
+4. F5 matches a substring.
+5. F6 skips the `--version` check.
+6. F8 skips the owner check.
+7. F11 ignores `discord/`.
+8. P1 closes on any output.
+9. P5 maps to `closed` with `jarvis` in docker.
+10. P9 drops the jarvis item.
+11. P11 accepts any `Before=`.
+12. A P check's `unnamed` sets the exit to 1.
+
+## 6. The .53 window
+
+Nothing in this row touches .53 (sage-1809). Every root step below is ops-01's, over
+`ssh [email protected]` with `sudo`, and waits on a Jason decision (mos-1086). The window needs:
+- row 226 landed;
+- Jason's or Mos's go naming the commit, the bundle's sha256, the node and claude pins, the role set and
+  Jason's human id;
+- a backup first;
+- a STATE report after.
+
+| # | Step | Runs as | Source |
+|---|---|---|---|
+| W0 | re-read section 0's items; stop on any change and report it | `localadmin`, read only | section 0 |
+| W1 | PBS backup of VM 1008 | ops-01 on pve | section 4 |
+| W2 | the stack's user and home | root | run sheet 1 |
+| W3 | node under `/opt` | root | run sheet 2 |
+| W4 | claude under `/opt`, managed settings | root | run sheet 3 |
+| W5 | bubblewrap, the profile, the statoverride, the no-new-privs test, the drift stop; `hostcheck.sh --check` exits 0 with item 7 at 1023 | root | run sheet 4 |
+| W6 | the port floor (read) | root | run sheet 5 |
+| W7 | the bundle, root's checkout at `<sha>`, `mosaic`'s clone | root, then `sudo -u mosaic -H` | run sheet 6 |
+| W8 | `case2-install.sh --profile factory` with section 1's inputs: bootstrap, the business file, roles, human id, the copy | `sudo -u mosaic -H env PATH=...` | row 226 |
+| W9 | place `claude-session.env` | Jason, or who he names | run sheet 9, section 3 |
+| W10 | write `dev.args` (section 1); `case2-unit.sh` from it, which enables both units and starts the bus, then the Console | root | run sheet 7, 10 |
+| W11 | `case2-precheck.sh --business mosaic-stack --profile factory` exits 0; `hostcheck.sh --check` exits 0 with item 7 at 732 | `mosaic`; root | row 230, 240 |
+| W12 | `stack-release.sh adopt mosaic-stack --units external`, unless row 226's install does it | `sudo -u mosaic -H` | row 232 |
+| W13 | `case1-accept.sh` (section 5); the output to Duckworth, then Mos confirms | root | this row |
+| W14 | STATE report to Mos | ops-01 | brief |
+
+Install rollback, any step before W13 passes. Stop and disable both units, remove their files and
+`dev.args`, then the run sheet's rollbacks for sections 4, 3 and 2 in that order. Removing the user and
+home (`userdel -r mosaic`) needs its own Mos go, since it deletes the home. W1's backup covers the rest.
+
+What row 195 needs from row 226. Row 226 is assigned to Gosalyn, briefed and not started, so I'm listing what the window
+needs from its design, not designing it:
+
+1. `--profile factory` writes the business file with `bus.tester` on and no `library` key, and the roles
+   the go names.
+2. It writes no token slot and no persona files (its brief says so).
+3. It runs before the unit render, since the copy must exist for `case2-unit.sh --copy`, and it starts no
+   unit.
+4. Who writes `dev.args`. The C2-13b brief says the install doesn't write unit files, and the run sheet
+   says "I2's install writes it". `mosaic` can't write `/etc/mosaic-stack`. So either root's part of I2
+   writes it, or ops-01 writes it from section 1 at W10. Either works for row 195. The file's content is
+   fixed above.
+5. Whether it runs `adopt`. If it doesn't, W12 does.
+
+I sent these to Gosalyn on 2026-10-21 (gosalyn-0085 acknowledged), and the run sheet takes whichever answer 226 gives.
+
+## 7. The business id
+
+.53's business id is `mosaic-stack` (sage-1813). It appears in:
+- the args file, twice;
+- the bus unit `[email protected]`;
+- the business file name;
+- `case1-accept.sh --business`.
+
+The landed boot unit `packages/cli/systemd/mosaic-hostcheck.service` has
+`[email protected]`. So at boot the drift stop runs before .53's bus, and DEFERRED 240
+N1 (da3051ccc: `After=mosaic-hostcheck.service` in `mosaic-bus.service.in`) doesn't bind this row.
+
+If a go ever names another id for .53, the window stops before W8, and the N1 fix lands first as its own
+reviewed row. P11 is the check on the host. It reads `unnamed` when the boot unit's `Before=` doesn't
+name the installed bus.
+
+DEFERRED 240 N2 (the apt hook goes in before the first `--check`) is a run sheet order note. This row
+doesn't edit the run sheet, so it stays deferred.
+
+## 8. Rulings this design rests on
+
+- sage-1451: Q1 system units; Q3 the Console on 127.0.0.1 with `ssh -L`; Q4 a rebase goes to a new branch
+  name (#426(a), mos-1086).
+- mos-1091, mos-1096, mos-1098, mos-1101: the bwrap path, its profile and P9; the port squat and P10; .53
+  runs the PM. Their r6 sections stand, and rows 232, 233, 240 and 230 implemented them.
+- mos-1108 (Q187) and mos-1118: the installer rows and the scope cut. mos-1122 (Q189): both units start at
+  boot.
+- sage-1522: claude under `/opt`, root-owned.
+- sage-1809: no step on .53, root steps named and left to ops-01, the business id stated.
+- sage-1813: 226 in the after list (rev 2718); the id is `mosaic-stack` and 240 N1 doesn't apply.
+- Q185: the factory's model account. Q173: credentials placed by Jason or his named person.
+
+## 9. Manifest (planned)
+
+- `scripts/case1-accept.sh` (new), mode 100755.
+- `packages/cli/tests/case1-accept.test.mjs` (new). Section 5's cases and mutants.
+- `docs/TOOLS.md`: a `case1-accept.sh` entry with usage, marks and exits, beside the hostcheck entry.
+- `agents/darkwing/work/queue-195/BUILD.md` (new): run environment, the mutant results, deviations.
+- No change to `case2-*.sh`, `stack-upgrade.sh`, `stack-release.sh`, `case1-hostcheck.sh` or the run
+  sheet. Two follow-ups stay out of this row:
+  - row 230 r2 N1. The "still on copy" line reads the id from the unit file. On .53 neither the install
+    nor `stack-upgrade.sh` reaches that line, since both start from stopped units.
+  - DEFERRED 240 N2.
+- No change to `~/.mosaic-dev`, `~/.config/mosaic-dev`, dragon-lin's units or `~/.mosaic`.
+
+Gate: Duckworth approves this design, then the manifest; the cli suite and every `scripts/test-*.sh`
+green on Sage's gate; section 5's twelve mutants killed in a slot Sage grants.

agents/darkwing/work/queue-232/BUILD.md

@@ -0,0 +1,287 @@
+# Row 232 (I1): stack-release external units and bundle copies
+
+Brief: `docs/plans/2026-10-20_installer-rows.md` section I1, blob `f35e7e57daee` (commit ad6f0be7a). Gitea
+#1734, Vikunja P19 #432. Owner Darkwing, reviewer Filbert, gate owner Sage. Design input: row 195 DESIGN r6,
+`agents/darkwing/work/queue-195/DESIGN.md` at b7239bb66 (approved in duckworth-0055). Where the brief and
+r6 differ, the brief wins. sage-1561 ruled where the stack user's `stack-release.sh` runs: from its own
+clone of the release bundle, so `check_target`, the plan's commit list and status drift are unchanged and
+nothing adds `safe.directory`.
+
+## Files
+
+Base: cb5fdb064 (row 199's landing, on top of row 200's 9e1085816). Branch `darkwing/row232-r1`. The first
+build, 0af0c73c6 on `darkwing/row232`, sat on 00d4cc1f6 (row 190); row 200 landed first, so this one is
+rebased onto it (see D9 and D10).
+
+- `scripts/stack-release.sh`: `--units user|external`, the `sc` and `jctl` backend, `confirm`, `revert`,
+  `gate --since`, `rollback --to`, `--plan --expect-from`, the external gate (start floor, PM check from
+  `launches list`), `external-pm`, and the `awaiting units:` status line.
+- `scripts/stack-copy.sh`: `check --units external`, `copy --bundle FILE SHA`, `wrapper ID --create`.
+- `packages/cli/tests/stack-release-external.test.mjs` (new, 25 tests).
+- `packages/cli/tests/stack-release-fixture.mjs` (new): the helpers `stack-release.test.mjs` defined, moved
+  so both files share them. See deviation D1.
+- `packages/cli/tests/stack-release.test.mjs`: the helpers leave and one import line comes in. The 74 tests
+  have the same names and the same bodies as on the base.
+- `packages/cli/tests/stack-copy.test.mjs`: three new `row 232:` tests and a wider `node:fs` import.
+- `docs/TOOLS.md`: the stack-copy usage block and three paragraphs, the stack-release usage block, and a new
+  subsection "Root-owned units (`--units external`, row 232)".
+- `packages/cli/README.md`: one paragraph.
+- This file.
+
+The worktree's `node_modules` symlink is not part of the candidate.
+
+## User mode is unchanged
+
+Every `systemctl` call goes through `sc` and every `journalctl` call through `jctl`. Under `user` they
+are `systemctl --user "$@"` and `journalctl --user "$@"`. Under `external`, `sc` allows only `show`,
+`is-active` and `list-units`, and `jctl` returns 1, so an external run can't start, stop, install or read
+the journal even through a path the tests miss.
+
+Two tests hold the brief's "every command line and every byte of output":
+
+- `user mode: every systemctl call carries --user, and activate, rollback and check make the base's
+  calls`. A fixture repo gets the base's two scripts from `git show cb5fdb064:`. The same activate,
+  rollback and `stack-copy.sh check` run from both trees, and the recorded argv (with the fixture root and
+  port replaced by placeholders) must match line for line. Every call carries `--user`.
+- `user mode: a default activate --plan prints the base's bytes`, for four plans.
+
+The base output is produced live from the base blobs, not stored as a fixture file. See deviation D3.
+
+## r6 section 7, test by test
+
+All in `stack-release-external.test.mjs` unless named.
+
+| r6 :742-812 item | Test |
+|---|---|
+| `units-running` (N4), store, log and TAKEN left | `units-running (N4) refuses while a unit is active...`; also checks that `failed` counts as down and that the Console is checked first |
+| activate leaves the pointer, writes `AWAITING-UNITS` and a backup | `activate stages: ...`, which also checks the set's file list, `UNITS.sha256`, no `--user`, no journal call and `status` |
+| `open-activation` with zero, two, the wrong copy, one not open | `confirm and revert refuse open-activation ...` |
+| `confirm` polls: 3 s fails at `--timeout 1`, passes at `--timeout 10` | `confirm polls: bus status good after 3 s fails ...` and `confirm polls to a pass ...` |
+| `stale-start` floor with `started` at .900 | `stale-start: @1792540799 fails ...` and `stale-start is a gate code ...` |
+| `confirm` pass writes pointer, ok, removes marker; timeout writes `FAILED` and exits 1 | the two polling tests |
+| `activation-failed` when `FAILED` exists | `confirm polls: ... FAILED then refuses activation-failed` |
+| lines carry the started op, from, to, activation and backup | `sameAsStarted` in every confirm test, and sequence 7 |
+| `gate` (N2) with and without `--since` | `gate (N2, A2f): ...` and the usage test |
+| `--plan --expect-from` (N5), activate and `rollback --to` | sequence 7 |
+| A3 order: capture-failed, marker-failed, wrapper failure after migrate | `A3 order: ...` and sequence 2 |
+| refusals log no activation; `interrupted` unchanged | `open-activation` test and sequence 5 |
+| PM check: one, none, two, early, not live, other business, other instance; no journal call | `the external PM check reads launches list ...` (modes '', coder, none, twolive, early, dead, other) and `journalCalls` in every external test |
+| `external-pm` | `pm-on and activate --pm-after-harness refuse external-pm` |
+| `revert` restores TAKEN only after a migration | `revert puts the wrapper back and leaves the store ...` and sequences 2 and 8 |
+| `confirm --rollback` per cause, `unrecorded`, `rollback-failed`, mismatch | sequences 1, 2, 3, 5 and 8, and `confirm --rollback refuses rollback-mismatch, and logs rollback-failed ...` |
+| sequences 1-8 | `sequence 1:` to `sequence 8:`, each ending with the `closed` check (one started and one result line, empty `interrupted`, no marker or `FAILED`, a following `--plan` that doesn't refuse `interrupted-run`) |
+| `rollback --to` refuses not-previous; `rollback --restore` finds an external backup | sequence 7, and `confirm --rollback after a --restore swap ...` |
+| `gate` writes nothing | the `gate (N2, A2f)` test and sequence 4 compare the log, the pointer and the state tree |
+| `confirm`, `revert`, `gate`, `--to` refuse without `--units external` | `confirm, revert, gate, --to and --expect-from need --units external ...` |
+| default path: every call carries `--user`; default `--plan` bytes | the two user-mode tests above |
+
+The brief's additions, in `stack-copy.test.mjs`:
+
+- `row 232: copy --bundle copies a SHA the bundle's refactor reaches, byte-identical to copy SHA, and
+  refuses the rest`: a short SHA, a missing file, a symlink, a bundle that fails `git bundle verify`, a
+  bundle with no `refs/heads/refactor`, a SHA not in the bundle, and a SHA the bundle carries on another
+  branch that refactor doesn't reach. The bundle copy's tree matches `copy SHA`'s byte for byte, and the
+  `release:` and `bundle sha256:` lines are checked.
+- `row 232: wrapper --create writes the first wrapper only, the same bytes wrapper ID writes, and refuses
+  over any file`, a symlink included. Without `--create` a missing wrapper still refuses.
+- `row 232: check --units external reads the system units, the default reads the user units`.
+
+## Mutants
+
+`mutants.sh` in my scratch (not committed, it edits the worktree), 17 mutants: r6's re-pin list (:817-838)
+minus the three `case1-repin.sh` ones, plus the brief's two. Each one applies exact replacements after a
+checked backup, runs `bash -n`, runs its named killers, restores the file and checks its sha256. Two
+controls run first with no change: the whole external file, and stack-copy's `row 232:` tests.
+
+| Mutant | Killers |
+|---|---|
+| m01 `confirm` writes the pointer on a gate failure | `confirm polls: bus status` |
+| m02 `gate_once` in place of `gate` | `confirm polls to a pass`, `stale-start is a gate code` |
+| m03 PM check counts any instance | `external PM check` |
+| m04 PM check drops the `startedAt` bound | `external PM check` |
+| m05 `confirm` takes the newest `AWAITING-UNITS` | `open-activation` |
+| m06 `rollback --to` skips the comparison | `sequence 7:` |
+| m07 the default path drops `--user` from one call (`is-active`) | `user mode: every systemctl` |
+| m08 the timeout writes r4's interim `rollback pending` line | `confirm polls: bus status`, `sequence 1:`, `sequence 5:` |
+| m09 `AWAITING-UNITS` last, after the wrapper | `sequence 2:` |
+| m10 a refusal names the open activation | `sequence 5:`, `open-activation` |
+| m11 `stale-start` is a refusal | `stale-start is a gate code` |
+| m12 `revert` restores without `MIGRATING` | `revert puts the wrapper back` |
+| m13 `confirm` logs op `confirm` | `sequence 7:`, `confirm polls to a pass` |
+| m14 `MIGRATING` after the migration | `sequence 8:` |
+| m15 `gate` takes its floor from the log without `--since` | `gate (N2` |
+| m16 `copy --bundle` skips the reachability check | stack-copy `row 232:` |
+| m17 `wrapper --create` overwrites | stack-copy `row 232:` |
+
+## Deviations and choices
+
+D1. The shared helpers moved to a new file, `packages/cli/tests/stack-release-fixture.mjs`. The brief's
+files list names `stack-release.test.mjs` "where a shared helper moves" but not a destination. Importing
+from the other test file would run its 74 tests twice, so the helpers need a module of their own.
+
+D2. The fixture's T17 check (what a run may never remove) now exempts a rollback set's `AWAITING-UNITS` and
+`FAILED`. `confirm` removes both when it closes the activation (r6 A5 and R4). User mode writes neither, so
+user-mode runs check exactly what they did.
+
+D3. The user-mode argv and `--plan` tests read the base's scripts with `git show cb5fdb064:` rather than
+storing their output as a fixture file. A later row that changes user-mode output on purpose moves the
+`BASE` constant in the test to its own base, or the test fails. I chose this over a stored fixture because
+a stored copy can drift from the base without anyone noticing.
+
+D4. `marker-failed` is reached by making `state/stack-rollback` unwritable. r6 says "an existing `$RS`", but
+`next_activation` never picks a taken name, so no test can make the run meet an existing `$RS`. The
+exclusive `mkdir` is still what refuses.
+
+D5. The stale-start polling case turns the enter time to `@1792540800`, not r6's `@1792540805`, with the
+started line at 1792540800.900. That also checks that the floor is the whole second, so .900 doesn't push it
+to 1792540801.
+
+D6. No fake `sudo` or `case2-unit.sh`. r6's sequences ran under them because r6 had `case1-repin.sh` drive
+the steps, and that script is I3's. Here the test plays root: it stops and starts the fake system units and
+installs with the existing `bus-service.sh` and `webui-service.sh` stand-ins, between the real
+`stack-release.sh` calls, on one log.
+
+D7. The fake marker in the `open-activation` test is named `20000101T000000Z-<C1 prefix>` so it sorts
+before the real one. A marker that sorted after it would leave m05 (newest marker) alive.
+
+D8. m10 sets `ACT` inside `open_activation`, where r6's wording ("ACT set before the checks") lands in this
+code. `ACT` is set only after every check in `confirm`.
+
+D9. Row 200's `--sso` is a usage error under `--units external`, with the proof flags, `--no-proof` and
+`--no-send`. It is a Console flag, and root's Console unit carries the Console flags; the script under
+external renders no Console line and never calls `console_for_target`, so `sso_checks` doesn't run there
+either. The usage text, the TOOLS.md bullet and the external usage test name it.
+
+D10. Row 200's `config_checks` runs under `--units external` too, after `plugin_checks`, in both the
+`--plan` and run paths of `activate` and `rollback --to`. It checks the target's loader against the stack
+user's `config.json`, which the bus on a VM still reads, so a `console` key the target refuses would break
+root's bus start the same way. The cost is one more refusal (`config-console-key`) an external run can
+print; I took it over a bus that fails after root's start. The rebase changed no user-mode line: the
+conflicts were the `SSO=0` globals line, the `plan` body (row 200's `SSO_PLAN` line sits in the user
+branch) and the two `--plan` lines that gained `config_checks`. In the tests, row 200's fixture lines
+(the loaders, `sso-config.mjs` and the `--sso` cli.mjs line for C1 and C) moved into
+`stack-release-fixture.mjs` with the rest of the copy setup, and the `ALGS` import stays in
+`stack-release.test.mjs`, which T57 uses.
+
+## duckworth-0055's notes on r6 (brief line 169)
+
+Duckworth's r6 approval (REVIEW-r5.md at 23f5520b5) carried two notes.
+
+- N1, A2's stop timeout under `gate --since`. A unit that never stopped keeps its old `ActiveEnterTimestamp`,
+  so `gate --since` fails it with `stale-start`, and the run ends at exit 2 with root stopping the units.
+  That is intended: a unit that won't stop is a fair reason to stop. In I1 this is the gate code and its
+  polling (`stale-start: @1792540799 fails ...`, `gate (N2, A2f)`, m11). The run sheet's A2f line and the
+  re-pin test that points "exits 1 with OLD's gate passing" at an A3 exit 3 belong to I3, which owns
+  `scripts/stack-upgrade.sh` and `docs/guides/host-run-sheet.md`. I'll name both in the I3 build.
+- N2, the claude path under `/opt/mosaic-stack` (gosalyn-0058, sage-1522). I1 doesn't touch it. Under
+  `--units external` the script checks no claude pin of its own (`no-claude-pin` applies only to user
+  mode), because root's unit carries it. The `--claude` value, the managed-settings reasoning, F6 and the
+  run sheet's claude step go to I2 and I3.
+
+## Run environment
+
+Worktree `/mnt/storage/scratch/darkwing-r232`, `TMPDIR=/mnt/storage/scratch/tmp/r232`, node from PATH.
+One external file run takes about 94 s.
+
+## Results
+
+Singles on the rebased candidate, before the gate:
+
+| File | Tests | Pass | Fail |
+|---|---|---|---|
+| `packages/cli/tests/stack-release-external.test.mjs` | 25 | 25 | 0 |
+| `packages/cli/tests/stack-copy.test.mjs` | 16 | 16 | 0 |
+| `packages/cli/tests/stack-release.test.mjs` (row 200's T57 included) | 192 | 192 | 0 |
+| `packages/cli/tests/stack-instances.test.mjs` | 23 | 23 | 0 |
+| `packages/webui/tests/pinned-copy.test.mjs` | 10 | 10 | 0 |
+| `packages/cli/tests/channel-recovery.test.mjs` (imports `channel-fixture.mjs`, which names the scripts) | 1 | 1 | 0 |
+| `packages/cli/tests/host.test.mjs` (reads `packages/cli/README.md`) | 42 | 42 | 0 |
+
+These are every test file that reads `stack-release.sh` or `stack-copy.sh` (a grep of `packages/*/tests` and
+`scripts/`). None of them pins a sha256 of a changed file. `packages/cli/tests/host.test.mjs` reads
+`packages/cli/README.md` for a unit file name; this row only adds a paragraph there. The grep and the runs
+were repeated on the rebased tree on 2026-10-21; the reader set is the same. A dry run of `mutants.sh`
+matches each of the 17 replacements once on the rebased scripts.
+
+### Gate, 2026-10-21, Sage's slot (sage-1618)
+
+Candidate a0ffabc3f on `darkwing/row232-r1`, run by `~/darkwing-scratch/r232/gate.sh`: the cli suite, then
+every `scripts/test-*.sh`, one after another, stopping at the first failure. busy.sh passed at 01:07:49Z
+after Launchpad's single `stack-release.test.mjs` run ended. The gate stopped at the first one, so the
+chain waited for that PID to exit and checked again. The EXIT trap removed the compose network; no
+container was left.
+
+| Step | Time (UTC) | Result |
+|---|---|---|
+| `packages/cli`, `node --test tests/*.test.mjs` | 01:07:50 to 01:17:53 | 561 pass, 0 fail, 0 skipped |
+| `scripts/test-auth.sh` | 01:17:53 to 01:17:54 | 15 passed, 0 failed |
+| `scripts/test-conductor.sh` | 01:17:54 to 01:18:00 | 17 passed, 0 failed |
+| `scripts/test-config.sh` | 01:18:00 to 01:18:02 | 31 passed, 0 failed |
+| `scripts/test-discord.sh` | 01:18:02 to 01:18:12 | 78 passed, 0 failed |
+| `scripts/test-extension-package.sh` | 01:18:12 to 01:18:13 | 18 passed, 0 failed |
+| `scripts/test-foundation.sh` | 01:18:13 to 01:19:01 | 44 passed, 0 failed |
+| `scripts/test-land-work.sh` | 01:19:01 to 01:19:14 | 86 passed, 0 failed |
+| `scripts/test-queue.sh` | 01:19:14 to 01:19:37 | 156 node tests pass, queue suite 28 passed, 0 failed |
+| `scripts/test-release.sh` | 01:19:37 to 01:19:51 | 14 passed, 0 failed |
+| `scripts/test-task.sh` | 01:19:51 to 01:20:44 | 98 passed, 0 failed |
+
+### Mutants, 2026-10-21, same slot
+
+`~/darkwing-scratch/r232/mutants.sh`, right after the gate. Both controls (the external file whole, and
+stack-copy's `^row 232: ` tests) exited 0 on the unmutated tree. Each mutant was applied after a checked
+backup and a syntax check, ran its killers from the table above, and was put back with its sha256
+checked. The script stops on any restore mismatch, and it ran to its end.
+
+| Mutant | Killer exit | Result |
+|---|---|---|
+| m01 pointer on gate failure | 1 | killed |
+| m02 gate once | 1 | killed |
+| m03 PM from any instance | 1 | killed |
+| m04 no startedAt check | 1 | killed |
+| m05 newest marker | 1 | killed |
+| m06 --to not compared | 1 | killed |
+| m07 one call without --user | 1 | killed |
+| m08 interim pending line | 1 | killed |
+| m09 marker written last | 1 | killed |
+| m10 refusal names the open activation | 1 | killed |
+| m11 stale-start refuses | 1 | killed |
+| m12 revert always restores | 1 | killed |
+| m13 confirm op | 1 | killed |
+| m14 MIGRATING after migrate | 1 | killed |
+| m15 gate floor from the log | 1 | killed |
+| m16 bundle reachability unchecked | 1 | killed |
+| m17 --create overwrites | 1 | killed |
+
+17 of 17 killed, 01:22:16 to 01:24:32Z. I read the logs for m01 and m09, two of the quick kills: each failed on
+its named test's assertion (m09 on `AWAITING-UNITS` in sequence 2), not on a load error.
+
+## Round 2: rebase onto 8fede5fc6 (sage-1673)
+
+Rebase only. Before the landing gate, a check of BASE..HEAD on the manifest paths found that row 230
+(c8bc5cf4c) had changed one of them after the round 1 base, cb5fdb064. Sage ruled a re-round with a
+scoped review, the same shape as row 210 round 3.
+
+Branch `darkwing/row232-r2`: the two round 1 commits, a0ffabc3f and 84f1a91e6, cherry-picked onto
+8fede5fc6 with no conflict, then this section. No code or test changed.
+
+- `git merge-tree --write-tree origin/refactor darkwing/row232-r1` (refactor at 8fede5fc6) gives tree
+  837bde79236c with no conflict. The cherry-picked tip before this section has the same tree.
+- `packages/cli/README.md` is a clean 3-way merge. Row 230's hunk is at lines 710-717 (the session credential
+  paragraph); this row's is a new paragraph at 773. With `git patch-id --stable`, the README diff from r1 to
+  r2 is 02b679e2, the same as row 230's README diff `cb5fdb064..8fede5fc6`. This row's README diff is
+  c395ecd2 on both bases (`cb5fdb064..r1` and `8fede5fc6..r2`).
+- The seven code, test and doc paths other than the README hash the same as in manifest 7a3b4ea1, which
+  Filbert approved in round 1: `docs/TOOLS.md`, `packages/cli/tests/stack-copy.test.mjs`,
+  `packages/cli/tests/stack-release-external.test.mjs`, `packages/cli/tests/stack-release-fixture.mjs`,
+  `packages/cli/tests/stack-release.test.mjs`, `scripts/stack-copy.sh`, `scripts/stack-release.sh`.
+  This file also matched until this section was appended. Its other lines are unchanged.
+- The one test that reads the README, `host.test.mjs:855`, looks for the unit's `EnvironmentFile=` line.
+  That line is unchanged context in row 230's hunk.
+- No row 230 test reads `stack-release.sh` or `stack-copy.sh`, and no test of this row reads a row 230 file.
+
+Nothing was run for this round. The landing gate runs on the r2 tip on Sage's slot.
+
+Follow-up, doc-only (sage-1673): `scripts/case2-unit.sh:108` and `scripts/case2-precheck.sh:157` cite
+`scripts/stack-copy.sh:8` and `:22` for `COPIES` and `copy_root`. With this row those lines are `:10` and
+`:26`. Only comments are affected and no test reads them. Row 233 doesn't touch those scripts, so the fix
+goes on the #1732 carry list.

agents/darkwing/work/queue-233/BUILD.md

@@ -0,0 +1,249 @@
+# Row 233 (I3): root's upgrade driver and the host run sheet
+
+Brief: `docs/plans/2026-10-20_installer-rows.md` section I3, blob `e61291bcf1c6` (commit a0e3d7cfd), re-pinned
+by Sage (sage-1685, rev 2631) from `f35e7e57daee` (ad6f0be7a). The later blob only appends I4; the I3 text
+is the same. Gitea #1735, Vikunja P19
+#432. Owner Darkwing, reviewer Filbert, gate owner Sage. Design input: row 195 DESIGN r6,
+`agents/darkwing/work/queue-195/DESIGN.md` at b7239bb66, sections 2, 4 and 7. Where the brief and r6
+differ, the brief wins. Sage's rulings during the build: sage-1650 and sage-1652 (`--backup last`, the
+`--no-rehearsal` mapping, `--rehearse-port`, hostcheck), and sage-1653 (`from_log newest`, the two external
+plan refusals, the `BACKUP_STORE` line).
+
+## Files
+
+Base: e65a3ab4d, row 232's landing, on `darkwing/row233-r1`. The build started on ea1e85c7b
+(`darkwing/row233`, row 232's candidate e6ca230d2 and its BUILD.md) before row 232 landed. The three row 232
+files this row changes are identical on the two bases, so the uncommitted diff moved across unchanged.
+
+- `scripts/stack-upgrade.sh` (new): `upgrade` and `rollback`, root's side of r6 A1-A5, A2f and R1-R4.
+- `packages/cli/tests/stack-upgrade.test.mjs` (new, 20 tests).
+- `docs/guides/host-run-sheet.md` (new).
+- `docs/TOOLS.md`: a new subsection "Root's upgrade driver (`scripts/stack-upgrade.sh`, row 233)", plus the
+  row 232 lines below.
+- Row 232 files, changed on Sage's rulings (the brief's files list doesn't name them):
+  - `scripts/stack-release.sh`:
+    - `rehearse --backup last` takes the newest backup the log records (`from_log newest`) and prints
+      `PASS backup-last`. With none it fails `no-backup`, exits 3 and makes no rehearsal directory.
+      A newest backup that isn't an activation id aborts `backup-unreadable`, exit 1.
+    - The rehearsal prints `BACKUP_STORE <activation id> schema <version>` before its migration step.
+    - `--plan` under `--units external` refuses `open-activation` when any rollback set holds
+      `AWAITING-UNITS`, and `migrate-required` for a migrating target without `--migrate`. Root reads
+      only the plan's exit, so these two have to be refusals there. User mode prints the same bytes.
+  - `packages/cli/tests/stack-release.test.mjs`: three new `row 233:` tests for `--backup last`.
+  - `docs/TOOLS.md`: `--backup ACTIVATION|PATH|last` in the rehearse usage, a paragraph on `last`, and a
+    paragraph on the two external plan refusals.
+- This file.
+
+## The brief, item by item
+
+| Brief item | Where |
+|---|---|
+| Root runs from a root-owned checkout, never a copy | `head-mismatch` (A1); TOOLS.md; run sheet section 6 |
+| I2's render with `/etc/mosaic-stack/<instance>.args`, `--copy` the one changed value | `read_args`, `args_with`; the args test |
+| The args file changes only after a confirmed run | `prepare_args` before A2, `mv` after A5; sequences 1 and 7, m6 |
+| `copy --bundle` as the stack's user before A1 | the `fetch`, `ff`, `copy` steps; sequence 1's sudo keys |
+| A rehearsal before A2, a failed one refuses with nothing stopped | `rehearse`; three rehearsal tests, m4 |
+| The root lock, held to the end, rollback included | `flock -n 9`; the lock test and sequence 3's probe, m1, m2 |
+| A1 refuses `open-activation` | stack-release.sh's external plan; the AWAITING-UNITS test, m3 |
+| `migrate-required` without `--migrate` | stack-release.sh's external plan; its test, m5 |
+| The step log, 0640, one line per step | `logl`, `step`; every test checks lines against `STEP` |
+| Exit codes 0-3 | `finish`, `refuse`; exit 4 is usage |
+| duckworth-0055's notes | the next section |
+| Root parses no stack user output beyond exits | the step log test; the one exception is sage-1653's `BACKUP_STORE` |
+| The host run sheet | `docs/guides/host-run-sheet.md` |
+
+## duckworth-0055's notes on r6 (brief line 169)
+
+- N1, A2's stop timeout under `gate --since`. Row 232's BUILD.md left two pieces to I3. The run sheet's
+  A2f line is in section 6 ("When a run doesn't exit 0", exit 2). The test is `N1: a bus that outlives
+  A2's timeout keeps its old start`: a bus that ignores `stop` keeps its old `ActiveEnterTimestamp`,
+  `wait-down` logs `rc=1 ... state: active`, A2f restarts and gates, the gate fails `stale-start`, and the
+  driver stops both units and exits 2. Sequence 4 is the other half: an A3 exit 3 goes to A2f and exits
+  1 with the old copy's gate passing.
+- N2, the claude path under `/opt/mosaic-stack`. Run sheet section 3 installs it there as root with
+  managed settings. The args file's `--claude` carries it, and `case2-unit.sh` already refuses a binary
+  that isn't root's or sits under the home. The driver passes the args file through and adds no claude
+  check of its own. F6 is I2's.
+
+## Sage's rulings during the build
+
+- sage-1650 and sage-1652. Root always runs the rehearsal and maps its exit:
+  - 0 goes on, or refuses `rehearsal-required` with `--no-rehearsal`.
+  - 3 refuses `no-backup`, or with `--no-rehearsal` logs `rehearsal-skipped` and goes on.
+  - Anything else refuses `rehearsal-failed`.
+
+  `--rehearse-port N`, default 7339. Hostcheck: a missing file or a nonzero `--check` refuses
+  `profile-drift`.
+- sage-1653. `from_log newest`, and the external plan refusals `open-activation` and `migrate-required`.
+  Residual: the `BACKUP_STORE` id and schema land in root's step log, but nothing ties that backup to the
+  one the activation's own backup step takes later. A stopped backup before the upgrade would close that
+  gap; it's a later row, not this one.
+
+## Tests
+
+`stack-upgrade.test.mjs` runs the driver as the test's user against a scratch root, with the test seams
+`STACK_UPGRADE_*`. The stand-ins are a fake `sudo` (logs its argv, checks the driver's form, then runs the
+real command as the test's user, r6's B1 pattern), a fake `case2-unit.sh` render that installs and starts
+the fixture units, a fake `systemctl` for root's system units, and a shell `hostcheck.sh`. The stack's
+user's steps run the real `stack-release.sh` and `stack-copy.sh` from a clone made from a real bundle. The
+units, copies and store are `stack-release-fixture.mjs`'s.
+
+| Test | Covers |
+|---|---|
+| sequence 1 | confirm fails healthz, rollback with `--cause A5`, exit 1; every sudo call in the driver's form |
+| sequence 2 | `activate --migrate` fails at the wrapper, store restored, `--cause A3`, exit 1 |
+| sequence 3 | render fails, `--cause A4`; a probe run during `render-old` refuses `upgrade-running` |
+| sequence 4 | stage exits 3, A2f restarts and gates the old units, exit 1 |
+| N1 | a unit that won't stop: A2f's gate fails `stale-start`, exit 2, units stopped |
+| sequence 5 | confirm of the wrong copy refused, `--cause A5`, exit 1 |
+| sequence 6 | revert fails, exit 2; the next run refuses `interrupted-run` at its plan |
+| sequence 7 | two upgrades and a `rollback --to` with `--restore`; the args file after each confirm; `to-not-previous` |
+| sequence 8 | a migration that writes and fails, store back byte for byte, exit 1 |
+| lock | a second run while the lock is held: one log line, no call |
+| open-activation | any `AWAITING-UNITS` refuses at A1, nothing stopped |
+| migrate-required | refused without `--migrate`, no rehearsal, nothing stopped |
+| rehearsal-failed | the rehearsal's argv, exit 3, nothing stopped |
+| `BACKUP_STORE` | the line after a match; four malformed lines log `BACKUP_STORE none` |
+| no-backup | the real rehearsal with no backup refuses; `--no-rehearsal` logs the skip and goes on |
+| backup-last | the real rehearsal names the newest backup; `--no-rehearsal` with one refuses `rehearsal-required` |
+| args file | group write, other write, two `--copy`, an unknown flag, a symlink, `args-differ` |
+| hostcheck | nonzero `--check` and a missing file refuse `profile-drift` before the plan |
+| head-mismatch | checkout not at `--sha`; a commit the clone can't fast-forward to refuses `fetch-failed` |
+| usage | twelve bad argvs exit 4 with no log and no lock |
+
+The step log check (`STEP`) runs in every test that reads the log: each line must be a step line or the
+result line, and none may hold the stack user's output (`stack-release:`, `PASS `, `FAIL `, `REHEARSAL`,
+the fake rehearsal's text).
+
+## Mutants
+
+`~/darkwing-scratch/r233/mutants.sh`, not committed because it edits the worktree. It has the brief's six
+mutants and two for sage-1650's mapping. The method is row 232's: a checked backup, exact replacements, a
+syntax check, the named killers, then the file put back with its sha256 checked. One control runs first:
+the whole `stack-upgrade.test.mjs` with no change. `DRY=1` matched each replacement once on the candidate
+(2026-10-21).
+
+| Mutant | File | Killers |
+|---|---|---|
+| m1 drop the flock | stack-upgrade.sh | `a second run while the lock is held`, `sequence 3:` |
+| m2 release the lock when the rollback starts | stack-upgrade.sh | `sequence 3:` |
+| m3 skip A1's open-activation check | stack-release.sh | `A1 refuses open-activation` |
+| m4 skip the rehearsal | stack-upgrade.sh | `the rehearsal runs after the plan`, `sequence 1:` |
+| m5 accept a migrating target without `--migrate` | stack-release.sh | `migrate-required` |
+| m6 write the args file before confirm | stack-upgrade.sh | `sequence 7:`, `sequence 1:` |
+| m7 `--no-rehearsal` accepted with a backup | stack-upgrade.sh | `refuses rehearsal-required` |
+| m8 drop the `rehearsal-skipped` line | stack-upgrade.sh | `a real rehearsal with no backup` |
+
+## Deviations
+
+D1. The brief has A1 refuse `open-activation` for an open `AWAITING-UNITS` or a non-empty `interrupted`
+set. The interrupted case refuses with row 232's existing code, `interrupted-run`; only `AWAITING-UNITS`
+gives `open-activation`. Both reach root as `plan-refused`, exit 3 (sequence 6, the open-activation test).
+
+D2. Root copies one line of the stack user's output into its log, `BACKUP_STORE`, on sage-1653. It
+matches a fixed pattern first, takes the last match, logs `BACKUP_STORE none` otherwise, and decides
+nothing on it.
+
+D3. The stack user's steps carry no `--instance`. The driver takes `--instance dev` only, row 190's default
+instance, which the stack user's commands select with no flag. A named instance's units are a later row.
+
+D4. Most tests fake the rehearsal in the fake `sudo`: the fixture's stub copies can't pass a real one. Two
+tests run the real rehearsal (`faults/real-rehearse`): no-backup and backup-last. `stack-release.test.mjs`
+covers `--backup last` itself.
+
+D5. Any nonzero `--plan` exit refuses `plan-refused`, exit 3, whatever the code. The stack user's output
+above it names the refusal; root doesn't parse it.
+
+D6. `rollback --restore ACT` is accepted without `--events`, as `stack-release.sh rollback` accepts it.
+The brief's usage pairs them. `--events` without `--restore` is a usage error.
+
+D7. The refusal of any `STACK_UPGRADE_*` seam when run as root has no test, because the tests don't run
+as root. It is three lines at the top of the script.
+
+D8. The fake `sudo` keeps the test's environment, where real `sudo` resets it. The driver passes
+everything the stack user needs through `env PATH=...` and `-H`, and the fake checks that form.
+
+D9. Exit 3 means nothing stopped, not nothing changed. A refusal after `fetch` leaves the stack user's
+clone fast-forwarded and the new copy made. Both are the user's own state, and the next run reuses them.
+TOOLS.md and the run sheet say so.
+
+D10. The brief's usage has neither `--no-rehearsal` nor `--rehearse-port`. Both come from sage-1650 and
+sage-1652.
+
+## Decisions
+
+- `rollback` has no HEAD check. Its target is an older copy than root's checkout, which already exists.
+  It fetches, copies and rehearses nothing (sequence 7).
+- The new args file is written next to the old one (`.dev.args.XXXXXX`, same mode) before A2, so a full
+  `/etc` refuses before anything stops. It moves into place after A5. A2f and the rollback remove it; a failed move keeps it and names it.
+- Every stack user step gets `--copies` explicitly, so the copies directory comes from the args file's
+  `--home`, never from the user's environment.
+- The stack's user does the fetch, the fast-forward and the copy, so root never runs git on a tree that
+  user can write.
+- A4 is the render, and `case2-unit.sh` starts the bus, then the Console. The forward path has no
+  `systemctl start` of its own; only A2f does.
+
+## Run environment
+
+Worktree `/mnt/storage/scratch/darkwing-r233`, `TMPDIR=/mnt/storage/scratch/tmp/r233`, node from PATH. One
+whole `stack-upgrade.test.mjs` run takes about 56 s.
+
+## Results
+
+### Singles, run 1, 2026-10-21, Sage's slot (sage-1689)
+
+`~/darkwing-scratch/r233/singles.sh` on `darkwing/row233-r1` (base e65a3ab4d, uncommitted tree), 03:48:20Z
+to 03:59:00Z. These are the test files that read a changed script. `stack-instances.test.mjs` reads
+`stack-release.sh`, so it joined the three named in the plan.
+
+| File | Result |
+|---|---|
+| `stack-upgrade.test.mjs` | 20 pass, 0 fail |
+| `stack-release.test.mjs` | 194 pass, 1 fail |
+| `stack-release-external.test.mjs` | 25 pass, 0 fail |
+| `stack-instances.test.mjs` | 23 pass, 0 fail |
+
+The failure was my test, not the script. "row 233: --backup last takes the newest backup..." compares
+`untouched(e)` before and after the run, and `untouched` includes `existsSync(e.log)`. The test took its
+before snapshot ahead of `rlog()`, which writes the log, so that flag went from false to true. Every hash in
+the snapshot matched. The fix takes the snapshot after `rlog()`. No other row 233 test calls `untouched`.
+
+### Singles, run 2
+
+`~/darkwing-scratch/r233/rerun.sh` on aacfa2d7a, Sage's slot (sage-1695), 04:13:05Z to 04:21:28Z:
+`stack-release.test.mjs` whole, 195 pass, 0 fail, 0 skipped. The fixed test passed. The other three files
+did not change after run 1. The gate and the mutants run next, in Sage's slot.
+
+### Gate and mutants, 2026-10-21, Sage's slot (sage-1704)
+
+`~/darkwing-scratch/r233/gate.sh` then `mutants.sh`, chained behind `busy.sh`, on d99166ade (code
+aacfa2d7a; d99166ade changes only this file). Counts are an awk sum over `gate-r1.out`.
+
+| Part | Time (UTC) | Result |
+|---|---|---|
+| cli suite (`node --test tests/*.test.mjs`) | 04:29:01-04:37:27 | 616 pass, 0 fail, 0 skipped |
+| the 10 `scripts/test-*.sh` | 04:37:27-04:39:38 | selftests 429 passed, 0 failed; `test-queue`'s node part 156 pass, 0 fail |
+| gate total | | 1201 pass, 0 fail, 11 suites, `GATE_PASSED` |
+| c0 control | 04:39:38-04:40:35 | exit 0 |
+| m1-m8 | 04:40:35-04:41:25 | 8 of 8 killed, every one exit 1 |
+
+Every restore passed its sha256 check, and `git diff` was clean at d99166ade afterwards. The EXIT trap
+removed the `darkwing-r233_default` network.
+
+N1, found in the process sweep after the run: a `sleep 60` was left with its cwd in `packages/cli`.
+`stack-upgrade.test.mjs:312` spawns `flock LOCK sleep 60`, and its `t.after` SIGKILLs only the flock, so
+flock's child outlives the test by up to 60 s. It exited on its own. Row 232's T20
+(`stack-release.test.mjs:370`) spawns its holder `detached` and kills the group with `process.kill(-pid)`.
+The fix is the same two lines. That test is one of m1's killers.
+
+Sage ruled it a fix now (sage-1707), and 08db6ac3f makes it, test only. After the gate's d99166ade
+the only change outside this file is that test:
+
+```
+$ git diff --stat d99166ade 08db6ac3f
+ packages/cli/tests/stack-upgrade.test.mjs | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+```
+
+The gate stands on Sage's ruling. The rerun is the whole `stack-upgrade.test.mjs` singly plus m1, in
+Sage's slot, with a sweep for a leftover `sleep` afterwards.

agents/darkwing/work/queue-240/BUILD.md

@@ -0,0 +1,173 @@
+# Row 240 (I4): root's host check, its pins and the boot unit
+
+Brief: `docs/plans/2026-10-20_installer-rows.md` section I4, blob `4a5a65020f00` (commit b00d7d94d, rev 2665,
+the pin row 240 carries; the I3 carry items came in with it). Sage split it out of I3 (sage-1650). Gitea #1746, Vikunja P19 #432. Owner Darkwing, reviewer Filbert, gate owner Sage.
+Design: row 195 DESIGN r6 B2, `agents/darkwing/work/queue-195/DESIGN.md` at b7239bb66, :262-303 (the script,
+the three callers) and :839-860 (files, test cases, mutants). Where the brief and r6 differ, the brief wins.
+
+## Files
+
+Drafted on `darkwing/row240-r1` from d99166ade (row 233's candidate) while row 233's gate ran, then applied
+as one patch onto row 233's landing, 57f59e0c3, on `darkwing/row240-r2` (sage-1753). It applied cleanly; between
+the two bases the only change on this row's paths is 233's N1 test fix in `stack-upgrade.test.mjs`. Row 234
+then landed as c771a36f4 on 57f59e0c3. Sage preferred that the gate run with it in the tree (sage-1773), so both
+commits were picked onto c771a36f4 as `darkwing/row240-r3`. That was a clean pick: the 42 paths changed from
+57f59e0c3 to c771a36f4 share none with this row's 9.
+
+- `scripts/case1-pins.sh` (new, 0644): `PIN_PROFILES_VERSION`, `PIN_PROFILE_SHA256`, `PIN_BUBBLEWRAP_VERSION`,
+  r6 section 0's values.
+- `scripts/case1-hostcheck.sh` (new, 0755): the seven items and `--check`, `--enforce`, `--upstream`.
+- `packages/cli/systemd/mosaic-hostcheck.service` (new): the boot oneshot.
+- `packages/cli/tests/case1-hostcheck.test.mjs` (new, 16 tests). The cli suite's `tests/*.test.mjs` glob picks
+  it up.
+- `docs/guides/host-run-sheet.md` section 4: the install lines that replace "Install them from row 240's run
+  sheet lines once it lands", plus rollback, drift recovery and `--upstream` before a re-pin window. Sections
+  3, 6, 8 and 10 for the I3 carry items below.
+- `scripts/stack-upgrade.sh` and `packages/cli/tests/stack-upgrade.test.mjs`: I3 N1 below.
+- `docs/TOOLS.md`: a new subsection "Root's host check (`scripts/case1-hostcheck.sh`, row 240)" after the
+  upgrade driver's.
+
+Brief line 257 said I3's `stack-upgrade.sh` doesn't change. Sage's ruling sage-1727 widened the row to it for
+N1 alone. Its default `STACK_UPGRADE_HOSTCHECK=/usr/local/lib/mosaic-stack/hostcheck.sh` is where the run
+sheet installs this script.
+
+## Carried from I3
+
+Filbert's row 233 approve (Gitea 29922) left five notes. Sage ruled N1, N4 and N5 into this row and N2 and N3
+to DEFERRED.md (sage-1727).
+
+| Note | Change |
+|---|---|
+| N1: `stack-upgrade.sh` exits 1 `args-failed` when the args move after A5 fails, but exit 1 means the old copy runs | The move's failure exits 5 `args-failed`. The header, TOOLS.md's step 5 and exit line, and run sheet section 6's exit list name exit 5 and what root does: move the new file the result line names into place. Test `row 240: I3 N1: a failed args move after A5 exits 5 ...` makes `/etc/mosaic-stack` read-only at confirm and checks exit 5, the step names, `args rc=1`, the result line, both units on the new copy, the old args file's bytes and the new file beside it. The step log regex takes `exit=5`. Mutant M8. |
+| N4: section 3's `npm install` has no npm on root's PATH, and the `--claude` path is unnamed while `node_modules/.bin/claude` is a symlink `case2-unit.sh:140` refuses | The install line runs with section 2's pinned node first on PATH (the postinstall runs `node` too). The `--claude` path is `node_modules/@anthropic-ai/claude-code/bin/claude.exe`, and a `--version` line catches the postinstall's 500-byte stub. |
+| N5: sections 8 and 10 lack precheck lines | Each gets "Precheck line: none" and its missing line. |
+
+Exit 5 is new rather than 2 because 2 means both units are stopped, and here both run. Exit 4 stays usage.
+
+The `claude.exe` path comes from the 2.1.304 package itself: `npm view` gives `bin.claude` as `bin/claude.exe`,
+and its `install.cjs` hardlinks the platform binary over that placeholder, or copies it across devices, then
+sets 0755. I downloaded the tarball into `/mnt/storage/scratch/tmp/r240/cc304` and read it; nothing ran. The
+run sheet says a newer pin needs the same check.
+
+## The brief, item by item
+
+| Brief line | Where |
+|---|---|
+| 247 `case1-pins.sh` holds the three pins | `scripts/case1-pins.sh`; the pins test checks the values against r6's |
+| 248-249 seven items, `--check` exits 0 or 1 | `items()` and the final dispatch; the check tests |
+| 250-251 `--enforce`: `apparmor_parser -R`, `root:root 0700`, `DRIFT`, a log line, exit 0 | `enforce()` and `stop_bwrap()`; the four enforce tests |
+| 252 `--upstream` compares the current deb to the pin | `upstream()`; the upstream test |
+| 253 the boot oneshot | `mosaic-hostcheck.service`; the boot unit test |
+| 254-255 fakes for every host tool, r6's seven case groups, seven mutants | the test file; Tests and Mutants below |
+| 257 the I3 run sheet item points here | run sheet section 4 |
+
+## Tests
+
+Fakes on PATH, each logging its argv to `$HC/calls.log`: `aa-status`, `dpkg`, `dpkg-statoverride`,
+`apparmor_parser`, `systemd-run`, `stat`, `chown`, `chmod`, `apt-get`, `dpkg-deb`. `host(t)` builds a scratch
+root (`/etc`, `/proc/sys`, `/usr/bin/bwrap`, `/var/log`) and a lib dir with a copy of the script and fixture
+pins that hold the fixture profile's sha256. Every run passes `--root`.
+
+r6's case groups (:843-856) against the tests:
+
+| r6 case | Tests |
+|---|---|
+| `--check` exits 0 with all seven, 1 with each failing alone, its line naming it | `check: exits 0 ...`, `check: exits 1 with each item failing alone ...`, plus one test per item for the item's edge cases |
+| item 3: a second file naming `bwrap` as a word, `/{usr/,}bin/bwrap` included; passes with the profile alone | `check: item 3 ...` |
+| item 4: `unpriv_bwrap (enforce)` or a trailing space fails; the argv carries `-p NoNewPrivileges=yes` and the 2a' properties | `check: item 4 ...` checks the whole argv |
+| item 7: the floor at 732 fails | `check: item 6 ...; item 7 ...` (733 passes as the control) |
+| `--enforce` exits 0 on a pass and every failure; unload, close, `DRIFT`, one log line; `DRIFT` present with every item passing still closes | `enforce: a pass ...`, `enforce: each failure ...`, `enforce: with DRIFT present ...` |
+| `--enforce` never calls `dpkg-statoverride` with `--update`, `--add` or `--remove` | `enforce: no unload ...; never writes the statoverride` (every call is `--list /usr/bin/bwrap`) |
+| a bubblewrap version other than the pin is a line, not a failure | `check: a bubblewrap version other than the install pin ...` |
+| `--upstream` against a differing deb prints the difference, exits 0 | `upstream: ...` (also: a match, a deb with no profile, a failed download) |
+| the unit: `Type=oneshot`, `After=apparmor.service`, `[email protected]`, runs `--enforce` | `boot unit: ...` |
+
+The last test also checks that the repo script reads `scripts/case1-pins.sh` beside it, that bad usage exits
+2, and that a non-root run without `--root` refuses.
+
+Singles are the two files that run a changed script: `case1-hostcheck.test.mjs` and `stack-upgrade.test.mjs`.
+Sage asked (sage-1759) whether `stack-release.test.mjs` or `stack-release-external.test.mjs`, which share
+`stack-release-fixture.mjs`, run `stack-upgrade.sh` or `case1-pins.sh`. They don't. `grep -cF` for
+`stack-upgrade`, `case1-pins`, `case1-hostcheck` and `hostcheck` gives 0 in all three files; the control
+`stack-release.sh` gives 2 in the fixture and 8 in `stack-release.test.mjs`. `scripts/stack-release.sh` names
+`stack-upgrade.sh` once, in a comment (:2061). The gate's cli suite runs both files anyway.
+
+## Mutants
+
+r6's seven (:858-860) and one for I3 N1, scripted in `~/darkwing-scratch/r240/mutants.sh` with r233's method: a checked backup,
+an exact replacement that must match once, `bash -n`, the named killer by `--test-name-pattern`, the restore
+and a sha256 check. A dry run matched all eight once each. Results below.
+
+| Mutant | Change | Killer |
+|---|---|---|
+| M1 | `--enforce` exits 1 after the stop | `enforce: each failure exits 0 ...` |
+| M2 | `[ ! -e "$DRIFT" ] \|\| had=1` becomes `true \|\| had=1` | `enforce: with DRIFT present ...` |
+| M3 | item 1's `dpkg -S` becomes `owner=""; rc=1` | `check: item 1 fails when a package owns ...` |
+| M4 | item 3's `grep -rlw bwrap` becomes `grep -rlF /usr/bin/bwrap` | `check: item 3 ...` |
+| M5 | item 4's `[ "$label" = "$LABEL" ]` becomes a substring match | `check: item 4 ...` |
+| M6 | item 4 drops `-p NoNewPrivileges=yes` | `check: item 4 ...` (argv) |
+| M7 | item 7's `-gt` becomes `-ge` | `check: item 6 ...; item 7 fails with the floor at 732 ...` |
+| M8 | `stack-upgrade.sh`'s `finish 5 args-failed` becomes `finish 1 args-failed` (I3 N1) | `row 240: I3 N1: a failed args move ...` |
+
+## Deviations
+
+- Repo name `scripts/case1-hostcheck.sh` (r6), installed as `/usr/local/lib/mosaic-stack/hostcheck.sh`, the
+  name in brief line 239 and I3's `stack-upgrade.sh` default. r6's apt hook line says `case1-hostcheck.sh`;
+  the run sheet's hook uses the installed name.
+- `stat` is a fake too. r6 lists seven fakes; a test can't make a root-owned file, so item 5's `stat` reads a
+  fixture.
+- Item 7 with no Console unit installed reads the port as 1023 and says so ("1023, because no Console unit
+  is installed"). Until I2 installs the unit the floor must be above 1023. A unit with no `--port` fails.
+- Item 4 runs under `timeout 60`. A hung `systemd-run` would otherwise hang the apt hook and the boot unit.
+
+## Decisions
+
+- Fail closed where r6 is silent:
+  - pins with no 64-hex sha fail item 1;
+  - `dpkg -S` exit 1 (no owner) passes, exit 0 fails with the owner, any other exit fails with the code;
+  - a failed `aa-status` fails item 2 and counts as loaded, so `--enforce` tries the unload.
+- `--root DIR` is the test seam (r6 :840). Root refuses it; a non-root user needs it. Both exit 2. Root runs
+  with `PATH=/usr/sbin:/usr/bin:/sbin:/bin`.
+- `DRIFT` is append-only (`<stamp> <failed line>`), and `--enforce` never removes it. The log line is written
+  only when the stop runs: `<stamp> enforce stop items=<ids or none> drift-before=<0|1> unload=<rc=N|no-file|skipped> chown=N chmod=N`.
+- `--upstream` exits 1 when the download or the unpack fails, since it then compared nothing. A deb without
+  the profile file is a difference (exit 0), per r6 :302-303.
+- The bubblewrap note reads the version from `dpkg -s bubblewrap`.
+- The run sheet's recovery steps (`chown root:mosaic`, `chmod 0750`, `apparmor_parser -r`, then `--check`
+  before root removes `DRIFT`) are mine. r6 says only that root removes `DRIFT` in a reviewed step.
+
+## Run environment
+
+Worktree `/mnt/storage/scratch/darkwing-r240b`, branch `darkwing/row240-r3` on c771a36f4, with `node_modules`
+linked to the canonical checkout's. Node v26.8.1, kernel 7.2.2-1-cachyos, 16 CPUs, TMPDIR
+`/mnt/storage/scratch/tmp/r240`, compose project `darkwing-r240b`. Sage's slot (sage-1773, 06:16Z). Each run is
+one chain behind `busy.sh`, launched from `/`: `~/darkwing-scratch/r240/run-all.sh` checks the HEAD pin and a
+clean tree, runs the singles, then the mutants (8 killed, none surviving, the tree clean after), then the gate
+(the cli suite and every `scripts/test-*.sh`), each stopping the chain on failure, then sweeps `/proc` cwd links
+for anything left in the r240 trees.
+
+## Results
+
+Run r1, 06:17:10Z on 47ec9fe2f, failed at the singles. `case1-hostcheck.test.mjs` passed 16/0/0, and
+`stack-upgrade.test.mjs` went 20 pass, 1 fail. The failure was the N1 test's own `t.after` hook, which ran
+`chmodSync(e.etc, 0o755)` after the fixture's cleanup had already removed the scratch root, so it threw ENOENT.
+Every assertion in the test body had passed, exit 5 included. The fixture's cleanup runs `chmod -R u+w` on the
+root before `rmSync`, so the 0555 dir never needed the hook. b45852daa drops it and changes nothing else. The
+mutants and the gate didn't run. The sweep found nothing left. Sage counted r1 as this slot's one failure
+(sage-1788).
+
+Run r2, 06:20:41Z to 06:33:28Z on b45852daa, passed. The counts come from awk over the .out files
+(`~/darkwing-scratch/r233/sum.sh`):
+
+| Step | Result |
+|---|---|
+| `case1-hostcheck.test.mjs` | 16/0/0 |
+| `stack-upgrade.test.mjs` | 21/0/0 |
+| c0 control | exit 0 |
+| M1-M8 | 8/8 killed, none survived, every restore's sha256 matched, tree clean after |
+| `packages/cli` suite | 639/0/0 |
+| `scripts/test-*.sh` | auth 15, conductor 17, config 31, discord 78, extension-package 18, foundation 44, land-work 86, queue 156 node + 28 selftest, release 14, task 98; 585 pass, 0 fail |
+| Gate total | 11 suites, 1224 pass, 0 fail |
+| Sweep | nothing left in the r240 trees; the compose network was removed |
+
+This commit adds only these BUILD.md lines. No test reads BUILD.md.

agents/darkwing/work/queue-245/BUILD.md

@@ -0,0 +1,91 @@
+# Row 245 build: Duckworth's N1-N3 on `scripts/case1-accept.sh` (row 195 follow-up)
+
+Duckworth approved row 195's manifest round 1 (duckworth-0088, `agents/duckworth/work/row195/REVIEW-m1.md`
+at 6afcee2a5) with three notes that don't block. Row 195's code landed as b65014647, and the notes are in
+`docs/plans/DEFERRED.md` (d6cff0cdd). Row 245 carries them: brief `docs/plans/2026-10-20_hub-own-uid.md` §
+"Row 195 follow-up" at 62ddc96cc, owner Darkwing, reviewer Duckworth, gate owner Sage (sage-1923).
+
+The branch is `darkwing/row245`, on 62ddc96cc. Its first commit is a cherry-pick of `darkwing/row195-n1`
+1e3c4767c, which was written on 37171f65b and never run. The script, test and TOOLS.md blobs are the same
+as in 1e3c4767c, and none of those paths changed between 37171f65b and 62ddc96cc.
+
+## What changes
+
+N1. F9 ran `$ROOT$NODE` as root (`case1-accept.sh:298` at 37171f65b) before F10 checked that `--node` is
+the pinned path. Duckworth offered two fixes: F9's parse through `AS_USER`, or F10's path check first. I
+took the path check, plus one more:
+- F9 now runs node only when `--node` equals `/opt/mosaic-stack/node-<--node-pin>/bin/node`.
+- Then `not_root_only` walks from that file up to `/`. Each entry must be the running user's (root's on the
+  host) with no group or other write, the rule `case2-unit.sh` `root_only` applied when it rendered the
+  units. A symlink fails it, because its mode is 777. The first entry that breaks the rule goes in the
+  evidence.
+
+I didn't run the parse through `AS_USER`. That would hand a check about a root file to the stack's user,
+and a process running as `mosaic` shares that node's uid. Whether it could change what node prints then
+turns on the host's ptrace setting, and the root-only check doesn't depend on that. Sage agreed in
+sage-1877. Rechecking ownership costs one loop and doesn't depend on
+how the host was installed.
+
+N2. The header (:9-15) and the `docs/TOOLS.md` entry now list what root runs: `systemctl show` and
+`is-enabled` (F1, P11), `curl` on the loopback healthz (F2), `sudo -l` (P1, P3), `sudo -u jarvis bwrap
+--version` and `hostcheck.sh --check` (P9), and node for F9 under the rule above.
+
+N3. F6 matched `--claude` by prefix, so `/opt/mosaic-stack/claude-<pin>/../claude-2.0.9/...` passed the
+path check. F6 now fails on any `..` segment, before it runs `--version`. F10 compares for equality, so
+it needed no change.
+
+Row 195's BUILD.md gets a correction entry for deviation 6. Row 195's DESIGN.md is unchanged. Its "either
+works" wording at `DESIGN.md:336-338` is superseded by gosalyn-0087 (root writes `dev.args` at W10), and
+it stays in place: an approved design isn't edited (sage-1877).
+
+## Tests
+
+`packages/cli/tests/case1-accept.test.mjs`:
+- The node stub touches `node-as-root` in the state directory when something runs it outside the fake
+  `sudo` (which sets HOME to the stack's home). `host()` sets the node file's directories and the scratch
+  root to 0755, so the umask can't fail F9.
+- "every check passing" also asserts that root ran the pinned node.
+- New: "F9 won't run --node as root off the pin path or with a writable directory above it". Another node
+  path fails F9 and F10, with no root run. A group-writable `bin/` and a symlinked node each fail F9
+  alone, with the bad path in the evidence and no root run.
+- The F6 test gains a `..` case: a path under `claude-<pin>/` by prefix that names 2.0.9's binary, which
+  prints the pin. F6 alone fails, with "has a .. segment".
+
+That makes 23 tests. All 23 pass on Sage's slot (results below).
+
+## Mutants
+
+The twelve from row 195 still apply, unchanged. These four are new, each one exact replacement:
+
+| # | Mutant | Expected killer |
+|---|---|---|
+| 13 | F9 runs any `--node` (the pin check becomes `true`) | F9 won't run (another node) |
+| 14 | F9 skips the ownership walk (`bad=""`) | F9 won't run (writable `bin/`, symlink) |
+| 15 | `not_root_only` checks only the file, not the directories above it | F9 won't run (writable `bin/`) |
+| 16 | F6 accepts a `..` segment | F6 stub, path and `..` |
+
+The brief's gate asks for a mutant for each of N1 and N3. Mutants 13-15 are N1's, and 16 is N3's.
+
+## Slot plan
+
+Same shape as row 195's steps, on this row's tip: the single test file, then the sixteen mutants, then
+the gate (the cli suite and every `scripts/test-*.sh`), each behind the busy checks and chained with
+`&&`. The scripts are in `/mnt/storage/scratch/darkwing-245-out/`.
+
+## Slot results (grant sage-1961, 2026-10-21)
+
+All three steps ran on 0590a29fc with node v26.8.1, launched from `/`. Both busy checks were CLEAR
+before each step.
+
+- Singles, 11:27:46-11:27:59Z: `case1-accept.test.mjs` passed 23, failed 0.
+- Mutants, 11:28:10-11:31:20Z: all 16 killed, each with exit 1. The runner restored the script, and
+  its sha256 875bb5b7 matches the committed blob. Rows 1-12 died as in row 195. 13, 14 and 15 died on
+  "F9 won't run --node as root off the pin path or with a writable directory above it". 16 died on
+  "F6 fails on a stub that prints nothing, on a path outside claude-<pin> and on a .. segment".
+- Gate, 11:31:20-11:42:51Z: the cli suite passed 664, failed 0, skipped 0. Every `scripts/test-*.sh`
+  exited 0: auth 15, conductor 17, config 31, discord 78, extension-package 18, foundation 44,
+  land-work 86, queue 28 (its node part 156/0), release 14, task 98. That's 429 selftests, none failed.
+- Afterwards no process had its cwd in the worktree, the out dir or TMPDIR, and the
+  `darkwing-r245_default` network was gone.
+
+Logs: `/mnt/storage/scratch/darkwing-245-out/` (`step1.log`, `mut.out`, `mut/m1-16.log`, `gate.out`).

agents/darkwing/work/queue-251/BUILD.md

@@ -0,0 +1,106 @@
+# Row 251 build: T27 lists no identities right after `ssh-add -t 1` (Vikunja #453)
+
+Brief `docs/plans/2026-10-21_t27-ssh-add-lifetime.md` (rev 2931), Mos ruling mos-1185 item 2, assigned in
+sage-2075. Owner Darkwing, reviewer Dewey, gate owner Sage. Branch `darkwing/row251` from 3b0aef995,
+claimed in-progress at rev 2938.
+
+## Step 1: the failure names its cause (e5e4b2e5a)
+
+T27's two lists now carry a message that prints only when they fail. It gives the time from addKey's
+start to its resolve and to each `ssh-add -l` call, the hrtime at each with how far into its second it
+fell, `/proc/uptime` at each, and whether the agent process and its socket were still there. The checks
+themselves did not change. The commit holds nothing else.
+
+## Step 2: the cause
+
+ssh-agent counts a key's lifetime in whole seconds of CLOCK_BOOTTIME, at the add and at the reap. I read
+OpenSSH 10.5p1, the version on dragon-lin (`ssh -V`: OpenSSH_10.5p1), at tag V_10_5_P1 (ssh-agent.c
+sha256 873691c4, misc.c sha256 ee467f43):
+
+- `misc.c:1790-1798` and `:1828`: `monotime()` returns `ts.tv_sec` of `clock_gettime(CLOCK_BOOTTIME)`,
+  falling back to MONOTONIC. The fraction of the second is dropped.
+- `ssh-agent.c:1315`: the `-t` constraint sets `*deathp = monotime() + seconds`. Lines 1410 and 1598
+  do the same for the agent's default lifetime.
+- `ssh-agent.c:1064`: the reaper drops a key when `now >= id->death`, `now` being `monotime()` again.
+- `ssh-agent.c:2650`: the main loop runs `reaper()` after every poll, before it reads requests. A list
+  that arrives after the boundary sees the key gone.
+
+So a key added at second s plus a fraction f dies at s + N, and `-t N` keeps it N - f seconds, between
+N - 1 and N. With `-t 1`, an add late in a second leaves the key milliseconds to live. That matches
+Sage's probe in the brief: 8 of 80 `-t 1` adds missed, each one made at 0.9947-0.9973 of a monotonic
+second and finished at 0.998-0.0008, and none earlier in the second missed. It also matches proof 5's
+failure, where the first list ran 31.9 ms into the test and found no identities.
+
+Node's hrtime is CLOCK_MONOTONIC. BOOTTIME differs from it by the time the host spent suspended. On
+dragon-lin the difference read 0.000001 s at 19:09Z, so a monotonic second boundary is a BOOTTIME one
+here.
+
+`addKey` and the agent start are not the cause. `addKey` passes the lifetime through as `-t`
+(`host-run.mjs:90`), and the agent starts with no default lifetime (`:175`). Production adds the key
+with `timeout + 30` (`:180`), where losing up to a second makes no difference. The only caller that
+can't afford the lost fraction is T27, which asks for 1 s. The fix belongs in the test's lifetime choice,
+and `host-run.mjs` doesn't change.
+
+The slot confirms this against T27 itself (below), not just from the source.
+
+## Step 3: the fix (this commit)
+
+T27 adds the key with `-t 2`. The agent then keeps it more than 1 s and at most 2 s. The first list
+runs milliseconds after the add, so it has over a second of margin even under load. The sleep before
+the second list grows from 2.5 s to 3.5 s, which keeps the old 1.5 s margin past the new 2 s ceiling.
+Both checks stay: listed after the add, gone after the lifetime. A comment above the add says why the
+lifetime is 2.
+
+I considered `-t 3` with a 4.5 s sleep for a 2 s floor. One second of floor is far above anything the
+first list has needed (31.9 ms in proof 5), and the concurrent-suite run below tests it under load, so I
+took the smaller change.
+
+## Base
+
+The branch stays on 3b0aef995. By 19:15Z origin/refactor was at 6096b051b, after rows 66 and 243
+landed. `git diff 3b0aef995 6096b051b` touches neither `packages/bus/src/host-run.mjs` nor
+`packages/bus/tests/host-run.test.mjs`, so there's no rebase (sage-2084). Row 243 did change
+`packages/bus/tests/process.test.mjs`. My slot's bus suites run that file as it was at 3b0aef995, and the
+gate rerun on Sage's slot runs it as landed.
+
+## Prediction for part A on e5e4b2e5a (written before the slot)
+
+The hook starts `ssh-add -t 1` at the given fraction of a monotonic second. From the brief's probe, the
+agent stores the key about 3 ms later. The first list reaches the agent a few ms after addKey resolves:
+Node's exit event, the mark, and `ssh-add -l`'s own start. A red needs the add to land before the second
+boundary and the list to land after it.
+
+- 0.990: green. The add and the list both land before the boundary.
+- 0.993, 0.995, 0.996, 0.997: red expected. The add lands before the boundary, the list after. At 0.993
+  and 0.997 I'm less sure, because the list (at 0.993) or the add (at 0.997) can land right at the
+  boundary. A green at either is in line with the cause, and so is a red.
+- 0.998: green. The add lands after the boundary, so the key gets almost a full second.
+
+Every red should show "first list got" an answer with no SHA256 line. It should also show addKey
+resolving before a second boundary and the first list starting after it or within a few ms of it, with
+the agent alive and its socket present.
+
+Under sage-2084's rule, on e5e4b2e5a only a red at 0.990 or 0.998 counts toward the stop, and two such
+reds stop the run. On the fix commit any red counts, and two stop it. In parts B to D, the first red stops
+the run.
+
+## Slot plan
+
+All scripts are in `/mnt/storage/scratch/darkwing-251-out/`, launched from `/`, each behind the busy
+checks and chained with `&&`, TMPDIR under `/mnt/storage/scratch/tmp`.
+
+1. Confirmation. `align-hooks.mjs` is a load hook, outside the repo, that serves `host-run.mjs` with
+   `addKey` wrapped to start `ssh-add` at a chosen fraction of a monotonic second. T27 runs unchanged
+   under it, alone (`--test-name-pattern`). It runs at fractions 0.990, 0.993, 0.995, 0.996, 0.997 and
+   0.998, three times each:
+   - on e5e4b2e5a (step 1, `-t 1`). Expected: some first lists fail, and the step 1 message shows the
+     add's resolve and the list on either side of a second boundary, with the agent alive and the
+     socket present. These reds are the point of the run.
+   - on the fix commit (`-t 2`). Expected: all 18 pass.
+2. `host-run.test.mjs` whole, once, on the fix commit.
+3. The bus suite whole, three times in a row.
+4. The bus suite whole in two clean worktrees at the same commit, started together.
+
+## Slot results
+
+Not run yet.

agents/duckworth/README.md

@@ -3,5 +3,5 @@
 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 row 195 settles per-agent identity, it pushes only its own `duckworth/*` branches
+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/gizmoduck/work/queue-234/BUILD.md

@@ -0,0 +1,310 @@
+# Row 234 (#436a row a, Gitea #1740): host enrollment, store records and bus schema 3i to 3j
+
+Gizmoduck, 2026-10-21. Reviewer Duckworth, gate owner Sage. Lands by 10-25, before the .53 and .54 installs
+(mos-1134).
+
+- Brief: `docs/plans/2026-10-20_host-credentials.md`, section "Machine grant row a: enrollment, store records
+  and migration 3i-3j", blob 64451be5 (queue rev 2617).
+- Design: `agents/gizmoduck/work/machine-grant/DESIGN.md` r6, f9039682e on `gizmoduck/machine-grant-design`,
+  approved by Duckworth (duckworth-0064, REVIEW-r6.md at 8ea792256). Not reopened here. Cites "r6:" are lines
+  of that file.
+- Grant event rule: #436b section 7, fa5658941 on `megavolt/row199`,
+  `agents/megavolt/work/436b/DESIGN.md:431-490`, file sha256
+  96510b83778e79a71b33d0d5f6fd0c806dfe74f6de315ff4a9f1fbe5620f6c69, approved by Duckworth (duckworth-0067).
+- Base: origin/refactor 8fede5fc6, with rows 199 (cb5fdb064) and 210 (f5753c0e8) landed. Branch
+  `gizmoduck/row234`. Code cites are `path:line` at 8fede5fc6 unless they say otherwise.
+
+## Names: r6 against section 7
+
+r6's `grant.*` and `host.enroll.*` names are `body.action` values on `action.allowed` events, not event
+kinds. The `events` kind CHECK isn't rebuilt. Four r6 names move under `grant.`:
+
+| r6 | This row |
+|---|---|
+| `host.enroll.step` | `grant.host.enroll.step` |
+| `host.enrolled` | `grant.host.enrolled` |
+| `host.checked` | `grant.host.checked` |
+| `host.removed` | `grant.host.removed` |
+
+Only the consume record carries `decision`: `{operation: 'grant.host-enroll', decision}`. Every other
+guarded body names the decision `grantDecision`, so r6's `decision` field in step, enrolled and failed bodies
+is `grantDecision` here. The actor of every guarded event is `actor_role` NULL with `actor_run` 'grant',
+and `body.by` names the caller the broker checked.
+
+## Split (r6 section 12 Q-S4)
+
+Row a builds:
+
+1. **Schema 3i to 3j.** `migrations/3i-3j.sql` adds `hosts` and `host_grants` (r6 S1, primary keys
+   (business, host) and (business, agent, host)) and the guard trigger: an `action.allowed` whose
+   `body.action` or `body.operation` GLOBs `'grant.*'` aborts unless the actor is (NULL, 'grant').
+   `SCHEMA_VERSION` 3j, a migration test with a step that fails partway.
+2. **Grant event writer.** A private session-less broker writer for guarded events. `#event` doesn't change.
+   `recordEvent` refuses `reserved-event` for the guarded namespace.
+3. **The `grant` raise frame.** `decision.raise` takes `grant` only with `credential.mint`, only from the chief
+   (`grant-chief-only`), and in row a only with `method: 'host-enroll'`. Any other method refuses
+   `invalid-request` until row b adds `host`. E1's checks, the `ssh-keyscan` set compare before the raise
+   transaction, and the rendered block.
+4. **Enrollment executor.** `#consumeGrant`, the start on the human's cli yes (X1), E2 steps 1 to 4, the
+   installer key at `<configDir>/secrets/hosts/<business>/<hostId>/installer`, the failure cleanup, and the
+   start reconcile for enrollments: the `registry` step undo, and a resolved-yes unspent enrollment ending
+   `grant.failed interrupted` (X3).
+5. **`hosts.check` and `hosts.remove`** (E4), with `mosaic hosts status|check|remove`.
+6. **`tools/host/`**: `mosaic-keys`, `mosaic-keys-write`, `mosaic-keys.sudoers`, `mosaic-keys.sshd.conf` (E3).
+7. **`host.run` on the store** (X4 first and third bullets): it reads the `hosts` and `host_grants` records
+   and the Approve record check, and at start the runtime gives `Credentials` a reference per `host_grants`
+   record. The loader refuses `hosts` at the top level and in a role (S1). Row 210's tests move to store
+   fixtures.
+8. **Reader filter** (duckworth-0067 N1): every grant-evidence reader in this row (status, the start
+   reconcile, `openGrantDecisions`) filters `kind = 'action.allowed' AND actor_role IS NULL AND actor_run =
+   'grant'`, with a test that an `action.refused` look-alike and a session-written one are ignored.
+   `hosts.remove`'s `hostLineLeft` reader is one of them (duckworth-0079 M4).
+
+Row b keeps the `host` method's raise binding (R4), the grant executor (X2), the grant rows of X3, X5,
+`Credentials.register`/`claim`/`abortClaim`, revoke (section 6) and `sweep`. So row a has no way to make a
+`host_grants` record outside a test fixture, and from its landing to row b's no agent holds a host grant
+(r6 N9, the run sheet strips row 210's keys).
+
+Tests in row a (r6 section 10): G1 and G5 for the `host-enroll` raise, G6 and G10 for the enrollment
+executor, G11's enrollment cases, G14, G15, G16, G17, G18, G20, G21 (its `host-line-left` case reads an
+event fixture until row b writes `hostLineLeft`), G25, the migration test, the trigger cases, the reader
+filter test, and row 210's T-tests on store fixtures. Row b: G2 to G4, G7 to G9, G11's grant cases, G12,
+G13, G19, G22 to G24, G26 to G28.
+
+## Early check items (duckworth-0079, REVIEW-build-split.md 10672772e on `duckworth/reviews`)
+
+Moves into row a:
+- M1. G4 for the `host-enroll` block (r6:240-242): a question can't forge the block, and the 4096-character
+  limit holds with the block appended. G4 for the `host` block stays in row b.
+- M2. The tag function (r6:265-266), because E2 step 2 tags the installer line. G24's first sentence moves
+  here: names of 64 characters with `.` and `_` give distinct tags of the fixed length. The `sweep` half
+  stays in row b.
+- M3. A store-fixture test that `host.run` refuses `host-not-granted` for no record, an unresolved decision,
+  a decision resolved by an arbiter, the tester or an agent or not via cli, a consume record with operation
+  `grant.host-enroll` in place of `grant.host`, and an unspent decision (X4 first bullet, r6:593-596). A
+  restart test that a `host_grants` fixture gives `Credentials` a reference (X4 third bullet).
+
+G21's `host-line-left` case:
+- F1. The fixture goes through this row's private grant writer in the real shape: `action.allowed`, actor
+  (NULL, 'grant'), `body.action` 'grant.failed', `body.host`, `body.hostLineLeft`. No raw SQL around the
+  trigger.
+- F2. `hosts.remove` reads `body.hostLineLeft` from any guarded body, not only `grant.failed`.
+- F3. Decided: a guarded body that carries `hostLineLeft` also carries `host`. Row b adds `host` to
+  `grant.revoke.closed`, so its body is `{tag, host, hostLineLeft}` (r6:716 has `{tag, hostLineLeft}`).
+  The reader matches on `body.host`, and doesn't map tags back to hosts through `grant.step`. A direct
+  field is one equality in SQL, and a tag lookup would add a second reader that the N1 filter also has to
+  cover.
+- F4. Row b carry: "no later `sweep` cleared it" (r6:403) needs `grant.sweep`, which only row b writes. Row
+  b adds the sweep clear to `hosts.remove` with a G21 case, and its G8 or G13 shows `hosts.remove`
+  refusing after a real `hostLineLeft` write, not only after the fixture. Until then row a's check is "any
+  guarded `hostLineLeft` for this host refuses".
+
+## Mutants (r6:838-883, numbered here)
+
+Row a, killed on this row's tree:
+
+| # | Mutant |
+|---|---|
+| A1 | drop the chief check |
+| A2 | start the executor on a `credential.mint` with no `grant` |
+| A3 | start it on an arbiter resolve |
+| A3b | start it on a `cli` yes by someone other than the human (duckworth-0083 N8) |
+| A4 | start it on `no` |
+| A5 | skip the keyscan compare |
+| A6 | compare only one key |
+| A7 | write the private key into the event body |
+| A8 | drop the "not yet enrolled" check in E2 step 1 |
+| A9 | drop the `hosts` primary key |
+| A10 | skip the start check for a resolved, unspent enrollment decision |
+| A11 | `host.run` reads the business file instead of the grant record |
+| A12 | build the tag without the business |
+| A13 | drop `from=` in the writer |
+| A14 | let the writer touch a line outside the tag pattern |
+| A15 | drop `O_NOFOLLOW` on the user file |
+| A16 | drop one group from the writer's refused list |
+| A17 | drop the user pattern check before the path use |
+| A18 | treat a `privileged` entry as enough without `users` |
+| A19 | let the writer accept a sudo user not in `privileged` |
+| A20 | trigger: drop the `body.operation` arm, so the consume record passes from a session |
+| A21 | trigger: accept actor_role NULL with any actor_run |
+| A22 | a grant reader drops the `kind = 'action.allowed'` or actor filter. The runner splits it: A22a drops the kind, and G21's `action.refused` look-alikes kill it. A22b drops the actor, which the trigger can't stand in for, because 3i-3j adds the trigger without checking old rows. Its killer is the grant-migration test "A22b, sage-1703": a session-written `grant.host.removed` with `hostLineLeft` and a `grant.host-enroll` row from 3i, migrated to 3j, where `hosts.remove` still removes the host and `reconcileGrants` ends nothing |
+| A23 | `host.run` skips the Approve record check (any `host_grants` record is enough) |
+
+Row b keeps the rest of r6's list: the `ready` check, the three hash compares, the definition check, the
+install and record order, `remove` on a verify failure, both start sweeps, the reconcile's remote `remove`,
+the `grant.step` before install, revoke leaving the record, `register` before `issue`, the abort check and
+the `await` before `issue`, revoke and an unreferenced claim, `sweep` and any `mosaic-` line, revoke's host
+step order, claim before consume, the resolved unspent grant decision, an async `commit`, `hosts.revoke`
+through `credential-verbs.mjs`, the revoke marker reconcile, the upsert, the undo past `grant.revoked`, the
+abort after step 5 and a missing `bus.tester` as dev.
+
+## Broker functions this row touches (sage-1677)
+
+For row 236 (Megavolt), which rebuilds on this landing. Old lines are `packages/bus/src/broker.mjs` at
+8fede5fc6, new lines are at the last commit that changed this file (they moved by 10 after `runEnrollment`
+went in). The planned list is kept in this file's history (827b89ea6).
+
+Changed:
+- `constructor` (:279): one more option, `hostGrant`, the object `host-grant.mjs` builds.
+- `recordEvent` (old :1243-1251, new :1606): one more refusal. An `action.allowed` whose `body.action` or
+  `body.operation` is a `grant.*` name refuses `reserved-event`.
+- `request()` (old :1362, new :1726): two routes ahead of the sync path, a `decision.raise` with `grant` to
+  `#raiseGrant` and the `hosts.*` verbs to `#requestHosts`. Both are async.
+- `requestHost` (old :1712-1795, new :2079): the business-file lookups (old :1730-1736) become one
+  `#hostAccess` call, in the same transaction as `#agent`. `commands` and `entry` come from it.
+- `#dispatch` (old :1796, new :2160) gets a fifth parameter, `enroll`, which only `#raiseGrant` passes.
+  - `decision.raise` (new :2244): `grant` joins the allowed keys, and `grant` without `enroll` (or the
+    reverse) refuses `invalid-request`. The `host.sudo` block reads `#hostAccess` in place of `b.hosts`
+    and the role's `hosts`, and an undefined `target` still refuses `host-unknown`. `validArgv` and
+    `validStdin` now run after the access check, so a malformed argv for an ungranted host refuses
+    `host-not-granted` first. The enrollment block is appended to the question before `string(question)`,
+    so the 4096 cap counts it (M1). The decision's raise body carries `grant: enroll`.
+  - `decision.resolve` (new :2409): when `op` is `resolved`, `#approvedGrant` reads the decision, and a
+    `host-enroll` grant starts `#runEnrollment` from `setImmediate`, after the transaction commits. The
+    result adds `grant: 'started'`.
+
+New, all private but two:
+- `#grantEvent` (:657), the writer of guarded events. It runs the secret check, then `writeGrantEvent`.
+- `#approvedGrant` (:667), `#consumeGrant` (:678). `#consumeGrant` sits after `#approvedGrant`, not next
+  to `#consumeAuthority` as planned.
+- `#hostRecord` (:685), `#hostAccess` (:692), `#grantNotice` (:708), `#enrollFailed` (:736),
+  `#runEnrollment` (:750), `#openGrantDecisions` (:823).
+- `runEnrollment` (:745), public, a trusted entry to `#runEnrollment` for G10. No verb reaches it.
+- `reconcileGrants` (:833), public, which `runtime.mjs` calls once at start.
+- `#raiseGrant` (:866), `#hostsCaller` (:886), `#requestHosts` (:900), `#hostLinesLeft` (:964).
+
+Module level, new (:184-230): `GRANT_RUN`, `grantName`, `GRANT_EVIDENCE` (the N1 filter as SQL),
+`registrySha256`, `writeGrantEvent` (exported, the one writer of guarded events, which test fixtures use
+for F1), `HOSTS_VERBS`, `fingerprintOf`, `INSTALLER_COMMENT`.
+
+Unchanged: `#event`, `#spent`, `#consumeAuthority`.
+
+Other `src` files:
+- `bus/src/host-grant.mjs`, new: the keyscan, the installer key pair, and `hosts.check`'s `list`.
+- `bus/src/runtime.mjs`: builds `hostGrant`, calls `reconcileGrants` before the server starts, and adds
+  the `host_grants` references before `new Credentials` (X4 third bullet).
+- `bus/src/host-run.mjs`: `runHost` takes `command`, sent as is in place of the sudo argv, for the
+  installer's `list`.
+- `bus/src/server.mjs`: the `hosts.*` verbs and a raise with `grant` go down the async path.
+- `bus/src/store.mjs`: the 3i-3j step, `SCHEMA_VERSION` 3j. `bus/src/credentials.mjs` exports
+  `privateDir`.
+- `business/src/business.mjs` and `business/src/hosts.mjs`: the loader refuses `hosts` (S1).
+  `checkHosts` and `checkHostGrants` are gone.
+- `cli/src/hosts.mjs`, new, routed from `cli.mjs` and `scripts/mosaic`.
+
+## Decisions taken in the build
+
+- **`#hostAccess` binds the agent and the host.** X4 says the Approve record check passes when the
+  decision is an approved `host` grant with a `grant.host` consume. The check also requires the grant's
+  `agent` to equal the session's role and its `host` to equal the requested host. Without that, an
+  approved grant for one agent and host would vouch for any `host_grants` row that names its decision.
+  Cost: none for row b, whose executor writes the row from the same grant.
+- **Store fixtures are written the real way.** `bus/tests/host-fixtures.mjs` inserts the decision rows by
+  SQL, but every guarded event goes through `writeGrantEvent`, so the trigger sees it (F1). An enrollment
+  fixture writes `grant.host.enrolled`, or the start reconcile reads it as interrupted.
+- **The resolver test for host kinds is gone.** `business/tests/hosts.test.mjs` lost its D5 case, because
+  the loader now refuses `host.<id>` credential refs. The `isHostKind` filter in `business/src/resolve.mjs`
+  can't be reached now. I left it in, since row b may want it back, and it's one line.
+- **Store before Credentials.** The runtime already opened the store before `Credentials`. The
+  `host_grants` references depend on that order, and the comment there says so.
+- **CLI.** `mosaic hosts` prints tab lines, and `--json` prints the bus rows. Usage errors exit 4 and bus
+  refusals exit 2, as `mosaic credentials` does. There is no enroll command: enrollment is the chief's raise.
+- **Host tools tests live in the bus suite.** `bus/tests/host-tools.test.mjs` loads the writer by path
+  through a Python harness under `python3 -B -I`. The harness passes its own key dir, config dir, owner
+  uid and user, group and sudo lookups, and runs `mosaic-keys` from a copy with stub `sudo` and `logger`.
+  The gate runs the bus suite, so G16 and G25 run there. The real `pwd`, `grp` and `sudo -l` paths are
+  checked on the #433 VM, not here. The test also runs `visudo -c` on the sudoers file and `sshd -T` on
+  the drop-in.
+- **Writer details the design left open.** The `from` file must hold exactly one value matching
+  `[0-9A-Za-z.:/*?!_-]+(,[0-9A-Za-z.:/*?!_-]+)*`, so it can't close the quote. `users`, `privileged` and `from` must be
+  regular, owned by the owner uid and not group or world writable, and are opened without following a
+  symlink. Lines starting with `#` are comments. A refusal exits 1 with its code on stderr and in syslog.
+  `add` of a tag that is already there exits 0 and writes nothing.
+- **`runEnrollment` is public for G10 (duckworth-0081 B1).** G10 needs a second start for a spent
+  decision, and the resolve path can't give one: a second resolve refuses `decision-closed`
+  (broker.mjs:2416) before the executor runs. So
+  `#runEnrollment` returns its code (`enrolled`, `host-enrolled` or the refusal), and a public
+  `runEnrollment` calls it, as `reconcileGrants` is public. The test checks a spent
+  decision gives `decision-consumed`, and an open or agent-resolved one gives `not-authorized`, with
+  nothing written. That second case also reaches the `via` and `by` checks in `#approvedGrant`, so A3 is
+  no longer vacuous (N1).
+  Who can call it (sage-1692): only code holding the `Broker` object, which is the bus process and the
+  tests. The one `new Broker` in `src` is `runtime.mjs:126`, and no `src` file calls `runEnrollment`;
+  the resolve path calls the private `#runEnrollment` from `setImmediate` (broker.mjs:2445). A seat
+  holds no `Broker`. It reaches the bus only over `broker.sock`, where `server.mjs` calls a fixed set of
+  methods by name (`request` at :134 and :140, `identity`, `disconnect`). `request()` routes on the verb
+  through the `#dispatch` switch, and neither file looks a method up by name (no `this[` in either), so no
+  verb string can reach `runEnrollment`.
+- **A `sudo -l` that times out refuses `user-sudo` (N2).** `_sudo` returns an empty answer on
+  `TimeoutExpired`, which isn't the expected line, so `main` logs the refusal and exits 1.
+- **Keyscan comment (N3).** A scan that can't start refuses `host-failed`. One that runs and finds no key
+  returns no lines, and the raise refuses `host-key-mismatch`. The comment in `host-grant.mjs` now says so.
+- **No tag on in-run `grant.failed` (N4).** r6:578 tags only the `interrupted` one, so the code follows it.
+- **Run sheet (N5).** The writer refuses `config-privileged` when the file is missing, so each host needs an
+  empty, root-owned `/etc/mosaic-keys/privileged` (0644) before the first enrollment.
+
+## Mutant results (Sage's slot, 2026-10-21)
+
+All 25 killed: A1 to A23, with A3b added for duckworth-0083 N8 and A22 split into A22a and A22b. The
+runner is `mutants.py` outside the repo. Each mutant gets its own session, a 420 s limit with a group kill,
+and a byte restore checked against git status. None hung. Run 1 (04:24Z, on 95f966b1c) killed A1 to A22a
+and stopped at A22b, which survived. Run 2 (04:43Z, on 097892741) killed A22b and A23.
+
+- Each kill comes from a named assertion in the mutant's own test files, except A9. Dropping the `hosts`
+  primary key leaves `host_grants`' foreign key with no parent key, so the store refuses to open
+  ("foreign key mismatch") and 28 of 29 tests fail at setup. That's a structural kill, not the S1 test.
+  The schema can't exist without the key (sage-1709).
+- A22b drops the actor filter from `GRANT_EVIDENCE`. The trigger can't stand in for it, because a 3i store
+  can hold a session-written grant row that the 3i-3j step keeps. The grant-migration test "A22b,
+  sage-1703" kills it (see the A22 row above).
+
+Follow-up, not in row a: G18's control calls `runHost` directly, so nothing runs `hg.check` end to end
+with a good pin (duckworth-0083 N9). The #433 VM run covers it.
+
+## Status at 097892741
+
+Done: every Split item, 1 to 8, duckworth-0081 B1 to B3, duckworth-0083 N8, and all 25 mutants killed.
+
+Single files in the slot, all exit 0, 178 pass and 0 fail by an awk sum over 23 logs: bus grant-enroll
+24, host-run 24, grant-migration 6, host-tools 6, account-migration 3, chief-of-staff 18,
+comment-migration 5, hard-waits 13, name-migration 1, project-runtime 3, spec-migration 1,
+thread-migration 3, usage-migration 1, project-files 8, spec-socket 6, spec-review 12, land 17, spec 4;
+harness spec-tools 2, raise-domain 2; business hosts 4; cli hosts 5; seat sandbox 10.
+
+Left: Sage runs the whole bus, business and cli suites and every `scripts/test-*.sh` at the landing gate,
+after Duckworth approves.
+
+## Round 3 (sage-1742): two tests that count the schema
+
+The landing gate failed `packages/bus/tests/schema.test.mjs:522`. It counts the tables and triggers that
+`schema.sql` creates, and row a adds two tables and a trigger, so the counts go from 16 to 18 tables and
+from 70 to 71 triggers. My singles didn't run it because I took it for a test of other rows' tables.
+
+I grepped `packages/*/tests/*` for `sqlite_master` and `schema.sql`, with `schema.test.mjs:517` as the
+positive control. That turned up one more test that would fail: T46 in
+`packages/cli/tests/stack-release.test.mjs:910`. It puts every schema table in exactly one of four lists, and
+hosts and host_grants were in none. I'd left the stack-release tests out of the r2 singles on the claim that
+they don't load the bus, but T46 reads `schema.sql`. Both tables go in its untimed list (Sage's ruling,
+sage-1745: the message_threads pattern). Neither has an `at` column. Row a writes hosts at five lines,
+and each runs in one store transaction with a `grant.*` events row, which the restore guard counts.
+`#grantEvent` (broker.mjs:657) writes that row through `writeGrantEvent` (:201, INSERT INTO events at
+:212).
+
+- :737 DELETE, in `#enrollFailed`, with grant.failed at :738. Both callers wrap it in a transaction,
+  :816 and :849.
+- :763 INSERT, in the step 1 transaction (:754), with grant.host.enroll.step at :761.
+- :783 UPDATE installer_fingerprint, in the step 4 transaction (:780), with grant.host.enrolled at :784.
+- :932 DELETE, in the hosts.remove transaction (:927), with grant.host.removed at :933.
+- :950 UPDATE state ready, in the hosts.check transaction (:944), with grant.host.checked at :951.
+
+Row a writes no host_grants rows. It only reads them (broker.mjs:695, :930, runtime.mjs:103). Row b adds
+the writes, and each must share a transaction with a `grant.*` event the same way. That goes on row
+235's carry list. The other hits pin an older schema
+(account, comment, name, spec, thread and usage migrations, chief-of-staff 3c) or count only their own
+tables (state.test.mjs:106 reads every table but pins no list, threads.test.mjs:129).
+
+hosts and host_grants are mutable by design, so the refused-labels loop above `schema.test.mjs:517` gets no
+entry for them. hosts.check updates a host to ready. hosts.remove and a failed enrollment delete the
+record. Row b updates and deletes grant records. Neither table has append-only triggers. The one new
+trigger, events_grant_actor, guards events. grant-migration.test.mjs tests it, and it killed mutants
+A20 and A21.

agents/gizmoduck/work/queue-235/BUILD.md

@@ -0,0 +1,598 @@
+# Row 235 build: machine grant row b (#436, Gitea #1741)
+
+Brief: `docs/plans/2026-10-20_host-credentials.md`, "Machine grant row b: raise binding, executor,
+reconcile and revoke". Design r6 f9039682e. Built on row 234's landing c771a36f4 (sage-1775), branch
+gizmoduck/row235-b. Line numbers below were read on b0320d395, whose src files are byte-identical to the landing's.
+
+## Squash onto 4ced5e63d (sage-1812, sage-1831)
+
+Steps 1-6 were six local commits on c771a36f4 (gizmoduck/row235-b, tip f9fff4300). Sage named
+4ced5e63d as the base, so this branch, gizmoduck/row235-c, holds one commit on it: the diff
+c771a36f4..f9fff4300 applied with `git apply --index`. N10 is in that commit. N12 needs no change,
+because row b doesn't touch schema.sql.
+
+Rows 240, 228 and 238 landed between c771a36f4 and 4ced5e63d and changed 18 paths. One of them is
+also mine:
+
+- `packages/cli/README.md`. Row 228 (86249ac55) changed the session credential paragraphs at about
+  lines 432 and 706. My hunk adds three lines on `hosts revoke` and `hosts sweep` at about line 1052.
+  The two don't overlap, so the blob here is row 228's blob plus my three lines, with no landed line
+  reverted. cli tests/host.test.mjs:855 reads this README, and run 1's cli suite covers it.
+
+The other 12 paths are byte-identical to f9fff4300. The line numbers in the step notes below were read
+on the old base.
+
+## Run 1 (sage-1831, sage-1833, sage-1838)
+
+Run 1 on 4d4bb4af6, 07:45-07:54Z, failed: 1351 tests, 1285 pass, 66 fail. The 66 are 33 tests counted
+twice, once in the files run and once in the bus suite. The cli suite, the cli hosts test, seat
+sandbox.test and bus project-runtime.test passed. Two defects, both mine:
+
+- grant-executor.test.mjs, 32 tests. setup() never made `dir/data`, and `new Store` lstats its root
+  (store.mjs:137), so every test stopped at setup with ENOENT. setup() now makes it, mode 0700.
+- credential-claim.test.mjs:76 (X4), 1 test. A register after a revoke left the key in `#revoked`, so
+  status() said `revoked` for a new grant's reference that has no token yet. register now clears
+  `#revoked`, as unregister does. `#revoked` feeds only status(), and issue clears it as well.
+
+Both fixes are amended into the one commit. The rerun covers the five bus files, the bus suite, and
+cli credentials.test.mjs and verbs.test.mjs, which read credential state strings.
+
+## Run 1 rerun (sage-1842, sage-1843)
+
+The rerun on ac7c45975, 08:06-08:07Z, failed: 701 tests, 695 pass, 6 fail, which are 3 grant-executor
+tests counted in both the files run and the bus suite. All three were test defects that run 1's setup
+failure had hidden. No src file changed for them:
+
+- G10. The two fixture decisions were built after `before`, and grantDecision (host-fixtures.mjs)
+  INSERTs one events row each, so the count read 13 for 11. The test now builds them first, asserts
+  they added exactly 2 rows, and then pins the executor's 0 against that count.
+- G27. setup's t.after removes the scratch dir before a hook the test adds later runs, so the test's
+  chmod hook hit ENOENT after the body had passed. The body now restores the mode in a try/finally.
+- G22. The slow run's promise had no handler until `refusesWith`, four lines on. The revoke rejected it
+  first, and node failed the test on the unhandled rejection. The handler now goes on at creation.
+
+The fix is one more amend of the single commit. The rerun is grant-executor.test.mjs whole plus the bus
+suite.
+
+Rerun 1c on 5df4b52c5, 08:15Z, was green: 623 of 623, grant-executor 34 of 34 and the bus suite 589 of 589.
+
+## Mutants B1-B37 (sage-1894, sage-1899, sage-1904)
+
+Three chunks ran on 5df4b52c5, 09:22-09:37Z. Restores matched HEAD after each. 33 were killed and four
+survived. Two of the misses were mine, in the file lists:
+
+- B2 and B23 listed only grant-executor, and that file never makes the raise either mutant changes.
+  grant-enroll.test.mjs:227 (A2, A4) resolves a plain `credential.mint` yes and a host grant no, and
+  asserts no grant events for either. mutants.py now lists grant-enroll and grant-executor for both.
+  B2 then ran alone and A2 killed it. B23 runs again with this round's tests.
+
+The other two survivors needed tests, and Sage ruled on all four (sage-1904):
+
+- B16 drops the abort check after `verify`. The check after `step('commit')` still ends the grant
+  revoked, so G23 X5's asserts held. The run then logs a commit step for a grant that never committed.
+  G23 X5 now asserts that its only `grant.step` is `install`.
+- B17 adds `await null` after the commit check. Sage accepted it as equivalent. `await null` yields
+  only to microtasks. Every revoke starts in a macrotask of its own (a socket request, or a test's
+  call), so none can land in that gap. There is no test for it.
+- B27 makes issue's commit callback async. issue() doesn't await it, so the executor returns `applied`
+  before the INSERT runs. The two differ only when the commit transaction throws, and a real store can
+  throw there with a full disk, an I/O error or a busy timeout. Under the mutant that throw becomes an
+  unhandled rejection after the key file is written, and the catch's undo never runs. The new G8 test
+  makes the store's `run` throw SQLITE_FULL once on the host_grants INSERT. It asserts host-failed, no
+  record, key file, reference or line, and the steps install, commit, failed. The store object comes
+  from the test's setup, so src gains no seam.
+
+These two test changes went in as a new commit on gizmoduck/row235-d (8b13d0ca0). That branch then
+moved onto row 213's landing as gizmoduck/row235-e, below. B16, B23 and B27 run there, after the touched
+test files run whole.
+
+## Rebase onto 62ddc96cc (sage-1922)
+
+Row 213 landed as 361ba2387, and refactor's tip is 62ddc96cc, with only docs past it. gizmoduck/row235-e
+starts at 62ddc96cc and cherry-picks 8b13d0ca0's one commit. The patch-id is unchanged (c062b73fa9f1).
+row235-c and row235-d stay as they were.
+
+Between 4ced5e63d and 62ddc96cc, 361ba2387 is the only commit that touches a file of mine. The one
+drifted path is `packages/bus/src/broker.mjs`:
+
+- 213 adds `CREATIVE_DEFINITIONS` to the vocabulary import at :6, and refuses `decision.raise` from a
+  creative role with `decision-not-allowed` at :2176. Both hunks stay as landed.
+- My 31 removed broker lines read the same before and after the cherry-pick, so no landed line is
+  reverted.
+
+`packages/cli/README.md` isn't in 361ba2387. Every other path of mine is byte-identical to 8b13d0ca0.
+Line numbers in the section below were read on the row235-e working tree; earlier sections keep theirs.
+
+## Creative roles get no host grant (mos-1163, sage-1905, sage-1908, sage-1916)
+
+Brief blob b16e236188f6 (4364dddb0, rev 2784) requires two refusals: the writer, at the raise and at the
+step 1 recheck, and host.run at spend time, with the record kept. Webby's N2 on row 213 r4 asks whether
+a creative role can spend a decision another role raised.
+
+The spend answer. Mos confirmed it read-only (mos-1164, sage-1916) on 8b13d0ca0 and 01e1fe512; the
+row235-e line follows each:
+
+- Only the chief raises a host grant. `#raiseGrant` refuses `grant-chief-only` for any other
+  definition: :1232 on 8b13d0ca0, :870 on 01e1fe512, :1238 here. The hosts verbs check the same at
+  :1307 on 8b13d0ca0, :896 on 01e1fe512, :1313 here. `chief-of-staff` isn't in `CREATIVE_DEFINITIONS`.
+- No agent spends one. `#consumeGrant` (:697) is called for a host grant only from `#runHostGrant`
+  (:902) and from the restart reconcile (:1106), which ends it interrupted. `#runHostGrant` starts from
+  the resolve hook (:2881) only when `#approvedGrant` returns a grant, and that needs a close by the
+  business's human, via cli, with the raise's approval choice (:691). An agent's resolve records via
+  `broker`, so it starts nothing (grant-enroll A3). The public `runHostGrant` (:891) is a trusted API
+  that no verb reaches.
+
+So a creative role can't raise, approve or spend a host grant. The gap was a different one: the chief
+could raise a grant whose `agent` is a creative role, and the human could approve it. The only check on
+that agent was `#hostDefinition`, which refuses `host-not-declared` (:864) unless the definition's
+`credentials` names `host`. Row 213's `checkCreative` (business/src/role.mjs:143) limits a creative
+role's tools, authority and messaging, not its `credentials`, so a creative role file naming `host`
+passed both the raise and the step 1 recheck.
+
+As built:
+
+- Writer. `#hostDefinition` refuses `host-creative-role` (:862) before the `host-not-declared` check.
+  The raise binding (:1266) and the step 1 recheck (:879) both call it, so a grant raised before its
+  agent's instance moved to a creative definition ends at step 1, spent, with no remote step.
+- Spend. `#hostAccess` refuses `host-creative-role` (:714) when the agent's current definition is
+  creative, before it reads the record. Both callers go through it: host.run (:2543) and the host.sudo
+  raise (:2778). The record stays, because revoke still owns the cleanup (sage-1908). This goes past
+  the brief's writer line in the same direction; Sage tells Mos.
+
+Tests:
+
+- grant-host.test.mjs:115. A `muse` role on a `research` definition that declares host. The raise
+  refuses `host-creative-role` and adds no decision.
+- grant-executor.test.mjs:947. The restart moves `ops` to a creative definition that declares host,
+  then a fixture grant runs. It ends `host-creative-role` at step 1, the decision is spent, and there is
+  no remote request and no record. The fixture comes after the restart, because the restart's reconcile
+  ends any resolved, unspent host grant as interrupted.
+- grant-executor.test.mjs:958. An applied grant, then a restart with `ops` creative, then host.run
+  refuses `host-creative-role`. No remote request is added, sudo.log has no `systemctl`, and the record
+  is still there.
+
+The broker clones `businesses` when it's built, so a definition change needs a new Broker. The test's
+`restart()` gains a `business` parameter, default unchanged, for that.
+
+Mutants: B38 removes the `#hostDefinition` line, run against grant-host and grant-executor. B39 removes
+the `#hostAccess` line, run against grant-executor.
+
+## Run 2 (sage-1928)
+
+Run 2 on 534f2254a, 10:12:52-10:14:51Z, was green. grant-host.test.mjs 9 of 9, grant-executor.test.mjs
+37 of 37 and grant-enroll.test.mjs 24 of 24, each run whole. grant-enroll is unchanged, but it drives the
+broker, and broker.mjs changed. Then the five mutants, all killed, with the restore matching HEAD:
+
+| Id | Killed by |
+|---|---|
+| B16 | G23 (X5), the revoke as verify returns |
+| B23 | A2, A4 |
+| B27 | G8, the store fault in the commit transaction |
+| B38 | both mos-1163 tests |
+| B39 | the sage-1908 test |
+
+## Mutant results, B1-B39
+
+| Run | Head | Killed | Survived |
+|---|---|---|---|
+| B1-B13, 09:22Z | 5df4b52c5 | 12 | B2 (file list) |
+| B2 alone, B14-B37, 09:28-09:37Z | 5df4b52c5 | 21 | B16, B17, B23, B27 |
+| B16 B23 B27 B38 B39, 10:13Z | 534f2254a | 5 | none |
+
+38 of 39 are killed. B17 is equivalent (sage-1904), for the macrotask reason in the B1-B37 section.
+B1-B37 ran on 5df4b52c5, before the move onto row 213's landing, and weren't rerun on 534f2254a.
+`--check` matches all 39 anchors once on 534f2254a.
+
+## Carry list
+
+- N10 (duckworth-0084, row 234 r1): `cli/src/hosts.mjs:30-31` reads `shape[verb]` off a plain object,
+  so `mosaic hosts constructor` passes usage and the bus refuses it with exit 2 instead of 4. Row b adds
+  `hosts revoke` and `hosts sweep` to the same table (design r6 :562, :680), so the fix goes in with
+  them: `Object.hasOwn(shape, verb)` and a usage test for an `Object.prototype` name (sage-1726).
+- Untimed tables (sage-1745, row 234 r3): stack-release T46 lists hosts and host_grants as untimed
+  because every write to them shares one store transaction with a `grant.*` events row. Row a writes only
+  hosts. Every host_grants INSERT, UPDATE and DELETE row b adds must do the same, and BUILD.md lists each
+  with its event line. A write without one is a stop to raise with Sage.
+- N12 (duckworth-0086, row 234 r3, doc-only): row 234's round 3 list of other schema hits leaves out
+  `packages/cli/tests/stack-release-fixture.mjs:214` and `scripts/test-land-work.sh:254`. Both look up
+  one table by name and need no change. If row b changes the schema, its grep list names them.
+
+## What row a already gives row b (b0320d395)
+
+- `#approvedGrant`, `#consumeGrant(business, decision, method)` and `GRANT_EVIDENCE` (broker.mjs:667-690).
+  Row b calls `#consumeGrant` with `'host'`.
+- `#openGrantDecisions(business, method)` and `reconcileGrants()` (broker.mjs:823-860), which today handle
+  `host-enroll` only. Row b adds the `host` method, the `grant.step` undo table (r6 X3) and the
+  revoke-marker reconcile (r6 section 6, N4).
+- The resolve hook at broker.mjs:2444-2445 starts `#runEnrollment` for `host-enroll`. Row b adds the same
+  start for `host`, under the same human, via cli and choice checks.
+- `host.run` already reads the store grant record and checks the Approve record (broker.mjs:691-703).
+- The raise check `grant-chief-only` (broker.mjs:870, :896). `host-grant.mjs:55` refuses every method but
+  `host-enroll`, and row b opens it to `host`.
+- `Credentials` has `#inflight` with the `host-busy` claim inside `runHost` (credentials.mjs:118, :355).
+  It has no `claim`, `abortClaim`, `register` or `unregister`. Row b adds those (r6 X4, X5).
+
+## Plan, in build order
+
+1. Raise binding (r6 R1-R4): the `grant` argument for `method: 'host'`, `host-not-declared`,
+   `host-not-ready`, the 210 D6 argv rules, `rotateBy`, the rendered block and the 4096 cap, and the raise
+   body hashes. Tests G1-G5, G19.
+2. `Credentials.claim`, `release`, `abortClaim`, `register`, `unregister`, with the shared reference check.
+3. The executor in `bus/src/host-grants.mjs`, steps 1-6 (r6 X2), with failure undo (X3) and the abort rule
+   (X5, C1). Tests G7-G10, G15, G23, G24.
+4. Restart reconcile for `grant.step`, unspent `host` decisions, and the start sweep of `host.<id>` key
+   files with no record (r6 X3, N1). Tests G11, G27, G28.
+5. `hosts.revoke` and `hosts.sweep` verbs, plus the CLI `revoke` and `sweep` with N10. Tests G12, G13,
+   G26, G27.
+6. G22 end to end on one bus. Then the mutant list from r6 section 10 for row b, numbered B1 onward in
+   this file, with the upsert mutant and the abort-after-commit mutant included.
+
+There is no schema step. If one turns out to be needed, I stop and ask Sage to re-brief first.
+
+## Step 1 notes (raise binding, read on b0320d395)
+
+Where the code goes:
+
+- `#raiseGrant` (broker.mjs:866-885) runs the checks and keyscan for `host-enroll` today, and every raise
+  with `grant` reaches it (:1738-1739). Row b branches on `a.grant?.method`. `host` takes no keyscan, so
+  its checks can all run inside the one raise transaction, as R4 asks.
+- `enrollCheck` (host-grant.mjs:50-69) refuses every method but `host-enroll` (:55). Row b adds a sibling
+  `hostGrantCheck` for the R4 shape `{method, agent, host, commands, rotateBy}` and keeps `enrollCheck`
+  as it is, so the 234 tests don't move.
+- The raise body is at broker.mjs:2270, :2345-2353 and :2391. `enroll` becomes a generic `grant`
+  binding. The question block for `host` follows the `host.sudo` block (:2337-2341): agent, host id,
+  address, user, sudo, each prefix JSON-quoted, rotate date, and new key or changed commands. The
+  4096 cap comes from `string(question)` (:2354).
+- The argv rules come from `checkCommands` (business/src/hosts.mjs:67-87): no wildcard, no empty prefix,
+  no glob characters, a bare name or an absolute path, and `refusedCommand` for shells and runners. It
+  throws `refuse(...)` with a message, so the bus maps any throw to `invalid-request`, as `enrollCheck`
+  maps `checkAddress` (host-grant.mjs:57-61).
+- `host-not-declared`: the agent's definition must list `{"service": "host"}`. business.mjs:126-129 reads
+  `definition.credentials` and filters out `HOST_SERVICE` (vocabulary.mjs:113). The bus needs the
+  definition's service list. Read how the running business exposes the definition before choosing.
+- Both lookups are answered. `loadBusiness` returns `definitions`, each role file's validated document
+  (business/src/business.mjs:114-124, :159, returned at :267). `busBusiness` clones the whole business
+  (bus/src/business.mjs:7), so the broker has `b.definitions`. `#definitions` already reads it
+  (broker.mjs:1027-1029), and the comment there says the broker doesn't read `roles/` (sage-0590).
+  - `host-not-declared` checks `b.definitions[b.roles[agent].definition].credentials` for
+    `{service: 'host'}`. role.mjs:118 normalizes a host entry to exactly that.
+  - Deviation from R4: `definitionSha256` is sha256 over `canonicalJson` of that validated definition,
+    not over the file's bytes. The broker doesn't read `roles/`. A whitespace-only edit to the file no
+    longer voids an approval, but any change to a field the loader keeps still does. The bus sees a
+    definition change only after a business reload or restart, the same as every other role field.
+    This goes in the round 1 note.
+
+Assumption, accepted for round 1 by Sage (sage-1782), for Duckworth to check in review: design R4 says `rotateBy` is "a date inside 210's rotation window", but 210
+defines no window in code. It checks only that the value is a real calendar day (bus
+credentials.mjs:16-20, issue at :245). The business load calls a past `rotateBy` a problem
+(business/src/credentials.mjs:114). So the raise takes a real day strictly after today, UTC, and refuses
+`invalid-request` otherwise. There is no upper bound, because no requirement states one and 210
+checks none.
+
+## Step 1 as built (not run yet; no slot)
+
+- `hostGrantCheck(grant, today)` in host-grant.mjs takes exactly `method`, `agent`, `host`, `commands` and
+  `rotateBy`. `agent` must match ID_PATTERN and `host` HOST_ID. `commands` goes through `checkCommands`,
+  and any throw becomes `invalid-request`. `rotateBy` must pass 210's `day` (now exported from bus
+  credentials.mjs) and be later than the bus clock's UTC day.
+- `#raiseGrant` branches on `a.grant?.method === 'host'` after the chief check and before `enrollCheck`.
+  So a host-enroll shape with `method: 'host'` still refuses `invalid-request`, and the 234 G1 list holds.
+- `#hostGrantBinding` runs inside the raise transaction. It refuses `unknown-role` for an agent that
+  isn't a role instance (the code bindLaunch uses, broker.mjs:522). It refuses `host-not-declared`, and
+  `host-unknown` for a host with no record, as `#hostAccess` does. A record in `pending-install` refuses
+  `host-not-ready`. R4 names only `host-not-ready`. I picked `host-unknown` for a missing record so
+  "not enrolled" and "enrolled but not checked" stay apart.
+- `commandsSha256` is sha256 over `JSON.stringify(commands)`. For arrays of strings this equals
+  canonicalJson, and step 3's executor recomputes it the same way.
+- `#dispatch` takes `binding = {body, block}` in place of `enroll`. The enrollment block moved into
+  `enrollBinding` at module level with its text unchanged, so the 234 G4 test reads the same question.
+- No new import in broker.mjs, so RUNNER_FILES doesn't change. host-grant.mjs now imports
+  business/src/util.mjs for canonicalJson. Nothing in the sandbox loads host-grant.mjs. Before in-review
+  I still run seat sandbox.test.mjs and bus project-runtime.test.mjs whole.
+- The new-key line reads host_grants (a SELECT). Step 1 writes no host_grants row.
+- Tests: bus/tests/grant-host.test.mjs, G1 (host), G2, G3, rotateBy, G19, R4/G5 body hashes, G4 block.
+  The G5 tester-thread case: a thread run is always THREAD_DEFINITION, never chief-of-staff, so
+  `grant-chief-only` refuses it first. The test covers the tester's own cap (`tester-refused`).
+
+## Step 2 as built (not run yet)
+
+- The constructor's per-reference checks moved into `#checkRef`, in the same order, and `register` calls
+  it (r6 X4). `register` reads no file. A key file that a failed revoke unlink left at the path stays
+  unused until the start sweep (step 4) removes it. `register` refuses `credential-reference` while the
+  entry holds a live token. An entry with no token, revoked or never issued, is replaced, so a new grant
+  after a revoke registers again.
+- `unregister` drops an entry with no token and clears its revoked mark. A live token refuses.
+- `claim` refuses `host-busy` when the slot is held, by a claim or a `host.run`, and returns the signal.
+  It needs no reference, because the executor claims at step 1 and registers at step 5.
+  `release(instance, service, signal)` frees the slot only for its own signal. I added the signal
+  argument so a late release can't free a later claim.
+- `abortClaim` aborts whatever holds the slot and returns `{pending}`. An aborted claim keeps the slot
+  until the executor releases it in its `finally` (X2).
+- Tests: bus/tests/credential-claim.test.mjs. The D5 `use(` allowlist is unchanged.
+
+## Step 3 as built (not run yet)
+
+Where the code goes. The remote steps are in host-grant.mjs (`grantKey`, `install`, `verify`, `remove`)
+and the orchestration is `#runHostGrant` in broker.mjs, next to `#runEnrollment`. BUILD.md's plan said a
+new `bus/src/host-grants.mjs`. I kept row 234's split instead: the broker holds every store write and
+host-grant.mjs holds the network and key files. A new broker import would also change what the sandbox
+must mount (RUNNER_FILES), and this way broker.mjs gains none.
+
+The broker gets `hostKeys`, made by `grantKeys({credentials, storeRoot})` in host-grant.mjs. It wraps
+only `claim`, `release`, `abortClaim`, `register`, `unregister`, `issue` and `revoke`, keyed by
+(business, agent, hostId). The broker still never gets `use()`. runtime.mjs builds it and passes it in.
+`hostReference` gives the store reference, and the runtime's start load uses the same function.
+
+Every host_grants write in step 3, with its event (sage-1745):
+
+| Write | Where | Event in the same transaction |
+|---|---|---|
+| INSERT, a new key | the `commit` callback that `issue` calls | `grant.applied` |
+| UPDATE commands and decision, a commands change | step 5's transaction | `grant.applied` |
+
+No other step 3 code writes host_grants.
+
+Deviations from r6, for the round 1 note:
+
+- `grant.applied` commits with the record, inside `commit`, not after `issue` at step 6. The untimed-table
+  rule needs an event in the record's transaction. `grant.step commit` can't be that event, because X2
+  writes it before the key file. So X3's "5 after commit" row has nothing to undo in the executor: once the
+  record commits, `grant.applied` has too. What's left in `issue` after `commit` is the memory fill, which
+  writes no file and no store row. The executor sets `committed` after the transaction returns and from
+  then ignores an abort (C1). The restart reconcile (step 4) keeps the commit row, because a crash can fall
+  between the key file write and `commit`.
+- Event bodies name the decision as `grantDecision`, as row 234's enrollment events do. The consume record
+  is the only grant body with `decision`, so `#spent` counts it and nothing else.
+- For a commands change, `grant.applied` has `fingerprint: null`. The executor holds no key on that path.
+  The record's `rotate_by` stays. X2 names only commands and the decision id.
+- The keygen dir goes as soon as `grantKey` has read the key back into memory, not in step 5's `finally`.
+- Step 4 runs `true` as the remote command as is, not through the sudo argv, since a user with no sudo
+  must pass it too.
+- `hostGrant()` takes `installerUser`, `mosaic-installer` by default. Only the tests change it, because
+  the scratch sshd logs in only as the test's own user.
+- A commands-change UPDATE that changes no row ends `host-changed`. Only a revoke deletes a live record,
+  and a revoke aborts the claim first, so this is a guard.
+
+Step 1 codes, after the spend and in its transaction: `host-not-configured`, `unknown-role`,
+`host-not-declared`, `decision-mismatch` (definition, registry or commands hash), `host-unknown`,
+`host-not-ready`, `revoked` (a `grant.revoked` of the agent and host after the raise). The definition
+check moved into `#hostDefinition`, which the raise binding uses too.
+
+Tests: bus/tests/grant-executor.test.mjs, a scratch sshd on 127.0.0.1 with stub `list`, `add` and
+`remove` that edit a second authorized-keys file. G7 (new key, and a commands change), G8 (install, verify,
+a failed remove, step 5 before commit, a failed step 1 check), G9, G10, G15, G23 (a revoke during install
+through `abortClaim`, a `grant.revoked` before start, and a held slot), G24's tag part. G23's held slot
+uses `claim` in place of a running `host.run`. Both hold the same `#inflight` entry. The `revoke` verb
+comes in step 5, so G23 here writes `grant.revoked` through the fixture writer and aborts through
+`abortClaim`. Step 5 adds the verb's own path.
+
+## Step 4 as built (not run yet)
+
+The restart reconcile has three parts, in start order:
+
+1. `sweepHostKeys` (host-grant.mjs), in runtime.mjs right before `Credentials` loads. In each loaded
+   business's agent store it unlinks every `host.<id>` file that has no `host_grants` record, and logs
+   one `hosts: {"event":"host-key-swept",...}` line per file to stderr. A store dir that isn't private
+   refuses `credential-file`, and so does the start. A name that isn't `host.` plus a valid host id
+   stays, so ssh-keygen's `.pub` stays too. A business the bus didn't load is left alone.
+2. `reconcileGrants`, where row 234 already calls it, after `Credentials` loads and before the socket
+   opens. For a `host` grant it ends a spent decision that has no `grant.applied` and no `grant.failed`.
+   It also spends and ends an unspent one the human resolved yes. Each ends `grant.failed interrupted`,
+   with the tag and a notice. When the last step is `install`, or `commit` with `previous: null`, a line
+   may be left. For those, it claims the (agent, `host.<id>`) slot and queues the decision for part 3.
+3. `reconcileHosts`, which runtime.mjs calls once `serve` returns, with no await, so a start doesn't
+   wait on the network. Each queued decision runs `remove <user> <tag>` through the installer, as the
+   step's `user`. Then it ends `grant.failed interrupted`, with `hostLineLeft` if the remove failed or
+   there's no host record, and releases the claim. The claim makes a new grant for the same agent and
+   host refuse `host-busy` while the remove runs. Otherwise its new line, with the same tag, could be
+   removed.
+
+Deviations from r6's restart table, for the round 1 note:
+
+- No record write on restart. Step 3 commits the record with `grant.applied` in one transaction. So a
+  decision with no `grant.applied` has no record. For a new key, the record undo has nothing to delete.
+  For a commands change, the "back to `previous`" undo has nothing to put back. What's left of the
+  `commit, new key` row is the key file, written before `commit`, and the start sweep unlinks it.
+  The `commit, commands change` row ends interrupted with nothing undone. G28's "a revoke before
+  `grant.applied`" can't happen, because they commit together. Step 5 tests G28 as a change, then a
+  revoke, then a restart.
+- The local undo of row 234's enrollments stays after `Credentials` loads, where row 234 put it. That
+  undo touches only the installer key and the host record, and `Credentials` reads neither.
+- The host grant part writes no `host_grants` row, so the untimed-table rule (sage-1745) adds nothing
+  here.
+
+Fixture change: `hostGrantRecord` (tests/host-fixtures.mjs) writes `grant.applied` after a `grant.host`
+spend, as the executor always does. Without it, a start over a fixture record ends that record's
+decision `interrupted`. Row 234's M3 start test (host-run.test.mjs:602) does that start. No test counts
+the fixture's grant events (checked by grep across the bus tests).
+
+Tests in grant-executor.test.mjs, through a `restart` helper that follows runtime.mjs's order on the
+same store:
+
+- G11 after `install`: the line goes, the slot is held between the two parts, and the grant ends
+  interrupted. A second start adds nothing, and `runHostGrant` refuses `decision-consumed`.
+- G11 after a new key's `commit` with the key file written: no key file, record, reference or line.
+- G11 after a change's `commit`: the record, key and line are unchanged, and the host gets no request.
+- G11 (B2) before step 1, spent and unspent: each ends interrupted with a notice, and the unspent one
+  is spent exactly once.
+- A failed remote undo, and a missing host record: each ends with `hostLineLeft` and the sweep hint.
+- A finished grant: the reconcile adds nothing.
+- N1 (G27's sweep part): only files with no record in loaded businesses go, and a dir that isn't private
+  refuses.
+
+The revoke-marker part of the reconcile (section 6, N4) comes with the revoke verb in step 5.
+
+## Step 5 as built (not run yet)
+
+Two new bus verbs, `hosts.revoke` and `hosts.sweep`, join `HOSTS_VERBS`. The CLI gets
+`mosaic hosts revoke AGENT HOST --reason R` and `mosaic hosts sweep HOST`.
+
+`hosts.revoke {agent, host, reason}` follows r6 section 6:
+
+1. One transaction deletes the `host_grants` record and writes `grant.revoked` with a new `revoke` id
+   (a UUID), the computed tag, `hostLine: "pending"`, `granted`, `reason` and `by`. With no record it
+   still writes the marker, with `granted: false`, so a stale line can be named (N4). A host with no
+   record refuses `host-unknown` and writes nothing.
+2. With no await between, `Credentials.revoke` drops the key from memory, aborts a `host.run` in flight
+   and unlinks the file. With no reference (`credential-unknown`), an executor holds only a claim, so
+   `abortClaim` stops it. Any other throw, such as an unlink that fails, comes back as `keyFile: "left"`.
+   The record is already gone, so the next start's sweep unlinks that file.
+3. `remove <user> <tag>` through the installer, as the host record's user (the executor's user too).
+   Then `grant.revoke.closed` with the same `revoke` id and `hostLine: "removed"`, or `hostLineLeft`.
+
+Callers (G26): the human, and the assistant of the session's business, checked with `#threaded`. The
+tester can call it when `bus.tester` is exactly `true`, read again at the call. Any other agent gets
+`revoke-refused`, a code new in this row. A tester session can't hold a business whose `bus.tester`
+isn't `true`, since `bindTester` refuses `tester-off`, and the broker's businesses don't change while
+it runs. So `tester-dev-only` can't be reached from a test. The check stays for N8, in case a later
+row reloads businesses.
+
+`hosts.sweep {host}` is the human's or the tester's; an agent gets `human-required`. It runs
+`list <user>`, then removes each listed tag that this business recorded for the host in a `grant.step`
+or `grant.revoked` and that no live grant holds. Another business's line and an unrecorded `mosaic-`
+line stay (G24's sweep part). It writes `grant.host.swept {host, removed, left, by}`, where `left` is
+each earlier left tag still listed and not removed. `#hostLinesLeft` now starts from the last
+`grant.host.swept` and adds only later `hostLineLeft` bodies (F4).
+
+The restart reconcile adds the marker part: `reconcileGrants` collects each `grant.revoked` with
+`hostLine: "pending"`, a text `revoke` id and no `grant.revoke.closed` of that id. `reconcileHosts`
+runs step 3 for each. A `grant.revoked` with no `revoke` id, as G23's fixtures write, isn't reopened.
+`hosts.status` adds `revoking`, the tags of the open markers on the host.
+
+Other changes:
+
+- N10: the CLI checks the verb with `Object.hasOwn`, so `constructor`, `toString` or `__proto__` is a
+  usage error.
+- `--reason` is required with `revoke` and refused with any other verb.
+- The reason goes through the broker's `string(x, 500)`, as `credentials.revoke`'s does, so a reason of
+  only spaces is accepted there too.
+- Correction to step 4: the first G11 test expected `list` then `remove`. `reconcileHosts` sends only
+  `remove`, so the test now expects that.
+
+Residuals for the round 1 note:
+
+- A new grant whose line goes in while a revoke's step 3 or a sweep runs can lose that line, if it has
+  the revoked tag. Revoke holds no claim during step 3. If the remove lands after the new grant's
+  verify, the grant is recorded but its line is gone, so its logins fail. I didn't add a claim, because
+  a revoke must not wait on a slot.
+- The enrollment's installer tag is never in the sweep's set, so a `hostLineLeft` naming it stays
+  until the human removes it by hand.
+
+Tests in grant-executor.test.mjs:
+
+- G12: the human's revoke of a live grant, and the bodies of both markers. A restart adds nothing.
+- G12 (N4): a revoke with no record removes the computed tag's line. Bad args refuse
+  `invalid-request` and an unknown host `host-unknown`.
+- G13: a revoke during `install` aborts the executor, which ends `revoked`. A raise before a revoke
+  and started after it ends `revoked` at step 1.
+- G26: who may revoke and who may sweep.
+- G27: a restart after step 1 (the sweep takes the key file, then step 3 runs), after step 2 with the
+  host down (`hostLineLeft`, then a sweep clears it), and a file a revoke couldn't unlink.
+- G28: a commands change, then a revoke, then a restart.
+- G24 (B4): the sweep's tag set, a failing `list`, and the left list it records.
+
+The CLI tests in packages/cli/tests/hosts.test.mjs cover revoke and sweep, the N10 usage cases and the
+`revoking` field in a status line.
+
+## Step 6 as built (not run yet)
+
+New tests in grant-executor.test.mjs:
+
+- G22 (B1), one bus with no restart. The chief enrolls web1, the human approves, and `hosts.check`
+  marks it ready. A grant of `echo` follows, then a `host.run` of `echo hi` that prints `hi`. A
+  `sleep` raise refuses `command-not-granted`, and after a commands change to `echo` and `sleep` the
+  next `host.run` of `sleep 30` starts. A revoke kills that run with `credential-unavailable`. The next
+  call refuses `host-not-granted`.
+- G12: the local steps finish before the host step. With the host's `remove` held, the record and key
+  file are already gone and `hosts.status` shows the tag under `revoking`.
+- G13: a revoke whose host `remove` fails returns `hostLineLeft`, drops the record and key, and closes
+  the marker, so a restart adds nothing.
+- G23 (X5): a revoke right after the executor's spend reaches its claim and the grant ends `revoked`.
+- G23 (X5): a revoke that lands as `verify` returns ends `revoked` with no record, key file or line.
+  Only the abort check after `verify` catches it.
+
+The fixture gains a `sudo` stub (logs to sudo.log, then runs the command as the test's user), a
+`hold-remove` flag, `opts.enroll` (no host record and no installer key) and `opts.wrap` (changes the
+host API the broker gets). `hostGrant` gets a fake `scan` that returns the scratch sshd's host key.
+
+G22 deviations, for the round 1 note:
+
+- `checkAddress` (business/src/hosts.mjs:62) refuses this machine's address, so the test enrolls
+  192.0.2.10 with the fake keyscan. It then points the record at the scratch sshd with an SQL update
+  and adds the enrolled installer key to the sshd's authorized keys. Enrollment, check, grant, run and
+  revoke all go through the real code after that.
+- r6 B1 says the next `host.run` after a revoke refuses `credential-unavailable`. Here it refuses
+  `host-not-granted`, because step 1 deletes the record and `requestHost` checks the record
+  (`#hostAccess`) before it reaches the key. The call in flight does refuse `credential-unavailable`.
+
+### Mutants
+
+`/mnt/storage/scratch/gizmo-235-out/mutants.py` holds each mutant as anchored edits. `--check` applies
+them in memory and runs no test. All 39 anchors match once. Each mutant runs its named test files.
+
+From r6 section 10, as they apply to row b:
+
+| Id | Mutant | Test file |
+|---|---|---|
+| B1 | drop the chief check on a host grant raise | grant-host (G1) |
+| B2 | start the executor on a `credential.mint` with no `grant` | grant-enroll (A2), grant-executor |
+| B3 | skip the `ready` check at the raise | grant-host (G19) |
+| B4 | skip the `ready` check at step 1 | grant-executor |
+| B5 | skip the definition hash compare | grant-executor (G9) |
+| B6 | drop the definition check (`host-not-declared`) | grant-host (G2), grant-executor (G9) |
+| B7 | skip the commands hash compare | grant-executor (G9) |
+| B8 | skip the host record hash compare | grant-executor (G9) |
+| B9 | write the grant record before install | grant-executor (G8) |
+| B10 | skip `remove` on a verify failure | grant-executor (G8) |
+| B11 | skip the start sweep of key files with no record | grant-executor (N1, G27) |
+| B12 | skip the reconcile's remote `remove` | grant-executor (G11) |
+| B13 | skip the `grant.step` before install | grant-executor (G11) |
+| B14 | revoke leaves the grant record | grant-executor (G12) |
+| B15 | skip `register` before `issue` | grant-executor (G7) |
+| B16 | drop the abort check after `verify`, the last one before `issue` | grant-executor (G23 X5) |
+| B17 | add an `await` between the abort check and `issue` | grant-executor |
+| B18 | revoke ignores a claim with no reference | grant-executor (G13, G23 X5) |
+| B19 | build the tag without the business | grant-executor (G24) |
+| B20 | `sweep` removes any `mosaic-` line | grant-executor (G24 B4) |
+| B21 | run revoke's host step before the local steps | grant-executor (G12) |
+| B22 | start the executor on an arbiter resolve | grant-executor (G10) |
+| B23 | start it on `no` | grant-enroll (A2, A4), grant-executor |
+| B24 | write the private key into the event body | grant-executor (G15) |
+| B25 | put an `await` between the spend and the claim | grant-executor (G23 X5) |
+| B26 | skip the start check for a resolved, unspent grant decision | grant-executor (G11 B2) |
+| B27 | make `commit` async | grant-executor (G8) |
+| B28 | route `hosts.revoke` to `Credentials.revoke` alone, as `credential-verbs.mjs` would | grant-executor (G12, G27) |
+| B29 | skip the revoke marker reconcile | grant-executor (G27) |
+
+Row 235's own:
+
+| Id | Mutant | Test file |
+|---|---|---|
+| B30 | skip the `grant.revoked` check at step 1 | grant-executor (G13, G23) |
+| B31 | the sweep set keeps a live grant's tag | grant-executor (G24 B4) |
+| B32 | reopen a `grant.revoked` with no revoke id | grant-executor (G27) |
+| B33 | step 3 reports `removed` when the host remove fails | grant-executor (G13, G27) |
+| B34 | any agent revokes, not just the assistant | grant-executor (G26) |
+| B35 | `hostLineLeft` ignores the last sweep | grant-executor (G24 B4, G27) |
+| B36 | a stale `release` frees a later claim | credential-claim (X5), grant-executor |
+| B37 | `register` replaces an entry with a live token | credential-claim (X4) |
+| B38 | drop the creative check in `#hostDefinition` | grant-host (mos-1163), grant-executor (mos-1163) |
+| B39 | drop the creative check in `#hostAccess` | grant-executor (sage-1908) |
+
+B17 may survive. `await null` yields only to microtasks, and every revoke starts in a macrotask of its
+own (a socket request, or a test's call), so none can land in that gap. If it survives I'll report it
+as equivalent under this build, not add a test that fakes a microtask revoke.
+
+Section 10 items not run as row b mutants, and why:
+
+- The upsert mutant ("let the undo to `previous` insert a record") and "run past a newer
+  `grant.revoked`". Row 235 has no undo to `previous`. A commands change commits the UPDATE and
+  `grant.applied` in one transaction (sage-1745), so a restart after it leaves the record as it is
+  (G11). The UPDATE can't meet a missing record either: step 1 reads the live record, and nothing
+  awaits between there and the UPDATE. An upsert there would be equivalent.
+- "let the executor act on an abort after step 5 commits". The record and `grant.applied` commit
+  together, and no abort check follows the commit, so no code path reaches the `if (committed)` guard
+  with an abort. Removing the guard is equivalent. C1's case is covered by G28 with a later revoke.
+- "treat a missing `bus.tester` as dev". The tester check can't be reached from a test (step 5 notes).
+- Row a's: the keyscan compare, the writer items, the "not yet enrolled" check, the `hosts` primary key
+  and `host.run` reading the business file. Row 234 ran those as A5, A6, A8, A9, A11 and A13-A19.

agents/gizmoduck/work/queue-249/BUILD.md

@@ -0,0 +1,98 @@
+# Row 249 build notes (Gizmoduck)
+
+Gitea #1751, Vikunja P19 445 under #436. Brief: docs/plans/2026-10-20_host-credentials.md, section
+"Machine grant row b follow-up: the undo can't prove the remote add has ended" (6de1ebc62). Reviewer
+Duckworth, gate owner Sage. Branch gizmoduck/row249-on-8a04, on row 248's landing 8a04f4aa4 (sage-2012).
+No file under packages/bus/src changed between 6d5545d44 and 8a04f4aa4, so the brief's src line numbers
+hold on the base. Line numbers below are on this branch.
+
+## Correction to the brief
+
+The brief, copying gizmoduck-0139, puts the sweep's host-unknown refusal at broker.mjs:1350. On
+6d5545d44 it is :1349. On this branch it is :1354.
+
+## The change
+
+`#runHostGrant` in packages/bus/src/broker.mjs:
+
+- :943 adds `installed = false` next to `installing`.
+- :956 sets `installed = true` on the line after `await this.#hostGrant.install(...)`, before the
+  `stop()` that follows it. An abort that lands after install returned still ends revoked, with no hint,
+  because install returning means every request it sent has exited.
+- :1025, in the catch, inside `if (installing)` and after the remove: `if (!installed) extra =
+  { hostLineLeft: tag };`. The remove still runs first and its result doesn't matter. A remove that
+  throws sets the same hint as before (:1021).
+
+The rule keys on install not returning, not on `signal.aborted`. That covers an abort (host-run.mjs:136,
+SIGKILL to the local group), a timeout (host-run.mjs:131-134, SIGTERM, then SIGKILL after `graceMs`) and
+a dropped connection, which fails the request with no signal at all. `#hostGrantFailed` (:845) already
+adds "A line tagged X may be left on the host. Run: mosaic hosts sweep <host>" when `hostLineLeft` is
+set (:852), so the message needed no change.
+
+False hints. install is one call that runs `list`, maybe `remove`, then `add` (host-grant.mjs:329-333).
+Any failure inside it now records the hint, including a `list` that exits 1 before any add was sent, and
+an abort that lands before the first ssh starts (the G23 X5 case at "a revoke right after the spend").
+The brief accepts this for an add that exits nonzero. The other cases are the same kind: the line isn't
+on the host, and a sweep that doesn't list the tag drops the hint (G24, "a left tag no longer on the
+host", broker.mjs:1358). Narrowing it would need install to report which request was in flight, which is
+a change to host-grant.mjs's API that the brief doesn't ask for.
+
+## Row a's enroll
+
+The race can't happen there, because enrollment sends nothing to the host. `#runEnrollment`
+(broker.mjs:772-842) writes the record, calls `this.#hostGrant.enroll(business, host)` (:800) and
+commits the fingerprint. `enroll` (host-grant.mjs:247-286) runs ssh-keygen locally and writes the
+private half to its file. It opens no ssh session. The installer line goes on the host by hand: the
+notice tells ops-01 to write it, then to run `mosaic hosts check`. The undo at :835 is `unenroll`, which
+deletes the local key file. There is no remote add to outlive a kill, and no remote undo to race with.
+
+## Tests
+
+packages/bus/tests/grant-executor.test.mjs:
+
+- `lateAdd` (:451) is the shared tail. After the grant ends it asserts the code, `hostLineLeft` on
+  grant.failed, the sweep line in the notice, and that the undo's remove was the last request. Then it
+  writes `release`, so the held add writes its line and exits 0, and waits for the line in `granted`. It
+  checks there's no record, `hosts.status` lists the tag in `hostLineLeft`, `hosts.remove` refuses
+  host-line-left, `hosts.sweep` returns `removed: [tag]` and the line is gone, then `hosts.remove`
+  succeeds.
+- :468, the abort case. `hold-add`, the human approves, the add holds, `abortClaim` aborts the
+  executor's claim. Ends revoked.
+- :480, the timeout case. A 30 s wait is too long for the file, and making the timeout an option would
+  add a src seam, so the test wraps `install` through `opts.wrap` instead. The wrapper passes install its
+  own AbortController signal, waits for `holding`, aborts it, which SIGKILLs the local ssh group as the
+  timer does, then throws as a timed-out request does. The executor's signal isn't aborted, so it ends
+  host-failed. Nothing under src changes for it.
+- G8 (:283) changes. fail-list and fail-add now carry `hostLineLeft` and the sweep line. noop-add fails at
+  verify, after install returned, so it keeps no hint and the old message.
+- The comment at :436 (:432 at 6d5545d44) now says `skip` makes the held add exit without writing and that a
+  killed session's add can still write. G13 has no such comment.
+
+Both new tests write `release`, so their held stub exits before `t.after` removes the dir. Row 248's dir
+check (:67, :72) is the backstop.
+
+## Mutant
+
+/mnt/storage/scratch/gizmo-235-out/mutants-249.py, on row 235's runner. C1 removes the :1025 line and
+runs grant-executor.test.mjs. Both new tests and G8 should fail under it. `--check` matches its anchor
+once.
+
+## Runs
+
+On Sage's grant sage-2015, at 8457af076 (7cee1a1ab plus this file), TMPDIR /mnt/storage/scratch/g249t:
+
+| Run | Window | Result |
+|---|---|---|
+| grant-executor.test.mjs whole | 13:29:01-13:29:21Z | 39 of 39 pass |
+| C1 | 13:29:21-13:29:40Z | killed: both row 249 tests and G8 fail on `hostLineLeft` undefined |
+
+After C1 the worktree was clean and broker.mjs matched HEAD. After the runs, no node, sshd or sh process had a
+cwd under the worktree or g249t, and no `fake/add` or `fake/remove` stub was running. The bus suite runs on
+Sage's gate.
+
+## Rebase onto 8a04f4aa4 (sage-2012)
+
+The first commit, 02bfd184b, sat on bc579f7a8 as gizmoduck/row249, which was never pushed. Row 248 landed
+as 8a04f4aa4, changing grant-executor.test.mjs at :54, :67 and :72. gizmoduck/row249-on-8a04 starts at
+8a04f4aa4 and cherry-picks 02bfd184b with no conflict. 248's lines stay as landed. The patch-id is the
+same on both (c33823941e61). Test line numbers moved down by one, and this file was updated for that.

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/gosalyn/work/queue-212/BUILD.md

@@ -0,0 +1,53 @@
+# Row 212 build notes, C2-01 packages/library (#1713, Vikunja #416)
+
+## Rounds
+
+- Round 1: bdf18272a on gosalyn/c2-01, base 32b54ac3b. Webby approved it in Gitea comment 29704.
+- Round 2: d3c7bbf839d9c3bf50f154b18e7e4472fbd005ed on gosalyn/c2-01-r2, rebased onto 9b5362018 after row 232 drifted three paths (sage-1714). Webby approved it at merge scope, rev 2666 against comment 29921 (webby-0052).
+- Round 3: this commit on gosalyn/c2-01-r3, one commit on the row 234 landing c771a36f4 (sage-1736, sage-1779, mos-1160). Row 234 changed scripts/mosaic, so round 3 review covers that one file.
+
+## Round 2 merge
+
+range-diff 32b54ac3b..bdf18272a against 9b5362018..d3c7bbf83 shows one change, the context line where upstream added `credentials` to the scripts/mosaic case line. Patch-id moved from 8f80dfa3 to 175f45c6 for that reason only. All three drifted hunks keep both sides:
+
+- scripts/stack-copy.sh COPY_PATHS reads `packages/queue/src packages/library/src`. Row 232's bundle, --create, --units and instance code is unchanged.
+- scripts/mosaic runs the `library survey` exec block before the case line, and the case line keeps `credentials`.
+- packages/cli/tests/stack-copy.test.mjs adds `packages/library/src/index.mjs` to the copy file list.
+
+## Round 2 singles, evidence for the 19 paths other than scripts/mosaic
+
+Run on d3c7bbf83 in Sage's slot (sage-1723) from 2026-10-21T05:00:09Z to 05:11:29Z. The HEAD and a clean tree were checked first. The counts are an awk sum over the 23 logs: 481 passed, 0 failed, 0 skipped, 0 cancelled, and every file exited rc=0.
+
+| Package | File | Pass |
+|---|---|---|
+| library | links | 6 |
+| library | mapping | 7 |
+| library | reader | 11 |
+| library | render | 11 |
+| library | survey | 4 |
+| cli | app | 30 |
+| cli | case2-unit | 30 |
+| cli | credentials | 5 |
+| cli | host | 42 |
+| cli | instances | 5 |
+| cli | project | 4 |
+| cli | stack-copy | 16 |
+| cli | stack-instances | 23 |
+| cli | stack-release-external | 25 |
+| cli | stack-release | 192 |
+| cli | tester-reads | 6 |
+| cli | tester-threads | 5 |
+| cli | usage | 2 |
+| queue | dispatch | 4 |
+| runs | task-cli | 9 |
+| webui | pinned-copy | 10 |
+| webui | service | 31 |
+| webui | views | 3 |
+
+The file list comes from the library tests plus every test that names scripts/mosaic or stack-copy.sh, by basename and by join() path. No 64-hex pin in the tests names a merged path.
+
+## Round 3 scripts/mosaic
+
+The only path both row 234 and this row change is scripts/mosaic. Row 234 added `hosts` to the cli case line and changed nothing else in the file. Round 3 takes the landed blob cce1fdee4 and adds this row's six-line `library survey` block before the case line by hand, so `hosts` stays. The mode stays 100755. The other 19 paths are byte-identical to d3c7bbf83. Against d3c7bbf83 the only difference is the `hosts` context line.
+
+Round 3 runs only the tests that read scripts/mosaic, in Sage's slot. Their counts go to Sage in T3 and onto #1713, since this file can't hold them and stay one commit. Those tests are library survey, cli app, case2-unit, credentials, hosts, host, instances, project, stack-copy, stack-release, stack-release-external, stack-upgrade, tester-reads, tester-threads and usage, queue dispatch, runs task-cli, webui pinned-copy, service and views, plus scripts/test-queue.sh. hosts.test.mjs is new with row 234.

agents/gosalyn/work/queue-221/BUILD.md

@@ -0,0 +1,158 @@
+# Row 221 build notes, C2-20 Bean and Chet persona import (#1722, Vikunja #416)
+
+Brief: docs/plans/2026-10-20_case2-rows.md "C2-20", blob 16847e94ae17 (sage-1834). Claimed rev 2736.
+Rulings: sage-1836 (fence, pairing) and sage-1840 (YAML parser, handoff).
+
+## Base
+
+Built on Morgana's row 213 r4 tip 2b3e67e36 (origin/morgana/row213-r4), since the brief says "After:
+C2-08" and 221 exports 213's fence check. Before review it goes onto 213's landing under a new branch
+name, and its tests run again there.
+
+## What changed
+
+- `scripts/case2-persona-import.mjs`, new. Verbs `stage` and `install`, usage in its header.
+- `packages/cli/tests/case2-persona-import.test.mjs`, new, and `packages/cli/tests/fixtures/case2-persona-import/`,
+  a fixture Hermes home plus `trace.mjs`, the read trace.
+- `packages/harness/src/bundle.mjs`: the three text rules in `readPersona` move into an exported
+  `personaTextFault(text)`, which returns null or the reason, and `readPersona` calls it. Nothing it
+  checks changes and the messages are byte for byte the same, so 213's creative tests hold. There is
+  one copy of the rules and the import calls it (sage-1836).
+- `package.json` and `package-lock.json`: `yaml` 2.9.0 becomes an exact direct dependency (sage-1840 Q3).
+
+## Rulings recorded
+
+Profile to name (sage-1836, answers DESIGN.md:1322 as an implementation ruling, not a PRD change).
+Hermes at df5700ebe has no field holding a profile's own name. `profile.yaml` has only `description`
+and `description_auto` (hermes_cli/profiles.py:798-850), and `agent_name` at cli.py:3494 is skin
+branding with the default "Hermes Agent". So the human passes the pairing as `--pair default=Bean
+--pair chet=Chet`. The script checks both profile directories exist, each name is exactly Bean or Chet
+and the two differ, then prints the pairing with each SOUL.md's byte count and sha256 before it writes.
+The brief's "confirm profile to name" is met by the human supplying and confirming the pairing.
+
+The persona is `<profile dir>/SOUL.md`, where Hermes loads it (agent/prompt_builder.py:1829-1855).
+The default profile's directory is the Hermes root, and others are `profiles/<name>`, with names
+checked against hermes_cli/profiles.py:37. A missing or blank SOUL.md is "no persona", as in Hermes.
+The file is staged byte for byte. Hermes strips it and runs its own scan before use, but this import
+copies her text unchanged.
+
+Handoff between the steps (sage-1840 Q4). `stage` writes 0600 files owned by whoever ran it. `install`
+runs as `<user>` and refuses a staging file that isn't its own or has a group or other bit. The script
+changes no owner. It prints the root step, `chown -R <user>: <staging>`, as an instruction. **Item for
+Jason's go:** who runs stage on `<host>`, and the root chown between the two steps.
+
+## Word list
+
+69 tool names: every literal `name="..."` in a `registry.register(` call under hermes-agent's
+`tools/*.py` at df5700ebe, plus Hermes and Discord. Two more registrations, in tools/mcp_tool.py:4997
+and :5034, and plugin tools (hermes_cli/plugins.py:430) get their names at run time, so a fixed list
+can't hold them. Matching is whole word, any case. `memory`, `terminal`, `todo`, `process`, `patch` and
+`clarify` are ordinary words, so a persona line using them in prose counts, and the count leans high.
+It is a hint for Jason and changes nothing in the import.
+
+## Channel prompts
+
+Hermes takes a platform's block from `<platform>` at the top level of config.yaml, else from
+`platforms.<platform>` or `gateway.platforms.<platform>` (gateway/config.py:1159-1178), and its
+prompts from `channel_prompts` (:1233). The script lists all three by platform, channel id and byte
+count, and says "not text" for a value that isn't a string. The dry run doesn't read config.yaml.
+
+yaml parses with `intAsBigInt`, so an unquoted 18 or 19 digit Discord id prints exactly instead of
+rounding as a double, and with `uniqueKeys: false`, so a repeated key keeps the last value as Python's
+`safe_load` does. `logLevel: "silent"` stops yaml's warnings, which quote config text. yaml reads YAML
+1.2 and Hermes's PyYAML reads 1.1. They differ on scalars such as `yes` and `0123`, but neither
+changes a channel prompt's key or its byte count for a quoted or decimal id.
+
+## yaml dependency (sage-1840 Q3)
+
+Made with `npm install --save-exact [email protected] --package-lock-only --ignore-scripts` at the worktree
+root. `git config core.hooksPath` was unset before and after. npm moved nothing else:
+
+```
+ package-lock.json | 3 ++-
+ package.json      | 3 ++-
+ 2 files changed, 4 insertions(+), 2 deletions(-)
+```
+
+```
+@@ -10,7 +10,8 @@
+       "license": "UNLICENSED",
+       "dependencies": {
+         "@earendil-works/pi-coding-agent": "0.85.1",
+-        "oauth4webapi": "3.8.8"
++        "oauth4webapi": "3.8.8",
++        "yaml": "2.9.0"
+       }
+     },
+```
+
+node_modules/yaml is 2.9.0, from the pinned pi packages (package-lock.json:502 and :556).
+
+Where it runs. `scripts/case2-persona-import.mjs` isn't in stack-copy's COPY_PATHS, and a copy carries
+no node_modules of its own beyond its `npm ci`. So the script runs from a checkout at the reviewed
+commit after `npm ci`, where `import "yaml"` resolves through the root package.json and
+`../packages/harness/src/bundle.mjs` is beside it. Whoever runs `stage` needs read access to that
+checkout and to her Hermes home, which is part of the item for Jason's go above.
+
+## Tests
+
+Round 1, on 213 r4 2b3e67e36, slot grants sage-1851 and sage-1863. One `node --test` per file.
+
+Run 1 started at 08:19:44Z. A 600 s tool timeout on my wrapper killed it at about 08:29:45Z, inside
+stack-release-external, after stack-release took 494 s. One test in this row's file failed in run 1.
+Its filter `includes("per-channel prompt")` also matched the "profile chet: no per-channel prompts"
+line that the next assert checks on its own. That was a test defect, and the script's output was
+right. The filter is now `includes(": per-channel prompt ")`. The kill orphaned one fixture
+holder.cjs, which I killed, and I removed its tmp dirs. Sage counts this as one failure under mos-0823.
+
+The rerun, 08:31:11Z to 08:33:31Z, covered this row's file, stack-release-external, stack-upgrade
+and the fixture dry run. The 15 files that run 1 finished green stand on code the fix didn't touch. Their counts come from run 1.
+
+| File | pass | fail |
+|---|---|---|
+| packages/business/tests/launch-settings.test.mjs | 16 | 0 |
+| packages/cli/tests/stack-copy.test.mjs | 16 | 0 |
+| packages/cli/tests/stack-release.test.mjs | 195 | 0 |
+| packages/conversation/tests/cohort.test.mjs | 37 | 0 |
+| packages/harness/tests/bundle.test.mjs | 22 | 0 |
+| packages/harness/tests/claude-gate.test.mjs | 3 | 0 |
+| packages/harness/tests/claude-session.test.mjs | 8 | 0 |
+| packages/harness/tests/creative.test.mjs | 7 | 0 |
+| packages/harness/tests/mcp-server.test.mjs | 5 | 0 |
+| packages/harness/tests/pi-session.test.mjs | 8 | 0 |
+| packages/harness/tests/skills.test.mjs | 10 | 0 |
+| packages/plugins/tests/harness.test.mjs | 9 | 0 |
+| packages/seat/tests/sandbox.test.mjs | 10 | 0 |
+| packages/webui/tests/editor.test.mjs | 5 | 0 |
+| packages/webui/tests/pinned-copy.test.mjs | 10 | 0 |
+| packages/cli/tests/case2-persona-import.test.mjs | 11 | 0 |
+| packages/cli/tests/stack-release-external.test.mjs | 25 | 0 |
+| packages/cli/tests/stack-upgrade.test.mjs | 20 | 0 |
+
+Total over the 18 files: 417 pass, 0 fail, 0 cancelled, summed by awk.
+
+The dry run on the fixture, `stage --hermes-root packages/cli/tests/fixtures/case2-persona-import/hermes
+--pair default=Bean --pair chet=Chet --dry-run`, exited 0 and printed:
+
+```
+files 2
+profile default: lines 3, lines starting "# " or "## " 0, lines naming a Hermes tool or channel 0
+profile chet: lines 2, lines starting "# " or "## " 0, lines naming a Hermes tool or channel 0
+```
+
+## Rebase onto 213's landing (sage-1925)
+
+213 landed as 361ba2387, with the same `git patch-id --stable` as r4 2b3e67e36, f313e69b6f7e. The
+refactor tip was 62ddc96cc. I cherry-picked 2d7a99aee onto it under the new branch gosalyn/c2-20-r2 as
+48f044ccc. The patch-id is eb094ae783e9 before and after. None of the 22 paths changed between 2b3e67e36
+and 62ddc96cc. The fence export from sage-1836 Q1 was already in the commit: `personaTextFault` from
+packages/harness/src/bundle.mjs, called by the script. I checked the test list again on the new base by
+grepping tests and scripts/test-*.sh for each non-test path's basename. The new hits name other packages'
+package.json files or write lockfiles in temp dirs, so the 18 files stand. 231 landed after that as
+29ce1e360. It touches only packages/library and the queue-231 packet, none of these 22 paths.
+
+Rerun on 48f044ccc, slot grant sage-1932, 10:18:09Z to 10:30:14Z, after a busy check. All 18 files ran
+whole, one `node --test` each, every rc 0: 419 pass, 0 fail, 0 cancelled, summed by awk. That's two more
+than the 417 above, both from the base. stack-release went from 195 to 196 and stack-upgrade from 20 to 21,
+and rows 238 and 240 changed those test files. Every other file has the count in the table above. The dry
+run printed the same three lines, rc 0.

agents/gosalyn/work/queue-230/BUILD.md

@@ -0,0 +1,104 @@
+# Row 230: C2-13a unit render and host precheck
+
+Gitea #1732. Vikunja #416 (track T2). Brief: docs/plans/2026-10-20_case2-rows.md, section "C2-13a",
+blob f6b4933f0f47 (01b40d357, sage-1562). Base: 00d4cc1f6 (row 190). Reviewer: Webby. Gate: the cli
+suite plus every scripts/test-*.sh.
+
+## What ships
+
+`scripts/case2-unit.sh` renders `[email protected]` and `mosaic-webui.service` from the two existing
+templates into the system unit directory, for the default instance only. It writes each unit through
+a temp file at mode 0644, runs `daemon-reload`, enables both units, starts the bus and then the
+Console. If the bus fails to start, the script refuses and leaves the Console unstarted. Both units
+get `WantedBy=multi-user.target`, and neither gets `After=` or `Wants=`. The script never links a unit
+file into place. A re-install refuses unless each installed unit passes the same checks, both units
+name one copy, and each equals the render apart from the copy id.
+
+`--profile library` (the default) refuses `--pm`, `--claude`, `--tester-port` and `--sso`, and needs
+the preview proxy flags plus the proof pair. `--profile factory` refuses the six proxy flags and takes
+`--pm` and `--claude`. Both refuse `--checkout` and `--board`.
+
+`scripts/case2-precheck.sh --business ID [--profile factory|library]` runs as `<user>`. It prints one
+`ok` or `REFUSED` line per check and exits 1 if any check refused. It prints variable names only,
+never values.
+
+`packages/cli/README.md:713` now says nothing creates the session env file, only the Case 2 precheck
+reads it, and the precheck prints only variable names (webby-0034 N2, webby-0035).
+
+## Deviations for review
+
+Sage accepted all six for the build (sage-1570). Webby rules on each.
+
+1. The precheck takes `--business ID`. The brief names no other way to find the business file.
+2. A run root `<dataRoot>/launches/<business>` that doesn't exist passes, with a note that the first
+   launch creates it at 0700 (session.mjs:47 and newRun). A symlink refuses, and so does an existing
+   entry that isn't a 0700 directory.
+3. The claude marker check passes when the reply holds the marker and input plus cache tokens are at
+   most 2000. **The 2000 ceiling is unmeasured.** The tests use fakes at 40 and 9000 tokens. Measuring
+   it on a real claude belongs to row 195's install run, not this row.
+4. A non-root test can't create a root-owned proof file. For the "proof not owned by the user" case,
+   the fake getent reports another uid for the user, so the user's own file reads as someone else's.
+5. The unit script refuses `%h` left in any unit, rendered or installed. A system unit expands `%h`
+   to root's home. The render replaces every `%h`, so the test edits an installed unit to reach it.
+6. With `--auth-header X-Authentik-Uid`, the allowed user must be 64 lower-case hex characters (lead
+   decision 101). The test covers both the refusal and the pass.
+
+## Tests (packages/cli/tests/case2-unit.test.mjs, 30 cases after round 2)
+
+The tests use a scratch unit directory and a scratch home, plus fake systemctl, getent, sudo, id,
+node, bwrap and claude. They never touch /etc/systemd, ~/.mosaic-dev, ~/.config/mosaic-dev or a
+live unit. Every precheck case asserts its output doesn't hold the fixture key.
+
+- Unit: the clean library render, PATH for a node outside the default list and for /usr/bin/node, the
+  systemctl order, a failed bus start, no `systemctl link`, factory `--pm` and `--claude` rendered and
+  absent, re-install to another copy, edits to an installed unit, template restrictions,
+  EnvironmentFile placement, unknown tokens, PermissionsStartOnly and `+`/`-+` Exec prefixes,
+  symlinked unit paths, bad `--node`, re-install drift, a split copy pair, bad copy ids, every library
+  and factory flag refusal, and bad `--claude`.
+- Precheck: a good host, node older than 24, more than one group, sudo succeeding, XDG_DATA_HOME,
+  HOME mismatch, a run root mode, a bad config, bwrap failing, the port floor at or below the Console
+  port, a missing Console unit, bus.tester per profile, profile-library-business, the claude check
+  (no route, replaces, appends, missing, the unit's MOSAIC_CLAUDE_BIN beating PATH), and the session
+  env file (missing, 0644, symlink, empty, emptied by a later line, quoted).
+- Bind (mos-1100): inside `binds()` plus `sandboxArgv()`, a bind on port 980 gets EACCES, and a bind
+  on a free port of 1024 or above succeeds. The test fails if the host's floor is at or below 980.
+
+## Verification
+
+Round 1 singles, run before the gate: case2-unit.test.mjs passes 28/28 with no skips, and host.test.mjs (it
+reads the cli README) passes 42/42. No test pins a hash of the README. No other test reads the two
+scripts.
+
+## Round 2 (webby-0046, sage-1589, sage-1590, sage-1591)
+
+Base: origin/refactor (rebased from 00d4cc1f6; the 15 commits between touch none of the five paths
+or the two unit templates). Branch gosalyn/c2-13a-r2.
+
+B1. The precheck now has a case for each refusal Webby named: the user missing from passwd (:77),
+a business file that is unparsable, missing or fails the schema (:137), a run root that is a symlink
+to a 0700 directory (:151), a Console ExecStart with no --port (:179), an unreadable port floor
+(:180), a claude reply without the marker (:223) and a claude reply that isn't JSON (:224). The fake
+claude gained `nomarker` and `text` kinds. The no-claude-code case and the missing-claude case share
+a PATH without `/usr/bin/claude` (`pathWithoutClaude`), so the no-claude-code case now shows a host
+with no claude passes.
+
+N1 (ruled in for this round). Before writing, `case2-unit.sh` asks `systemctl is-active` for both
+units. For each unit that was running, it prints that the unit is still on its old copy, never
+"started", and then that the bus and Console must restart together to reach the new copy. A unit
+that wasn't running gets "started ... on copy". A fresh install prints the round 1 line. The script
+still restarts nothing. The new test covers both units running and only the Console running.
+
+N4. The README line at :713 is rewrapped.
+
+Mutants, run in Sage's slot on a scratch worktree, one branch each: :77, :137, :151, :179, :180,
+:223, :224, a precheck that refuses with no claude on PATH (for the no-claude-code case), and an
+install that prints "started" for a running unit (sage-1591).
+
+## Carry items for row 195
+
+- N1's restart. Row 195 restarts the bus and Console together after a re-install over running
+  units, as the install line now asks.
+- N2. A system drop-in check like `bus-service.sh:122-145`, so a drop-in under
+  `[email protected]/` or `mosaic-webui.service.d/` can't change what the checked unit runs.
+- N3. The precheck finds claude on the shell PATH. The bus unit's `PATH=` is what a session uses
+  when `MOSAIC_CLAUDE_BIN` is unset, so the check should search that PATH.

agents/gosalyn/work/queue-231/BUILD.md

@@ -0,0 +1,96 @@
+# Row 231 build notes, C2-01b survey escapes, list item lines and attachment embeds (#1733)
+
+Brief: docs/plans/2026-10-20_case2-rows.md "C2-01b survey escapes, list item lines and attachment embeds",
+blob 16847e94ae17. These are Webby's row 212 notes N1 to N3 (webby-0041), split out by sage-1517.
+
+## Base
+
+First built as 777f7358a on 212's first round bdf18272a. 212 landed as ee7b2f137 (sage-1886), so the
+commit was cherry-picked onto refactor fefd54e13 under the new branch gosalyn/c2-01b-r2 as 3647a5a93.
+`git patch-id --stable` is 45911915a9ee before and after. packages/library is the same in bdf18272a
+and in 212's landed round a2c72ac95, so nothing the commit touches moved under it.
+
+## What changed
+
+- N1, `packages/library/src/survey.mjs`: JSON strings escape C0 controls but leave DEL, C1 and bidi
+  controls raw. The new `quote()` escapes those too, and folder names print through it.
+- N2, `packages/library/src/reader.mjs`: front matter parsing records each block list item's line, and
+  a link in a block list carries its item's line instead of its key's.
+- N3, `links.mjs` exports `isAttachment` through `index.mjs`. A wikilink or embed whose target's last
+  segment ends in an extension other than `.md` is an attachment. The reader neither resolves nor
+  indexes it, and it raises no problem. The survey prints a count of body links to attachments.
+- `packages/library/README.md` describes all three, and the links, reader and survey tests cover them.
+
+## Outside readers
+
+`packages/cli/tests/stack-copy.test.mjs:38` checks only that `packages/library/src/index.mjs` exists, and
+`scripts/mosaic:41` execs `survey.mjs`. No test pins a hash of a library file.
+
+## Tests
+
+On 3647a5a93, slot grant sage-1889, 09:20:01Z to 09:20:14Z, after a busy check. One `node --test` per
+file, every rc 0.
+
+| File | pass | fail |
+|---|---|---|
+| packages/library/tests/links.test.mjs | 7 | 0 |
+| packages/library/tests/mapping.test.mjs | 7 | 0 |
+| packages/library/tests/reader.test.mjs | 13 | 0 |
+| packages/library/tests/render.test.mjs | 11 | 0 |
+| packages/library/tests/survey.test.mjs | 6 | 0 |
+| packages/cli/tests/stack-copy.test.mjs | 16 | 0 |
+
+Total: 60 pass, 0 fail, 0 cancelled, summed by awk.
+
+## Round 2, after webby-0070 (CHANGES) and sage-1900
+
+Webby's round 1 review is agents/webby/work/queue-231/REVIEW-r1.md at 387f04dfd, rev 2774.
+
+Ruling sage-1900, recorded here as asked. B2: the brief stays as approved (sage-1517, case2-rows.md
+C2-01b N3). Only a `![[x.ext]]` embed can be an attachment. Plain wikilinks and front matter values keep
+resolving, and an unresolved one is R4. README's line "A link to a `.canvas` file or an attachment is
+R4" is back as it was at fefd54e13. B1: resolve first. An embed is an attachment only when it resolves
+to nothing and its target has an extension other than `.md`. So `![[Dr.Quinn]]` with Dr.Quinn.md
+indexed resolves, `![[cover.png]]` gives no problem, `![[missing-note]]` is R4 and `![[note.md]]`
+resolves. My own design ruling after r11 (28213ac27) also made plain links attachments. The brief
+narrowed that, and the brief governs this row.
+
+Changes:
+
+- `links.mjs`: `isAttachment` is true only for a body embed, `link.embed === true && !link.field`,
+  with the extension test as before. Its comment says it goes by name, so the reader asks it only
+  after resolving.
+- `reader.mjs`: every link resolves first. An unresolved one is R4 unless `isAttachment` holds.
+- `survey.mjs`: `quote()` also escapes U+061C (Webby N1). The attachment count now covers body embeds
+  only, since it uses `isAttachment`.
+- Webby N2, my choice of Sage's two options: the survey keeps a count by name and the README says so,
+  "the count of body embeds whose target has an extension other than `.md`", and that `![[Dr.Quinn]]`
+  counts there even when Dr.Quinn.md exists. Checking against the survey's path list would mean a second
+  resolver in the survey, for a count that only guides the mapping.
+- Tests. links: embeds only, with `[[cover.png]]`, `[[Board.canvas]]`, `[[Dr.Quinn]]`, a front matter
+  value and a markdown link all false, and `![[Dr.Quinn]]` true by name. reader: the Shore case now
+  gives R4 for the front matter `"![[portrait.JPG]]"` (line 3), for `[[Board.canvas]]` (line 5) and for
+  `![[missing-note]]` (line 6). The new Dr.Quinn case has Dr.Quinn.md indexed and resolves `[[Dr.Quinn]]` in
+  a block list and in the body, plus `![[Dr.Quinn]]`, with no problem. survey: a U+061C folder name
+  prints escaped, and the attachment count is 1, since `[[map.PDF]]` is a plain link.
+
+Round 2 tests, one `node --test` per file, each run after a busy check.
+
+Run 1, slot grant sage-1903, 09:39:32Z to 09:39:46Z: 60 pass, 1 fail. The new Dr.Quinn reader test failed
+on order alone. All three links resolved to Dr.Quinn.md with the right field, line and embed values, and
+there was no problem. The reader lists body links before front matter links, and my expected array put
+the `relationships` link first. I stopped and reported it (gosalyn-0098).
+
+Run 2, after the test-only fix sage-1907 approved, which moves that entry to the end of the expected array,
+09:43:42Z to 09:43:56Z. Every rc 0.
+
+| File | pass | fail |
+|---|---|---|
+| packages/library/tests/links.test.mjs | 7 | 0 |
+| packages/library/tests/mapping.test.mjs | 7 | 0 |
+| packages/library/tests/reader.test.mjs | 14 | 0 |
+| packages/library/tests/render.test.mjs | 11 | 0 |
+| packages/library/tests/survey.test.mjs | 6 | 0 |
+| packages/cli/tests/stack-copy.test.mjs | 16 | 0 |
+
+Total: 61 pass, 0 fail, 0 cancelled, summed by awk.

agents/gosalyn/work/queue-247/BUILD.md

@@ -0,0 +1,87 @@
+# Row 247 build notes, C2-20b persona import follow-up (#1749)
+
+Brief: docs/plans/2026-10-20_case2-rows.md "C2-20b persona import follow-up: printed keys, the dry run
+fence check and the mkdir race", landed in 335bb3e30. These are Webby's row 221 notes N1, N2 and N4
+(webby-0073, REVIEW-r1 a0a00630e on webby/reviews). N3 is in DEFERRED (sage-1941).
+
+## Base
+
+Branch gosalyn/c2-20b from 335bb3e30, which is row 221's landing 300766450 plus the brief.
+
+## What changed
+
+- N1, `scripts/case2-persona-import.mjs`: the per-channel prompt line prints the platform key, with its
+  fixed `platforms.` or `gateway.platforms.` prefix, and the channel key through `JSON.stringify`. A key
+  holding a newline prints as `\n` inside one quoted line. The profile name on that line is not config
+  text: `pairing` already holds it to `PROFILE_ID`.
+- N2: the dry run calls `personaTextFault` on each persona after its count line. A fault prints as
+  `profile P: persona <reason>, so C2-08's fence would refuse it`, where the reason is the fixed string
+  `personaTextFault` returns, never persona text or a line number. With any fault the run refuses, exit
+  1, and writes nothing, as stage would. The header comment no longer says a fault is counted, not
+  refused, and now says a SOUL.md over four times the fence in bytes refuses before any count, which is
+  what `soul()` already did (Webby's second point under N2).
+- N4: `privateDir` catches an EEXIST from its mkdir and refuses with `<path> was made by something else
+  between the check and mkdir`. Any other mkdir error is thrown as before, since the brief names only
+  EEXIST.
+- Tests, `packages/cli/tests/case2-persona-import.test.mjs`:
+  - The per-channel prompt test expects the quoted keys.
+  - New: a chet config.yaml with a newline in the platform key and in the channel key prints one quoted
+    line, and no output line starts with the forged text.
+  - The dry run heading test now expects the fence fault line, exit 1 and the refusal, still with
+    nothing written. Its persona has two heading lines, which the fence refuses.
+  - New: a persona of 8001 two-byte characters, 16002 bytes and under the 32000 byte cap, makes the dry
+    run print the over 8000 characters fault, write nothing and exit 1. At exactly 8000 it exits 0.
+  - New: the mkdir race refuses by name at stage, for the staging directory, and at install, for
+    `personas/<business>`. Each refused directory is left empty.
+- New fixture `packages/cli/tests/fixtures/case2-persona-import/mkdir-race.mjs`, an `--import` preload
+  like `trace.mjs`. It makes the directory named by `$PERSONA_MKDIR_RACE` just before the script's own
+  `mkdirSync` of that path, so the script meets a real EEXIST from the kernel, not a thrown stub.
+
+## Known limit of N1
+
+`JSON.stringify` escapes C0 controls, `"` and `\`, but leaves DEL, C1, U+2028, U+2029 and the bidi
+controls raw. None of those ends a line on a terminal, so the forged line N1 names can't happen. A bidi
+control could still reorder how the rest of that one line displays. The brief asks for `JSON.stringify`,
+and Sage kept it in sage-1964 because the keys come from Jason's own Hermes config. Note for Webby: row
+231's `quote()` in packages/library covers the wider set, and this row doesn't import it. If you want it,
+ask for it in review.
+
+## Mutants
+
+One per fix, plus a second for N1 so each of its two keys has its own. Each replaces one exact string
+in the script, runs the test file, then restores the script from a copy and checks its sha256.
+
+| Mutant | Fix | Change |
+|---|---|---|
+| M1 | N1 | the channel key prints raw |
+| M2 | N1 | the platform key prints raw |
+| M3 | N2 | the dry run's refusal after a fault is skipped |
+| M4 | N4 | privateDir's EEXIST branch never matches, so EEXIST is thrown raw |
+
+## Outside readers
+
+`git grep` over packages/*/tests/* and scripts/test-*.sh finds `case2-persona-import` only in its own
+test file and in two files of its fixture tree, README.md and trace.mjs, which name the test file in a
+comment. No test pins a hash of the script.
+
+## Tests
+
+Two slot runs, `busy.sh && run.sh` in /mnt/storage/scratch/gosalyn-r247, on the test file alone.
+
+Run 1, grant sage-1969, 11:47:45Z to 11:48:00Z, was red: 14 tests, 12 pass, 2 fail. The fault was in the
+script. Adding `JSON.stringify` to the per-channel line dropped the space after the comma, so it printed
+`"-1001",29 bytes`. The two per-channel tests caught it. run.sh also went on to the mutants with a red
+base, so their counts meant nothing. Sage approved both fixes in sage-1971: the space goes back, and run.sh
+now exits 3 before the mutants unless the base is rc=0 with fail 0.
+
+Run 2, grant sage-1971, 11:49:04Z to 11:49:22Z, was green: 14 tests, 14 pass, 0 fail, rc=0.
+
+| Mutant | Line | rc | Failed | Killed by |
+|---|---|---|---|---|
+| M1 | 237 | 1 | 2 | the per-channel prompt test and the newline key test |
+| M2 | 237 | 1 | 2 | the same two |
+| M3 | 238 | 1 | 2 | the dry run fence test and the dry run heading test |
+| M4 | 192 | 1 | 1 | the mkdir race test |
+
+After the run the script's sha256 was 7031d2c0dc9bd22bc748b364a35b461fc01cb98b795032a2e0ec436f3188d4e4, the
+same as the copy taken before it. The /proc scan found no process in the worktree or the scratch dir.

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/herb/work/queue-197/BUILD.md

@@ -0,0 +1,432 @@
+# Row 197 execution ledger
+
+Plan: MANIFEST.md r2, approved by Webby ca6b32d66.
+Build grant: sage-1390. Suites, image builds and paired proof are not granted.
+Rebased five documentation commits onto origin/refactor aa1bd209e before code.
+Existing worktree herb/row197 and plain node_modules symlink retained.
+
+- T1 preflight/steps: in progress.
+- T2 locks/status/recovery: pending.
+- T3 image/Docker: pending.
+- T4 fixtures/timing: pending.
+- T5 evidence/acceptance: historical timing done; implementation pending.
+
+Preflight interfaces: T1 RunPaths supplies T2 ownership and T3 image checks.
+T2 run receipt supplies T4 lane/port state and T5 attribution. T3 image identity
+is checked before Docker-bearing steps. T4 timings supply T5 pair summaries.
+No interface conflict found. No product API or assertion changes are authorized.
+
+Ruling: use this approved BUILD.md as the execution ledger, rather than adding
+skill workspace paths outside the manifest. This preserves the reviewed path
+boundary. Missing ledger detail would cost recovery time, not product behavior.
+
+## Implementation checkpoint 2026-10-20T20:11:58Z
+
+T1-T5 source is present within the approved manifest. Full acceptance is pending.
+Fresh single-file checks: preflight/supervisor 6/6; state/recovery 11/11; image and
+Docker guard 4/4; port leases/attribution/proof summary 3/3. No skips or failures.
+Existing files checked singly: board serve; WebUI serve, preview, proof-cli,
+tester-cli and service; harness pi and Claude. Stack-release R1 selected single
+passed 1/1. WebUI service also passed 31/31 with lane-a leases and a 30-byte root.
+All existing assert lines are unchanged. Shell syntax and diff checks pass.
+
+Observed defects fixed during the single-file cycles: cancellation incorrectly
+returned zero when a TERM handler exited zero; recovery did not supersede an
+unclean terminal; status omitted the lock-before-receipt window. Evidence logs
+retain the failing and passing observations. Source still has no commit because
+applicable suites have not run. No image build, proof, push or live operation.
+
+Ruling: use an instrumented single-lane author gate on a frozen dirty-source
+clone before committing source. The new wrapper requires a clean candidate and
+proven image receipt, while repository rules require green suites before source
+commits. The author gate retains every suite and assertion, caps concurrency at
+two, uses own port/state/temp/project roots, and guards Docker against builds.
+Cost if wrong: the author gate fails; clean-candidate wrapper baselines and the
+paired proof remain mandatory after source is verified and committed.
+
+Ruling: publish the initial run directory atomically after the start receipt is
+complete. This avoids a second lane observing a partially written start. A
+crash before publication has started no test or mutable Docker operation.
+Cost if wrong: a lane refuses or quarantines; no protected state is bypassed.
+
+## Implementation review corrections, 2026-10-20T20:33Z
+
+Webby-0029 reviewed the first implementation packet at f942bd7d4.
+B1 identified missing manifest tests. B2 identified a test that leased both real
+bands through a private lock namespace. The old author-gate clear was withdrawn
+in herb-0019. SOURCE.json, BUILD.patch and gate.sh still describe the old frozen
+clone. They are not a clear for the edited working tree. No author gate ran.
+
+B2 correction: the helper test uses only the active lane and MOSAIC_GATE_STATE.
+It compares the other band arithmetically and has no unasserted listener. The
+occupied-port probe first obtains its own real lease, binds that port, and
+asserts that its sentinel listener survives refusal. No test reserves another
+lane's band. Exhaustion narrows only the test process's band to one owned port.
+
+B1 coverage added within the existing approved paths. No case is dropped:
+
+| Manifest case | Added check |
+| --- | --- |
+| T1 canonical and builder checkout, existing output | gate-lane.test: direct validateRun refusals |
+| T1 92-byte socket and over-107-byte socket | exact design example with a distinct gt- test root; 108-byte refusal |
+| T1 both candidates carry tooling | validateTooling compares each launcher file, including missing and changed cases |
+| T1 duplicates and NODE_TEST_CONTEXT | repeated package/script fixture is retained; sanitized environment is exercised by both supervised children |
+| T2 one-winner race and inherited FDs | two actual shell wrappers race; a controlled supervisor verifies held FDs, and its child checks that no FD points to either lock file |
+| T2 same checkout and legacy claim refusal | activeConflicts uses synthetic process observations with a live lane and a sibling landing gate |
+| T2 surviving child and interrupted recovery | locked recovery kills a child proven by the private root, preserves a foreign child, is killed during fake Docker cleanup, leaves quarantine, and resumes under a new fixture grant |
+| T3 missing receipt and missing image | verifyImage refuses absent provenance and failing inspection |
+| T3 tag changed mid-gate and at gate end | runGate now uses the same executePinnedSteps boundary exercised by the tests; the next step never runs after a changed ID |
+| T3 mutable-tag rebuild | fake preparation returns a new image ID with identical input digest; the old receipt refuses it |
+| T3 cold and warm counters | preparation records one build and its time; warm execution records zero builds; repeated verification never builds |
+| T4 parallel test-file leases | two generated Node test files hold ports in the same lane/state; locks are checked during child execution and shutdown |
+| T4 exhausted band, occupied port and foreign listener | a one-port process-local band refuses both a held lease and an existing sentinel listener; the listener survives |
+| T4 owner death | a killed allocator releases only its own holder; a foreign lease remains held |
+| T4 lease through child shutdown | parent probes the lock while the fixture test runs and after its child has stopped |
+| T4 fixtureCacheEnv | replacement child environment writes only under separate tmp, jiti and cache directories |
+| T5 unrelated session append | a separate process waits for a running-step barrier, appends under a fixture HOME, and remains unrelated in the resulting metadata attribution |
+
+N1 removes the unused closed binding. All leases reserve an unbound endpoint;
+existing closed options need no call-site change. N2 makes child TMPDIR a tmp
+subdirectory. N3 normalizes ss interface scopes before checking port 9. N4 uses
+gt- for unit run roots. N5 documents the canonical node_modules dependency.
+N6 is recorded: row 200 also edits stack-release.test.mjs; the second landing
+must rebase and rerun that file singly. Sage was told in herb-0019.
+
+Before Sage's hold, expanded preflight tests passed 11/11, state tests 14/14,
+image tests 7/7, and the pi/Claude singles passed 8/8 each with separate tmp
+subdirectories. Later source/test edits still need verification. In particular,
+the new parallel test-file probe had a cleanup-order defect and is unverified.
+Its root cleanup ran before child shutdown. Cleanup now stops children before
+removing their root. Output is retained for a useful failure report. The initial
+FD probe also assumed Node did not reopen FD numbers; it now checks the actual
+lock targets. The early passing fixture file covered child allocators, before
+they were changed to actual generated test files. It is not acceptance of the
+latest file.
+
+Sage-1448 stopped all node --test runs at 20:30Z for Rocko's browser slot.
+The remaining owned process tree was stopped at 20:30:32Z. Inspection found no
+remaining owned test processes afterward. Edits and static inspection continue.
+20 module syntax checks, shell syntax and git diff checks pass. Existing-file
+assertion lines remain identical to HEAD. No test is run during the hold.
+
+Next: after Sage passes Rocko's clear, verify the corrected files singly,
+including a lane-env helper-file check. Then refresh the frozen clone and all
+three packet artifacts, send their hashes, and request a new author-gate clear.
+Suites, image builds and paired proofs still need their own grants. No source
+commit, push, suite, real Docker build or paired proof has run in this phase.
+
+## Refrozen review packet, 2026-10-20T20:41Z
+
+Sage-1454 lifted the single-file hold. Fresh runs passed without failures or
+skips: review-t1-resume.log 11/11, review-t2-resume.log 14/14,
+review-t3-resume.log 8/8, review-t4-resume.log 8/8. The helper file also passed
+8/8 with lane-a environment in review-t4-lane-a.log. Its retained state had only
+an a port-lock namespace, no b directory, and every lock was released. Generated
+fixture Node test entries explicitly use --test-concurrency=2. The child-test
+probe now finishes and cleans up before removing its root. All 41 new tests pass.
+
+B1 and B2 fixes are ready for Webby's review. No manifest case was dropped.
+All 25 source paths were copied to a new frozen clone and compared by mode and
+SHA-256. This supersedes the earlier withdrawn source packet:
+
+- SOURCE.json: 91ba149f2fc039a8bed0e6d1ad5da44b80fb8cbec84d0fa4e38616040138596b
+- gate.sh: 48e06e23e45d3484755f8cd79ad5b6dfde5ef4f960081e7c455a2540e707fed1
+- BUILD.patch: 0b3871bd9848ca223c7cda50266debc04643e5d986eb7f0fece096aaf25ff43e
+- Frozen checkout: /mnt/storage/scratch/mg197-a-d22dacd92735/wt
+- Output: /mnt/storage/scratch/mg197-a-d22dacd92735/out
+- Temporary root: /mnt/storage/scratch/ga-VPXhG7 (30 bytes)
+- Compose project: mg197-a-d22dacd92735
+
+After an explicit author-gate grant, run this command with Sage's actual ID:
+
+```sh
+env MOSAIC_GATE_GRANT=ACTUAL_SAGE_GRANT_ID bash /home/jwoltje/.t3/worktrees/mosaic-stack/herb-row197/agents/herb/work/queue-197/gate.sh > /mnt/storage/scratch/mg197-a-d22dacd92735/out/gate.log 2>&1
+```
+
+No gate or suite has started. Queue order from sage-1454 is 192, 201, 204,
+200, Gander, then 197. No branch deletion is authorized or attempted. Any later
+rebase uses a new branch name, and pr-merge.sh -d stays off under #426(a).
+Whichever of rows 197 and 200 lands second must rerun stack-release singly.
+Clean-candidate wrapper baselines, image preparation and paired proofs remain
+separately gated acceptance work. There is still no source commit or push.
+
+## Implementation approval and final notes, 2026-10-20T20:47Z
+
+Webby-0031 approved r2 in REVIEW-impl-r2.md at 1f404c973. Their static review
+verified every source hash/mode and patch result, and all B1/B2 cases. No queue
+review request comment exists yet; Sage owns creating it if needed.
+
+Folded all three optional notes into the same approved paths. The helper file's
+standalone fallback now shares /mnt/storage/scratch/mosaic-gate-lanes with real
+lane-a leases and leaves its stable lock files in place. Band assertions use the
+imported BANDS. Both T5 polling children fail after five seconds if their barrier
+is missed. README records the shared standalone namespace and deadlines.
+
+Fresh single-file logs review-r3-fixtures.log and review-r3-lane-a.log both pass
+8/8 with zero skips. The lane-a run has no b lock directory, and every lock was
+released. Syntax and diff checks pass. No existing test assertions or timeouts
+changed. Remaining source matches the 11/14/8-file checks from r2.
+
+Refreshed all 25 source rows in the existing frozen checkout. New digests replace
+the preceding r2 packet. gate.sh and its command are unchanged:
+
+- SOURCE.json: 3584763642506e81a532c839bdd07b111d25daa87e35dbe441d8e8c01a2c2aab
+- gate.sh: 48e06e23e45d3484755f8cd79ad5b6dfde5ef4f960081e7c455a2540e707fed1
+- BUILD.patch: 55fe390da17ab926a0593d39e79561abe52756a1b1a2c756ec57f45d90f10fde
+
+Author gate remains unstarted and queued for Sage's explicit grant. No source
+commit, suite, image build, paired proof, push or branch deletion ran.
+
+## R3 approval receipt
+
+Webby-0033 approved r3 in REVIEW-impl-r3.md at a5643f9bd. Static review verified
+the three packet hashes, all 25 source rows, and the patch result. Their review
+accepts N1-N3; no additional hang-guard test is requested. No queue review request
+comment exists yet, so Webby has not recorded a queue review.
+
+Read-only verification after receipt confirms that the approved packet hashes
+and all 25 worktree/frozen source hashes and modes still match. Source and gate
+script stay frozen. The author gate has not started and still needs Sage's grant.
+
+## Queue review round 1
+
+Sage-1476 authorized moving row 197 to in-review before the author gate.
+Created CANDIDATE.sha256 from the same 25 reviewed SOURCE.json rows. Its digest
+is 6318f0d0bba9ee90ccaa3503cac8c2e04c6397f2ef6c3564f687fbc2092989e3.
+Ran the queue move from the canonical checkout with op herb-197-review-r3.
+The move succeeded at revision 2395, opening round 1 on #1695. The request post
+failed before send because MOSAIC_GITEA_CREDENTIAL_FILE is not set; revision 2396
+records the failed outcome. Exit code 1 describes the failed post, not a failed
+row transition. Read-back confirms state in-review and the correct candidate.
+Sage will post as jarvis and give Webby the request comment number. No credential
+lookup, alternate post or retry was attempted here.
+
+SOURCE.json, BUILD.patch, gate.sh and all 25 frozen source rows remain unchanged.
+Latest slot order is row 190 r2, 201, 204, 200, Gander, then Herb. No gate starts
+before Sage sends an explicit grant ID.
+
+## Follow-on assignment
+
+Sage-1503 assigns row 215, Case 2 C2-04, to Herb after row 197 (queue rev 2455,
+Gosalyn design r11). Read docs/plans/2026-10-20_case2-rows.md, C2-04 section,
+at 5b8def2f1 when starting that row. Its required base is origin/refactor
+305857c8f. This assignment does not replace row 197 or authorize its gate.
+Keep row 197's approved source frozen while awaiting Sage's grant. Start row
+215 only after row 197, using a new branch name under the existing fleet rule.
+
+## Round 2 merge preparation on row 233
+
+Sage-1757 replaces history replay with one candidate commit on 57f59e0c3.
+The attempted history replay on herb/row197-r2-233 had already finished when
+that instruction arrived. Its only conflict was the append-only BUILD-LOG tail.
+That branch remains for history; none of its replayed commits is in this round.
+The current branch is herb/row197-r3-233, directly from
+57f59e0c399ce29b1bb85ca6af686fdc10eb195d.
+
+Stash correction: shared refs/stash was used incorrectly. The exact entry
+2767b88549dfd8c7e810908b5416876fa50cb571 is now kept on
+herb/row197-r3-wip. After verifying stash@{0} still named it, only that entry was
+dropped. The two other entries remain. No further stash creation, force push,
+branch deletion or refs/stash mutation is planned. A separate working-copy
+backup is /mnt/storage/scratch/herb197-merge-W4oiLg.
+
+Sage-1760 requires preserving every landed hunk on every changed manifest path.
+Checked each of the 25 r1 paths with git diff aa1bd209e 57f59e0c3 -- PATH.
+Exactly three changed upstream. Their r2 diff against 57f59e0c3 is captured in
+r2-merge-only.patch:
+
+| Merged path | Only row 197 changes against landed base | Landed content retained |
+| --- | --- | --- |
+| packages/cli/tests/stack-release.test.mjs | leasePort and laneAfter imports; freePort now calls the lease helper | All landed tests, including row 233's tests after R15 and BACKUP_STORE checks |
+| packages/webui/tests/service.test.mjs | leasePort and laneAfter imports; closedPort now calls the lease helper | SEND_REFUSAL permits --sso; default unit rendering removes the @CONFIG_ENV@ line |
+| scripts/test-discord.sh | fixture PI_CODING_AGENT_DIR setup; optional two-worker nested Node cap | Row 190's absent scratch MOSAIC_CONFIG selection and caller-config restoration |
+
+The other 22 paths equal the r1 reviewed source bytes and modes. r2-MERGE.json
+lists every path, its r1/r2 digest, mode, upstream-change flag and equality result.
+Source copies came from the hash-verified r1 frozen checkout. Original r1 digest:
+6318f0d0bba9ee90ccaa3503cac8c2e04c6397f2ef6c3564f687fbc2092989e3.
+No existing assertion or timeout line differs from the landed base. Static
+checks only: 20 module syntax checks, four shell syntax checks and git diff check
+pass. BUILD-LOG.md equals 57f59e0c3 byte for byte and is outside this commit.
+
+Sage explicitly requested the local candidate SHA before granting tests. This
+commit is an untested preparation checkpoint, not gate evidence. No tests or
+push are authorized yet. r2-TEST-FILES.txt lists the requested grant scope:
+16 Node test files singly and scripts/test-discord.sh, test-foundation.sh and
+test-queue.sh. The four stack-release consumers are stack-release.test.mjs,
+stack-release-external.test.mjs, stack-upgrade.test.mjs and stack-instances.test.mjs.
+The shared stack-release-fixture.mjs is exercised by its importing test files,
+not run as a standalone test. This covers all 13 touched Node test files plus
+three additional stack-release consumers and all three touched shell suites.
+
+Current slot order from sage-1760: Gizmoduck, Launchpad, Darkwing, then Herb,
+around 06:30Z. Wait for an explicit grant. After granted checks and authorized
+push, build the new candidate manifest from that pushed tip and open the
+merge-scoped round 2. Old SOURCE.json, CANDIDATE.sha256 and gate.sh remain r1
+historical artifacts and are not a clear to run the merged candidate.
+
+## Round 2 rebuilt on row 234
+
+Sage-1776 names landing c771a36f4bd0b6c359282425c668996a90072f93.
+Built a new branch, herb/row197-r4-234, directly from that landing. No history
+replay, stash, force push, branch deletion, test run or push is involved.
+The prior candidate a3b7cbde8 remains untested and is not the queued candidate.
+
+Checked git diff --name-only 57f59e0c3 c771a36f4 against all 25 source paths.
+Only packages/cli/tests/stack-release.test.mjs overlaps; the other 24 do not.
+The full comparison is in r2-on234-OVERLAP.txt. The stack-release file starts
+from the landing and keeps both T46 untimed entries, host_grants and hosts.
+Its only changes against the landing are the leasePort and laneAfter imports
+and freePort's call to the lease helper. r2-on234-merge-only.patch records those
+hunks. Existing assertions and timeouts match the landing exactly.
+
+Every other source path equals a3b7cbde8 byte for byte and retains its mode.
+This includes the previously merged service and test-discord files, preserving
+all landed --sso, CONFIG_ENV and scratch-config handling. The earlier evidence
+r2-MERGE.json still records those three pre-234 merge cases. The new
+r2-on234-MERGE.json records each current digest, prior digest, mode and equality
+result. BUILD-LOG.md equals the new landing byte for byte and is excluded.
+
+Static check of the changed Node file and the candidate diff pass. No tests
+were run. The scope stays r2-TEST-FILES.txt: 16 Node files singly plus the three
+shell suites. No manifest or queue round is rebuilt until granted checks and
+authorized push. Old SOURCE.json, CANDIDATE.sha256 and gate.sh remain historical
+r1 evidence. The test slot follows Darkwing 240 and needs Sage's explicit grant.
+
+
+## Round 6 preparation (sage-1883, mos-1162)
+
+New branch herb/row197-r6 starts at fefd54e13, after the standalone row
+212 landing ee7b2f137. No r5 manifest path changed between e7078e6a8 and
+this base; all 32 r5 blobs and modes were copied intact before the two
+umask changes. No history replay, stash, force push or branch deletion.
+
+executeSteps now launches each argv through /bin/bash with umask 022
+and exec, preserving the process group and argv boundaries. The supervisor
+and gate-lane.sh retain 077, including state, locks, private logs and roots.
+New gate-lane tests assert the actual child umask and created file mode,
+the unchanged parent mask, private log mode, and actual wrapper-created
+state/lock modes. No shell, image preparation, credentials test or other
+existing assertions changed. process.test.mjs equals the landed base;
+lane-image.mjs equals r5. N7 remains DEFERRED at fefd54e13; rows 243 and
+244 own the explicit chmod and PI_AUTH_FILE fixtures respectively.
+
+Read Sage's permitted failed pkg-bus log: process.test startup token refusal
+saw ready.ok true, consistent with inherited 077 narrowing its fixture mode.
+No further diagnostic read of the retained ga-8I3iZc root is needed.
+No r6 tests or probes have run. Source commit, push and new manifest await
+the explicit granted checks. r6-OVERLAP.json records the empty overlap.
+
+
+Sage-1892 focused grant: gate-lane.test whole 13/0, process.test whole
+through executeSteps 8/0, zero skips/cancellations. Syntax checks passed.
+All new umask/mode assertions passed. No Docker, image, lane or proof run.
+Empty /proc cwd/argv scan and removal recorded in r6-granted/cleanup.json;
+clear herb-0068 at 09:21Z. The source matches r5 on 29 of its 32 paths,
+including modes. Only BUILD.md, gate-lane.test.mjs and gate-lane.mjs differ.
+The new r6-OVERLAP.json records the base comparison. No process test edit.
+Sage-1895 authorizes one source commit and seat-only push after range check.
+
+
+## Round 7 preparation (sage-1951, sage-1955)
+
+The r6 proof passed all package suites with the original process.test,
+then failed script-release. The guard injected --no-build into compose run;
+Compose 5.5.1 rejects it before container creation. The old unit test only
+asserted the same invalid argv, so it could not detect this compatibility
+error. This supersedes no-build-flag claims in the historical packet.
+
+herb/row197-r7 starts at b1fece6f0. No r6 manifest path changed between
+fefd54e13 and this base; all 33 r6 blobs/modes were copied intact before
+r7 tests were authored. No history replay, stash, force push or deletion.
+Sage-1955 accepts the private tempRoot/compose-no-build.yaml override,
+mode0600, with build: !reset null and image pinned to the receipt's imageId.
+The guard owns the -f arguments and forces run --pull never --no-deps.
+Caller-supplied Compose config/build/pull options remain refused.
+The existing proof removes successful temp roots and retains failed roots;
+the override stays within that same cleanup ownership.
+
+Tests first: installed-binary run --help before SERVICE checks parser
+acceptance without starting a container. A separate compose config --format
+json check uses the actual candidate compose.yaml, made-up env/auth paths,
+and an empty Docker config directory, asserting no build key and the exact
+pinned image. The no-build-restoration mutant must fail that parser test.
+No test, probe or Docker command has run on r7; waiting for Sage's grant.
+
+Primary references: Docker's merge reference documents !reset null:
+https://docs.docker.com/reference/compose-file/merge/#reset-value
+Docker's run reference documents --pull and --no-deps, with no --no-build:
+https://docs.docker.com/reference/cli/docker/compose/run/
+Installed 5.5.1 acceptance and merged configuration are still unverified.
+
+
+Sage-1956 focused grant, 2026-10-21 11:19-11:21Z: busy check CLEAR.
+Whole gate-lane-image.test on the r6 guard: 9 pass, 2 fail. The installed
+Compose parser emitted unknown flag: --no-build; the other expected failure
+was the missing override helper. No cancellation or skip. After the fix,
+whole file 11/0. The committed r7-no-build.mutant.patch restores the invalid
+flag. Applied only for the installed parser regression: 0/1 with the same
+unknown-flag error, killed. Restored source and whole file passed 11/0 again.
+Both approved node --check commands passed. Empty /proc cwd/argv scan;
+clear herb-0073 at 11:21:04Z. No container start, image build, lane, proof or
+full suite ran. Logs/counts/scan are in r7-granted/ (local run evidence).
+
+The guard supplies both absolute -f paths, suppressing automatic override
+selection, pins receipt imageId, removes build via !reset null and adds
+--pull never --no-deps. Its main entry publishes the override before Docker
+runs. A unique private staging file plus hard-link publication prevents
+partial writes or replacement under concurrent guard calls; existing bytes,
+mode0600, file type and ownership must match, with O_NOFOLLOW on reads.
+The file stays under the run's short private tempRoot for existing proof
+cleanup. Caller Compose options remain allowlisted and config/build/pull
+options refuse. The actual installed Compose config test reports no build
+key and the exact image ID; parser help is before SERVICE, so no container
+operation can run. Fixtures supply made-up env/auth paths and empty Docker
+configuration. Existing image provenance, cleanup and umask behavior remain.
+
+Range check: one source commit on b1fece6f0, same 33 r6 paths plus the
+mutant patch and r7 overlap receipt (35 paths). Thirty r6 paths retain the
+same blob/mode. Only lane-docker.mjs, gate-lane-image.test.mjs and BUILD.md
+differ from r6. process.test and BUILD-LOG equal the landing. No force push,
+branch deletion, history replay or other source edits. Sage-1956 authorizes
+the source commit and seat-only push; fresh proof remains Sage's action.
+
+
+## Round 8 preparation (sage-1979)
+
+The r7 D5 proof passed business and bus, then failed the two installed
+Compose probes in pkg-cli. Their subprocess fixture retained the lane's
+shim-leading PATH but omitted MOSAIC_GATE_DOCKER_RECORD, so the shim read
+an undefined path. This is a test context error; the production guard stays
+byte-identical to r7.
+
+New herb/row197-r8 starts at 5c6f73ed7. None of r7's 35 manifest paths
+changed from b1fece6f0 to this base. Tests choose the record's real absolute
+Docker path when a lane record is set; outside lanes they keep using docker.
+Only the two read-only help/config probes use this helper. The subprocess
+env still holds fixture-only configuration; the record need not propagate
+to it. No run or policy allowlist is widened.
+
+Sage-1979 grants 215's 16 singles first, then r8's normal and lane-shaped
+shim-leading PATH whole-file checks and the record-lookup-removal mutant.
+The shim fixture invokes the actual unchanged guard, with a private made-up
+record naming the real Docker binary. No image build, container start, lane
+or proof is part of r8 checks. No r8 checks have started yet.
+
+
+Sage-1979 r8 checks followed 215's early singles, then clear herb-0078 at
+2026-10-21 12:09:28Z. Whole gate-lane-image.test normal PATH11/0; whole
+actual guard-shim-leading PATH plus private record11/0. The committed
+r8-record-lookup.mutant.patch removes the lookup: installed-Compose argv
+regression0/1, killed with the original Received undefined path error.
+Restored code, repeated whole shim-PATH file11/0. All zero skips/cancellations.
+Logs/counts/fixture metadata/empty /proc cwd+argv scan are in r8-granted/.
+Both 215 and r8 private roots were removed after an empty process scan.
+No image build, container start, suite, lane or proof ran for r8.
+
+Range: one commit on5c6f73ed7. Of r7's35 paths,33 keep the same blob/mode;
+only gate-lane-image.test and this BUILD.md change. The r8 mutant and overlap
+receipt are added. The production guard and all other tooling match r7.
+BUILD-LOG and process.test equal the landing. No history replay, force push,
+branch deletion, live state change or policy widening. Fresh proof remains
+Sage's action after Webby's merge review.

agents/herb/work/queue-197/r2-MERGE.json

@@ -0,0 +1,207 @@
+{
+  "r1Base": "aa1bd209e",
+  "r1Candidate": "6318f0d0bba9ee90ccaa3503cac8c2e04c6397f2ef6c3564f687fbc2092989e3",
+  "r2Base": "57f59e0c399ce29b1bb85ca6af686fdc10eb195d",
+  "rows": [
+    {
+      "path": "packages/cli/tests/fixtures/gate-lane-child.mjs",
+      "r1Sha256": "209682b968e929da4b46dc97c64fcd7aa68c490f3c6be44595f5d85f8d2e1483",
+      "r2Sha256": "209682b968e929da4b46dc97c64fcd7aa68c490f3c6be44595f5d85f8d2e1483",
+      "mode": "0o644",
+      "landedPathChanged": false,
+      "r1BlobEqual": true
+    },
+    {
+      "path": "packages/cli/tests/gate-lane-fixtures.test.mjs",
+      "r1Sha256": "29afa181804a724c695678eb9459c156e00f1084647c704e814c5bee156c0c25",
+      "r2Sha256": "29afa181804a724c695678eb9459c156e00f1084647c704e814c5bee156c0c25",
+      "mode": "0o644",
+      "landedPathChanged": false,
+      "r1BlobEqual": true
+    },
+    {
+      "path": "packages/cli/tests/gate-lane-image.test.mjs",
+      "r1Sha256": "0253621a49c2e77ffcdbf32beee7e1f773ec2c52c8487dcc5aa254e61807af7c",
+      "r2Sha256": "0253621a49c2e77ffcdbf32beee7e1f773ec2c52c8487dcc5aa254e61807af7c",
+      "mode": "0o644",
+      "landedPathChanged": false,
+      "r1BlobEqual": true
+    },
+    {
+      "path": "packages/cli/tests/gate-lane-state.test.mjs",
+      "r1Sha256": "948d62c76447d8269f03518562a261564c202ec9207461fb21d2b1c11c9bb9fc",
+      "r2Sha256": "948d62c76447d8269f03518562a261564c202ec9207461fb21d2b1c11c9bb9fc",
+      "mode": "0o644",
+      "landedPathChanged": false,
+      "r1BlobEqual": true
+    },
+    {
+      "path": "packages/cli/tests/gate-lane.test.mjs",
+      "r1Sha256": "240bf0c15025ad6f88b251917a3c8d72bd21c2e5df6771e1ceb83a1d90b24a51",
+      "r2Sha256": "240bf0c15025ad6f88b251917a3c8d72bd21c2e5df6771e1ceb83a1d90b24a51",
+      "mode": "0o644",
+      "landedPathChanged": false,
+      "r1BlobEqual": true
+    },
+    {
+      "path": "packages/cli/tests/stack-release.test.mjs",
+      "r1Sha256": "8ca733a600d5f5534d7e14d8533e1b16d710ebd43080ef8421238b5dd145fade",
+      "r2Sha256": "b95c0c125b6a283961e24adc07d43150bcbd05d2f11005180b836043015c52a6",
+      "mode": "0o644",
+      "landedPathChanged": true,
+      "r1BlobEqual": false
+    },
+    {
+      "path": "packages/control-board/tests/serve.test.mjs",
+      "r1Sha256": "4838cb4609da28fc921370c5542a82402fbc9ceb469692a36f0eafc713bb56c8",
+      "r2Sha256": "4838cb4609da28fc921370c5542a82402fbc9ceb469692a36f0eafc713bb56c8",
+      "mode": "0o644",
+      "landedPathChanged": false,
+      "r1BlobEqual": true
+    },
+    {
+      "path": "packages/harness/tests/claude-session.test.mjs",
+      "r1Sha256": "0a09b0255e9144a039428eb8e9f56181f94ccb2d187e474ea13392b485fdd008",
+      "r2Sha256": "0a09b0255e9144a039428eb8e9f56181f94ccb2d187e474ea13392b485fdd008",
+      "mode": "0o644",
+      "landedPathChanged": false,
+      "r1BlobEqual": true
+    },
+    {
+      "path": "packages/harness/tests/pi-session.test.mjs",
+      "r1Sha256": "6db5c3b7063baf933061e91e8bdf66740717dbb3066be3b70ac779fb17022094",
+      "r2Sha256": "6db5c3b7063baf933061e91e8bdf66740717dbb3066be3b70ac779fb17022094",
+      "mode": "0o644",
+      "landedPathChanged": false,
+      "r1BlobEqual": true
+    },
+    {
+      "path": "packages/webui/tests/preview.test.mjs",
+      "r1Sha256": "ada49ec100d75b3e739263593164b2798c378f3df0f38d73d80cf011ef16e234",
+      "r2Sha256": "ada49ec100d75b3e739263593164b2798c378f3df0f38d73d80cf011ef16e234",
+      "mode": "0o644",
+      "landedPathChanged": false,
+      "r1BlobEqual": true
+    },
+    {
+      "path": "packages/webui/tests/proof-cli.test.mjs",
+      "r1Sha256": "d3cec62f6eb8e2c1e0747f2a1bf1fc3f1a2122e45870d5a416d1830d3b6182cb",
+      "r2Sha256": "d3cec62f6eb8e2c1e0747f2a1bf1fc3f1a2122e45870d5a416d1830d3b6182cb",
+      "mode": "0o644",
+      "landedPathChanged": false,
+      "r1BlobEqual": true
+    },
+    {
+      "path": "packages/webui/tests/serve.test.mjs",
+      "r1Sha256": "36ecdfcb3d0d9a2411eec751421f770b5bb41ec2fbf9236c5794fb241fd3196b",
+      "r2Sha256": "36ecdfcb3d0d9a2411eec751421f770b5bb41ec2fbf9236c5794fb241fd3196b",
+      "mode": "0o644",
+      "landedPathChanged": false,
+      "r1BlobEqual": true
+    },
+    {
+      "path": "packages/webui/tests/service.test.mjs",
+      "r1Sha256": "c915239f0c223209baf84c96ec9f5ae2845fce7dd98ad46b073a96033aa7d6df",
+      "r2Sha256": "845313239547ddbc478090b29f96385f0b8853e5087c572393be328e7075f578",
+      "mode": "0o644",
+      "landedPathChanged": true,
+      "r1BlobEqual": false
+    },
+    {
+      "path": "packages/webui/tests/tester-cli.test.mjs",
+      "r1Sha256": "8bf4491f7982399b4162cfbe36d0b68888e99ceb2cbaefefc2361732dd95e0c8",
+      "r2Sha256": "8bf4491f7982399b4162cfbe36d0b68888e99ceb2cbaefefc2361732dd95e0c8",
+      "mode": "0o644",
+      "landedPathChanged": false,
+      "r1BlobEqual": true
+    },
+    {
+      "path": "scripts/test-discord.sh",
+      "r1Sha256": "c10af53b0717344026cb22462964f253c7401c5082ac6ef3722a89d9dfa5c661",
+      "r2Sha256": "a5dcf783c51a5d5d184a357f91ebf9fa1c4e054f0cb84a3d1d7668f6156e025e",
+      "mode": "0o755",
+      "landedPathChanged": true,
+      "r1BlobEqual": false
+    },
+    {
+      "path": "scripts/test-foundation.sh",
+      "r1Sha256": "2e11038e7f784ec4f539eb768f63bab0fab9c9940334388a1fe2d47ab9e2b008",
+      "r2Sha256": "2e11038e7f784ec4f539eb768f63bab0fab9c9940334388a1fe2d47ab9e2b008",
+      "mode": "0o755",
+      "landedPathChanged": false,
+      "r1BlobEqual": true
+    },
+    {
+      "path": "scripts/test-queue.sh",
+      "r1Sha256": "c270f181d1fa8b6d42ff4131c339beba786a8fd620bb66f8afdcec05e8b10868",
+      "r2Sha256": "c270f181d1fa8b6d42ff4131c339beba786a8fd620bb66f8afdcec05e8b10868",
+      "mode": "0o755",
+      "landedPathChanged": false,
+      "r1BlobEqual": true
+    },
+    {
+      "path": "scripts/testing/README.md",
+      "r1Sha256": "845db994e648f29f10efb5e6a4ddcf4be4e28798fc27f1eddf9d150f0e8b5319",
+      "r2Sha256": "845db994e648f29f10efb5e6a4ddcf4be4e28798fc27f1eddf9d150f0e8b5319",
+      "mode": "0o644",
+      "landedPathChanged": false,
+      "r1BlobEqual": true
+    },
+    {
+      "path": "scripts/testing/gate-lane.mjs",
+      "r1Sha256": "2e5decf42a546b1441c199337c9a3162693051f2299878f617dd039d6231f226",
+      "r2Sha256": "2e5decf42a546b1441c199337c9a3162693051f2299878f617dd039d6231f226",
+      "mode": "0o644",
+      "landedPathChanged": false,
+      "r1BlobEqual": true
+    },
+    {
+      "path": "scripts/testing/gate-lane.sh",
+      "r1Sha256": "41804d964c55dd07b6224855aae9dc44037f4e80c515c10f98fe04d6d3fa0084",
+      "r2Sha256": "41804d964c55dd07b6224855aae9dc44037f4e80c515c10f98fe04d6d3fa0084",
+      "mode": "0o755",
+      "landedPathChanged": false,
+      "r1BlobEqual": true
+    },
+    {
+      "path": "scripts/testing/lane-docker.mjs",
+      "r1Sha256": "fbe54165439923a852f64d69a6188ef29d237755289e9e21ddbfdab00e9ef933",
+      "r2Sha256": "fbe54165439923a852f64d69a6188ef29d237755289e9e21ddbfdab00e9ef933",
+      "mode": "0o644",
+      "landedPathChanged": false,
+      "r1BlobEqual": true
+    },
+    {
+      "path": "scripts/testing/lane-evidence.mjs",
+      "r1Sha256": "51d4dcff4ab01730b923e0a59c218f9a3d33e6ba729be1def03703bc457fb37e",
+      "r2Sha256": "51d4dcff4ab01730b923e0a59c218f9a3d33e6ba729be1def03703bc457fb37e",
+      "mode": "0o644",
+      "landedPathChanged": false,
+      "r1BlobEqual": true
+    },
+    {
+      "path": "scripts/testing/lane-fixtures.mjs",
+      "r1Sha256": "8634070d68bca694c8a58911eda9576991ed0eca1eb055a2c1bbf10261305939",
+      "r2Sha256": "8634070d68bca694c8a58911eda9576991ed0eca1eb055a2c1bbf10261305939",
+      "mode": "0o644",
+      "landedPathChanged": false,
+      "r1BlobEqual": true
+    },
+    {
+      "path": "scripts/testing/lane-image.mjs",
+      "r1Sha256": "2259045913b4e3042b7afd3ff6a0fb9c2cc9b4cf359f943e4dce9b8658b91982",
+      "r2Sha256": "2259045913b4e3042b7afd3ff6a0fb9c2cc9b4cf359f943e4dce9b8658b91982",
+      "mode": "0o644",
+      "landedPathChanged": false,
+      "r1BlobEqual": true
+    },
+    {
+      "path": "scripts/testing/lane-state.mjs",
+      "r1Sha256": "c37b3d5ec3025948dd8150d18d4ccc4eeb3539739ca37e4d86edede5bcafd1a8",
+      "r2Sha256": "c37b3d5ec3025948dd8150d18d4ccc4eeb3539739ca37e4d86edede5bcafd1a8",
+      "mode": "0o644",
+      "landedPathChanged": false,
+      "r1BlobEqual": true
+    }
+  ]
+}

agents/herb/work/queue-197/r2-TEST-FILES.txt

@@ -0,0 +1,19 @@
+packages/cli/tests/gate-lane-fixtures.test.mjs
+packages/cli/tests/gate-lane-image.test.mjs
+packages/cli/tests/gate-lane-state.test.mjs
+packages/cli/tests/gate-lane.test.mjs
+packages/cli/tests/stack-instances.test.mjs
+packages/cli/tests/stack-release-external.test.mjs
+packages/cli/tests/stack-release.test.mjs
+packages/cli/tests/stack-upgrade.test.mjs
+packages/control-board/tests/serve.test.mjs
+packages/harness/tests/claude-session.test.mjs
+packages/harness/tests/pi-session.test.mjs
+packages/webui/tests/preview.test.mjs
+packages/webui/tests/proof-cli.test.mjs
+packages/webui/tests/serve.test.mjs
+packages/webui/tests/service.test.mjs
+packages/webui/tests/tester-cli.test.mjs
+scripts/test-discord.sh
+scripts/test-foundation.sh
+scripts/test-queue.sh

agents/herb/work/queue-197/r2-merge-only.patch

@@ -0,0 +1,45 @@
+diff --git a/packages/cli/tests/stack-release.test.mjs b/packages/cli/tests/stack-release.test.mjs
+index 8788158c3..a78f52062 100644
+--- a/packages/cli/tests/stack-release.test.mjs
++++ b/packages/cli/tests/stack-release.test.mjs
+@@ -0,0 +1,2 @@
++import { leasePort } from '../../../scripts/testing/lane-fixtures.mjs';
++import { after as laneAfter } from 'node:test';
+@@ -1777 +1779 @@ const TESTER='7499';
+-const freePort=async()=>{const s=createServer();s.listen(0,'127.0.0.1');await once(s,'listening');const p=String(s.address().port);await new Promise((r)=>s.close(r));return p};
++const freePort=async()=>String(await leasePort({after:laneAfter},{closed:true}));
+diff --git a/packages/webui/tests/service.test.mjs b/packages/webui/tests/service.test.mjs
+index a6e66608a..adb460d07 100644
+--- a/packages/webui/tests/service.test.mjs
++++ b/packages/webui/tests/service.test.mjs
+@@ -0,0 +1,2 @@
++import { leasePort } from '../../../scripts/testing/lane-fixtures.mjs';
++import { after as laneAfter } from 'node:test';
+@@ -48,9 +50 @@ function filled(flags, root = REPO) {
+-async function closedPort() {
+-  const server = createServer();
+-  server.listen(0, '127.0.0.1');
+-  await once(server, 'listening');
+-  const { port } = server.address();
+-  server.close();
+-  await once(server, 'close');
+-  return port;
+-}
++async function closedPort() { return leasePort({after:laneAfter}, {closed:true}); }
+diff --git a/scripts/test-discord.sh b/scripts/test-discord.sh
+index 114994936..4daf0d143 100755
+--- a/scripts/test-discord.sh
++++ b/scripts/test-discord.sh
+@@ -73,0 +74,2 @@ TOOLS_JSON="{\"roots\":[{\"name\":\"docs\",\"path\":\"$SANDBOX/toolroot\"}],\"ma
++export PI_CODING_AGENT_DIR="$SANDBOX/pi-agent"
++mkdir -p "$PI_CODING_AGENT_DIR"
+@@ -145 +147,8 @@ fi
+-node_tests() { env -u NODE_TEST_CONTEXT node --test "$@"; }
++node_tests() {
++    local lane_concurrency=()
++    if [ -n "${MOSAIC_TEST_CONCURRENCY:-}" ]; then
++        [ "$MOSAIC_TEST_CONCURRENCY" = 2 ] || return 2
++        lane_concurrency=(--test-concurrency=2)
++    fi
++    env -u NODE_TEST_CONTEXT node --test "${lane_concurrency[@]}" "$@"
++}

agents/herb/work/queue-197/r2-on234-MERGE.json

@@ -0,0 +1,235 @@
+{
+  "base": "c771a36f4bd0b6c359282425c668996a90072f93",
+  "priorCandidate": "a3b7cbde8ef51c206a83769a7c272e4f9a1de5bc",
+  "originalCandidate": "6318f0d0bba9ee90ccaa3503cac8c2e04c6397f2ef6c3564f687fbc2092989e3",
+  "overlap": [
+    "packages/cli/tests/stack-release.test.mjs"
+  ],
+  "rows": [
+    {
+      "path": "packages/cli/tests/fixtures/gate-lane-child.mjs",
+      "r1Sha256": "209682b968e929da4b46dc97c64fcd7aa68c490f3c6be44595f5d85f8d2e1483",
+      "priorCandidateSha256": "209682b968e929da4b46dc97c64fcd7aa68c490f3c6be44595f5d85f8d2e1483",
+      "newSha256": "209682b968e929da4b46dc97c64fcd7aa68c490f3c6be44595f5d85f8d2e1483",
+      "unchangedFromPrior": true,
+      "overlaps234": false,
+      "mode": "0o644"
+    },
+    {
+      "path": "packages/cli/tests/gate-lane-fixtures.test.mjs",
+      "r1Sha256": "29afa181804a724c695678eb9459c156e00f1084647c704e814c5bee156c0c25",
+      "priorCandidateSha256": "29afa181804a724c695678eb9459c156e00f1084647c704e814c5bee156c0c25",
+      "newSha256": "29afa181804a724c695678eb9459c156e00f1084647c704e814c5bee156c0c25",
+      "unchangedFromPrior": true,
+      "overlaps234": false,
+      "mode": "0o644"
+    },
+    {
+      "path": "packages/cli/tests/gate-lane-image.test.mjs",
+      "r1Sha256": "0253621a49c2e77ffcdbf32beee7e1f773ec2c52c8487dcc5aa254e61807af7c",
+      "priorCandidateSha256": "0253621a49c2e77ffcdbf32beee7e1f773ec2c52c8487dcc5aa254e61807af7c",
+      "newSha256": "0253621a49c2e77ffcdbf32beee7e1f773ec2c52c8487dcc5aa254e61807af7c",
+      "unchangedFromPrior": true,
+      "overlaps234": false,
+      "mode": "0o644"
+    },
+    {
+      "path": "packages/cli/tests/gate-lane-state.test.mjs",
+      "r1Sha256": "948d62c76447d8269f03518562a261564c202ec9207461fb21d2b1c11c9bb9fc",
+      "priorCandidateSha256": "948d62c76447d8269f03518562a261564c202ec9207461fb21d2b1c11c9bb9fc",
+      "newSha256": "948d62c76447d8269f03518562a261564c202ec9207461fb21d2b1c11c9bb9fc",
+      "unchangedFromPrior": true,
+      "overlaps234": false,
+      "mode": "0o644"
+    },
+    {
+      "path": "packages/cli/tests/gate-lane.test.mjs",
+      "r1Sha256": "240bf0c15025ad6f88b251917a3c8d72bd21c2e5df6771e1ceb83a1d90b24a51",
+      "priorCandidateSha256": "240bf0c15025ad6f88b251917a3c8d72bd21c2e5df6771e1ceb83a1d90b24a51",
+      "newSha256": "240bf0c15025ad6f88b251917a3c8d72bd21c2e5df6771e1ceb83a1d90b24a51",
+      "unchangedFromPrior": true,
+      "overlaps234": false,
+      "mode": "0o644"
+    },
+    {
+      "path": "packages/cli/tests/stack-release.test.mjs",
+      "r1Sha256": "8ca733a600d5f5534d7e14d8533e1b16d710ebd43080ef8421238b5dd145fade",
+      "priorCandidateSha256": "b95c0c125b6a283961e24adc07d43150bcbd05d2f11005180b836043015c52a6",
+      "newSha256": "071ea2803b8c7e0450bb4c86ac9b49ae7c180af1599dca52bfce6d0274ca205b",
+      "unchangedFromPrior": false,
+      "overlaps234": true,
+      "mode": "0o644"
+    },
+    {
+      "path": "packages/control-board/tests/serve.test.mjs",
+      "r1Sha256": "4838cb4609da28fc921370c5542a82402fbc9ceb469692a36f0eafc713bb56c8",
+      "priorCandidateSha256": "4838cb4609da28fc921370c5542a82402fbc9ceb469692a36f0eafc713bb56c8",
+      "newSha256": "4838cb4609da28fc921370c5542a82402fbc9ceb469692a36f0eafc713bb56c8",
+      "unchangedFromPrior": true,
+      "overlaps234": false,
+      "mode": "0o644"
+    },
+    {
+      "path": "packages/harness/tests/claude-session.test.mjs",
+      "r1Sha256": "0a09b0255e9144a039428eb8e9f56181f94ccb2d187e474ea13392b485fdd008",
+      "priorCandidateSha256": "0a09b0255e9144a039428eb8e9f56181f94ccb2d187e474ea13392b485fdd008",
+      "newSha256": "0a09b0255e9144a039428eb8e9f56181f94ccb2d187e474ea13392b485fdd008",
+      "unchangedFromPrior": true,
+      "overlaps234": false,
+      "mode": "0o644"
+    },
+    {
+      "path": "packages/harness/tests/pi-session.test.mjs",
+      "r1Sha256": "6db5c3b7063baf933061e91e8bdf66740717dbb3066be3b70ac779fb17022094",
+      "priorCandidateSha256": "6db5c3b7063baf933061e91e8bdf66740717dbb3066be3b70ac779fb17022094",
+      "newSha256": "6db5c3b7063baf933061e91e8bdf66740717dbb3066be3b70ac779fb17022094",
+      "unchangedFromPrior": true,
+      "overlaps234": false,
+      "mode": "0o644"
+    },
+    {
+      "path": "packages/webui/tests/preview.test.mjs",
+      "r1Sha256": "ada49ec100d75b3e739263593164b2798c378f3df0f38d73d80cf011ef16e234",
+      "priorCandidateSha256": "ada49ec100d75b3e739263593164b2798c378f3df0f38d73d80cf011ef16e234",
+      "newSha256": "ada49ec100d75b3e739263593164b2798c378f3df0f38d73d80cf011ef16e234",
+      "unchangedFromPrior": true,
+      "overlaps234": false,
+      "mode": "0o644"
+    },
+    {
+      "path": "packages/webui/tests/proof-cli.test.mjs",
+      "r1Sha256": "d3cec62f6eb8e2c1e0747f2a1bf1fc3f1a2122e45870d5a416d1830d3b6182cb",
+      "priorCandidateSha256": "d3cec62f6eb8e2c1e0747f2a1bf1fc3f1a2122e45870d5a416d1830d3b6182cb",
+      "newSha256": "d3cec62f6eb8e2c1e0747f2a1bf1fc3f1a2122e45870d5a416d1830d3b6182cb",
+      "unchangedFromPrior": true,
+      "overlaps234": false,
+      "mode": "0o644"
+    },
+    {
+      "path": "packages/webui/tests/serve.test.mjs",
+      "r1Sha256": "36ecdfcb3d0d9a2411eec751421f770b5bb41ec2fbf9236c5794fb241fd3196b",
+      "priorCandidateSha256": "36ecdfcb3d0d9a2411eec751421f770b5bb41ec2fbf9236c5794fb241fd3196b",
+      "newSha256": "36ecdfcb3d0d9a2411eec751421f770b5bb41ec2fbf9236c5794fb241fd3196b",
+      "unchangedFromPrior": true,
+      "overlaps234": false,
+      "mode": "0o644"
+    },
+    {
+      "path": "packages/webui/tests/service.test.mjs",
+      "r1Sha256": "c915239f0c223209baf84c96ec9f5ae2845fce7dd98ad46b073a96033aa7d6df",
+      "priorCandidateSha256": "845313239547ddbc478090b29f96385f0b8853e5087c572393be328e7075f578",
+      "newSha256": "845313239547ddbc478090b29f96385f0b8853e5087c572393be328e7075f578",
+      "unchangedFromPrior": true,
+      "overlaps234": false,
+      "mode": "0o644"
+    },
+    {
+      "path": "packages/webui/tests/tester-cli.test.mjs",
+      "r1Sha256": "8bf4491f7982399b4162cfbe36d0b68888e99ceb2cbaefefc2361732dd95e0c8",
+      "priorCandidateSha256": "8bf4491f7982399b4162cfbe36d0b68888e99ceb2cbaefefc2361732dd95e0c8",
+      "newSha256": "8bf4491f7982399b4162cfbe36d0b68888e99ceb2cbaefefc2361732dd95e0c8",
+      "unchangedFromPrior": true,
+      "overlaps234": false,
+      "mode": "0o644"
+    },
+    {
+      "path": "scripts/test-discord.sh",
+      "r1Sha256": "c10af53b0717344026cb22462964f253c7401c5082ac6ef3722a89d9dfa5c661",
+      "priorCandidateSha256": "a5dcf783c51a5d5d184a357f91ebf9fa1c4e054f0cb84a3d1d7668f6156e025e",
+      "newSha256": "a5dcf783c51a5d5d184a357f91ebf9fa1c4e054f0cb84a3d1d7668f6156e025e",
+      "unchangedFromPrior": true,
+      "overlaps234": false,
+      "mode": "0o755"
+    },
+    {
+      "path": "scripts/test-foundation.sh",
+      "r1Sha256": "2e11038e7f784ec4f539eb768f63bab0fab9c9940334388a1fe2d47ab9e2b008",
+      "priorCandidateSha256": "2e11038e7f784ec4f539eb768f63bab0fab9c9940334388a1fe2d47ab9e2b008",
+      "newSha256": "2e11038e7f784ec4f539eb768f63bab0fab9c9940334388a1fe2d47ab9e2b008",
+      "unchangedFromPrior": true,
+      "overlaps234": false,
+      "mode": "0o755"
+    },
+    {
+      "path": "scripts/test-queue.sh",
+      "r1Sha256": "c270f181d1fa8b6d42ff4131c339beba786a8fd620bb66f8afdcec05e8b10868",
+      "priorCandidateSha256": "c270f181d1fa8b6d42ff4131c339beba786a8fd620bb66f8afdcec05e8b10868",
+      "newSha256": "c270f181d1fa8b6d42ff4131c339beba786a8fd620bb66f8afdcec05e8b10868",
+      "unchangedFromPrior": true,
+      "overlaps234": false,
+      "mode": "0o755"
+    },
+    {
+      "path": "scripts/testing/README.md",
+      "r1Sha256": "845db994e648f29f10efb5e6a4ddcf4be4e28798fc27f1eddf9d150f0e8b5319",
+      "priorCandidateSha256": "845db994e648f29f10efb5e6a4ddcf4be4e28798fc27f1eddf9d150f0e8b5319",
+      "newSha256": "845db994e648f29f10efb5e6a4ddcf4be4e28798fc27f1eddf9d150f0e8b5319",
+      "unchangedFromPrior": true,
+      "overlaps234": false,
+      "mode": "0o644"
+    },
+    {
+      "path": "scripts/testing/gate-lane.mjs",
+      "r1Sha256": "2e5decf42a546b1441c199337c9a3162693051f2299878f617dd039d6231f226",
+      "priorCandidateSha256": "2e5decf42a546b1441c199337c9a3162693051f2299878f617dd039d6231f226",
+      "newSha256": "2e5decf42a546b1441c199337c9a3162693051f2299878f617dd039d6231f226",
+      "unchangedFromPrior": true,
+      "overlaps234": false,
+      "mode": "0o644"
+    },
+    {
+      "path": "scripts/testing/gate-lane.sh",
+      "r1Sha256": "41804d964c55dd07b6224855aae9dc44037f4e80c515c10f98fe04d6d3fa0084",
+      "priorCandidateSha256": "41804d964c55dd07b6224855aae9dc44037f4e80c515c10f98fe04d6d3fa0084",
+      "newSha256": "41804d964c55dd07b6224855aae9dc44037f4e80c515c10f98fe04d6d3fa0084",
+      "unchangedFromPrior": true,
+      "overlaps234": false,
+      "mode": "0o755"
+    },
+    {
+      "path": "scripts/testing/lane-docker.mjs",
+      "r1Sha256": "fbe54165439923a852f64d69a6188ef29d237755289e9e21ddbfdab00e9ef933",
+      "priorCandidateSha256": "fbe54165439923a852f64d69a6188ef29d237755289e9e21ddbfdab00e9ef933",
+      "newSha256": "fbe54165439923a852f64d69a6188ef29d237755289e9e21ddbfdab00e9ef933",
+      "unchangedFromPrior": true,
+      "overlaps234": false,
+      "mode": "0o644"
+    },
+    {
+      "path": "scripts/testing/lane-evidence.mjs",
+      "r1Sha256": "51d4dcff4ab01730b923e0a59c218f9a3d33e6ba729be1def03703bc457fb37e",
+      "priorCandidateSha256": "51d4dcff4ab01730b923e0a59c218f9a3d33e6ba729be1def03703bc457fb37e",
+      "newSha256": "51d4dcff4ab01730b923e0a59c218f9a3d33e6ba729be1def03703bc457fb37e",
+      "unchangedFromPrior": true,
+      "overlaps234": false,
+      "mode": "0o644"
+    },
+    {
+      "path": "scripts/testing/lane-fixtures.mjs",
+      "r1Sha256": "8634070d68bca694c8a58911eda9576991ed0eca1eb055a2c1bbf10261305939",
+      "priorCandidateSha256": "8634070d68bca694c8a58911eda9576991ed0eca1eb055a2c1bbf10261305939",
+      "newSha256": "8634070d68bca694c8a58911eda9576991ed0eca1eb055a2c1bbf10261305939",
+      "unchangedFromPrior": true,
+      "overlaps234": false,
+      "mode": "0o644"
+    },
+    {
+      "path": "scripts/testing/lane-image.mjs",
+      "r1Sha256": "2259045913b4e3042b7afd3ff6a0fb9c2cc9b4cf359f943e4dce9b8658b91982",
+      "priorCandidateSha256": "2259045913b4e3042b7afd3ff6a0fb9c2cc9b4cf359f943e4dce9b8658b91982",
+      "newSha256": "2259045913b4e3042b7afd3ff6a0fb9c2cc9b4cf359f943e4dce9b8658b91982",
+      "unchangedFromPrior": true,
+      "overlaps234": false,
+      "mode": "0o644"
+    },
+    {
+      "path": "scripts/testing/lane-state.mjs",
+      "r1Sha256": "c37b3d5ec3025948dd8150d18d4ccc4eeb3539739ca37e4d86edede5bcafd1a8",
+      "priorCandidateSha256": "c37b3d5ec3025948dd8150d18d4ccc4eeb3539739ca37e4d86edede5bcafd1a8",
+      "newSha256": "c37b3d5ec3025948dd8150d18d4ccc4eeb3539739ca37e4d86edede5bcafd1a8",
+      "unchangedFromPrior": true,
+      "overlaps234": false,
+      "mode": "0o644"
+    }
+  ]
+}

agents/herb/work/queue-197/r2-on234-OVERLAP.txt

@@ -0,0 +1,47 @@
+Compared 57f59e0c3 to c771a36f4bd0b6c359282425c668996a90072f93
+agents/gizmoduck/work/queue-234/BUILD.md
+docs/SESSIONS.md
+packages/bus/README.md
+packages/bus/schema.sql
+packages/bus/src/broker.mjs
+packages/bus/src/credentials.mjs
+packages/bus/src/host-grant.mjs
+packages/bus/src/host-run.mjs
+packages/bus/src/migrations/3i-3j.sql
+packages/bus/src/runtime.mjs
+packages/bus/src/server.mjs
+packages/bus/src/store.mjs
+packages/bus/tests/account-migration.test.mjs
+packages/bus/tests/chief-of-staff.test.mjs
+packages/bus/tests/comment-migration.test.mjs
+packages/bus/tests/fixtures/schema-3i.sql
+packages/bus/tests/grant-enroll.test.mjs
+packages/bus/tests/grant-migration.test.mjs
+packages/bus/tests/hard-waits.test.mjs
+packages/bus/tests/host-fixtures.mjs
+packages/bus/tests/host-run.test.mjs
+packages/bus/tests/host-tools.test.mjs
+packages/bus/tests/name-migration.test.mjs
+packages/bus/tests/project-runtime.test.mjs
+packages/bus/tests/schema.test.mjs
+packages/bus/tests/spec-fixtures.mjs
+packages/bus/tests/spec-migration.test.mjs
+packages/bus/tests/thread-migration.test.mjs
+packages/bus/tests/usage-migration.test.mjs
+packages/business/src/business.mjs
+packages/business/src/hosts.mjs
+packages/business/tests/hosts.test.mjs
+packages/cli/README.md
+packages/cli/src/cli.mjs
+packages/cli/src/hosts.mjs
+packages/cli/tests/hosts.test.mjs
+packages/cli/tests/stack-release.test.mjs
+scripts/mosaic
+tools/host/mosaic-keys
+tools/host/mosaic-keys-write
+tools/host/mosaic-keys.sshd.conf
+tools/host/mosaic-keys.sudoers
+
+Overlap with row 197 source manifest:
+packages/cli/tests/stack-release.test.mjs
+Other 24 source paths: no overlap.

agents/herb/work/queue-197/r2-on234-merge-only.patch

@@ -0,0 +1,10 @@
+diff --git a/packages/cli/tests/stack-release.test.mjs b/packages/cli/tests/stack-release.test.mjs
+index daae6efb7..910785bc4 100644
+--- a/packages/cli/tests/stack-release.test.mjs
++++ b/packages/cli/tests/stack-release.test.mjs
+@@ -0,0 +1,2 @@
++import { leasePort } from '../../../scripts/testing/lane-fixtures.mjs';
++import { after as laneAfter } from 'node:test';
+@@ -1779 +1781 @@ const TESTER='7499';
+-const freePort=async()=>{const s=createServer();s.listen(0,'127.0.0.1');await once(s,'listening');const p=String(s.address().port);await new Promise((r)=>s.close(r));return p};
++const freePort=async()=>String(await leasePort({after:laneAfter},{closed:true}));

agents/herb/work/queue-197/r6-OVERLAP.json

@@ -0,0 +1,5 @@
+{
+  "base": "fefd54e13",
+  "prior": "9aa6d52d9",
+  "overlaps": []
+}

agents/herb/work/queue-197/r7-OVERLAP.json

@@ -0,0 +1,6 @@
+{
+  "base": "b1fece6f0",
+  "r6": "df0c59608",
+  "r6Base": "fefd54e13",
+  "overlaps": []
+}

agents/herb/work/queue-197/r7-no-build.mutant.patch

@@ -0,0 +1,11 @@
+--- a/scripts/testing/lane-docker.mjs
++++ b/scripts/testing/lane-docker.mjs
+@@ -34,7 +34,7 @@
+     const service=argv.indexOf('mosaic-agent',2);
+     if(service<0||argv.slice(2,service).some(a=>!['--rm','-T','--no-deps','--interactive','-i'].includes(a)))refuse('Docker Compose run options not allowed');
+     const [base,override]=composeFiles(run);
+-    return ['compose','-f',base,'-f',override,'run','--pull','never','--no-deps',...argv.slice(2)];
++    return ['compose','-f',base,'-f',override,'run','--no-build','--pull','never','--no-deps',...argv.slice(2)];
+   }
+   refuse('Docker mutation or unowned command');
+ }

agents/herb/work/queue-197/r8-OVERLAP.json

@@ -0,0 +1,6 @@
+{
+  "base": "5c6f73ed7",
+  "r7": "9c3166915",
+  "r7Base": "b1fece6f0",
+  "overlaps": []
+}

agents/herb/work/queue-197/r8-record-lookup.mutant.patch

@@ -0,0 +1,11 @@
+--- a/packages/cli/tests/gate-lane-image.test.mjs
++++ b/packages/cli/tests/gate-lane-image.test.mjs
+@@ -85,7 +85,7 @@
+ // including when the lane's guard is first on PATH. Child fixture env stays
+ // isolated; passing the real absolute path avoids re-entering that guard.
+ function installedDocker(){
+- const file=process.env.MOSAIC_GATE_DOCKER_RECORD;
++ const file=undefined; // mutant: lose the lane's real-binary lookup
+  if(!file)return 'docker';
+  const binary=JSON.parse(readFileSync(file,'utf8')).docker;
+  assert.ok(typeof binary==='string'&&isAbsolute(binary),'lane record must name the real absolute Docker binary');

agents/honker/README.md

@@ -3,5 +3,5 @@
 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 row 195 settles per-agent identity, it pushes only its own `honker/*` branches
+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

@@ -3,5 +3,5 @@
 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 row 195 settles per-agent identity, it pushes only its own `launchpad/*` branches
+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/megavolt/work/queue-199/BUILD.md

@@ -0,0 +1,216 @@
+# Row 199 (#1697): per-agent credential store, each agent's own git identity, publish to its fork
+
+Builder: Megavolt. Brief: `docs/plans/2026-10-20_agent-credentials.md`. Design: `DESIGN.md` r6 at
+4d3007ec9, approved by Duckworth in duckworth-0027 (REVIEW-r6.md at 640011518). Authority model ruled
+by Mos in mos-1027. Branch: megavolt/row199. Reviewer: Duckworth.
+
+Status: candidate on megavolt/row199-on-190, rebased on origin/refactor 00d4cc1f6 (sage-1555). The
+full gate and the section 11 mutants ran in Sage's slot; results under "Runs".
+
+## Commits so far
+
+- 286bf598c business: agent identity, the publish grant, the project upstream with the D9c parse, store
+  credential references; git.push.remote as a hard wait.
+- a2c387dba bus: broker publish authority (checkPublish, recordPublish, publishRefused, pushCommit on
+  the raise); the D9c parse moves to `business/src/vocabulary.mjs`; pm.md and chief-of-staff.md list
+  git.push.remote among the hard waits.
+- 609dc9364 bus: the per-agent credential store in `credentials.mjs`.
+- 504336797 bus: runtime wiring, the store root and the four publish entries in the op table.
+- a18fc6cf8 tasks: request calls use `useFor` keyed from the session; the start probe keeps `use`. The
+  D5 test in `credential-store.test.mjs` pins the `use(` call sites to `credentials.mjs` (useFor's own
+  call) and `tasks/src/adapter.mjs` (the host's @sync and start probe).
+- aa740cc71 bus: the lifecycle verbs `credentials.issue`, `credentials.revoke` and `credentials.delete`
+  in `credential-verbs.mjs`, the broker branch, the runtime wiring; `organizationWriter` gets a
+  `detail` on `write` and a receipt-only `record`.
+- 0cdace415 cli: `mosaic credentials status|issue|rotate|revoke|delete`, the scripts/mosaic route, docs.
+
+## Deviations from DESIGN.md r6
+
+1. **Identity is optional on an agent.** D8 reads as identity on every agent. Today's business files
+   carry none, so identity stays optional and `publish` requires it (N10's load refusal). An agent
+   without identity commits as E7 (T6).
+2. **Revoke of a `{file}` or `{env}` reference.** Section 6 describes revoke for store references.
+   For a reference outside the store, revoke forgets the token in memory and never unlinks the file;
+   the lifecycle verb then turns the business file's reference into `store`, so a restart finds
+   nothing. The test: `credential-store.test.mjs`, "revoke of a {file} reference".
+3. **Issue order.** Issue writes the token file (tmp, fsync, rename, dir fsync), then runs the
+   caller's commit (the business file's reference becomes `store`), then sets memory. A failed commit
+   leaves the file on disk and the token out of memory, so the agent stays `not-issued` until the
+   issue is run again. The test: "a failed commit leaves the token on disk but not in memory".
+4. **The D9c parse lives in `business/src/vocabulary.mjs`, not `business.mjs`.** The broker reads
+   `forkProblem` and `forkUrl`, and `project-runtime.test.mjs` pins the broker's import closure to
+   files that import nothing. `business.mjs` wraps `parseGiteaUrl` with the loader's refusal
+   messages. The pin test names the two new imports.
+5. **`withGitea` takes the publish ticket, not a cap (D9b).** The key is the session checkPublish
+   checked with `#agent` (a run holding its claim; never a tester, reader or human), read through
+   `broker.publishSession(ticket)`. The token is usable only between checkPublish and recordPublish
+   or publishRefused. Its refusals are filed once, by publishRefused on the task's trail, and not
+   also by `refusing()`. The test: `publish.test.mjs`, "runtime: withGitea keys from the open ticket
+   only".
+6. **Role contracts.** `workflow-roles.test.mjs` requires the hard waits listed in `roles/pm.md` and
+   `roles/chief-of-staff.md` to equal GATED_ONLY. Adding git.push.remote to the vocabulary made it
+   fail, so both lists now name git.push.remote. Prose only; no hash pin reads either file. Duckworth
+   should review this hunk because `roles/` is reviewed authority.
+
+7. **Delete takes a reason.** Section 6 lists `delete AGENT` with no reason. The broker requires
+   `reason` on delete as on revoke, so every receipt that ends a credential says why.
+8. **Rotate is `credentials.issue`.** There are three bus verbs, not four. An issue over an entry the
+   bus holds is recorded as `rotate` in the receipt and the answer. The CLI's `rotate` reads the
+   status first and refuses before reading stdin when nothing is issued.
+9. **Issue covers entries the bus loaded.** The business file must already name the kind for the
+   agent, and the bus must have loaded that reference at start; otherwise `credential-unknown`. An
+   agent added after the bus started needs the restart row 165 already asks for. Row 194's human
+   `create` is where a new agent's `store` references come from.
+10. **No Console page yet.** Section 6 puts the verbs in the Console's agent page too. This branch has
+    the bus verbs and the CLI. The Console page is a separate piece (packages/webui, its `BUS_VERBS`
+    and `STATUS` pins); I raise the split with Sage before the manifest. Ruled in sage-1421: the
+    Console page is out of row 199 and becomes a follow-up row with Webby as reviewer. The manifest
+    holds bus, business, tasks, cli and seat.
+11. **The push runs in the bus child, and the git socket polls for it (D9b).** The git socket runs in
+    the host process. The broker, the runtime and the token are in the bus child that
+    `packages/cli/src/host.mjs` forks, and host ops cross that IPC one at a time with a 10 s answer
+    limit. ls-remote and the push can run longer than that, so `withGitea(ticket, fn)` can't wrap a
+    host-side git. The split: the socket runs D9 steps 3 and 4 (tip and identity under the lock,
+    `working.publish`), then op `publishPush`, which starts `publishRemote` in the bus child under
+    `withGitea` and answers `{state: 'running'}`. The socket polls op `publishResult` every 200 ms
+    until it reads `pushed` or `refused`. Fork, user, source and destination come from the ticket
+    (`broker.publishTarget`), never from the host's message. `recordPublish` also refuses `ref-moved`
+    when the pushed ref isn't the ticket's destination. A second `publishPush` on a running ticket
+    refuses `publish-busy`. The token reaches git on fd 3 only (`runGit` option `pass`), read once
+    by a one-shot credential helper that answers `get` for https on the fork's exact host and port.
+    On close, a running publish's git isn't awaited; git's own time limit ends it, and the ticket
+    goes with the process. The 10 s IPC limit stays as it is (sage-1440). The poll has a bound
+    (sage-1440): `publishDeadlineMs`, by default four times git's limit and grace (publishRemote runs
+    at most four git commands) plus 30 s. Past it the socket refuses `publish-timeout`, filed once by
+    publishRefused, and logs that the bus process's push may still reach the fork. A failure that is not a refusal is filed as `git-failed` and logged on
+    the bus's stderr by error name and code only. Tests: `seat/tests/publish.test.mjs` (11),
+    `bus/tests/publish.test.mjs` (the process ops), `cli/tests/publish-socket.test.mjs` (7, end to
+    end through the socket, the in-process runtime, the store and a TLS fake Gitea; one is the
+    publish-timeout outcome).
+12. **No harness tool for publish.** `packages/harness/src/git-tools.mjs` has push, fetch and land
+    clients. A runner tool that calls the socket's `publish` op is in packages/harness, outside the
+    manifest scope sage-1421 set. Today a publish needs a socket client; the tool is a follow-up.
+13. **The bind rule's `git.push.remote` clause has no test of its own.** D11 adds it and the
+    launcher has it. A role can publish only a push its own role made (`work-not-yours`), and
+    `recordPush` needs `git.push.working`, which already binds the socket. No role reaches the
+    clause alone, so dropping it changes no outcome today. It matters once a role can publish work
+    it didn't push. Ruled in sage-1440: keep it; its mutant goes in the section 11 list as
+    equivalent, with this reasoning, and Duckworth judges it.
+14. **A push between checkPublish and the git push refuses; it never lands a different commit.**
+    T3 says such a push "doesn't change the commit that lands". Under the hard wait it refuses:
+    `working.publish` checks the work ref's tip against the ticket's source under the lock
+    (`ref-moved`, `seat/tests/publish.test.mjs`), and `recordPublish` checks `pushCommit` again
+    (`decision-mismatch`, `bus/tests/publish.test.mjs` "r4 B4"). The fork gets only the ticket's
+    oid either way. N9's routing-commit test still applies. Ruled in sage-1440: T3's wording in
+    DESIGN.md now reads "refuses with `ref-moved` or `decision-mismatch`", and an end-to-end test
+    asserts each code mid-flight in `cli/tests/publish-socket.test.mjs`: a push after checkPublish
+    refuses `ref-moved` with no request to the fork; a push recorded while the bus process pushes
+    refuses `decision-mismatch`, filed once, and the fork holds only the ticket's oid.
+
+15. **Fix: rotate on a due gitea key (gizmoduck-0050, sage-1494).** The CLI's `ISSUED` set
+    (`packages/cli/src/credentials.mjs`) listed valid, expiring and expired, but the bus's `status()`
+    gives a gitea key past its rotate-by date `rotation-due`. So `credentials rotate` refused the one
+    case it exists for. `ISSUED` now names every state status() gives a held token. The test:
+    `cli/tests/credentials.test.mjs`, "rotate goes ahead on each held state". Its mutant (the old set)
+    fails that test and goes in the section 11 list.
+
+16. **The bus process refuses a boot config carrying `publishTls` (M26, sage-1563).** process.mjs
+    used to drop `publishTls` from the boot config before `startBroker`, and no test could see the
+    drop. The host's boot config (`packages/cli/src/config.mjs`) never carries it; it is the tests'
+    scratch CA for an in-process runtime only. A boot that carries it now refuses
+    `invalid-host-request` and the process exits 2, rather than trusting it or dropping it quietly.
+    The test: `bus/tests/publish.test.mjs`, "the bus process answers the publish ops from their own
+    lines". Every test file that reads process.mjs ran singly, green (see "Runs").
+17. **M17 is equivalent: `#authorityFor`'s pushCommit comparison is also made by `#publishFacts`.**
+    A git.push.remote raise with no recorded push refuses `no-push` (`broker.mjs` raise,
+    `pushCommit = ... ?? fail('no-push')`), so every publish decision carries a pushCommit.
+    `#publishFacts` takes `source = result.pushCommit` and refuses `decision-mismatch` when it isn't
+    `#latestPush(task_ref).commit`, the same two values `#authorityFor` compares. The check stays as
+    defense in depth, for a decision whose context lacks pushCommit, which no code path writes today.
+    Duckworth judges it, as with M27.
+
+## N9, for the routing commit (sage-1388)
+
+Today git.push.remote is a hard wait, so every publish carries a decision, and the decision's
+`pushCommit` fixes the commit. If a later commit routes git.push.remote within role, a publish has
+no decision and no `pushCommit`. `#publishFacts` then takes the commit from `#latestPush`, and the
+git socket's tip check under the lock is the only thing that holds it. That commit needs a test
+that a push between checkPublish and the git push doesn't change what lands.
+
+## R1, the backup set
+
+Checked at 504336797. Row 185's `backup_store` (`scripts/stack-release.sh:372-392`) copies only
+`<dataRoot>/bus/bus.sqlite`, plus its sums, modes, listing and stamps, into
+`<dataRoot>/backups/stack/<activation>/`. Nothing under `<configDir>` is copied, so
+`<configDir>/secrets/agents` isn't in the backup set. `rehearse` copies the live business file
+through `R_BUSINESS_JS` (`:1268-1288`). Its `swap` replaces every credential reference, a `store`
+one included, with a placeholder file in the rehearsal's own dir. The guard then refuses
+`credential-ref-live` unless every reference is such a placeholder (`:1329-1337`), so a rehearsal
+never reads a store token. A backup tool outside this repository that copies `<configDir>` would
+copy tokens. That is R1's open half, and it is Jason's to check on each VM.
+
+## T1 limit
+
+A wrong owner on a store dir or file can't be set up without root, so T1 covers modes, symlinks and
+dirs. The owner check (`st.uid !== process.getuid()`) is in `privateDir` and `#read`, and is untested.
+
+## Runs
+
+Single files, each green on its commit: bus broker, decision-close, decision-route, decisions,
+hard-waits, land, project-runtime, launch-notice, review, publish, credential-store, credentials,
+credential-status, limits, tester, plugins-verb, routes-verb, limits-runtime, instances-verb, web,
+usage-runtime, limit-checks, daily-quota-runtime, chief-of-staff, tasks, tester-writes; every
+business test file. Since: credential-verbs (2/2), credential-store (11/11, with D5), each tasks file,
+tester, credential-status, plugins-verb, routes-verb, instances-verb; business launch-settings,
+plugin-settings, instance-settings, token-limit-settings; cli credentials (3/3), cli, app,
+tester-reads, tester, other-tree, transport, instances, limits, verbs. Hash pins: none on a changed
+file (`thread-migration.test.mjs:46` pins DDL only).
+
+Publish, single files, each green before its commit: seat
+checkout (77), working (26), publish (11), landing (8); bus process (8), land (17), publish (12),
+credential-verbs (2); cli publish-socket (4), git-socket (24), launcher (29); harness tools (22).
+Hash pins: none on a changed file.
+
+sage-1440 changes (the poll bound, the mid-flight tests), single files, green before the commit: cli
+publish-socket (7), git-socket (24), launcher (29). Hash pins: none on a changed file.
+
+The rotation-due fix, single files: cli credentials (4), green; the old-set mutant fails it 3/1.
+Hash pins: none on a changed file.
+
+Slip, 2026-10-20 about 19:51Z: I ran `node --test packages/tasks/tests/*.test.mjs` in one command,
+which is a package suite, without asking Sage for the slot. It passed, 97 pass and 0 fail, in under a
+minute. Reported to Sage in megavolt-0017.
+
+Rebase (sage-1555): the 21 commits from megavolt/row199 sit on origin/refactor 00d4cc1f6 as the new
+branch megavolt/row199-on-190 (no force-push). `git range-diff` shows all 21 patches as `=`; the
+merge of 12c85ada1 flattened with an empty remerge-diff.
+
+Full gate, Sage's slot, on c6868ba41 (base 00d4cc1f6), logs started 2026-10-20T22:55:44Z: bus 476
+pass 0 fail; business 191/0; tasks 97/0; cli 522/0 (472 s); seat 163/0; scripts/test-queue.sh
+156/0; test-auth, test-conductor, test-config, test-discord, test-extension-package,
+test-foundation, test-land-work, test-release and test-task each exit 0. The test-task compose run
+left the network megavolt-row199_default with 0 containers; I removed it.
+
+Section 11 mutants, batch 1, on c6868ba41, 2026-10-20T23:09:03Z to 23:09:56Z, restores verified and
+packages/ clean: 22 of 28 killed; M27 survived, expected equivalent (deviation 13). Five expected
+kills survived, each a test gap: M05 (the token in the push URL), M06 (revoke unlinks before it drops
+memory), M12 (http.followRedirects=false dropped), M17 (#authorityFor's pushCommit check dropped)
+and M26 (publishTls reaches startBroker). Launchpad's stack-release single file ran alongside from
+23:09:28Z, so batch 2 reruns all 28 (sage-1563).
+
+Fixes, each checked by its mutant alone: 5fa7b2553 seat publish, a test reads git's argv through a
+PATH shim and finds no token and no userinfo (M05 killed); the 302 test's target shares the CA git
+trusts, so only http.followRedirects=false keeps git off it (M12 killed). 116eeec48 bus,
+credential-store: revoke's unlink fails (dir 0500) and the token is already out of memory (M06
+killed); process.mjs refuses publishTls, deviation 16 (M26 killed, its anchor is now the refusal
+line). M17 is equivalent, deviation 17. Single files after the fixes, each green: seat publish (12),
+bus credential-store (12), bus publish (12), bus process (8), and every other file that reads
+process.mjs: bus credential-status (4), limit-checks (16), land (17), tasks (9), end-launch (7); cli
+trackers-boot (1), thread-launch (11), publish-socket (7). Hash pins: none on a changed file.
+
+Section 11 mutants, batch 2, all 28, on 7c3cdd940 in Sage's slot (sage-1565), 2026-10-20T23:17:59Z to
+23:18:48Z, restores verified and packages/ clean: 26 killed; M17 and M27 survived, both expected
+equivalent (deviations 17 and 13). Each of the five batch 1 survivors but M17 now fails its test. Then
+pkg-bus 477 pass 0 fail, pkg-seat 164/0, pkg-cli 522/0 (461 s), ending 23:26:40Z. No other seat's run
+was active: the busy check said CLEAR before the batch started. Logs:
+/mnt/storage/scratch/megavolt-r199/batch2-20261020T231650Z/.

agents/megavolt/work/queue-199/DESIGN.md

@@ -0,0 +1,416 @@
+# Row 199 design: a credential store per agent, own git identity, pushes to a remote
+
+Megavolt, 2026-10-20. Gitea #1697, MVP T1 item 6. Brief: `docs/plans/2026-10-20_agent-credentials.md`.
+Reviewer Duckworth. Mos rules on the authority model (section 9) before any code. Base: refactor at 992650232.
+No credential value was read to write this. Evidence is code and docs only.
+
+r2 answers duckworth-0013 (review at 6ab9cd927 on duckworth/reviews): B1 in D3a, T1 and T5, B2 in D9 step 5
+and T3, N1 in section 6 and Q-M3, N2 in section 6, N3 in D9 step 3, N4 in D9a and T3, N5 in E5 and D9b.
+
+r3 records Mos's rulings (mos-1027) in section 9. The Q-M2 hard wait changes D9 step 1, D9b and T3. Q-M1
+drops O2 (D10, A3, R2).
+
+r4 answers duckworth-0017 (REVIEW-r3.md at 4065ed59f): B3 in T3 and D9 step 5, B4 in D9 steps 1, 3 and 5, N6
+and N7 in D9a, N8 in D9 step 1.
+
+r5 takes webby-0011 N1 (row 194 review, through honker-0009): the host checks at each push that the
+remote's owner is the agent's own Gitea user. r4 named one `remote` per project, which can't be a fork per
+agent (O1) once two agents publish the same project. So `projects.<p>.remote` now names the upstream
+repository, and the host builds each agent's fork URL from it (D9 step 2, D10, T3). It also fixes a conflict
+found while building: D8 made `identity` required for every agent whose definition declares `gitea`, while D9
+step 2 says today's files load unchanged. Coder declares `gitea`, so r5 makes `identity` optional and
+`publish` require it (D8).
+
+r6 answers duckworth-0026 (REVIEW-r5.md at 3cb6888e1), with Mos's acceptance (mos-1043). B5: the derived URL
+has one name, `fork`, and D9a's `ls-remote`, step 5's push, the helper's host match, `checkPublish`'s result
+and step 6's event all use it (D9, D9a, D9b, T3). B6: the URL parse is written down (D9c) and tested (T3).
+N10 in D8 and T3. N11 in D9a and A3. N9 is carried to BUILD.md for the routing commit.
+
+## 0. Terms
+
+- **Stack instance**: one Mosaic Stack deployment (row 190). It has one OS user, one config dir
+  `~/.config/mosaic-NAME` (here `<configDir>`), one data root and one bus. Case 1 and Case 2 are two stack
+  instances on two VMs (DECISIONS Q180).
+- **Agent**: a role instance in a business file (`roles.<agent>`). Today's code calls it "instance". This
+  design says agent.
+- **Kind**: a credential type: `gitea`, `vikunja`, `model`.
+- **Host**: the bus process and its git socket, running as the stack instance's OS user, outside any sandbox.
+
+## 1. What exists (measured at 992650232)
+
+| Code | Fact | Where |
+|---|---|---|
+| E1 | The business file references credentials per agent: `roles.<agent>.credentials.<kind> = {file or env, rotateBy or expires}`. The kinds an agent may hold are the ones its role definition lists | `business/src/business.mjs:89-111`, `credentials.mjs:18-38`, `role.mjs:105-118` |
+| E2 | The bus reads each token once at start (O_NOFOLLOW, own uid, 0600, at most 16 KiB, outside the repos and data root) into a private map keyed `<business>/<agent>:<kind>` | `bus/src/credentials.mjs:18-89`, `bus/src/runtime.mjs:78-89` |
+| E3 | Only Vikunja uses a token: `credentials.use("<business>/<agent>", "vikunja", ...)`. Gitea tokens are loaded and never used. `assertClean` refuses any event that contains a token | `tasks/src/adapter.mjs:70`, `runtime.mjs:134`, `broker.mjs:560` |
+| E4 | Agents run in bwrap as the bus's own uid. `~/.config`, `~/.mosaic` and `~/.ssh` are not bound. The git socket is bound only for `git.push.working`, `review.verdict` or a landing | `seat/src/sandbox.mjs:21-30, 104-124`, `cli/src/launcher.mjs:401` |
+| E5 | A session proves who it is with a 64-hex cap the broker mints and maps to a frozen session record. The git socket resolves the cap to (business, role) before anything else | `broker.mjs:280, 379-383`, `packages/cli/src/git-socket.mjs:398-407` |
+| E6 | The model credential is one env file per host (`EnvironmentFile=-%h/.config/mosaic-dev/secrets/claude-session.env`). `ENV_ALLOW` passes it into every sandbox, so every agent holds the same model token | `cli/systemd/mosaic-bus.service.in:24`, `seat/src/session.mjs:83-94` |
+| E7 | Commits in a session's clone use `<agent>@<business>.mosaic.invalid`. Landed squashes use "Mosaic bus host" | `sandbox.mjs:151-157`, `working.mjs:280-281` |
+| E8 | No code pushes to a remote. The git socket pushes bundles into a local bare working repo with no remote and no credential | `working.mjs:1-14, 198-238` |
+| E9 | Adding or changing an agent refuses a definition that declares credentials (`organization-credentials-out-of-scope`). Binding them is a hand edit. Row 194's design keeps that refusal for create and hire "until the credentials row" | `business/src/instance-settings.mjs:20-29`, row 194 DESIGN.md D1 |
+| E10 | The development repository's helper pushes as one identity from one JSON file | `scripts/git-credential-mosaic.mjs` |
+
+So per-agent references and a host-only reader already exist for two kinds. What's missing: a fixed place for
+the files, an agent identity, any remote push, lifecycle verbs, and a model credential that agents don't
+share.
+
+## 2. The store (brief item 1)
+
+D1. **Layout.** Each stack instance keeps its agents' secrets under its own config dir:
+
+```
+<configDir>/secrets/agents/                       0700, owner = the stack instance's OS user
+<configDir>/secrets/agents/<business>/<agent>/    0700
+<configDir>/secrets/agents/<business>/<agent>/<kind>   0600, the token only, one line
+```
+
+This is row 190's secrets root (`<configDir>/secrets/...`, as Q175's slot uses). The token file keeps E2's
+format, so the bus reader doesn't change. Nothing in a token file is a name, an email or a URL. Those are not
+secret and go in the business file (D6), where review sees them.
+
+D2. **The business file reference.** A new reference form, `{"store": true, "rotateBy" | "expires": DATE}`,
+means "the file at the layout path for this business, agent and kind". The path is derived, never written,
+so an agent's entry can't name another agent's file. The old `{file}` and `{env}` forms stay valid for
+migration (section 7). A `{file}` reference that points inside `<configDir>/secrets/agents/` but not at its
+own agent's path refuses `credential-not-yours` when the business file loads.
+
+D3. **Read path.** Unchanged in shape: the bus reads every entry once at start (E2) and on a store change
+(section 6), and holds the values in memory. No sandbox binds `<configDir>` (E4 already holds). No token goes
+into a sandbox for `gitea` or `vikunja`. The agent asks the bus to act, and the bus uses the token.
+
+D3a. **A `store` reference with no file.** ENOENT on a `store` path loads as an absent entry. `status` shows
+`not-issued`, and `useFor` refuses `credential-unavailable`. The bus still starts. This is the state after a
+create without `issue` (D13) and after `revoke` (section 6). Every other defect still refuses start: wrong
+owner or mode on the file or a dir, a symlink, a non-regular file, bad format, a missing or wrong-mode
+`secrets/agents/` dir. `{file}` and `{env}` keep E2's behavior, where a missing file refuses start.
+
+## 3. The "RLS equivalent" (brief item 1)
+
+Three layers. Each one is enforced by code or the OS, not by prose.
+
+D4. **OS, between stack instances.** Files are 0600 and dirs 0700, owned by the stack instance's own OS user.
+Case 1's user can't read Case 2's store (Q180: each instance under its own user without sudo). The bus refuses
+to start when any file or dir under `secrets/agents/` has the wrong owner or mode (`credential-file`, as E2
+does for files today, extended to the dirs).
+
+D5. **Bus, between agents of one stack instance.** The principal for every credential use comes only from the
+verified cap (E5). The agent-facing API is `credentials.useFor(session, kind, op)`: `session` is the broker's
+frozen record, and the key is built from `session.business` and `session.role`. It has no agent argument, so
+there is nothing in a request to point at another agent. The existing `use(name, kind, op)` stays for the
+host's own `@sync` entry and is not reachable from a request. The tasks adapter's per-role calls (`ctx.as`,
+`verbs.mjs:126`) move to `useFor`. Any request field that names an agent other than the caller (`as`,
+`agent`, `instance`, `role` on a credential path) is refused `credential-not-yours` and recorded through
+`broker.refuse()` as `action.refused`, with the caller's cap and the task ref. A build test greps every
+`credentials.use(` call site and fails on a new one outside the allowlist.
+
+D6. **What stays open.** A process of the same OS user outside the sandbox can read every agent's file. That
+is the same limit as the human proof (P19 333). Q180's per-user VMs move the boundary to "one stack instance
+per OS user". Agents of one instance are kept apart by the sandbox and D5, not by the OS.
+
+## 4. Kinds (brief item 2)
+
+| Kind | 10-27 | Use |
+|---|---|---|
+| `gitea` | yes | Git push to a granted remote (section 5). Gitea API verbs (issues, pull requests) wait. The factory's review flow runs in the working repo today, and no 10-27 case needs an agent to open a pull request |
+| `vikunja` | yes, exists | Moves to `store` references and `useFor`. No behavior change |
+| `model` | per stack instance only | See D7 |
+
+D7. **Model provider.** A model token has to sit inside the sandbox today, because the harness calls the
+provider itself (E6). Per-agent model tokens need a proxy that holds the real token and gives each run its own
+short-lived one, which is the CLIProxyAPI line in TARGET.md. That waits for its own row. For 10-27 the model
+credential is per stack instance: row 190's `<configDir>/secrets/claude-session.env`, owned by that
+instance's OS user. It is never a copy of jwoltje's file. Jason signs in on each VM user himself (A6). Whether
+Case 1 and Case 2 run on Jason's existing subscription or need a new account is Jason's call (Q-J1). This row
+doesn't pick. A pi model credential also waits for P19 #383.
+
+## 5. Git identity and push (brief item 3)
+
+D8. **Identity.** A new business-file key, `roles.<agent>.identity = {name, email, gitea: {url, user}}`. It is
+optional, because today's business files with a `gitea` agent (coder) must load unchanged. `publish` (D9
+step 2) requires it, and requires that the definition declare `gitea`. A business file with a `publish`
+grant on an agent that lacks either refuses at load, and the error names `roles.<agent>.publish` and says
+"needs identity and a gitea definition" (N10). Load is the only place this is checked: a business file that
+fails it never reaches the bus. The sandbox sets `GIT_AUTHOR_*` and `GIT_COMMITTER_*` from
+it in place of E7's invalid domain. The email is the one Jason gives the agent's Gitea user, so Gitea links the
+commits to that user. Agents without `gitea` keep E7.
+
+D9. **Push to a remote: a new git socket op, `publish`.** No new socket, no bundle, and no token in the sandbox.
+
+```
+publish {"cap", "op": "publish", "task_ref", "project", "branch", "decision"}
+  -> {"ok": true, "result": {"fork", "ref", "commit", "previous"}} or a refusal
+```
+
+The host checks, in order, and each refusal goes through `broker.refuse()`:
+
+1. Identity from the cap (E5), then the broker's `#checkAuthority(s, "git.push.remote", {decision, target:
+   task_ref})`, as `checkLand` does for a merge (`broker.mjs:907-913`). `git.push.remote` is a new action in
+   ACTIONS and is not in ROUTED (REQ-WAIT-3, `packages/business/src/vocabulary.mjs:52-58`,
+   `broker.mjs:42-69`), so it is a hard wait and classifies `gated` for every role. Every publish therefore
+   needs a decision the human resolved for this task ref. A decision is spent once (`decision-consumed`).
+
+   **The decision binds one commit.** `#authorityFor` binds action, role, thread and target only
+   (`broker.mjs:769-798`), so the commit needs its own carrier. The raise records it the same way it records
+   `holderRun` for `role.revoke` (`broker.mjs:1733`). When the action is `git.push.remote`, the
+   `decision.raise` event body gets `pushCommit`. That is the commit of `#latestPush(business, target)` at
+   raise time, read by the broker and never taken from the agent. A raise with no recorded push for the task
+   refuses `no-push`. The decision's question shown to the human ends with that commit. `#authorityFor` then
+   refuses `decision-mismatch` when `context.pushCommit` differs from the commit of `#latestPush` now, which
+   is the same check `holderRun` gets at `broker.mjs:796`. So the sequence approve at A, push B, publish B
+   refuses.
+   No role definition grants the action yet. When Jason's PRD version routes it (Sage, Vikunja #420), a
+   reviewed commit adds it to both ROUTED lists and to coder's `withinRole`. From then on a coder publishes
+   without a decision, and `decision` is optional for a within-role class only.
+2. The project is in the agent's grant, `roles.<agent>.publish: [project]`, and the business file names the
+   project's upstream repository, `projects.<project>.remote: "https://HOST/OWNER/REPO"`
+   (`remote-not-granted`). Both URLs pass D9c's parse at load. The upstream's host and port equal
+   `identity.gitea.url`'s (`remote-host-mismatch`). The host never contacts that URL. It builds the agent's
+   fork, `fork = https://HOST[:PORT]/<gitea.user>/REPO`, from the upstream's origin and repository name and
+   the agent's own `gitea.user`. `fork` is the only URL the rest of `publish` uses: D9a's `ls-remote`, step
+   5's push, the helper's host match, `checkPublish`'s result and step 6's event. So the owner of the
+   repository that receives a push is the agent's own Gitea user on every push, by construction, and the
+   agent can't name it (webby-0011 N1). D9c is what makes "by construction" hold. Gitea's refusal of a
+   push to a repository the user doesn't own or collaborate on is the second layer. An upstream whose owner
+   equals the agent's `gitea.user`, compared without case, refuses `remote-not-fork`, at load and at push. `remote` is a new key
+   beside `root` and `repo` (`business.mjs:186`), and `identity` and `publish` are new keys on a role entry
+   (`business.mjs:89`). All three are optional, so today's business files load unchanged.
+3. The source is one commit, `C = context.pushCommit`. It is checked three ways, so all three are equal:
+   the decision's commit, the commit of `#latestPush`, and the work ref's tip in the working repo,
+   `work/vikunja-<project>-<task>` (`working.mjs:110-114`). The tip is read under the repository's lock, and
+   if they differ the push refuses `ref-moved`. The work ref is per task, not per agent. Two checks make it the
+   caller's: `#latestPush` was recorded by the caller's role (`work-not-yours`), and step 4. The destination is always `refs/heads/<gitea.user>/<branch>`, built by the host.
+   `validBranch(branch)` holds (`invalid-request`). The agent never names the destination ref.
+4. Every commit in `main..<work ref>` has author and committer email equal to `identity.email`
+   (`identity-mismatch`).
+5. The push runs through `credentials.useFor(session, "gitea", ...)`: `git push <fork> <C>:<dst>`, by oid,
+   with no `+` and no `--force`. It never pushes by ref name, so a push to the working repo after
+   `checkPublish` can't change what goes out (`non-fast-forward` from git stays a refusal). Git runs with E8's SAFE flags
+   (`working.mjs:92-98`), which set `protocol.allow=never`. `publish` adds exactly two flags,
+   `protocol.https.allow=always` and `http.followRedirects=false`, plus `GIT_TERMINAL_PROMPT=0` and no global
+   or system config. The token reaches git through a one-shot credential helper that reads it from an
+   inherited pipe, never through argv, env, the URL or a file. Seat `gitEnv` (`checkout.mjs:79-89`) takes only
+   PATH from the host and sets the rest itself, so no proxy or `GIT_SSL_*` variable reaches git. `publish` takes a `tls` parameter that
+   defaults to `[]`, the same way `push` takes `fsck = FSCK` (`working.mjs:100`). Tests pass
+   `["-c", "http.sslCAInfo=<scratch CA>"]`. The host never sets it, and nothing in config or env reaches it. The helper answers `get` only when `protocol`
+   is `https` and `host`, port included, equals `fork`'s. It writes nothing for any other `get` and for
+   `store` and `erase`. `assertClean` checks git's output, so a fork that echoes the token gets
+   `credential-leak`.
+6. The bus records `action.allowed` for `git.push.remote` with fork, ref and commit.
+
+D9a. **The agent's fork must share root's history.** A push sends every object the fork lacks. The working
+repo's `main` is the project root's history (`working.mjs`, seed), so a fork that doesn't share it would
+receive all of root, landing squashes included. The check runs on `fork`, never on the upstream: a related
+upstream says nothing about what the agent's `<user>/REPO` holds.
+`publish` runs `seed` first (`working.mjs:164-176`), under the repository's lock as `push` does, so `main`
+catches up with root before the check below. That means a fork also receives any landed root commits that
+upstream doesn't have yet, because they sit under the agent's work. That is expected: the agent's branch is
+built on them.
+Before the push, the host runs `git ls-remote --symref <fork> HEAD` (same flags and helper). It refuses
+`remote-unrelated` when the fork is empty or when that tip isn't a commit the working repo already has and an
+ancestor of `main`. When `ls-remote` exits non-zero, for a fork that doesn't exist, a refused token or a
+network failure, `publish` refuses `fork-unavailable` and the push doesn't run (N11). Git's stderr isn't
+parsed to tell those apart and isn't returned, since it can carry the URL. Only `ls-remote` crosses the
+network for this, so nothing is fetched from the fork. If the fork has moved past root, the refusal stands
+until root catches up. That is a human pull into root, not an agent's.
+
+D9c. **The URL parse (B6).** `projects.<p>.remote` and `identity.gitea.url` are parsed with `new URL()` at load,
+and the business file refuses to load unless all of these hold:
+
+- The scheme is `https:`. There is no username, password, query or fragment.
+- The string equals its own normalized form: for the upstream, `url.origin + url.pathname`; for
+  `gitea.url`, `url.origin + "/"` or `url.origin`. So a dot segment (`/<user>/../OWNER/REPO`), a
+  percent-encoded dot, an upper-case host, an explicit `:443`, a backslash, userinfo, a query and a fragment
+  each refuse, because `new URL()` would change them (checked with node: each differs from its normalized
+  form). A trailing slash survives normalization and is refused by the two-segment rule below. The checks below run on that path, so the owner that is checked is
+  the owner that is used.
+- The upstream's path is exactly `/OWNER/REPO`: two non-empty segments, no more and no fewer. One trailing `.git` on
+  REPO is allowed and stripped. `fork` is built from the stripped REPO.
+- `OWNER`, `REPO` and `gitea.user` each match Gitea's name rule, `^[A-Za-z0-9_.-]{1,100}$` and not `.` or
+  `..`. REPO after stripping must still match.
+- `gitea.url`'s path is `/`. A Gitea served under a sub-path isn't supported by this row and refuses at load.
+- Host and port are compared after `new URL()` normalized them, and an omitted port counts as 443 on both
+  sides.
+- Gitea compares user and repository names without case (`lower_name`), so `remote-not-fork` compares the
+  upstream's OWNER with `gitea.user` without case. An upstream owned by `Coder` and a `gitea.user` of `coder`
+  would otherwise build a "fork" that is the upstream itself.
+
+D9b. **How `publish` reaches the broker and the store.** The git socket runs in the bus process
+(`cli.mjs:504-506`) and reaches the broker only through the host's op table (`bus/src/runtime.mjs:222-246`).
+`publish` adds three entries there, each wrapped in `refusing()`:
+
+- `checkPublish(cap, args)`: steps 1 to 3, including the decision check. It returns `{ticket, fork, user,
+  email, source}` and no token. The ticket holds the session and the decision until `recordPublish`, the
+  same way `checkLand` holds a landing.
+- `withGitea(cap, fn)`: `credentials.useFor(broker.session(cap), "gitea", fn)`. `fn` gets the token and runs
+  step 5. The token never leaves that call.
+- `recordPublish(ticket, result)`: step 6, and it spends the decision.
+
+The op table gets no entry that returns a token.
+
+D10. **Which refs.** Our side: only `refs/heads/<gitea.user>/*`, set by the host (D9 step 3). The default
+branch and other agents' prefixes can't be named. Gitea side, two options (Q-M1):
+
+- **O1. A fork per agent. Ruled by Mos (mos-1027).** The agent's Gitea user has read on the upstream repo and owns a fork
+  named like it. The host derives the fork's URL from the upstream and the agent's user (D9 step 2).
+  Its token can write only repos the user owns or collaborates on, so Gitea itself stops any push to upstream
+  or to another agent's fork. No branch rules are needed per agent, so none can drift. The cost: work reaches
+  upstream as a pull request from the fork, opened by a human or a later API verb.
+- **O2. One shared repo. Not chosen.** The agent is a Write collaborator. Upstream's default and release branches get
+  branch protection with no agent on the push list, plus a rule `<user>/*` per agent. Gitea doesn't stop agent
+  A from creating an unprotected name outside `A/*` unless a catch-all rule outranks the per-agent ones. That
+  depends on Gitea's rule priority, which I haven't verified on our version (probe P1). Every hire adds a rule.
+
+Token scopes for either: `write:repository` and `read:user`, nothing else, per vocabulary.mjs rules (no
+`all`, no admin).
+
+D11. **The host git socket.** `publish` is added to the socket. `push`, `fetch` and `land` don't change. The
+socket's bind rule (E4) adds `git.push.remote`. The working repo stays credential-free and remote-free. The
+`fork` URL is passed per call and never written into its config. A landing still squashes into the project
+root as "Mosaic bus host". Landings don't push anywhere.
+
+## 6. Lifecycle (brief item 4)
+
+All verbs are on the bus, in the CLI (`mosaic credentials ...`) and in the Console's agent page. Every verb is
+human-only. Under Q173 the tester may run `status` and `revoke` on the dev stack instance. `issue` and
+`rotate` stay with Jason, because the tester is an agent and the token would pass through its session
+(duckworth N1). Each one appends to the organization
+writer's `changes.jsonl` (actor, agent, kind, verb, date; never a value). No schema migration, no new event
+kind. A refusal uses `action.refused`.
+
+| Verb | What it does |
+|---|---|
+| `issue AGENT KIND --rotate-by DATE` (gitea) or `--expires DATE` (vikunja) | Reads the token on stdin (never argv), checks E2's format, writes `<kind>.tmp` 0600, fsyncs, renames over `<kind>`, and sets the business file reference to `{"store": true, date}`. The bus reloads that one entry, with no restart |
+| `rotate` | Same as `issue` over an existing entry. The old value is gone from disk and memory when the call returns. Jason then deletes the old token in Gitea (A5) |
+| `revoke AGENT [KIND] --reason` | Drops the entry from the bus's memory first, then unlinks the file. A use in flight finishes. Every later use refuses `credential-unavailable` |
+| `delete AGENT` | `revoke` for every kind, then removes the agent's dir. Refused while the agent has a running claim |
+| `status [AGENT]` | Kind, date and state per entry (E3's `status()`), no values |
+
+D12. **"Stops working at once."** On our side this holds without a timing window. A fired agent never holds a
+`gitea` or `vikunja` token (D3), so revoking means the bus no longer has it. On the Gitea and Vikunja side the
+token still exists until Jason deletes it (A5). The status line for a revoked entry says so until Jason
+confirms. The model token is the exception: it sits in the running sandbox (D7), so a fired agent's runs must
+end. Row 194's fire ends them.
+
+D13. **What row 194 calls.**
+
+- `credentials.issue` is never called by the chief. Row 194's hire stays uncredentialed (its D1).
+- A human `create` of a credentialed definition: row 194 lifts E9's refusal for the human path only. The agent
+  is created with `store` references and no files. `launch` refuses `credential-unavailable` until Jason runs
+  `issue`.
+- `fire` and `delete`: row 194 calls `credentials.revoke(business, agent, {reason, actor})` before it changes
+  the business file. A failed revoke stops the fire (`credential-revoke-failed`), so an agent can't be fired
+  with its credentials still live on our side.
+- `regenerate`: no credential change.
+
+## 7. Who does what (brief item 5)
+
+Agents never mint accounts or tokens. Jason's steps, per agent that needs `gitea`:
+
+- A1. Create the Gitea user: Site Administration, User Accounts, Create User Account. The name is the agent's
+  `gitea.user`. The email is the agent's `identity.email`.
+- A2. Create its token: sign in as that user, Settings, Applications, Generate New Token, scopes
+  `write:repository` and `read:user`, nothing else.
+- A3. Create the fork of each granted repo as that user (O1). Gitea's push-to-create
+  (`ENABLE_PUSH_CREATE_USER`, `ENABLE_PUSH_CREATE_ORG`) stays off, so a push to a missing `<user>/REPO`
+  fails rather than creating a plain repository (N11). `publish` refuses `fork-unavailable` before that.
+- A4. On the stack instance's VM, as its OS user: `mosaic credentials issue AGENT gitea --rotate-by DATE`, with
+  the token pasted into stdin.
+- A5. On fire or rotate: delete the token in Gitea (Settings, Applications), or disable the user.
+- A6. Model: sign in to the provider on each VM user to write `<configDir>/secrets/claude-session.env`.
+
+Vikunja bot accounts and tokens are already Jason's (tracker bots). Only A4 changes for them.
+
+## 8. Migration (brief item 6)
+
+- M1. Existing `{file}` and `{env}` references keep working. A business moves one agent at a time with
+  `issue`, which rewrites that agent's reference to `store`.
+- M2. Nothing here touches the dev repository's helper, its `.git/config`, `~/.mosaic` or `~/.mosaic-dev`.
+  Dev seats (jarvis, seat tokens) keep pushing as today. The mos-0981 rule ends only when Mos says so.
+- M3. The live dev stack instance needs no change at re-pin: no reference uses `store` until someone issues
+  one.
+
+## 9. Questions
+
+Mos ruled on the authority model in mos-1027 (2026-10-20T19:27Z):
+
+- Q-M1. O1, one fork per agent.
+- Q-M2. `git.push.remote` and its bounds in D9 to D11 are approved. It lands as a hard wait: out of ROUTED,
+  and no role grants it within-role (D9 step 1). Sage puts its routing in the PRD version draft going to
+  Jason with `role.hire` and `role.fire` (Vikunja #420). After his approval, a reviewed commit routes it and
+  grants it to coder.
+- Q-M3. Issue, rotate and delete are human-only, and the chief gets none of them. Under Q173 the dev
+  instance's tester gets `status` and `revoke` only.
+- Q-M4. The model credential stays per stack instance for 10-27. Per-agent model tokens wait for a proxy
+  row.
+
+Open for Jason. Mos takes these to him one at a time:
+
+- Q-J1. The model account for Case 1 and Case 2: existing subscription or a new account.
+- Q-J2. Gitea users and tokens for the agents that need them (A1 to A3).
+
+## 10. What this closes (brief item 7)
+
+- G11: closes the store (D1 to D6) and lifecycle (section 6) for `gitea` and `vikunja`. Still open: per-agent
+  model credentials (D7), and the same-uid limit inside one stack instance (D6).
+- G13: closes "own credentials for git" (D8 to D10). Still open: Gitea API verbs (section 4).
+- C2.5 (git remote): Case 2's books repo can use `publish` once its project names a remote.
+
+## 11. Tests and mutants
+
+All tests use scratch roots, fake tokens and a fake Gitea: `git http-backend` behind a node http server on
+127.0.0.1 that checks basic auth against a fake token and records each ref update. No request leaves the host.
+
+- T1. Layout: wrong mode or owner on a dir or file refuses start. A `{file}` reference into another agent's
+  path refuses `credential-not-yours`. A bus restart after a create without `issue` starts, and the agent's
+  status is `not-issued`. A missing `{file}` still refuses start.
+- T2. `useFor` keys from the cap only. A request naming another agent is refused and leaves one
+  `action.refused`.
+- T3. The fake Gitea serves https on 127.0.0.1 with a cert from a scratch CA made by the test. It reaches git
+  only through the `tls` parameter (D9 step 5). Each refusal test that should reach the network asserts that
+  the first port received the request, so no test passes because git refused http first. `publish`: the
+  happy path lands `refs/heads/<user>/<branch>` on the agent's fork in the fake, which shares root's history, at
+  exactly the decision's commit. Refusals for each step in D9, one test each, including `work-not-yours`. Until routing, a publish with
+  no decision refuses, one with a decision for another task or commit refuses, and a second publish on a
+  spent decision refuses `decision-consumed`. Approve while the latest push is A, push B, publish: refuses
+  `decision-mismatch`, and the fork receives nothing. A push to the working repo between `checkPublish` and
+  the git push refuses with `ref-moved` or `decision-mismatch` (sage-1440, BUILD.md deviation 14). A raise with no recorded push refuses `no-push`. A test pins that `git.push.remote` is in neither ROUTED list
+  and that no `roles/*.json` grants it. A force-push attempt is
+  refused by git's non-fast-forward. A fake fork that answers 302 to a second 127.0.0.1 port: the push
+  fails, and the second port receives no request with an Authorization header. A remote on the right host
+  and a different port is refused at step 2. Two agents granted one project each land on their own fork:
+  agent A's push reaches `/<A's user>/REPO` only and B's reaches `/<B's user>/REPO` only, and the fake's
+  upstream repository receives nothing. An upstream owned by the agent's own user refuses `remote-not-fork`,
+  and so does one whose owner differs from `gitea.user` only in case. With an upstream that shares root's
+  history, a first publish to an empty fork and to an unrelated fork each refuse `remote-unrelated`, and
+  neither fork nor upstream receives objects. A fork that doesn't exist refuses `fork-unavailable`, and the
+  fake records no push. `ls-remote` and the push each reach the fork's path only (the fake records every
+  path). Load refusals (D9c), one test each: a dot segment, an extra path segment, a missing segment,
+  a trailing slash, userinfo, a query, a fragment, an explicit `:443`, a name outside Gitea's rule, and a `gitea.url` with a
+  sub-path. A `.git` suffix loads and builds the fork without it. A `publish` grant on an agent without
+  `identity`, and on one whose definition lacks `gitea`, each refuse at load with the N10 message.
+- T4. Token handoff: the token never appears in argv, env, the fork URL, the working repo config,
+  `changes.jsonl`, events or logs (scan every file under the scratch roots).
+- T5. Lifecycle: issue, rotate, revoke and delete, each live with no restart. After revoke, `publish` and the
+  Vikunja path refuse `credential-unavailable`, and so they do after a bus restart that follows the revoke.
+  The tester can run `status` and `revoke`, and `issue` and `rotate` refuse it.
+- T6. Default: an agent without `identity` commits as E7. Existing `{file}` references load unchanged.
+
+Mutants to kill: drop the cap-derived key in `useFor`, let the request name the destination ref, add `+` to
+the refspec, skip the identity check, put the token in the URL, revoke file before memory, skip the dir mode
+check, allow a `{file}` reference into another agent's dir, make ENOENT on a `store` path fatal again, make
+ENOENT on a `{file}` path silent, a helper that answers any host, drop `http.followRedirects=false`, drop the
+`work-not-yours` check, drop the `remote-unrelated` check, add `git.push.remote` to ROUTED, skip the spent
+check on the decision, drop the `pushCommit` comparison in `#authorityFor`, push by ref name in place of the
+oid, push to the upstream URL in place of the derived fork, run `ls-remote` against the upstream in place of
+the fork, take the fork's owner from anywhere but the agent's `gitea.user`, compare the owner with case, run the
+D9c checks on the raw path in place of the normalized one, read a failed `ls-remote` as empty, skip the tip
+check under the lock, and pass a CA flag in production.
+
+## 12. Risks
+
+- R1. Backups: if a backup tool copies `<configDir>`, it copies tokens. The build checks row 185's backup set
+  and says what it includes.
+- R2. Withdrawn. O1 was ruled, so probe P1 isn't needed.
+- R3. Outbound HTTPS from the bus host to Gitea is new network reach for the host process. On the VMs this is
+  Jason's network to confirm.

agents/megavolt/work/queue-237/BUILD.md

@@ -0,0 +1,75 @@
+# Row 237: one decision publishes once (#1743)
+
+Megavolt, 2026-10-21 (from `date -u`). Brief: `docs/plans/2026-10-20_agent-credentials.md`
+§ "row 199 follow-up N1", blob dca67d310e1b. Source: Duckworth's row 199 round 1 note N1
+(duckworth-0068). Base: `cb5fdb064` (row 199's landing). Reviewer Duckworth, gate owner Sage.
+
+## The defect
+
+`checkPublish` opens a ticket after checking the decision is unspent. The decision is spent only at
+`recordPublish`, which runs after the bus process has pushed. Two `checkPublish` calls on one decision
+therefore both get tickets, and both push. With different branches, the commit lands on two fork refs:
+`refs/heads/<user>/feat` and `refs/heads/<user>/other`. The second `recordPublish` then refuses
+`decision-consumed`, but by then its push has already reached the fork.
+
+## The fix, and why this option
+
+`checkPublish` refuses `publish-busy` when an open ticket in `#publishes` holds the same business and
+decision (`packages/bus/src/broker.mjs:1038-1040`). It runs after the authority and fact checks, so a
+spent decision still refuses `decision-consumed` first.
+
+The brief's other option, rechecking `#spent` in `publishTarget`, doesn't close the race. Both tickets
+reach `publishTarget` before either push ends, and nothing is spent until `recordPublish`. So both
+rechecks pass and both pushes run. The only state that exists while the first push runs is the open
+ticket, so the check reads that.
+
+A refusal (`publishRefused`) drops the ticket and leaves the decision unspent, so a retry on the same
+decision gets a new ticket. That is row 199's behaviour, unchanged. A within-role publish has no
+decision and isn't affected.
+
+## Tests
+
+- `packages/bus/tests/publish.test.mjs:186`. A second ticket refuses `publish-busy`, on the same branch
+  and on another. After `publishRefused` the retry gets a ticket and a third refuses busy. After
+  `recordPublish` there is one `action.allowed` for git.push.remote and the next call refuses
+  `decision-consumed`. Another agent's decision on the same task isn't held.
+- `packages/cli/tests/publish-socket.test.mjs:269`. End to end through the git socket, the bus runtime
+  and the TLS fake Gitea. While the first publish holds its ticket, a second publish on the same
+  decision to branch `other` gets `publish-busy`. The fake Gitea gets exactly one `git-receive-pack`,
+  the fork has only `refs/heads/coder/feat`, and there is one `action.allowed`.
+
+Runs on this branch, single files:
+- publish.test.mjs: 13/13.
+- publish-socket.test.mjs: 8/8.
+
+## Mutant
+
+M1 removes the `publish-busy` line. Both tests fail:
+- The bus test fails at the first busy assert.
+- The cli test fails because the second publish answers `ok: true` with `ref: refs/heads/coder/other`.
+  That is the defect: two refs on the fork.
+
+Logs are in `/mnt/storage/scratch/megavolt-r237/` (m1-bus.log, m1b-cli.log). `cmp` confirmed
+broker.mjs matched the saved copy after the restore. The first cli mutant run (m1-cli.log) was against
+a hook that recursed on every checkPublish. I fixed the hook to fire only for branch `feat` and reran
+it (m1b-cli.log).
+
+## Residuals, not fixed here
+
+1. **A ticket that never ends holds its decision until the bus restarts.** `#publishes` is in memory.
+   That happens when the host dies between checkPublish and recordPublish or publishRefused. It fails
+   closed (`publish-busy`), and a restart clears it.
+2. **publish-timeout (sage-1440).** The socket files `publishRefused` and drops the ticket, but the bus
+   process's push may still be running. A retry on the same decision can then open a ticket while that
+   push is live. This is the same residual the socket already logs ("the bus process's push may still
+   reach the fork"). Closing it means the runtime's `remotes` must keep the decision busy until its push
+   settles, which reaches into runtime.mjs. That is beyond the brief's two options.
+3. **checkLand has the same shape.** `#landings` takes a ticket per call and the decision is spent at
+   `recordLand`. Whether two landings on one decision can both reach main isn't checked here. That's a
+   follow-up for Sage to row or dismiss.
+
+## Gate
+
+Per the brief: Duckworth approves the manifest, the bus suite and every `scripts/test-*.sh` are green
+on Sage's gate, and M1 is killed. This row also changes a cli test file, so the cli suite (or that file
+alone) should run on the gate too.

agents/megavolt/work/queue-241/BUILD.md

@@ -0,0 +1,71 @@
+# Row 241: one decision lands once (#1747, P19 441)
+
+Megavolt, 2026-10-21 (from `date -u`). Brief: `docs/plans/2026-10-20_agent-credentials.md`
+§ "Brief: row 237 follow-up, one decision lands once, with tests at the broker", c25785d3d. Source:
+row 237 residual 3, megavolt-0068, megavolt-0069 and sage-1651. Base: origin/refactor f5753c0e8, row 210's landing.
+Reviewer Duckworth, gate owner Sage. Tests only; no source changes.
+
+## Why landing has no row 237 race
+
+Row 237 fixed publish: two tickets on one decision both pushed, because the decision is spent only
+after the push, and a push to a remote fork can't be taken back. Landing has the same ticket shape
+(`checkLand` opens a ticket, `recordLand` spends the decision), but three guards keep one decision
+from landing twice:
+
+1. **land-busy, the outer guard.** `doLand` in `packages/cli/src/git-socket.mjs:351` refuses
+   `land-busy` while another landing runs. The slot is taken before the first await, and freed only
+   when the landing ends. There is one git socket per launcher, and one host per dataRoot (host.lock).
+   So through the socket two landings never overlap, and a later one stops at `checkLand` with
+   `decision-consumed`. Even past that, applying the same reviewed patch to the new main fails
+   `base-conflict` in `prepareLand`.
+2. **The CAS on main.** `finishLand` (`packages/seat/src/working.mjs:391`) moves main with
+   `update-ref main <commit> <old>`, so a landing prepared on a tip that has since moved refuses
+   `base-moved` and writes nothing.
+3. **The recordLand recheck.** `finishLand` calls `record()`, which is `recordLand`, under the same
+   repository lock. `recordLand` runs `#landFacts` again (`packages/bus/src/broker.mjs:963`), which
+   refuses `decision-consumed` once the decision is spent. When `record()` throws, `finishLand` moves
+   main back.
+
+Guards 2 and 3 can't be reached end to end, because guard 1 stops a second landing first. So they are
+pinned below the socket, and no test bypasses land-busy.
+
+### The unrecorded-commit window
+
+Between the `update-ref` and the end of `record()`, main names the squash, which isn't recorded yet.
+That window is under the repository's lock, so no other push, review or landing in this host sees
+it. If `record()` refuses, main moves back. If moving back fails, `finishLand` refuses
+`rollback-failed` and main keeps naming an unrecorded commit (tested at `working.test.mjs:555`, the
+main.lock case). That is existing behaviour, unchanged here.
+
+## The test
+
+`packages/bus/tests/land.test.mjs:312`. Two tickets pass `checkLand` on one decision before either
+records. `recordLand` on the first lands. `recordLand` on the second refuses `decision-consumed`
+(:319), and leaves one merge `action.allowed`, one RESULT and no `action.refused`. `landRefused`, as
+the socket would call it, then files the refusal and ends the ticket.
+
+**The assert that pins the recordLand recheck is :319.** The `#spent` line is shared with
+`checkLand`, so dropping it also fails :144 (a `checkLand` after the decision is spent). Only :319
+shows the recheck at record time.
+
+Single file on this branch: land.test.mjs 18/18.
+Whole suites on this branch before in-review: bus 500/500, seat 164/164, cli 565/565 (02:52 to 03:01Z).
+
+## Mutants
+
+| Mutant | Change | Killed by |
+|---|---|---|
+| M1 | drop the `#spent` line in `#landFacts` (broker.mjs:963) | land.test.mjs: :312 at :319, and :94 at :144 (16/2) |
+| M2 | drop `land.old` from the `update-ref` in `finishLand` (working.mjs:391) | working.test.mjs:555 at :567, the `base-moved` assert (25/1) |
+| M3 | drop the `land-busy` throw (git-socket.mjs:351) | git-socket.test.mjs:812 at :825, the `land-busy` assert (23/1) |
+
+Each run was one test file on base f5753c0e8 (row 210's landing, which moved the `#spent` line from
+:945 to :963), 2026-10-21 02:51Z. Each assert failed with "Missing expected exception" or "rejection".
+`cmp` confirmed each source matched its saved copy after the restore. M2 is killed by the existing
+working.test:555, so per the brief working.test.mjs isn't changed. Logs: `/mnt/storage/scratch/megavolt-r241/`
+(m1.log to m3.log, with each diff).
+
+## Gate
+
+Per the brief: Duckworth approves the manifest; the bus, seat and cli suites and every
+`scripts/test-*.sh` are green on Sage's gate; the three mutants are killed.

agents/megavolt/work/queue-242/BUILD.md

@@ -0,0 +1,108 @@
+# Row 242 build: a retry after publish-timeout pushes once
+
+Row 242, #1748, P19 440. Brief: docs/plans/2026-10-20_agent-credentials.md, "Brief: row 237
+follow-up N1, a retry after publish-timeout pushes once" (9d165be8c). Base: origin/refactor
+8fede5fc6 (row 210 landed f5753c0e8).
+
+## The defect
+
+The git socket polls publishResult until publishDeadlineMs, then refuses publish-timeout
+(packages/cli/src/git-socket.mjs:433) while the bus process's push (runtime publishPush) can
+still be running. The socket then calls publishRefused, which went straight to
+broker.publishRefused: it filed the refusal and deleted the ticket. checkPublish no longer saw an
+open ticket on the decision, so a retry got a new ticket and pushed a second ref while the first
+push was still on its way to the fork.
+
+## Fix chosen: hold the decision until the push ends, then record a push that reached the fork
+
+packages/bus/src/runtime.mjs, `publishRefused` and `settle`:
+
+- If the bus has no push for the ticket, publishRefused goes to the broker as before.
+- If the push is still running, the refusal code is held on the entry and the ticket stays open.
+  checkPublish refuses another publish on the decision with publish-busy (row 237's check),
+  the same as when the socket is still polling.
+- When the push ends, `settle` runs:
+  - A push that reached the fork is recorded with broker.recordPublish, which spends the
+    decision. The bus logs `pushed after the git socket refused <code>; recorded`.
+  - A push that failed is filed as publishRefused with the socket's code.
+  - If recordPublish refuses with a BusError, that code is filed instead.
+- If the push has already ended when the refusal arrives, it's settled at once. The sage-1440 test
+  relies on this: its push fails fast, so publish-timeout is filed once, immediately, as before.
+
+Why hold rather than kill. Killing the git client doesn't undo a push the fork has already
+received: receive-pack can update the ref after the client dies. After a kill the bus would have
+to ls-remote the fork to learn what landed, and the result could still race the server. Holding
+waits for the push's own outcome. Each git run in publishRemote already has its own limit
+(publishRemote defaults to checkout.mjs GIT_LIMITS), so a hold is bounded. Holding also reuses the existing publish-busy
+state, and the refusal text is unchanged.
+
+Why record and not only hold. If the hold just filed publish-timeout once the push ended, the
+ticket would close and the decision would be free again with a ref on the fork. A retry would then
+push a second ref. Recording the late push spends the decision, so the retry gets
+decision-consumed.
+
+The publish-timeout refusal text is unchanged (brief condition).
+
+## Test
+
+packages/cli/tests/publish-socket.test.mjs:302, "row 242: a retry after publish-timeout refuses
+publish-busy while the bus process's push runs; the late push is recorded and the decision pushes
+once".
+
+- publishDeadlineMs 150 and a store token. The fork's pre-receive hook writes `held`, then loops
+  until the test writes `release`.
+- The first publish gives publish-timeout. The test waits for `held`.
+- A retry to branch `other` gives publish-busy (:322). Refused events: ["publish-busy"]. No
+  git.push.remote allowed event.
+- The test writes `release` and waits until there is exactly one allowed event, with ref
+  refs/heads/coder/feat and the work commit.
+- The next retry gives decision-consumed (:330).
+- Exactly one git-receive-pack request reached the fake Gitea, and the fork has only
+  refs/heads/coder/feat. Refused events: ["publish-busy", "decision-consumed"]. No TOKEN appears in
+  events or logs.
+
+Fail fast (sage-1681): the body is wrapped in try/finally, and the finally writes `release`. Under
+the first mutant run, the assert at the retry failed and the hook was never released. setup's
+teardown waits for the fake Gitea, which waited for the held push, so the file hung until I stopped
+it. Now a failed assert ends the hook and the run. Each wait is bounded at 10 s with an assert.fail.
+
+## Mutants
+
+Script: /mnt/storage/scratch/megavolt-r242/mutants.sh. Each mutant: save, one-line sed, run
+publish-socket.test.mjs whole, restore, cmp.
+
+| Mutant | Change | Expected kill |
+|---|---|---|
+| M1 | export `publishRefused: (ticket, args) => broker.publishRefused(ticket, args)` again (removes the fix) | :302 at :322: the retry gets a new ticket and its own push, so publish-timeout, not publish-busy (seen in the stopped 03:06Z run) |
+| M2 | `settle` files publishRefused without trying recordPublish (hold only) | :302 at the wait for one allowed event, then :330 |
+
+Results (Sage's slot, sage-1686, 2026-10-21T03:35:00Z to 03:35:15Z): both killed, both restored
+(cmp ok).
+
+- M1: publish-socket 8/1, the row 242 test fails at :322 in 0.5 s.
+- M2: publish-socket 8/1, the row 242 test fails at :327, the wait for one allowed event, through
+  the assert.fail inside `until` (:311) after its 10 s bound, in 10.3 s.
+
+## Suites
+
+On Sage's slot (sage-1686), on base 8fede5fc6 plus this row:
+
+- bus `node --test tests/*.test.mjs`: 499/499, 03:35:20Z to 03:35:34Z. This is one fewer than
+  Sage's 241 gate (500) because the base predates row 241's land.test case.
+- cli `node --test tests/*.test.mjs`: 566/566, 03:35:34Z to 03:43:47Z. That's 565 plus the
+  row 242 test.
+
+Singles before the slot: publish-socket.test.mjs 9/9, bus publish.test.mjs 13/13. The seat suite
+and scripts/test-*.sh are left for Sage's landing gate.
+
+## Residuals
+
+- The agent was told publish-timeout, but the push is recorded later and the run isn't
+  notified. The allowed event and the bus log line are the only trace. A later publish on the
+  decision gets decision-consumed, which tells the agent the decision was used. Whether the run
+  should get a RESULT for a late record is a follow-up question for Sage.
+- A late push whose recordPublish refuses (Duckworth N2) is filed with that code: the ref stays on
+  the fork and the decision is not spent, the same residual as an in-band push whose record
+  refuses.
+- The hold lives in the bus process's memory, like the broker's open tickets. A bus restart during
+  a hold drops both, the same as today for any publish in flight.

agents/morgana/README.md

@@ -3,5 +3,5 @@
 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 row 195 settles per-agent identity, it pushes only its own `morgana/*` branches
+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/morgana/work/queue-193/DESIGN.md

@@ -1,482 +0,0 @@
-# Row 193 design: many humans per business, human roles, private and shared threads
-
-Morgana (Opus 5.5), 2026-10-20. Revision 5: sage-1373 item 1 (mos-1023 item 2), the user sentence names every record the owner sees. Revision 4: duckworth-0011 B3 and N5. Revision 3: duckworth-0008 B1, B2 and N1-N4, sage-1368. Revision 2: sage-1354 (5.7 private from the owner, 193b split) and gizmoduck-0018 (coverage and the R4 predicate in FED r4.1). Gitea #1691, queue row 193, brief `docs/plans/2026-10-20_human-users.md`
-(blob f7472d1e47b1). Reviewer Duckworth, gate owner Sage. Base: `refactor` at 53bb59462.
-
-Read for this design: COMMON.md (53bb59462), the brief, Gizmoduck's federation design r4.4 (b67bc6de9 on
-gizmoduck/federation-design, cited as FED; r3.1 a2840a6be was read first), Duckworth's federation reviews (b402197ff, 03a663cd7,
-45cbe5896 on duckworth/reviews), Sage's Q175 SSO design (`agents/sage/work/q175-sso/DESIGN.md`), the row 192
-and row 196 briefs, Darkwing's row 190 packet (uncommitted, sha256 5493c9df3ec0...), and the bus, business,
-cli and webui code at the lines cited. Messages: morgana-0001 to 0003, sage-1338, gizmoduck-0009,
-gander-0002 and gander-0005.
-
-## 1. Summary
-
-- Three human roles: **owner**, **collaborator**, **viewer**. The owner is the business file's one `human`,
-  as today. Collaborators and viewers are access.json users, the same store federation uses (FED 3.5).
-  Their role is the `level` of a grant, so a role is per project and instance, not per person.
-- Every human principal is minted by one bus verifier, owned by row 196 (Gander). Row 193 states what it
-  needs from that verifier (section 6) and adds no second mechanism.
-- Threads stay private to their owner by default. A thread owner may share a thread, read-only, with a
-  named user, with the owner, or with everyone granted on it. Shares live in a new append-only bus table,
-  `thread_shares`. This is a deviation from brief point 4, agreed by Sage (sage-1338), for Duckworth to rule
-  on (section 5.1).
-- A share never widens a grant. It counts only while the reader's live grant covers the thread's project
-  and instance, and while the thread's owner still has coverage. Revocation, expiry and unsharing take
-  effect on the next request.
-- Existing businesses keep working unchanged: every existing thread is already owned by the business
-  human, and an instance without access.json has exactly one human, the owner.
-- The build splits so the part without a schema change can land first. `thread_shares` needs schema 3j and
-  a `--migrate` window with Jason.
-
-## 2. What exists today (measured at 53bb59462)
-
-- One `human` per business (`packages/business/src/business.mjs:160`). `bindHuman` refuses any other name
-  (`packages/bus/src/broker.mjs:532-538`).
-- The owner's CLI proof is path-bound (#225): `verifyHuman` checks uid, start time, nonce
-  (`MOSAIC_BUS_CLI_NONCE`), `argv[1]` equal to the tree's `human-cli.mjs`, then walks parents and refuses
-  agent markers, launch records and agent binaries (`packages/bus/src/human.mjs:64-96`).
-  `authenticateHuman` binds the proof to `businesses[business].human` (`packages/bus/src/runtime.mjs:175-182`).
-- Threads: `threads(seq,id,at,business,project,instance,owner,name)`, append-only
-  (`packages/bus/schema.sql:247`, triggers at :310-312). `#owner(s)` returns `tester` or `s.human`
-  (broker.mjs:364-366). `#thread` refuses a non-owner with `thread-not-owned` (:357-362).
-- Thread verbs are gated `if (!s.tester) this.#human(s)`: `project.list` (:2318), `thread.create` (:2325),
-  `thread.list` (:2351, owner filter), `thread.open` (:2365), `thread.send` (:2374, writes `human.input`
-  for the human only), `thread.messages` (:2401).
-- Board reads are business-wide and human or reader only: `inbox`, `agents`, `tasks`, `trail` (:2143-2167),
-  `decisions` (:2174), `credentials` (:2195), `messages` (:2217, `to_role='human'`), `replies` (:2422).
-  `trail` and `replies` return any message in the business by id (:2679-2700, :2422-2432).
-- The Console reads threads by polling the same verbs (`packages/webui/src/chat.mjs:22-26`). It has no
-  stream, so a refusal on the next poll ends access.
-- The launcher restarts a thread with pending messages as the business human
-  (`packages/cli/src/launcher.mjs:533-542`).
-
-## 3. The human model (brief point 1)
-
-### 3.1 Who the humans are
-
-| Human | Where it is declared | How many | Identity |
-|---|---|---|---|
-| owner | business file `human` (unchanged) | exactly one per business | the business human's name |
-| user (collaborator or viewer) | access.json `users[]` with `home: "local"` (or a peer id under federation) | any number | `user:<id>` |
-| tester | not a human; row 177 test principal | one | `tester` |
-
-The owner stays outside access.json (FED 9 Q2). A business has no second owner and no admin level. Adding
-one is out of scope; section 9 lists it as a follow-up for Jason.
-
-### 3.2 How a sign-in or a call becomes exactly one human
-
-| Entry | Becomes | Checked by |
-|---|---|---|
-| Console SSO session whose `(provider, sub)` is in `console.sso.providers[].subjects` (row 192) | the owner | the Console after OIDC checks, then the bus verifier (row 196) |
-| Console SSO session whose `(provider, sub)` is a `users[].subjects` entry in access.json with a live grant | that one user | same |
-| Console SSO session matching neither | nobody: refused | the Console, and the bus refuses any later claim |
-| CLI call through `human-cli.mjs` that passes the human proof | the owner | the bus (`verifyHuman`) |
-| Any other process, including an agent | nobody | the bus |
-
-Why each is exactly one:
-
-- The R1 loader refuses a `(provider, sub)` pair that appears twice in access.json or also in
-  `console.sso.subjects` (FED 3.5). So one subject maps to at most one human.
-- A user id can't be `human`, `tester` or any business's human (FED 3.5). So a user can't be named as the
-  owner.
-- A terminal maps only to the owner. The only identity the bus can verify for a local process is the
-  instance's OS user, and that is the owner's. A user has no CLI path in row 193. This follows Mos's B1 rule
-  (mos-0985): the principal comes from what the bus verifies, never the process's own claim.
-- The bus never reads a user name from a request body as identity. The verifier returns the principal
-  (section 6).
-
-## 4. Human roles (brief point 2)
-
-### 4.1 The three roles
-
-- **owner**: everything the business human does today. Only the owner restructures the organization
-  (business file writer, project and role changes) and only the owner manages users and grants.
-- **collaborator**: FED 3.5's level, unchanged. Creates threads in granted projects on granted instances,
-  sends into and opens its own threads, and in row 193 also shares its own threads.
-- **viewer**: new. Reads threads shared with it, within its grant. It creates, opens and sends nothing, so
-  it never drives an instance. FED 3.5 notes that a collaborator's message drives the instance with the
-  owner's role authority (F10). A viewer has none of that.
-
-The word "collaborator" stays, so FED's tests and help text need no rename. The brief's example "member" is
-this level.
-
-A role is the `level` on a grant, and a grant is per business, project set and instance set. A user may
-hold a collaborator grant on one project and a viewer grant on another. Every check asks "does a live
-grant of a level that allows this verb cover this project and instance". A user has no single role.
-
-### 4.2 R1 widening
-
-FED R1 refuses any level but `collaborator`, because the 10-27 slice ships only that (FED 9 Q2).
-Row 193 widens R1's level check to `collaborator` or `viewer`, with its own test that each is accepted and
-anything else refuses. Nothing else in the access file changes. If R1 has not landed when row 193 builds,
-this one-line widening goes into the row 193a candidate chained on R1's candidate (Q177).
-
-### 4.3 Bus verbs per role
-
-Every verb not in a user's column fails `access-refused` before its own checks, as FED 3.5 requires for
-collaborators. That covers every owner verb, every board read, `message.*`, `decision.*`, project files,
-`spec.read`, `assistant.stop`, `launch.*`, `name.set`, `usage.*` and `access.reload`.
-
-| Verb | owner | collaborator | viewer |
-|---|---|---|---|
-| `project.list` | all | projects covered by any live grant | projects covered by any live grant |
-| `thread.create` | yes | collaborator grant covers project and instance | refused |
-| `thread.list` | own threads | own threads still covered | own threads still covered (from an earlier collaborator grant) |
-| `thread.list {shared: true}` (new) | threads shared with the owner | threads shared with me and readable (5.4) | same |
-| `thread.open` | own | own, collaborator grant still covers | refused |
-| `thread.send` | own | own, collaborator grant still covers, no `human.input` | refused |
-| `thread.messages` | own, or shared with the owner | own (any level still covering), or shared and readable | same as collaborator |
-| `thread.share`, `thread.unshare` (new) | own threads | own threads, collaborator grant still covers | refused |
-| `thread.shares` (new) | own threads | own threads | refused |
-| `names` | all | instances covered by any live grant | instances covered by any live grant |
-| every other verb | as today | refused | refused |
-
-Notes:
-
-- `thread.list` keeps its response shape exactly. Shared threads come only from `thread.list {shared: true}`,
-  whose rows add `owner`. The Console and existing tests read the plain list unchanged.
-- A viewer can still read its own threads when a collaborator grant is lowered to viewer, but can't send
-  or open them. This is the downgrade path.
-- The tester keeps its row 177 verbs. It can't share or be shared with: `thread.share`, `thread.unshare`
-  and `thread.shares` fail `tester-refused`, and a share target is never `tester`. Agent testers (Q173) test
-  sharing through the bus suites, not the live 7333 listener.
-- `reader` sessions (Console read caps, broker.mjs:1303) are the owner's board view and stay owner-only.
-  A user never gets a reader session.
-
-### 4.4 Console per role
-
-- owner: as today, plus a share control on each own thread and a "Shared with me" list.
-- collaborator: the chat view only, for granted projects (FED R6's granted-user sign-in), plus share
-  controls on its own threads and "Shared with me". No board.
-- viewer: "Shared with me" and its own old threads, read-only. No composer, no open, no share control.
-- The Console hides controls a role can't use, but the bus check is authoritative. A Console bug can't
-  widen a grant (FED 3.6). Each role gets a webui test with the UI check removed (mutant) that the bus still
-  refuses.
-
-### 4.5 Who manages humans and roles
-
-Only the owner, through `mosaic access` (FED R5), which checks the human proof and refuses tester and agent
-callers. Row 193 needs from R5:
-
-- `mosaic access user add <id> --home local --subject <provider>:<sub>` and `user remove <id>`;
-- `--level viewer` on `grant`;
-- the receipt line in `<dataRoot>/state/access-log.jsonl` and the `access.reload` call, as FED R5 has.
-
-If R5 has no `user` verbs when row 193 builds, row 193c adds them on R5's candidate. The Console gets no
-user or grant writes in row 193: a write from the Console would need a new owner verb that writes
-access.json from the bus, and access.json is a config file only the owner's CLI writes. A read-only users
-page for the owner is a follow-up (section 9).
-
-The owner keeps every restructuring power (TARGET Case 1). Users can't touch the business file, projects,
-roles or access.json.
-
-## 5. Private and shared threads (brief point 3)
-
-### 5.1 Deviation from brief point 4, agreed by Sage (sage-1338)
-
-Brief point 4 says access.json is the one store. Users, roles and grants live there. Per-thread shares do
-not, for three reasons (morgana-0002):
-
-- F1. Thread ids are bus-generated UUIDs. A hand-typed share with a typo would fail the loader, and the
-  loader refuses the whole file on any failure, which revokes every user.
-- F2. Only the owner writes access.json. A collaborator could never share its own thread.
-- F3. Threads are append-only bus rows, and a share is a runtime act by a principal that wants a trail.
-
-So shares go in an append-only bus table, gated by the grant. Sage agreed (sage-1338). Gizmoduck had no
-objection (gizmoduck-0009) and recorded it as FED 9 Q2. Duckworth rules on it in this review.
-
-### 5.2 Schema 3j
-
-```sql
-CREATE TABLE thread_shares (
-  seq INTEGER PRIMARY KEY AUTOINCREMENT,
-  at TEXT NOT NULL,
-  business TEXT NOT NULL,
-  thread TEXT NOT NULL REFERENCES threads(id),
-  op TEXT NOT NULL CHECK (op IN ('share','unshare')),
-  target TEXT NOT NULL,
-  by TEXT NOT NULL
-) STRICT;
-CREATE INDEX thread_shares_thread ON thread_shares (thread, target, seq);
--- no_update, no_delete and no_replace triggers, as thread_opens has (schema.sql:319-321).
-```
-
-- `target` is an owner string: `user:<id>`, the business human's name, or `*`. A share whose target is a
-  name that is no longer the business's `human` (after a rename) is void: rule 1 in 5.4 compares against
-  the current owner string, so it matches nobody (Duckworth N4).
-- `by` is the sharer's owner string, which is always the thread's owner.
-- A share's state is its latest row per `(thread, target)` (Duckworth N12, REVIEW-r3.md:74-76). Shares
-  are not assumed to only grow.
-- No existing row changes. Existing threads are already owned by the business human (`#owner` at
-  broker.mjs:364-366), so they are the owner's and private. The brief's "all become the current human's"
-  is already true.
-
-The migration `3i-3j.sql` creates the table, index and triggers. `thread_shares` joins every table list that
-holds timed append-only tables: `timedTables` in store.mjs (:60-74), the broker's clock list
-(broker.mjs:223-235), the restore guard's counted tables (row 181) and `COUNTED` in
-`scripts/stack-release.sh:315`. The schema digest for 3j is pinned as the other versions are.
-
-### 5.3 Verbs
-
-- `thread.share {thread, to}`: the caller must own the thread (`thread-not-owned`). For a user, a
-  collaborator grant must still cover the thread. `to` is `user:<id>`, the business human's name or `*`.
-  A `user:<id>` target must have a live grant, of any level, covering the thread's project and instance,
-  else `share-not-covered`. Sharing with yourself fails `invalid-request`. A share that is already in force
-  fails `share-exists`. Writes one `share` row.
-- `thread.unshare {thread, to}`: the caller must own the thread. The share must be in force, else
-  `share-not-found`. Writes one `unshare` row. Unsharing the owner's or `*` shares works the same way.
-- `thread.shares {thread}`: the caller must own the thread. Returns the shares in force, latest row each.
-- Both writes go through `refuse()` on failure, so each refusal records `action.refused` with `by` set
-  (FED 3.6 item 6).
-
-### 5.4 The read check, one function
-
-`#readable(s, t)` decides whether a session may read thread `t` it doesn't own. True only when all hold:
-
-1. a share for `t` is in force whose target is the caller's owner string, or `*`;
-2. the caller is the owner, or the caller has a live grant of any level covering `t.project` and
-   `t.instance`;
-3. if `t.owner` is a user, that user still has a live grant covering `t` (a revoked owner hides the
-   thread, sage-1338);
-4. `t.owner` is not `tester`.
-
-`#thread(s, id)` keeps its owner check for `thread.open`, `thread.send`, `thread.share`, `thread.unshare`
-and `thread.shares`. A new `#threadRead(s, id)` admits the owner or `#readable`, and serves only
-`thread.messages`. A sharee fails `thread-not-owned` on every write verb.
-
-### 5.5 Every read path and its filter
-
-| Read path | Today | After row 193 |
-|---|---|---|
-| `thread.list` | `owner=?` | unchanged for the owner; for users also each row's thread still covered |
-| `thread.list {shared: true}` | none | rows where `#readable` holds |
-| `thread.messages` | `#thread` | `#threadRead` |
-| `thread.open`, `thread.send` | `#thread` | `#thread`, plus a collaborator grant for users |
-| `project.list`, `names` | business-wide | per FED 3.5 for users, unchanged for the owner |
-| `trail`, `replies` | human, reader or tester; any message by id | users refused (`access-refused`); for the others, messages in other users' unshared threads hidden (5.7) |
-| `messages`, `inbox`, `agents`, `tasks`, `decisions`, `credentials` | human or reader | users refused (`access-refused`); owner unchanged. A user-thread run can't send to the human (`user-thread-human`, FED 3.6), so `messages` holds none of a user's thread |
-| `message.receive` by a run | its own thread (:1933) | unchanged: runs read their own thread, never a share |
-| `threadsState` (launcher) | all threads | adds `revoked` per 5.6 |
-
-### 5.6 Revocation, expiry and unsharing
-
-Gizmoduck asked that a grant loss end access to threads shared with that user (gizmoduck-0009 point 2).
-
-- A sharee holds no claim and no run. Its access is only reads, and every read runs `#readable` against the
-  access state the broker already refreshes on each request (mtime, size, inode), on its 30 s timer, and on
-  `access.reload` (FED 3.7). So a removed, expired or invalid grant ends share reads on the next request,
-  with nothing to tear down. The Console polls, so a revoked sharee's next poll fails.
-- An unshare row ends access on the next request in the same way.
-- A user who loses coverage of their own thread also loses its shares: rule 3 in 5.4.
-
-The downgrade case. With viewer, "no live grant covers" would be wrong for runs: a viewer grant covers the
-thread but must not let a run continue. FED puts this in R4: `revoked`, claim end and the launch check call
-`covers` with level `collaborator`, so a downgrade to viewer ends the run within one launcher tick. FED r4.4
-(b67bc6de9, mos-1020) chains R4 after row 193's viewer level (193a) and keeps the level-loss test and its
-mutant in R4. Row 193 carries neither (Duckworth N3), so the mutant has one owner.
-
-### 5.7 What "private" means, stated plainly
-
-Sage ruled (sage-1354): a user's thread is private from the owner on the bus too. Jason's words are "private
-agent sessions per user", and in Case 2 the owner of Melanie's hub is not the user whose thread it is.
-Duckworth's B1 asked where the line sits, since a user-thread run acts with the owner's role authority (F10).
-I took Duckworth's option (a): **the user's messages are private, and the run's governance is not.** The
-run spends the owner's authority, so its decisions, task writes and claims are the owner's to see and
-answer. Filtering them too (option b) would need a thread link on `decisions`, more schema, and would hide
-from the owner what is done in the owner's name.
-
-Every read an owner or reader session has, and its side of the line:
-
-| Read | Shows | Side |
-|---|---|---|
-| `thread.list`, `thread.messages`, `thread.open` | own threads only, plus shares to the owner from 193b2 | private: other users' threads never appear |
-| `trail` | events, messages, decisions and deliveries by subject | messages filtered (below); decision rows and their events stay visible |
-| `replies` | messages replying to an id | filtered (below) |
-| `messages`, `message.receive`, `message.read` | messages `to_role='human'` (broker.mjs:1931-1936, :1953) | private by construction: a user-thread run can't send to the human (`user-thread-human`, FED 3.6 item 7) |
-| `inbox` | open decisions routed to the human | governance, visible |
-| `decisions {list: roles \| recent}` | decision rows with question, options and recommendation | governance, visible |
-| `agents` | role claims and each held role's state | governance, visible |
-| `tasks`, `state` | tracker tasks and launch state | governance, visible |
-| `credentials`, `usage` | credential state, usage records | governance, visible; neither holds message text |
-| `project.files`, `project.file` | project files, including records a run writes with `record.write` (broker.mjs:1395-1407, :1441-1450) | governance, visible |
-| `project.list`, `names` | projects and instance names | business-wide for the owner, visible |
-
-So a decision a user-thread run raises shows in the owner's `inbox` or `decisions`, with the free text the
-run wrote. Its role claims show in `agents`, its task writes in `tasks`, and a record it writes in
-`project.file`. Any of these can quote the user, and 5.7 doesn't call them private. The users' help text
-(R5) and the Console's share and thread pages say so in one sentence, which FED R6 reuses (mos-1023 item 2,
-duckworth-0012 N21):
-
-> The business owner sees your thread's agent's decisions, inbox entries, claims, tasks and project files,
-> but not your messages.
-
-The gated-raise route. A user-thread run's uncited gated raise or hard wait routes to the human (broker.mjs:1677-1680).
-FED r4.5 (acd5f1f42, B9) settled this with no guard: the tester guard at :1683 (`tester-thread-human`) is not
-copied, and the decision reaches the owner's inbox and no other (sage-1368, mos-1021, mos-1022). FED R3 tests it.
-Row 193 adds nothing here.
-
-The message filter. A message is hidden from a session when it is in a thread (`message_threads`) whose owner
-is a `user:<id>` other than the caller, and `#readable(s, t)` is false. Threads owned by the business human or
-by `tester` are not affected, so row 177's behaviour is unchanged.
-
-- `trail`: drops hidden messages, their `deliveries` rows, and `events` rows whose `subject` is a hidden
-  message id. A `subject` that is itself a hidden message returns `message-not-found`, as an unknown id does,
-  so the reply doesn't confirm the id exists.
-- `replies {id}`: a hidden `id` fails `message-not-found`, and hidden messages are dropped from the result.
-- It applies to every session that can call these verbs: the owner, reader sessions and the tester.
-- It lands in 193b1, with no schema (Duckworth B2). Before 193b2 there are no shares, so `#readable` is false
-  for anyone but the thread's owner and b1 hides every message in another user's thread. 193b2 adds only the
-  share exception. So no build order can put a user thread live without the filter.
-
-What it does not do. The owner holds the store as the instance's OS user and can read it with sqlite. That is
-the same-uid limit in section 6, not a bus path. An owner audit verb, explicit and logged, is a follow-up row
-only if Jason asks for one (sage-1354).
-
-## 6. The bus human boundary (brief point 5)
-
-Row 196 (Gander, #1694, brief `docs/plans/2026-10-20_human-boundary.md` at 96f243faf) owns P19 333 and the
-verifier. Row 193 cites it and designs no boundary of its own (sage-1338: one mechanism).
-
-Agreed with Gander (gander-0002, morgana-0003, gander-0005):
-
-- One bus verifier, `verifyPrincipal(request, connection) -> {kind, business, id}`, kind `owner`, `user` or
-  `tester`. It mints one transient principal per request. It returns no role. The broker reads the level
-  from the live grant on every request, so a grant change acts without a new principal.
-- Gander recommends FED 3.6's shape for users (path-bound `user-cli.mjs`, direct parent the bus tree's
-  `packages/webui/src/cli.mjs serve`) plus kernel peer PID binding, and weighs bus-side ID-token
-  verification as the larger alternative.
-- Correction from Gander, accepted: the tester proof doesn't run the full agent walk, because agents bind
-  tester by design (Q173). Managed runs still fail it. The tester listener moves from TCP 7333 to a private
-  Unix socket, with `bus.tester` unchanged (agreed by Sage with Gander).
-
-What row 193 needs from row 196:
-
-- H1. Owner on the CLI keeps today's proof. Owner in the Console is a `console.sso.subjects` entry.
-- H2. A user principal comes only from an OIDC sign-in, through a path the bus verifies. No CLI path for
-  users.
-- H3. The user binding fails closed on no live grant, an unknown subject, a subject also in
-  `console.sso.subjects`, or a missing or invalid access.json. A broken access.json never stops the owner.
-- H4. Agent processes never get an owner or user principal.
-- H5. Revocation ends a bound user within 30 s and at once on `access.reload`, from the same access state
-  row 193's share check reads.
-
-The same-uid limit. Within one instance, a non-agent process on the instance's uid can claim the owner, and
-can start its own Console copy and claim any granted user (FED 3.6). An unsandboxed same-uid agent that
-detaches from its ancestry can do the same. The walk doesn't stop that, and Gander's design won't claim it
-does (gander-0005). Several humans don't make this worse: a user principal is no stronger than the owner
-principal that the same process could already take. Users themselves are not on the uid. They reach the
-bus only through the Console, so the limit is about local processes, not other humans.
-
-Does row 190 narrow it? Row 190 runs several instances under one uid, so no. Row 190b puts an instance (the
-hub) under its own Linux user (mos-0986). That narrows reach across instances: another instance's uid fails
-the uid check (human.mjs:67) and can't read the hub's store or access.json. It does not narrow reach within
-one instance. Private threads are private from other humans using the bus, not from processes running as
-the instance's uid.
-
-## 7. Migration and rollback (brief point 6)
-
-- No access.json: the business has exactly its owner, every verb behaves as today, and the share verbs
-  work for the owner only (target `*` or none). A broken access.json revokes users and leaves the owner.
-- Existing threads: already owned by the business human. Nothing is rewritten.
-- Schema: 3i to 3j adds `thread_shares` only. A re-pin past a schema bump needs a `--migrate` window with
-  Jason, and row 185's backup before activate covers it.
-- Rollback before any share is written: activate the previous copy with the store restored from the
-  pre-activate backup. A 3i copy refuses a 3j store, as it does for every bump.
-- Rollback after shares are written: the same restore loses shares made since the window. Grants are in
-  access.json and survive. Users re-share. Row 181's restore guard counts `thread_shares`, so the loss is
-  shown, not silent.
-- To keep that window small, the build splits (section 9): 193a, 193b1, 193c and 193d have no schema
-  change and can go live in any window. 193b2 carries 3j.
-
-## 8. Tests and mutants
-
-Bus, each in `packages/bus/tests/` (193b1: viewer, mixed grants, board reads, the 5.7 message filter and governance pin; 193b2: shares, the share exception to the filter, migration):
-
-- Viewer: each allowed verb works, every other verb refuses `access-refused`, including `thread.create`,
-  `thread.open`, `thread.send` and `thread.share`.
-- Mixed grants: collaborator on project A and viewer on B. Create in A works, create in B refuses.
-- Downgrade: not here. FED R4 owns the level-loss test and its mutant (r4.4, mos-1020, N3).
-- Shares: owner shares with `user:<id>`, the user reads `thread.messages` and gets `thread-not-owned` on
-  `thread.send` and `thread.open`. Share with `*` reaches every covered user and the owner. Share with a user
-  whose grant doesn't cover the project or instance refuses `share-not-covered`.
-- A share never widens: the target's grant drops the project, the next read refuses.
-- Revoke, expiry and an invalid file each end share reads on the next request. The 30 s timer and
-  `access.reload` paths each have a case.
-- A revoked thread owner hides the thread from sharees.
-- Unshare ends access. Share, unshare, share again leaves it shared (latest row wins).
-- Non-owner `thread.share`, `thread.unshare`, `thread.shares` refuse. Tester refuses on all three.
-- `thread.list` plain shape unchanged. `thread.list {shared: true}` returns only readable threads.
-- Board reads refuse users and viewers.
-- Governance pin (B1, sage-1368): a user-thread run raises a decision; it shows in the owner's
-  `decisions recent` with its question text, and `inbox` lists it when routed to the human; the run's
-  role claim shows in the owner's `agents`, its task write in `tasks`, and its `record.write` in
-  `project.file` (B3, sage-1373); the user's message bodies stay hidden from the owner's `trail` and
-  `replies`. The test names each item of the 5.7 user sentence, so the sentence and the pin match.
-- `trail`, for the owner, a reader session and the tester (193b1): a user's thread message as `subject`
-  fails `message-not-found`; a decision trail that reaches such a message omits it, its deliveries and its
-  events. Once the thread is shared with the owner, the owner's trail shows it.
-- `replies`, same three sessions (193b1): a hidden `id` fails `message-not-found`; hidden replies are dropped. The
-  owner's own and the tester's threads are unchanged.
-- Migration: a 3i store with threads migrates to 3j, row counts unchanged, `thread_shares` empty and
-  append-only (update, delete, replace each abort). Restore-guard and `COUNTED` include it.
-
-Business (193a): R1 accepts `viewer`, refuses any other new level.
-
-CLI (193c): `mosaic access user add/remove` and `grant --level viewer` refuse tester and agent callers,
-write a receipt line and call `access.reload`.
-
-Webui (193d): a viewer has no composer or share control. With each UI check removed, the bus still refuses.
-
-Mutants, each must be killed:
-
-1. `#readable` rule 1 dropped (any covered user reads any thread).
-2. Rule 2 dropped (a share widens the grant).
-3. Rule 3 dropped (a revoked owner's thread stays visible).
-4. Latest-row lookup replaced by "any share row" (unshare ignored).
-5. (Moved to FED R4, N3: the level-loss mutant is R4's.)
-6. Viewer allowed `thread.send`.
-7. `#threadRead` used for `thread.send` (sharee writes).
-8. `share-not-covered` check removed.
-9. `thread.share` owner check removed (sharee re-shares).
-10. A user allowed `trail`.
-11. The `trail` filter removed (the owner reads a user's unshared message by id).
-12. The `replies` filter removed (the owner reads replies in a user's unshared thread).
-
-## 9. Build rows and order
-
-| Row | Work | Chains on | Schema |
-|---|---|---|---|
-| 193a | R1 level check widened to viewer | FED R1 candidate | none |
-| 193b1 | Bus: viewer verb list, per-grant level checks, users refused on board reads, the 5.7 `trail` and `replies` filter with `#readable` as owner-only | FED R3, R4 candidates, row 196 verifier | none |
-| 193b2 | Bus: `thread_shares`, share verbs, the share rules of `#readable`, `#threadRead`, the 5.5 share filters | 193b1 candidate | 3j |
-| 193c | `mosaic access` user verbs and `--level viewer`, if R5 lacks them | FED R5 candidate | none |
-| 193d | Console: shared list, share controls, viewer read-only | FED R6, row 192 candidates, 193b2 for share controls | none |
-
-Sage ruled the split (sage-1354): 193b1 has no schema change and can go live first. 193b2 carries 3j, and
-Sage takes its migrate window to Mos when 193b2 is near. The 5.7 message filter is in 193b1 (Duckworth B2,
-sage-1368), so it is live before any user thread can be, whatever order FED R8 and 193b2 land in. 193b2 adds
-only the share exception. FED R4 chains on 193a (viewer level), and 193b1 chains on R4.
-
-Coverage, settled in FED r4.1 (73677b87d, gizmoduck-0018, still under Duckworth's review). A grant's
-`projects` is `["*"]` or bus project UUIDs (`projects.id`, broker.mjs:2306; `threads.project` references it).
-R1 exports one pure `covers(grant, {business, project, instance}, now, {level})`. Row 193 uses only that
-function and adds no second one (Sage confirmed, sage-1354):
-
-- share reads (5.4 rules 2 and 3) and `share-not-covered`: `covers(g, thread, now, {})`, any level;
-- `thread.create`, `thread.open`, `thread.send`, `thread.share`: `covers(g, thread, now, {level: 'collaborator'})`;
-- `project.list` and `names` for users: any level, as FED 3.5.
-
-`covers` needs no further argument for row 193. If r4.1 changes in review, 193b1 follows it.
-
-Follow-ups, not in this row:
-
-- A read-only users and grants page for the owner in the Console.
-- A second owner or admin level, if Jason wants one.
-- An explicit, logged owner audit verb for user threads, only if Jason asks for one (sage-1354).
-
-## 10. Gate
-
-Per the brief: Duckworth approves this design, then the manifest. The bus, business, cli and webui suites and
-every `scripts/test-*.sh` pass on Sage's gate, and the section 8 mutants are killed. No test touches the live
-directories. No product code before Duckworth approves.

agents/morgana/work/queue-213/BUILD.md

@@ -0,0 +1,252 @@
+# Row 213 (C2-08) build: creative roles, persona file and block, M1, M2, M6, M10, prompt by file
+
+Morgana (Opus 5.5), 2026-10-20. Queue row 213, Gitea #1714. Brief: `docs/plans/2026-10-20_case2-rows.md`
+§ C2-08 (on `refactor` from 32b54ac3b). Design: Gosalyn's Case 2 design r10, sections 4 and 5.
+Reviewer Webby, gate owner Sage. Base: `base.txt` (088087ac9). Manifest: `candidate-manifest.sha256`.
+D1 and D2 approved as deviations in sage-1492.
+
+## What it is
+
+1. **Six creative roles** (`roles/<name>.json` and `.md`, roleVersion 2): companion and research get
+   read and web, with network api-only. ideas, proofreader, fact-checker and continuity get read only, with
+   network none. All six get withinRole `["message.send"]`, no credentials, and messaging that sends to and
+   receives from `human` only. `vocabulary.mjs` names them in `CREATIVE_DEFINITIONS`, plus `CREATIVE_KINDS`,
+   `CREATIVE_TOOLS` and `THREAD_DEFINITIONS`. `END_PROTECTED` becomes `THREAD_DEFINITIONS`.
+2. **M1** (`role.mjs` `checkCreative`): a creative role file is refused if it names a tool outside
+   `CREATIVE_TOOLS`, holds any authority but withinRole `message.send`, lacks `messaging`, names anyone but
+   `human` in messaging, or is version 1.
+3. **M2**: since the role files name no write, edit or bash tool, the existing gate refuses write, edit and
+   bash on pi and Write, Edit and Bash on claude-code for each creative role. No gate code changed. The
+   test pins it.
+4. **M6**: `tools.mjs` leaves `raise_decision` out for a creative definition. `broker.mjs` refuses
+   `decision.raise` from a creative session with `decision-not-allowed`, after `#secretCheck` and before
+   the spec-cited path, so a cited raise is refused too.
+5. **M10**: a creative instance belongs to the human.
+   - `launch-settings.mjs` `creativeHumanOnly` gives `organization-creative-human-only` to any other actor.
+     It covers: a `models` key that a creative instance's `model` or `fallback.model` var names (changed or
+     removed), `setRoutes` for the instance, and the `instances` key. The `instances` key is refused for
+     every actor with `organization-creative-instance`, because the model changes through `instances.set`
+     or `routes.set`.
+   - `instance-settings.mjs`: add, change and redefine to or from a creative definition are the human's.
+     A creative definition is `END_PROTECTED`, so the new `closed()` lets this writer still add and change
+     one. `accepted` and `protected` use `closed()` too, so the human's Console form offers the creative
+     definitions and marks those instances as editable.
+6. **Persona** (design 4): vars `persona.name` (one line, max 40) and `persona.sha256` (64 lowercase hex),
+   agent layer. The file lives at `<configDir>/personas/<business>/<instance>.md`.
+   - `bundle.mjs` `readPersona` opens it with O_NOFOLLOW and refuses with `persona-invalid` when the file
+     is missing, a symlink, not a regular file, owned by another uid, carries group or other mode bits, is
+     over 8000 characters, is not UTF-8, or holds `</persona-file>` or a line starting `# ` or `## `.
+   - It refuses with `persona-mismatch` when the bytes don't match the digest.
+   - A file present with no `persona.sha256` var is ignored. A digest with no `personaDir` refuses.
+   - The block sits between the contract and `## This session`, wrapped in
+     `<persona-file instance=... sha256=...>`.
+7. **Web**: `webPlan` refuses `web-source-not-allowed` when a creative definition is on
+   `harness-builtin`, so every creative fetch goes through the broker.
+8. **Prompt by file**: claude passes `--system-prompt-file <path>`, and pi passes `--system-prompt <path>`.
+   Both make the path absolute. The prompt text no longer appears in `/proc/<pid>/cmdline`.
+   `adapters/README.md` says so.
+
+## Refusal codes
+
+`persona-invalid`, `persona-mismatch`, `web-source-not-allowed`, `organization-creative-human-only` and
+`organization-creative-instance` are new. `decision-not-allowed` is named in the brief but is also new in
+code. My morgana-0021 message called it an existing code, which was wrong.
+
+## Deviations (sage-1492)
+
+- **D1** `packages/business/src/business.mjs`: `checkPersonaVars`, plus one call line at the end of
+  `checkRoles`'s per-instance block. The persona vars are accepted only on an instance of a creative
+  definition, and only both together. Without D1, any instance's agent layer could carry a persona
+  digest, and the bundle would read a persona file for a pm or chief.
+  Test: `business.test.mjs` "persona vars: agent layer, creative definition only, both or neither". It
+  covers the business layer, pm and chief, one key alone and malformed values. `instance-settings.test.mjs`
+  also covers it: changing a persona-carrying companion to security-reviewer is refused.
+  Mutants: D1a, D1b, D1c.
+- **D2** `packages/cli/src/launcher.mjs`: one line, `personaDir: join(configDir(env), "personas"),` in the
+  `buildBundle` call. Without it a creative instance with a persona can never launch.
+  Test: `launcher.test.mjs` "row 213 a creative instance's persona is read from <configDir>/personas: off
+  its digest the launch fails with the mismatch as its reason". Mutant: D2.
+
+- **Adapter tests' file** (webby-0040 N1). Brief line 68 puts the adapter tests in `claude-session.test.mjs`
+  and `pi-session.test.mjs`. They are in `harness/tests/creative.test.mjs` instead, next to the other row 213
+  harness tests, so the row's adapter cases sit in one file and the two session test files stay unchanged.
+  Same cases: argv holds the absolute prompt path and no marker, and pi refuses a missing, unreadable or
+  directory prompt.
+
+The checkRoles change sits in its own block and the launcher change is one line, so the rebase over rows
+194 and 199 (both touch `business.mjs`, and 199 touches `launcher.mjs`) stays small.
+
+## Pinned-test edits and the pi tightening (sage-1492, named here)
+
+1. `packages/bus/tests/project-runtime.test.mjs:26`: the pinned broker import line gains
+   `CREATIVE_DEFINITIONS` (M6 reads it).
+2. `packages/harness/tests/skills.test.mjs:170`: the test checked the prompt text in argv after
+   `--system-prompt`. Each adapter now passes a path, so the test looks up the flag for each harness,
+   checks that the next argument is the bundle's prompt file, and reads the MARKED and chief checks from
+   that file.
+3. `adapters/pi/adapter.sh`: `[ -f "$PROMPT_FILE" ] && [ -r "$PROMPT_FILE" ]`, exit 2 otherwise. Pi 0.85.1
+   uses the path string as the prompt when it can't read the file. Test: `harness/tests/creative.test.mjs`
+   "pi refuses a missing, unreadable or directory prompt" (pi never runs). Mutant: A1.
+
+One more pinned assertion changed: `business/tests/assistant.test.mjs` REQ-HARN-2 expected only the
+assistant to hold `web`. Companion and research now hold it too.
+
+## Files
+
+Source: `packages/business/src/{vocabulary,role,vars,business,launch-settings,instance-settings}.mjs`,
+`packages/harness/src/{bundle,tools}.mjs`, `packages/bus/src/broker.mjs`, `packages/cli/src/launcher.mjs`,
+`adapters/{pi,claude}/adapter.sh`, `adapters/README.md`, `roles/{companion,research,ideas,proofreader,
+fact-checker,continuity}.{json,md}`.
+
+Tests changed: `business/tests/{role,business,launch-settings,instance-settings,assistant}.test.mjs`,
+`harness/tests/skills.test.mjs`, `bus/tests/project-runtime.test.mjs`, `cli/tests/launcher.test.mjs`.
+New: `harness/tests/creative.test.mjs` (7), `bus/tests/creative.test.mjs` (3).
+
+I grepped `packages/*/tests` and `scripts/` for each changed source path next to a 64-hex string. The hits
+are `thread-migration.test.mjs` (a DDL digest, not a pin on `broker.mjs`; 3/3 pass) and discord's own
+`tools.mjs`. No test pins a changed file.
+
+## Evidence
+
+Each file alone from its package with `node --test --test-reporter=tap <file>`, 2026-10-20, all fail 0:
+
+- Touched: business role 17, business 17, launch-settings 16, instance-settings 12, assistant 11; harness
+  creative 7, skills 10, bundle 22; bus creative 3, project-runtime 3; cli launcher 30. Round 2 reran
+  bus creative, instance-settings, business, launch-settings, role, harness creative and bundle, bus
+  tester-writes 8 and chief-of-staff 18, and the vars readers business vars 7, discord context 7 and git 12.
+- Other files that read a changed path: business hard-waits, record-grants, token-limit-settings,
+  workflow-roles, chief-of-staff, project-repo, plugin-settings; harness bundle 22, tools 22,
+  claude-session 8, pi-session 8, raise-domain, spec-tools, claude-gate, mcp-server, gate, runner 34,
+  git-tools; bus hard-waits, launch-notice, tester-writes, business, broker 16, workflow-roles, web 19,
+  task-page, thread-migration 3; discord git, web, setspark, engine, tools; plugins harness, loader; seat
+  working, sandbox, session; cli launch-limit-checks, limits, git-socket, launch-account, thread-launch,
+  launch-limits, launch-routes, instances, stack-copy, stack-release 174; webui limits-browser, editor,
+  settings-form, tester-browser.
+
+Suites, `scripts/test-*.sh` and the mutants are not run yet. They need Sage's slot.
+
+Drift: `git diff --stat 088087ac9 305857c8f` over the 35 manifest paths is empty (2026-10-20, sage-1501).
+Row 192's async `scripts/mosaic-config.mjs` and `webui-service.sh` are outside the manifest. The broker's
+new import comes from `vocabulary.mjs`, which it already imported, so `RUNNER_FILES` doesn't change.
+
+Mutants: `mutants.py` in this directory, 31 mutants over 11 files. It backs up each file to scratch first,
+aborts on a bad backup or any anchor count other than one (all 31 checked as unique without editing), runs
+the named test files per mutant, restores each file after its mutant and again in `finally`. Log:
+`mutants.log`, written on the run. The brief's `models` mutant is L1.
+
+| Mutant | File | Tests |
+|---|---|---|
+| D1a/b/c persona vars check (D1) | business.mjs | business, instance-settings |
+| D2 no personaDir (D2) | launcher.mjs | launcher |
+| L1 models key by anyone (the `models` mutant) | launch-settings.mjs | launch-settings |
+| L2 fallback.model not checked | launch-settings.mjs | launch-settings |
+| L3 instances key allowed | launch-settings.mjs | launch-settings |
+| L4 setRoutes by anyone | launch-settings.mjs | launch-settings |
+| L5 creativeHumanOnly never refuses | launch-settings.mjs | launch-settings, instance-settings |
+| I1/I2/I3 add, change, redefine by anyone | instance-settings.mjs | instance-settings |
+| R1/R2/R3 checkCreative off, wider tools, non-human messaging | role.mjs | role |
+| B1-B8 mode bits, digest, headings, symlink, char cap, block, no dir, builtin web | bundle.mjs | harness creative |
+| T1 raise_decision offered | tools.mjs | harness creative |
+| K1 broker raise check off | broker.mjs | bus creative |
+| K2/K3 chief or tester session reaches the writer as the human (round 2, B1) | broker.mjs | bus creative |
+| V1 persona.name line separators accepted (round 2, N3) | vars.mjs | business |
+| A1 pi without -f; A2/A3 relative path kept | adapters | harness creative, skills |
+
+## Residuals
+
+- `ID_PATTERN` allows dots, so a human id could read like `<definition>.<instance>`. That is only cosmetic:
+  `creativeHumanOnly` compares the actor with `document.human`.
+- TOCTOU between pi's `[ -f ] && [ -r ]` and pi's own read of the bundle's prompt file.
+- The other-uid owner check in `readPersona` can't be tested without root.
+- O_NOFOLLOW covers only the last path component, so a symlinked `personas/` or `personas/<business>/` is
+  followed (webby-0040 N2). The digest still refuses any bytes but the pinned ones. A comment in
+  `bundle.mjs` says so.
+- The claude adapter checks the prompt file with `[ -r ]` only, and pi checks `-f` and `-r`. The brief asks
+  for pi's check (webby-0040 N4).
+- **Launch-failed mapping.** A BundleError thrown from `buildBundle` inside `start()` becomes the Refusal
+  `launch-failed`, with the code's message in the log's `why`. That holds for the persona codes and for
+  webPlan's `web-source-not-allowed`. By then the run dir `launches/<business>/<run>/` exists with only
+  `session/`, and no bundle is written. Only `check()`'s readSkills preflight surfaces bundle codes. The
+  D2 test pins both facts. I kept the launcher change to one line, as sage-1492 asked.
+
+## Follow-ups (not in this row)
+
+- A persona preflight in launcher `check()`, so a bad persona refuses with its own code before a run dir
+  exists. Sage agreed it as a follow-up (sage-1501) and files it after this row lands.
+- The webui `bus.mjs` code-to-HTTP map lacks the new codes.
+- webby-0053 N1: `checkCreative` doesn't refuse `credentials`, so a later role-file commit could give a
+  creative instance a gitea credential. All six creative role files have `credentials: []` today. A
+  one-line refusal and a `role.test.mjs` case close it.
+- The cli `instances.mjs` message wording for the creative refusals.
+
+## Round 2 (webby-0040, round 1 CHANGES on bb5f4600)
+
+- **B1**: `bus/tests/creative.test.mjs` adds "M10 through the broker". It runs on a real organization file
+  and writer behind `startBroker`, with a claimed chief session, a bound tester session and the human.
+  - The chief's `organization.set` of bean's `launch.models` key is refused with
+    `organization-creative-human-only`. Its `instances` key is refused with `organization-creative-instance`.
+  - The tester's `organization.set` and `limits.set` are refused `tester-refused` (N5: the broker refuses
+    first). Its `instances.set` (change bean, add an ideas instance) and `routes.set` for bean reach the
+    writer as `tester` and are refused with `organization-creative-human-only`.
+  - The file bytes are unchanged and no committed log entry exists after all of these.
+  - The human's `limits.set` of the same change lands, and the one committed entry names `jason`.
+  - Mutants K2 and K3 change the broker's actor naming for a role or tester session.
+- **B2**: `instance-settings.test.mjs` asserts the mode of `writer.logFile("acme")` (0600) and that it sits
+  in the history dir. It lives at `.history/acme/changes.jsonl`, so the round 1 loop over that dir already
+  covered it, but no line named it.
+- **N1**: listed under Deviations. **N2**: comment and residual. **N3**: `persona.name` now refuses U+2028
+  and U+2029, with two values added to the business test and mutant V1. **N4**: noted under residuals.
+
+- Drift: `git diff --stat 088087ac9 f41729178` over the 35 manifest paths is empty. Round 2 manifest
+  digest b5ff0ac0e754cb1e5891417f4ab1da9597f5cf49fb2fe2d5f0fbf066f821c43a.
+
+## Round 3 (sage-1715): rebase onto 9b5362018
+
+Rows 199 (cb5fdb064), 237 (d7d943199) and 210 (f5753c0e8) landed on six manifest paths after the round 2
+approval. Round 3 rebases the three commits onto origin/refactor 9b5362018 on a new branch,
+`morgana/row213-r3`. The round 2 branch stays as it was. Nothing else changed.
+
+- Five files conflicted. Each resolution keeps both sides:
+  - `bus/src/broker.mjs` and `bus/tests/project-runtime.test.mjs`: the vocabulary import keeps rows 199
+    and 210's names (forkProblem, forkUrl, credentialKind, validArgv, commandAllowed) and adds
+    CREATIVE_DEFINITIONS last. The pinned import line in the test carries the same list. RUNNER_FILES
+    is unchanged, since the import is still the vocabulary file only.
+  - `business/src/business.mjs`: one vocabulary import with row 199's names plus CREATIVE_DEFINITIONS.
+    The `checkRoles(roles, file, rolesDir, business, hosts)` signature is row 199's. `checkPersonaVars`
+    runs after row 199's identity and publish checks.
+  - `business/src/role.mjs`: the import keeps row 210's HOST_SERVICE and adds CREATIVE_DEFINITIONS and
+    CREATIVE_TOOLS.
+  - `business/src/vocabulary.mjs`: the creative constants and `END_PROTECTED = THREAD_DEFINITIONS` come
+    before row 199's Gitea URL parse, which is kept whole.
+- `cli/src/launcher.mjs` merged without a conflict.
+- `git range-diff 088087ac9..aee32d185 9b5362018..morgana/row213-r3`: commits 2 and 3 are `=`. Commit 1
+  differs only in the conflict hunks above.
+- None of the new base's added lines name END_PROTECTED, THREAD_DEFINITION, CREATIVE_* or the creative
+  refusal codes, apart from docs. All 31 mutant anchors still count 1. The hash-pin grep finds no
+  64-hex pin on a manifest path.
+- The manifest is rebuilt from the round 3 tree. It has the same 35 paths, and six digests changed: the
+  six drifted files. `base.txt` is 9b5362018.
+- Singles of every touched test file, plus the seat sandbox and bus project-runtime tests (RUNNER_FILES
+  rule), wait on Sage's slot. They are recorded here when run.
+
+## Round 4 (sage-1778, mos-1160): one commit on row 234's landing c771a36f4
+
+Row 234 landed as c771a36f4 after the round 3 approval (webby-0053). Round 4 is one commit on c771a36f4,
+on the new branch `morgana/row213-r4`. It is the round 3 change applied onto the landed blobs. The round 3
+branch stays as it was.
+
+- Overlap, `git diff --name-only 9b5362018 c771a36f4` against the round 3 paths: `business/src/business.mjs`,
+  `bus/src/broker.mjs` and `bus/tests/project-runtime.test.mjs`. Each starts from the landed blob, and the
+  row 213 edits are merged by hand. No landed hunk is reverted (sage-1760).
+  - `broker.mjs` and the pinned `project-runtime` import line: row 234's list with `HOST_ID`, then
+    `CREATIVE_DEFINITIONS`. The test keeps both rows' comments. The import still names only
+    `vocabulary.mjs`, so RUNNER_FILES is unchanged.
+  - `business.mjs`: row 234's import (no `HOST_PREFIX`, no `hosts.mjs`) plus `CREATIVE_DEFINITIONS`.
+    `checkPersonaVars` sits before row 234's `HOSTS_MOVED` and its four-argument `checkRoles`, and still
+    runs after the identity and publish checks.
+- Check: the removed and added non-packet lines of `diff c771a36f4..r4` and `diff 9b5362018..2d2ad2760`
+  differ only in those three import lines. All 31 mutant anchors count 1.
+- Row 234's hosts verbs: `#hostsCaller` admits the human, the tester or the chief definition
+  (`grant-chief-only`), so a creative role can't reach them and M1 stays as narrow.
+- The manifest has the same 35 paths. The three overlap files changed digest. `base.txt` is c771a36f4.
+- Singles and the 31 mutants wait on Sage's slot. They are recorded here when run.

agents/morgana/work/queue-213/base.txt

@@ -0,0 +1 @@
+c771a36f4bd0b6c359282425c668996a90072f93

agents/morgana/work/queue-213/candidate-manifest.sha256

@@ -0,0 +1,35 @@
+37cc5d74636465c592c9eb8f3d9b66c2632299be922444737b32d3d3be43c239  adapters/claude/adapter.sh
+1e0487ab682ff97e974a9fed4765994f70ee362058bd0aa6aee32c2a7891e0d2  adapters/pi/adapter.sh
+2cb62d90f4f52f17ca606e57d4714b872520d0224cd94fd116308becee864b71  adapters/README.md
+ee5521840784d9ff3603c22cc6b5f090ac062e8575946a071972fedc089724d1  packages/business/src/business.mjs
+a93b4efe213750b35730d6391594f3e26ffe667040a5d7baf5262b83341164b1  packages/business/src/instance-settings.mjs
+3e957579bcfdf5f88e60f7235b7ead4fb27cb455e34b7588f4e22b8ab5542bec  packages/business/src/launch-settings.mjs
+6b84018c202ff08e59b4e946556703d199fe75ef97e9e6ac4a390c89705ac796  packages/business/src/role.mjs
+f6b15ee8dad2d985c0ae66b1f106ca46cb56ec86ac8cd5dec8a05c887596a421  packages/business/src/vars.mjs
+814ba93ca7403ad77ea2e7fb7bc21c2b40846bf8a3c2eae53b32446278af061c  packages/business/src/vocabulary.mjs
+b67917c5c7bb270b82f1cbd97071a195b79a57c9a343acbc5feae2a877fb9e8f  packages/business/tests/assistant.test.mjs
+b4606af3288624475e23ca506f7dea084a1e606efce4b1556d132b03230c2be1  packages/business/tests/business.test.mjs
+2b80070db1e1d72b82a32cec75711c59a9383188b5a659854fd0ba8ae2dc0f5b  packages/business/tests/instance-settings.test.mjs
+647b4835836566070c7b859b2bbcaf3fd748030fe88c8f20e990f5038ec65e88  packages/business/tests/launch-settings.test.mjs
+0c9f082d8c05582382dc646c74aa60a46b89804717f828db9fadde51f2e258a8  packages/business/tests/role.test.mjs
+15f530d49eaf25167113f84b743d7057c17a273e56731d8937bad26196325bfc  packages/bus/src/broker.mjs
+21946cdecab263ae65791977eb4599594340c8e049b3c216e3181610638f0952  packages/bus/tests/creative.test.mjs
+4b1c6688beba124492cf130247a2ff93fdd6d18594990cde84709139964d0b5b  packages/bus/tests/project-runtime.test.mjs
+a968a19d1b32416aecb2488c7fb9768db7d5160374f1b790166380d41acea894  packages/cli/src/launcher.mjs
+7933f256e5f097999ff36cc7e48b0c417385c6c3727919f38437bd501aecc438  packages/cli/tests/launcher.test.mjs
+2c1aad8d8be1a03be12eca93b4da36c656236ad38d09bfdc314e42a68240afc3  packages/harness/src/bundle.mjs
+22f9e3c1dce25e5eb6713306ccdf22dc77a4ccf0c99e9186f2e16602f58aeb49  packages/harness/src/tools.mjs
+305be35111c432a663d5671a4dac9bfe5bbb1a9b34ace77087e12c6f687602a1  packages/harness/tests/creative.test.mjs
+3d68294493e41db3b647cd71cd94436c28fc531c64a8b1589be7644c3bf59f94  packages/harness/tests/skills.test.mjs
+9425a319ec8966712fc38027bc62f7fbf52a216e30b9520cbd877386990c92d6  roles/companion.json
+2533b3ec4dfa78cd81b254c167865b984a6edf6b00454911363012ab5ac1e4c1  roles/companion.md
+cb2512590330efe4514c88eb31d09e3e3b159943803e462a224b77010c249de7  roles/continuity.json
+193c82fa803a85ee4c4b2f946ce2d69e94a192c00c5093d4db91cc274a5d11ed  roles/continuity.md
+7a59218d903b26174c51f0118a347b0b14e187e2d0c229ca43c98dad357f3435  roles/fact-checker.json
+8895fbe1d7961bbb98b272cd888250d6ef44f74986948032719b44dc3dc56579  roles/fact-checker.md
+3a932eefe3af967d046d5e241d59f5b2700bd5ad4ef236d6a937011500200b5f  roles/ideas.json
+8ce05e198cefb29f2aea53a25a2cd6599782b34c7a0815a2b6d26272c0fdae50  roles/ideas.md
+cb117d44e48f288048a4e697ee237b445b8fcea21bb95f9723e91b17ab542a3f  roles/proofreader.json
+a2214ab481ef27d24c20da9e5e7bbc86c6ea769cacc8a163330813e75a20ec15  roles/proofreader.md
+95f5fc2bd2a0593177c21ca1898317c671ad04334e5c561c29917fe2ceae2c51  roles/research.json
+7a602b0efe44669028e52fc6aca83f00bd3dd32a105d0729538f2ed357f6ecd3  roles/research.md

agents/morgana/work/queue-213/mutants.py

@@ -0,0 +1,91 @@
+#!/usr/bin/env python3
+# Row 213 (C2-08) mutants across the changed sources. Run from the row213 worktree root, in Sage's slot.
+# Each mutant changes one anchor (count must be 1), runs the named test files alone, then restores.
+import os, shutil, subprocess, sys
+BAK = "/mnt/storage/scratch/morgana-r213/mutant-backups"  # any scratch path outside the tree
+BIZ = "packages/business/src/business.mjs"
+LS = "packages/business/src/launch-settings.mjs"
+IS = "packages/business/src/instance-settings.mjs"
+ROLE = "packages/business/src/role.mjs"
+BUNDLE = "packages/harness/src/bundle.mjs"
+TOOLS = "packages/harness/src/tools.mjs"
+BROKER = "packages/bus/src/broker.mjs"
+LAUNCHER = "packages/cli/src/launcher.mjs"
+PI = "adapters/pi/adapter.sh"
+CLAUDE = "adapters/claude/adapter.sh"
+T_BIZ = [("business", "tests/business.test.mjs")]
+T_LS = [("business", "tests/launch-settings.test.mjs")]
+T_IS = [("business", "tests/instance-settings.test.mjs")]
+T_ROLE = [("business", "tests/role.test.mjs")]
+T_HC = [("harness", "tests/creative.test.mjs")]
+T_BUS = [("bus", "tests/creative.test.mjs")]
+T_LAUNCH = [("cli", "tests/launcher.test.mjs")]
+T_ADAPT = [("harness", "tests/creative.test.mjs"), ("harness", "tests/skills.test.mjs")]
+ABS = '    *) PROMPT_FILE="$(pwd)/$PROMPT_FILE" ;;'
+MUTANTS = [
+  # D1 (deviation): persona vars only on a creative definition, both or neither.
+  ("D1a persona vars check not called", BIZ, "    checkPersonaVars(out[instance].vars, entry.definition, at);\n", "", T_BIZ + T_IS),
+  ("D1b any definition may carry persona vars", BIZ, "  if (!CREATIVE_DEFINITIONS.includes(definition)) refuse(", "  if (false) refuse(", T_BIZ + T_IS),
+  ("D1c one persona var alone accepted", BIZ, "  if (set.length === 1) refuse(", "  if (false) refuse(", T_BIZ),
+  # D2 (deviation): the launcher hands buildBundle the persona directory.
+  ("D2 launcher passes no persona directory", LAUNCHER, '      personaDir: join(configDir(env), "personas"),', "      personaDir: null,", T_LAUNCH),
+  # M10: the human's settings.
+  ("L1 models-key change by anyone", LS, "          if (was !== is) creativeHumanOnly(", "          if (false) creativeHumanOnly(", T_LS),
+  ("L2 fallback.model key not checked", LS, '        for (const key of [vars.model, vars["fallback.model"]]) {', "        for (const key of [vars.model]) {", T_LS),
+  ("L3 instances key allowed for a creative instance", LS, "        if (CREATIVE_DEFINITIONS.includes(next.roles[instance].definition)) {\n          throw new OrganizationError(\"organization-creative-instance\"", "        if (false) {\n          throw new OrganizationError(\"organization-creative-instance\"", T_LS),
+  ("L4 setRoutes by anyone", LS, "      creativeHumanOnly(old.document, actor, instance, next.roles[instance].definition);", "", T_LS),
+  ("L5 creativeHumanOnly never refuses", LS, "  if (CREATIVE_DEFINITIONS.includes(definition) && actor !== document.human) {", "  if (false) {", T_LS + T_IS),
+  ("I1 add of a creative instance by anyone", IS, "      creativeHumanOnly(old, actor, instance, args.definition);\n      definitionFor(rolesDir, args.definition);\n      next.roles[instance] =", "      definitionFor(rolesDir, args.definition);\n      next.roles[instance] =", T_IS),
+  ("I2 change of a creative instance by anyone", IS, "      creativeHumanOnly(old, actor, instance, entry.definition);\n", "", T_IS),
+  ("I3 redefine to creative by anyone", IS, "        creativeHumanOnly(old, actor, instance, args.definition);\n", "", T_IS),
+  # M1: role files.
+  ("R1 checkCreative not called", ROLE, "CREATIVE_DEFINITIONS.includes(role.name) ? checkCreative(role) : role", "role", T_ROLE),
+  ("R2 wider tools accepted", ROLE, "  if (wider.length > 0) refuse(", "  if (false) refuse(", T_ROLE),
+  ("R3 non-human messaging accepted", ROLE, '    if (role.messaging[key].some((entry) => entry !== "human")) {', "    if (false) {", T_ROLE),
+  # Persona file and block.
+  ("B1 group/other mode bits accepted", BUNDLE, "    if (stat.mode & 0o077) throw", "    if (false) throw", T_HC),
+  ("B2 digest not checked", BUNDLE, "  if (sha256(data) !== digest) {", "  if (false) {", T_HC),
+  ("B3 headings and end tag accepted", BUNDLE, "  if (text.includes(PERSONA_END) || /^##? /m.test(text)) {", "  if (false) {", T_HC),
+  ("B4 symlink followed", BUNDLE, "constants.O_RDONLY | constants.O_NOFOLLOW | constants.O_NONBLOCK", "constants.O_RDONLY | constants.O_NONBLOCK", T_HC),
+  ("B5 character cap off", BUNDLE, "  if ([...text].length > PERSONA_CHARS) throw", "  if (false) throw", T_HC),
+  ("B6 persona block dropped", BUNDLE, "    ...personaSection(resolved, persona),\n", "", T_HC),
+  ("B7 no personaDir with a digest accepted", BUNDLE, "    if (digest === undefined) return null;\n    throw new BundleError(", "    return null;\n    throw new BundleError(", T_HC),
+  ("B8 creative role on harness-builtin web", BUNDLE, '  if (granted && source === "harness-builtin" && CREATIVE_DEFINITIONS.includes(resolved.definition)) {', "  if (false) {", T_HC),
+  # M6.
+  ("T1 raise_decision offered to creative roles", TOOLS, '  if (!CREATIVE_DEFINITIONS.includes(resolved.definition)) add("raise_decision"', '  add("raise_decision"', T_HC),
+  ("K1 broker creative raise check off", BROKER, "      if (request.verb === 'decision.raise' && !s.human && !s.tester &&\n          CREATIVE_DEFINITIONS", "      if (false &&\n          CREATIVE_DEFINITIONS", T_BUS),
+  # B1 (webby-0040): the broker names the writer's actor from the session.
+  ("K2 chief session reaches the writer as the human", BROKER, 'actor = this.#business(s.business).roles[s.role].definition + "." + s.role;', 'actor = "jason";', T_BUS),
+  ("K3 tester session reaches the writer as the human", BROKER, 'let actor = s.tester ? "tester" : s.human;', 'let actor = s.tester ? "jason" : s.human;', T_BUS),
+  ("V1 persona.name line separators accepted (N3)", "packages/business/src/vars.mjs", "\\u007f\\u2028\\u2029]", "\\u007f]", T_BIZ),
+  # Prompt by file (adapters).
+  ("A1 pi prompt check without -f", PI, '[ -f "$PROMPT_FILE" ] && [ -r "$PROMPT_FILE" ] ||', '[ -r "$PROMPT_FILE" ] ||', T_ADAPT),
+  ("A2 pi relative prompt path kept", PI, ABS, "    *) ;;", T_ADAPT),
+  ("A3 claude relative prompt path kept", CLAUDE, ABS, "    *) ;;", T_ADAPT),
+]
+os.makedirs(BAK, exist_ok=True)
+files = sorted({m[1] for m in MUTANTS})
+orig = {}
+for f in files:
+  bak = os.path.join(BAK, f.replace("/", "__"))
+  shutil.copyfile(f, bak)
+  orig[f] = open(bak).read()
+  if orig[f] != open(f).read(): sys.exit(f"backup mismatch for {f}, abort")
+for name, f, a, b, _ in MUTANTS:
+  if orig[f].count(a) != 1: sys.exit(f"{name}: anchor count {orig[f].count(a)}, abort")
+killed = 0
+try:
+  for name, f, a, b, tests in MUTANTS:
+    open(f, "w").write(orig[f].replace(a, b))
+    failing = []
+    for pkg, t in tests:
+      p = subprocess.run(["node", "--test", "--test-reporter=tap", t], cwd=f"packages/{pkg}", capture_output=True, text=True, timeout=600)
+      failing += [f"{pkg}/{t.split('/')[-1]}: {l[7:]}" for l in p.stdout.splitlines() if l.startswith("not ok")]
+    open(f, "w").write(orig[f])
+    status = "KILLED" if failing else "SURVIVED"
+    killed += bool(failing)
+    print(f"{status} {name}", flush=True)
+    for line in failing: print(f"    {line}", flush=True)
+finally:
+  for f in files: open(f, "w").write(orig[f])
+print(f"killed {killed}/{len(MUTANTS)}; restored: {all(open(f).read() == orig[f] for f in files)}")

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/prd18-r7-raise/NOTE.md

@@ -0,0 +1,8 @@
+# PRD 1.8 r7: no in-Stack raise (mos-1154)
+
+Sage, 2026-10-21T01:20:06Z. Jason approved PRD 1.8 in T3 (thread 38bc4c81, before 2026-10-21T01:16:55Z), verbatim:
+"PRD 1.8: I am preemptively approving it. Do not surface in the Mosaic Stack board. Just proceed."
+Mos records it as DECISIONS Q192 (mos-1154). The [mos test] raise request drafted here was dropped
+unsent, and the template is deleted. Jason closed 3a6c8fb9 himself at 01:05:45Z (no, "superseded by r7").
+Scope (Mos's reading): r7 at 47c2cb33c plus 82df17347, 342 lines, sha256
+de079281ff2760911039276379ec4b190287b2ce2e4e8a79c9459939727440cd, Duckworth duckworth-0073 (pass, no findings).

agents/sage/work/prd18-raise/decision.json

@@ -0,0 +1,35 @@
+{
+ "seq": 22,
+ "id": "3a6c8fb9-a5ab-42f8-9755-902a88375ca2",
+ "at": "2026-10-20T22:41:14.444Z",
+ "business": "mosaic-stack",
+ "project": null,
+ "raised_by_role": "pm",
+ "raised_by_run": "rc9e993da24cf",
+ "class": "gated",
+ "action": "prd.approve",
+ "route_to": "human",
+ "question": "Approve PRD 1.8 exactly as drafted?\n\nFile: agents/honker/work/queue-194/PRD-1.8-DRAFT.md on mosaicstack/stack at commit 762a6711ff7ed049aa73dfde98b75ebf326bdd99 (revision 5), 319 lines, sha256 8eee52470b1d7df139164e3ba5cc128dc469457b2b52f298c12685c3483011a8. Duckworth reviewed it (duckworth-0061, confirmed duckworth-0062) and Mos checked it (mos-1140). The tip of branch honker/row194-b2 holds a later r6 (aba3cbdeb), which is not used here. This approval covers only the r5 commit and sha256 above. The PM copied these values from the request and did not compute or check the sha256.\n\nNotes the approval carries:\n1. Mos's reading: \"the main agent or chief of staff\" in Q10 is one role under two names, the chief of staff. Only the chief raises a grant request; the assistant passes the user's request to the chief. To change it, say so at approval and REQ-GRANT-1 changes first.\n2. Mos's reading: revoke by \"you, Mos or the tester\" means the user, the assistant (\"Mos\", Jason's assistant) for grants in its own organization, and the tester only on a dev instance.\n3. N5: host.sudo keeps the arbiter route version 1.7 set for git.push.remote. A raise for it that cites the spec and isn't within-role goes to the arbiter for its domain, not to the user. In manual mode it comes to the user.\n4. B7 residual: only an Approve creates a grant, but an agent running as the stack's OS user can still write the stack's own store (Q182 on dragon-lin, #423 on .53 and .54). This version doesn't close it.\n5. N6: the broker enforces only that the chief of staff raised a grant request. The rest of the chain of command is the messaging lists and role contracts, not a broker check.\n\nSource: a tester request relayed by the chief (message 6990efb4, tester message d54a190e). It is a test request, not Jason's instruction. It takes the same route as PRD 1.7 (decision d52febb5): non-blocking, no task, uncited, so it goes to the human's Inbox. I recommend yes because two reviewers have passed r5 and the open points are written down above, not hidden.",
+ "options": [
+  {
+   "key": "yes",
+   "text": "Approve PRD 1.8 exactly as drafted: the r5 file at commit 762a6711ff7ed049aa73dfde98b75ebf326bdd99 with the sha256 below, and only that."
+  },
+  {
+   "key": "no",
+   "text": "Don't approve. Say what changes, and a new revision comes back for review."
+  }
+ ],
+ "recommendation": "yes",
+ "task_ref": null,
+ "requirement_ref": null,
+ "blocking": false,
+ "supersedes": null,
+ "spec_path": null,
+ "spec_commit": null,
+ "authorization": {
+  "action": "prd.approve",
+  "target": null,
+  "approvalChoice": "yes"
+ }
+}

agents/sage/work/prd18-raise/inbox.json

@@ -0,0 +1,37 @@
+[
+  {
+    "seq": 22,
+    "id": "3a6c8fb9-a5ab-42f8-9755-902a88375ca2",
+    "at": "2026-10-20T22:41:14.444Z",
+    "business": "mosaic-stack",
+    "project": null,
+    "raised_by_role": "pm",
+    "raised_by_run": "rc9e993da24cf",
+    "class": "gated",
+    "action": "prd.approve",
+    "route_to": "human",
+    "question": "Approve PRD 1.8 exactly as drafted?\n\nFile: agents/honker/work/queue-194/PRD-1.8-DRAFT.md on mosaicstack/stack at commit 762a6711ff7ed049aa73dfde98b75ebf326bdd99 (revision 5), 319 lines, sha256 8eee52470b1d7df139164e3ba5cc128dc469457b2b52f298c12685c3483011a8. Duckworth reviewed it (duckworth-0061, confirmed duckworth-0062) and Mos checked it (mos-1140). The tip of branch honker/row194-b2 holds a later r6 (aba3cbdeb), which is not used here. This approval covers only the r5 commit and sha256 above. The PM copied these values from the request and did not compute or check the sha256.\n\nNotes the approval carries:\n1. Mos's reading: \"the main agent or chief of staff\" in Q10 is one role under two names, the chief of staff. Only the chief raises a grant request; the assistant passes the user's request to the chief. To change it, say so at approval and REQ-GRANT-1 changes first.\n2. Mos's reading: revoke by \"you, Mos or the tester\" means the user, the assistant (\"Mos\", Jason's assistant) for grants in its own organization, and the tester only on a dev instance.\n3. N5: host.sudo keeps the arbiter route version 1.7 set for git.push.remote. A raise for it that cites the spec and isn't within-role goes to the arbiter for its domain, not to the user. In manual mode it comes to the user.\n4. B7 residual: only an Approve creates a grant, but an agent running as the stack's OS user can still write the stack's own store (Q182 on dragon-lin, #423 on .53 and .54). This version doesn't close it.\n5. N6: the broker enforces only that the chief of staff raised a grant request. The rest of the chain of command is the messaging lists and role contracts, not a broker check.\n\nSource: a tester request relayed by the chief (message 6990efb4, tester message d54a190e). It is a test request, not Jason's instruction. It takes the same route as PRD 1.7 (decision d52febb5): non-blocking, no task, uncited, so it goes to the human's Inbox. I recommend yes because two reviewers have passed r5 and the open points are written down above, not hidden.",
+    "options": [
+      {
+        "key": "yes",
+        "text": "Approve PRD 1.8 exactly as drafted: the r5 file at commit 762a6711ff7ed049aa73dfde98b75ebf326bdd99 with the sha256 below, and only that."
+      },
+      {
+        "key": "no",
+        "text": "Don't approve. Say what changes, and a new revision comes back for review."
+      }
+    ],
+    "recommendation": "yes",
+    "task_ref": null,
+    "requirement_ref": null,
+    "blocking": false,
+    "supersedes": null,
+    "spec_path": null,
+    "spec_commit": null,
+    "authorization": {
+      "action": "prd.approve",
+      "target": null,
+      "approvalChoice": "yes"
+    }
+  }
+]

agents/sage/work/prd18-raise/msg.txt

@@ -0,0 +1,13 @@
+[mos test] Please have the PM raise a prd.approve decision for PRD 1.8, the same route as PRD 1.7 (decision d52febb5): blocking false, no task_ref, recommendation yes, gated to the human. The PM must not compute or change the sha256; it copies the values below.
+
+Question: "Approve PRD 1.8 exactly as drafted?"
+File: agents/honker/work/queue-194/PRD-1.8-DRAFT.md on mosaicstack/stack at commit 762a6711ff7ed049aa73dfde98b75ebf326bdd99 (revision 5), 319 lines, sha256 8eee52470b1d7df139164e3ba5cc128dc469457b2b52f298c12685c3483011a8. Reviewed by Duckworth (duckworth-0061, confirmed duckworth-0062) and checked by Mos (mos-1140). The branch tip of honker/row194-b2 holds a later r6 (aba3cbdeb) that is not used; the approval covers only the r5 commit and sha256 above.
+
+The decision notes must carry these five items:
+1. Mos's reading: "the main agent or chief of staff" in Q10 is one role under two names, the chief of staff. Only the chief raises a grant request; the assistant passes the user's request to the chief. To change it, say so at approval and REQ-GRANT-1 changes first.
+2. Mos's reading: revoke by "you, Mos or the tester" means the user, the assistant ("Mos", Jason's assistant) for grants in its own organization, and the tester only on a dev instance.
+3. N5: host.sudo keeps the arbiter route version 1.7 set for git.push.remote. A raise for it that cites the spec and isn't within-role goes to the arbiter for its domain, not to the user. In manual mode it comes to the user.
+4. B7 residual: only an Approve creates a grant, but an agent running as the stack's OS user can still write the stack's own store (Q182 on dragon-lin, #423 on .53 and .54). This version doesn't close it.
+5. N6: the broker enforces only that the chief of staff raised a grant request. The rest of the chain of command is the messaging lists and role contracts, not a broker check.
+
+Reply with the decision id once raised. Do not resolve it.

agents/sage/work/prd18-raise/talk.txt

@@ -0,0 +1,8 @@
+sent d54a190e to chief
+chief (RESULT, re d54a190e) cc46a7b4:
+I passed your request to the pm without changing any of it, and launched the pm so it can act on it. No decision id yet, because the pm hasn't raised the decision.
+
+- **Message to pm:** 6990efb4-8321-4d0e-9b8a-771f65625b83. It says the request comes from a tester and authorizes nothing, and it carries your PRD 1.8 values and the five notes as you wrote them.
+- **pm launch:** run rc9e993da24cf.
+
+When the pm answers with the decision id, I'll send it to you.

agents/sage/work/prd18-raise/trail.txt

@@ -0,0 +1,5 @@
+trail 3a6c8fb9-a5ab-42f8-9755-902a88375ca2: 4 row(s)
+2026-10-20T22:40:47.949Z  events#1550  session.launched  pm
+2026-10-20T22:40:47.969Z  role_claims#102  claim pm by rc9e993da24cf
+2026-10-20T22:41:14.444Z  decisions#22  gated prd.approve → human: Approve PRD 1.8 exactly as drafted? File: agents/honker/work/queue-194/PRD-1.8-DRAFT.md on mosaicstack/stack at commit …
+2026-10-20T22:41:14.445Z  events#1553  action.allowed  pm  decision.raise  decision 3a6c8fb9

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/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/queue-197/OBSERVATIONS.md

@@ -0,0 +1,17 @@
+# Row 197 proof observations (Sage)
+
+Kept here, not in Herb's BUILD.md, because that file is one of row 197's 37 paths and the landing check
+(mos-1174, mos-1185 item 5) requires them equal to c45ddeb6b.
+
+## Open observation (mos-1185 item 3), 2026-10-21
+
+Proofs 4 and 5 each stopped on a test outside 197's paths, in a pair wave, and both times in lane b:
+
+- Proof 4, pair1-b, pkg-conversation, K12 (`cohort.test.mjs:292`): `populated` undefined. Row 250, Vikunja #450.
+- Proof 5, pair2-b, pkg-bus, T27 (`host-run.test.mjs:469`): no identities right after `ssh-add -t 1`. Vikunja #453.
+
+Mos checked the step log birth times: the twin step started in both lanes within half a second each time
+(proof 4 pkg-conversation a 11:03:59.343, b .855 CDT; proof 5 pkg-bus a 12:07:25.354, b .573). Waves run in
+lockstep, so that holds for every pair wave, the passing ones too. Lane b is the twin that starts later.
+Mos's reading: contention exposing fragile tests, not a 197 defect. Paired lanes add contention, and that
+is 197's cost, covered by #451.

agents/sage/work/queue-218/BUILD.md

@@ -0,0 +1,149 @@
+# Row 218 draft notes: claims and sources
+
+Drafts for `docs/case2/SETUP-SHEET.md` and `docs/case2/SURVEY-RUN.md`. Repo base: `refactor` at
+947101d8a, which holds 29ce1e360 (row 231). "Design" means
+`git show 75fb3e10e:agents/gosalyn/work/case2/DESIGN.md`, cited as `D:<line>`. "Brief" means
+`docs/plans/2026-10-20_case2-rows.md`. Code paths are relative to the repo root. Nothing was run
+except reads, greps and `git merge-base --is-ancestor 29ce1e360 HEAD`.
+
+## SETUP-SHEET.md
+
+| Claim | Source |
+|---|---|
+| She keeps writing in Obsidian, obsidian-git pushes to git.mosaicstack.dev, nothing changes on her machine, nothing commits to her repo | D:939-940 (7.1) |
+| Agents read what she pushed; a push reaches them in about a minute | D:1006-1007 (7.5); D:972-973 (60-second sync timer) |
+| Agents read `.md` notes inside book folders only | D:457-461 (1.2); `packages/library/src/scope.mjs:9-19` |
+| Not read: top-level notes, `.canvas`, `.base`, attachments, anything outside a book folder | D:461 |
+| Other repos under `~/src` are not read | D:489 (1.3), D:494-497 (N4) |
+| Agents can't write to her repo: canon, playground, anything | D:389 (D3); D:1008 |
+| Folder roles live in the `projects` entry of the business file, hand-edited, agents can't change it | D:409-429, D:443-451 (1.1, M9) |
+| Jason asks her to confirm the mapping first | D:431; D:1324-1328 (10 step 7) |
+| A folder named in `playground` is her playground | Brief:22; D:434 |
+| Each playground prefix sits inside one book folder | D:434-436; `packages/library/src/mapping.mjs:77-80` |
+| One per book, e.g. `<book>/playground/`; until then everything mapped is canon | D:438-439 |
+| Agents search canon unless they ask for the playground | D:463 |
+| Playground may back an idea or question, not a fact, finding or correction; refused before she sees it | D:858 (`playground-cited-as-canon`); D:378-382, D:835-839 (guard runs before store) |
+| Only the folder decides; a tag or property can't change scope | D:388 (D2); D:440-441; `scope.mjs:1` |
+| Graph colour group via Groups and a `path:` query, her own vault setting, changes nothing for agents | Brief:23; D:941-943. Obsidian UI steps from the task prompt, not the design |
+| Path starts with the books repo folder because the vault is `~/src` | D:939 |
+| N2: moving a note into a book folder makes it canon, agents may cite it as fact | D:944-945; D:259 |
+| Rough drafts outside the playground are canon | Inference from D:460 (scope rule) |
+| N4: Obsidian resolves short links across `~/src`, the reader sees one repo, the two can differ, the reader can't tell | D:494-497; D:262-263 |
+| A name only in another repo leads nowhere for agents | D:489 (R4); `packages/library/src/links.mjs:61-87` |
+| A full-path link resolves the same in both | D:497-498. Hub side: `links.mjs:77-78` (`vault-prefix` step) |
+| "New link format: Absolute path in vault" setting | Obsidian UI knowledge. Not in design or code. Reviewer may strike it |
+| `appears_in` and `relationships` links are read as links | D:489-490; `packages/library/src/reader.mjs:15`, `:153-162` |
+| Quoted flow list `["[[A]]", "[[B]]"]` parses | `reader.mjs:81-96` (flow), `:66-73` (quoted scalar), `:159` |
+| Block list with quoted items parses | `reader.mjs:117-122`, `:66-73` |
+| Unquoted `[[[A]], [[B]]]` is R3 | Brief:28-29; `reader.mjs:87` (bracket inside a flow list stops parsing), `:137` |
+| R3 effect: whole front matter unread, note still indexed by path, name and body, listed as a problem | D:480; `reader.mjs:103-105`, `:193`; `packages/library/README.md:69` |
+| Problems show in Mosaic's status | D:473-474; D:999-1000 (7.4 status line) |
+| A value without `[[ ]]` is a name | D:489-490; `reader.mjs:159` |
+| Bean and Chet keep names and personalities | D:660-661 (Q180) |
+| Hermes: free text and story text. Mosaic: short cited items, a prose request gets a question or idea | D:778-781 (design 4) |
+| Bean and Chet's item kinds: idea, question, finding, fact; web cites allowed | D:649 (`companion`); D:860 (`citation-unfetched`) |
+| Limits 10 items, 5 ideas of 200, others 300 | D:819 (M5) |
+| She or Jason can ask for lower limits | D:1329-1330 (10 step 8); D:831 |
+| "No cited answer" notice | D:870-871, D:996-997 |
+| One item can't mix two worlds | D:859 (`citation-cross-universe`) |
+| She talks to them in the Console; Hermes keeps running until she moves over; stopping it is her choice | D:381-382; D:1331 |
+| Five more helpers; she chooses the start set and can add one later | D:647-654; D:783-784; D:1327-1328 |
+| What Jason will ask | D:1325-1327 (10 step 7) |
+
+## SURVEY-RUN.md
+
+| Claim | Source |
+|---|---|
+| Runs on `<host>` 10.1.1.54 under design 10 step 7, after step 4 | D:1324; D:1266 (host) |
+| Prints names and counts, never note text, property values, file names or link targets | `packages/library/src/survey.mjs:1-6`; README:118-125 |
+| Sending to Melanie is Jason's call | Brief:36; D:1324-1328 |
+| Token slot `library-gitea` is step 4 | D:1314-1316 |
+| Run as `sudo -u mosaic -H` from `localadmin`; `mosaic` has no login shell | D:1195-1197; D:1281-1282 |
+| Copy at `/srv/mosaic/.local/share/mosaic-stack/copies/<id>`, `<id>` = commit in Jason's go | D:1286-1292 (2c); `docs/TOOLS.md:417`; home `/srv/mosaic` per D:1314-1315 |
+| The copy carries `packages/library/src` | `scripts/stack-copy.sh:36` |
+| Row 231 adds the control and bidi escapes | `git log` 29ce1e360; `survey.mjs:78-82`; README:121-122 |
+| `<node dir>` is the `--node` directory of step 2c; `scripts/mosaic` execs `node` from PATH | D:1290-1291; `scripts/mosaic:41` |
+| Dispatch: `mosaic library survey` goes to `survey.mjs` with `survey <args>` | `scripts/mosaic:37-41` (one `shift` leaves `survey` as argv[0]); `survey.mjs:102-103` |
+| Command and flags: `<repo>` plus optional `--mapping <file>` once; anything starting with `-` refuses | `survey.mjs:16`, `:104-110` |
+| No fetch; reads `HEAD` | `survey.mjs:5-6`, `:27`; `reader.mjs:22-24` |
+| Top folder only: ceiling is the path's parent | `packages/project/src/git.mjs:12`, `:62` |
+| Owner must be `mosaic`: git gets no global config | `packages/seat/src/checkout.mjs:79-89` (`GIT_CONFIG_GLOBAL=/dev/null`, `GIT_CONFIG_NOSYSTEM=1`). The dubious-ownership refusal is git's own behaviour |
+| Bus mirror path `<dataRoot>/projects/<business>/<project>` | Brief:300; `packages/project/src/paths.mjs:34-40` |
+| C2-04 and C2-03a not landed | `grep` of `packages/*/src` finds no library entry handling or `refs/heads/served`; `docs/guides/host-run-sheet.md:269` says "not landed" |
+| Served ref `refs/heads/served` | D:963 (7.2); Brief:676 |
+| Token kept out of URL, config, argv, logs | D:955-956 (7.2) |
+| Mapping file is the entry alone; `remote`, `branch` required | `survey.mjs:114-116`; `mapping.mjs:38-47` |
+| Output lines and fields | `survey.mjs:83-97`; data from `:26-76` |
+| Folder lines list folders that directly hold an entry, full path | `survey.mjs:30-35` |
+| Key names: short identifiers print, others as `(other key)` | `survey.mjs:17-20`, `:47` |
+| `unresolved` equals the R4 count | `survey.mjs:72` |
+| Scope counts cover all tree entries | `survey.mjs:66` |
+| Refusal exit codes 0, 2, 3, 4 | `survey.mjs:99-124`; README:127-129 |
+| Mapping checked before repo | `survey.mjs:112-121` |
+| stderr format `library survey: <message>` | `survey.mjs:101`; `problems.mjs:3-5` |
+| `(project-git)` suffix on git failures | `reader.mjs:18-20`; `paths.mjs:4-6` |
+| `library-playground-outside-book` message | `mapping.mjs:79-80` |
+| 100-second git timeout | `checkout.mjs:49`, `:52`; `git.mjs:68` |
+| Exit 127 when `node` is missing | `scripts/mosaic:18`, `:41` (bash `exec` failure). Not run |
+| Other errors rethrow as a stack trace | `survey.mjs:117`, `:123`, `:128-131` |
+| Don't work around a refusal | AGENTS.md invariant 6 |
+
+## Code and design disagreements
+
+1. Design 1.1 shows the mapping nested in `"projects": {"books": {...}}` (D:412-429). The survey's
+   `--mapping` file must be the inner entry alone (`survey.mjs:114-116`). The run sheet follows the code.
+2. Design 1.3 calls `vaultPrefix` part of the mapping (D:418). The code makes it optional
+   (`mapping.mjs:48`, README:30). Without it, a full vault path link, the N4 advice, resolves to
+   nothing in the hub (`links.mjs:73-87`: `root` fails, `vault-prefix` is skipped, `shortest` refuses a
+   `/`). The setup sheet's full-path advice holds only when Jason sets `vaultPrefix` to her books repo
+   folder name.
+3. The task prompt calls the unquoted form "refused". R3 is not a refusal. It is a reported problem,
+   and the note stays indexed (D:473, D:480). The sheet says what happens instead.
+
+## Open questions
+
+1. Where `<repo>` comes from on .54. The survey reads a local repo's `HEAD` and never fetches. The bus
+   mirror needs C2-04 and C2-03a, neither landed. C2-03a moves `refs/heads/served`, not `HEAD`, so the
+   mirror's `HEAD` may name no commit and the survey would refuse with exit 2. The sync also needs a
+   checked mapping with at least one book (`mapping.mjs:59`, `:70`), and the mapping's values are
+   meant to come from this survey (D:431). Sage needs to rule: a placeholder mapping for the first
+   sync, a `HEAD` the sync sets, a `--commit` flag on the survey, or another source.
+2. The brief says Obsidian's property editor writes `appears_in: ["[[A]]", "[[B]]"]` (Brief:28-29,
+   webby-0041 N4). I didn't read webby-0041 or check Obsidian's output. Both the flow and the block
+   quoted forms parse, so the sheet shows both and says only that the editor adds the quotes.
+3. Whether `/srv/mosaic/.npm-global/bin/mosaic` exists on .54. The run sheet uses the copy's
+   `scripts/mosaic` by full path to avoid depending on a wrapper.
+
+## Sage's rulings on the open questions (2026-10-21)
+
+1. Survey source: the bus's bare mirror after the first `library.sync`, the only copy on the host
+   (design 2.1). The C2-03a brief now requires the mirror's `HEAD` to be a symbolic ref to
+   `refs/heads/served`, with a test (5c6f73ed7), so the survey reads the served commit with no ref flag.
+2. Property list forms: the sheet shows both quoted forms, since both parse. Webby checks the claim
+   that Obsidian's property editor writes the quoted form.
+3. The "New link format: Absolute path in vault" tip stays. It is an Obsidian setting, not a design
+   claim, and Webby may strike it.
+4. The run sheet calls the copy's `scripts/mosaic` by full path. That holds whether or not a wrapper
+   is on `PATH`.
+5. `vaultPrefix`: the run sheet's step 4 tells Jason to set it, because the setup sheet's full-path
+   link advice depends on it.
+
+## Round 2 (2026-10-21), from Webby's round 1 notes (webby-0075, rev 2848)
+
+- N1, by Mos's ruling mos-1165 (fix before landing): SETUP-SHEET.md now gives the 1,200 character
+  total of item text per reply (design M5, step 8). The word "Today" is gone. No code enforces these
+  caps until C2-06 lands, so my ruling is that the sheet goes to Melanie only after C2-06 lands, and
+  then only on Jason's go (#419). The wording stays as is, because by then it holds.
+- N2: SURVEY-RUN.md says tab, newline, carriage return, backspace and form feed print as `\t`, `\n`,
+  `\r`, `\b` and `\f`, and other control and bidi characters as `\uXXXX` (survey.mjs quote()).
+- N3: SURVEY-RUN.md has a refusal row for `library-commit:` (reader.mjs listTree). survey.mjs turns
+  every LibraryError into exit 2 with its message.
+- N4: SURVEY-RUN.md's new step 2 checks `command -v node` under the same sudo and PATH before the
+  survey runs.
+
+## Round 3 (2026-10-21), from Webby's round 2 note N5 (webby-0077, rev 2856)
+
+- N5: the library-commit row no longer says a moved `HEAD` causes it. The survey reads `HEAD` once,
+  and listTree raises library-commit only for an id that isn't 40 hex or an object that isn't a
+  commit (reader.mjs:29, :31). In practice that means a SHA-256 repository, so a rerun doesn't help.
+  The row now says "for example in a SHA-256 repository" and "Report to Sage".

agents/sage/work/queue-66/BUILD.md

@@ -0,0 +1,200 @@
+# Row 66: managed sessions run the unslop check on both harnesses
+
+Sage, 2026-10-20. Brief: `docs/plans/2026-10-11_managed-session-config.md`, section "Managed
+sessions run the unslop check on both harnesses", blob 21ae25a328d4. Issue #1559. Reviewers:
+Dewey and Filbert. Built in the worktree `/mnt/storage/scratch/sage-b66` (branch `sage/row66`)
+on base 5487ed39d.
+
+Candidate: see the commit line in the review request. `candidate-manifest.sha256` in this
+directory has the sha256 of each changed file at the candidate.
+
+## What changed
+
+**Wiring.** Both harness modules mount `tools/unslop-hook/lists.json`, `unslop-check.js` and
+the harness's own entry (pi `extension.ts`, Claude Code `claude-hook.js`) read-only at their
+own paths, and the bundle manifest lists the three in `sources` with their digests. Pi loads
+`extension.ts` as the second entry of `MOSAIC_EXTENSIONS`, after the gate extension. Claude
+Code's `settings.json` gains a Stop hook and a UserPromptSubmit hook, each
+`timeout -k 2 10 '<node>' '<dir>claude-hook.js' stop|prompt; exit 0`, hook timeout 20, no
+matcher. Neither can block a reply or a prompt.
+
+**claude-hook.js** (new). `stop` checks each assistant message with text since the turn's
+prompt and logs `checked` or `flagged`. `prompt` checks the last reply and, when it has tells,
+prints the extension's notice, word for word, as `additionalContext`, once per reply (it reads
+the log for an earlier `notice_injected` with the same entry id). A broken lists.json logs
+`broken_lists`; any other fault logs `hook_failed`; the exit is always 0.
+
+**The operator channel.** The runner sets `MOSAIC_UNSLOP_LOG` to `<run>/unslop.jsonl` after the
+module's variables, so a module can't point it elsewhere. After the landing turn and after each message turn it reads what the
+log gained (whole lines only, from an offset). The next RESULT it sends ends with a note. The
+whole note, both parts and the blank line before them, is at most 600 characters (r2):
+
+- `[unslop: N reply|replies of this session flagged since the last note: <details>. The session gets a correction notice on its next turn.]`
+- `[unslop: the check is broken, so this session's replies go unchecked: <reason>]`, once a run.
+
+That RESULT is what `mosaic talk` and `mosaic follow` print. A turn that sends no reply (an
+incoming RESULT, the landing turn) keeps its note for the next one. `note()` doesn't change
+state and `sent()` runs only after `message.send` succeeds, so a failed send keeps the note.
+`clip()` caps the body at 32000 characters plus its 33-character cut line before the note, so the
+sum is at most 32633, under the bus limit of 32768. The broken reason is cut at 300 where the
+runner takes it, from the log or from its own read failure, so the broken part is at most 371
+characters and the flagged part is cut to what is left.
+
+**Counts.** `unslopCounts(path)` reads the log after the session ended:
+`{checked, flagged, patterns: {<source>: n}, notices, broken}`. A missing log gives zeros.
+Findings now carry `source`, the entry's pattern id (`ms-unslop:7`), so `patterns` is per id.
+
+**The stack copy (r2).** `scripts/stack-copy.sh` `COPY_PATHS` gains `tools/unslop-hook`. Both
+modules join their files under `REPO`, and a session launched from a pinned copy has
+`REPO = copies/<sha>`. Without it every managed session from a copy past this row would fail at
+bundle build with ENOENT (Dewey P1, comment 29440).
+
+## Round 2
+
+Round 1 (candidate 8ec03b45a, manifest e68c6bce5ec4) got changes from Filbert (29439) and Dewey
+(29440). Round 2 carries:
+
+- F1 (both): a note with both parts wasn't bounded. A 300-character reason, a long flagged part
+  and a clipped answer came to 32934 (Filbert) or 33004 (Dewey), over 32768, and the broker
+  refused the send. `note()` now gives the flagged part only the room the broken part leaves, and
+  `fresh()` cuts every reason at 300, the runner's own read-failure reason included. Tests: the
+  runner test with an answer of 40000 characters, a 400-character `hook_failed` reason and 30
+  flagged replies (note ≤ 600, body ≤ 32768, cut line at 32000), and a unit check that both
+  parts come to exactly 600 and that a read failure on a 250-character path is cut.
+- F2 (Filbert; Dewey's M3): no test failed a send through `main()`. The new runner test has the
+  broker refuse the first RESULT. The note then rides the next RESULT. One correction to the
+  F1 consequence as written: the broker marks a received message delivered, so the refused
+  message isn't received again in that run. It stays unread and its sender gets no reply; the
+  turn doesn't rerun.
+- P1 (Dewey): `COPY_PATHS` gains `tools/unslop-hook`. The copy fixtures in
+  `stack-copy.test.mjs` and `pinned-copy.test.mjs` copy `tools/unslop-hook` too, and the
+  pinned-copy top-level list gains `tools`. A new `stack-copy.test.mjs` test makes a copy, loads
+  both harness modules from it, and checks that the adapter, the six unslop paths and the mounts
+  are under the copy and exist.
+- N1 (Filbert): the two session-test comments say `<dir>/unslop.jsonl`.
+- N2 (Filbert), doc-only follow-up: the brief's `<run>/session/unslop.jsonl` (:463) and "print
+  mode notifies nobody" (:477) are stale. The brief is Jason's text for this row; the deviation
+  below records the path.
+- Dewey's notes, no change: the Claude Code Stop timing (finding 3 below) gets a look in the
+  landing session; `patterns` keys per entry source, which is the brief's "per pattern".
+
+r2 mutants, each killed by its intended test (`mutants-r2.log`):
+
+| Mutant | Killed by |
+|---|---|
+| K1 the r1 `note()` cut | the clipped-answer runner test (the send is refused and it times out) and the unit check |
+| K2 `fresh()` doesn't cut the reason | the unit check |
+| K3 `sent()` before `message.send` | the refused-send runner test |
+| K4 `COPY_PATHS` without `tools/unslop-hook` | the copy test |
+
+## Ship list against the brief
+
+| Brief item | Where |
+|---|---|
+| A reply with a tell gets a correction notice on the next turn, both harnesses | `pi-session.test.mjs`, `claude-session.test.mjs`, row 66 four-turn tests: notices per request `[0, 1, 1, 2]`, notice text matched in the second request |
+| A clean reply gets none | same tests: turn 2 is clean and turn 3's request carries no new notice |
+| Broken lists.json fails closed: no clean verdict, operator told once, session alive | the row 66 broken-lists tests per harness: checked 0, flagged 0, first note broken, second note empty, the session answers both turns |
+| Counts readable after the session ends | `unslopCounts` on each session's log: `{checked: 4, flagged: 2, notices: 2, broken: null}`, patterns non-empty |
+| Interface 1 and the export list unchanged | no harness module export added or removed; the runner gains `unslopLog`, `unslopCounts`, `unslopNotes` |
+
+## Findings made while building
+
+1. **extension.ts read the wrong reply.** Pi 0.85.1 `getBranch()` returns entries root first
+   (`session-manager.js:958-967` reverses the leaf-to-root walk). `before_agent_start` took the
+   first assistant entry it met, which was the session's first reply, every turn. In the
+   four-turn test the old code gave notices `[0, 1, 2]` over three turns (turn 3 re-noticed
+   turn 1); walking from the end gives `[0, 1, 1]`. Fixed in `extension.ts`; this also affects
+   the fleet copy under `~/.mosaic/tools`, which I didn't touch.
+2. **claude-hook replies() merged replies.** Grouping by `message.id` across the transcript
+   merged two replies that shared an id (the test API answers `msg_mock` for all). It now groups
+   adjacent assistant lines only, keyed by the first line's uuid. Before the fix turn 4 got no
+   notice (`[0, 1, 1, 1]`).
+3. **Claude Code Stop timing.** On the first turn of a new session the transcript didn't yet
+   hold the reply when Stop ran, so the hook checked `last_assistant_message` with an empty
+   `entryId`. On resumed turns the reply was in the transcript. The verdict is the same either
+   way; only the entry id differs.
+4. The finding detail format is `banned word "delve" x1`.
+
+## Deviations
+
+- **The log path is `<run>/unslop.jsonl`, not the brief's `<run>/session/unslop.jsonl`.** A
+  thread run's session directory is the thread's store, and
+  `packages/cli/tests/thread-launch.test.mjs:179` pins that a thread run keeps no per-run
+  `session/`. My first build made `<run>/session` for the log and failed that test in the gate
+  (452/453). The brief's other line, "`unslop.jsonl` in the run directory", still holds, and each
+  run keeps its own log.
+
+- **`packages/seat/tests/sandbox.test.mjs`** isn't an owned file. Its pin
+  `binds(args).length === list.length - 1` broke because the modules now mount three more files.
+  It is now `- 4`, and the test asserts the three unslop read-only binds by name.
+- **`scripts/stack-copy.sh`** and the two copy tests aren't owned files. The copy change is P1
+  above. PB3 of the Part B window (`repin-partB-proof.md`) holds `scripts/stack-copy.sh` still
+  until B7, so this row lands after the Part B window has run.
+- `MOSAIC_EXTENSIONS` is set through the pi module's `env`, not in the runner.
+- `unslop-check.js` gained the `source` field on findings (needed for per-pattern counts).
+
+## Limits
+
+- The log is in the run directory, which the session can write. A session could forge or erase
+  its own counts. They are the session's report, not host evidence.
+- The pi extension's dedupe is in memory: after a restart, or when a turn's final message is
+  tool-only, the same earlier reply can get a second notice.
+- `hook_failed`, `skipped_broken` and `broken_lists` all count as broken for the operator note.
+- No blocking (Q84 option B), no list changes, no skill changes: out of scope by the brief.
+
+## Gate
+
+Recorded with the candidate in the review request: test-unslop-check, the harness, plugins,
+seat and cli suites, and every `scripts/test-*.sh`. At landing Sage runs one managed session per
+harness and attaches the notice, the correction and the counts.
+
+## Round 4
+
+Round 3 (2369c00e3 on sage/row66-r3, base c40d846cb, manifest 42e3876ca168) had approvals from
+Filbert (29770) and Dewey (29771). Since then rows 200, 199, 232, 233, 240 and 238 changed three
+of the 23 paths: `docs/TOOLS.md`, `scripts/stack-copy.sh` and
+`packages/cli/tests/stack-copy.test.mjs`. Round 4 is the two round 3 commits cherry-picked onto
+4ced5e63d (sage/row66-r4). Neither pick had a conflict, and the tree equals a hand merge of each
+path with `git merge-file`. No code changed: `git diff BASE TIP | git patch-id --stable` is
+6d085621fd35 for both rounds.
+
+- Row 232 added `copy --bundle` (`copy_bundle`). It builds the bundle with `copy_tree`, which
+  copies `COPY_PATHS`, so a bundle copy also carries `tools/unslop-hook`. No extra change needed.
+- The Part B hold under Deviations is void. Part B was superseded by the Q175 SSO work and will
+  not run, so nothing holds `scripts/stack-copy.sh`.
+- Review scope: the merge on the three moved paths and this section. The other 19 paths have the
+  same blobs as round 3.
+
+Rebased again on fefd54e13, after row 212 landed (ee7b2f137), as branch `sage/row66-r4b`, before the round 4
+request went out. 212 added `packages/library/src` to `COPY_PATHS` and a library line to the
+`stack-copy.test.mjs` file list. None of the four picks had a conflict. Every file's patch-id equals the 4ced5e63d
+build's except `scripts/stack-copy.sh`, where the only change is the hunk's context line
+(`packages/queue/src packages/library/src`). Row 66's two added lines are the same.
+
+Rebased again on 29ce1e360, after rows 195, 213 and 231 landed, as branch `sage/row66-r4c` (r4b stays at
+49ad61963). Two of row 66's paths moved: `adapters/README.md` and `docs/TOOLS.md`. TOOLS.md merged without a
+conflict. In adapters/README.md, row 213 rewrote the skill-cap paragraph, because `claude` now gets the prompt
+as a file. The merge keeps 213's paragraph whole and adds row 66's "The unslop check (row 66)" section after
+it. Row 66's old cap sentence is dropped, since it described the argument limit that 213 removed. Every other
+path has the same blob as on r4b. Row 213 also changed the harness and both adapter scripts, so all of row 66's
+harness tests run whole again on this base before the request.
+
+Rebased again on 7b9737953, after rows 245, 248 and 249 landed, as branch `sage/row66-r4d` (r4c stays at
+670b83f65). Only `docs/TOOLS.md` moved under row 66: row 245 rewrote the paragraph on what root reads in the
+host check. The cherry-pick had no conflict. `git patch-id --stable` of row 66's whole diff is 508bb684eade on
+both bases, and so is each file's own patch-id, TOOLS.md included. So row 66's hunks are byte-identical and only
+their context moved. The one test that names TOOLS.md, `packages/cli/tests/stack-release.test.mjs`, uses it in a
+message string and is in the singles list.
+
+Rebased on a36523713 after row 197 landed (mos-1186 item 4), as branch `sage/row66-r5` (r4d stays at
+82c830779). Row 197 also touched `packages/harness/tests/claude-session.test.mjs` and `pi-session.test.mjs`.
+The cherry-pick had no conflict. The range-diff shows commit 1 differing only in one hunk header of
+pi-session.test.mjs, where git now names the context line. Commits 2-7 are `=`. `git patch-id --stable` is
+0049d05fb585 for the whole diff and d67275ac4251 without `agents/` on both bases. Correction: the r4d note
+above gives 508bb684eade for the whole diff. That number came from e25f76f54 before the 7b9737953 rebase. The
+whole-diff number on r4d is 0049d05fb585. The harness suite runs whole again on this base before landing.
+
+Correction (Filbert round 4 N2, comment 30086): the r4c paragraph says "Row 66's old cap sentence is
+dropped." That's wrong. In round 3's diff the 64 KiB cap sentence is unchanged context, so row 66 never
+wrote it. Row 213 replaced it, and none of row 66's lines were dropped. The landing sessions are in
+LANDING-SESSION.md.

agents/sage/work/queue-66/LANDING-SESSION.md

@@ -0,0 +1,43 @@
+# Row 66 landing sessions (mos-1186 items 2-3)
+
+Sage, 2026-10-21. Both ran on a scratch data root built from the candidate tree, branch `sage/row66-r5`
+at 273fff6f9 on a36523713, as row 64's D2 did (rc13bcd555652). The scripts were
+`/mnt/storage/scratch/sage-r66r5x/d2s/d2-build.mjs` and `d2-drive.mjs`. They used the business example
+with stand-in token files, tracker and Gitea URLs pointing at 127.0.0.1:9, and a scratch project repo.
+Nothing live was touched. The six skills were installed and enabled on each data root with
+`scripts/skill.sh` from the candidate tree.
+
+Before the sessions, the harness suite ran whole on 273fff6f9: 149 pass, 0 fail, 12 s
+(2026-10-21T18:47:42Z).
+
+## Claude Code, run r4ab24630d323 (18:48Z)
+
+The chief and cto were bound, and the coder was launched through `launcher.fromSession` on claude-code,
+model claude-sonnet-5-5. The launch bundle names `tools/unslop-hook/claude-hook.js`, `unslop-check.js`
+and `lists.json`.
+
+- Turn 1. cto asked for one sentence with four banned words. The RESULT body `mosaic talk` would print
+  ends with the operator note:
+  `[unslop: 1 reply of this session flagged since the last note: banned word "additionally" x1; banned word "crucial" x1; banned word "testament" x1; banned word "vibrant" x1. The session gets a correction notice on its next turn.]`
+- Turn 2. `unslop.jsonl` logs `notice_injected` for that turn. The coder's transcript has the notice as
+  UserPromptSubmit hook additional context in the API request:
+  `UNSLOP NOTICE (mechanical style check, not the user speaking): your previous reply contained violations of the fleet writing standard (SYSTEM.md / ms-unslop): ...`.
+  cto asked the coder to quote it. The coder answered "I can't answer that one, and I won't quote
+  anything from it." So the notice reached the model, which chose not to repeat it. Its reply checked
+  clean.
+- Counts from `unslopCounts`: checked 2, flagged 1, patterns `ms-unslop:7` 4, notices 1, broken null.
+
+This scratch instance has no `mosaic talk` view of its own, so the note above is the RESULT body the bus
+returned to cto. That is the text `mosaic talk` and `mosaic follow` print.
+
+## pi, run r1dd94171bede (launch only)
+
+The coder launched on pi, model claude-sonnet-5-5. The launch bundle names
+`tools/unslop-hook/extension.ts`, `unslop-check.js` and `lists.json`. No turn ran. This host has no
+credential pi reads until P19 #383 settles, and mos-0865 D2 rules out mapping the Claude Code token into
+a pi variable. No `unslop.jsonl` was written. Counts: checked 0, flagged 0, notices 0.
+
+## Still open
+
+Vikunja #454 tracks both live checks. Claude Code runs in the first re-pin whose tree includes row 66,
+backup first. Pi runs one full session with a tell after #383. See `docs/plans/DEFERRED.md`.

agents/sage/work/queue-66/R3.md

@@ -0,0 +1,21 @@
+# Row 66 round 3: rebase only
+
+Sage, 2026-10-20. Round 2 (candidate 0f4a57956, manifest cee63e06fdea) was approved by Filbert (29442) and
+Dewey (29443). Its base 5487ed39d is now far behind refactor, and rows 190 and 192 changed four of its paths.
+Under the base drift rule a drifted candidate gets a new round on the new base before it lands.
+
+- Candidate: branch `sage/row66-r3`, commit 2369c00e36874e1100b301e0d01cbd105c0c5d4f, two cherry-picks of 8ec03b45a and 0f4a57956 onto c40d846cb.
+  No conflicts and no hand edits.
+- `git patch-id --stable` of the r3 diff (c40d846cb..2369c00e36874e1100b301e0d01cbd105c0c5d4f) equals the r2 diff's (5487ed39d..0f4a57956):
+  6d085621fd355d43ccaf0efaefe7e74179888ff2.
+- Manifest `candidate-manifest-r3.sha256`, sha256 42e3876ca1689719f0e07e66fc9fbd6e4faf3c07678da024accb54c58caef0d1. Same 23 paths as r2. Four hashes differ, and only
+  because the base moved: `docs/TOOLS.md`, `scripts/stack-copy.sh`, `packages/cli/tests/stack-copy.test.mjs`,
+  `packages/webui/tests/pinned-copy.test.mjs`. The other 19 are byte-identical to r2.
+- Singles on the new base (`singles-r3.log`): every touched test file plus the unslop selftest, all green.
+  `packages/bus/tests/channel-proof.test.mjs` pins plug-in hashes and names `index.mjs`; it reads only channel
+  plug-ins, not the two harness files this row changes, and it passes (2/0).
+- Still to do: the full gate on my slot after the MVP gates, then the landing sessions on both harnesses that
+  the row's gate names.
+
+What I ask the reviewers: confirm the rebase. In the four drifted files, check that row 66's hunks sit correctly
+next to rows 190 and 192 (`stack-copy.sh` COPY_PATHS in particular). Nothing else changed.

agents/sage/work/queue-66/candidate-manifest-r3.sha256

@@ -0,0 +1,23 @@
+b99e7f4bf58ac68c8f5fa58eb7b90c0f85b15ca9a80fd093f6aaeafeac931608  adapters/README.md
+c32d2a3276db92433d4e3c4f4b45fab048d9a46119d9f69cead6a11cfacfeadb  agents/sage/work/queue-66/BUILD.md
+ac318150f5e6193adf3750d76b64c643c29f324310c4004b0bdde8caef863b53  docs/TOOLS.md
+64a2d00ba57b8673c0905f322711023c10d4dfdc0ccc7e6daa2c440b4d57e34e  packages/cli/tests/stack-copy.test.mjs
+b027dc74583217b4151173ecbabfcfbfc7b108ac6b7a8e93dd21a2834051714f  packages/harness/README.md
+bfb2156c609eeaf87c9e209c562576a5ef47535eaeee61d841bb0bd75a76a69d  packages/harness/src/runner.mjs
+0a27f2c8de7b9191f9c0d4a209331c63ff7630923e669838b41715924b0a64b0  packages/harness/tests/bundle.test.mjs
+81d0352f2dcd41eb2e2ef962365d9b97515d7e8d9668a35bb9ce9dce4f1451ea  packages/harness/tests/claude-session.test.mjs
+b16f33442cefd5b5ae2af85edab33250ee6b31025e437edf0e4eba9fe0afa793  packages/harness/tests/fixtures/fake-adapter.mjs
+1e187a2e23a197640d139e6975dfaf83dd7e337c360d128833678dc60f3e2046  packages/harness/tests/pi-session.test.mjs
+37ca6ad6467573658c1ac6807b6cd00e3f9da289107fb689190a1872bff9b89c  packages/harness/tests/runner.test.mjs
+04c24058f37260c9192d5036c8cf28b50faba8e3e3bf57f198d233485d0d57e6  packages/plugins/harness/claude-code/index.mjs
+2c1252e8e8db3ba4551bf1e34156ddf4e933cc664fc157105bef9a2705d6ce3b  packages/plugins/harness/pi/index.mjs
+7e0bea27d4360a39874fa64b3506a85f83888613a285ec0b087d74bf22b76421  packages/plugins/README.md
+ec4ec9502ee8e766e3abd04d9f724c0d8ff4ef114394a0f76d5320c2dc715c5c  packages/plugins/tests/harness.test.mjs
+f6141dac9a8c61573e4198480fed85e093992ee9c19fb55e9bc2752381b7b07a  packages/seat/tests/sandbox.test.mjs
+09c6cadaf2e27677c95ba5bcb6a359cb6b3ce596ba1db6171b26586d4f9834a8  packages/webui/tests/pinned-copy.test.mjs
+e9ff91cd073a1b784f9ea440b18db913ce8107df6246e3b0b0e962eda43f046b  scripts/stack-copy.sh
+7ee6ed6e6ac55b1348d40a358372e66c86fdebacd90001d447040133e1187882  tools/unslop-hook/claude-hook.js
+ce1dfb11d0a8e8efd3d6dae67cc259c2e7443a62c7416bdedd4c71306d8c6df1  tools/unslop-hook/extension.ts
+f07d67806f40763b4be87d31c2976448b5cfc34d7328519fae2d8313b1ca3e20  tools/unslop-hook/README.md
+dbe3d5c9ae654d2401e3c496a6b03757a438e4a551fd8e460df8c82902bb80a7  tools/unslop-hook/test-unslop-check.js
+76be78178a0703b9d20a7df2278ecb13f429dea90cea45180f22302e267ea25e  tools/unslop-hook/unslop-check.js

agents/sage/work/queue-66/singles-r3.log

@@ -0,0 +1,11 @@
+packages/cli/tests/stack-copy.test.mjs rc=0 ℹ pass 14 ℹ fail 0 
+packages/harness/tests/bundle.test.mjs rc=0 ℹ pass 22 ℹ fail 0 
+packages/harness/tests/claude-session.test.mjs rc=0 ℹ pass 10 ℹ fail 0 
+packages/harness/tests/pi-session.test.mjs rc=0 ℹ pass 10 ℹ fail 0 
+packages/harness/tests/runner.test.mjs rc=0 ℹ pass 39 ℹ fail 0 
+packages/plugins/tests/harness.test.mjs rc=0 ℹ pass 9 ℹ fail 0 
+packages/seat/tests/sandbox.test.mjs rc=0 ℹ pass 10 ℹ fail 0 
+packages/webui/tests/pinned-copy.test.mjs rc=0 ℹ pass 10 ℹ fail 0 
+unslop rc=0 28/28 passed
+SINGLES_DONE
+2026-10-20T23:15:14Z

agents/sage/work/slice1-acceptance/run-log.md

@@ -196,3 +196,37 @@ a piece. It passed, so the "pm doesn't answer" branch does not apply and
 no defect is filed.
 
 Piece 1 is Jason's next real Mosaic Stack request to pm. It is not open yet.
+
+## 2026-10-21T01:14Z dates (sage-1622, Mos mos-1148, Vikunja #442)
+
+Mos accepted the plan with changes C1 and C2. The dates are latest-by markers (Q111).
+
+1. Pieces 1-5 open by 2026-10-23 23:59Z. Mos gives Jason the plain command after tonight's open items with him
+   (Q13 on PRD 1.8, the 1012 and 1008 boot). I don't ask again.
+2. C1: no piece is pinned to a copy. A piece runs on whatever copy is live when Jason sends it. For each piece
+   this log records the activation id at send. A piece still open across a window gets the new activation id
+   recorded too.
+3. C2: neither the Q175 phase 2 window (10-23) nor the 10-24 re-pin window rolls back or restores while a piece
+   has history, unless that window has failed. If a restore happens anyway, this log names the pieces to redo.
+4. All five closed and reviewed by 2026-10-26 18:00Z. Jason reads the five trails at his gate on 10-26 or
+   10-27. A pass starts merge plan step 1 under decision 146, and step 4 stays his.
+5. Fallback: if fewer than five pieces are open by 10-23, the gate moves to 10-28. No agent opens a piece in
+   Jason's place.
+
+When Jason sends a piece, I tell Mos its message id.
+
+Correction (2026-10-21T01:06Z): the heading above says 01:14Z. The clock read 2026-10-21T01:05:56Z when I wrote that entry, so 01:06Z is the right time.
+
+## 2026-10-21T01:20Z Jason's pre-S7 checks (mos-1154)
+
+Between 01:11:06Z and 01:13:03Z Jason sent pm five requests with `mosaic talk pm`: ed9e1e14, 51c19692,
+94f5d62c, 0645a3b7, f75449c0 (bus seq 1583 to 1591). pm run rc9e993da24cf answered each in 4 to 16 s. They were
+two jokes, the sandwich, the purpose of Mosaic Stack and pm's mission. pm made no task and raised no decision
+for any of them, and said so each time. Mos's reading, which I take: none is a piece, because a piece has to
+become work that gets closed and reviewed. They are recorded as Jason's pre-S7 checks. The five pieces are
+still open, latest-by 10-23 23:59Z. Activation at send: copy 4429a104f, as in the 01:06Z entry (C1). Source: Mos
+(mos-1154) read the bus. I didn't read the message bodies.
+
+pm also told Jason that its state snapshot lists only the first 50 of 198 open tasks and that it pages the rest
+with list_tasks. That is the row 109 (#1603) design: broker.mjs `state` returns `cap: TASK_PAGE` (50) with
+`total`, and list_tasks pages up to TASK_PAGE_MAX (200).

agents/sage/work/vikunja-setup/catchup-2026-10-20.json

@@ -0,0 +1,27 @@
+{
+ "at": "2026-10-20T23:19:35.714Z",
+ "comments": [
+  {
+   "task": 413,
+   "status": 201,
+   "id": 411,
+   "readBack": 200,
+   "found": true
+  },
+  {
+   "task": 424,
+   "status": 201,
+   "id": 412,
+   "readBack": 200,
+   "found": true
+  },
+  {
+   "task": 414,
+   "status": 201,
+   "id": 413,
+   "readBack": 200,
+   "found": true
+  }
+ ],
+ "problems": []
+}

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

@@ -0,0 +1,51 @@
+// Sage, 2026-10-20: row 192 (Q175 phase 1, #1690) landed. One comment on P19 412, 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-412-r192-landed.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: 412, title: /^Console SSO: zero-trust OIDC verification/, body: [
+    "Row 192 (Q175 phase 1, Gitea #1690) landed and pushed. Landing commit 4429a104f (Launchpad's launchpad/row192 53bb59462..37582e820, manifest round 2, 18 paths; Webby approved). Patch-id 4a486902614d matches the reviewed diff. Queue revs 2429-2430 (landing note and done) are in 305857c8f, range 32b54ac3b..305857c8f on refactor. #1690 is closed.",
+    "Sage gate on 088087ac9: package suites 2758 pass 0 fail, scripts/test-*.sh 429 pass 0 fail, mutants 22 of 23 killed (#23, the second origin check, ruled equivalent). The Console now verifies SSO itself under --sso as an OIDC relying party on oauth4webapi 3.8.8, pinned exactly. mosaic-config.mjs load is now async, so in-flight rows that call it rebase and await it (row 190 round 3 is doing this).",
+    "Not live. The live stack still runs copies/490e2771d3d0. The new dependency needs npm ci in a new stack copy, so the live re-pin is a window with Mos (mos-1099 item 3); Sage sends Mos the plan. Row 200 (phase 2) follows.",
+  ] },
+];
+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/comment-catchup-2026-10-20.mjs

@@ -0,0 +1,59 @@
+// Sage, 2026-10-20: catch-up landing and status comments on P19 413 (row 189), 424 (row 210) and 414 (rows 201
+// and 204), per mos-0882. Sage's own key (bot user 13); the sync key reads back. Comments only: no task edits.
+// Checks each task's title before posting. Prints no secret.
+// Usage: node comment-catchup-2026-10-20.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: 413, title: /^stack-release\.sh activate --no-send/, body: [
+    "Row 189 landed on refactor as ace27dc5e (Gitea #1687): stack-release.sh activate --no-send drops the Console's --send and keeps the pointer and the unit in step. Dewey approved (comment 29485), and Sage's gate passed.",
+    "The stack activation log shows the same-copy activate on 490e2771d3d0 after the landing: activation 20261020T192956Z-490e2771d3d0, result ok at 19:30:00Z, with backup 20261020T192956Z-490e2771d3d0. Since then the live Console runs without --send. The re-pin to 4429a104f at 22:02Z (row 192) carried the pointer's flags, no --send and no --sso, as its W3 plan check required.",
+  ] },
+  { id: 424, title: /^Credential store: per-agent host access/, body: [
+    "Status, 2026-10-20 23:20Z. Row 210 (Gizmoduck) builds this task. Its design r3 is approved, and the machine-grant design final r6 f9039682e is approved for code once row 210 lands (mos-1141, mos-1143). Every grant name sits under grant.* behind one guard (mos-1144). No agent creates a grant: the chief requests, Jason approves, and protected code creates it (Q188).",
+    "Order (mos-1135, mos-1137): row 210 lands only after row 199, the per-agent credential store. Row 199's gate is green on c6868ba41. Megavolt fixed five surviving mutants and is rerunning all 28 now on 7c3cdd940, before the Duckworth review. Rows 190, 199 and 210 go live together in the one 10-24 window with the 3i-3j migration (mos-1145 line 9), backup first, under Q173.",
+  ] },
+  { id: 414, title: /^MVP platform: the Given list for Cases 1 and 2/, body: [
+    "RBAC rows landed (Given list, RBAC enforcement). Row 201, FED R1: access.json loader and validator with covers, afad4993f (Gitea #1699), Gizmoduck, Duckworth approved (comment 29581). Gate: business 173/0, scripts/test-*.sh 422/0, mutants 44 of 44 killed.",
+    "Row 204, 193a: the access level check widened to viewer, d0bbc5c1c (Gitea #1702), Morgana, Duckworth approved (comment 29595). LEVELS gains collaborator and viewer, covers() takes a required least level, and an unknown grant level covers nothing. Gate: packages and scripts 2789/0, mutants 7 of 7 killed.",
+    "Neither changes the live stack. Rows 205-208 (193b1 to 193d) follow, and 206 adds a schema step, so it goes live only in a --migrate window.",
+  ] },
+];
+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/comment-p19-405-411-replan.mjs

@@ -0,0 +1,60 @@
+// Sage, 2026-10-21: re-plan comments on P19 405-408 and 411 (due 10-22). Sage's own key (bot user 13); the sync key reads back. Comments only: no task edits.
+// Checks each task's title before posting. Prints no secret.
+// Usage: node comment-p19-405-411-replan.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: 405, title: /^stack-release --plan: no test plans a missing store/, body: [
+    "Re-plan (Sage, 2026-10-21, due 10-22). Tasks 405, 406, 407, 408 and 411 become one queue row, a stack-release follow-up row. All five touch scripts/stack-release.sh, scripts/webui-service.sh or docs/TOOLS.md, and rows 232 (Darkwing) and 238 (Launchpad) are changing stack-release.sh now. So I brief the row after 232 and 238 land, from their landing, which avoids base drift (the row 68 rule). It lands after the 10-24 window, because that window holds the four service scripts at NEW (P5). 411's hold was the Part B window, and Part B is superseded (Q175, mos-0970), so that hold is gone. Each item keeps the test and mutant its task names. I'll name the owner when I brief it, either the seat that frees up first of Darkwing and Launchpad, or me.",
+  ] },
+  { id: 406, title: /^stack-release --plan: backup line printed/, body: [
+    "Re-plan (Sage, 2026-10-21, due 10-22). Tasks 405, 406, 407, 408 and 411 become one queue row, a stack-release follow-up row. All five touch scripts/stack-release.sh, scripts/webui-service.sh or docs/TOOLS.md, and rows 232 (Darkwing) and 238 (Launchpad) are changing stack-release.sh now. So I brief the row after 232 and 238 land, from their landing, which avoids base drift (the row 68 rule). It lands after the 10-24 window, because that window holds the four service scripts at NEW (P5). 411's hold was the Part B window, and Part B is superseded (Q175, mos-0970), so that hold is gone. Each item keeps the test and mutant its task names. I'll name the owner when I brief it, either the seat that frees up first of Darkwing and Launchpad, or me.",
+  ] },
+  { id: 407, title: /^stack-release\.sh: the proof_for_target comment/, body: [
+    "Re-plan (Sage, 2026-10-21, due 10-22). Tasks 405, 406, 407, 408 and 411 become one queue row, a stack-release follow-up row. All five touch scripts/stack-release.sh, scripts/webui-service.sh or docs/TOOLS.md, and rows 232 (Darkwing) and 238 (Launchpad) are changing stack-release.sh now. So I brief the row after 232 and 238 land, from their landing, which avoids base drift (the row 68 rule). It lands after the 10-24 window, because that window holds the four service scripts at NEW (P5). 411's hold was the Part B window, and Part B is superseded (Q175, mos-0970), so that hold is gone. Each item keeps the test and mutant its task names. I'll name the owner when I brief it, either the seat that frees up first of Darkwing and Launchpad, or me.",
+  ] },
+  { id: 408, title: /^docs\/TOOLS\.md: the row 178 paragraph/, body: [
+    "Re-plan (Sage, 2026-10-21, due 10-22). Tasks 405, 406, 407, 408 and 411 become one queue row, a stack-release follow-up row. All five touch scripts/stack-release.sh, scripts/webui-service.sh or docs/TOOLS.md, and rows 232 (Darkwing) and 238 (Launchpad) are changing stack-release.sh now. So I brief the row after 232 and 238 land, from their landing, which avoids base drift (the row 68 rule). It lands after the 10-24 window, because that window holds the four service scripts at NEW (P5). 411's hold was the Part B window, and Part B is superseded (Q175, mos-0970), so that hold is gone. Each item keeps the test and mutant its task names. I'll name the owner when I brief it, either the seat that frees up first of Darkwing and Launchpad, or me.",
+  ] },
+  { id: 411, title: /^stack-release\.sh and webui-service\.sh: the proof file repository check/, body: [
+    "Re-plan (Sage, 2026-10-21, due 10-22). Tasks 405, 406, 407, 408 and 411 become one queue row, a stack-release follow-up row. All five touch scripts/stack-release.sh, scripts/webui-service.sh or docs/TOOLS.md, and rows 232 (Darkwing) and 238 (Launchpad) are changing stack-release.sh now. So I brief the row after 232 and 238 land, from their landing, which avoids base drift (the row 68 rule). It lands after the 10-24 window, because that window holds the four service scripts at NEW (P5). 411's hold was the Part B window, and Part B is superseded (Q175, mos-0970), so that hold is gone. Each item keeps the test and mutant its task names. I'll name the owner when I brief it, either the seat that frees up first of Darkwing and Launchpad, or me.",
+  ] },
+];
+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/comment-r200-r199-landed.mjs

@@ -0,0 +1,53 @@
+// Sage, 2026-10-21: landing comments on P19 412 (row 200) and 424 (row 199), per mos-0882. Sage's own key (bot user 13); the sync key reads back. Comments only: no task edits.
+// Checks each task's title before posting. Prints no secret.
+// Usage: node comment-r200-r199-landed.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: 412, title: /^Console SSO: zero-trust OIDC verification/, body: [
+    "Row 200 landed on refactor as 9e1085816 (Gitea #1698, closed): stack-release.sh activate --sso, the phase 2 prerequisite. Launchpad built it and Webby approved r3. Sage's run killed 13 of 14 mutants (M12 is the equivalent ruled in round 2). Gate: 15 package suites and 10 scripts/test-*.sh suites, all green, at 00:07:57Z.",
+    "Follow-up N1 is row 238 (Gitea #1744, Launchpad, Webby). The sso-config hint will carry --instance NAME for a named instance. Nothing is live until a window activates a copy that includes 9e1085816.",
+  ] },
+  { id: 424, title: /^Credential store: per-agent host access/, body: [
+    "Row 199 landed on refactor as cb5fdb064 (Gitea #1697, closed). It adds the per-agent credential store, the agent's own git identity and pushes to a remote. Megavolt built it and Duckworth approved r1 (comment 29779). Gate on 9e1085816 plus the patch: packages 2735/0, scripts 429/0.",
+    "Row 210 (Gizmoduck) now rebases onto cb5fdb064 on a new branch (mos-1135, mos-1137). Rows 234 and 235 follow it. Rows 190, 199 and 210 go live together in the 10-24 window with the 3i-3j migration, backup first, under Q173 (mos-1145).",
+  ] },
+];
+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/comment-w11-r190-2026-10-20.mjs

@@ -0,0 +1,66 @@
+// Sage, 2026-10-20: W11 of the re-pin window 490e2771d to 4429a104f (STATE.md in commit 99a406ed3) on P19 386, 412
+// and 393, and the row 190 landing (00d4cc1f6, #1688) on P19 414, per mos-0882. Sage's own key (bot user 13); the
+// sync key reads back. Comments only: no task edits. Checks each task's title before posting. Prints no secret.
+// Usage: node comment-w11-r190-2026-10-20.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 STATE = "agents/sage/work/window-repin-4429a104f/STATE.md in commit 99a406ed3 (pushed), sha256 a4d0a7b12f431f15";
+const POSTS = [
+  { id: 386, title: /^Q173 test system: tester writes/, body: [
+    "Q173 re-pin window, 490e2771d to 4429a104f (row 192), done. STATE report: " + STATE + ".",
+    "Activation 20261020T220206Z-4429a104f6d6 with --pm, exit 0, every gate check including pm_launched. Store stays on 3i, migration none. Backup ~/.mosaic-dev/backups/stack/20261020T220206Z-4429a104f6d6 (SHA256SUMS b61d6484), rollback set beside it; rollback would go to 490e2771d. Business file unchanged (sha256 1e49bdf0). Console flags unchanged: no --send, no --sso, --tester-port 7333.",
+    "W0 to W10 passed, nothing rolled back. W10 stopped once on two browser checks; both were checks written before row 192 (the hidden #sign-out link, and a chat check that read only the first project list). Mos passed them (mos-1135) and the corrected checks are in the plan. Matrix line g is 6575 bytes, not 6454, because row 192 grows index.html by 121 bytes; Mos passed it (mos-1137).",
+    "S1 to S2 store deltas include task_snapshots +7 and task_comment_cursors +5. The writer is the bus's Vikunja poll (packages/tasks/src/adapter.mjs tick, sync.mjs recordTask), source 'poll', not the window. Nobody acted as Jason: no --by jason, no pi, no Save, no mosaic name, bus.tester untouched.",
+  ] },
+  { id: 412, title: /^Console SSO: zero-trust OIDC verification/, body: [
+    "Row 192 (Q175 phase 1) is live in copy 4429a104f since activation 20261020T220206Z (Q173 window with Mos). The sign-in code is in the copy but dormant: the Console runs without --sso, and the proof pair stays unset. The new oauth4webapi 3.8.8 dependency came in through npm ci in the new copy and imports cleanly from it.",
+    "STATE report: " + STATE + ". The webui journal since activation shows one 'Proxy: proxy proof off' line and no 'Sign-in:' line, as expected without --sso.",
+  ] },
+  { id: 393, title: /^dragon-lin: seven legacy user units in failed state/, body: [
+    "Current failure times read during the Q173 re-pin window W11 (systemctl --user show, CDT with UTC): mosaic-standup-pm.service failed 2026-10-19 19:00:28 CDT (10-20 00:00:28Z), exit 1. mosaic-install-drift.service failed 2026-10-20 00:12:54 CDT (05:12:54Z), exit 9. [email protected] failed 2026-10-20 13:16:12 CDT (18:16:12Z), exit 4.",
+    "The marker's journal at 18:16:12Z says its tmux send to jarvis failed ('tmux target not found', socket mosaic-fleet), so that page never arrived; the record is in ~/.local/state/mosaic-unit-failures/20261020.jsonl. mosaic-reconcile.service itself last ran OK at 17:16:27 CDT (22:16:27Z), so the marker is stale until reset.",
+    "All three predate the re-pin at 22:02Z and come from the legacy ~/.mosaic and jarvis-brain setup. The window changed none of them. Disabling or resetting any still needs Jason or ops-01's charter. Details: " + STATE + ", section 'Failed user units'.",
+  ] },
+  { id: 414, title: /^MVP platform: the Given list for Cases 1 and 2/, body: [
+    "Row 190 (several Mosaic Stack instances on one host, MVP T1.1, Gitea #1688) landed and pushed: 00d4cc1f6 on refactor (99a406ed3..00d4cc1f6). Squash of Darkwing's darkwing/row190-r3 176a6bf4b..df65a3d4c, 25 paths, manifest cc0ea9e8, Filbert approved round 3; patch-id matches the branch diff.",
+    "Sage gate on d0bbc5c1c with the patch: 15 package suites 2664 pass 0 fail, 10 scripts/test-*.sh suites 429 pass 0 fail. Mutants 20 of 20 killed. Not live: the stack runs copy 4429a104f until a re-pin. Row 230 (C2-13a) now carries row 190's @CONFIG_ENV@ and @SESSION_ENV@ tokens (gosalyn-0058 item 4).",
+  ] },
+];
+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-r237-followups.mjs

@@ -0,0 +1,66 @@
+// Sage, 2026-10-21: files row 237's review follow-ups N1 and N3 (duckworth-0069, #1743 comment 29810) as two P19 tasks.
+// 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-r237-followups.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 TASKS = [
+  {
+    title: "Bus publish: a retry after publish-timeout can push a second fork ref while the first push still runs (row 237 N1)",
+    description: ps(SIG, [
+      "Duckworth's row 237 review N1 (#1743 comment 29810, duckworth-0069). Row 237 makes checkPublish refuse publish-busy while an open ticket holds the same business and decision. publishRefused drops the ticket on publish-timeout, but the bus process's push may still be running, so a retry to another branch can push a second ref to the fork.",
+      "The fix belongs in packages/bus/src/runtime.mjs, in `remotes`: either keep the ticket until the push process exits, or kill the push on timeout and wait for it. A test should start a slow push, time it out, retry to another branch, and expect one ref on the fork. Not in row 237's scope. Megavolt's BUILD.md residual 2 (agents/megavolt/work/queue-237/BUILD.md). Needs a queue row once 237 lands.",
+    ]),
+  },
+  {
+    title: "Bus land: check whether checkLand has the same open-ticket race that row 237 fixed in checkPublish (row 237 N3)",
+    description: ps(SIG, [
+      "Row 237 residual 3 (Megavolt's BUILD.md) and Duckworth's N3 (#1743 comment 29810): checkLand has the same ticket shape as checkPublish had before row 237. Two lands on the same decision may both pass the check before either records. Duckworth didn't check it.",
+      "First step: read checkLand and its ticket code in packages/bus/src/broker.mjs against row 237's fix (broker.mjs:1038-1043). If the race exists, file a queue row with a race test like publish-socket.test.mjs's; if not, record why and close this task.",
+    ]),
+  },
+];
+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);
+};
+const have = await existing();
+for (const T of TASKS) if (have.some((t) => t.title === T.title)) throw new Error("title exists; refusing");
+writeFileSync(OUT, "", { flag: "wx" });
+rec.created = [];
+for (const T of TASKS) {
+  const r = await api("PUT", `/api/v1/projects/${PROJECT}/tasks`, { title: T.title, description: T.description }, key);
+  const c = { status: r.status, id: r.json?.id ?? null };
+  rec.created.push(c);
+  if (r.status >= 300 || !Number.isSafeInteger(r.json?.id)) { rec.problems.push(`create: ${r.status} ${r.json?.message ?? ""}`); continue; }
+  const back = await api("GET", `/api/v2/tasks/${r.json.id}`, undefined, sync);
+  Object.assign(c, { readBack: back.status, done: back.json?.done });
+  if (back.status !== 200 || back.json?.title !== T.title || back.json?.done) rec.problems.push(`read-back differs for ${r.json.id}`);
+}
+save();
+console.log(JSON.stringify(rec));

agents/sage/work/vikunja-setup/p19-405-411-replan-2026-10-21.json

@@ -0,0 +1,41 @@
+{
+ "at": "2026-10-21T01:06:25.071Z",
+ "comments": [
+  {
+   "task": 405,
+   "status": 201,
+   "id": 416,
+   "readBack": 200,
+   "found": true
+  },
+  {
+   "task": 406,
+   "status": 201,
+   "id": 417,
+   "readBack": 200,
+   "found": true
+  },
+  {
+   "task": 407,
+   "status": 201,
+   "id": 418,
+   "readBack": 200,
+   "found": true
+  },
+  {
+   "task": 408,
+   "status": 201,
+   "id": 419,
+   "readBack": 200,
+   "found": true
+  },
+  {
+   "task": 411,
+   "status": 201,
+   "id": 420,
+   "readBack": 200,
+   "found": true
+  }
+ ],
+ "problems": []
+}

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

@@ -0,0 +1,13 @@
+{
+ "at": "2026-10-20T21:35:49.240Z",
+ "comments": [
+  {
+   "task": 412,
+   "status": 201,
+   "id": 395,
+   "readBack": 200,
+   "found": true
+  }
+ ],
+ "problems": []
+}

agents/sage/work/vikunja-setup/r200-r199-landed-2026-10-21.json

@@ -0,0 +1,20 @@
+{
+ "at": "2026-10-21T00:28:32.038Z",
+ "comments": [
+  {
+   "task": 412,
+   "status": 201,
+   "id": 414,
+   "readBack": 200,
+   "found": true
+  },
+  {
+   "task": 424,
+   "status": 201,
+   "id": 415,
+   "readBack": 200,
+   "found": true
+  }
+ ],
+ "problems": []
+}

agents/sage/work/vikunja-setup/r237-followups-2026-10-21.json

@@ -0,0 +1,19 @@
+{
+ "at": "2026-10-21T00:38:47.170Z",
+ "project": 19,
+ "created": [
+  {
+   "status": 201,
+   "id": 440,
+   "readBack": 200,
+   "done": false
+  },
+  {
+   "status": 201,
+   "id": 441,
+   "readBack": 200,
+   "done": false
+  }
+ ],
+ "problems": []
+}

agents/sage/work/vikunja-setup/read-tasks.mjs

@@ -0,0 +1,16 @@
+// Sage, 2026-10-21: read-only. Prints id, done, title, the last update and the description as plain text for the
+// given P19 tasks, with the sync key. Writes nothing. Prints no secret.
+// Usage: node read-tasks.mjs https://tasks.woltje.com SYNC_TOKEN_FILE ID...
+import { readFileSync } from "node:fs";
+const [ORIGIN, SYNC, ...IDS] = process.argv.slice(2);
+if (!/^https:\/\/tasks\.woltje\.com$/.test(ORIGIN)) throw new Error("tasks.woltje.com only");
+const sync = readFileSync(SYNC, "utf8").trim();
+const text = (h) => (h ?? "").replace(/<\/p>|<br\s*\/?>|<\/li>/g, "\n").replace(/<[^>]+>/g, "").replace(/&lt;/g, "<").replace(/&gt;/g, ">").replace(/&amp;/g, "&").trim();
+for (const id of IDS) {
+  const r = await fetch(`${ORIGIN}/api/v2/tasks/${id}`, { headers: { Authorization: `Bearer ${sync}` }, redirect: "error" });
+  const j = await r.json().catch(() => null);
+  if (r.status !== 200 || j?.project_id !== 19) { console.log(`== ${id}: status ${r.status}, not P19`); continue; }
+  const out = `== ${id} done=${j.done} updated=${j.updated}\n${j.title}\n${text(j.description)}\n`;
+  if (out.includes(sync)) throw new Error("secret in output");
+  console.log(out);
+}

agents/sage/work/vikunja-setup/w11-r190-2026-10-20.json

@@ -0,0 +1,34 @@
+{
+ "at": "2026-10-20T22:51:44.218Z",
+ "comments": [
+  {
+   "task": 386,
+   "status": 201,
+   "id": 406,
+   "readBack": 200,
+   "found": true
+  },
+  {
+   "task": 412,
+   "status": 201,
+   "id": 407,
+   "readBack": 200,
+   "found": true
+  },
+  {
+   "task": 393,
+   "status": 201,
+   "id": 408,
+   "readBack": 200,
+   "found": true
+  },
+  {
+   "task": 414,
+   "status": 201,
+   "id": 409,
+   "readBack": 200,
+   "found": true
+  }
+ ],
+ "problems": []
+}

agents/sage/work/window-plan/repin-1024-draft0.md

@@ -0,0 +1,90 @@
+# 10-24 window: re-pin 4429a104f to the row 234 landing, with the 3i-3j migration (draft 0)
+
+Sage, 2026-10-21T01:05Z, draft 0, for mos-1145 under DECISIONS Q173. This is the skeleton. NEW isn't fixed yet,
+so Mos doesn't check this draft. Draft 1 names NEW and goes to Mos for the P0 check. The step layout follows
+`repin-4429a104f.md`. Steps that match are named, not copied.
+
+## Scope (mos-1145, mos-1134)
+
+- One window carries the code of rows 190, 199 and 210, plus row 234 (row a) with its schema step 3i to 3j
+  through `activate --migrate`, agent-run under Q173, backup first.
+- Row a lands before the .53 and .54 installs, by 10-25 (mos-1134). If row 234 hasn't landed by 10-24 12:00Z,
+  I ask Mos whether to run the window without it (no migration) or to move it.
+- Jason has no step. Nobody acts as Jason. No pi (P19 383). No Save, no `mosaic name`. Nothing is pruned.
+- `--sso` stays off. Row 200's `activate --sso` is in NEW as a tool. Turning it on changes who reaches the Console
+  from outside, so that's Jason's (Q173 exclusion). It has its own window, the Q175 phase 2 window on 10-23
+  (mos-1148). That window runs first, so this window's OLD may be the phase 2 copy, and P1 reads it from
+  `status`.
+
+## Names
+
+- OLD, live: `4429a104f6d65ccf165f6c83b5d1dce3147dfde0`, schema 3i, pointer `pm: true` (record 99a406ed3).
+  P1 re-reads the activation id and the Console flags from `status`. I don't copy them from the last window.
+- NEW: `c771a36f4bd0b6c359282425c668996a90072f93`, the row 234 landing (2026-10-21 06:16Z), unless Mos rules a
+  later code landing. 194 is the open candidate. 210, 237, 232, 241, 242, 233 and 234 have landed.
+- REPO, `P`, `WIN=agents/sage/work/window-repin-<NEW12>/`, `SNAP`: as in `repin-4429a104f.md`, with the
+  sha checks at P0 and before S1, S2 and any D3.
+
+## What NEW carries over OLD (refactor c771a36f4)
+
+`git log --first-parent 4429a104f..HEAD`, path-limited to packages, scripts, roles, contracts, adapters, skills
+and the package files:
+
+| Row | Commit | Live effect to check |
+|---|---|---|
+| 201 | afad4993f | business: access.json loader. Check: the live business has no access.json, and load stays LOAD_OK (P1). |
+| 204 | d0bbc5c1c | business: 193a viewer level. Same check. |
+| 190 | 00d4cc1f6 | Several instances per host. Touches `stack-release.sh`, `webui-service.sh`, `bus-service.sh`, `stack-copy.sh`. The default instance must render the same units: P2 diffs the rendered units OLD vs NEW for `mosaic-stack`, and any difference stops the window until it's explained. |
+| 200 | 9e1085816 | Tool: `activate --sso`. Off here. `--plan` must show no `--sso` line. |
+| 199 | cb5fdb064 | Credential store per agent. Check: bus start with no store entries for the live agents changes nothing, and the chief's and pm's launches still pass. The P3 rehearsal covers start. |
+| N3 | 390ea5261 | README only. |
+| 230 | c8bc5cf4c | Case 2 scripts, tools only. Not run live. |
+| 210 | f5753c0e8 | Host access. The live business has no `hosts`, so nothing is granted. Bus start runs the host-run sweep (M34d). P3 must show it removes nothing. |
+| 237 | d7d943199 | Publish busy check (199 N1). |
+| 232 | e65a3ab4d | Installer I1: `stack-release.sh --units external` and `stack-copy.sh copy --bundle`, `wrapper --create`. Both are opt-in, and this window uses neither. The default units path must render the same units, so the P2 unit diff covers it with row 190. P0 checks that no window command line carries `--units external`. |
+| 241 | 5d4a61776 | Test only (bus land.test.mjs). No live effect. |
+| 242 | 5fb736b92 | Bus publish hold: after publish-timeout the bus holds the decision until its push ends, then records a late push. The live business has no publish in flight at W1, and P3 shows none open. Its follow-up fc1cb856b is comments only (git-socket.mjs). |
+| 233 | 57f59e0c3 | Installer I3: new tool `scripts/stack-upgrade.sh` and a `stack-release.sh` change. This window doesn't run `stack-upgrade.sh`. The P2 unit diff covers the `stack-release.sh` change with rows 190 and 232. |
+| 234 | c771a36f4 | Machine grant row a and the 3i to 3j schema step (new tables `hosts` and `host_grants`). `--plan` must say `migration: 3i -> 3j`. |
+| PRD 1.7+1.8 | 0adf8ddfe | `docs/prd/mosaic-stack.md` and `packages/tasks/requirements.json` move to version 1.8 (mos-1154, mos-1156, DECISIONS Q192). The live pm cites 1.6 until this window. Check after: the pm's requirements read answers version 1.8. |
+
+Service script drift OLD to HEAD is 415+/91- over the four scripts, mostly row 190. P5 holds them at NEW.
+
+## Backups and the migration
+
+- W5: the stopped store backup that every activate takes (row 185), with SHA256SUMS, SCHEMA 3i and STAMP,
+  plus the rollback set. Before `--migrate` writes, I check that SCHEMA reads 3i and the backup SHA256SUMS hash.
+- W0b: the business file copy, as in the last window.
+- Rollback after a migration isn't the plain rollback. OLD is 3i and the store is 3j, so going back needs
+  `--restore <W5 activation>`, and that loses the events written after W5. The row 181 restore guard counts
+  11 tables, and the untimed ones need the D3 snapshot. Row 234 adds `hosts` and `host_grants` to the untimed
+  list (T46), so at 3j the D3 snapshot covers them too. Draft 1 recounts the list from NEW. Mos decides any restore past W5, as before.
+- Grant look-alikes (row 234 A22b, gizmoduck-0107). `3i-3j.sql` adds `events_grant_actor` but doesn't check
+  rows already in the store, so after the migration only the actor filter in `GRANT_EVIDENCE` (actor_role NULL,
+  actor_run 'grant') ignores an old session-written row. P3, and again just before `--migrate`: on the
+  backup copy, count the `action.allowed` events whose body.action or body.operation starts with `grant.`, or
+  whose body has `hostLineLeft`. Expect 0, since no grant code has run live. Any nonzero count stops the window
+  until I've read those rows.
+- P3 is the rehearsal with `--migrate` on a copy of the live backup. It must show the 3j step and the row
+  counts before and after.
+
+## Row 42 (S7) interaction
+
+Row 42's pieces may be in flight at window start (sage-1622, mos-1148 C1 and C2). W1 adds: list open pm tasks, and either pm
+finishes or parks them before W5, or I record which piece crosses the window. No restore while a piece has
+history unless the window fails.
+
+## Open before draft 1
+
+- Q1, ruled by mos-1161: draft 1 doesn't wait for 194. NEW is the latest code landing when I cut draft 1. If
+  194 has landed with a green full gate (15 packages, ten script suites), NEW is the 194 landing and P3 also runs
+  the lifecycle verbs once on the backup copy and gets one pm reply under the new roles/chief-of-staff files. A
+  P3 failure that traces to 194 drops NEW back to c771a36f4 before anything touches live, and the window goes on.
+  Otherwise NEW is c771a36f4 and 194 rides a later window.
+- Q2, settled by mos-1148: phase 2 is its own window on 10-23. Draft 1 takes OLD and the Console flags,
+  `--sso` included, from `status` after that window.
+- Q3: who operates. If Darkwing is free, Darkwing operates and I check. Otherwise I operate as in the last
+  window.
+- The P-step evidence list for rows 199 and 210 at bus start. Both have landed (cb5fdb064, f5753c0e8), so
+  it's due in draft 1. I take each log line and exit code from a P3 rehearsal run, not from the code.
+- Rows 241 and 242 (bus): P3 shows no publish or land decision open before W5.

agents/sage/work/window-plan/repin-4429a104f.md

@@ -0,0 +1,125 @@
+# Re-pin 490e2771d to 4429a104f (row 192, Q175 phase 1), with npm ci in the new copy
+
+Sage, 2026-10-20, draft 1, for mos-1099 item 3 under DECISIONS Q173. Mos checks this file at its commit before
+P0. Any change to this file or to NEW after the check means Mos checks again (mos-0849/0850).
+
+This is a smaller window than `repin-rows-177-185.md` (draft 2, which Mos checked in mos-0929). Where a step is
+the same, this file names that file's step and says what differs. The 7332 matrix, the snapshot, the W9 list and
+the rollback compare are reused unchanged.
+
+## Who, and what nobody does
+
+- Sage operates, as the tester. Darkwing holds the gate lane for row 190 round 3 tonight, so I take the
+  operator seat. Mos verifies each step's output before the next one and runs `rehearse` (P3), which reads the
+  live config and a live backup (`docs/TOOLS.md` `rehearse`: Jason or Mos runs it).
+- Jason has no step. Q173 covers a re-pin of this test system with a backup first and a STATE report after.
+  Nothing is pruned.
+- Nobody acts as Jason: no `--by jason`, no human shell or tmux pane, every bus read and write carries
+  `--tester`, and no request carries `jason.woltje`. `bus.tester` stays as it is; if it isn't `true`, stop at P1.
+- No pi (mos-0865 D2, P19 #383). No Save in the human Console, no `mosaic name`.
+- Outside reach doesn't change. The Console keeps its current flags. `--sso` stays off: row 192's sign-in code is
+  dormant without the flag, and `cli.mjs:57` refuses `--sso` with the preview flags the pointer carries anyway.
+  The proof pair stays unset. The tunnel still forwards 7332 only (P4 and W10 check it).
+
+## Names
+
+- OLD, live: `490e2771d3d057ab76991e2c7859cd251857e64c`, activation `20261020T192956Z-490e2771d3d0`, pointer
+  `pm: true`, schema 3i, Console `--port 7332 --public-host mosaic.woltje.com --auth-header X-authentik-username
+  --allow-user jason.woltje --tester-port 7333` (no `--send`, read from `stack-release.sh status` between 21:36Z and 21:39Z).
+- NEW: `4429a104f6d65ccf165f6c83b5d1dce3147dfde0`, row 192's landing, 103 commits past OLD (`git rev-list --count 490e2771d..4429a104f`).
+  The 106 that `status` showed is OLD to HEAD 305857c8f, so it also counts the three record commits below.
+  The commits after it (5b8def2f1 plans, 176a6bf4b sessions, 305857c8f queue) are records and don't move NEW. If
+  another code row lands before W0 (row 190 is the likely one), NEW stays here unless Mos rules otherwise.
+- REPO: the canonical checkout. `activate` runs REPO's `webui-service.sh`, so the four service scripts are held
+  at NEW for the window (P5).
+- `P=/mnt/storage/scratch/sage-pin-de352dfaf` (`business-check.mjs`, `console-check.sh`, checked against
+  `agents/sage/work/window-plan/repin-de352dfaf/SCRIPTS.sha256`).
+- `WIN=agents/sage/work/window-repin-4429a104f/`, where every transcript goes.
+- `SNAP=$WIN/snapshot.mjs`, a copy of `agents/darkwing/work/window-rows-177-185/snapshot.mjs`, sha256
+  `639fd28a2674aaa03ce824e3394b4052f21cdef7d6fa49bae61a9927ed341e67` (mos-0899). I check the sha before S1, S2
+  and any D3.
+
+## What NEW carries over OLD
+
+The path-limited log over `packages`, `scripts`, `roles`, `contracts`, `adapters`, `skills` and the package files:
+
+| Row | Commit | Live effect |
+|---|---|---|
+| 186 | 269134d8d | Tool only: the activate plan's backup line says what the run will do. |
+| 187 | 9a71e4e80 | Tool: activate sets, carries and drops the proof pair. The pointer has no pair, so nothing changes. |
+| 188 | 8fc0ee216 | Tool: proof file checks on a carried pair. No pair, no effect. |
+| 163 | 8ecc7a239 | Tool: `rehearse`, which P3 uses, and `bus start --no-launch`. CLI `cli.mjs` and `launcher.mjs` gain the `--no-launch` path; the default start is unchanged. |
+| 189 | ace27dc5e | Tool: `activate --no-send`. Live already runs without `--send`; the pointer carries that. |
+| 192 | 4429a104f | Console `--sso` (off here), `scripts/mosaic-config.mjs` load becomes async, `webui-service.sh` renders `--sso` only when given, and a new dependency, oauth4webapi 3.8.8. `cli.mjs` imports `sso.mjs` at the top, so the Console won't start from a copy without that module. |
+
+No schema step: `SCHEMA_VERSION` (`packages/bus/src/store.mjs:17`) is 3i at OLD and NEW, and no migration was
+added. `--plan` must say `migration: none`. No roles, skills, contracts, adapters or plug-in kinds changed. So: no
+harness set, no skill carry, no `pm-on`. One `activate --pm`.
+
+## npm ci in the new copy
+
+mos-1099 asks for npm ci in the new copy. `stack-copy.sh copy` already does it: it extracts the archive to a temp
+dir, refuses without `package.json` and `package-lock.json` (:55), runs `npm ci --no-audit --no-fund` there and
+writes no copy if it fails (:56). W0 checks the result: `node_modules/oauth4webapi/package.json` in the copy reads
+3.8.8, and `node --input-type=module -e "await import('oauth4webapi')"` from the copy exits 0. The live copy is
+163M; `/home` has 30G free (94% used), enough for one more.
+
+## Backups
+
+| Before | Backup | Taken by |
+|---|---|---|
+| W5 | the stopped store, `$DATA/backups/stack/<W5 activation id>/` with SHA256SUMS, DATA_ROOT, SCHEMA 3i, STAMP | `stack-release.sh` (row 185: every activate) |
+| W5 | the rollback set (units, wrapper, pointer) | `stack-release.sh` |
+| W9 | the business file, `cp -p` to `~/.config/mosaic-dev/businesses/mosaic-stack.json.pre-window-<stamp>` with its sha256, as evidence nothing wrote it | Sage, in W0b |
+
+## Before the window (nothing stopped)
+
+| # | Who | Step |
+|---|-----|------|
+| P0 | Mos | The `$P` sha check, as in the 177-185 plan P0. |
+| P1 | Sage | The business file, read only, the same values as the 177-185 plan P1. I report its sha256 now rather than assume the 06:15Z value. `business-check.mjs` for OLD now and for NEW after W0: LOAD_OK both. |
+| W0 | Sage | `cd $REPO && scripts/stack-copy.sh copy $NEW`, in a gap between gate-lane runs, since npm ci is heavy. Then the two npm checks above, and `diff <(git -C $REPO show $NEW:package-lock.json) $COPIES/$NEW/package-lock.json` empty. W0 writes only under `copies/` and changes nothing live, so it moves before P2 and P3, which need the copy. |
+| P2 | Sage | `console-check.sh $NEW` against a stub Console of NEW on a scratch port, once without and once with `--tester-port` on a second scratch port. CONSOLE_PASS both. |
+| P3 | Mos | `scripts/stack-release.sh rehearse $NEW mosaic-stack --backup 20261020T192956Z-490e2771d3d0 --port <scratch>`. It must pass every gate check but the PM's. It stops no unit and writes no pointer. Transcript in `$WIN/p3/`. Correction (mos-1107): `rehearse` starts NEW's Console with only `--port` and `--business`, not the pointer's flags. So Mos also starts NEW's Console by hand with the pointer's flags on two scratch ports and reads healthz and `/api/config` on both, then stops it (`$WIN/p3/flags-check.txt`, `flags-console.log`). |
+| P4 | Sage | The tunnel read, as in the 177-185 plan P4. |
+| P5 | Sage | `git -C $REPO diff --quiet $NEW HEAD -- scripts/stack-release.sh scripts/webui-service.sh scripts/bus-service.sh scripts/stack-copy.sh` and an empty `git status --porcelain` on the same four. Row 190 round 3 touches `webui-service.sh`; if it lands before W5, P5 fails and the window waits for Mos's ruling. |
+| P6 | Sage | The 7332 matrix (a)-(g) on OLD, as in the 177-185 plan, saved as `$WIN/matrix-old.txt`. |
+
+## The window
+
+| # | Who | Step |
+|---|-----|------|
+| W0b | Sage | The business file copy. |
+| W1 | Sage | Idle check (`mosaic agents --business mosaic-stack --tester`, `mosaic launches list`), the start stamp from `date -u`, then S1 `node $SNAP --store "$DATA/bus/bus.sqlite" --held`. |
+| W2 | Sage | `stack-release.sh status mosaic-stack`: pointer on OLD, `pm: true`, 3i, last line ok, unit flags match. |
+| W3 | Sage | `stack-release.sh activate $NEW mosaic-stack --pm --plan`. Must show from OLD to NEW, `migration: none`, the backup line, and the Console line with OLD's flags exactly: no `--send`, no `--sso`, no proof pair, `--tester-port 7333`. Any other difference stops here. |
+| W4 | Sage | The unit reads, as in the 177-185 plan W4. |
+| W5 | Sage, on Mos's go | `stack-release.sh activate $NEW mosaic-stack --pm`. Exit 0, `result ok`, every gate check including `pm_launched`. Record the activation id, the backup path and STAMP, and the backup SHA256SUMS sha256. Then `status`. |
+| W9 | Sage, after Mos verifies W5 | The 177-185 plan's W9 list unchanged, the chief turn and the one `assistant` thread turn included (mos-0929 Q3), plus two lines: the webui journal since the W5 stamp (with `UTC`) has one `Proxy: proxy proof off` and no `Sign-in:` line, and `ls -l /proc/<Console pid>/cwd` names the NEW copy. |
+| W10 | Sage | The browser check on 127.0.0.1:7333 and the matrix again as `$WIN/matrix-new.txt`, identical to `matrix-old.txt`. Then P4 again. Corrections after the window (mos-1135, mos-1137): the matrix line for a file the pin changes isn't "identical". Line (g) serves `index.html`, which row 192 grows by 121 bytes (6470 to 6591), so (g) is 200 non-json at 6575 bytes, not 6454. The two browser checks come from the 177-185 window, before row 192 and before a second thread project. "Only tester forms" now allows `#sign-out` while it is `hidden` and `/api/config` has no `sso: true`. "Chat lists the W9 thread" now reads every `.chat-projects section.panel` list (chat.js:93 renders one per project), not the first. |
+| W11 | Sage | STATE report in `$WIN/STATE.md`, posted on P19 386 and P19 412 and on Gitea #1690. |
+
+## Stop conditions and rollback
+
+The same as the 177-185 plan. Two failures in one window: stop and report (mos-0823).
+
+Rollback: `stack-release.sh rollback mosaic-stack --plan`, then the real run. The previous distinct copy in the
+log is 490e2771d, both are 3i, so no `--restore` and no data loss. OLD takes the same Console flags. The R1 and
+R1post compares are as in the 177-185 plan. A restore past W5 follows that plan's D3 steps, with Mos deciding.
+
+Keep every copy. Prune nothing.
+
+## Questions for the plan check
+
+- Q1: NEW is row 192 alone, not bundled with row 190. Row 190 (several instances) changes `stack-release.sh`
+  and `webui-service.sh` and deserves its own window. I recommend running this one first.
+- Q2: Sage operates instead of Darkwing, who is on the row 190 gate. OK?
+- Q3: W0 before P2 and P3. It writes a copy only. OK?
+
+## What Sage ran for this plan
+
+Read only, 2026-10-20 between 21:36Z and 21:39Z (clock read 21:39:50Z at the commit): `stack-release.sh status mosaic-stack` (pointer, last five log
+lines, unit flags match, 106 commits of drift), `git rev-list --count`, `SCHEMA_VERSION` at both ends, the
+path-limited log, `git diff --stat` on the service scripts, CLI and config loader, `stack-copy.sh:23-56`,
+`webui/src/cli.mjs:15-120`, `docs/TOOLS.md` on `rehearse`, `du -sh` of the live copy and `df -h /home`. Nothing
+live was changed.

agents/sage/work/window-repin-4429a104f/.w1-agents.txt

@@ -0,0 +1,3 @@
+chief  rbb708846b605  claude-code  since 2026-10-20T19:29:59.053Z
+pm  rc36b17ef3788  claude-code  since 2026-10-20T20:20:56.278Z
+# exit 0

agents/sage/work/window-repin-4429a104f/.w10-browser.txt

@@ -0,0 +1,256 @@
+{
+  "settings loaded": {
+    "pass": true
+  },
+  "settings": {
+    "banner": "Tester Console. Changes are recorded as tester, never as the human.",
+    "h1": "Settings",
+    "forms": [
+      "sign-out",
+      "conv-form",
+      "routes-form",
+      "instance-add-form",
+      "instance-change-form",
+      "tester-name-form",
+      "tester-name-form",
+      "tester-name-form",
+      "tester-name-form",
+      "tester-name-form",
+      "tester-name-form"
+    ],
+    "convFormHidden": true,
+    "panels": [
+      "Routing",
+      "Role instances",
+      "Seat names"
+    ],
+    "instancesTable": true,
+    "nameForms": 6,
+    "routesForm": true,
+    "routesSubmitEnabled": true,
+    "forbidden": [],
+    "tokenLimitsPanel": false
+  },
+  "tester banner": {
+    "pass": true,
+    "detail": "Tester Console. Changes are recorded as tester, never as the human."
+  },
+  "instance, routes and name editors present": {
+    "pass": true
+  },
+  "only tester forms (conv-form is index.html:21, global and hidden)": {
+    "pass": false,
+    "detail": [
+      "sign-out",
+      "conv-form",
+      "routes-form",
+      "instance-add-form",
+      "instance-change-form",
+      "tester-name-form",
+      "tester-name-form",
+      "tester-name-form",
+      "tester-name-form",
+      "tester-name-form",
+      "tester-name-form"
+    ]
+  },
+  "no launch settings, assistant, limit reset or send": {
+    "pass": true,
+    "detail": []
+  },
+  "no Token limits panel (plan W10 item 2, amended)": {
+    "pass": true
+  },
+  "board": {
+    "busViewHidden": true,
+    "banner": true,
+    "headings": [
+      "Waiting on you –",
+      "All sessions –"
+    ],
+    "unavailable": false,
+    "length": 179,
+    "forms": [
+      "sign-out",
+      "conv-form"
+    ]
+  },
+  "board reads": {
+    "pass": true,
+    "detail": {
+      "busViewHidden": true,
+      "banner": true,
+      "headings": [
+        "Waiting on you –",
+        "All sessions –"
+      ],
+      "unavailable": false,
+      "length": 179,
+      "forms": [
+        "sign-out",
+        "conv-form"
+      ]
+    }
+  },
+  "chat": {
+    "hash": "#/chat",
+    "banner": true,
+    "threads": [
+      {
+        "href": "#/chat/threads/d0ba7a66-aa3f-4918-9518-94132bce6b28",
+        "name": "w9",
+        "instance": "assistant"
+      }
+    ],
+    "conversationOpen": false,
+    "forms": [
+      "sign-out",
+      "conv-form",
+      "chat-project-form"
+    ]
+  },
+  "chat lists the W9 thread": {
+    "pass": false,
+    "detail": [
+      {
+        "href": "#/chat/threads/d0ba7a66-aa3f-4918-9518-94132bce6b28",
+        "name": "w9",
+        "instance": "assistant"
+      }
+    ]
+  },
+  "W9 thread page not opened": {
+    "pass": true,
+    "detail": "#/chat"
+  },
+  "tester banner on chat": {
+    "pass": true
+  },
+  "requests": [
+    {
+      "method": "GET",
+      "url": "/api/config",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/config",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/messages",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus-status",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/messages",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/settings",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/usage",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/settings",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/usage",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/names",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/names",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/instances",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/instances",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/routes",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/routes",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/limits",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/limits",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/inbox",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/agents",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/messages",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/chat/projects",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/chat/threads",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/business",
+      "refused": false
+    }
+  ],
+  "no write through the listener": {
+    "pass": true,
+    "detail": []
+  },
+  "no request to the W9 thread messages or open": {
+    "pass": true,
+    "detail": []
+  }
+}
+W10 browser: FAIL
+# exit 1

agents/sage/work/window-repin-4429a104f/.w10-diag.txt

@@ -0,0 +1,200 @@
+{
+  "config": {
+    "sso": null
+  },
+  "forms": [
+    {
+      "id": "sign-out",
+      "hidden": true,
+      "action": "/auth/logout",
+      "method": "post"
+    },
+    {
+      "id": "conv-form",
+      "hidden": true,
+      "action": null,
+      "method": null
+    },
+    {
+      "id": "routes-form",
+      "hidden": false,
+      "action": null,
+      "method": null
+    },
+    {
+      "id": "instance-add-form",
+      "hidden": false,
+      "action": null,
+      "method": null
+    },
+    {
+      "id": "instance-change-form",
+      "hidden": false,
+      "action": null,
+      "method": null
+    },
+    {
+      "id": "tester-name-form",
+      "hidden": false,
+      "action": null,
+      "method": null
+    },
+    {
+      "id": "tester-name-form",
+      "hidden": false,
+      "action": null,
+      "method": null
+    },
+    {
+      "id": "tester-name-form",
+      "hidden": false,
+      "action": null,
+      "method": null
+    },
+    {
+      "id": "tester-name-form",
+      "hidden": false,
+      "action": null,
+      "method": null
+    },
+    {
+      "id": "tester-name-form",
+      "hidden": false,
+      "action": null,
+      "method": null
+    },
+    {
+      "id": "tester-name-form",
+      "hidden": false,
+      "action": null,
+      "method": null
+    }
+  ],
+  "chat": {
+    "hash": "#/chat",
+    "open": false,
+    "projects": [
+      {
+        "project": "window-20261020-0801",
+        "threads": [
+          "#/chat/threads/d0ba7a66-aa3f-4918-9518-94132bce6b28"
+        ]
+      },
+      {
+        "project": "window-20261020-2205",
+        "threads": [
+          "#/chat/threads/446201de-e8b5-4df3-9356-d0d5422cc899"
+        ]
+      }
+    ]
+  },
+  "requests": [
+    {
+      "method": "GET",
+      "url": "/api/config",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/config",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/messages",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus-status",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/messages",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/settings",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/usage",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/settings",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/usage",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/names",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/names",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/instances",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/instances",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/routes",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/routes",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/limits",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/bus/limits",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/config",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/chat/projects",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/chat/threads",
+      "refused": false
+    },
+    {
+      "method": "GET",
+      "url": "/api/business",
+      "refused": false
+    }
+  ]
+}
+sign-out hidden true, sso null; W9 thread listed true; thread page open false; writes 0
+# exit 0

agents/sage/work/window-repin-4429a104f/.w10-matrix.txt

@@ -0,0 +1,8 @@
+a 200 ok=true
+b 401 error="sign-in required"
+c 401 error="sign-in required"
+d 403 error="proxy Host refused"
+e 403 error="tester listener required"
+f 403 error="proxy header refused"
+g 200 non-json 6575 bytes
+# exit 0

agents/sage/work/window-repin-4429a104f/.w10-p4.txt

@@ -0,0 +1,7 @@
+# P4 2026-10-20T22:31:29Z
+DropInPaths=
+ExecStart={ path=/home/jwoltje/.local/bin/chisel ; argv[]=/home/jwoltje/.local/bin/chisel client --fingerprint ce+ISFvMAhuoCRDuc7riIf+hYz87TLHk/C9C/H8QsUg= --keepalive 25s --max-retry-interval 10s http://10.1.1.227:8080 R:0.0.0.0:7332:127.0.0.1:7332 ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
+# exit 0
+# R: specs (1): R:0.0.0.0:7332:127.0.0.1:7332 
+P4 PASS: one R: spec R:0.0.0.0:7332:127.0.0.1:7332, DropInPaths empty
+# exit 0

agents/sage/work/window-repin-4429a104f/.w11-bus.txt

@@ -0,0 +1,6 @@
+ActiveState=active
+DropInPaths=
+MainPID=2950923
+ExecStart={ path=/home/jwoltje/.local/share/mosaic-stack/copies/4429a104f6d65ccf165f6c83b5d1dce3147dfde0/scripts/mosaic ; argv[]=/home/jwoltje/.local/share/mosaic-stack/copies/4429a104f6d65ccf165f6c83b5d1dce3147dfde0/scripts/mosaic bus start mosaic-stack --pm ; ignore_errors=no ; start_time=[Tue 2026-10-20 17:02:08 CDT] ; stop_time=[n/a] ; pid=2950923 ; code=(null) ; status=0/0 }
+WorkingDirectory=/home/jwoltje/.local/share/mosaic-stack/copies/4429a104f6d65ccf165f6c83b5d1dce3147dfde0
+# exit 0

agents/sage/work/window-repin-4429a104f/.w11-failed.txt

@@ -0,0 +1,12 @@
+● jarvis-curation-gate.service                            loaded failed failed Jarvis curation-gate liveness check (wake the agent if staged pulls sit uncurated)
+● jarvis-retro-check.service                              loaded failed failed Jarvis weekly retrospective ARTIFACT check (did Sunday's tick produce a retro?)
+● jarvis-retro.service                                    loaded failed failed Jarvis weekly retrospective tick
+● mosaic-install-drift.service                            loaded failed failed Assert the installed Mosaic binaries still match the committed source (drift, not failure)
+● mosaic-standup-pm.service                               loaded failed failed Coordinator standup trigger (evening)
+● [email protected] loaded failed failed Escalate failed Mosaic unit jarvis-curation-gate.service to the local agent seat
+● [email protected]   loaded failed failed Escalate failed Mosaic unit jarvis-retro-check.service to the local agent seat
+● [email protected]         loaded failed failed Escalate failed Mosaic unit jarvis-retro.service to the local agent seat
+● [email protected] loaded failed failed Escalate failed Mosaic unit mosaic-install-drift.service to the local agent seat
+● [email protected]     loaded failed failed Escalate failed Mosaic unit mosaic-reconcile.service to the local agent seat
+● setspark-tmp-guard.service                              loaded failed failed SetSpark: /tmp and scratch guard
+# exit 0

agents/sage/work/window-repin-4429a104f/.w11-tunnel.txt

@@ -0,0 +1,5 @@
+ActiveState=active
+SubState=running
+ActiveEnterTimestamp=Tue 2026-10-13 08:40:19 CDT
+MainPID=1317
+# exit 0

agents/sage/work/window-repin-4429a104f/.w11-webui.txt

@@ -0,0 +1,6 @@
+ActiveState=active
+DropInPaths=
+MainPID=2950925
+ExecStart={ path=/usr/bin/node ; argv[]=/usr/bin/node /home/jwoltje/.local/share/mosaic-stack/copies/4429a104f6d65ccf165f6c83b5d1dce3147dfde0/packages/webui/src/cli.mjs serve --checkout /mnt/storage/src/mosaic-stack --port 7332 --public-host mosaic.woltje.com --auth-header X-authentik-username --allow-user jason.woltje --tester-port 7333 ; ignore_errors=no ; start_time=[Tue 2026-10-20 17:02:08 CDT] ; stop_time=[n/a] ; pid=2950925 ; code=(null) ; status=0/0 }
+WorkingDirectory=/home/jwoltje/.local/share/mosaic-stack/copies/4429a104f6d65ccf165f6c83b5d1dce3147dfde0
+# exit 0

agents/sage/work/window-repin-4429a104f/.w9-agents.txt

@@ -0,0 +1,2 @@
+chief  r097436c91816  claude-code  since 2026-10-20T22:02:08.951Z
+# exit 0