Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

fix(ui): address Copilot findings on overlay mouse integration tests

Copilot flagged three weaknesses in the click-dispatch tests added in
the prior review-fix commit:

1. TestModel_HandleMouse_ClickConfirmsThemeSelect asserted only
   overlay-close, which Manager.HandleMouse guarantees on
   OutcomeThemeConfirmed before Model dispatch runs — and opening via
   mgr.OpenThemeSelect bypassed Model.openThemeSelector, leaving
   themePreview nil so confirmThemeByName was a silent no-op. Now
   opens via the real Model path, uses the test theme catalog, and
   asserts themePreview cleared + activeThemeName set to the clicked
   entry.

2. TestModel_HandleMouse_ClickJumpsAnnotList had the same weak
   assertion. Now asserts pendingAnnotJump set to the cross-file
   target (b.go, line 1) — the real Model-side effect of
   jumpToAnnotationTarget.

3. Base screen buffer used Repeat("line\n", height) which adds a
   trailing newline and makes strings.Split yield height+1 rows,
   shifting Manager.bounds vs real View() output. Added
   makeOverlayBase helper matching overlay/help_test.go::makeBase
   (join without trailing), used across all affected tests.

Click coordinates are now computed against concrete popup layouts
(themeselect popup spans rows 15-23; annotlist popup spans 15-23 with
5 items) so the tests hit known entry rows deterministically.