## System details

```text
Omarchy: 4.0.2-1
Kernel: 7.1.9-arch1-2
Hyprland: 0.56.2
CPU: AMD Ryzen 7 9800X3D
GPU: NVIDIA GeForce RTX 4090, driver 610.57.04
hyprmoncfg: 1.16.1-2
Omarchy shell plugin: crmne.hyprmoncfg 2.1.0
Monitors: DP-1 WAM G274K, DP-3 Dell AW3225QF
hyprctl plugin list: no plugins loaded
hyprctl configerrors: clean
hyprmoncfg doctor: OK, hyprmoncfg monitor file loads last
Diagnostics: /tmp/omarchy-debug.log generated with /usr/bin/omarchy debug --no-sudo --print
```

## What's wrong?

hyprmoncfg correctly generates workspace monitor rules, but Omarchy's default whole-workspace move bindings can move a workspace away from its assigned monitor.

Configured/generated workspace rules:

- Workspaces 1,2,3,7,8,9 -> Dell AW3225QF / DP-3
- Workspaces 4,5,6 -> WAM G274K / DP-1

Generated config:

```lua
hl.workspace_rule({ workspace = "1", monitor = "desc:Dell Inc. AW3225QF 2PKZXZ3", default = true, persistent = true })
hl.workspace_rule({ workspace = "4", monitor = "desc:WAM G274K 0000000000000", default = true, persistent = true })
```

Relevant default Omarchy bindings:

```lua
o.bind("SUPER + SHIFT + ALT + LEFT", "Move workspace to left monitor", hl.dsp.workspace.move({ monitor = "l" }))
o.bind("SUPER + SHIFT + ALT + RIGHT", "Move workspace to right monitor", hl.dsp.workspace.move({ monitor = "r" }))
o.bind("SUPER + SHIFT + ALT + UP", "Move workspace to up monitor", hl.dsp.workspace.move({ monitor = "u" }))
o.bind("SUPER + SHIFT + ALT + DOWN", "Move workspace to down monitor", hl.dsp.workspace.move({ monitor = "d" }))
```

Steps to reproduce:

1. Configure workspace monitor assignments with hyprmoncfg.
2. Assign workspace 1 to the left/Dell monitor and workspace 4 to the right/WAM monitor.
3. Focus workspace 1.
4. Press `SUPER+SHIFT+ALT+RIGHT`.

Actual result:

Workspace 1 moves from DP-3 to DP-1, even though workspace 1 is assigned to DP-3 by the generated hyprmoncfg workspace rule. `hyprctl workspacerules -j` still shows the correct rule, so the saved/generated configuration did not change.

Expected result:

Omarchy should either avoid exposing whole-workspace monitor move bindings when workspace monitor assignment is managed by hyprmoncfg, or make the behavior clearer/protected so assigned workspaces are not accidentally moved off their configured monitors.

Additional checks:

- `hyprctl plugin list` reports `no plugins loaded`.
- `hyprctl configerrors` is clean.
- `hyprmoncfg doctor` reports that `~/.config/hypr/hyprland.lua` loads `~/.config/hypr/hyprmoncfg-monitors.lua` last.
- Moving a window silently to workspace 7 with `SUPER+SHIFT+ALT+7` respects the workspace rule and places it on DP-3.
- The issue appears specific to the whole-workspace monitor move bindings, not normal window-to-workspace movement.

Diagnostics note:

The documented diagnostic command is `omarchy debug --no-sudo --print`, but on this system `command -v omarchy` resolves to `/usr/share/omarchy/bin/omarchy`, and that wrapper returns:

```text
Unknown Omarchy command: omarchy debug --no-sudo --print
```

Running `/usr/bin/omarchy debug --no-sudo --print` works and writes `/tmp/omarchy-debug.log`.