Grant actions: read so Claude can check CI status

[jonathangreen]

Description

Add actions: read to the review job's permissions block in the reusable Claude PR review workflow.

Motivation and Context

When the review runs, claude-code-action logs this warning and disables CI status visibility:

Warning: The github_ci MCP server requires 'actions: read' permission. Skipping CI server installation. To enable CI status checks, add 'actions: read' to your workflow permissions.

The github_ci MCP server lets Claude read the PR's workflow run / check status. Without actions: read it's skipped, so the review can't take CI results into account. Granting the read-only permission enables it.

How Has This Been Tested?

Not yet run in CI. This is a minimal, read-only permission addition; the next review run on a same-repo PR should no longer emit the warning and should have CI status available.

Checklist

• I have updated the documentation accordingly.
• All new and existing tests passed.

[claude]

Claude finished @jonathangreen's task in 2m 48s —— View job

---

Code Review

• Gather context (reusable workflow, README, self-caller)
• Verify actions: read enables the github_ci MCP server
• Check whether --allowedTools also needs the CI tools
• Assess permissions impact on consumers

Summary

The one-line addition of actions: read is correct, minimal, and follows least-privilege — it's exactly the read-only scope the github_ci MCP server requires to inspect workflow runs and check status. I also confirmed it's sufficient on its own: the action auto-allows its own MCP server tools, so the mcp__github_ci__* tools become usable without being added to the --allowedTools list. I verified this empirically — this review run uses the local claude-review.yml (via claude-review-self.yml) with this change applied, and the github_ci tools are available to me here despite not appearing in --allowedTools. There's also no new failure mode for consumers: if a caller's token scope doesn't include actions: read (e.g. an explicitly restricted caller), the server is simply skipped as it is today — nothing breaks. No actionable findings.