### System details

Desktop PC with USB/wireless keyboard (Telink Wireless Device), Omarchy 3.4.2

### What's wrong?

The [commit 6ad5d22](https://github.com/basecamp/omarchy/commit/6ad5d225f8bfc38d26850af9d584c4f69d2a2ee8) added a Copilot key → Omarchy Menu remap via makima by shipping the config file:

```
~/.config/makima/AT Translated Set 2 keyboard.toml
```

Makima matches devices by filename — the config filename must match the device name exactly as reported by the kernel. The name `"AT Translated Set 2 keyboard"` only applies to **built-in laptop keyboards and PS/2 keyboards**. On systems with USB or wireless keyboards, the device name is different (e.g. `"Telink Wireless Device"`, `"Genius Wireless Device"`, `"CORSAIR CORSAIR K70 RGB MK.2 Keyboard"`, etc.).

As a result, `makima` silently finds no matching device and the remap never takes effect — pressing the Copilot key does nothing.

## Steps to reproduce

1. Have a desktop PC (or a laptop with an external USB keyboard as the primary keyboard).
2. Apply migration `1772734610.sh` or run `install/config/makima.sh`.
3. Press the Copilot key → Omarchy Menu does **not** open.

You can verify the mismatch by checking:

```bash
cat /proc/bus/input/devices | grep ^N
```

If there is no `"AT Translated Set 2"` device listed, the remap will not work.

## Workaround

Create an additional makima config file named after your actual keyboard device:

```bash
# 1. Find your keyboard name
cat /proc/bus/input/devices | grep ^N

# 2. Create a config matching that name, for example:
cp ~/.config/makima/"AT Translated Set 2 keyboard.toml" \
   ~/.config/makima/"Telink Wireless Device.toml"

# 3. Restart makima
sudo systemctl restart makima
```

After this, `makima` will log `"Telink Wireless Device" detected, reading events.` and the Copilot key will correctly open the Omarchy Menu.

## Suggested Improvement

`install/config/makima.sh` could auto-detect the primary keyboard device name at install time and generate the correct config filename dynamically. For example:

```bash
# Detect keyboard with LEDs support (typical indicator of a "real" keyboard)
KEYBOARD_NAME=$(cat /proc/bus/input/devices | awk '
  /^N:/ { name=substr($0, index($0,"=")+1) }
  /Handlers=.*kbd.*leds/ { print name; exit }
')

if [ -n "$KEYBOARD_NAME" ]; then
  cp "$OMARCHY_PATH/default/makima/AT Translated Set 2 keyboard.toml" \
     "$HOME/.config/makima/$KEYBOARD_NAME.toml"
fi
```

---

## Related issues

- **[#4947](https://github.com/basecamp/omarchy/issues/4947) — Problem with binds after 3.4.2 update**: Reports that keybinding combinations stopped working after 3.4.2. Worth noting that the makima migration (`1772734610.sh`) landed in this same release cycle and could be contributing to the reported bind issues on desktop setups where the Telink/USB keyboard is not being picked up by makima at all. The `GRAB_DEVICE = "true"` setting in the makima config exclusively takes over the matched device — if no device is matched but the service runs, behavior could be unexpected.