gizmoduck: rows 270+271 combined gate (C2) record before the first run (sage-3073, sage-3086, mos-1275, mos-1351): blob table, timeout table, GREEN and RED, order; code is ac44d0de9's

2026-10-22 19:06:47 -05:00
1 parent ac44d0de93
commit 0f5e5d62d6
@@ -504,3 +504,65 @@ unchanged, because 203 touches none of those four files. No test pins a sha256 o
 test-config.sh, stack-release.sh or stack-release.test.mjs.

 Nothing has run on this base yet. The combined gate is sage-3073 item 4, on Sage's CLEAR.
+
+## Combined 270+271 gate (C2), written before the first run (sage-3073 item 4, sage-3086, mos-1351)
+
+The gate runs on the commit that adds this section. Its code is ac44d0de9's: `git diff --name-only
+ac44d0de9 HEAD` is this file only. The review keys stay manifest-270-r4 4f5e7041… and manifest-271-r4
+3ab1f5c8…, Duckworth approves at revs 3379 and 3380. Worktree /mnt/storage/scratch/gizmo-270, with
+node_modules linked to the canonical checkout. Base 25c09f19f. Script
+/mnt/storage/scratch/gizmo-271-out/run-r4.sh, run with pipefail and tee, logs in
+/mnt/storage/scratch/gizmo-271-out/r4/. TMPDIR comes from `mktemp -d /mnt/storage/scratch/tmp/gXXX`.
+
+### Blob table
+
+sha256 of every source file a mutant edits, at the gate commit. Each restore is `git checkout --` the
+file, then this hash, then a clean tree.
+
+```
+b5a078a096e447c4afe15812696d1f2f8c3f2b7665868c02e61a4e1edc8cd874  packages/seat/src/compactions.mjs  (270)
+d7cdc8a17e337e00dfe2d1bf6249cc2c2e696b16c5b426b2fe616089e5559509  packages/bus/src/broker.mjs  (270, 271)
+21a7e910d81848aeb99036028d5b87354a2a515f3642779105c881b43a8b6e05  packages/cli/src/launcher.mjs  (270, 271)
+5ae423438a178b1c8eac3b8ce0e0c22f5bb7caebb9011ce7098a36d95b53f1ca  packages/bus/src/runtime.mjs  (270)
+```
+
+### Timeout table (mos-1275)
+
+Every run is `timeout -k 10 LIMIT`. The longest records are 271's gate on e8af389e6 (BUILD.md queue-271
+"Gate on e8af389e6") and 271's "Run limits" table.
+
+| Run | Longest recorded | LIMIT |
+| --- | --- | --- |
+| stack-release.test alone | 575 s | 1800 s |
+| each other touched test file alone, stack-instances.test, webui pinned-copy.test | 15 s | 300 s |
+| business suite | none recorded | 900 s |
+| bus suite | 24 s | 900 s |
+| seat suite | 6 s | 600 s |
+| cli suite | 591 s | 1800 s |
+| each scripts/test-*.sh | 42 s (test-foundation; 39 s at e8af389e6) | 900 s |
+| 270 mutant, seat or bus kill file | none recorded | 120 s |
+| 270 mutant, cli compactions-launch.test | none recorded | 600 s |
+| 271 mutant, each session-clear.test file | 57 s for both files (e8af389e6) | 300 s |
+
+A shell-phase timeout goes to Mos unplaced. A timeout with no failed test is a hang and goes to Sage.
+
+### GREEN and RED
+
+- GREEN for a test run: rc 0, `fail 0`, and at least one pass for a single file. A skip is named in the
+  report.
+- RED: any other rc, a failed test, or zero passes.
+- A mutant is killed when its kill file is RED with a `not ok` on the test K names. 270's K is in
+  queue-270/mutants.py. 271's kills are the bus or cli session-clear.test failures in queue-271/BUILD.md.
+  A mutant whose kill file stays GREEN survived.
+- A first-run red in a new test (seat compactions-budget.test, cli compactions-launch.test, 271's new
+  tests) is placed and reported after (mos-1272). A red in an old test, a product change, a looser
+  assertion or a second red on a row stops the run and goes to Sage before any change (sage-3086).
+- Mutants run only on a GREEN base.
+
+### Order
+
+1. The 20 touched test files whole, then cli stack-instances.test, webui pinned-copy.test and the
+   business suite (the config loader's readers, round 2 run plan item 3).
+2. bus, seat and cli suites whole.
+3. The ten scripts/test-*.sh, test-config.sh among them, with skips named.
+4. 270 M1-M24, each on its K file whole. Then 271 M1-M14, each on bus and cli session-clear.test whole.