fix(keybinds): SUPER+? never fired — shifted keysym needs SHIFT in the modmask

? is typed as Shift+/, so Hyprland saw mods SUPER+SHIFT with keysym
`question` and the exact-modmask match skipped the `$mod, question`
bind — the keypress fell through to the focused window (caught on the
Latitude, BACKLOG item 26; the menu itself was fine from a terminal).

- keybinds.nix: bind is now `$mod SHIFT, question`.
- rofi.nix prettyKeys collapses "SHIFT + ?" back to "?" so the
  cheatsheet row keeps the documented SUPER + ? label.
- MEMORY.md gotcha: shifted keysyms need SHIFT in mods — invisible to
  eval-tier tests.

Verified: V0 (flake check --no-build); V1 both surfaces (eval'd
settings.bind renders `$mod SHIFT, question, exec, nomarchy-menu
keybinds`; built nomarchy-menu's cheatsheet renders `SUPER + ?`).
V3 queued: SUPER+? on the Latitude after home-update + relogin.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

agent/BACKLOG.md

@@ -25,20 +25,6 @@ next, in what order*.
 *Items 21–26: real-hardware QA findings from the Latitude 5410
 (Bernardo, 2026-07-04) — bugs found on metal outrank the queue.*
 
-### 26. SUPER+? cheatsheet bind never fires on hardware
-Reported (Latitude sweep #2): SUPER+? does nothing — the ? reaches the
-focused terminal. Cause: keybinds.nix binds `$mod, question`, but
-typing ? holds Shift, so Hyprland sees mods SUPER+SHIFT with keysym
-`question` and its exact-modmask match skips a bind declaring SUPER
-only (the "question already implies Shift" comment doesn't hold on
-real input; headless V1/V2 never pressed the key). Fix: `$mod SHIFT,
-question` (user-facing label stays SUPER+?); while there, audit the
-bind list for other shifted keysyms (none today — letters carry
-explicit SHIFT mods). Confirmed bind-only: `nomarchy-menu keybinds`
-from a terminal opens the cheatsheet fine (Latitude, 2026-07-04).
-**Verify:** V1 (rendered bind string in the HM generation); V3 retest
-on the Latitude.
-
 ### 25. swaync text unreadable on summer-day (light-theme contrast)
 Reported: on summer-day, notification/control-centre text is invisible
 (contrast). Root cause (traced 2026-07-04): swaync.nix renders `.body`