Power-profile migration finishes outside a graphical login unless the package swap or daemon restart fails
A change merged into quattro lets the power-profiles migration finish when polkit denies a profile switch outside a graphical login. A failed package swap or daemon restart still stops the migration.
Until this change, the migration ended by applying the power profile with omarchy-powerprofiles-set autodetect. Switching a profile needs polkit's active-session grant, which an update has only from inside a graphical login.
Over SSH, or on a machine nobody is logged into, polkit denies the switch and the setter exits non-zero. Before the change, the migration then failed after the package swap had already happened, and that pending migration stopped every migration queued behind it.
The profile does not need to be applied in the migration. omarchy-powerprofiles-init runs at every login, and it runs the same autodetect. The migration reports that the switch is deferred and finishes.
The pull request says that on a stock install over SSH it exits 0 with omarchy-power-profiles-daemon installed and the daemon running, where it exited 1. The change edits the shipped migration rather than adding another, because migrations run strictly in order and a machine where this one failed still has it pending.