refine-pr-review

# Refine PR review The **Refine** phase for review feedback: turn a `.PR-REVIEW.md` (from /fetch-pr-review; ask if the path is ambiguous) into user-settled per-comment verdicts, drafted replies, and a REQUIREMENTS file covering the accepted code changes. Triage and replies are settled here; the plan and execute phases see only code changes. ## Verdicts - **address**: the change enters the requirements in full; the reply stays a canned one-liner ("fixed", "good catch, thanks"). - **partial**: part of the change is accepted into the requirements, and the reply explains what was done and what was kept and why. - **push back**: no code change; the reply carries the reason. ## Phase 1 — triage every comment with the user Read the code behind each comment first: verify its premise against the current codebase, never judging from the quoted hunk alone. Then form a recommendation — verdict, reasoning, and (for partial and push back) a draft reply. Nothing is decided silently: - **Contentious ones one at a time**: every comment recommended partial or push back, or uncertain, is its own question carrying recommendation, reasoning, and draft reply. - **Obvious ones as one batch**: then list the comments recommended address or no action for a single confirmation; the user can pull any item out for individual discussion. Per comment type: - Open/active human threads → full triage. - **Outdated** → code check first; when the concern is moot in the current code, recommend "n...