Finish a Branch

Decide what happens to completed work: gate on verify, detect the environment, offer a fixed menu, execute the choice, clean up safely. Terminal crossings use record-before-crossing via record-decision.

1. Gate: verify, trace, and acceptance

REQUIRED SUB-SKILL: use verify to run every verify command from docs/agents/project.md (typecheck, lint, unit, e2e) fresh AND to confirm the trace check is clean — a branch must not merge with untraced requirements, the same gate release enforces. If no test command is discoverable, ask the user for it and suggest setup-repo.

If the branch has user-facing behavior that has not been driven through the running system, REQUIRED SUB-SKILL: use acceptance-check before offering Merge or PR — green units prove assertions pass, not that the feature works.

On failure: show the failures. While any verify, trace, or required acceptance check fails: withhold merge and PR; still offer terminal block and discard (emit a decision record against red evidence). Mechanical failure alone, or pause/defer, without an explicit terminal block/discard → no decision record.

Done when: green path can offer the full menu, or red path has offered only block/discard (or the user paused).