feat(pr-watch): integrate reviews/comments into pr-watch

The pr-watch skill and script now cover reviews/comments, not just CI checks.
An agent reading only the pr-watch skill now knows to track both.

.agents/skills/pr-watch/SKILL.md:
- Reframed: 'watching a PR' means checks AND reviews
- Added 'Reviews and Comments' section with the three surfaces table
- Added 'Review Obligations' subsection (answer feedback, identity line, etc.)
- Documented --reviews (default) and --no-reviews flags
- Cross-references AGENTS.md for full workflow details

scripts/pr-watch:
- Added --reviews (default) and --no-reviews flags
- After exit 0 (green/mergeable), calls scripts/pr-reviews to show all
  reviews and comments. Does not change exit code — answering is agent's job.
- Updated usage text to document the new behavior
- Composes with existing pr-reviews (fixture mode passes through)

scripts/pr-watch-test.sh:
- Added mk_reviews_empty() and mk_reviews_with_review() helpers
- Added review fixtures to all cases that exit 0 (pr-reviews needs them)
- Added tests: 'green with reviews shows review output' and
  '--no-reviews skips review output'
- All 56 tests pass

AGENTS.md / context/cloud-agents.md:
- Updated cross-references to point to pr-watch skill as agent-facing recipe
- Simplified text now that pr-watch handles reviews automatically

Co-authored-by: Ed Langley <fiddlerwoaroof@users.noreply.github.com>

.agents/skills/pr-watch/SKILL.md

@@ -5,8 +5,14 @@ description: Wait for a GitHub PR's checks to finish before merging or reporting
 
 # Waiting on a PR
 
+"Watching a PR" means tracking **both** CI checks **and** GitHub comments/reviews.
+A PR is not ready to merge just because checks are green — review feedback must be
+read and answered first.
+
+## CI Checks
+
 ```
-scripts/pr-watch <pr-number> [--expect <sha>] [--timeout <sec>] [--interval <sec>]
+scripts/pr-watch <pr-number> [--expect <sha>] [--timeout <sec>] [--interval <sec>] [--reviews]
 ```
 
 ```
@@ -23,19 +29,54 @@ exit 5  the PR is MERGED or CLOSED, at the head the watch pinned; it ends on
         the first poll that sees it closed, which may be mid-wait
 ```
 
+**`--reviews`** (default): after checks complete, print all reviews and comments
+via `scripts/pr-reviews`. Use `--no-reviews` to skip this. The reviews are shown
+but do not change the exit code — answering them is your responsibility.
+
 **Exit 0 now means mergeable, not only green.** GitHub computes mergeability
 lazily and reports `UNKNOWN` for a while after the base moves. It also reports
 `BLOCKED` for the moment before a required check that `needs:` another job has
 registered. The watch waits out both, so you do not need to re-check
 `mergeable` by hand after it. **Exit 3 is not a pass.** It may be a required
-check that never ran. Why each
-state counts the way it does: `context/code/tooling.md`, "pr-watch and
-mergeability" (improvise-edpl).
+check that never ran. Why each state counts the way it does:
+`context/code/tooling.md`, "pr-watch and mergeability" (improvise-edpl).
 
 **Pass `--expect <sha>` whenever you know which commit you are asking about.**
 It is the difference between "this PR is green" and "the thing I pushed is
 green", and a PR here was once merged at a head that predated its own fix.
 
+## Reviews and Comments
+
+Reviews are a **separate API surface** from the comment thread. Codex/ChatGPT
+reviews arrive as *reviews*, not comments — checking only the comment thread
+misses them entirely. `pr-watch --reviews` (the default) shows all three:
+
+| Surface | What it is |
+|---|---|
+| `[REVIEW]` | The review's own body (pulls/{n}/reviews) |
+| `[INLINE]` | A comment on a line of the diff (pulls/{n}/comments) |
+| `[COMMENT]` | A comment on the PR thread (issues/{n}/comments) |
+
+To fetch reviews directly: `./scripts/pr-reviews <n>` — **do not pipe it**. The
+script's `$?` must be read directly; piping or chaining loses the exit code.
+Redirect to a file if you need to process it.
+
+### Review Obligations
+
+Before treating a PR as done or merging:
+
+1. **Read all review feedback** — reviews against an earlier head may still apply
+2. **Answer substantive feedback** on the PR with an identity line naming the
+   model (the repo owner's account is shared)
+3. **Re-check after each push** that new reviews target the current head SHA
+4. **Don't wait indefinitely on Copilot/Codex** — reviews arrive as quota allows;
+   an absent review and an unrequested one look identical. The adversarial review
+   that gates a merge is dispatched by the orchestrator; external reviews are
+   read *in addition*, not instead.
+
+See AGENTS.md "Shipping a wave" and "Read the PR's reviews before merging" for
+the full workflow, Copilot request mechanics, and how to answer declined findings.
+
 ## Do not write the loop yourself
 
 Four signals look like "finished" and are not: