Remove Sentry error capture integration

[BigSimmo]

Summary

• Fully removes the optional server-side Sentry error-capture integration, which is no longer used.
• Deletes src/lib/observability/error-capture.ts (the @sentry/node wrapper) and its test.
• Drops the Sentry.init(...) block and the onRequestError hook from src/instrumentation.ts; the production boot guards (requireServerEnv / requireOpenAIEnv / requireQueryHashSecret, demo-mode and no-auth refusals) are unchanged.
• Removes the captureServerException / captureServerEvent call sites in src/app/api/answer/route.ts, src/app/api/answer/stream/route.ts, and src/lib/rag.ts, along with the now-dead clientAborted / signal guards that existed only to gate those calls.
• Removes the SENTRY_DSN entry from the env schema (src/lib/env.ts) and the corresponding block in .env.example.
• Removes the @sentry/node dependency from package.json and regenerates package-lock.json (453 lines of @sentry/* tree removed).
• Strips the Sentry-specific cases from tests/instrumentation.test.ts, keeping full production boot-guard coverage.

Behavior is preserved: the capture calls were fire-and-forget and fully inert without a SENTRY_DSN, so removing them changes no runtime behavior. logStreamError still logs via logger.error; only the Sentry-reporting branch was removed.

Verification

• npm run verify:pr-local — not run in full; ran the individual offline gates below instead.
• npm run typecheck — no errors in any touched file (the 20 reported errors are pre-existing missing-dep issues in untouched DOM/UI test files).
• npm run lint — clean at --max-warnings 0.
• Targeted vitest run: tests/instrumentation.test.ts (8/8), answer-slo + answer-telemetry + clinical-search (50/50), and all 25 rag-* suites (291/291, including rag-answer-fallback which exercises the generation-fallback path where a capture call was removed).
• Grep sweep confirms no remaining sentry / error-capture / captureServer* references in code, config, or docs.

Not run (out of scope for this change): verify:ui (no UI/routing/styling change), eval:retrieval:quality and eval:rag (no retrieval, ranking, selection, scoring, synthesis-prompt, or answer-contract change — only an observability call was removed from the fallback branch), and check:production-readiness (it is a static env validator that never referenced SENTRY_DSN, so this change is transparent to it; in this demo-mode container it would only emit expected missing-secret noise).

Clinical Governance Preflight

This change touches the answer-generation route files, but only to remove observability call sites; no clinical, retrieval, ranking, source-rendering, document-access, or privacy behavior changes.

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

Notes

• Removing SENTRY_DSN means any deployment that set it will now ignore that variable; no other config changes are required.
• This leaves the server with no external error-reporting sink. If a replacement provider is wanted later, the seam was the two captureServer* helpers — those call sites are now gone and would need to be re-introduced.

🤖 Generated with Claude Code

---

Generated by Claude Code

Summary by CodeRabbit

• Bug Fixes

  • Simplified answer API error handling to return consistent, client-friendly responses.
  • Stream error handling now only logs locally, avoiding conditional server-side capture.

• Chores

  • Removed server-side error reporting/capture and related client instrumentation wiring.
  • Updated monitoring to rely only on the public Sentry DSN configuration.

• Documentation

  • Removed the /api/monitoring entry from the sitemap.
  • Updated .env.example to drop the server-side Sentry DSN placeholder.

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

[github-actions]

CI triage

CI failed on this PR. Automated classification of the 9 failed job(s):

• Unit coverage — needs investigation.
• Critical UI smoke — possible known flake: UI/Playwright job; check tests/flake-ledger.json (tests/ui-smoke.spec.ts, tests/ui-smoke.spec.ts, tests/ui-tools.spec.ts, tests/ui-tools.spec.ts) and re-run before bisecting.
• Advisory quarantined UI tests — possible known flake: UI/Playwright job; check tests/flake-ledger.json (tests/ui-smoke.spec.ts, tests/ui-smoke.spec.ts, tests/ui-tools.spec.ts, tests/ui-tools.spec.ts) and re-run before bisecting.
• Build — possible known flake: UI/Playwright job; check tests/flake-ledger.json (tests/ui-smoke.spec.ts, tests/ui-smoke.spec.ts, tests/ui-tools.spec.ts, tests/ui-tools.spec.ts) and re-run before bisecting.
• UI regression — possible known flake: UI/Playwright job; check tests/flake-ledger.json (tests/ui-smoke.spec.ts, tests/ui-smoke.spec.ts, tests/ui-tools.spec.ts, tests/ui-tools.spec.ts) and re-run before bisecting.
• Static PR checks — needs investigation.
• Advisory mockup UI — possible known flake: UI/Playwright job; check tests/flake-ledger.json (tests/ui-smoke.spec.ts, tests/ui-smoke.spec.ts, tests/ui-tools.spec.ts, tests/ui-tools.spec.ts) and re-run before bisecting.
• Safety and config checks — needs investigation.
• PR required — possible known flake: UI/Playwright job; check tests/flake-ledger.json (tests/ui-smoke.spec.ts, tests/ui-smoke.spec.ts, tests/ui-tools.spec.ts, tests/ui-tools.spec.ts) and re-run before bisecting.

Heuristic only — a main-side or flake label is a starting point, not a verdict.

[coderabbitai]

📝 Walkthrough

Walkthrough

The change removes Sentry server and client integrations, including dependencies, environment fields, initialization, error capture, fallback telemetry, and client boundary reporting. Answer routes retain structured error responses and logging. Monitoring tests use only the public DSN.

Changes

Sentry observability removal

Layer / File(s)	Summary
Runtime observability configuration package.json, src/lib/env.ts, src/instrumentation.ts, src/instrumentation-client.ts, tests/instrumentation.test.ts, .env.example, next.config.ts	Removes Sentry dependency, environment parsing, initialization, client instrumentation, build-time flag wiring, and related tests and configuration guidance.
API error handling src/app/api/answer/route.ts, src/app/api/answer/stream/route.ts	Removes server-exception capture and abort-related reporting while preserving structured error responses and stream logging.
Client error reporting src/app/global-error.tsx, src/components/route-error-boundary.tsx, src/lib/observability/*	Removes client exception capture, Sentry client registration, and privacy scrubbing helpers while retaining error logging and recovery UI.
Monitoring and fallback telemetry src/lib/rag.ts, tests/sentry-client.test.ts, docs/site-map.md	Removes fallback event reporting, updates monitoring tests to use only NEXT_PUBLIC_SENTRY_DSN, and removes the monitoring route from the sitemap.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Possibly related PRs

• BigSimmo/Database#600: Directly overlaps with removal of server-side Sentry capture and answer-route handling.
• BigSimmo/Database#642: Directly overlaps with removal of client Sentry integration and monitoring support.

Suggested reviewers: claude

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 18.18% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely matches the main change: removing Sentry error capture integration.
Description check	✅ Passed	The description follows the template with Summary, Verification, Clinical Governance Preflight, and Notes, and gives relevant implementation details.
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.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/optimistic-euler-jsite9

---

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

[BigSimmo]

@copilot resolve the merge conflicts on this branch.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@src/app/api/answer/stream/route.ts`:
- Around line 95-97: Update logStreamError to restore the prior filtering:
ignore client-abort errors and caught responses with non-500 payload statuses,
while continuing to log only qualifying stream failures through logger.error.
Keep the Sentry capture removed and preserve the existing safeErrorLogDetails
handling for errors that pass the filters.

🪄 Autofix (Beta)

❌ Autofix failed (check again to retry)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 7285f1a2-1334-42bc-8fe2-7ca37fc4f8c5

📥 Commits

Reviewing files that changed from the base of the PR and between 71d9f2c and d3319a4.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (13)

• .env.example
• package.json
• src/app/api/answer/route.ts
• src/app/api/answer/stream/route.ts
• src/app/api/monitoring/route.ts
• src/instrumentation-client.ts
• src/instrumentation.ts
• src/lib/env.ts
• src/lib/observability/error-capture.ts
• src/lib/rag.ts
• tests/error-capture.test.ts
• tests/instrumentation.test.ts
• tests/sentry-client.test.ts

💤 Files with no reviewable changes (6)

• src/lib/observability/error-capture.ts
• tests/error-capture.test.ts
• src/lib/rag.ts
• package.json
• src/app/api/answer/route.ts
• .env.example

[coderabbitai]

Note

Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it.

⚠️ Branch updated during autofix.

The branch was updated while autofix was in progress. Please try again.

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)

src/app/api/answer/stream/route.ts (2)

306-308: 🩺 Stability & Availability | 🟠 Major | ⚡ Quick win

Preserve the original exception when replacing Sentry capture.

This branch wraps the error with a new PublicApiError containing only error.name, then passes that wrapper to jsonError. The original message and stack are therefore unavailable to the supplied logging path, leaving production logs without the root cause after Sentry removal. Preserve the original error as a cause or log its sanitized details before wrapping it for the public response.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/app/api/answer/stream/route.ts` around lines 306 - 308, Update the Error
branch in the answer-processing handler to preserve the original exception’s
message and stack for internal logging while still returning the sanitized
PublicApiError response. Pass the original error as the wrapper’s cause or
explicitly log sanitized error details before calling jsonError, without
exposing sensitive details publicly.

---

303-308: 🩺 Stability & Availability | 🟠 Major | ⚡ Quick win

Keep client-abort gating before jsonError.

Abort errors raised during parsing, authentication, or rate-limit work now reach jsonError, whose logging path records them. The stream-local abort guard does not cover this outer catch, so routine client cancellations can still pollute server-failure logs. Restore an early request.signal.aborted path or make jsonError abort-aware.

As per coding guidelines, add a targeted regression test for this abort path and run the narrowest relevant validation.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/app/api/answer/stream/route.ts` around lines 303 - 308, Ensure the outer
error handling in the answer stream route checks request.signal.aborted before
either jsonError call, returning the existing client-abort response without
logging it as a server failure. Preserve the current PublicApiError and generic
Error responses for non-aborted requests, and add a focused regression test
covering an abort during parsing, authentication, or rate-limit processing.

Source: Coding guidelines

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@src/app/api/answer/stream/route.ts`:
- Around line 306-308: Update the Error branch in the answer-processing handler
to preserve the original exception’s message and stack for internal logging
while still returning the sanitized PublicApiError response. Pass the original
error as the wrapper’s cause or explicitly log sanitized error details before
calling jsonError, without exposing sensitive details publicly.
- Around line 303-308: Ensure the outer error handling in the answer stream
route checks request.signal.aborted before either jsonError call, returning the
existing client-abort response without logging it as a server failure. Preserve
the current PublicApiError and generic Error responses for non-aborted requests,
and add a focused regression test covering an abort during parsing,
authentication, or rate-limit processing.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: a480ca4d-8fbd-4389-ac02-fc7d63544e8e

📥 Commits

Reviewing files that changed from the base of the PR and between d3319a4 and 1452485.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (12)

• docs/site-map.md
• next.config.ts
• package.json
• src/app/api/answer/stream/route.ts
• src/app/api/monitoring/route.ts
• src/app/global-error.tsx
• src/components/route-error-boundary.tsx
• src/instrumentation-client.ts
• src/lib/env.ts
• src/lib/observability/sentry-client.ts
• src/lib/observability/sentry-scrub.ts
• tests/sentry-client.test.ts

💤 Files with no reviewable changes (10)

• src/lib/observability/sentry-client.ts
• src/app/global-error.tsx
• src/components/route-error-boundary.tsx
• docs/site-map.md
• src/lib/observability/sentry-scrub.ts
• package.json
• tests/sentry-client.test.ts
• src/lib/env.ts
• src/app/api/monitoring/route.ts
• src/instrumentation-client.ts