fix same-mode focus restore not stealing deliberate focus

[BigSimmo]

Summary

• Follow-up to Make the shared home mode-aware #1790: remove the force-focus fallback on same-mode reselect so deferred restore uses only restoreFocusUnlessMoved.
• Add a DOM regression test that moves focus outside during restore and asserts the mode trigger does not steal it.
• Append the Make the shared home mode-aware #1790 babysit ledger row.

Why

CodeRabbit flagged that PR #1790's same-mode focus fix could override deliberate focus moves after the mode menu closed. That correction raced auto-merge and did not land in the squash, so this PR lands it on main.

Areas touched

• MasterSearchHeader same-mode focus restore path
• Mode-menu DOM coverage
• Branch review ledger (append-only)

Verification

• Focused change is a 4-line behavior fix plus one DOM test and one ledger row.
• Full PR CI will validate on this head.

Risk and compatibility

• No route, API, schema, retrieval, ranking, or clinical-output changes.
• Narrow focus-behavior correction only.

RAG impact: no retrieval behaviour change — focus restore and DOM test only; submission routing, retrieval, ranking, and answer generation are unchanged.

  

[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

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 46 minutes

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

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

Run ID: 084262df-72a3-49cb-9684-d73c5b4f8c79

📥 Commits

Reviewing files that changed from the base of the PR and between 1074c0d and 4712a12.

📒 Files selected for processing (5)

• docs/branch-review-ledger.md
• src/components/clinical-dashboard/master-search-header.tsx
• tests/check-lighthouse-budget.test.ts
• tests/mode-menu-prefetch.dom.test.tsx
• tests/test-runner-safety.test.ts

---

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

[github-actions]

CI triage

CI failed on this PR. Automated classification of the 2 failed job(s):

• Unit coverage — needs investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.
• PR required — needs investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.

Compared with main CI run #9583 (cancelled).

Classification is evidence routing, not permission to ignore a failure. Exact quarantined Playwright identities remain governed by the flake ledger.

[cursor]

Babysit summary (merged)

• Tip at merge: 4712a128f8c9cc1dae748058df87697d4889f339
• Sync/merge-tree: clean; synced through fix(ci): silence TS5101 baseUrl deprecation for Playwright builds #1798/ci: optimize smart test routing and browser gates #1789
• Blocked earlier by: TS5101 Playwright build (fixed via fix(ci): silence TS5101 baseUrl deprecation for Playwright builds #1798), unit coverage contract drift on generated tsconfig (fixed on branch), up-to-date protection
• Required CI: green
• Merge: squash-merged as 3c193fb83d39355c12ea3b7efd949db7b00f95bb
• Residual risks: none for this focus-restore fix