Restore Windows modifier overlay window

[enaboapps]

Summary

• move the initially visible Windows modifier WebView away from Windows' (-32000, -32000) minimized-window sentinel
• explicitly restore the modifier window before moving and showing it
• cover the safe off-screen bootstrap policy with a regression test

Root cause

Alpha 4 made the Windows modifier WebView initially visible so WebView2 would initialize, but positioned it at (-32000, -32000). Windows uses that placement for minimized windows. The packaged app could therefore initialize the page while leaving the later presentation path unable to produce a visible window.

Installed Alpha 4 inspection matched that failure: the main Tauri window and native cursor-overlay windows existed, but no presentable modifier-overlay Tauri window appeared after the field test.

Validation

• npm run lint
• npm test (57 tests)
• npm run build
• cargo fmt --manifest-path src-tauri/Cargo.toml --check
• cargo clippy --manifest-path src-tauri/Cargo.toml --all-targets -- -D warnings
• cargo test --manifest-path src-tauri/Cargo.toml (133 tests)

Closes #568

[greptile-apps]

Greptile Summary

Summary

Windows modifier-overlay startup now places its visible WebView bootstrap beyond the virtual desktop boundary and restores the window before showing it during a control session. The negative-coordinate monitor layout was exercised with a desktop ending at x=0; the overlay started at x=16, so it does not overlap the display.

Confidence Score: 5/5

No blocking failure remains.

No accepted blocking findings remain.

T-Rex Logs

What T-Rex did

• T-Rex ran the requested contract verification for the pull request, and both verification runs reported that local artifact references were not uploaded.

_{Ran code and verified through T-Rex}

_{Reviews (2): Last reviewed commit: "Keep bootstrap policy portable" | Re-trigger Greptile}