finish-worklisted

# Finish Work Ship-phase entry skill. Close out a branch safely. Run the pre-merge gate, decide between four finish options, and handle launch ritual when production traffic is involved. ## Iron Rule <EXTREMELY-IMPORTANT> 1. NEVER push to main, force-push, merge a PR, or stage a launch without explicit user authorization for THIS specific action. Prior approval for unrelated work does not transfer. 2. NEVER auto-merge a PR with a failing required CI lane. 3. NEVER skip the pre-merge gate (simplicity + tests + failure-mode + evidence + reviewer) because "the diff is small". A user waiver granted at an earlier phase carries forward — quote it in the finish menu's gate status (which gate, the user's words) instead of re-demanding the waived work or skipping silently. 4. The reviewer who flagged a BLOCKER is not the final authority on whether it is fixed — the qa-tester / Lead floor confirms before merge. 5. Worktree cleanup follows order: merge → verify → `cd` to main root → `git worktree remove` → `git worktree prune` → delete branch. Reversed order leaves stuck refs. Only remove worktrees we created (path under `.worktrees/` or `worktrees/`); never touch harness-owned workspaces. </EXTREMELY-IMPORTANT> ## When to use - Implementation done, verified, reviewed - Branch ready to merge or PR - Long-running branch needs a stop decision (keep / discard) - Production launch with rollback plan needed - CI is red and needs to be triaged before merge Skip when: - The branch is not