Diagnose harness misbehavior from the flight recorder — the local, append-only ledger at .vigiles/runs.jsonl that vigiles writes as your harness runs. It records what actually happened, so you debug from evidence instead of guessing.

What's in the ledger

One JSON record per line, each with a kind:

hook — a compiled-hook gate decision: {event, decision: allow|deny|ask, mode: enforce|observe, rule, cmd, reason}.
agent — a subagent tool-contract decision: {name, tool, allowed, reason} (a false = the agent went outside its lane).
skill — a skill activation: {name, fired}.
eval — a measured metric: {name, metric, value} (e.g. trigger-rate recall/precision).
capability-diff — a blast-radius change: {pr, added, removed, widened}.

debug-my-harness

What's in the ledger

Instructions

Step 1: Read the ledger