fix(ci): keep dispatched and scheduled CI runs alive through main churn

[BigSimmo]

Summary

• One-line change to the workflow-level concurrency group in .github/workflows/ci.yml: workflow_dispatch and schedule events now use a per-run group (github.run_id) instead of the shared CI-<ref> group, so pushes to the same ref can no longer cancel deliberate one-off runs mid-flight. Push and pull_request runs keep the shared ref group with cancel-in-progress: true, so superseded PR heads still stop early exactly as today.
• Why: the 70-minute release-browser-matrix (WebKit/Firefox full UI matrix — the only real coverage for those engines) was cancelled twice on 2026-07-19/20 by main merges landing minutes into the run, and the weekly Sunday 18:00 UTC scheduled run sits in the same cancel-in-progress group, so it is subject to the identical livelock. On a repo where main merges every few minutes, the matrix could effectively never complete.
• Also appends the review-ledger row for this change (docs/branch-review-ledger.md).

Verification

• npm run check:github-actions — pin check passed (no new uses:, no ubuntu-latest; the checker does not constrain the concurrency block)
• npm run check:ci-scope — self-test passed (classifier change scope unaffected; this PR classifies as workflow_changed)
• npm run format:check — repo files clean

Verification not run: npm run verify:pr-local full gate — the diff is a workflow-file expression change plus a ledger row; the three checks above are the complete static surface for it (no source, test, or build behavior changes). UI verification not run: no UI change.

Risk and rollout

• Risk: low. GitHub expression (github.event_name == 'workflow_dispatch' || github.event_name == 'schedule') && github.run_id || github.ref follows the standard and/or ternary idiom; github.run_id is always non-empty so the fallback can never misfire. Accepted side effect: a deliberate dispatch/scheduled run can now execute concurrently with push-triggered runs on the same ref (rare — dispatches are manual, the schedule is weekly; bounded runner cost). release-browser-matrix is not a required branch-protection check, so no merge-gating semantics change.
• Rollback: plain revert of the one-line commit restores the previous shared-group behavior.
• Provider or production effects: None.

Clinical Governance Preflight

Not applicable — CI concurrency grouping only; no ingestion, answer generation, search/ranking, source rendering, document access, privacy, production env, or clinical output surface is touched.

Notes

• If this merges before Sunday 18:00 UTC, tonight's scheduled run should finally complete the WebKit/Firefox matrix on main (previous attempts were cancelled by churn, not failing).

🤖 Generated with Claude Code

https://claude.ai/code/session_01EXsJcLrbZUXwnBeG91cVo9

---

Generated by Claude Code

[coderabbitai]

Warning

Review limit reached

@BigSimmo, you've reached your PR review limit, so we couldn't start this review.

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 Plus

Run ID: 6619f1a7-c31a-41ed-82ab-c68ef334e941

📥 Commits

Reviewing files that changed from the base of the PR and between 5b46e80 and ac0182a.

📒 Files selected for processing (2)

• .github/workflows/ci.yml
• docs/branch-review-ledger.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/clinical-kb-pwa-review-asi3wb

---

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

[supabase]

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.