sage: merged B+C window STATE checked and filed (P19 386 c324, 382 c325 done, #1673 29334, #1674 29335); #394 doc fixes: carry-past-row64.md runs from REPO held to the pinned sha, plan line 222 and W8 row amended (mos-0924)

carry-past-row64.md sha256 6799542cb23aba4c, repin-merged-bc.md 99f86c078d01663f (draft 9 was 523f20e03be8aa11). BUILD-LOG phase and SESSIONS line.
2026-10-19 21:23:57 -05:00
parent ac1e16a99a
commit 88f3253d98
4 changed files with 52 additions and 10 deletions
@@ -5140,3 +5140,13 @@ Before: managed project/thread verbs had no Console conversation area. After: fi
 - Follow-ups, one row after the merged window with P19 391: Dewey's N1 (--plan console_for_target exits through refuse or usage, not check_refuse) and N2 (tester_port_ok strips leading zeros, so 007333 renders and serve refuses it).
 - Merged B+C plan draft 8 (sha256 38683b89acd456a5): NEW 89af38a83, tool blob adcb68477c25, the 176 table line, stack-release.sh line numbers moved to NEW, broker.mjs:2189 corrected to :2237, and draft 7's header stamp corrected from 01:05Z to 00:55Z (an estimate, not a clock read). Sent to Mos for the formal check (sage-1138). Darkwing has the slot for P3 on blob adcb6847 with --events N above 0 (sage-1137).
 - Not live: the live stack stays on copy 5fa9cc8f2.
+
+2026-10-20 02:23:57 UTC | Sage | Merged B+C window: 89af38a83 live with its PM on store 3i, tester listener 7333
+
+- Before: the live stack ran copy 5fa9cc8f2 on store 3h with no tester listener. Plan draft 9 (sha256 523f20e03be8aa11, c49de08e8) had Mos's W0 go (mos-0907). Q173 makes this business a test system.
+- Darkwing operated W0 to W11 and Mos verified each step. W5 activate --pm-after-harness --migrate --tester-port 7333, 20261020T013708Z-89af38a83afa: exit 0, 3h to 3i. Store backup ~/.mosaic-dev/backups/stack/20261020T013708Z-89af38a83afa, STAMP 2026-10-20T01:37:08.917Z, SHA256SUMS ef78f7d4. W6: the tester set plugins.harness to [claude-code] (transaction 0a63a1dc). W7 pm-on 20261020T014103Z-89af38a83afa launched chief rc78c9700c8e9. W8 carried the seven skills, each matching NEW. W9: the tester reads and a chief talk passed, and a coder started by the chief answered with its four skills and was stopped at 02:01:41Z. W10: the 7333 browser showed only tester forms, and 7332 refuses x-mosaic-tester with 403.
+- Three deviations, each accepted by Mos. (1) W8 ran from REPO, because a stack copy has no skill.sh or skills/ (mos-0914). My carry doc was wrong. (2) The W9 coder was started by the chief, since TESTER_VERBS has no role.launch (mos-0917). (3) The tester Settings has no Token limits panel by design, and no human Console read ran (mos-0920, mos-0922, mos-0923).
+- Sage checked STATE.md (sha256 7be42b6bcab5657d) against window/. The snapshot hashes, S1/S2 counts, S2b, W5/W7/W8 exits, activation log lines, units, listeners and healthz all match. Not stated in STATE: the backup has events 1384 and role_claims 88 against S1's 1383 and 87, so the OLD bus wrote one of each between S1 (01:34:49Z) and the backup (01:37:08Z). That's expected with OLD live.
+- Filed: P19 386 comment 324. P19 382 comment 325, then marked done because W5 to W9 passed (plan line 135). Gitea #1673 comment 29334 and #1674 comment 29335, as jarvis. The W9t inbox --json point goes to row 177's README (sage-1148).
+- After: the carry doc runs from REPO held to the pinned sha, with an empty-diff check before and a per-file sha256 check after (P19 394, mos-0915). Plan line 222 names what the tester page shows, and the W8 row matches the carry doc. Mos checked both in mos-0924.
+- Open: P19 390 (restore guard), P19 391 (activation-id race) with row 176 N1/N2, row 177 N1/N2 README notes, and the "Read never." subtitle (Mos's task).
@@ -16,20 +16,44 @@ re-pin.

 ## The step (before the first role start on the new pin)

-Run from the pinned copy, so the skill bytes come from that copy's `skills/` directory (mos-0863 F3). The seven
-skills not yet enabled:
+Run from the canonical checkout (REPO), held to the pinned sha by the checks before and after the loop. The skill
+bytes must equal the pinned sha's `skills/` (mos-0863 F3).
+
+Correction, Sage, 2026-10-20: the first version of this step said to `cd` into the pinned stack copy. A stack copy
+holds only stack-copy.sh's COPY_PATHS, which have no `scripts/skill.sh`, no `scripts/common.sh` and no `skills/`.
+Darkwing held the merged B+C window at W8 before writing anything, and Mos amended W8 to run from REPO with these
+checks (mos-0914). Mos asked for this file to say the same (mos-0915). The window recorded it as deviation 1
+(`agents/darkwing/work/window-merged-bc/STATE.md`). The shapes below follow Darkwing's `window/w8-run.sh` and
+`window/w8-verify.sh`.
+
+Before the loop, with `N` the pinned sha. Any output from either command, or a nonzero diff exit, is a stop:

 ```
-cd <copies>/<pinned sha>
-for s in ms-unslop ms-sdlc ms-file-read ms-file-write ms-archify ms-grill-me ms-goal; do
+cd <REPO>
+SEVEN="ms-unslop ms-sdlc ms-file-read ms-file-write ms-archify ms-grill-me ms-goal"
+paths=(scripts/skill.sh scripts/common.sh); for s in $SEVEN; do paths+=("skills/$s"); done
+git diff --stat "$N" -- "${paths[@]}"
+git status --porcelain --ignored -- "${paths[@]}"
+```
+
+The loop, for the seven skills not yet enabled:
+
+```
+for s in $SEVEN; do
  scripts/skill.sh install "$s" && scripts/skill.sh activate "$s" || { echo "STOP skill $s"; break; }
 done
 scripts/skill.sh list
 ```

-The check: `list` shows all eight under `enabled:` (the seven plus ms-communications), and ms-tools stays under
-`available:`. Before running, the plan re-reads the role lists at the pinned sha (`git show <sha>:roles/<r>.json`)
-and updates the seven if they changed.
+The checks after it:
+- `list` shows all eight under `enabled:` (the seven plus ms-communications), and ms-tools stays under
+  `available:`.
+- For each of the seven, the file list under `<dataRoot>/skills-enabled/<s>` equals
+  `git ls-tree -r --name-only "$N" skills/<s>`.
+- Each file's sha256 equals that of `git show "$N:skills/<s>/<file>"`. A mismatch is a stop.
+
+Before running, the plan re-reads the role lists at the pinned sha (`git show <sha>:roles/<r>.json`) and updates
+the seven if they changed.

 ## Pi needs its own credential first (mos-0865 D2)

@@ -42,9 +66,10 @@ Nobody maps CLAUDE_CODE_OAUTH_TOKEN into a pi variable.
 ## Rollback

 Deactivate and uninstall the same seven, in that order, then `scripts/skill.sh list` shows ms-communications
-alone under `enabled:` again:
+alone under `enabled:` again. This also runs from REPO, since the copy has no `scripts/skill.sh`:

 ```
+cd <REPO>
 for s in ms-unslop ms-sdlc ms-file-read ms-file-write ms-archify ms-grill-me ms-goal; do
  scripts/skill.sh deactivate "$s" && scripts/skill.sh uninstall "$s"
 done
@@ -129,7 +129,7 @@ is what the 176 brief's Gate section asks for.
 | W5 | Darkwing, on Mos's go | Phase 1: `scripts/stack-release.sh activate $NEW mosaic-stack --pm-after-harness --migrate --tester-port 7333`. Exit 0, final `result ok`, every gate check except `pm_launched`. Record the activation id and the backup path and stamp. Then `status`: pointer on NEW, `pm: false`, `pmPending: true`, schema 3i, Console flags with `--tester-port 7333`, and the pending line. The bus is live without its PM. |
 | W6 | Darkwing, after Mos verifies W5 | The harness set, as the tester: `$C_NEW plugins --business mosaic-stack --tester --json` for the revision, then `$C_NEW plugins set --file $WIN/harness.json --business mosaic-stack --tester` with `{"revision":"<that revision>","plugins":{"harness":["claude-code"]}}`. Read it again: `harness` is `["claude-code"]`, `usage-source` and `channel` unchanged. The organization receipt names actor `tester`. Then Mos runs `business-check` under NEW on the patched file: LOAD_OK. |
 | W7 | Darkwing, on Mos's go | Phase 2: `scripts/stack-release.sh pm-on mosaic-stack`. Exit 0: the chief launched and the pointer is `pm: true` with no `pmPending`. Exit 1 or 2: see the stop conditions. |
-| W8 | Darkwing, after Mos verifies W7 | The row 64 skill carry, from the pinned copy (`carry-past-row64.md`): `cd $COPIES/$NEW`, install and activate the seven, then `scripts/skill.sh list` shows eight under `enabled:` and ms-tools under `available:`. A STOP line is a stop condition. |
+| W8 | Darkwing, after Mos verifies W7 | The row 64 skill carry, from REPO held to `$NEW` (`carry-past-row64.md`): an empty diff against `$NEW` first, install and activate the seven, a per-file sha256 check against `$NEW` after, then `scripts/skill.sh list` shows eight under `enabled:` and ms-tools under `available:`. A STOP line is a stop condition. Amended after the window (Sage 2026-10-20): draft 9 said `cd $COPIES/$NEW`, and a copy has no skill.sh or skills/. W8 ran from REPO on mos-0914, recorded as deviation 1. |
 | W9 | Darkwing | The checks and the turn below. |
 | W10 | Darkwing | The browser check below, then P4's tunnel read again. |
 | W11 | Darkwing, then Sage | The STATE report (below). Sage files it on P19 386 and 382 and closes 382 if W5 to W9 passed. |
@@ -219,7 +219,13 @@ What passes:
 On http://127.0.0.1:7333/ with the webui browser harness, from Darkwing's run:

 1. The page shows the tester banner and the instance, routes and name editors only.
-2. The Board and Settings read. Settings shows Token limits with no daily quota entry.
+2. The Board and Settings read. The tester Settings shows the routes, instances and tester names sections and
+   nothing else. It has no Token limits panel by design: bus.js settingsView returns early for the tester (:817
+   at 89af38a83). Token limits are read as the tester through `mosaic limits` (W9i), and the tester page's
+   GET /api/bus/limits (:816) must not be refused. No step renders the human Token limits panel, because on 7332
+   that needs Jason's auth header. (Amended after the window, Sage 2026-10-20, per mos-0920 and mos-0923, with
+   Darkwing's corrected text in `window/msg-mos-w10-corr.txt`. Draft 9 said "Settings shows Token limits with no
+   daily quota entry", which the tester page can't show. The window ran it as deviation 3.)
 3. A request to 7332 with `x-mosaic-tester: 1` and a loopback Host gets 403.
 4. No write through the listener. The routes editor's write path is row 176's test 12 on a fixture, not a live
   change in this window.
@@ -1259,3 +1259,4 @@ are never rewritten or removed; corrections are new entries.
 2026-10-20T01:25:27Z | Sage (Opus 5.5, 1ef1e4f8) | row 176 gate, landing and records (#1674, mos-0902) | gate run 1 failed T34 capture-failed (row 169's activation-id race, base reproduces with the id pinned, P19 391); run 2 green 2455 pkg + 422/156 scripts, 0 fail; landed 89af38a83 (patch-id e6f0a0fb622b), pushed 0a478dfc3..89af38a83, #1674 closed (29331), P19 386 comment 316, queue 3faa30184; plan draft 8 38683b89 to Mos (sage-1138), P3 slot to Darkwing (sage-1137)
 2026-10-20T01:32:26Z | Sage (Opus 5.5, 1ef1e4f8) | merged B+C plan draft 9 and W0 go; row 177 start (mos-0906, mos-0907, #1675) | draft 9 (sha256 523f20e03be8aa11) applies Mos's A1-A4 text fixes, committed c49de08e8; Darkwing's TP=1 P3 sums checked (SHA256SUMS c26e1a4f, 36/36, five expected nonzero exits); Mos closed the formal check, W0 go sent to Darkwing (sage-1140), W5 and W7 wait for Mos; queue revs 2093-2094 committed d3996adea; pushed b61335ad6..c49de08e8 (PUSH_READY); Dewey launched on row 177 design (sage-1141)
 2026-10-20T01:45:24Z | Dewey (Opus 5.5, 84fb346c) | row 177 tester threads (#1675): claimed (rev 2095), design written at origin/refactor c49de08e8, agents/dewey/work/queue-177/DESIGN.md sha256 99ce578091bb4587e5bf95163f7d49044a9fd7231c5075a50e036cfe1a2660f0 | sent to Sage for approval (dewey-0707); no code, no test runs
+2026-10-20T02:23:57Z | sage | merged B+C window STATE check, filing, #394 doc fixes | STATE.md 7be42b6b matches window/ (OLD wrote 1 event + 1 role_claim between S1 and the W5 backup, unstated, expected); P19 386 c324, 382 c325 + done, Gitea #1673 29334, #1674 29335; carry-past-row64.md runs from REPO held to N, plan line 222 + W8 row amended (mos-0924); W9t inbox note to Dewey (sage-1148)