docs: record document trigger rollout

[BigSimmo]

Summary

• Move outstanding issue Create codeql.yml #26 to the resolved archive now that PR db: add fail-safe document-change ingestion trigger #1100, hosted migration replay, production catalog proof, and live drift validation are complete.
• Keep operator activation separately open under Fix Next.js binding to allow Railway healthchecks #25 because the Vault secret and base-URL GUC are intentionally absent.

RAG impact: no retrieval behaviour change — documentation-only rollout evidence.

Verification

• npm run verify:pr-local — not repeated for this one-line docs-only move; the dry-run selected the full unit suite despite no executable change, and the identical code passed this gate in PR db: add fail-safe document-change ingestion trigger #1100.
• npm exec prettier -- --check docs/outstanding-issues.md — passed.
• git diff --check — passed.
• npm run check:drift — passed against Clinical KB Database; no unexpected live schema drift.
• npm run verify:cheap was attempted after the docs edit but the shell timeout closed stdout at 122 seconds, producing EPIPE; no assertion failure was reported. It was not repeated because PR db: add fail-safe document-change ingestion trigger #1100 already passed the identical executable tree locally and in hosted CI.
• npm run verify:ui — not run; no UI change.
• npm run verify:release — not run; no release behavior change.

Risk and rollout

• Risk: documentation-only. The production trigger remains inert until the operator inputs tracked in Fix Next.js binding to allow Railway healthchecks #25 are configured.
• Rollback: revert this ledger move if the live proof is later invalidated.
• Provider or production effects: read-only Supabase catalog and drift checks only; this PR performs no provider mutation.

Clinical Governance Preflight

• 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
• No clinical decision-support behavior changed

---

Note

Low Risk
Documentation-only ledger update with no runtime, schema, or RAG behavior changes.

Overview
Updates docs/outstanding-issues.md only: #26 (wire the Supabase document-change trigger) is removed from the open table and recorded under Resolved / archive with rollout evidence from PR #1100 (migrations, production catalog proof, check:drift).

The archived outcome states the trigger is deployed but still inert until operator secrets/base URL from #25 are configured—no change to open #25 or any application/RAG code.

^{Reviewed by Cursor Bugbot for commit 820a9fb. Configure here.}

[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

@BigSimmo, you've reached your PR review limit, so we couldn't start this review.

Next review available in:46 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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 Plus

Run ID: c3090765-19dd-4bb1-a449-6c7d62f04e99

📥 Commits

Reviewing files that changed from the base of the PR and between 6a56a89 and 93696b8.

📒 Files selected for processing (1)

• docs/outstanding-issues.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/document-change-trigger-rollout-evidence

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:820a9fb94d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".