Expose privacy-safe answer coalescing metrics on deep health probe

[BigSimmo]

Summary

• Adds privacy-safe in-process answer coalescing metrics (originations, waiters, active, rate) on the authorized deep health probe without exposing queries, owners, documents, or cache keys.
• Keeps /api/health/ready free of diagnostic counters.
• Supersedes Expose privacy-safe in-process answer coalescing metrics on deep health probe #754.

Verification

• Hosted Static PR checks / Build / Unit coverage / Migration replay / Advisory UI on the predecessor head.
• Verification not run locally in this babysit pass: hosted CI used as evidence.

Risk and rollout

• Risk: low; additive in-process observability only; no patient content exposed.
• Rollback: revert this PR to remove the coalescing metrics block from the deep health probe.
• Provider or production effects: None

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

  

[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

@cursor[bot], you've reached your PR review limit, so we couldn't start this review.

Next review available in: 1 minute

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: fac4311b-f8aa-4053-8142-02ab24cbf3b4

📥 Commits

Reviewing files that changed from the base of the PR and between d723aa2 and ebf35c8.

📒 Files selected for processing (8)

• docs/capacity-review.md
• docs/observability-slos.md
• src/app/api/health/ready/route.ts
• src/lib/health-response.ts
• src/lib/observability/answer-coalescing-metrics.ts
• src/lib/rag.ts
• tests/answer-coalescing-metrics.test.ts
• tests/health-route.test.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cursor/coalescing-metrics-db17

---

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