docs(issues): queue #316 window close-out + D4, re-scope #Q5JHBJ (#316)

[BigSimmo]

Summary

• Queues one #316 update: the Phase 3/6.1 production window closed on 2026-08-18 without a push (all five 20260818* migrations were already applied by the Supabase GitHub integration; live-drift 32131517648 = 0 function mismatches), the RPC-divergence half of the row is closed, D4 (auto-deploy) is recorded as the pending owner decision with the recommendation to disable "Deploy to production" until decided, and the remaining Phase 4/5 scope plus the auto-deploy constraint and CLI session traps are stated.
• Queues one #Q5JHBJ update: the 20260818090000 probe is already live on production, so that row re-scopes to triaging the 15 reported no-statements versions and authoring fail-fast guard migrations.

Inbox requests only; no canonical ledger edit, no code, no schema, no provider call. Reconcile in the next serialized issues:reconcile.

Verification

• npm run check:outstanding-issues → Outstanding-issues guard passed: 378 rows (44 open, 334 archived) …
• npm run check:ledger-write-discipline → passed (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.

[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:11 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: 910a6465-2d32-4aba-8175-fbe928249e8d

📥 Commits

Reviewing files that changed from the base of the PR and between 0216f18 and dfdb7ca.

📒 Files selected for processing (3)

• docs/branch-review-records/3bf415052283c7c9ccd1792f7d354ba9a0d6efd4d5b0716281e86fcb133abbf1.record.md
• docs/outstanding-issues-inbox/7a93a5a2-d3b9-4f3d-9747-22049300cd64.json
• docs/outstanding-issues-inbox/d96c4613-bdfc-4e80-b084-7c27dfff1bb8.json

---

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