fix: finish screenshot-PR residuals (Also matches order + error focus)

[BigSimmo]

Summary

• Moves tools/favourites UniversalSearchAlsoMatches rendering to after primary mode hub content in ClinicalDashboard, matching the post-results placement landed from the screenshot PR queue (Place Also matches panel after primary search results #797 via fix: land unique open-PR queue onto current main #808).
• Switches the route error-boundary heading from focus-visible: to focus: so programmatic recovery focus remains visible after pointer-driven failures (CodeRabbit finding on superseded fix: harden Therapy Compass recovery and error accessibility #800).
• Distinguishes EmptyState error titles by mode (Answer unavailable vs Search unavailable) from superseded fix: unify answer recovery states with shared EmptyState #802 review feedback.

Verification

• npm run test:focused -- --files src/components/route-error-boundary.tsx,src/components/ClinicalDashboard.tsx (5 passed)
• UI verification not run: change is DOM order + focus utility class + EmptyState title string only; hosted Production UI covers the affected dashboard paths
• Hosted CI: Static / Unit / Production UI as required by change scope

Risk and rollout

• Risk: low — DOM order for Also matches on tools/favourites, a11y focus ring on error recovery, and mode-specific error titles
• Rollback: revert this squash merge
• 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

• Follow-up residuals after fix: land unique open-PR queue onto current main #808/docs: record screenshot PR queue merge babysit in ledger #810 closed the screenshot PR queue.

Summary by CodeRabbit

• Bug Fixes
  • Improved how “also matches” results are displayed by ensuring they appear consistently across answer and non-answer views.
  • Made the route error heading more consistent for keyboard users by adjusting focus styling.
  • Updated the error fallback messaging to be mode-aware, showing the appropriate “unavailable” title depending on the current view.

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

📝 Walkthrough

Walkthrough

This change makes search error messaging mode-aware, broadens UniversalSearchAlsoMatches rendering based on its visibility flag, and changes route error heading focus styling from focus-visible to focus utilities.

Changes

Universal search rendering

Layer / File(s)	Summary
Universal search match and error rendering src/components/ClinicalDashboard.tsx	Unavailable errors now distinguish answer and search modes, while UniversalSearchAlsoMatches renders based solely on showUniversalAlsoMatches.

Route error focus styling

Layer / File(s)	Summary
Error heading focus styling src/components/route-error-boundary.tsx	The error heading uses focus:outline* utilities instead of focus-visible:outline* utilities.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• BigSimmo/Database#658: Changes related UniversalSearchAlsoMatches rendering and activeModeResultKind logic.
• BigSimmo/Database#745: Updates the related “Also matches” panel behavior.
• BigSimmo/Database#758: Updates route error heading focus behavior and styling.

Suggested labels:codex

Suggested reviewers:claude, cursoragent

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.
Title check	✅ Passed	The title is specific and matches the main UI fixes, including Also matches ordering and focus/error behavior.
Description check	✅ Passed	The description follows the template and includes summary, verification, risk, and clinical governance sections.

✨ 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 cursor/pr-queue-residuals-8807

---

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