status

/audit:status — pipeline status report

Run

python3 "${CLAUDE_PLUGIN_ROOT}/scripts/status/audit-status.py" <manifestPath> $ARGUMENTS

Print its stdout verbatim. Do NOT re-format, summarize, re-tabulate, or "improve" it.

It already renders the whole report: an overall line with a progress bar, the usage line when metering is on, one aligned table across every phase (markers [x] done · [~] in_progress · [!] blocked · [ ] pending), what each pending task is waiting on, a tests column carrying the verdict of the run that last exercised each task exactly as the manifest recorded it — shown only when a task in view has recorded one, so a plan that has never run a gate renders exactly as it did before the column existed, and - inside it means no run was recorded, which is not a failure — the ready-now list with a copy-pasteable /audit:run <id>, open bugs, parked proposals when /audit:init parked any (plus a one-line footer counting free-form legacy proposals, which /audit:propose list still reads), a BY AREA rollup when the plan tags areas (per tag: phases and done/total tasks, - <owner> when the area declares its advisory owner, an untagged footer, and — only when a phase actually carries several tags — the caveat that such a phase counts under each), and a RESUMABLE line when a phase was interrupted.

This used to be prose telling you how to lay the rollup out. That cost tokens on every call and produced a different layout each time — the same self-defeating shape /audit:usage already refuses. You do not need to read the manifest either: the renderer reads it in-process, so the per-task detail that once required a second read is in the output already.

Pass $ARGUMENTS through unchanged. --json emits the machine-readable rollup instead, for CI or another tool.

--phase <id> scopes the human render to one phase - the table lists that phase alone, and the render says so on a line of its own. Totals stay whole-plan: the overall line, the usage line and the bug counts are the project's, not the phase's, because a phase view that silently rescoped them would misreport the project. And it does not scope the other modes - --gate evaluates its conditions over the whole manifest and --json emits the whole rollup, whatever --phase says, so --phase P3 --gate still gates on a task in P7. That last reading has already been got wrong here. An id no phase carries is a usage error (exit 2) naming the ids there are.