[Bug]: Windows 11: G305 Lightspeed is detected but not shown in the UI

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

### Operating system

Windows

### OS version & architecture

Windows 11 Pro 25H2 (Build 26200.8973), x64

### Device model

Logitech G305 Lightspeed Wireless Gaming Mouse

### How is the device connected?

Other / not sure

### 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 version
v0.6.23

### OS
Windows 11 Pro 25H2 (Build 26200.8973)

### Device
Logitech G305 Lightspeed Wireless Gaming Mouse (WPID 4074)

### Problem

OpenLogi detects my G305 successfully in the logs, but the mouse never appears in the Devices list.

When I click the "+" button, I immediately get:

Pairing failed
No supported pairing-capable receiver was found.

However, the log shows that the receiver and the mouse are detected correctly.

Relevant log lines:

```text
sweep: slot 1: G305 Lightspeed Wireless Gaming Mouse (Mouse, online, wpid 4074)
sweep: done: 1 receiver(s)/device(s) usable
session: open slot 1 on receiver ls-046dc53f: interface score 1026
```

No ERROR or WARN messages are present.

### Expected behavior

The detected G305 should appear in the Devices list and be configurable.

### Steps to reproduce

1. Start OpenLogi v0.6.23 on Windows 11 Pro 25H2.
2. Connect a Logitech G305 Lightspeed mouse using the original Lightspeed USB receiver.
3. Open OpenLogi.
4. Click the "+" (Add Device) button.
5. The pairing dialog immediately shows "Pairing failed - No supported pairing-capable receiver was found."
6. The Devices list remains empty, although the logs show that the G305 is detected successfully.

### Diagnostics report

```markdown
### OpenLogi Diagnostics

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

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

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

### `openlogi list` output

```text
Not available. The Windows package does not expose the `openlogi` command in PATH.
```

### Logs

```shell
sweep: slot 1: G305 Lightspeed Wireless Gaming Mouse (Mouse, online, wpid 4074)
sweep: done: 1 receiver(s)/device(s) usable
session: open slot 1 on receiver ls-046dc53f: interface score 1026
```

### 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 with a G305 and capture the discovery logs alongside the empty Devices list. Trace how the detected receiver and mouse inventory reaches the GUI and how the "+" pairing flow selects supported receivers. Done means the detected G305 appears in the Devices list and can be configured without the pairing failure.

Written by the indexing model from the issue text.