KEYBOARD_SHORTCUTS

Every shortcut the editor binds, as data.

This list *is* the binding: the handler below dispatches through it and the keyboard-shortcuts dialog renders from it, so the sheet cannot describe a key the editor does not answer to, and a key added here appears in the sheet without anyone remembering to write it down. The previous arrangement — a switch statement here and a separate list in the dialog — is exactly the shape that drifts.

Tool switches are *not* here. They come from the UI tool list, because that is the list an app's TLUiOverrides.tools can rewrite; useToolShortcuts binds them and the dialog reads the same list.