### System details

Dell XPS 14 DA14260 (2026, Intel Core Ultra X7 358H, Panther Lake), BIOS 1.3.1, Omarchy 4.0.4, linux-omarchy 7.2.5-3, power-profiles-daemon 0.30-1

### What's wrong?

When the current profile is Performance, picking Power Saver in the battery panel or the Power profile menu ends on Balanced. The daemon reports `power-saver`, then about 0.1 s later moves itself to `balanced`. The panel highlights Balanced on its next refresh.

`omarchy-powerprofiles-set` saves the profile that was asked for, not the one the daemon ended on. So the state file says `power-saver` while the laptop runs Balanced. The bounce also hits the automatic restores. With Omarchy's default AC profile of Performance and Power Saver saved for battery, unplugging runs Performance → Power Saver again, which bounces again and stays on Balanced. Power Saver only sticks when the switch starts from Balanced.

Steps:
1. Pick Performance in the battery panel.
2. Pick Power Saver.
3. `powerprofilesctl get` → `balanced`. `cat ~/.local/state/omarchy/powerprofiles/battery` → `power-saver`.

I tested the battery panel, the Power profile menu (`autodetect`), `omarchy-powerprofiles-set battery|ac` as the battery service runs it on plug/unplug, and `omarchy-powerprofiles-init`, with all three profiles. The only switch that fails is Performance → Power Saver. Balanced → Power Saver, Power Saver → Performance and the switches to Balanced all stick.

The cause is in power-profiles-daemon, not Omarchy. It happens with a plain `powerprofilesctl set power-saver` straight after `powerprofilesctl set performance`. The XPS 14 registers two platform-profile handlers whose choices don't overlap below balanced:

```
platform-profile-0  SoC Power Slider  low-power balanced performance
platform-profile-1  dell-pc           cool quiet balanced performance
/sys/firmware/acpi/platform_profile_choices  →  balanced performance
```

With no `low-power` offered, the daemon writes `balanced` to the firmware for Power Saver. Coming from Performance that is a real firmware change, and the daemon seems to take the firmware's change notification as a new choice of Balanced. I'll report it to power-profiles-daemon and link it here.

### Possible fix on the Omarchy side

Going through Balanced first avoids it. Starting from Performance, `powerprofilesctl set balanced` followed by `powerprofilesctl set power-saver` sticks every time. I tested it with no pause, 0.2 s and 0.5 s in between. Every caller (panel, menu, the battery service's plug/unplug restore and `omarchy-powerprofiles-init`) goes through `omarchy-powerprofiles-set`, so one change there covers all of them. Placed just before `powerprofilesctl set "$profile" || exit`:

```bash
# power-profiles-daemon 0.30 bounces performance → power-saver back to balanced
# on some machines (Dell XPS 14); performance → balanced → power-saver sticks.
if [[ $profile == power-saver ]] && profile_available balanced &&
   [[ $(powerprofilesctl get 2>/dev/null) == performance ]]; then
  powerprofilesctl set balanced || true
fi
```

On machines without the bug, this only adds a brief Balanced step to that one switch. I've worked around it locally with a user service that sets Power Saver again after the bounce, but a fix in the setter would be simpler.

Related but different: #12734 (saved battery profile not applied when booting on battery).