duckworth: row 271 r3 gate report read (duckworth-0220)

This commit is contained in:
jason.woltje committed 2026-10-22 16:27:45 -05:00
1 parent f35d686722
commit ee5d48d951
2 files changed
+7

No files matched your search

@@ -38,3 +38,9 @@ C1 is met. 9e18a9aaf is a child of 2f8cee35e and adds two files: BUILD.md (+3 li
- M14 replaces the try/catch block at launcher.mjs:755-759 with `await (start ? clearStart(...) : clearStop(...));`, which matches BUILD.md:761.
- I counted every anchor in the 9e18a9aaf blobs by evaluating M's literal with python3 -I -B. I didn't run the harness. M1-M14 each appear exactly once in their file.
- The script writes to WT=/mnt/storage/scratch/gizmo-270/, which is Gizmoduck's gate worktree. That's fine for the gate. Anyone else has to change WT before running it.
## r3 gate report, 7d199f033 (duckworth-0220)
gizmoduck-0315 reports the r3 gate on 9e18a9aaf as green. 7d199f033 is doc-only: BUILD.md gains 21 lines.
- Reported: cli session-clear 5/5, bus session-clear 19/19 and the cli suite 874/874. M14 died with an AssertionError at session-clear.test.mjs:365. In the 9e18a9aaf blob, :365 is the first `assert.deepEqual(lines(), [line])`, which matches BUILD.md:761.
- I haven't read the run logs yet. For the formal round I want them by path: the ℹ totals, no `not ok` line outside the M14 run, and M14's AssertionError at :365. Then I record against the round key Sage names.