## What happened

While my laptop was sitting at the lock screen discharging through the low-battery range, the shell sent **"Time to recharge!" every ~3.2 seconds, continuously, for 14 minutes** — ~260 critical notifications between 14:11 and 14:25 (10% down to 3%), until the machine died.

Notification state files (one per popup, timestamped) show the cadence:

```
14:11:45 +  0.0s Time to recharge! | Battery is down to 10%
14:11:50 +  4.2s Time to recharge! | Battery is down to 10%
14:11:53 +  3.3s Time to recharge! | Battery is down to 10%
...continues every ~3.2s through 10% → 9% → 8% → ... → 3%...
14:25:29 +  3.0s Time to recharge! | Battery is down to 3%
```

## Root cause

The journal shows the AC adapter's reported online status was **flapping every ~3.2 seconds** during the same window (UCSI/PD trouble at critical charge — `ucsi_acpi USBC000:00: unknown error 256`). The ACAD udev events alternate between the plugged and unplugged rules at that cadence:

```
14:11:52 (udev-worker): ACAD: ... omarchy-wifi-powersave off' failed with exit code 1.
14:11:52 (udev-worker): ACAD: ... omarchy-wifi-powersave on' failed with exit code 1.
14:11:53 kernel: ucsi_acpi USBC000:00: unknown error 256
14:11:55 (udev-worker): ACAD: ... omarchy-wifi-powersave off' ...
14:11:55 (udev-worker): ACAD: ... omarchy-wifi-powersave on' ...
```

In `shell/plugins/services/battery/BatteryModel.js`, the notified-latch is recomputed as `notifiedLowBattery: low` on every check:

```js
var low = isDischarging(device, onBattery, dischargingState) && level <= threshold
return { level: level, notify: low && !alreadyNotified, notifiedLowBattery: low }
```

and `Service.qml` calls `checkBattery()` from `onOnBatteryChanged`. So every flap runs two checks: the "on AC" one computes `low = false` and **resets the latch**, and the "on battery" one immediately re-notifies. One critical notification per flap cycle, forever.

Since critical popups never auto-expire (#9361), all ~260 piled up on screen until the battery died. Each flap also re-ran `omarchy-powerprofiles-set` (visible as `omarchy-power-profile.service` start/stop churn every ~3s).

## Expected

One warning per low-battery episode. A momentary blip in `onBattery` / device state should not re-arm the warning.

## Suggested fix

Any (or all) of:
- **Hysteresis on the latch:** only clear `notifiedLowBattery` once the battery is genuinely recovering (level > threshold, or charging state sustained for e.g. 30s) — not on any instant where `low` computes false.
- **Rate-limit** `sendLowBatteryWarning` (e.g. at most once per 5 minutes).
- Pass a **replaces-id** (`-r`) from `omarchy-battery-low` so repeats coalesce into a single popup instead of stacking.

## System

- Framework Laptop 13 (AMD Ryzen 7 7840HS / Radeon 780M)
- Omarchy `4.0.0.r1846.g946704f-1`, quickshell `0.3.1-1`, kernel `7.1.9-arch1-2`

Related: #9361 (critical toasts never expire — the aggravator that made this a wall of popups), #8813 (low-battery toast persists after charger connect).