### System details

- Omarchy Quattro 4.0.0
- Kernel: `7.1.8-arch1-3`
- Hyprland: `0.56.2`
- Aquamarine: `0.14.0`
- Machine: Apple Mac mini (Late 2014), DMI product `Macmini7,1`
- GPU: Intel Haswell ULT integrated graphics, `i915`, device ID `0a2e`
- One external LG UltraFine 23.7-inch 4K display over Thunderbolt/DisplayPort, exposed as `DP-2`

### What's wrong?

With Omarchy's default catch-all monitor rule:

```lua
local omarchy_monitor_scale = "auto"
hl.monitor({ output = "", mode = "preferred", position = "auto", scale = omarchy_monitor_scale })
```

the machine boots normally and the text console is visible, but the LG display becomes illuminated black when the graphical session starts after login. Hyprland itself starts and can be reached from another TTY. This reproduced on graphical login until an explicit monitor mode was configured.

This looks complementary to #6668 and the recovery merged in #6701:

- #6668 handles a connected monitor with no modes, reported as `width=0 height=0`.
- Here the output has a nonzero mode and Hyprland considers it enabled, so `omarchy-hyprland-monitor-modeless` considers it healthy, but the physical display is black.

After recovering with an explicit rule, `hyprctl monitors all -j` reports:

```json
{
  "name": "DP-2",
  "description": "LG Electronics LG UltraFine 006NTVS8J151",
  "width": 3840,
  "height": 2160,
  "refreshRate": 29.998,
  "scale": 2,
  "dpmsStatus": true,
  "disabled": false,
  "currentFormat": "XRGB8888",
  "availableModes": [
    "[email protected]",
    "[email protected]",
    "[email protected]",
    "[email protected]",
    "[email protected]",
    "[email protected]"
  ]
}
```

The mode list begins with 4K at 49.99 Hz. I have not yet captured an `AQ_TRACE` log from the failing session to prove exactly which mode `preferred` selected or whether the DRM commit returned an error.

Both of these explicit modes produce a visible desktop:

```lua
hl.monitor({ output = "", mode = "1920x1080@60", position = "auto", scale = 1 })
```

```lua
local omarchy_monitor_scale = 2
hl.monitor({ output = "", mode = "3840x2160@30", position = "auto", scale = omarchy_monitor_scale })
```

The second rule is the current working configuration: 4K at approximately 30 Hz with scale 2.

The Hyprland shared-library versions match, `ldd` reports no missing libraries, and the kernel initializes `i915` without an obvious GPU crash in the standard boot log. Limine and the text console work normally.

### Expected behavior

If the preferred mode cannot produce a visible output, the session should fall back to another advertised mode, or Omarchy should provide a TTY-safe recovery path for an output that DRM/Hyprland reports as active but is physically black.

A global replacement of `preferred` would be undesirable. Possible Omarchy-level improvements could be:

- document the explicit-mode recovery procedure in the Intel Mac/monitor documentation;
- provide an `omarchy hyprland monitor safe` command usable from a TTY;
- detect persistent Aquamarine output-commit errors and retry a lower mode;
- if DRM falsely reports success, consider a narrowly targeted hardware quirk rather than changing defaults for all displays.

I can collect a failing `AQ_TRACE`/DRM trace if needed, while keeping the known-good 4K30 rule available for recovery.