Background (round 4, snapshot10e): 7/7 pass.
d5: new TaskList used live; backgroundShells listed all 8 ids/commands/'stopped, exit code 143' exactly matching the tasks frame. Limit message and repeat guard correct.
d6: driver SIGINT -> 'Stopped before this turn finished.' is the right wording (signalAbortCause maps SIGINT to user); interrupted turn saved with marker, synthetic 'Not run' for the unstarted call, no orphan tool_use; resume did not redo npm init/install/FileWrite.
d7: SIGKILL -> server port free 733 ms later; session paired. Guillotine monitor not started (cloud provider, guardEligible false) -> watchdog change not exercised live here; covered by unit test and the local-model runs.
Cosmetic: d2 exit code now appears three times in one Bash error result (BashTool.ts:1081-1088 + toolRunner.ts:355-356).
Harness: leftovers() ps check misses commands without the run folder (node --watch, sleep 300, foreground sleep); port checks and frames show nothing leaked.
