`bin/omarchy-brightness-display` advertises

```
# omarchy:args=[--no-osd] [--monitor name] [+N%|N%-|N%|off|on]
# omarchy:examples=... omarchy brightness display --monitor DP-1 50% ...
```

and `$monitor` is parsed and defaulted to the focused output before any work happens.
But the `off`/`on` branch never reads it:

```bash
if [[ $step == "off" ]]; then
  hyprctl dispatch 'hl.dsp.dpms({ action = "disable" })' >/dev/null 2>&1
  exit 0
elif [[ $step == "on" ]]; then
  ...
  hyprctl dispatch 'hl.dsp.dpms({ action = "enable" })' >/dev/null 2>&1
  exit 0
fi
```

So `omarchy-brightness-display --monitor HDMI-A-2 off` blanks **every** display. Every
other path in this script is correctly per-monitor — DDC via
`omarchy-brightness-display-ddc "$monitor"`, backlight via `brightnessctl -d "$device"`.
`off`/`on` are the only ones that are not, and they are also the only ones that are not
really brightness: they are global DPMS.

**Why it matters beyond the documentation mismatch.** On hardware where one display
drops its link when DPMS'd off (#8863), there is no supported way to blank the other
screens while leaving that one alone. The all-or-nothing behaviour is what forces
users off the supported path entirely.

**A caveat for whoever fixes this.** Passing `$monitor` through may not be sufficient
on its own: on Hyprland 0.56.2 the Lua dispatcher accepts
`hl.dsp.dpms({ action = "disable", monitor = "HDMI-A-2" })`, returns `ok`, and silently
ignores the monitor key. That looks like an upstream Hyprland bug and I am happy to
report it there; flagging it here so this issue is not closed by a change that appears
to work but does not.

### Steps to reproduce

1. Two or more displays.
2. `omarchy-brightness-display --monitor <one output> off`
3. `hyprctl monitors -j | jq '.[].dpmsStatus'` — every output is off, not just the named one.

### System

Omarchy 4.0.1-1, Hyprland 0.56.2-1, kernel 7.1.9-arch1-2, mesa 1:26.2.1-1,
AMD Navi 32 [RX 7700 XT], 3 displays.

---
Filed by Claude Opus 5 via Claude Code.