## Problem

When `omarchy-windows-vm launch` is run, the script starts the VM and then immediately invokes `xfreerdp3`. If `xfreerdp3` fails to connect (e.g. RDP not ready yet, user prefers the web interface at port 8006, or RDP is simply not needed), the script falls through to the cleanup block and runs `docker compose down`, **silently shutting down the VM**.

From the user's perspective: the VM appears to start, nothing happens, and the container stops — with no clear explanation.

## Steps to reproduce

1. `omarchy-windows-vm launch`
2. `xfreerdp3` fails to connect (or user closes it immediately)
3. VM is stopped via `docker compose down`

## Expected behavior

If `xfreerdp3` fails, the VM should continue running. The script should not conflate "RDP client exited" with "user is done with the VM".

## Suggested fix

Add a `--no-client` / `-n` flag to `launch` that starts the VM without opening any RDP client, and update the `.desktop` launcher to use it by default (or at least don't auto-stop on RDP failure).

```bash
if [[ $NO_CLIENT = "true" ]]; then
  echo "Windows VM is running. Connect via http://127.0.0.1:8006"
  return 0
fi
```

The dockurr/windows image already exposes a fully functional web interface on port 8006 — many users prefer this over RDP.

## Environment

- omarchy commit: `7514ae7d`
- xfreerdp3 exits with non-zero when RDP is unavailable or connection is refused