finish-and-shiplisted

# Finish and Ship Close the whole delivery loop from the repository's real state. “Done” means the requested outcome is implemented, verified, recorded, pushed when authorized, and handed off without hidden leftovers. ## Safety - Read repository instructions and identify the requested scope before changing, staging, or discarding anything. - Treat existing dirty changes as user-owned until proven otherwise. Never hide them with a broad stash, reset them, or fold them into the task silently. - Do not lower a quality gate, skip failing checks, expose secrets, rewrite published history, force-push a protected branch, or trigger a deployment unless the request includes it. - A request to “commit and push” authorizes those actions for the completed scope; it does not authorize releases, merges, branch deletion, or unrelated cleanup. ## Workflow 1. Inspect repository instructions, branch/upstream, worktrees, status, recent commits, and the complete diff. Build an explicit ledger of requested work, user-owned changes, generated changes, and unresolved items. 2. Trace the changed behavior through its real entrypoints and tests. Search for placeholders, disabled checks, temporary debug code, stale docs, and unhandled call sites. 3. Run the narrowest relevant checks first. Fix failures within scope, then run the repository's full documented gate from a fresh command. 4. Exercise the real behavior when the task has a user-visible or integration surface. Use `preview-and-prove` for