[Bug]: Update > Lost all connections; pairing failed; MX Master + Litra

### Pre-flight checklist

- [x] I searched [existing issues](https://github.com/AprilNEA/OpenLogi/issues?q=is%3Aissue) and this is not a duplicate.
- [x] I am on the [latest release](https://github.com/AprilNEA/OpenLogi/releases/latest) or a recent `master` build.
- [x] I quit **Logi Options+** before running OpenLogi (the two apps fight over HID++ access and only one can own a receiver at a time).

### Which part of OpenLogi?

GUI (desktop app)

### OpenLogi version

0.6.22

### Operating system

macOS

### OS version & architecture

macOS Tahoe 26.5.2 (25F84)

### Device model

MX Master Bluetooth and wired

### How is the device connected?

Wired (USB cable)

### Affected area(s)

- [x] Device discovery / detection
- [ ] Button remapping
- [ ] DPI control
- [ ] SmartShift
- [ ] Per-application profiles
- [ ] Battery status
- [ ] Settings / configuration (TOML)
- [ ] Auto-update
- [ ] Menu bar / tray
- [ ] Other

### What happened?

Every time I go to add a device it shows below

These were working with the prior version 0.5.x and were visible.

Now they're not, they're both wired- the mouse is also available via bluetooth

* I made sure that OpenLogi and the OpenLogi agent have correct permissions

I was forced to manually add the permissions to the Bluetooth permissions pane (it was _unknonwn)_

### Steps to reproduce

1. Launch OpenLogi
2. No devices
3. Go to Add a device
4. Sit forever

After cancelling:

5. Paring failed.

Happy to give logs and more if needed.

### Diagnostics report

```markdown

```

### `openlogi list` output

```text

```

### Logs

```shell

```

### macOS permissions (if applicable)

- [ ] OpenLogi has **Accessibility** permission (needed to remap buttons via the event tap).
- [ ] OpenLogi has **Input Monitoring** permission (needed for Bluetooth-direct devices and capture).

Start by reproducing the issue on macOS through the GUI's Add a device flow with the MX Master and Litra connected, then collect the diagnostics report, `openlogi list` output, and logs requested in the issue. Trace device discovery and pairing until the failure is located; done means both devices are detected and pairing completes instead of waiting indefinitely.

Written by the indexing model from the issue text.