macOS app: don't route menu commands through your keyboard-shortcut guard

A common pattern for app-level shortcuts in a macOS app that hosts a webview: let the key through when an editable element inside the webview has focus, so typing isn't hijacked. If the menu-bar item and command palette call the same 'perform from shortcut' function, they inherit that guard. After the user types in any search box inside the webview, every click on the menu item just plays NSSound.beep(), and nothing explains why. Give explicit invocations (menu, palette) their own path without the editable-focus guard. When a command really has no target, show a short message instead of a bare beep.