docs(db): board refresh — Phase 2 and reconcile #2098 landed; staging traps and #183 rider (#316)

[BigSimmo]

Summary

• Refreshes the remediation status board after PR Replay the migration chain onto staging to parity, and record that the chain does not reproduce schema.sql (Phase 2, #056) #2093 (Phase 2), docs(issues): reconcile 16 queued ledger requests after PR #2093 #2098 (ledger reconcile) and chore(drift): point stale comments and the RPC-missing hint at the v2 probe migration #2090 merged: Phase 2 marked complete with the re-measure still owed, the four Phase 2 §2.3/§2.4 findings recorded on the board (8 never-created objects, 3 column-set + 1 index-def mismatches, duplicate migration version pairs, staging worker GUC pointing at production — never seed the three vault secrets into staging), and the #183 rider (Supabase CLI now authenticated, queue the ledger update on the next product PR).

Docs-only. No code, schema, migration, RAG surface, or provider call.

Verification

• npx prettier --check docs/database-remediation-coordination.md → All matched files use Prettier code style!
• npm run docs:check-links → docs link check passed: 1881 repo path references resolve.

🤖 Generated with Claude Code

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

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

Limit details: You’ve used all 1 included review currently available under your plan. You completed 101 included PR reviews in the past 7 days; at that activity level, included reviews refill at 1 review per hour.

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: 0ac50cad-55a1-4fcd-a8e9-6d7aac3ae936

📥 Commits

Reviewing files that changed from the base of the PR and between 2c311c7 and 9652db1.

📒 Files selected for processing (2)

• docs/branch-review-records/26601359b89b2dd146e61f664ae30c068ebd46d97eb56a209e5e8f56adc175eb.record.md
• docs/database-remediation-coordination.md

---

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