Review Remediation

Consume one frozen set of existing PR feedback, establish the truth of every finding, and remediate confirmed problems. Reviewer identity and delivery surface are metadata; human comments, bot findings, security alerts, review bodies, threads, issue comments, checks, and annotations follow the same workflow.

Boundaries

• Address only the selected existing feedback. Later feedback belongs to another run; do not request, trigger, or wait for a new review.
• A remediation request includes local investigation, fixes, and verification. External replies, state changes, commits, pushes, and publication require explicit authority.
• Continue authorized fixes through verification and repair of attributable failures. Keep blocked items visible while completing independent work.

Inputs may identify a PR, exact review/comment/check/thread/run IDs or URLs, a reviewer, an expected SHA or time window, or a fixed set supplied by a supervising loop. Detect the PR from the current branch only when it is omitted.

Freeze The Feedback Set

Identify the PR, provider, branch, and head SHA. Collect concrete claims, questions, and requested changes from every provider surface relevant to the selector.

Selection rules: