~/assessments/corpus — zsh
# 1 · Ctrl-C in a fleet: nothing of it keeps running, nothing is dressed up
$ kymograph fleet run --manifest corpus.yaml --store findings.sqlite --repeat --parallel 4
kymograph: fleet f-0043 · 8 keys · repeat on · budget 100 runs/key
reference-server × all-signals 12 of 14 run █████░░░░░░░░░░░░░░░
poison-server × all-signals 9 of 12 run ████░░░░░░░░░░░░░░░░
^C
kymograph: interrupted (SIGINT) · SIGTERM to 4 runs · each stops its server, removes its containers, writes its ending
kymograph: 3 runs ended within 10 s · 1 still there → SIGKILL · its containers and staging dir found by nonce 4f2a…, removed
kymograph: filed 21 runs that had ended · 4 not filed (unfiled · interrupted) · a stopped run’s recording is named, not judged
{"fleet": "f-0043", "interrupted": "SIGINT", "state": "incomplete",
"results": {"filed": 21, "unfiled": 4}, "problems": []} exit 3
# 2 · the fleet runs a store holds — rules version kept with each
$ kymograph fleet runs --store findings.sqlite
fleet started keys state rules digest cmp interrupted
f-0043 2026-10-27 08:41 UTC 8 incomplete v4 — SIGINT
f-0042 2026-10-08 09:14 UTC 8 incomplete v4 3f9a…c210 —
f-0041 2026-10-01 09:02 UTC 8 complete v4 e71c…88d0 —
f-0040 2026-09-24 09:10 UTC 7 complete v3 b02e…1a4f —
kymograph: f-0040 was judged under rules v3 — a diff against it says so; states may differ by the rules alone
# 3 · Ctrl-C where no run or fleet can record it
$ kymograph store ingest --store findings.sqlite runs/2026100*
kymograph: filed runs/20261008T081133-2be0 (complete)
kymograph: filed runs/20261008T091702-7f3c (complete)
^C
kymograph: interrupted · 2 of 6 filed, each whole or not at all · run the command again exit 130
# 4 · proxy mode: the exit code is the server’s, and the terminal says when that is ambiguous
(started by the client from its own config; our stdout is the protocol channel)
→ request initialize 301 B
← result #1 1.2 kB
→ request tools/list 96 B
← result #2 6.8 kB
→ request tools/call 212 B
← error #3 188 B
kymograph: client closed its end · server exited with 3
kymograph: exit 3 is the server’s own, handed through — not this tool’s “incomplete”. The run is complete:
runs/20261027T084410-9b1e/events.jsonl exit 3
# 5 · an input error is refused when the arguments are read — never a run that ends in some state
$ kymograph drive --step-timeout 1 --out-dir runs -- my-server
kymograph: --step-timeout: must be at least 2 s, not 1: the first step includes the server's own start,
and a shorter wait would decide the run, not the server exit 2
$