fix(commands): also catch synchronous throws in command action

`Browser.commands.onCommand`'s `tab` parameter is documented as optional, so
an action that dereferences `tab.*` (e.g. `openSidePanel` reading
`tab.windowId` / `tab.id`) can throw synchronously before returning a
Promise. The previous `.catch` only observed Promise rejections, so a
synchronous throw would still surface as an uncaught error in the background
script.

Wrap the action invocation in try/catch and log+return on synchronous
failure, mirroring the async rejection handling.

Addresses CodeRabbit review on PR #963.

Author: octo-patch

src/background/commands.mjs

@@ -16,7 +16,16 @@ export function registerCommands() {
         // chrome.sidePanel.open() Promise). Keep the call synchronous so the
         // user-gesture context is preserved, but observe the Promise so a
         // rejection does not become an unhandled rejection in the background.
-        const result = menuConfig[command].action(true, tab)
+        // Also wrap in try/catch because Browser.commands.onCommand documents
+        // `tab` as optional, so an action that dereferences tab.* (e.g. the
+        // openSidePanel call) can throw synchronously.
+        let result
+        try {
+          result = menuConfig[command].action(true, tab)
+        } catch (error) {
+          console.error(`failed to run command action "${command}"`, error)
+          return
+        }
         if (result && typeof result.catch === 'function') {
           result.catch((error) => {
             console.error(`failed to run command action "${command}"`, error)