dhh merged omacom/omarchy#15020 into quattro to stop a second shell from taking over a session lock that another process may still hold. A separate quattro commit, omacom/omarchy@d1a614ce6629, makes lock requests read current lock state directly after a stale binding caused a pre-suspend lock request to do nothing.
greptile-apps[bot] questioned the recovery retry limit. dhh explained that recovery deliberately gives up while another Quickshell or hyprlock remains, accepting a possible orphan behind the compositor's failsafe rather than taking a live lock. The reviewer accepted that tradeoff in omacom/omarchy#15020:discussion_r4241553575. Normal shell restart waits for the previous shell to exit.
