review-prlisted

Render a pull-request verdict against a head the reviewer itself brought current, never against a head that has already fallen behind the base. Sellable as `vantage-peers` plugin. ## PRINCIPLE — the reviewer updates BEFORE it gates, and gates what it OBTAINED A verdict is pinned to a head SHA (Day-82 head-pin doctrine): a rebase or base-advance produces a new head and voids the prior verdict. On a repo with `required_status_checks.strict = true` + squash merge, a PR falls "behind base" the instant any *other* PR merges — so a verdict requested on a stale head is a wasted review cycle, and the round-trip "please rebase / re-request" repeats per collision. This routine removes the round-trip by making "update before the verdict" a mechanical FIRST STEP of the review, not a human instruction the requester has to remember. The reviewer updates the branch itself (allowed: `allow_update_branch = true`), reads back the head it OBTAINED, and pins its verdict to that head. It never sends a request back for being late — it makes the request current and gates it. This is the immediate net. The structural closure is GitHub's merge queue (which updates + tests + merges in order); this routine is what a reviewer does until, and alongside, that queue. ## WORKFLOW **Step 1 — Update the branch to the current base BEFORE any gating work** For the PR number `<pr>` on `<repo>`: ```bash gh pr update-branch <pr> -R <repo> ``` - `gh pr update-branch` merges the current base (`main`) into t