pr-finalizelisted

<!-- Generated by scripts/build-adapters.sh. Do not edit directly. --> # PR Finalize One PR, taken all the way to merge-ready. The job is not "make the bots stop talking": it is **land the change in a state a careful reviewer would sign off on**, with evidence for every claim. ## Inputs - **PR number or URL** (optional): detect from the current branch if not given. - `--no-push` (optional): do everything except the final push. Use when the repo auto-merges and the user wants to eyeball first. ## Non-negotiables These are the failure modes this skill exists to prevent. Violating one makes the whole run worthless: - **Never report a gate as passing without having run it.** Paste the real output. "Tests should pass" is not a result. - **Never resolve or claim-fix a finding you didn't actually fix.** Blocked is an honest outcome; a false "done" is not. - **Never `git add -A`.** Stage only the files your fixes touched. Start from a clean tree so that's safe. - **Never invent test coverage.** If the change has no browser-reachable surface, say so explicitly and name the suite that *is* the real gate. Do not add a hollow E2E test to look thorough. - **A green CI badge is not proof.** Many repos split their required check from the full suite (browser-free half only, etc.). Find out what the required check actually runs. ## Instructions ### 1. Establish the ground truth ```bash gh pr view <PR> --json number,title,body,state,isDraft,headRefName,baseRefName,mergeable,mergeStat