complete-milestonelisted

# Complete Milestone ## Overview Orchestrate every issue in a cliban milestone to completion: one agent per ticket, run in dependency order, each isolated in its own worktree, each driven through a planning stage then a test-first execution stage. The orchestrator owns integration and merges; agents never merge. **Craft-stack dependencies:** the planning and execution stages inside each ticket agent run on the craft stack bound in the repo adapter (`docs/agents/issue-tracker.md`, see cliban-workflow's Per-Repo Binding) — the milestone uses the same operating rhythm as solo work in the repo, just one instance per ticket. Known mappings: **superpowers** (`writing-plans`, `subagent-driven-development`, `using-git-worktrees`, `finishing-a-development-branch`) and **mattpocock-skills** — but note their workflow entry points (`implement`, `to-spec`, `to-tickets`) are user-invocable only (`disable-model-invocation: true`), so a ticket agent cannot invoke `/implement` via the Skill tool. Instead it follows implement's rhythm through the suite's agent-invocable building blocks: `mattpocock-skills:tdd` at the plan's seams, typecheck regularly, `mattpocock-skills:code-review` before reporting. No adapter or no stack: use the generic fallback given inline at each stage. The cliban-workflow contract (where specs, plans, and logs live) applies under every stack and supersedes any file-based artifact locations those skills describe. **Core principle:** The orchestrator is a conductor, n