fix(desktop): add macOS settings menu entry (anomalyco#26081)

Co-authored-by: jesse.mahnken <jesse.mahnken@tiefox.de>
(cherry picked from commit 9b30ee2)

Author: 2 people

.opencode/command/sync-upstream.md

@@ -27,9 +27,19 @@ Workflow:
    - never drop local PRO/custom behavior just to make the sync easier
    - do not use destructive git commands
 9. After the batch is applied, run verification:
-   - `bun typecheck` from `packages/opencode`
-   - `bun run test:ci` from `packages/opencode`
-   - if the batch touches SDK generation inputs or SDK package code, also run `./packages/sdk/js/script/build.ts` from repo root
+   - always run `bun --cwd packages/opencode typecheck`
+   - always run `bun --cwd packages/opencode test:ci`
+   - always run `bun lint` from repo root
+   - if the batch touches shared packages, cross-package contracts, schemas, or anything broad, also run `bun typecheck` from repo root
+   - if the batch touches `packages/core`, also run `bun --cwd packages/core test:ci` and `bun --cwd packages/core typecheck`
+   - if the batch touches `packages/ui`, also run `bun --cwd packages/ui test:ci` and `bun --cwd packages/ui typecheck`
+   - if the batch touches `packages/app`, also run `bun --cwd packages/app test:ci`, `bun --cwd packages/app typecheck`, and `bun --cwd packages/app build`
+   - if the batch touches frontend behavior, routes, UI components, or browser-facing contracts, also run `bun --cwd packages/app test:e2e:local`
+   - if the batch touches `packages/sdk/js` or SDK generation inputs, also run `bun --cwd packages/sdk/js build`
+   - if the batch touches `packages/plugin`, also run `bun --cwd packages/plugin build`
+   - if the batch touches `packages/desktop`, also run `bun --cwd packages/desktop build`
+   - if the batch touches storybook or design-system-facing files, also run `bun --cwd packages/storybook build`
+   - if the batch touches CLI packaging/build pipeline code, also run `bun --cwd packages/opencode build`
 10. If verification fails, stop immediately. Do not push. Do not silently revert. Report:
    - which commits were applied
    - where it failed
@@ -46,6 +56,7 @@ Execution rules:
 - Do not create a final commit unless the git operation itself requires it and the batch is valid.
 - If no safe small batch can be identified, explain why and propose the next safest candidate commits.
 - Keep the response focused on: selected commits, conflict decisions, test results, and next batch recommendation.
+- Choose the verification set from the actual changed paths. Prefer more coverage when unsure.
 - Be extremely concise. Prefer fragments over prose.
 - Do not write long explanations, introductions, retrospectives, or motivational text.
 - Keep the final user-facing response under 8 short lines unless there is a blocker or test failure.

packages/desktop/src/main/menu.ts

@@ -23,6 +23,11 @@ export function createMenu(deps: Deps) {
           enabled: UPDATER_ENABLED,
           click: () => deps.checkForUpdates(),
         },
+        {
+          label: "Settings",
+          accelerator: "Cmd+,",
+          click: () => deps.trigger("settings.open"),
+        },
         {
           label: "Reload Webview",
           click: () => deps.reload(),