## Description

`omarchy-brightness-keyboard off` saves the keyboard-backlight level with
`brightnessctl -s` every time it runs, with no guard against saving `0`. The
lock service can run it more than once per lock cycle, and the second run saves
`0` over the previously-saved good value.

`omarchy-brightness-keyboard restore` (called by `omarchy system wake`) then
faithfully restores `0`, so the keyboard backlight stays off after waking — and
stays off permanently, because nothing rewrites a nonzero value into the save
file. Re-arming the lights by hand does not repair it; the next idle cycle
restores darkness again.

**Expected:** waking after idle restores the keyboard backlight to the level it
was at before blanking.

**Actual:** the backlight stays off after the first double-blank, permanently.

## System

| | |
|---|---|
| Omarchy | 4.0.2-1 |
| Kernel | 7.1.8-arch1-2-ptl |
| Machine | XPS 14 DA14260 |
| CPU | Intel(R) Core(TM) Ultra X7 358H |
| LED device | `dell::kbd_backlight` (max_brightness 2) |
| brightnessctl | 0.5.1-3 |

(`omarchy debug` is not a command in 4.0.2, so no debug log is attached.)

## Steps to reproduce

Reproducible directly, without waiting for the idle cycle:

```console
$ DEV=dell::kbd_backlight; SAVE=$XDG_RUNTIME_DIR/brightnessctl/leds/$DEV
$ brightnessctl -d $DEV set 1
$ cat $SAVE
1
$ omarchy-brightness-keyboard --no-osd off     # saves 1, sets 0
$ cat $SAVE
1
$ omarchy-brightness-keyboard --no-osd off     # saves 0 over the good value
$ cat $SAVE
0
$ omarchy-brightness-keyboard --no-osd restore
$ brightnessctl -d $DEV get
0                                               # expected 1
```

In normal use this is reached through the lock screen: blank the display, then
have the shell re-arm and fire `runBlank()` again without an intervening
`runWake()`.

## Cause

`bin/omarchy-brightness-keyboard:29`

```bash
if [[ $direction == "off" ]]; then
  brightnessctl -sd "$device" set 0 >/dev/null
```

`-s` snapshots the current value before setting `0`. It is unconditional, so
calling `off` while the backlight is already `0` overwrites the saved level
with `0`.

`shell/plugins/lock/Service.qml:172`

```qml
function runBlank() {
  if (!blankProcess.running) blankProcess.running = true
}
```

The only guard is against a concurrent run, not against blanking something
already blank. `armBlankTimer()` is called from four places — `beginLock()`
(:136), `runWake()` (:169), the suspend-gap re-arm inside
`idleBlankTimer.onTriggered` (:424), and `onAuthenticatingPasswordChanged`
(:481) — and only `runWake()` restores brightness first. Any path that re-arms
without waking leads to a second `runBlank()` against an already-dark keyboard.

The display path (`omarchy-brightness-display`) is worth checking for the same
pattern.

## Suggested fix

Make the save conditional in `bin/omarchy-brightness-keyboard`:

```bash
if [[ $direction == "off" ]]; then
  # Only snapshot a level worth restoring; saving 0 over a good value makes
  # `restore` permanently restore darkness.
  if (( $(brightnessctl -d "$device" get) > 0 )); then
    brightnessctl -sd "$device" set 0 >/dev/null
  else
    brightnessctl -d "$device" set 0 >/dev/null
  fi
  exit 0
```

Guarding `runBlank()` on current brightness would also work, but fixing it in
the script covers every caller.

## Notes

Found on a fresh 4.0.2-1 install. The save file was already poisoned (`0`) by
normal use before any manual reproduction.