## What happened

Launching the Windows VM via `omarchy-windows-vm launch` (the "Windows" app menu entry) opens the FreeRDP window at the correct/full size for the monitor, but the **remote Windows desktop content itself only renders in a small region (top-left corner, roughly a quarter of the window), with the rest of the window left solid black**. It looks like the window "only fills a quarter of the screen" even though the window manager reports the window at the full/expected tile size.

Screenshot showing the issue (Windows desktop content confined to the top-left, black elsewhere): the Creative Cloud / Windows 11 desktop is visible only in roughly the top-left 40%×55% of the window.

## Root cause

The `xfreerdp3` invocation in `launch_windows()` relies solely on `/dynamic-resolution` (plus a `/floatbar:...,show:fullscreen` cosmetic flag — that only controls when the floating toolbar is shown, it does **not** force fullscreen mode) to size the remote session:

```
xfreerdp3 /u:"$WIN_USER" /p:"$WIN_PASS" /v:127.0.0.1:3389 -grab-keyboard /sound /microphone /clipboard \
  /cert:ignore /title:"Windows VM - Omarchy" /dynamic-resolution /gfx:AVC444 \
  /floatbar:sticky:off,default:visible,show:fullscreen $RDP_SCALE
```

There's no `/f` (true fullscreen) and no explicit `/w:`/`/h:` matching the target monitor's resolution. Under Hyprland + Xwayland, the initial dynamic-resolution negotiation with the guest does not reliably trigger to match the actual window/monitor size, so the RDP session comes up at a small default guest resolution while the local window itself is already correctly sized by the tiling WM — the mismatch shows up as a small rendered desktop pinned in a corner with black filling the rest.

## Fix that worked for me

Replacing the resolution-related flags with an explicit size and true fullscreen mode fixed it immediately and reliably:

```
xfreerdp3 /u:"$WIN_USER" /p:"$WIN_PASS" /v:127.0.0.1:3389 -grab-keyboard /sound /microphone /clipboard \
  /cert:ignore /title:"Windows VM - Omarchy" /w:<monitor_width> /h:<monitor_height> /dynamic-resolution /gfx:AVC444 /f
```

(`<monitor_width>`/`<monitor_height>` from `hyprctl monitors -j` for the focused monitor, same as the script already computes elsewhere for the scale logic.)

## Expected behavior

The Windows VM window should fill the whole window/monitor with actual remote desktop content on launch, matching pre-upgrade behavior, without requiring a manual reconnect or window resize to trigger correct negotiation.

## Steps to reproduce

1. Launch the Windows VM from the app menu (`omarchy-windows-vm launch`) on a Hyprland session with the compositor at a non-100% (or even 100%, this reproduced at 125%) scale.
2. Observe the FreeRDP window opens at the correct outer size, but the visible Windows desktop is confined to a small region in a corner with the rest black.

## System details

- Omarchy 4.0.3-1
- Hyprland 0.56.2-2
- FreeRDP 3.31.1
- Monitor: 2560x1440 @ 1.25x Hyprland scale (dual monitor, both HDMI-A-1 and DP-2 identical)
- GPU: NVIDIA GeForce GTX 1080 Ti (nvidia driver)