row 203: gate results on the rebased tip (c7b754d7b): stack-release 219/0, test-config 51/0, mutants 17/17, cli 895/0, ten scripts green with named skips; code tree unchanged from 7309260ae

agents/quackerjack/work/queue-203/BUILD.md

@@ -232,3 +232,79 @@ Run command shape: `timeout -k 10 <S> <cmd>`. Queue verbs are never wrapped in a
 
 Mutant kill rule: each of M1-M17 must fail on an assertion, not on a crash. The mutant run records the failing
 test name. Skips are named in the gate record.
+
+## Gate results on 7309260ae (23:00-23:16Z)
+
+- stack-release.test.mjs, whole: 219 pass, 0 fail, 0 skipped, 583.5 s (timeout 5400 s).
+- test-config.sh: selftest 51 pass, 0 fail, EXIT 0, 2.4 s (timeout 900 s).
+- Mutants, one run each, file restored from git after each. Each run of M1-M13 and M15-M17 is 2.4 s
+  (the first run is the timing: 2.4 s, so the 900 s timeout is far above it).
+
+| mutant | result | killed by (FAIL line in test-config.sh, or stack-release.test) |
+|---|---|---|
+| M1 | killed | federation unknown sub-key |
+| M2 | killed | federation peer unknown sub-key |
+| M3 | killed | federation peer origin over http |
+| M4 | killed | federation peer origin with a path (also userinfo, trailing slash) |
+| M5 | killed | federation peer id equal to self (also duplicate peer id) |
+| M6 | killed | federation peer label empty |
+| M7 | killed | federation not an object |
+| M8 | killed | federation self pattern |
+| M9 | killed | federation peers not an array |
+| M10 | killed | federation peer not an object |
+| M11 | killed | federation peer id pattern |
+| M12 | killed | federation peer label over 80 characters |
+| M13 | killed | duplicate peer id |
+| M14 | killed | row 203 subtest of T57 in stack-release.test.mjs (parent T57 also fails) |
+| M15 | killed | federation self missing |
+| M16 | killed | federation peer id missing |
+| M17 | killed | federation peer label missing |
+
+Correction (new entry; the kill-text column in the mutant plan above is kept as written): the plan named
+the kill labels for M8 and M11 as "self does not match the pattern" and "peer id does not match the pattern".
+Those labels are not in the test file. The assertions that fail are "federation self pattern" and
+"federation peer id pattern". Both mutants are killed; only the label text in the plan was wrong.
+
+M14 note: `node --test --test-name-pattern="row 203"` runs zero inner tests, because the row 203 case is a
+t.test subtest of T57 and the filter skips the parent. The first automated M14 run reported SURVIVED for
+that reason (rc 0 in 0.9 s, no FAIL line). It was re-run with `--test-name-pattern="T57|row 203"`: the row
+203 subtest fails (rc 1), so M14 is killed. The automated result is the wrong one and is not the gate record.
+
+## cli suite (23:20-23:37Z)
+
+- First run (timeout 2400 s, 627.6 s): 895 tests, 816 pass, 77 fail, 2 cancelled, EXIT 1. Cause: this worktree
+  had no node_modules, so scripts/case2-persona-import.mjs (and the other suites that import it) could not
+  resolve package 'yaml' (declared at 2.9.0 in package.json). Not a federation failure. Not in the gate record.
+- Fix in the environment only: node_modules symlinked to /mnt/storage/src/mosaic-stack/node_modules (the row 202
+  recipe). The symlink is excluded through .git/info/exclude and is not committed.
+- Rerun (timeout 2400 s, 621.9 s): 895 tests, 895 pass, 0 fail, 0 cancelled, 0 skipped, EXIT 0.
+
+## Gate summary (23:00-23:40Z, rebased tip c7b754d7b, code tree 7309260ae)
+
+| gate item | result | timeout S | measured |
+|---|---|---|---|
+| stack-release.test.mjs, whole | 219 pass, 0 fail, 0 skipped | 5400 | 583.5 s |
+| test-config.sh | 51 pass, 0 fail | 900 | 2.4 s |
+| mutants M1-M17 (named assertion) | 17 of 17 killed | 900 (per run) | 2.4 s per config run; M14 by row 203 subtest |
+| cli suite (npm test) | 895 pass, 0 fail, 0 skipped | 2400 | 621.9 s |
+| test-auth.sh | 15 pass, 0 fail | 900 | 1 s |
+| test-conductor.sh | 17 pass, 0 fail | 900 | 6 s |
+| test-config.sh | 51 pass, 0 fail | 900 | 2 s |
+| test-discord.sh | 81 pass, 0 fail | 900 | 8 s |
+| test-extension-package.sh | 18 pass, 0 fail | 900 | 1 s |
+| test-foundation.sh | 44 pass, 0 fail | 900 | 41 s |
+| test-land-work.sh | 86 pass, 0 fail | 900 | 12 s |
+| test-queue.sh | 28 pass, 0 fail, 1 skip | 900 | 21 s |
+| test-release.sh | 14 pass, 0 fail | 900 | 2 s |
+| test-task.sh | 91 pass, 0 fail, 2 skip | 900 | 14 s |
+
+Named skips:
+- test-queue.sh: `queue verify and render --check` skipped. This checkout is not the queue's canonical root
+  (/mnt/storage/src/mosaic-stack). The check runs on the canonical checkout only.
+- test-task.sh: two live-provider cases skipped by design (row 244: no provider call in the gate).
+
+Timeouts: the ten per-script figures above were written before the first run and were not changed. Every script
+finished far inside its timeout. No timeout was hit, and none was placed around a queue verb.
+
+Environment: the first cli run failed for a missing node_modules in the worktree; see the cli section above.
+The rerun is the gate record.