wrapuplisted

# /wrapup Finalize a feature. Close out the plan, archive the active state, capture lessons. ## When to use - All phases of a feature's `plan.md` are complete - Code review has returned APPROVE and PR is created (merge can happen before or after wrapup artifacts land) - Auto-suggested by `session-end.sh` hook when all phases checked ## Workflow 1. **Phase 1 — Load context.** Read the active feature's `plan.md`, `findings.md`, `progress.md`. 2. **Phase 2 — Verify completion:** - All checkboxes in `plan.md` are checked - **Code review passed:** read the latest `.studio/features/<id>/reviews/*-impl-review.md`. If the verdict is `CONCERNS` or `REJECT`, **stop** — wrap-up cannot proceed. Surface the open findings, resolve them, and re-run `/impl-review` until it returns `APPROVE`. The implementing agent writing `APPROVE` into the review file is not a gate verdict — APPROVE must come from a `/impl-review` re-run. - **PR created** (not necessarily merged yet — wrapup artifacts like lessons, `docs/INDEX.md`, and state archiving have no dependency on merge; they can land in the PR itself or as a follow-up commit on main after merge). If no PR exists yet, create one before continuing. - Tests passing on the feature branch (or on main if already merged) - Telemetry verified (if applicable) - Scope matches the original brief — invoke `/scope-check` if you haven't already this feature; closeout shouldn't paper ov