andon-statuslisted

# andon-status Strictly read-only: inspect the ledger, never modify it, never run a new pass. Read settings first so you look in the right place: ``` python3 ${CLAUDE_PLUGIN_ROOT}/scripts/andon_core.py load-settings <repo_root> ``` Use the returned `ledger_dir` / `output_dir` for everything below. ## If the ledger has never run ``` python3 ${CLAUDE_PLUGIN_ROOT}/scripts/andon_core.py render-board <repo_root> <ledger_dir> ``` If this returns `{"never_run": true}` (no `log.md` at `ledger_dir`), say so plainly and suggest `andon-preflight` then `andon-loop` as next steps. **Do not fabricate a board** -- an empty-looking board that implies "nothing to do" is a different, false, message from "this has never run." ## If the ledger exists The same `render-board` call returns everything needed, computed from the ledger's actual files (never invented): - `stages` and `wire_rows` (each wire's status is **derived from its latest linked evidence doc's verdict tag** -- green/red/unknown -- never inferred from anything else). - `cursor`: the first open gap found, or `"converged"`. - `counters`: `total_passes`, `current_cycle`, `pass_in_cycle`, `cycles_converged` -- parsed from `log.md`'s actual `Pass N` / `Cycle N converged` entries. Never invent or estimate these; if `log.md` doesn't mention it, the count is what the script computed, not a guess. - `constraint`: the stage/wire with the most sub-cycle log entries, or the oldest open gap if none have sub-cycled yet. - `o