docs(db): land and re-baseline the remediation coordination board (#316)

[BigSimmo]

Summary

• Carries docs/database-remediation-coordination.md (the coordinator handover written on claude/fable-tasks-issues-49hnvp at dc8969676, never merged) onto main.
• Re-baselines its status board against the repository record as of mainf5b093291: Phase 0 complete (ci(drift): route live-drift failures to a pinned issue and trigger on migrations #1938/ci(live-drift): route failures to a pinned issue and run after migration pushes (#316 phase 0) #1939/test(live-drift): prove the drift routing, and close out Phase 0 #1951/fix(ledger,guard): survive parallel reconciles and rewritten history #1978/docs(db): record the execution traps and parallel-session coordination rules #2027), Phase 1 partial with 1.2 the only executable next step, Phase 3 blocked on ten UNCLASSIFIED RPCs (per PR docs(issues): correct #316's next step — Phase 3 has no executable entries (#316) #2017), Phase 4/5 incident-scope partial evidence (docs(audit): 2026-08-14 incident forensics and live index restore evidence (#316, #231) #1960).
• Corrects two stale statements: the tracking anchor is #316, not #312; the originating "DDL never executed" verdict is marked superseded by the Phase 1.1 fingerprint (stmt_count 14).

Docs-only. No code, schema, migration, or RAG surface touched; no provider call made beyond a names-only gh secret list read.

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: 1799 repo path references resolve.

Ledger

#316 is the tracking anchor; no inbox request in this PR (the board doc is the coordinator's artifact; #316 prose is already corrected by PR #2017 pending reconcile PR #2032).

🤖 Generated with Claude Code

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

Limit details: You’ve used all 1 included review currently available under your plan. You completed 95 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: 9273ff53-ab07-4b38-81bf-dfbff8396a38

📥 Commits

Reviewing files that changed from the base of the PR and between b8e774b and 5a8036e.

📒 Files selected for processing (2)

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

---

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

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

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
36221231	Triggered	Generic High Entropy Secret	f84f0e4	tests/rag-adversarial-fixtures.test.ts	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}