ci: pin deliberate coverage scope policy

[BigSimmo]

Summary

• document that workflow-only changes deliberately retain the Unit coverage gate because workflow edits can alter test setup and required-gate execution
• pin that behavior in the CI scope self-test while preserving static-only treatment for documentation-like repository skills
• archive outstanding issue fix: restore green typecheck and runtime on main (PR #131 type migration + PR #133 ssr:false) #139 now that dead outputs and coverage breadth both have explicit dispositions

Verification

• npm run check:ci-scope
• npm run check:gate-manifest
• npm run check:outstanding-issues -- --base-ref origin/main
• npm run check:branch-review-ledger
• Prettier check for the changed script
• git diff --check origin/main...HEAD

verify:pr-local was not repeated because the executable selection policy is unchanged; this change adds explicit assertions and documentation. Hosted CI should still exercise the selected Unit coverage path for the script change.

Risk and rollback

Low risk. Workflow-only changes continue to pay the intentional Unit coverage cost (roughly four minutes). Revert this PR to restore the prior undocumented policy.

RAG impact: no retrieval behaviour change — CI scope policy and documentation only.

[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:26 minutes

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

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: 11d99d9a-0721-49e4-9063-104b9bf20690

📥 Commits

Reviewing files that changed from the base of the PR and between c8e53d5 and f69828a.

📒 Files selected for processing (3)

• docs/branch-review-ledger.md
• docs/outstanding-issues.md
• scripts/ci-change-scope.mjs

---

_{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 ↗︎.