issues: archive #103 as refuted, verified against main first

[BigSimmo]

Summary

• Add opt-in, privacy-first server-side Sentry error tracking that is inert without SENTRY_DSN and scrubs request, user, body, breadcrumb, and clinical content before export.
• Surface conservative, normalized source-governance metadata in the RAG prompt so generation can see provenance state without inventing adverse unverified status for empty, index-only, or partial-sibling documents.metadata.
• Document the privacy envelope, operator approval checklist, and rollback path in docs/error-tracking.md.

RAG impact: no retrieval behaviour change — prompt presentation only adds conservative normalized source-governance metadata; retrieval, ranking, and source selection are unchanged.

Verification

• npm run verify:pr-local
• Focused Vitest for tests/error-tracking.test.ts, tests/rag-source-governance-prompt.test.ts, and tests/source-metadata.test.ts
• npm run eval:rag:offline — 36/36 golden retrieval cases
• npm run check:production-readiness:ci returned READY (offline; expected missing-env warnings)
• npm run build succeeded for production instrumentation wiring
• Merged origin/main and resolved Codex Cloud git-remote helper conflicts; git merge-tree vs origin/main is clean
• UI verification not run: no UI, routing, styling, or browser-behavior changes
• Live answer-generation quality evaluation not run — OpenAI/provider interaction requires explicit owner approval

Risk and rollout

• Risk: medium; optional Sentry path is disabled unless configured, but prompt wording changes answer-generation context and should land only with owner acceptance of offline evidence or an approved live answer-quality check.
• Rollback: revert the squash-merge commit on main, remove SENTRY_DSN and restart services if observability was enabled, and confirm prompts no longer emit the Source governance line.
• Provider or production effects: None unless an operator explicitly sets SENTRY_DSN; no browser DSN, tracing, or source-map upload is configured.

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
• Deployment classification/TGA SaMD impact was checked when clinical decision-support behavior changed

Notes

• Empty/{}/index-only governance metadata remains unrecorded in prompts; partial sibling fields use neutral unknown rather than inventing adverse unverified; explicit stored clinical_validation_status: "unverified" from upload is preserved.
• Optional Sentry init failures are swallowed so observability cannot block production boot.
• Merge remains gated on approved live answer-quality verification or an explicit owner decision to accept the offline-only evidence.

Summary by CodeRabbit

• Documentation
  • Archived open item #103 as resolved and refuted.
  • Clarified that terminal migrations remove the wide trigram index, while the schema retains the narrow expression-matching index.
  • Documented that schema tests cover both index behaviors.

[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]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 65bcbb1f-9ee1-4bcc-bcd8-fe12b5bf15eb

📥 Commits

Reviewing files that changed from the base of the PR and between 2b04df4 and 30bb055.

📒 Files selected for processing (1)

• docs/outstanding-issues.md

---

📝 Walkthrough

Walkthrough

The documentation archives issue #103 as refuted. It records the intended trigram-index state in the migration, schema.sql, and schema tests.

Changes

Schema issue archive

Layer / File(s)	Summary
Archive issue #103 docs/outstanding-issues.md	Moves issue #103 from open items to the resolved archive and records the confirmed index and schema-test state.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• BigSimmo/Database#836: Related Supabase trigram-index schema and test changes resolved by this archived issue.
• BigSimmo/Database#1377: Documents the wide trigram index and schema/migration reconciliation related to issue #103.

Suggested labels: skip-branch-sync

Suggested reviewers: claude, cursoragent

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is structurally complete but describes Sentry and RAG changes that are absent from this pull request.	Replace the description with the issue #103 archival change, verification against origin/main, ledger checks, and the related issue #149 note.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes archiving issue #103 as refuted after verification against main.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

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