From f7e4ec3df541de5ffbe6e18fea1724bb3911808d Mon Sep 17 00:00:00 2001 From: Jason Woltje Date: Thu, 22 Oct 2026 09:23:39 -0500 Subject: [PATCH] row 264a (#1769): BUILD.md records the r13 gate on 2cc34aef8 (phases 1-3 green, M2 thrown at the trigger) and the r13p4 rerun at 84f53540d (M1-M4 killed on assertions, M2's four edits and kill rule), and the limits row gets the measured probe time; doc only (mos-1280 item 1, sage-2701) --- agents/gizmoduck/work/queue-264/BUILD.md | 44 +++++++++++++++++++++++- 1 file changed, 43 insertions(+), 1 deletion(-) diff --git a/agents/gizmoduck/work/queue-264/BUILD.md b/agents/gizmoduck/work/queue-264/BUILD.md index 99bafbfbd..ab714d3c4 100644 --- a/agents/gizmoduck/work/queue-264/BUILD.md +++ b/agents/gizmoduck/work/queue-264/BUILD.md @@ -473,7 +473,7 @@ red, and goes to Sage first (sage-2637). A timeout in the shell phase goes to Mo | cli suite | 591 s | row 281's gate, 2026-10-22 (row 235 run 1: 535 s; Megavolt row 199: 472 s) | 1800 s | | webui suite | 57 s | row 278 run 3 (row 66 r2: about 60 s) | 600 s | | each scripts/test-*.sh | 42 s (test-foundation); task 36.8, queue 23.4, land-work 12.6, release 12.2, discord 8.8, conductor 8.1, config 3.2, extension-package 3.0, auth 1.9 | the longest of row 268's gate (2026-10-22 04:40Z), row 196's receipts and row 278 run 3 | 900 s | -| mutant probes M1-M4 (sessions.test, thread-claims.test) | none recorded | | 300 s | +| mutant probes M1-M4 (sessions.test, thread-claims.test) | 1 s wall each (longest `ℹ duration_ms` 512, M3) | the r13p4 rerun, 2026-10-22 14:08:43Z to 14:08:45Z | 300 s | ## Runs @@ -504,3 +504,45 @@ red, and goes to Sage first (sage-2637). A timeout in the shell phase goes to Mo delivery_same_session (3k-3l.sql:147-153) share the WHEN, the ops and the holder check, and differ only in taking the latest claim per session and in the text, so :330 keeps its strength. Commit 20 changes :341 to `/only to its session's holder/` and nothing else in that file. +- r13 gate, 2cc34aef8 on e479521d3, manifest 65e04d27, Sage's CLEAR sage-2684. Start + 2026-10-22 13:39:53Z, busy count 0, HEAD and digest printed and matched, blobs checked with + `sha256sum -c`. Every count below has 0 fail, 0 cancelled and 0 todo. + - Phase 1, the 20 touched files whole, one at a time, all 0 skipped, wall 600 s: bus + account-migration 3/3, chief-of-staff 42/42, comment-migration 5/5, end-launch 7/7, + gitea-migration 5/5, grant-migration 6/6, message-filter 6/6, name-migration 1/1, schema 1/1, + sessions 7/7, spec-migration 1/1, tester-writes 8/8, thread-claims 6/6, thread-migration 3/3, + threads 17/17, usage-migration 1/1; cli stack-release 218/218, thread-cli 11/11, + thread-launch 11/11; webui chat 23/23. + - Phase 2, suites whole: bus 827/827 (23 s), cli 837/837 (593 s), webui 345 pass of 346 with 1 + skipped (55 s). The skip is the esbuild 0.28.1 editor rebuild (Duckworth named it in + duckworth-0146; DEFERRED row 264a N2). + - Phase 3, the 10 scripts/test-*.sh, all rc=0: auth 15, conductor 17, config 31, discord 81, + extension-package 18, foundation 44 (36 s), land-work 86, queue 156 node tests and 28 suite + checks, release 14, task 91. The worktree was clean after. + - Phase 4: M1 killed by T2 at sessions.test:204 (6/7). M2 then failed with no assertion: T1 + (:89) and T7 (:422) threw `storage-refused` from #refused (broker.mjs:4082) through request()'s + catch (:4242), because the delivery_same_session trigger refused #delivery's INSERT. The run + stopped there at 14:02:47Z, total wall 1374 s, and M3 and M4 did not run. 0 node processes + left. Mos ruled option B (mos-1279): phases 1-3 carry and phase 4 reruns with M2's four edits. + - Logs: gizmo-264-out/r13-run.out, with the per-file, suite and probe logs under + gizmo-264-out/r13/single, r13/suite and r13/probes. +- r13p4, phase 4 rerun under mos-1279 at HEAD 84f53540d (2cc34aef8 plus commit 21, the M2 note + in this file), Sage's CLEAR sage-2688 with the fourth edit confirmed in sage-2690. Start + 2026-10-22 14:08:43Z, busy count 0. `git diff --name-only 2cc34aef8..HEAD` was this file only, + and the non-BUILD.md blobs matched manifest 65e04d27. Kit gizmo-264-out/probes-264-r13p4.py + (`--check ok`), each probe under `timeout -k 10 300`, each file restored and its sha checked. + End 14:08:45Z, failures 0, 0 node processes left. + - M1, the #agent generation fence set to `false`: killed, sessions 6/7, T2 sage-2257 at + sessions.test:204 (`assert.throws(fn, { code: 'not-holder' }, label)`). + - M2, four edits: the `mt.session=?` clause and its argument dropped from message.receive + (broker.mjs:5251), delivery_same_session dropped from 3k-3l.sql and from schema.sql, and + store.mjs:16 SCHEMA_SHA256 set to the sha256 of the mutated schema.sql. Killed, sessions 4/7, + by T1 at sessions.test:89 (a1's receive got the second session's message). T7 also failed on + its receive assertion at :422. T2 failed at :168, the trigger's own pin, which doesn't count as + a kill under mos-1279. The kill rule: only an assertion in a test that exercises receive + counts, never a thrown error. + - M3, generation counted over every claim row in 3k-3l.sql: killed, sessions 6/7, T7 at + sessions.test:390 (the thread_claims generations). + - M4, thread.claims back to the latest row per thread: killed, thread-claims 5/6, T6 at + thread-claims.test:133 (two held sessions list as two rows). + - Logs: gizmo-264-out/r13p4-run.out and gizmo-264-out/r13p4/probes/M1.log to M4.log.