Reduce registry latency and align Sentry release identity

[BigSimmo]

Summary

• reduce Services and Forms registry latency with counts-only and compact search projections, explicit gzip, and correct Accept-Encoding cache variance
• keep the Therapy catalogue workspace off the exact mode home and unrelated routes while preserving child-route behavior
• align Sentry app, edge, worker, source-map, and Railway release identities; capture Next request errors through the SDK-native path and expose a validated deployment commit SHA in health responses
• queue canonical issue-ledger updates for route-wide LCP, Lighthouse enforcement, unavailable CrUX INP, and post-deploy registry verification

Verification

• npm run verify:pr-local
  • Partial: runtime, installed-lock parity, formatting, sitemap/docs, ledger guards, lint, and typecheck passed. The full Vitest stage exceeded the 30-minute outer wrapper and ended with output-pipe EPIPE; build and later stages were not reached in that invocation.
• npm run verify:ui when UI, routing, styling, browser behavior, reduced-motion, or forced-colors behavior changed
  • UI verification not run: no visual styling change; focused route-loading and consumer DOM contracts passed. Hosted CI remains authoritative for broad browser coverage.
• npm run verify:release before release or handoff confidence claims
  • Not run locally; hosted CI and post-deploy verification are required before release confidence.
• Focused Vitest: 98 tests passed across registry API, registry consumers, Therapy loading, health, Railway configuration, Sentry release/request capture, and worker observability.
• Registry API final rerun: 23/23 passed after the cache-variant repair.
• npm run format
• npm run check:production-readiness
  • Source/config guard ran; local provider-dependent checks failed closed because this isolated worktree intentionally has no .env.local, Supabase service key, OpenAI key, or query-hash secret.
• npm run check:deployment-readiness
  • Environment-gated: requires production-only Supabase/OpenAI/query-hash secrets; no secrets were copied into this worktree.

Risk and rollout

• Risk: registry response-shape and cache-header changes could affect home counts or cross-mode search; release metadata could fragment Sentry events if the host omits the Railway commit build argument.
• Rollback: revert this PR; registry clients return to the existing full projection and Sentry falls back to the prior release resolver. No schema or data migration is included.
• Provider or production effects: branch publication and PR creation are authorized. CI Lighthouse refresh and Railway deployment are being handled separately under the same explicit authorization; production verification must match the deployed commit SHA.

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

• Official CrUX current-record queries returned no eligible field dataset for the origin or reviewed routes. This is recorded as unavailable, not a pass.
• Local Lighthouse evidence was incomplete because Windows Chrome profile cleanup hit EPERM; no developer-machine baseline is proposed.

[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:7 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: 50cb4397-57d4-4344-86ae-d533f5bf1c21

📥 Commits

Reviewing files that changed from the base of the PR and between 8338cf9 and 9850510.

📒 Files selected for processing (39)

• .github/workflows/ci.yml
• Dockerfile
• docs/branch-review-records/402da565548d3320ca4658131e171ca3fd122ed2ee1208f0675ff691870f530e.record.md
• docs/branch-review-records/4aa3c2064bb6f8dc41dc844578ab75b6f89ec582b62bf08fea40e9ab761158d8.record.md
• docs/branch-review-records/540c7cf7962d52849e293ba470febceef7ea5949b2e7b7bc2506023e945e4783.record.md
• docs/error-tracking.md
• docs/outstanding-issues-inbox/155e96f9-c111-4d18-b4d8-5f83b3f79907.json
• docs/outstanding-issues-inbox/2ab54188-4652-42e2-a6b0-ff2f673d3d10.json
• docs/outstanding-issues-inbox/67f9ce93-caf5-4cd4-89e1-742e61ce882a.json
• docs/outstanding-issues-inbox/78fad74b-9478-4e58-9131-8a6bc5858c79.json
• docs/outstanding-issues-inbox/9a3ea3c5-31ed-4a89-a035-e6d364b906bf.json
• docs/outstanding-issues-inbox/a4bf50b9-95bf-458f-9a16-a80acf0830c0.json
• docs/outstanding-issues-inbox/e760edf4-fdf7-41c2-aa97-6f4563c6152f.json
• docs/process-hardening.md
• lighthouse-budget.json
• next.config.ts
• src/app/api/registry/records/route.ts
• src/components/clinical-dashboard/cross-mode-links.tsx
• src/components/clinical-dashboard/shared-search-app-shell.tsx
• src/components/clinical-dashboard/use-saved-registry-favourites.ts
• src/components/forms/forms-home-page.tsx
• src/components/services/services-home-page.tsx
• src/components/therapy-compass/screens/home-screen.tsx
• src/lib/health-response.ts
• src/lib/observability/error-tracking.ts
• src/lib/observability/sentry-release.ts
• src/lib/use-registry-records.ts
• src/sentry.edge.config.ts
• src/sentry.server.config.ts
• tests/catalog-refetch-privacy.dom.test.tsx
• tests/ci-cache-safety.test.ts
• tests/health-route.test.ts
• tests/mode-home-loading-contract.test.ts
• tests/railway-config.test.ts
• tests/registry-records-route.test.ts
• tests/sentry-release.test.ts
• tests/sentry-request-error.test.ts
• tests/therapy-compass-data-recovery.dom.test.tsx
• worker/observability.ts

✨ 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 codex/performance-fixes-20260813

---

_{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:41319ba9fb

ℹ️ 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".

[BigSimmo]

@codex resolve actionable Codex review findings for this pull request and current head using the repository instructions. This is the pull request's single automatic repair pass: do not perform a fresh review, create new standalone findings, or request another review. Work only the existing unresolved Codex threads on the current head. The only repository destination is BigSimmo/Database, and the only branch destination is the pull request head branch codex/performance-fixes-20260813 at starting commit 41319ba; never publish fixes to a detached or synthetic work branch and never create a stacked pull request. Use the authenticated GitHub connector to commit each approved fix to BigSimmo/Database:codex/performance-fixes-20260813, then verify that the pull request head contains the published commit before reporting success. Always fix P0 and P1 findings. For P2 and lower findings, fix only clear, scoped, low-risk issues; otherwise disposition them with a concise reason. For a fixed thread, reply with as the first line and as the second line. For a no-code disposition, use followed by . These result markers authorize the workflow to close that exact thread only after it verifies a fixed commit is the pull request head; a local-only commit is not a fix. If publication or verification fails, do not use either result marker, do not claim success, and leave the thread open with the blocker. If human input or new authorization is required, do the same. Finish only after every actionable thread is fixed or dispositioned and closed, or explicitly left open for a human decision. Do not update the branch from main, address unrelated reviews, broaden scope, or create more than one scoped fix commit. Do not use external APIs, paid services, credentials, dependency changes, or broad refactors unless explicitly authorized. Add targeted tests where behavior changes and run the narrowest relevant validation.

[github-actions]

CI triage

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

• Lighthouse budget — needs investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.
• PR required — needs investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.

Compared with main CI run #10508 (cancelled).

Classification is evidence routing, not permission to ignore a failure. Exact quarantined Playwright identities remain governed by the flake ledger.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Swish!

Reviewed commit:41319ba9fb

ℹ️ 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".