docs(issues): archive #028 after production Sentry enablement

[BigSimmo]

Summary

• Archived outstanding issue #028 after enabling privacy-safe production Sentry server error tracking and DB tracing on Railway.
• Production Database service now has SENTRY_DSN, SENTRY_ENVIRONMENT=production, and SENTRY_TRACES_SAMPLE_RATE=0.1 (verified with live span.op:db spans).
• Staging app service configured with the same DSN at SENTRY_ENVIRONMENT=staging.
• Intentionally left unset: NEXT_PUBLIC_SENTRY_DSN, sourcemap upload tokens (SENTRY_ORG / SENTRY_PROJECT / SENTRY_AUTH_TOKEN), and worker Sentry vars (worker has no Sentry instrumentation).

Clinical Governance Preflight

• No clinical risk paths changed (docs-only ledger archive).
• No RAG ranking / retrieval behaviour change.
• No privacy-envelope expansion beyond already-approved server-side scrubbed Sentry events.

Test plan

• Railway variable presence checks for production Database and staging app
• Production deploy healthy; staging deploy healthy
• Sentry Explore shows environment:production span.op:db
• Confirmed browser DSN / source-map tokens absent

RAG impact: no retrieval behaviour change — docs/outstanding-issues archive only.

[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

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:54 minutes

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: 6d80fe59-ab89-4f23-b3db-064204b09775

📥 Commits

Reviewing files that changed from the base of the PR and between 1452288 and 0f940f4.

📒 Files selected for processing (1)

• docs/outstanding-issues.md

---

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

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

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