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. ## Naming a comment Never refer to a comment by index or position, anywhere — questions, batch lists, hand-off text. Quote its opening words instead, truncated to the shortest unique prefix — the comment "the null check here misses …". Always verbatim, never translated or corrected, so the quote can be searched on the page. Only the ANSWERS table's own row numbers stay, for in-file cross-references. ## 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, and every question to the user is worded via `explain-in-simple-language` when available, the draft rep...