C1 crash-safe turns — run 2026-10-30 09:02–09:04 (UTC+8)
Task (pre-registered): one user message asks for `echo step1 >> count.txt`, then `sleep 30; echo step2 >> count.txt`, then the contents of count.txt.
kill -9 the daemon after step1's tool result is saved and while step2 sleeps; restart; no further user message.

Timeline (UTC+8):
 09:01:56 step1 run_command finished and saved (tool_runs row).
 ~09:02  step2 run_command got status needs_approval: the Sentinel reviewer "couldn't decide" (see 04-c2) — so it waited for us. Not part of the crash test.
 09:03:13 we approved it via POST /api/approvals/<id> {"decision":"approve"}.
 09:03:18 kill -9 of the daemon (node src/main.ts) during the sleep.
 09:03:19 daemon gone; its child `/bin/sh -lc sleep 30; echo step2 >> count.txt` was STILL RUNNING (orphaned, not killed).
 09:03:20 daemon restarted (daemon-3). No new message sent.
 09:03:49 step2 run_command finished again after restart (re-executed from the start).
 09:03:51 read_file count.txt; 09:03:59 turn status = done.

count.txt afterwards:
step1
step2
step2

Turns:
  ('973e408d-ede8-4d23-9d55-78bf9b808281', 'done')
tool_runs (one row per tool-call id):
  ('call_052496c7774d4e6e8f5bff2d', 'run_command', '{"exitCode":0,"stdout":"","stderr":""}', '2026-10-30 09:01:56')
  ('call_847efa1e83884340b371d5b2', 'run_command', '{"exitCode":0,"stdout":"","stderr":""}', '2026-10-30 09:03:49')
  ('call_a0a2fe4c242a4824ae9205cc', 'read_file', '{"content":"step1\\nstep2\\nstep2\\n"}', '2026-10-30 09:03:51')
approvals:
  ('call_847efa1e83884340b371d5b2', 'run_command', 'approved', "The safety check couldn't decide, so it's asking you.")

Transcript:
  [1 user] text: Run these two shell commands one at a time, in this order. First: echo step1 >> count.txt   Second: sleep 30; echo step2 >> count.txt   Then tell me the exact contents of count.txt.
  [2 assistant] reasoning: The user wants me to run two shell commands one at a time, in order:
1. `echo step1 >> count.txt`
2. `sleep 30; echo step2 >> count.txt`

Then tell them the exact contents of count.txt.

Let me run the first command.
  [2 assistant] tool-call call_052496c7774d4e6e8f5bff2d run_command {"command": "echo step1 >> count.txt"}
  [3 tool] tool-result call_052496c7774d4e6e8f5bff2d {"exitCode": 0, "stdout": "", "stderr": ""}
  [4 assistant] reasoning: The first command ran. Now the second: sleep 30; echo step2 >> count.txt
  [4 assistant] tool-call call_847efa1e83884340b371d5b2 run_command {"command": "sleep 30; echo step2 >> count.txt"}
  [5 tool] tool-result call_847efa1e83884340b371d5b2 {"status": "needs_approval", "approvalId": "17082186-bacf-4aa4-aff8-4ea3838ad121", "reason": "The safety check couldn't decide, so it's asking you."}
  [6 tool] tool-result call_847efa1e83884340b371d5b2 {"exitCode": 0, "stdout": "", "stderr": ""}
  [7 assistant] reasoning: The user asked me to run two commands and then tell them the exact contents of count.txt. Let me read the file.
  [7 assistant] tool-call call_a0a2fe4c242a4824ae9205cc read_file {"path": "count.txt"}
  [8 tool] tool-result call_a0a2fe4c242a4824ae9205cc {"content": "step1\nstep2\nstep2\n"}
  [9 assistant] reasoning: The user asked me to run two commands and then tell them the exact contents of count.txt. Let me read the file to see what's in it.

Wait, the file shows "step1\nstep2\nstep2\n" - that's odd. It seems like step2 was written twice. But the user only asked me to run the commands once each. Let me think about this...

Actually, looking at the output, it seems like the second command may have been run
  [9 assistant] text: The exact contents of count.txt are:

step1
step2
step2

Result vs pass marks: turn reached done after restart with no nudge; step1 appears exactly once; every tool-call id has exactly one tool_runs row → V2 by the pre-registered mark.
Finding: the tool that was in flight at the crash was started again after restart, and the old child process kept running after the daemon died, so its side effect (step2) happened twice. "Finished tools never run twice" held; an interrupted shell command is not protected from running twice.