phase-closelisted

# phase-close — phase-level verification gate At a **v3.x phase boundary** (e.g. v3.2-close after its last wave), before declaring the phase done or bumping the plugin version, spawn three independent **full-context, in-substrate** lenses in parallel to verify the **integrated phase against its exit criteria**. This catches what the per-PR / per-wave VALIDATE cannot, *by construction*: - **cross-PR contract drift** — a contract whose shape changed between PR-A and PR-B (each PR's review saw only its own diff); - **accumulated debt** — merged-but-dark deployment state, deferred follow-ups piling up, reserved-not-produced surfaces; - **phase-claim honesty** — "phase complete" vs the exit criteria *actually* met (deferred-but-claimed). **Precedent:** the v3.1 phase-close sign-off (PM honesty-auditor + principal architect, both CLOSEABLE — `docs/ROADMAP.md`). This formalizes that proven ad-hoc pattern. It is the **post-phase analog of `/verify-plan`** (which is pre-approval) and is **coarser** — it fires ONCE per phase, not per PR. ## When this skill applies - A v3.x phase (not a single wave/PR) is being declared complete OR the plugin version is about to bump. - The phase has a defined set of **exit criteria** (in its scope doc / `docs/ROADMAP.md`) and ≥2 merged PRs. ## When it does NOT apply - A single PR or a sub-wave (the per-wave VALIDATE already covers that — do NOT re-litigate per-PR diffs here). - A phase with no integration surface (one-PR phases). ## Procedure (