[Bug]: MX Ergo S not detected in Windows 11

### 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.8.3

### Operating system

Windows

### OS version & architecture

Windows 11 Home 23H2, amd64

### Device model

MX Ergo S, Logi Bolt Receiver

### How is the device connected?

Logi Bolt receiver

### 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?

OpenLogi is unable to detect my MX Ergo S on Windows. I've seen it detect once, and then it vanished and never again. The same device works fine on my Mac.

Logi Options+ used to be installed, but I've cmpletely uninstalled it and have rebooted several times since then.

### Steps to reproduce

Use Win11
Uninstall Logi+
Install OpenLogi
Have MX Ergo S

### Diagnostics report

```markdown
### OpenLogi Diagnostics

**App**
- OpenLogi (GUI): v0.8.3 (release)
- Agent: v0.8.3 (connected)
- IPC protocol: GUI 29 / agent 29
- Inventory: ready
- OS: Windows (x86_64)
- Locale: en-US (UI: follow system)
- Accessibility: granted · Input hook: installed
- Launch at login: yes · Menu bar: yes · Update check: on
- Running from: source build (dev)
- Config: schema 7 · 1 configured device(s) · thumbwheel 14

**Assets**
- Source: user cache · Index: loaded (210 models) · User cache: present
- Cache path: C:\Users\dfras\.local/share/openlogi\assets · Bundle assets: absent

**Devices (0)**
- No devices detected.
```

### `openlogi list` output

```text
PS C:\Users\dfras> openlogi list
(inventory read from the running agent)
No Logitech HID++ devices or webcams found.

Notes:
- On macOS, quit Logi Options+ first — both apps fight over HID++ access.
- A Bluetooth-direct mouse (e.g. Lift, Signature) needs Input Monitoring permission: System Settings → Privacy & Security → Input Monitoring.
- hidpp 0.2 only recognises Logi Bolt receivers (PID 0xC548); other receivers (Unifying) aren't surfaced yet.
PS C:\Users\dfras>
```

### Logs

```shell
PS C:\Users\dfras> set OPENLOGI_LOG=debug
PS C:\Users\dfras> openlogi
(no agent reachable — reading hardware directly; macOS judges this process's Input Monitoring grant, not the agent's)
2026-09-08T00:28:20.447595Z WARN openlogi_device::inventory: device probe timed out — treating as a failed probe budget=13s receiver=true
2026-09-08T00:28:33.865047Z WARN openlogi_device::inventory: device probe timed out — treating as a failed probe budget=13s receiver=true
2026-09-08T00:28:33.865177Z WARN openlogi_device::inventory: node probe keeps failing — retiring its channel before reopen
2026-09-08T00:28:47.730186Z WARN openlogi_device::inventory: device probe timed out — treating as a failed probe budget=13s receiver=true
2026-09-08T00:28:47.730291Z WARN openlogi_device::inventory: node probe keeps failing — retiring its channel before reopen
No Logitech HID++ devices or webcams found.

Notes:
- On macOS, quit Logi Options+ first — both apps fight over HID++ access.
- A Bluetooth-direct mouse (e.g. Lift, Signature) needs Input Monitoring permission: System Settings → Privacy & Security → Input Monitoring.
- hidpp 0.2 only recognises Logi Bolt receivers (PID 0xC548); other receivers (Unifying) aren't surfaced yet.
PS C:\Users\dfras>
```

### 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 Windows 11 with an MX Ergo S and Logi Bolt receiver, using `openlogi list` and the debug logging shown in the report. Investigate the device-discovery path based on the receiver probe timeouts and confirm that the device is detected reliably; done means it appears in inventory and `openlogi list`.

Written by the indexing model from the issue text.