phase-auditlisted

# Phase Audit This skill verifies that the artifacts the rest of the workflow trusts are actually consistent: that the index matches the logs, the logs match the files they cite, design docs are in sync, and git has no leftover branches/worktrees. Everything downstream (`phase-recap`, `phase-loop`, `phase-decompose`) assumes these hold — this skill is what guards that assumption. It is **not a phase** (no plan/log for running it). It is read-only by default; any fixes it applies are a docs-lane change (branch + PR), never a direct commit to the default branch. It produces a report — the 🩺 banner below. ## Appendability is not a defect Before listing checks: **never flag later additions to an old theme as drift.** A `3.8.0` logged long after Major 3 "finished", or a `3.4.3` Patch on a months-old Minor, is the workflow working *correctly* (see [TERMINOLOGY.md → Core principle](../../../TERMINOLOGY.md)). Numbering gaps and out-of-numeric-order index lines are expected, not errors. Audit checks *consistency*, not *recency* or *numeric tidiness*. ## What to check Run these against `development/phase_log/` and git. Order findings most-severe first. **Integrity (high severity — the log is lying):** 1. **Orphan plan.** A `phase_<NUM>_plan.md` with no matching log, where the index does **not** annotate it as open/partial/planned/abandoned. Either it's an undocumented in-flight phase or a forgotten one. (A plan-with-no-log that the index *does* annotate is fine — that's a know