row 207 (#1705): BUILD.md Runs records the gate on 712f79c0a (sage-3041): access.test 31/31, M1-M8 killed on their named tests, cli 894/894, ten scripts green under the mos-1275 limits, and the stopped first run's kill-check correction; doc only

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

@@ -135,4 +135,24 @@ On Sage's CLEAR, from a rebase onto 253's landing under a new branch name, stopp
 
 ## Runs
 
-Filled in after the runs.
+Gate on 712f79c0af43acc5486499f6d921e38664c1c1bb (megavolt/row207-r3, this row's three commits rebased onto
+01983cd3f after row 276 landed), Sage's CLEAR sage-3041, 22:07Z to 22:22Z 10-22. Gate worktree
+/mnt/storage/scratch/megavolt-r207/gate-wt, TMPDIR /mnt/storage/scratch/tmp/gbLURml, logs in
+/mnt/storage/scratch/megavolt-r207/logs/. Drift f2735bb6a..01983cd3f outside agents/: BUILD-LOG.md,
+DEFERRED.md, QUEUE.md, queue.json, cli tests case-sudo-fixture.mjs and case1-accept.test.mjs, scripts
+case1-accept.sh and case2-unit.sh; none is read by access.test.mjs.
+
+1. access.test.mjs whole: 31 tests, 31 pass, 0 fail, 0 skipped (base.log).
+2. Mutants, each the whole access.test.mjs under `timeout -k 10 180`, applied by mutate.py (one exact match or
+   refuse), restored by `git checkout` and checked clean after each. All 8 killed, each failing only its named
+   test: M1 T4, M2 T5, M3 T1, M4 T2, M5 T1 and T3, M6 T6, M7 T7, M8 T9 (M1.log to M8.log).
+3. cli package whole (`npm test` in packages/cli): 894 tests, 894 pass, 0 fail, 0 skipped, 674 s (cli.log).
+4. The ten scripts, rc 0 each, seconds against the limit: auth 0/126 (15 passed), conductor 7/145 (17),
+   config 1/130 (31), discord 8/147 (81), extension-package 1/130 (18), foundation 43/240 (44), land-work
+   13/158 (86), queue 26/191 (28), release 3/157 (14), task 14/231 (91). Skips: queue's verify and
+   render --check (the gate worktree is not the canonical root) and task's live provider cases (row 244).
+   test-task printed no Docker-group skip.
+
+Correction: a first run at 22:07Z was stopped after M2. Its kill check grepped TAP `not ok`, but node prints
+the spec reporter's `✖` to a file, so it reported M1 SURVIVED while M1 had failed on T4. The check was fixed
+to `^✖ T4 ` and M1-M8 were rerun from the start. That run's logs are in logs/run1-stopped/.