From aafcc857c980a24dc3730209b9719cb5c9407a11 Mon Sep 17 00:00:00 2001 From: Jason Woltje Date: Thu, 22 Oct 2026 12:50:51 -0500 Subject: [PATCH] row 269 (264b, #1774): BUILD.md M11 kill line is the survivor log assertion at session-launch.test.mjs:309, not the outcome assertion (mutant run 17:49Z, duckworth-0181) --- agents/gizmoduck/work/queue-269/BUILD.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/agents/gizmoduck/work/queue-269/BUILD.md b/agents/gizmoduck/work/queue-269/BUILD.md index 11370693c..a8727b2d1 100644 --- a/agents/gizmoduck/work/queue-269/BUILD.md +++ b/agents/gizmoduck/work/queue-269/BUILD.md @@ -267,7 +267,7 @@ another fence (sage-2707, C3 duckworth-0128). | M8 | a non-default session binds its workspace at the legacy `workspaces//` in-sandbox path | T1: `assert.equal` that a named session's in-sandbox workspace is its `session-workspaces///` path, read from the fake adapter's recorded cwd (sage-2717) | | M9 | `#threadRows` back to the default session only | T1: the named session's message starts its run | | M10 | the `legacy-run-live` refusal removed from check() | the legacy-run-live test: `outcome` equals `[[S, "legacy-run-live"]]` | -| M11 | recover() keeps a survivor only when the outer pid outlived the kill (the runner ignored) | the legacy-run-live test, same assertion | +| M11 | recover() keeps a survivor only when the outer pid outlived the kill (the runner ignored) | the legacy-run-live test: the survivor log `assert.ok` (session-launch.test.mjs:309); the host doesn't see the live runner, so the survivor line is never logged (run 17:49Z 10-22, duckworth-0181) | | M12 | check() reads every survivor, live or not | the legacy-run-live test: after the runner exits, `settle` gives one launch | M6 and the halt fences (C2, duckworth-0150). A plain halt never reaches start(). tick() admits first