Preserve focus=1 behavior on initial shell route loads

[Copilot]

Summary

• Initial hard loads of shell mode-home deep links (e.g. /forms?focus=1, /services?focus=1) could drop keyboard focus after hydration/remount timing, so only later param changes reliably focused the composer.
• Updated shell focus handling to make initial-load focus resilient and added targeted UI coverage for deep-link entry paths.
• Focus reapply hardening
  • Split focus handling into a dedicated effect keyed by route/search params.
  • Re-applies focus on first frame and one short delayed retry, while avoiding focus-steal if another interactive element is already active.
• Regression coverage
  • Added an e2e assertion that /services?focus=1 and /forms?focus=1 land with global-search-input focused.

const shouldApplyFocus = (activeElement: Element | null) =>
  !activeElement || activeElement === document.body || activeElement === document.documentElement;

const frame = window.requestAnimationFrame(focusInput);
const timeout = window.setTimeout(focusInput, focusHydrationRetryDelayMs);

Verification

• npm run verify:cheap
• npm run verify:ui when UI, routing, styling, browser behavior, reduced-motion, or forced-colors behavior changed
• npm run verify:release before release or handoff confidence claims
• npm run format:check
• npm run check:production-readiness when clinical workflow, privacy, environment, Supabase, source governance, or deployment behavior changed
• npm run check:deployment-readiness when deployment startup, hosting, or rollout behavior changed

Clinical Governance Preflight

Complete this section when the change touches ingestion, answer generation, search/ranking, source rendering, document access, privacy, production env, or clinical output.

• 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

• Scope is limited to shell composer focus behavior and its UI regression coverage; no clinical, privacy, or deployment-path logic changes.

[BigSimmo]

@copilot resolve the merge conflicts in this pull request

[Copilot]

@copilot resolve the merge conflicts in this pull request

Resolved by merging origin/main into this branch and fixing the conflict in src/components/clinical-dashboard/global-mockup-search-shell.tsx in commit b0cd9e2.