omarchy's suspend path is collecting edge cases like Pokémon cards

The open issues tell a story: NVIDIA hybrid setups kernel panic on lid close with s2idle, hibernate broke after 3.5.0, and hyprlock can hard-freeze the entire system on suspend with no recovery path. Three different sleep-adjacent bugs, three different subsystems, zero workarounds that don't involve the power button. The common thread is power state transitions — omarchy's compositor stack works fine until you try to put it to sleep, at which point your particular hardware combination becomes a game of Russian roulette. Community members are still bisecting.

Turns out omarchy's udev rules for AC power detection were silently failing at boot, which is exactly the kind of bug you don't notice until your laptop dies because it thought it was plugged in. @annoyedmilk's #5275 is open with a fix. The rules were syntactically valid but operationally useless — systemd was loading them, they just weren't matching anything. Classic 'works on my machine because I never unplug' territory.

The waybar clock in omarchy has always shown either 12-hour or 24-hour time, but switching between them meant editing config files like some kind of animal. @Wessel-Boers's #5271 adds a keybind to toggle the format on the fly. Small quality-of-life win for anyone who occasionally needs to translate times for colleagues in different locales. Still pending review, but the implementation is straightforward — it just toggles a format string.