[BUG]: ghost_movement corrupts workspace state after Win+D + single-window restore

With animation.ghost_movement: true, pressing Win+D (Show Desktop) corrupts the workspace state: minimized windows stay in the layout as tiled containers with their minimized parking coordinates (-32000, -32000). Restoring a single window from the taskbar then tiles it into a fraction of the screen, as if it were sharing the workspace with the phantom containers.

Same steps with ghost_movement: false work correctly: minimized windows are removed from the workspace and the restored window takes the full workspace.

Environment: nightly 0.1.42 (commit ccb39abd, 2026-07-05 MSI), Windows 11 Pro 25H2 (26200), single 5120x1440@144Hz monitor, window_hiding_behaviour: "Cloak", BSP, animation EaseOutCubic 200ms fps 120.

Repro:

1. 3-4 tiled windows on a workspace (mine included Discord, Chrome, WezTerm, File Explorer)
2. Win+D
3. Restore one window from the taskbar

komorebic state after step 3 (only Discord restored, wezterm-gui dropped out of the workspace entirely):

chrome.exe   {'left': -31993, 'top': -32000, 'right': 146, 'bottom': 21}
Discord.exe  {'left': 2562, 'top': 42, 'right': 2556, 'bottom': 672}
explorer.exe {'left': -31993, 'top': -32000, 'right': 146, 'bottom': 28}

The workspace stays broken until every window is restored manually and komorebic retile is issued.

Log lines around the sequence:

ERROR komorebi::com: could not get view for hwnd 9635842 due to os error: The requested lookup key was not found in any active activation context. (os error 14007)
ERROR komorebi::com: no view was found for 9635842
WARN  komorebi::reaper: error reaping orphan window (9635842) on monitor: 0, workspace: 1. Error: there is no window
WARN  komorebi::reaper: restarting failed thread: Invalid window handle. (0x80070578)
ERROR komorebi::process_event: there is no container/window

Happy to test builds — ghost movement is a huge improvement for heavy Chromium windows otherwise.