**What happened:** Plugged in AC power; `upower`/sysfs correctly report `state: charging`, but the Omarchy bar's battery icon and label show a non-charging state instead.

**Expected:** Bar icon reflects the actual `charging` state from UPower.

**Root cause (found in source):** `plugins/panels/power/Model.js`, `chargeThresholdActive()` overrides the real charging state whenever `time to full >= 8 hours` (or `changeRate <= 0.2W`), assuming this means a health-based charge-threshold pause. `batteryIcon()`/`modeLabel()` then render non-charging icons and the label 'Threshold' — even when `device.state === Charging`. There's no fallback distinguishing 'genuinely paused near a threshold' from 'just charging very slowly / bad estimate'.

**Steps to reproduce:** Have a battery with an unreliable time-to-full estimate (e.g. `energy-full` misreported far above `energy-full-design`, which can happen with an uncalibrated/miscalibrated battery), plug in AC. Bar shows a non-charging icon despite `upower -i` reporting `state: charging`.

**System details:**
- Omarchy version: 4.0.2-1
- `upower -i` excerpt: `state: charging`, `energy-full: 654.75 Wh`, `energy-full-design: 45.8 Wh`, `time to full: 27.4 hours`

**Secondary issue found while investigating:** `omarchy debug` is advertised in `omarchy --help` (and has its own command group), but running it returns 'Unknown Omarchy command: omarchy debug' — the dispatcher doesn't wire it up, even though the underlying `/usr/bin/omarchy-debug` binary works fine when invoked directly.