ci(was): ref-scoped concurrency retrofit

[yakimoto]

Adds a ref-scoped concurrency: block to per-commit/scheduled workflows lacking one (WAS Phase 3 retrofit).

Group ${{ github.workflow }}-${{ github.ref }} is merge-queue-safe (queue runs on a different ref, so no #852 self-eviction). Reusables + release workflows exempt.

Files:

• foundation-gate.yml

---

Note

Low Risk
CI-only workflow metadata change; no application code, secrets, or runtime behavior.

Overview
WAS Phase 3 retrofit: foundation-gate now uses ref-scoped concurrency so only one run per workflow + ref is active at a time, with cancel-in-progress: true to drop superseded runs when new commits land on the same ref.

The group is ${{ github.workflow }}-${{ github.ref }}, matching the merge-queue-safe pattern used elsewhere (e.g. public-repo-guard); queue runs on a different ref so they do not cancel each other.

^{Reviewed by Cursor Bugbot for commit 3c8bb65. Configure here.}

---

Summary by cubic

Adds a ref-scoped concurrency block to the foundation-gate workflow to limit CI to one run per ref and avoid merge-queue self-eviction. Uses group: ${{ github.workflow }}-${{ github.ref }} with cancel-in-progress: true.

^{Written for commit 3c8bb65. Summary will update on new commits.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_32094b10-66a7-4977-ba54-486ff4d80957)

[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: 46 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: ASSERTIVE

Plan: Pro Plus

Run ID: e6e6487b-c679-434a-9cb5-1b6c64d8d274

📥 Commits

Reviewing files that changed from the base of the PR and between f974ad7 and 3c8bb65.

📒 Files selected for processing (1)

• .github/workflows/foundation-gate.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ci/was-concurrency-retrofit

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch ci/was-concurrency-retrofit

---

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3c8bb65

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[cursor]

Risk: low. Not approving: Cursor Bugbot skipped (usage limit reached) and did not complete automated review. Human review is needed before merge; no suitable non-author reviewers were assigned.

  

_{Sent by Cursor Approval Agent: Pull Request Router and Approver}