fix(a11y): add focusin/focusout to saved-query nav hover tooltip (WCAG 2.1.1)

[bilal-karim]

Summary

The saved-query nav rail and its standalone-activities sibling render query buttons with mouse-only tooltip handlers. When the rail is collapsed, query-button labels are truncated — mouse users see the full label in the floating tooltip but keyboard users tabbing through the rail see only icons.

This PR adds onfocusin / onfocusout alongside the existing mouse handlers so the same onQueryBtnEnter / onQueryBtnLeave callbacks fire on keyboard focus. Handler signatures widen from MouseEvent to MouseEvent | FocusEvent.

   <div
     class="w-full"
     role="menuitem"
     tabindex="-1"
     onmouseenter={(e) => onQueryBtnEnter(e, view.name)}
     onmousemove={onQueryBtnMove}
     onmouseleave={onQueryBtnLeave}
+    onfocusin={(e) => onQueryBtnEnter(e, view.name)}
+    onfocusout={onQueryBtnLeave}
   >

How it works

• focusin / focusout bubble from descendants (unlike focus / blur)
• The wrapper has tabindex="-1" (not itself a focus stop); focus on the inner <Button> bubbles to the wrapper where the handlers are attached
• e.currentTarget resolves to the wrapper for both mouse and focus events, so positionTooltipFrom(el) computes the same bounding rect either way
• The existing if ($savedQueryNavOpen) return; guard short-circuits when the nav is expanded, so no tooltip is shown on focus when the inline label is sufficient (matches today's mouse-side behavior)

Audit context

• WCAG 2.2 SC 2.1.1 Keyboard (Level A) — Medium remediation priority.
• Pattern matches existing precedent in 3 Holocene table-body-cell components (workflows, activities, workers) that already pair onmouseover with onfocusin for hover-OR-focus UI reveal.

Test plan

• Collapse the saved-query nav (workflows page, saved-views drawer). Tab through each query-button. The floating tooltip should appear next to the focused button with the full (untruncated) name.
• Tab order is unchanged — only the inner <Button> is a focus stop; the wrapper stays tabindex="-1".
• Repeat on saved-views.svelte (standalone activities surface).
• Expand the nav and Tab through again — no tooltip should appear (inline label is sufficient; matches today's mouse behavior).
• Mouse hover still shows and hides the tooltip identically to today (regression check).
• Screen reader smoke test: confirm <Button> accessible name continues to announce normally.

Out of scope

• Escape-to-dismiss for the hand-rolled tooltip (deferred to a future migration onto the upgraded Tooltip primitive from PR fix(a11y): make Tooltip keyboard-accessible, dismissible, and hoverable #3429)
• aria-describedby linkage between trigger and tooltip (separate 4.1.2 concern)

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
holocene	Ready	Preview, Comment	May 26, 2026 1:10am

[temporal-cicd]

Warnings

⚠️

📊 Strict Mode: 4 errors in 2 files (0.4% of 908 total) src/lib/components/standalone-activities/saved-views.svelte (1) L153:25: Argument of type 'string | undefined' is not assignable to parameter of type 'string | number | boolean'. src/lib/pages/saved-query-views.svelte (3) L397:8: 'view.count' is possibly 'undefined'. L404:51: 'view.count' is possibly 'undefined'. L151:25: 'activeQueryView' is possibly 'undefined'.

Generated by 🚫 dangerJS against c46b8b9

[bilal-karim]

Warnings
⚠️
📊 Strict Mode: 4 errors in 2 files (0.4% of 908 total)

src/lib/components/standalone-activities/saved-views.svelte (1)

• L153:25: Argument of type 'string | undefined' is not assignable to parameter of type 'string | number | boolean'.

src/lib/pages/saved-query-views.svelte (3)

• L397:8: 'view.count' is possibly 'undefined'.
• L404:51: 'view.count' is possibly 'undefined'.
• L151:25: 'activeQueryView' is possibly 'undefined'.

Generated by 🚫 dangerJS against c46b8b9

Pre-existing errors