Renamed CI gate job to the org-standard "Required checks pass"

[aileen]

Why

Branch protection on this repo currently requires the status check named exactly All tests pass. Requiring a repo-specific or legacy check name couples the ruleset to this workflow's job naming: rename the job (or restructure the matrix) and the required check silently stops existing, blocking every PR.

The org is standardizing every repository on a single stable aggregator check named Required checks pass — one job that needs every job that must pass and fails if any of them failed or was cancelled. That gives every ruleset one uniform, rename-proof target.

What

• Renamed the gate job all-tests-pass / All tests pass → required-checks-pass / Required checks pass
• Coverage unchanged: the gate still depends on the same test job the old gate covered
• The workflow already had top-level permissions: contents: read

Note on merging

The branch ruleset is being updated in the same pass to require the new check context, so this PR must go green on Required checks pass before merge. Do not merge until the ruleset swap is confirmed.

[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: 24 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: b3c48e6b-451c-4173-baba-d48616024a8d

📥 Commits

Reviewing files that changed from the base of the PR and between 19f40eb and 946218a.

📒 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.}