harness-auditlisted

# /harness-audit ## Goal Produce **one interpreted health report** of the harness in a single read-only dry-run. The machine integrity layer (P1-1 `doc-reality.sh`, the CI jobs, and the `verify-all.sh` runner) is the *enforcement*; this skill is the *consumer* that runs it once, reads off a per-check pass/fail table, and turns each failure into a diagnosis a maintainer can act on. Concretely the report answers three questions with evidence: 1. **Is the harness passing its own gates right now?** — a per-check PASS / FAIL / SKIP table, taken verbatim from `verify-all.sh`. 2. **What does the doc-reality gate (P1-1) say?** — cited explicitly, because it is the gate that catches the harness lying about itself (phantom paths + drifted counts), and it is the one item most easily missed in a wall of green. 3. **For every non-PASS: why, and what next?** — the check's purpose, the likely root cause, the recommended fix, and whether it warrants a new backlog row. This skill supplies the *interpretation*; it does **not** re-implement any check. The checks live in `core/tests/` and CI; here you run them and read the results. ## Why this is a layer, not a duplicate of P1-1 P1-1 (`core/tests/doc-reality.sh`) is a **machine gate**: it runs in CI, exits 0/1, and mechanically blocks doc drift. This skill is the **agent consumer** that sits on top of that gate — it invokes the whole machine layer in one dry-run and *interprets* the results (root-cause, fix, backlog follow-up)