chore(drift): point stale comments and the RPC-missing hint at the v2 probe migration

[BigSimmo]

Summary

• Comment/hint follow-up to feat(db): migration-history probe, guard-migration contract, and index-monitoring ratchet (remediation Phase 6) #2058 (merged as 9c660af1f): scripts/generate-drift-manifest.ts pointed at tests/supabase-schema.test.ts for the manifest-freshness failure — it is tests/drift-detection.test.ts, and the header now also states that the replay's migration_history is always empty (no_history_table) and compared live-vs-allowlist. scripts/check-drift.ts header and the "RPC not available" hint now name the v2 probe migration 20260818090000 (falling back to the v1 name). docs/database-drift-detection.md "Duplicate migration-history versions" bullet no longer claims history is not compared at all — it says presence is not compared, and the no-statements fingerprint is compared live-vs-allowlist.
• No SQL, manifest, allowlist, or test change. The branch that carried feat(db): migration-history probe, guard-migration contract, and index-monitoring ratchet (remediation Phase 6) #2058 was accidentally re-created on the remote by a push after the squash-merge (claude/database-drift-allowlist-48839e, tip 3fe1deafe); it duplicates this change plus the merged commits and can be deleted — left in place because branch deletion needs your confirmation.

RAG impact: no retrieval behaviour change — comment and doc wording only.

Verification

• npx vitest run tests/drift-detection.test.ts tests/migration-history-guards.test.ts — Tests 25 passed (25).
• npm run docs:check-links — docs link check passed: 1838 repo path references resolve.
• npx prettier --write on the three files (unchanged after write).
• Verification not run: npm run verify:pr-local — comment/doc-only diff in two scripts and one doc; no executable path changed. npm run verify:ui not applicable.

Risk and rollout

• Risk: none functional — comments, a string in an error hint, and one doc bullet.
• Rollback: revert the commit.
• Provider or production effects: None.

Clinical Governance Preflight

Complete this section when the change touches ingestion, answer generation, search/ranking, source rendering, document access, privacy, production env, or clinical output.

• Source-backed claims still require linked source verification before clinical use
• No patient-identifiable document workflow was introduced or expanded without explicit governance approval
• Supabase target remains Clinical KB Database (sjrfecxgysukkwxsowpy)
• Service-role keys and private document access remain server-only
• Demo/synthetic content remains clearly separated from real clinical sources
• Source metadata, review status, and outdated/unknown-source behavior remain conservative
• Deployment classification/TGA SaMD impact was checked when clinical decision-support behavior changed

Notes

• Follow-up to feat(db): migration-history probe, guard-migration contract, and index-monitoring ratchet (remediation Phase 6) #2058; the 6.1 migration remains NOT deployed (owner-approved production window after Phase 4).

🤖 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:43 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: 3741d7d2-c56d-4202-8a3a-4d4ed41ead26

📥 Commits

Reviewing files that changed from the base of the PR and between 88fe4b9 and cd7fe48.

📒 Files selected for processing (4)

• docs/branch-review-records/e4f69008ad6f53bc51fceeff12fe8d1116722ca31f4c53c56bc0b1a611cf5e53.record.md
• docs/database-drift-detection.md
• scripts/check-drift.ts
• scripts/generate-drift-manifest.ts

---

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