### System details

Intel Xeon E-2176M, Intel UHD P630 + NVIDIA Quadro P2000 Mobile, Omarchy 4.0.0-1, bluez 5.87-2

### What's wrong?

If the first Bluetooth pair attempt fails, the panel never pairs that device again.

`omarchy-bluetooth-device pair` ignores a failed `bluetoothctl pair`, then always marks the address trusted:

https://github.com/basecamp/omarchy/blob/quattro/bin/omarchy-bluetooth-device#L33-L38

```bash
pair)
  power_on
  timeout 20s bluetoothctl pair "$address" >/dev/null 2>&1 || true
  trust_device
  timeout 20s bluetoothctl connect "$address" >/dev/null 2>&1 || true
```

The panel then treats `trusted` as already paired. Later clicks only `connect`:

https://github.com/basecamp/omarchy/blob/quattro/shell/plugins/panels/bluetooth/Panel.qml#L276-L279

```qml
function connectDevice(device) {
  if (!device || device.connected) return
  if (device.paired || device.bonded || device.trusted) runDeviceAction(device, "connect", "connecting")
  else runDeviceAction(device, "pair", "connecting")
}
```

Known devices are `paired || bonded || trusted`, and that list is labeled **PAIRED**:

https://github.com/basecamp/omarchy/blob/quattro/shell/plugins/panels/bluetooth/Model.js#L111-L112

BlueZ **Trusted** is not a bond. After a failed pair the device looks remembered, and connect cannot succeed.

Hit this with a Logitech MX Master 2S (BLE HID). `bluetoothctl info` after using the panel:

```
Paired: no
Bonded: no
Trusted: yes
Connected: no
```

Same trap for any device whose first pair fails (not in pairing mode, timeout, etc.).

**Repro**

1. Super+Ctrl+B, Bluetooth on, wait for scan
2. Click a discovered device that is not actually pairable, or whose pair times out
3. Device moves under **PAIRED**; tooltip on the next click is Connect, not Pair
4. Further clicks never pair
5. `bluetoothctl info <addr>` shows Trusted yes, Paired/Bonded no

**Expected**

- Trust only after pairing succeeds
- If a device is not paired/bonded, the next click should pair, even if it is already trusted
- Do not put trusted-but-unbonded devices under **PAIRED**

**Suggested fix**

- In `pair`, do not `|| true` the pair; only `trust` after `Paired`/`Bonded` is yes
- In `connectDevice()`, pair unless `paired || bonded` — do not use `trusted` as a stand-in
- Keep trusted-unpaired devices visible if wanted, but retry pair instead of connect

Related but different: https://github.com/basecamp/omarchy/discussions/7008 (MX series HID/LE scan). This issue is only the pairing state machine.