
╭────────────────────────────────────────────────────────────────────╮
│  Hankweave v0.11.0                                                 │
│  linux x64 • node v22.23.2                                         │
╰────────────────────────────────────────────────────────────────────╯

Resuming execution in: ~/.hankweave-executions/<exec-id>
Removed a stale diet pair found beside the live events.jsonl (verified duplicate of the journal; interrupted prune or diet)
Resuming: <exec-id>
  Source → data-after-checkpoint
  Exec   → ~/.hankweave-executions/<exec-id>
  SDKs   → Claude node_modules ✓

╭──────────────────────────────────────────────────────────────────────────────╮
│  Kill and resume v1.0.0                                                      │
│  2 codons • 0 loops                                                          │
╰──────────────────────────────────────────────────────────────────────────────╯

├─ [1] write-line (Write one line)
│     model: haiku │ mode: fresh │ prompts: 1 (2 lines)
│     checkpointedGlobs: 1
│     ↓
└─ [2] write-second (Write a second line)
      model: haiku │ mode: fresh │ prompts: 1 (2 lines)
      checkpointedGlobs: 1

!  Output directory '<workspace>/fixtures/scenarios/kill-and-resume/out-after' is not empty. Conflicting files will be renamed (e.g., file.txt -> file_1_<timestamp>.txt).
[<ts>] [ERROR] Execution thread failed, rolling back...

══════════════════════════════════════════════════
  Hankweave Server Started
  WebSocket: ws://localhost:<port>
══════════════════════════════════════════════════

Running in headless mode on port <port>
➜ Listening on: http://localhost:<port>/ (all interfaces)
exit=0
