[Bug]: Back button doesn't go back in macos

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

### Operating system

macOS

### OS version & architecture

Golden Gate, 27 beta 6, ARM

### Device model

MX MASTER 3S

### How is the device connected?

Bluetooth (direct, no receiver)

### Affected area(s)

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

### What happened?

The back button is configured with MouseBack:

But it keeps opening MISSION CONTROL. If I set other action, such as play/pause/ mute.. every other action works just fine, but mouseBack do not.

### Steps to reproduce

1 . Install openlogi via homebrew
2. Launch and confire mx master 3s
3. Test the mouseback and mouseforward buttons, the back one doesn't go back, keep opening mission control.

### Diagnostics report

```markdown
### OpenLogi Diagnostics

**App**
- OpenLogi (GUI): v0.7.4 (release)
- Agent: v0.7.4 (connected)
- IPC protocol: GUI 23 / agent 23
- Inventory: ready
- OS: macOS 27.0 (arm64)
- Locale: en-BR (UI: follow system)
- Accessibility: granted · Input hook: installed
- Launch at login: yes · Menu bar: no · Update check: off
- Running from: source build (dev)
- Config: schema 4 · 1 configured device(s) · thumbwheel 14

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

**Devices (1)**
- MX Master 3S — mouse (codename: MX Master 3S)
- Connection: Bluetooth (direct) · Online: yes · Battery: 95% (discharging, full)
- Capabilities: buttons=yes, pointer=yes, lighting=no
- Model: 0b034 (model-ids: b034/0000/0000, ext-model: 00)
- Transports: BTLE
- Render: mx_master_3s · direct
```

### `openlogi list` output

```text
MX Master 3S (—, vid=046d pid=b034)
└─ slot 255 ● MX Master 3S (mouse, wpid=?, battery=95% full (discharging))
model_ids=[b034,0000,0000] ext=00 serial=2434ZBL7QDG8 unit_id=327274ce transports=btle
```

### Logs

```shell
OPENLOGI_LOG=debug /Applications/OpenLogi.app/Contents/MacOS/OpenLogi
2026-08-22T17:34:09.065622Z DEBUG openlogi_hid::channel::transport: logitech HID node name=MX Master 3S pid=b034 usage_page=0x0001 usage_id=0x0002 matched=false
2026-08-22T17:34:09.065734Z DEBUG openlogi_hid::channel::transport: logitech HID node name=MX Master 3S pid=b034 usage_page=0x0001 usage_id=0x0001 matched=false
2026-08-22T17:34:09.065751Z DEBUG openlogi_hid::channel::transport: logitech HID node name=MX Master 3S pid=b034 usage_page=0xff43 usage_id=0x0202 matched=true
2026-08-22T17:34:09.065763Z DEBUG openlogi_hid::inventory: HID++ candidate interfaces count=1
2026-08-22T17:34:09.076821Z DEBUG openlogi_hid::channel::transport: opened HID++ channel name=MX Master 3S vid=046d
2026-08-22T17:34:10.117152Z DEBUG openlogi_hid::inventory::probe: BT-direct / wired device recognised os_name=MX Master 3S name=MX Master 3S
MX Master 3S (—, vid=046d pid=b034)
└─ slot 255 ● MX Master 3S (mouse, wpid=?, battery=95% full (discharging))
model_ids=[b034,0000,0000] ext=00 serial=2434ZBL7QDG8 unit_id=327274ce transports=btle
```

### macOS permissions (if applicable)

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

Start by reproducing the issue on macOS with an MX Master 3S over Bluetooth, using the reported MouseBack and MouseForward mappings. Trace the desktop button-remapping and event-tap handling to find why MouseBack opens Mission Control; done means the back button navigates back while the other reported actions continue to work.

Written by the indexing model from the issue text.