Validate PR Review Comments

Purpose

Triage the review comments on the current pull request using the GitHub CLI gh: evaluate each comment on its technical merits, implement only the feedback that holds up, reply to each thread with a clear position, and map any resulting edits to fixup commits for the user to run.

Prerequisites

• Authenticated GitHub CLI (gh auth status) with access to the repository.
• The PR branch checked out locally, with no unrelated uncommitted changes.

Core Principles and Constraints

• Evaluate before implementing. Reviewers act in good faith but rarely have full context — a suggestion can be wrong, already handled, or out of scope. Blindly applying every suggestion degrades the code, and a well-reasoned "no" is often the more useful reply.
• Reply to every triaged comment with a concise, professional, technically grounded position — whether or not it results in a change. Replies are immediately visible to reviewers and cannot be quietly retracted, so draft the full set locally and post only after the user approves it.
• Keep changes scoped to the review feedback; no unrelated changes or drive-by refactors.
• Never create commits. The user's commits are GPG-signed with a YubiKey that requires physical touch, so no commit can be completed here. Modify the working tree only and hand the user suggested git commit --fixup commands to run manually.
• Do not push branches, resolve or dismiss review threads, or submit a final PR review unless explicitly instructed.
• Beware of pagination in git and GitHub cli, set PAGER=cat and GH_PAGER=cat.