fix(packaging/windows): Windows 11 22H2 floor + tray install task + stale console-port fixes

The OS floor is now enforced at install time (MinVersion=10.0.22621 with an
explanatory [Messages] override): pf-vdisplay is built against IddCx 1.10, and
on Windows 10 (incl. LTSC) / Win11 21H2 the device fails start with Code 10
STATUS_DEVICE_POWER_FAILURE (field-reported). Docs (site requirements/install/
windows-host pages + README) state the floor; new docs-site Security page.

Installer also gains the trayicon task (punktfunk-tray.exe file + HKLM Run key,
post-install launch as the signed-in user, upgrade taskkill + uninstall
--quit/taskkill choreography before file deletion), and the wizard/cleanup
text/port sweeps move off the stale :3000 web-console references to :47992
(cleanups sweep both for upgrades from old installs).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

docs-site/content/docs/troubleshooting.md

@@ -73,6 +73,17 @@ Then log out and back in. On other distros this is `sudo usermod -aG input $USER
   concurrent native sessions (up to 4 by default); heavy load is usually bitrate-bound, so
   lower the bitrate first.
 
+## Windows: "punktfunk Virtual Display" shows Code 10 in Device Manager
+
+Sessions end with *"pf-vdisplay driver interface not found"* and Device Manager shows the
+**punktfunk Virtual Display** device failed with **Code 10** (`STATUS_DEVICE_POWER_FAILURE`).
+
+This means your Windows version is too old. The virtual-display driver requires the **IddCx 1.10**
+driver framework, which first shipped in **Windows 11 22H2 (build 22621)** — on Windows 10
+(including LTSC) and Windows 11 21H2 the driver installs but cannot start. Reinstalling won't help;
+the fix is updating to Windows 11 22H2 or newer. (Current installers refuse to run on older
+Windows for this reason; if you see this, the host was likely installed with an older installer.)
+
 ## Still stuck?
 
 Run the host with `RUST_LOG=info` (or `debug`) and check `journalctl --user -u punktfunk-host` for the