gizmoduck: row 270 (264c, #1775) gate results: run 3 red on case1-accept P10 band (Vikunja 573) and run 4 red on the checkout.test fixture race (Vikunja 574), both old tests unchanged in the range; run 5 GREEN on 53406f3e4 under mos-1369 and sage-3106, all phases and 38/38 mutants killed; BUILD.md only

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

@@ -625,3 +625,45 @@ anchors matching once.
 The file alone then passed 10 of 10 (/mnt/storage/scratch/gizmo-271-out/place-compactions-budget.log).
 Run 3 is the whole combined gate again, on one tree, on the commit with F1 and F2. A third red on 270
 stops it and goes to Sage and Mos before any change.
+
+### Runs 3 and 4: two old-test races, not 270 or 271 (mos-1367, mos-1369)
+
+Run 3 started 00:23:35Z on 53406f3e4. Phase 1 passed whole (business 231/231), bus 873/873 and seat
+202/202. cli went RED, 904 of 905: case1-accept.test.mjs:368, the P10 inner hop probe took 1.08 s, under
+its 1.25 s floor. The file is old and unchanged in 25c09f19f..53406f3e4. I stopped the run during phase 3
+(r4.out's last write 00:46:24Z) and changed nothing. Mos ruled (mos-1367, passed on in sage-3097): A1 run
+case1-accept alone, which passed 50/50 (00:50:01Z to 00:54:17Z, load 3.19 3.58 3.71); A2 run 4 on the
+same tip. Vikunja 573 (owner gander) owns the P10 band fix. Log: /mnt/storage/scratch/gizmo-271-out/r4-run3/.
+
+Run 4 started 00:54:25Z on 53406f3e4 (load 4.45 4.20 3.94). Phase 1 passed 23/23 files and bus 873/873.
+seat went RED, 201 of 202: checkout.test.mjs:239 "a dirty clone whose fetch fails is kept, fetch-failed,
+exactly as it was" failed :91 "the root is unchanged" at its first once(w) (:241). The file is old and
+unchanged in 25c09f19f..53406f3e4, and it passed in run 3. Load was 8.19 at 01:06Z. I stopped the run
+(r4.out's last write 01:06:31Z) and changed nothing. The cause is the fixture, not 270 or 271: its git
+helper (checkout.test.mjs:35) runs with gitEnv() (checkout.mjs:80-90), which does not set
+maintenance.auto=false, so its commit can leave a detached `git maintenance run --auto` writing in the
+root that once() fingerprints. Mos watched objects/maintenance.lock vanish after commit returned in 1 of
+30 fresh repos (mos-1369, passed on in sage-3106). Vikunja 574 (owner gander) owns the fixture fix; no test
+changed in this slot. Log: /mnt/storage/scratch/gizmo-271-out/r4-run4/.
+
+### Run 5: GREEN (mos-1369, sage-3106)
+
+Run 5 waited until the one-minute load was under 4, then started 01:17:11Z on 53406f3e4, unchanged since
+run 3 (loadavg 3.86 4.91 4.69, up 9 days 11:37; origin/refactor 062646487, no drift from 25c09f19f in
+packages or scripts). It ended 01:49:41Z, wall 1950 s, exit 0.
+
+| Phase | Result | Wall |
+| --- | --- | --- |
+| 1, touched test files whole and the loader's readers | 23/23 files pass; stack-release 219/219, compactions-budget 10/10, business 231/231 | 673 s |
+| 2, bus suite | 873/873 | 25 s |
+| 2, seat suite | 202/202 | 7 s |
+| 2, cli suite | 905/905; P10 inner hop probe 2.31 s, outer 4.14 s | 682 s |
+| 3, scripts/test-*.sh | all ten pass; tree clean after | |
+| 4, 270 M1-M24 | 24/24 killed, each on its K file, each restore matched | |
+| 4, 271 M1-M14 | 14/14 killed in the file the 271 table names (271 BUILD.md:713), each restore matched | |
+
+No zero-pass file. Three skips, the same as before: test-queue's queue verify and render --check (this
+checkout is not the queue's canonical root) and test-task's live provider cases, twice (row 244). No node
+process was left with its cwd in the worktree. Sage ran one `git fetch` from the canonical checkout at
+about 01:38:10Z, inside the cli suite (sage-3122); the suite had no red. Log:
+/mnt/storage/scratch/gizmo-271-out/r4/ and r4.out.