Claude: address #2

README.md

@@ -78,7 +78,11 @@ See `.env.example`.
 6. In Gitea: Site Administration -> Integrations -> Webhooks -> **System
    Webhooks** -> Add, URL `http://claude-hook:3000/`, trigger on **Issue
    Comment** (and **Issues**, if you want `@claude` in a fresh issue body
-   to work too). If you set `WEBHOOK_SECRET`, put the same value here.
+   to work too). To also support pull requests, enable **Pull Request**
+   (for `@claude` in a fresh PR description), **Pull Request Comment**
+   (general PR comments — routed the same as issue comments), **Pull
+   Request Review**, and **Pull Request Review Comment** (inline diff
+   comments). If you set `WEBHOOK_SECRET`, put the same value here.
 7. Add `GITEA__webhook__ALLOWED_HOST_LIST=private` to Gitea's own
    environment and restart it — Gitea refuses to call private addresses
    otherwise.
@@ -97,9 +101,6 @@ or pipeable into `jq`. Key events to look for:
 
 ## Known limitations
 
-- Only `issue_comment` and `issues` events are handled; PR *review* comments
-  (`pull_request_review_comment`) are a separate event type and are not
-  wired up.
 - Runs execute inside this one long-lived container, not a fresh sandbox
   per job — don't point `OWNER_LOGIN` checks loosely, and don't run this
   against repos where you don't trust every collaborator who can comment.