Remap any shortcut in Settings → Keyboard; the macOS menu bar follows

A Keyboard section in the Settings window edits the shared keymap: rows
by group with a search field, a chip per key (x removes), + to record,
reset per row and Reset all. Recording takes the keydown before every
other key in the window (Cmd+W records instead of closing), refuses
reserved combos without preventDefault (Cmd+Q still quits), requires a
chord or F-key for editor commands, and offers Replace when another
command in an overlapping scope owns the key. Rows flag conflicts and
plain character keys that would stop starting a type-to-filter query.
Fixed keys are listed read-only, in the platform's spelling.

Remaps are ordinary settings (only rows that differ from the defaults),
so every window, the menu hints and the tooltips follow live — and the
macOS menu bar: its accelerators are built from the keymap (only the
combos Electrobun's parser expresses faithfully) and rebuilt on a remap.
A main-window menu action fired from the editor or Settings window
brings the main window forward first.

Also: the "Enter / double-click on a file" setting under File list (do
nothing / open local files in their default app), arrow keys in the
Settings sidebar with focus on open and a hand-walked Tab, translations
for all seven languages (the spec now checks every language labels every
command), and a README shortcut table generated from the keymap.

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

docs/gotchas.md

@@ -311,6 +311,14 @@ touching the adjacent code.
   path bar) hides keys from it — don't add one.
 - **Hold-to-repeat** fired ⌘W once per repeat — every tab closed. `claim()`
   repeats only movement-like commands (`isRepeatable`).
+- **Electrobun's native menu accelerator turns a combo with no modifier token
+  into ⌘+key** ("f7" shows and fires ⌘F7), its `backspace` / `delete` tokens
+  are characters AppKit matches unreliably, and AppKit matches Shift+punctuation
+  by the shifted character ("}" for ⇧]). `toAccelerator` returns null for all of
+  those; the menu item then shows no key and the page still handles it.
+- **Recording a key must take the keydown before every window handler** — and
+  must NOT take reserved ones: preventDefault on ⌘Q while recording would make
+  the app unquittable from the keyboard.
 - **Focus after a state change needs `afterNextRender({ injector })`.** Under
   zoneless CD `queueMicrotask` runs before the render that creates an `@if`
   element (the editor's find box and textarea), so `.focus()` hit nothing.