[Device]: MX Master 4 on bluetooth on macOS Tahoe

### Pre-flight checklist

- [x] I quit **Logi Options+** before testing.
- [x] I searched existing issues for my device.

### Device model

MX Master 4 on Bluetooth

### Connection

Bluetooth (direct, no receiver)

### What's the problem?

Device is not detected at all

### `openlogi list` output

```text
(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.
```

### `openlogi diag features` output

```text

```

### Details

Environment

OpenLogi version: 0.7.1
macOS: Tested on both macOS 26 Tahoe (stable) and macOS 27 beta 7 — same result on both, so not OS-version specific
Device: Logitech MX Master 4
Connection: Bluetooth-direct (paired via macOS System Settings, not via a Logi Bolt USB receiver)

Problem

The MX Master 4 is correctly paired and connected at the macOS level (shows as "Connected" in System Settings → Bluetooth, works fine as a standard mouse — clicks, scrolling, cursor movement all work). However, it never appears in OpenLogi's device list, so none of the Logitech-specific features (buttons, gestures, DPI, Easy-Switch config) can be configured.

Troubleshooting already done

Granted OpenLogi Input Monitoring permission in Privacy & Security, fully quit (Cmd+Q) and relaunched the app afterward
Confirmed the mouse is on the correct Easy-Switch channel for this Mac
Toggled the mouse power off/on to force a fresh HID announce
Reproduced on both macOS 27 beta 7 and, after reverting, on stable macOS Tahoe — same behavior on both, so it doesn't appear to be an OS beta issue

Possible cause

The MX Master 4 is a very new device, and its Bluetooth product ID appears to need explicit allowlisting in HID++ tooling. The Linux kernel recently needed a patch specifically to recognize the MX Master 4 over Bluetooth (product ID 0xb042) before its HID++ features became accessible — see: https://lkml.iu.edu/hypermail/linux/kernel/2603.1/07694.html

My guess is OpenLogi's own device-recognition table may currently only match the MX Master 4's Bolt-receiver product ID, not its separate Bluetooth-direct product ID (0xb042). If that's the case, this might be a quick fix — adding that PID to the Bluetooth device table, similar to the linked kernel patch.

Start at the device-discovery path used by `openlogi list` and locate the Bluetooth HID++ recognition table. Compare its supported product IDs with the MX Master 4 Bluetooth PID `0xb042`, then verify that the device appears in `openlogi list` and that its HID++ features can be inspected.

Written by the indexing model from the issue text.