ifbars/diffuin/change-pull-request

Change a Pull Request

Treat the latest authorized request as a code-delivery contract. Read the PR body, complete base-to-head diff, prior conversation, and relevant surrounding code before editing.

1. Interpret the requested outcome from the whole message instead of relying on a fixed verb list.

For a submitted changes-requested review, verify every supplied finding against the current source. Identify each disposition by comment ID, explain false positives or already-fixed findings with evidence, and fix only applicable findings. If no changes are needed, leave the worktree unchanged and return the explanation.

1. Start from the checked-out PR head and preserve the PR's existing intent, base-branch compatibility, and unrelated work.
2. Make only the requested changes and the smallest supporting test or documentation updates needed for correctness.
3. Run focused validation first, followed by the appropriate repository build and test gates.
4. Leave the worktree changed only by the intended follow-up. Diffuin handles commit and push after the run.

Do not commit, push, create another pull request, or rewrite history. Do not claim game or runtime validation that was not performed. If the requested change conflicts with the PR or is genuinely blocked, return the exact conflict or blocker instead of making speculative edits.