A Hyprland upgrade skips the reload that raised a config error
An update that upgrades Hyprland and Omarchy's settings together showed a config error banner until a restart, because the reload hit the old binary. A change merged into quattro skips that reload when the running binary was replaced, and leaves errors hidden.
An update that upgrades Hyprland and Omarchy's settings in the same pacman transaction shows a config error banner until Hyprland is restarted. The reload was hitting the old binary, which does not know keys added for the new one. After 0.56 to 0.57, the banner names misc.bell_sound.
When the running compositor's binary was replaced, the resume step skips the reload and leaves autoreload off and errors hidden. Both settings live only in that compositor and go away when the session restarts on the new binary. An update that does not replace Hyprland behaves as before. The pull request merged into quattro.