row 271 (264d, #1776): BUILD.md r3 gate on 9e18a9aaf (sage-3017): cli and bus session-clear.test whole green (5/5, 19/19), cli suite 874/874, M14 killed by the T6 test's first lines() assertion at :365; no first-run red. Doc only.

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

@@ -767,3 +767,24 @@ r3 gate, on a CLEAR (sage-3001): the touched files run whole, the cli suite runs
 No src file changed in r3, so the full gate isn't due again. A first-run red in the new test is
 placed under mos-1272 and reported after; a fix that needs a product change goes to Sage and Mos
 before any edit.
+
+## r3 gate on 9e18a9aaf (sage-3017)
+
+Run 21:16:37Z to 21:27:04Z (627 s wall), TMPDIR /mnt/storage/scratch/tmp/gJmI, limits as in "Run
+limits" above (300 s per file and per mutant run, 1800 s for the cli suite). origin/refactor was
+f2735bb6a. No src file differs from e567f949c, so the full gate wasn't due (sage-3001).
+
+| Run | Result | Wall |
+| --- | --- | --- |
+| cli session-clear.test whole | 5/5 pass | 12 s for both files |
+| bus session-clear.test whole (r3 touched no other test; the bus half of the clear) | 19/19 pass | |
+| cli suite whole | 874/874 pass, 0 skipped or todo | 585 s |
+| M14, bus session-clear.test | 19/19 pass (M14 is launcher-only) | 30 s for both |
+| M14, cli session-clear.test | 1 fail: the T6 test | |
+
+- First-run reds: none. The new T6 test passed on its first run, so nothing was placed under mos-1272.
+- M14 kill: an AssertionError at session-clear.test.mjs:365, the T6 test's first `lines()`
+  assertion, as named above. The ticker's catch logged `thread tick: broker exited before it
+  replied` once per tick and the clear's own line never appeared.
+- The tree was clean after the tests and after the M14 restore; launcher.mjs matched HEAD. No node
+  process was left with its cwd in the worktree.