finishing-a-development-branch

# Finishing a Development Branch ## Overview Integration choice and checkout lifetime are separate. Verify first, mutate only task-owned resources, then prove what was removed or retained. **Core principle:** fresh evidence -> authorized integration -> ownership-aware cleanup -> Git/path readback. **Announce at start:** explain which branch/worktree lifecycle is being closed. ## Step 1: Environment and Ownership Detection Read the task's `TaskStartSnapshot` and current repository state. Record: - root, `HEAD`, branch/detached state, upstream divergence, and active Git ops; - staged/unstaged/untracked paths and the task-owned delta; - `git worktree list --porcelain`; - branch/worktree creator, task ownership, base branch, and cleanup trigger. Stop on conflicts, detached state, failed verification, dirty/untracked state in a cleanup target, or unknown ownership. Do not infer the base from the names `main` or `master`; use task records, repository authority, or explicit user direction. Never auto-stash, reset, clean, pull, rebase, amend, force-push, or bypass hooks. If no task-created branch/worktree exists and integration was not requested, skip this workflow: report the local task commit plus `Task clean` and `Repository clean`; do not invent merge/PR ceremony. ## Step 2: Fresh Verification Run the smallest current-authority test set that proves the completed task. If it fails, preserve all work and return to diagnosis. Do not present the branch as ready. ## Step 3...