From 8d1539dbb575e08ae912dd562e34f86da251c86e Mon Sep 17 00:00:00 2001
From: Cursor Agent <cursoragent@cursor.com>
Date: Sat, 18 Jul 2026 06:26:51 +0000
Subject: [PATCH 1/2] fix: place Also matches after mode hubs and always show
 error focus

Keep tools/favourites Also matches after primary hub content so the
panel matches the post-results placement landed from the screenshot
queue, and use focus: styles on the route error heading so recovery
focus remains visible after pointer-driven failures.

Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
---
 src/components/ClinicalDashboard.tsx    | 6 +-----
 src/components/route-error-boundary.tsx | 2 +-
 2 files changed, 2 insertions(+), 6 deletions(-)

diff --git a/src/components/ClinicalDashboard.tsx b/src/components/ClinicalDashboard.tsx
index 2e5b7b7b5..c56e1f662 100644
--- a/src/components/ClinicalDashboard.tsx
+++ b/src/components/ClinicalDashboard.tsx
@@ -3716,10 +3716,6 @@ export function ClinicalDashboard({
                     </div>
                   ) : null)}
 
-                {showUniversalAlsoMatches && activeModeResultKind !== "answer" ? (
-                  <UniversalSearchAlsoMatches modeId={searchMode} query={universalAlsoMatchesQuery} />
-                ) : null}
-
                 {activeModeResultKind === "differentials" ? (
                   <DifferentialsHome
                     query={query}
@@ -3880,7 +3876,7 @@ export function ClinicalDashboard({
                   />
                 ) : null}
 
-                {showUniversalAlsoMatches && activeModeResultKind === "answer" ? (
+                {showUniversalAlsoMatches ? (
                   <UniversalSearchAlsoMatches modeId={searchMode} query={universalAlsoMatchesQuery} />
                 ) : null}
               </section>
diff --git a/src/components/route-error-boundary.tsx b/src/components/route-error-boundary.tsx
index 6d31de18e..04f053b3a 100644
--- a/src/components/route-error-boundary.tsx
+++ b/src/components/route-error-boundary.tsx
@@ -59,7 +59,7 @@ export function RouteErrorBoundary({
         <h1
           ref={headingRef}
           tabIndex={-1}
-          className="mt-4 text-lg font-semibold tracking-tight text-[color:var(--text-heading)] focus-visible:outline focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-[color:var(--focus-ring,Highlight)]"
+          className="mt-4 text-lg font-semibold tracking-tight text-[color:var(--text-heading)] focus:outline focus:outline-2 focus:outline-offset-2 focus:outline-[color:var(--focus-ring,Highlight)]"
         >
           {title}
         </h1>

From de50f3658dcee93dbd23dc6182f64d43263ff972 Mon Sep 17 00:00:00 2001
From: Cursor Agent <cursoragent@cursor.com>
Date: Sat, 18 Jul 2026 06:30:24 +0000
Subject: [PATCH 2/2] fix: distinguish answer vs search EmptyState error titles

CodeRabbit residual from superseded #802: non-answer modes should not
show "Answer unavailable" for document-search/clipboard failures.

Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
---
 src/components/ClinicalDashboard.tsx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/components/ClinicalDashboard.tsx b/src/components/ClinicalDashboard.tsx
index c56e1f662..073fe88c9 100644
--- a/src/components/ClinicalDashboard.tsx
+++ b/src/components/ClinicalDashboard.tsx
@@ -3648,7 +3648,7 @@ export function ClinicalDashboard({
                 ) : error ? (
                   <EmptyState
                     icon={CircleAlert}
-                    title="Answer unavailable"
+                    title={activeModeResultKind === "answer" ? "Answer unavailable" : "Search unavailable"}
                     body={error}
                     live="assertive"
                     tone="danger"