Remote-agent / routine GitHub PR subscriptions don't deliver pull_request_review or pull_request_review_comment events

Summary

A Claude Code remote agent subscribed to a PR is woken only by issue_comment events (delivered to the agent as <untrusted_external_data source="pr_comment">). Formal reviews submitted via POST /repos/{o}/{r}/pulls/{n}/reviews (CHANGES_REQUESTED / COMMENTED / APPROVE) and inline review-comment threads (pull_request_review_comment) never wake the agent. As a result the agent can declare "no action needed" — or merge — while an unaddressed review sits on the PR.

This matches the documented routine GitHub triggers, which subscribe to pull_request.* and release.* only (https://code.claude.com/docs/en/routines#supported-events); pull_request_review and pull_request_review_comment are not among them.

Evidence (real PR)

On a PR where a code-review bot (claude[bot], state COMMENTED) and several status bots commented, the review was chronologically first, yet was the only item the agent never received:

| Time (UTC) | Surface | Event type | Agent woken? |
|---|---|---|---|
| 23:45:52 | pulls/{n}/reviews | pull_request_review (COMMENTED, substantive suggestions) | ❌ never |
| 23:48:55 | issues/{n}/comments | issue_comment (Firebase preview URL) | ✅ |
| 23:52:27 | issues/{n}/comments | issue_comment (CI status) | ✅ |
| 00:04:14 | issues/{n}/comments | issue_comment (screenshots) | ✅ |

The agent woke for the three issue_comments but not for the earlier review, confirming the review event was never delivered (not transcript truncation — the review predated everything it did see).

Expected behaviour

A submitted PR review, and its inline review comments, should wake the subscribed agent the same way a PR comment does.

Actual behaviour

Only issue_comment events are delivered. pull_request_review and pull_request_review_comment events are dropped, so the agent is never notified of reviews.

Impact

Silent loss of the single most important PR-feedback surface. An agent that opened a PR can merge it, or stop work, while a CHANGES_REQUESTED / COMMENTED review is unread. This is especially self-defeating when the reviewer is itself a Claude code-review bot — the writing agent and the reviewing agent never connect.

Suggested fix

Subscribe the Claude GitHub App to pull_request_review and pull_request_review_comment events and forward them to routine / remote-agent delivery, tagged distinctly from PR comments (e.g. source="pr_review" vs the current source="pr_comment") so the agent can tell a formal review from a plain comment.

Related

• #31687 — /pr-comments skill missing review comments from pull request reviews (related surface gap, different mechanism).