## What happened

The stock touchpad bindings in `default/hypr/bindings/media.lua` never fire:

```lua
o.bind_toggle("XF86TouchpadToggle", "Toggle touchpad", "touchpad", { locked = true })
o.bind("XF86TouchpadOn", "Enable touchpad", "omarchy-toggle-touchpad on", { locked = true })
o.bind("XF86TouchpadOff", "Disable touchpad", "omarchy-toggle-touchpad off", { locked = true })
```

Pressing the touchpad hotkey (Fn+F1 on a System76 Serval WS) does nothing — no OSD, no state change, no error.

## Expected

Fn+F1 toggles the touchpad and shows the "Touchpad disabled" / "Touchpad enabled" OSD.

## Cause

Hyprland's `input:resolve_binds_by_sym` defaults to `false`, and with it off the bind on `XF86TouchpadToggle` never matches. Omarchy never sets the option — `grep -rn resolve_binds_by_sym /usr/share/omarchy/` returns nothing — so every install gets the default and the three bindings above are dead out of the box.

Setting it fixes all three immediately:

```lua
hl.config({ input = { resolve_binds_by_sym = true } })
```

## Everything else in the chain is fine

Verified step by step on this machine:

- The EC emits atkbd scancode `f7`/`f8`; systemd's `60-keyboard.hwdb` (`svnSystem76*`) maps both to `touchpad_toggle`.
- The kernel delivers `KEY_TOUCHPAD_TOGGLE` (530) — confirmed by reading `/dev/input/event4` directly.
- Hyprland's live keymap (`xkbcli dump-keymap-wayland`) contains `key <I538> { [ XF86TouchpadToggle ] };`.
- `hyprctl binds` shows the bind registered: `bindld … key: XF86TouchpadToggle`.
- `omarchy-toggle-touchpad` works correctly when run directly (OSD, device disabled, state file written).
- `hyprctl getoption input:resolve_binds_by_sym` → `bool: false / set: false` before, `true` after.
- A `notify-send` probe bound to the same keysym fires on Fn+F1 only when the option is `true`.

## Likely mechanism

`XF86TouchpadToggle` sits at XKB keycode 538 (evdev 530), above the classic 255 keycode ceiling. With `resolve_binds_by_sym = false`, Hyprland matches binds through a keysym→keycode reverse lookup that appears not to reach that range. The low-keycode media binds in the same file — `XF86AudioRaiseVolume` (123), `XF86MonBrightnessUp` (233) — work fine under the same setting.

I have not confirmed this in Hyprland's source, so treat the mechanism as a hypothesis. The behavioural difference itself is reproducible and is what the fix rests on.

## Steps to reproduce

On any laptop whose touchpad hotkey emits `KEY_TOUCHPAD_TOGGLE`:

1. Confirm the key produces keycode 530 (`evtest` on the keyboard's event device).
2. Press the hotkey — nothing happens.
3. `hyprctl eval 'hl.config({ input = { resolve_binds_by_sym = true } })'`
4. Press again — the touchpad toggles and the OSD appears.

## Suggested fix

Ship `resolve_binds_by_sym = true` in Omarchy's Hyprland input defaults, or bind the touchpad keys by keycode instead of keysym.

## System

- Omarchy 4.0.2-1
- Hyprland 0.56.2 (`efb5099`, v0.56.2)
- Kernel 7.1.9-arch1-2
- System76 Serval WS (serw14), Intel Core Ultra 9 275HX
- Intel Arrow Lake-S graphics + NVIDIA RTX 5070 Ti Mobile

(Note: `contributing.md` in the docs still references `omarchy debug --no-sudo --print`, which no longer exists in 4.0.2 — hence the hand-collected details above.)