review-pr-thread-verify

# review-pr-thread-verify Decide what has happened to one review finding since we posted it. The caller hands over everything; this skill judges and returns, and never posts, resolves, or edits anything itself. **Receives.** The original finding (its anchor, body, the commit or head SHA it was reviewed at, and the concrete concern it raised); every author reply on the thread since our last message, plus every prior reply we posted there; the current code at the anchor with nearby context, and any commits since the original review that touched the relevant range; the full PR history (all comments, review threads, commit messages, the current PR description, our prior review and comment bodies); bundle context for each linked PR (diff, description, top-level conversation); and the caller's voice profile — its rules for how a posted comment reads — to apply to any reply drafted here. **Judges.** Read the concrete concern first and hold it fixed: the question is whether *that* failure mode is gone, conceded, disproven, or still live — not whether the thread has been discussed. A code change counts only when it touches the relevant range and removes the failure mode; a reply counts only when a fair-minded human reviewer would concede it. Push back only on new signal — a new author reply or a code change — and stay on the specific point under contention; never repeat an argument already made on the thread. **Returns exactly one disposition:** - `addressed-by-fix` — A commit after our review modified the relevant code and removes the concrete failure mode. Straightforward code fixes need no reply unless there was active discussion to answer; draft one only then. - `addressed-by-valid-reply` — The author replied on this or another thread with an argument a fair-minded human reviewer would concede: correct factual context, a deliberate owner trade-off, a valid out-of-scope boundary, or code elsewhere already covering the concern. Draft a short concession or acknowledgment. - `false-positive-or-stale` — Our comment was wrong, stale, or is disproven by current PR history. Draft a brief correction that owns the miss. - `needs-our-pushback` — The author replied or changed code, but the concrete concern remains. Draft a short reply for the existing thread on that specific point. - `still-pending` — No relevant new author reply and no relevant code change since our last look. Draft nothing. **Return shape.** The disposition name, one short reason (the evidence: the commit, the reply, or the absence of either), and the drafted reply text when the disposition calls for one, written in the supplied voice profile.