fix: unify answer recovery states

[BigSimmo]

Summary

• Unify answer journey recovery states (cancelled / no-results / failure) onto the shared EmptyState primitive in ClinicalDashboard.
• Keeps existing recovery actions while aligning visual hierarchy and ARIA semantics.
• Replaces superseded PR fix: unify answer recovery states #760/Unify answer recovery states with shared EmptyState primitive #755.

Verification

• npm run verify:pr-local — covered by CI Static PR checks / Unit coverage on this PR
• UI verification not run: recovery EmptyState wiring only; CI Production UI gate covers smoke

Risk and rollout

• Risk: low; UI recovery presentation only, no answer generation or retrieval contract changes
• Rollback: revert this PR to restore prior ad-hoc recovery surfaces
• 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

Notes

• Replacement PR with policy-complete evidence so CI can merge onto main.

  

[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: faa05a58-df3e-4b91-8e04-5540a6ceab54

📥 Commits

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

📒 Files selected for processing (3)

• src/components/ClinicalDashboard.tsx
• src/components/ui-primitives.tsx
• tests/ui-primitives.dom.test.tsx

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cursor/unify-answer-recovery-40ad

---

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