row 240: BUILD.md records the r1 failure, the b45852daa fix and the r2 results (cli 639/0, scripts 585/0, M1-M8 8/8), and the brief pin at b00d7d94d

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

@@ -1,7 +1,7 @@
 # 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 `e61291bcf1c6` (commit a0e3d7cfd). Sage split
-it out of I3 (sage-1650). Gitea #1746, Vikunja P19 #432. Owner Darkwing, reviewer Filbert, gate owner Sage.
+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.
 
@@ -96,7 +96,7 @@ Sage asked (sage-1759) whether `stack-release.test.mjs` or `stack-release-extern
 
 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 (no test run yet).
+and a sha256 check. A dry run matched all eight once each. Results below.
 
 | Mutant | Change | Killer |
 |---|---|---|
@@ -138,9 +138,36 @@ and a sha256 check. A dry run matched all eight once each (no test run yet).
 
 ## Run environment
 
-To come: `case1-hostcheck.test.mjs` and `stack-upgrade.test.mjs` singly, then the mutants, then the gate, each in Sage's slot behind `busy.sh`, TMPDIR
-`/mnt/storage/scratch/tmp/r240`.
+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
 
-None yet.
+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.