pr-finalize-completelisted

<!-- Generated by scripts/build-adapters.sh. Do not edit directly. --> # PR Finalize Complete Confirm a PR is genuinely merge-ready -- even when all issues were already addressed -- by verifying the evidence, not trusting the assumption. ## When to use this vs pr-finalize Use pr-finalize-complete when: - The branch owner says "it should be fixed already" and you need to confirm - Review bot findings may be stale (comments on old file paths, already-changed code) - You need to produce a verification report, not just drive fixes -- CI was green before but you need to re-confirm after a rebase Use pr-finalize when starting from scratch on an unaddressed PR. ## Inputs - **PR number or URL** (optional): detect from the current branch if not given. - `--no-push` (optional): run all verification steps but skip the final push. ## Non-negotiables - **Never claim a test passed without running it.** Report the actual exit code and test count. - **Never resolve a bot comment without checking whether the issue still exists in the current code.** Stale comments are common and silently resolving them is wrong. - **Never git add -A.** Start with a clean tree; stage only files your fixes actually touched. - **Stale comments are not done -- they are no longer applicable.** Distinguish the two in your report. ## Instructions ### 1. Establish ground truth ```bash gh pr view <PR> --json number,title,body,state,isDraft,headRefName,baseRefName,mergeable,mergeStateStatus,reviews,statusCh