fix: open popup on the same display as the source window in multi-monitor setups

[Copilot]

In multi-display environments, popup windows were always opening on the primary display instead of the display containing the source window.

Root Cause

getScreenSize() in the service worker context calls chrome.windows.getCurrent() to determine which display to use for bounds-checking. From a service worker, getCurrent() unreliably returns the last-focused window — often one on the primary display — rather than the window the user was actually interacting with. This caused adjustWindowPosition() to recalculate the popup position using the wrong display's bounds, snapping it to the primary monitor.

Changes

• screen.ts: Add optional hint?: { top: number; left: number } to getScreenSize(). When provided, the hint coordinates are used to identify the target display directly, bypassing getCurrent(). Falls back to existing getCurrent() behavior when no hint is given.

• chrome.ts: Pass the popup's target { top, left } coordinates as the hint when calling getScreenSize() in both openPopupWindow and openPopupWindowMultiple. These coordinates already originate from the content script's correct window position, so they reliably identify the right display.

// Before
const screenSize = await getScreenSize()

// After — use popup target coordinates to find the correct display
const screenSize = await getScreenSize({ top, left })

• screen.test.ts (new): Tests covering single/multi-display hint resolution, fallback to primary when hint is out-of-bounds, and non-service-worker path.

[codecov]

Codecov Report

❌ Patch coverage is 79.71014% with 14 lines in your changes missing coverage. Please review.
✅ Project coverage is 28.00%. Comparing base (a8b8dc9) to head (cbb656c).
⚠️ Report is 35 commits behind head on main.

Files with missing lines	Patch %	Lines
packages/extension/src/services/hub/background.ts	86.66%	6 Missing ⚠️
...ackages/extension/src/hooks/useCommandHubBridge.ts	0.00%	5 Missing ⚠️
packages/extension/src/services/chrome.ts	0.00%	2 Missing ⚠️
...ckages/extension/src/hooks/useDetectLinkCommand.ts	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #410      +/-   ##
==========================================
+ Coverage   27.84%   28.00%   +0.16%     
==========================================
  Files         317      317              
  Lines       32448    32480      +32     
  Branches     1815     1840      +25     
==========================================
+ Hits         9034     9097      +63     
+ Misses      23414    23383      -31     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}