Post-Task Verification (/done)

done is the single place a task closes. Send each check to the surface the user will touch and use repo checks only as evidence for surfaces they cover.

1. Bind the run and select acceptance lanes

Write down the original request as a stable, complete summary. Fold later user corrections into that summary before you move on.

For an initial Git run, record the exact outputs of git rev-parse --abbrev-ref HEAD as the branch and git rev-parse HEAD as the pre-verification head. A branch rename or switch invalidates the card. A post-publication run resumes the same card and keeps its branch, pre-verification head, base, and verified snapshot, except for the explicit existing-PR base-rebind path below.

For PR-bound work, settle the intended base once here. Use the repo policy when one exists. Otherwise look at the default and integration candidates:

gh repo view --json defaultBranchRef -q .defaultBranchRef.name
git ls-remote --heads origin 'refs/heads/dev*' 'refs/heads/develop*'

Pick the one clear active dev or develop integration branch and fall back to the default when none exists. Stop and ask when more than one candidate still looks plausible. Refresh only the exact chosen origin ref, then record its name, remote base-tip SHA, merge-base SHA, and the exact commands you ran: