Standardized required CI check on the org-wide aggregator gate name

[aileen]

Why

Branch protection on this repo currently requires a status check named exactly All tests pass. Requiring a legacy/individual check name couples the ruleset to the CI job matrix: rename the job and the required check silently stops existing, blocking every PR.

The org is standardizing every repo on one stable aggregator check named Required checks pass (job id required-checks-pass), per the shared required-check convention. This gives branch protection a single stable target regardless of how CI jobs evolve.

What changes

• Renames the all-tests-pass gate job in .github/workflows/test.yml to required-checks-pass / Required checks pass.
• Job shape is unchanged: if: always(), needs: [test] (same coverage as before - test is the only other job in the workflow), single verify step failing on failure/cancelled results. Top-level permissions: contents: read was already present.

Coordination

The branch ruleset is being updated in the same pass to require Required checks pass instead of All tests pass, so this PR must go green on the new gate before merge.

[cursor]

Bugbot is not enabled for this team, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[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: 32 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 88f05f88-45e0-48d6-ace8-c5380e0f89dc

📥 Commits

Reviewing files that changed from the base of the PR and between 7fc1789 and 5da21b5.

📒 Files selected for processing (1)

• .github/workflows/test.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ci/required-checks-pass-gate

---

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