docs(db): board — production window closed by auto-deploy, D4 pending, Phase 4 constraint (#316)

[BigSimmo]

Summary

• Updates the remediation status board after PR docs(forensics): §3.7 production window — five 20260818 migrations found already applied by the Supabase GitHub integration; db push not run #2123 (forensics §3.7): the authorised production window found all five 20260818* migrations already applied on production by the Supabase GitHub integration, so db push never ran; live-drift run 32131517648 shows zero function mismatches. Phase 3 and 6.1 are live on production.
• Records owner decision D4 (Supabase GitHub auto-deploy of merged migrations — recommend disabling "Deploy to production" until decided), the Phase 4 design constraint under auto-deploy (prebuild + fail-fast guard only, never a bare CREATE INDEX CONCURRENTLY migration), and the current inbox/reconcile state and CLI session traps.

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 → passed (see line pasted in the coordinator chat).

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

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

Limit details: You’ve used all 1 included review currently available under your plan. You completed 102 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: 5f7da580-87c1-4205-9110-cf22b056fbd3

📥 Commits

Reviewing files that changed from the base of the PR and between f55edd1 and 9c58475.

📒 Files selected for processing (2)

• docs/branch-review-records/323d37016e13d31cf7e0c23930490fae9d945ce0ebefbf3620ff7f0be07f39bd.record.md
• docs/database-remediation-coordination.md

---

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