fix(windows): link the client as a GUI subsystem — no console window on launch

The binary had no windows_subsystem attribute, so it linked as a console (CUI) app and Windows
opened a console window alongside the WinUI window on every launch (incl. the MSIX). Add
#![cfg_attr(windows, windows_subsystem = "windows")] so the windowed/MSIX launch is window-free
(verified: the built exe's PE subsystem flips from WINDOWS_CUI=3 to WINDOWS_GUI=2). To keep the CLI
paths usable, main now calls AttachConsole(ATTACH_PARENT_PROCESS) at startup — it binds to an
existing parent console only (never creates one), so --headless/--discover still print to the
launching terminal while Explorer/MSIX launches stay console-free. Adds the Win32_System_Console
windows feature.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

crates/punktfunk-client-windows/Cargo.toml

@@ -37,6 +37,7 @@ windows = { git = "https://github.com/microsoft/windows-rs", rev = "b4129fcc1ae8
     "Win32_Graphics_Direct3D11",
     "Win32_Graphics_Direct3D_Fxc",
     "Win32_Graphics_Gdi",
+    "Win32_System_Console",
     "Win32_System_LibraryLoader",
     "Win32_UI_Input_KeyboardAndMouse",
     "Win32_UI_WindowsAndMessaging",

crates/punktfunk-client-windows/src/main.rs

@@ -12,6 +12,11 @@
 //!   punktfunk-client --headless --connect host[:port] [--pin HEX] [--pair PIN] [--mode WxHxHz]
 //!                    [--bitrate MBPS] [--mic]  (no window; count frames + print stats)
 
+// Link as a GUI (windows) subsystem binary so the default windowed launch (MSIX / double-click)
+// does NOT pop a console window. The CLI paths (--headless/--discover) reattach to the launching
+// terminal's console at startup (see main), so their output is still visible when run from a shell.
+#![cfg_attr(windows, windows_subsystem = "windows")]
+
 #[cfg(windows)]
 mod app;
 #[cfg(windows)]
@@ -33,6 +38,15 @@ mod video;
 
 #[cfg(windows)]
 fn main() {
+    // With #![windows_subsystem = "windows"] the process starts with no console, so the GUI/MSIX
+    // launch is window-free. AttachConsole only binds to an ALREADY-EXISTING parent console (it
+    // never creates one), so when launched from a terminal — `--headless`/`--discover` — stdout and
+    // the tracing writer below land in that terminal; from Explorer/MSIX it's a harmless no-op.
+    unsafe {
+        use windows::Win32::System::Console::{AttachConsole, ATTACH_PARENT_PROCESS};
+        let _ = AttachConsole(ATTACH_PARENT_PROCESS);
+    }
+
     tracing_subscriber::fmt()
         .with_env_filter(
             tracing_subscriber::EnvFilter::try_from_default_env().unwrap_or_else(|_| "info".into()),