Update actions-runner to 2.336.0 (hand-mirrored)

[bryan-minimal]

The 2026-08-10 stacked run dropped this member: per-arch gs://-mirrored sources are the one combination the updater cannot mirror (it early-returns before the scan-before-mirror gate — an upload added naively would publish unscanned bytes). Done by hand instead, with the gate's diligence:

• Both 2.336.0 artifacts fetched from the actions/runner GitHub release and verified byte-for-byte against the sha256 values upstream publishes in the release notes (x64 04cf0be1…, arm64 58b758e4…).
• pkgscan diff old→new run for each arch: every finding is the changed-ELF class (bin/*.so, dotnet runtime, bundled node) — definitional for a prebuilt bundle bump and the same shape as the already-published 2.332.0 mirror. No new signal class.
• Artifacts mirrored to gs://minimal-staging-archives/actions/runner/; sha256 literals updated in lockstep.

Updater support for scan-gated multi-arch mirroring remains the real fix (the refusal message documents the gap).

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 4 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 24d4d491-ebd1-473a-bb60-158e8df56b7f

📥 Commits

Reviewing files that changed from the base of the PR and between ff3ca2f and f052f3d.

📒 Files selected for processing (1)

• packages/actions-runner/build.ncl

---

_{Comment @coderabbitai help to get the list of available commands.}