finishlisted

# Finish Finish is the interactive delivery handoff. Its job is to inspect what the thread has actually produced, surface any unresolved signals, and let the user decide how to deliver the current branch. It does not judge whether the thread is objectively complete, and it changes no thread artifacts — the inspection is read-only and the only mutations it performs are the git operations the user explicitly selects. Run it in three moves: inspect readiness and report the signals, ask how to dispose of the branch, then execute the chosen disposition. Branch delivery is inherently user-directed — no autonomous default is safe across users, repositories, or branch contexts — so the disposition is always the user's explicit choice. ## Resolve the active thread The thread root is a folder under `docs/threads/` named with a UTC-timestamp slug (e.g. `docs/threads/250522143000Z-my-feature/`). If the current working directory already sits inside a thread root, that is the thread. If several thread roots exist and which one is active is ambiguous, ASK the user — never silently pick the most recent timestamp. All within-thread paths below are thread-relative; git and branch state come from the current branch as found. ## Readiness inspection Run a lightweight, read-only inspection pass and report what it finds. Inspect: - **The apparent principal outcome.** For implemented work, whether `implementation-report.md` exists at the thread root. For Roadmap work, whether `roadmap.md` ex