ironlint-review

# IronLint Review Audit the check set against telemetry. Surface candidates for removal, scope adjustment, or a source fix. ## Source of truth `.ironlint/log.jsonl` — one record per check invocation, with a **per-check** breakdown. Each line: ```json { "type": "check", "ts": "2026-06-15T00:00:00Z", "file": "src/foo.rs", "status": "block", "elapsed_ms": 42, "checks": [ {"check": "no-debug", "status": "block", "elapsed_ms": 30}, {"check": "no-todo", "status": "pass", "elapsed_ms": 12} ] } ``` - The top-level `status` is the most severe of the checks that ran (`block` > `internal_error` > `pass`). There is no `warn` tier. - `checks[]` attributes the outcome to each check by id, so you can recommend on **specific checks**, not just files. `checks` is empty when no check matched the file. - A check with `status: "internal_error"` carries a `reason` (timeout, not_found, …) — it *couldn't run*, which is a broken check, not a finding. ## Process 1. Read `.ironlint/log.jsonl`. 2. Aggregate over the last N entries (default last 1000, or all if fewer), grouping by `checks[].check` (and cross-referencing `file`). 3. Surface concerning patterns per check: - **High block rate** (>50% of the files a check ran on): the check may be too strict, or the code it covers genuinely needs fixing at the source. - **Zero blocks across many runs**: the check may be dead — its `files` scope never matches anything dirty, or it never fires. Confirm i...