v0.1.1

v0.1.1 — exit codes documented truthfully

Agent loop detector: find where an AI agent looped and burned tokens, before it runs again. Zero-dependency CLI.

What changed

• Each gate now documents its own exit codes (0 / 1 / 2). The previous wording —
  "0 = clean, 1 = findings" — was wrong for gates that measure rather than judge.
• leak-gate: a mistyped path used to print scanned 0 file(s) and exit 0. A typo in
  CI meant a permanently green gate. It now exits 2 with error: path not found, and also
  errors when nothing was scannable.
• A contract test now asserts, for every gate: bundled example exit code = documented value,
  and a non-existent path exits 2.

About the bundled example

It exits 1: the bundled input is deliberately broken — that is the demo, not a bug

License

Code: Apache-2.0 · Spec & docs: CC BY 4.0