PR review feedback workflow

Addressing review feedback

After addressing PR review feedback, resolve the corresponding review thread(s) before concluding; if you lack permission, state it explicitly.
Before re-requesting review after addressing feedback, run the relevant verification suite and summarize results (commands + outcomes) in the PR comment/description.

After pushing fixes for PR review feedback, re-request review only from reviewer(s) who posted the addressed feedback in the current round.
Do not re-request review from reviewers (including AI reviewers) who did not post addressed feedback, or who already indicated no actionable issues.
If no applicable reviewer remains, ask who should review next.

When Codex and/or Copilot review bots are configured for the repo, trigger re-review only for the bot(s) that posted addressed feedback.

For Codex re-review (only when applicable): comment @codex review on the PR.
For Copilot re-review (only when applicable): use the GitHub API to remove and re-request the bot reviewer copilot-pull-request-reviewer[bot] (do not rely on UI-based reviewer assignment).
- Remove: DELETE /repos/{owner}/{repo}/pulls/{pr}/requested_reviewers with body {"reviewers":["copilot-pull-request-reviewer[bot]"]}
- Add: POST /repos/{owner}/{repo}/pulls/{pr}/requested_reviewers with body {"reviewers":["copilot-pull-request-reviewer[bot]"]}

Use DELETE /notifications/threads/{id} (HTTP 204) to mark notifications as done (removes from inbox/moves to Done tab).
Do NOT use PATCH /notifications/threads/{id} (marks as read but leaves in inbox).
After processing notifications, bulk-delete any remaining read-but-not-done notifications with the same DELETE API.

After completing a PR, merge it, sync the target branch, and delete the PR branch locally and remotely.