ci: detect deleted outstanding issue rows

[BigSimmo]

Summary

• compare outstanding issue IDs with the PR/push base so a row cannot silently disappear from both open and archive tables
• make the required static checkout fetch base history and fail closed when an explicitly supplied base cannot be read
• archive chore: remove accidentally committed scratch/ debugging files #148 after proving deletion, archive-move, new-ID, and unreadable-base behavior

Verification

• npm run verify:cheap — 442 files passed; 4,626 tests passed, 3 skipped
• npm run verify:pr-local — runtime/parity, format, lint, typecheck, 442 files / 4,626 tests, and 36-case RAG fixture manifest passed; build correctly skipped
• npm run check:outstanding-issues -- --base-ref origin/main
• unreadable explicit-base proof exits 1 with the decisive deletion-protection error
• npm run check:github-actions
• npm run check:ci-scope
• npm run check:gate-manifest
• npm run test -- tests/repo-hygiene.test.ts — 48 passed
• UI verification not run: no UI, routing, styling, or browser behavior changed.

Risk and rollback

• Risk: low-to-moderate CI risk; an incorrect base selection could block a legitimate ledger edit. CI pins the trusted event base SHA, fetches full history, accepts IDs retained in either table, and fails closed only when that explicit base is unreadable.
• Rollback: revert this PR to restore structural-only checking and the prior shallow static checkout.
• Provider or production effects: GitHub CI checkout depth and local/static validation only; no OpenAI, Supabase, Railway, or production-data interaction.

RAG impact: no retrieval behaviour change — CI and documentation ledger integrity only.

[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 ↗︎.

[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:44 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: af65dbbf-4941-45c4-a7df-8bdffa82d3a7

📥 Commits

Reviewing files that changed from the base of the PR and between c338f98 and 0bfd548.

📒 Files selected for processing (4)

• .github/workflows/ci.yml
• docs/branch-review-ledger.md
• docs/outstanding-issues.md
• scripts/check-outstanding-issues.mjs

---

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