Add an opt-in bridge for approved Windows apps in Omarchy

[btsouth]

The Reddit feedback asks for approved Windows applications to appear in the Omarchy launcher while Windows remains the host. The first useful step is a launch-and-return flow; showing a Windows window inside Hyprland is a separate integration milestone.

Phase 1: approved application launching

• Add an opt-in Windows Settings page to select and remove specific installed desktop applications. Keep approvals in the host installation's preferences.
• Export approved entries into the guest's application launcher with stable IDs and clear Windows labels/icons.
• Let the guest request only an approved ID. The host resolves it to a stored executable and launches it without a shell or guest-supplied path, arguments, URL, or working directory.
• Use QEMU's private host/guest channel. Bind the Windows service to loopback, not a LAN interface. Limit message size, rate, and concurrent launches, and report failures to the user.
• For the initial usable flow, reveal the launched Windows app and provide an obvious way back to the fullscreen Omarchy window. Startup must never implicitly launch approved Windows apps.
• Remove stale guest launcher entries when an approval is revoked, the app is removed, or this Try Omarchy installation is uninstalled.
• Test malformed requests, duplicate launches, revoked approvals, path changes, and installs with multiple Try Omarchy copies.

Phase 2: window integration

• Investigate capture, input, focus, scaling, audio, clipboard, and lifecycle for displaying a single approved Windows app in an Omarchy window. Preserve a reliable escape to the Windows desktop and make capture status obvious.
• Prototype with ordinary desktop apps first; measure latency and behavior across resize, minimize, monitor changes, and sleep/resume.
• Treat anti-cheat and protected content as compatibility tests. Native host execution alone does not guarantee they allow capture or embedded interaction.

The sign-in/fullscreen path is covered separately by PR #158.

[btsouth]

PR #164 now has a physically tested guest-to-host, one-shot Settings request over the existing private agent port. The host bounds pending connections, keeps the persistent guest agent separate, and dispatches the native window on the tray thread. This is useful infrastructure for phase 1 here, but it does not yet approve or launch Windows applications. App requests will need their own allowlisted IDs, per-installation preferences, rate limits and revocation behavior described above.

[btsouth]

Phase 1 is now PR #169. It adds the Windows approval UI, guest launcher entries, private ID-only launch request, immediate host-side revocation, and a tray return from fullscreen. The AMD laptop physically launched Notepad from the guest, rejected its ID after revocation, removed the guest entry on sync, and returned to Omarchy. The new guest image built and passed boot smoke. The acceptance record has exact hashes and limits. Keep this issue open for the embedded-window milestone and per-app icon work; the public v0.1.0 release does not yet carry phase 1.

[btsouth]

Phase 1 is shipped in public v0.2.0. The signed candidate on the AMD Windows 11 laptop opened host Settings from the guest, launched an approved Notepad entry, rejected its ID after approval was removed, removed the guest launcher entry on sync, and booted the updated guest twice with the original user file preserved. See the signed candidate record once the documentation follow-up lands. The public release workflow passed tagged and Latest asset checks. Keep this issue open for the separate embedded-window milestone and per-app icons.