milestone-wraplisted

# Milestone Wrap Closing a milestone is **orchestrator + Notion + git state spread across several homes**, run once when a milestone's work is done. This skill is a human-driven, confirm-gated loop over those homes — it does not improvise steps, and it **pauses before the one outward-facing, hard-to-reverse action** (the release tag, which auto-updaters pick up within ~24h). > **Not `/wrap`.** `/wrap` sweeps a *session* for unpersisted residue. This closes a > *milestone*. Don't conflate them. ## Doctrine (same spine as /gate and /ops) - **Verify by reading, act via sanctioned surfaces.** Read the actual state (task board, gate readiness, DB, git) before asserting a step is done or needed; make every change through the project's sanctioned surface (the `/api/projects` route, the device-authed clients, `gh`), **never a raw DB write** and **never a mutation of the prod checkout's branches**. - **Confirm before the irreversible/outward-facing.** Marking done + updating Notion/ `context.md` bookkeeping is reversible (do it, report it). Advancing `main` is reversible-ish. Two actions have live, hard-to-casually-undo consequences and **pause for explicit go-ahead**: repointing `projects.auto_launch_milestone_id` (on an auto-launch project, this is what turns on auto-dispatch of the next milestone's `🗂️ Ready` + `💻 Code` tasks) and the **release tag + GitHub release, the point of no return**. - **Don't hand the work back.** Find the "several places" yoursel