docs(db): board — Phases 2 and 3 complete, production window owed, Phase 4 next (#316) - #2116
Conversation
…ase 4 next (#316) Verified against main 511d22f: PR #2104 (Phase 2 re-measure, still 19), PR #2106 (Phase 3 codification: 20260818110000/111000/112000), open PR #2111 (staging proof + 20260818113000). Records the decided D1/D2/D3, the single production window (db push, five migrations, no canary), the check:drift --prune-stale staging trap, and the reconcile timing after #2111. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This pull request has been ignored for the connected project Preview Branches by Supabase. |
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in:32 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 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 configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
Comment |
Uh oh!
There was an error while loading. Please reload this page.
Summary
main511d22f4d: Phase 2 complete and re-measured (PR docs(db): re-measure staging drift at current main after the snapshot v2 migration (#056) #2104, still 19 findings against currentmain), Phase 3 complete repo-side (PR feat(db): codify live SET work_mem on the ten match_* RPCs, the eight schema-only objects, and three chain-stale columns (#316) #2106) with staging proof and20260818113000in open PR feat(db): Phase 3 staging proof + forward-codify three hybrid RPC bodies the chain never received (#316) #2111, Phase 6.1 deployed to staging but not production.supabase db pushof five migrations, no canary, no index build), thecheck:drift --prune-stalestaging trap, and the reconcile timing (one serializedissues:reconcileafter feat(db): Phase 3 staging proof + forward-codify three hybrid RPC bodies the chain never received (#316) #2111 merges).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: 1923 repo path references resolve.🤖 Generated with Claude Code