Windows

The windows role manages Windows from inside WSL over the interop bridge (see the windows role). Everything it ships runs over interop — powershell.exe, winget, and wt.exe on PATH, processes running as the interactive Windows user. These items extend past what interop covers.

Items

• WSL-side aliases that fire a workspace launcher from a Linux prompt (the wsl role ergonomics half)
• scoop as a second package source next to winget
• A real desired-state transport (SSH or WinRM) for headless convergence, using ansible.windows / community.windows win_* modules for packages, registry, and config

The transport question

SSH or WinRM would add real desired-state convergence for a headless host, but two constraints keep it undecided against the interop path that ships today:

• WSL2 networking: reaching the Windows host from the guest needs Windows 11 mirrored networking mode, or targeting the host by its gateway IP. Interop sidesteps this, since it is not a network connection.
• Session isolation: SSH/WinRM land in session 0, isolated from the interactive desktop, so GUI apps (the workspace launchers) never appear where you want them. Those stay on interop and login triggers regardless; SSH/WinRM would converge headless state only.