[Bug]: "Sleep" and "Lock" actions do not work

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

### Device model

MX Anywhere 2S

### How is the device connected?

Logi Bolt 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?

Both Sleep and Lock actions do not work on a work PC with Windows 11 Enterprise. I am not able to inspect what command is actually being sent, but it has no visible action.

### Steps to reproduce

1. Map a button to "Sleep" or "Lock" action
2. Click the button to execute the action

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

No source files, tests, diagnostics, logs, or `openlogi list` output are provided. Start by reproducing the mapped Sleep and Lock actions on Windows 11 Enterprise with the MX Anywhere 2S over a Logi Bolt receiver, then capture diagnostics and logs; done means both actions visibly execute from a remapped button.

Written by the indexing model from the issue text.