Verdict · read back from the recording, nowhere else
A run that is not a result is not “did not find”
$ kymograph verdict {{run.path}}/events.jsonl
state
{{run.state}}
exit {{run.exit}}
{{run.meaning}}
Causes — a fixed key beside the words
{{run.entry}}-
{{c.key}}{{c.words}} {{c.tag}}
{{run.note}}
What the recording holds — and where it falls short
events in order · the last line is read back, never assumed- {{e.type}} {{e.detail}}
verdict.CAUSES — can the server bring it about?
decides how a repeated series treats the run: worst case, or run againyes — stays in the worst case
no — not counted, the repetition is run again (at most 5 per key)
sandbox_failed is one key for two phases: before the target exists it cannot be the server’s; after, collecting the account can fail under what the target sent. Until it is split, it counts as “yes”.A recorded cap is complete
One message records at most 20 findings. Past that, findings_capped names every statement and signal it cut, with the true numbers. What was cut, and why, is known — the run is complete. If that event is lost, or its numbers do not add up, the run is incomplete again (cap_unaccounted).
The same idea for pagination: a listing cut at the driver’s page limit is capped, not complete — a truncated listing must not read as a full one. A comparison marks a gone finding whose pair the later run cut (cap_hint).
Whose exit code is it?
server_exited) and said on the terminal, never handed throughserver_failed and exits 4 — there is no observed outcome to hand through