## System details

AMD Ryzen AI MAX+ 395 (Radeon 8060S / Strix Halo, RADV), ASUS ProArt PA32QCV (6K) on DP-4, Omarchy 4.0.0-1, single monitor, no fingerprint.

## What's wrong?

After the idle lock blanks the display, waking it is nearly unusable on this monitor:

1. Screen locks (idle or manual), display blanks ~5s later — expected, per `plugins/lock/Service.qml` `idleBlankTimer` (hardcoded `interval: 5000`).
2. Pressing a key wakes the display, but the password prompt is visible for only **~1 second** before the display goes dark again.
3. Repeating input repeats the 1-second flash. The input path itself works fine: typing the password blind and pressing Enter unlocks normally.

This panel takes ~4s to resync a 6K DP signal after DPMS off, so whatever re-blanks it leaves effectively no usable window.

## What I ruled out

I cloned `omarchy.lock` and raised `idleBlankTimer.interval` from 5000 to 30000. **The symptom did not change** — the display still went dark ~1s after each wake. So the re-blank does not appear to come from the lock plugin's blank timer at all (every keystroke re-arms it via `wakeRequested` anyway).

Remaining suspects on the wake path:

- `omarchy-brightness-display on` skips the DPMS enable dispatch when `hyprctl monitors -j` reports all displays `dpmsStatus: true`. If that status flips true before the panel has actually resynced (e.g. Hyprland enabling DPMS itself on key press), the guard may be masking a failed/incomplete enable.
- 6K-over-DP link retraining after DPMS wake: the panel briefly shows a picture, then loses link and drops back to sleep — consistent with a modeset race rather than a deliberate blank.

## Timeline from journal (idle lock at 11:45, wake+unlock at 11:50)

```
15:45:36.704Z idle  lock-system: lock-timeout
15:45:36.780Z lock  lock-requested
15:45:37.303Z lock  secure=true
15:50:36.052Z idle  idle-cycle-cancel: activity   <- first key press, omarchy-system-wake runs
15:50:45.060Z lock  unlocked                      <- 9s of blind typing later
```

## Steps to reproduce

1. Omarchy 4 with a monitor that is slow to resync after DPMS off (large 6K/DSC panels).
2. Lock and wait for the display to blank.
3. Press a key: prompt appears for ~1s, display goes dark again.
4. Type the password blind: unlock succeeds, confirming only the display path is broken.

## Suggestions

- Make the lock blank delay configurable (the 5000ms in `plugins/lock/Service.qml` is hardcoded), though per the above that alone does not fix this.
- Re-examine the `dpmsStatus` skip-guard in `omarchy-brightness-display on` for staleness during wake, and consider not blanking at all while the password buffer is non-empty.