feat(tasks): Cmd+Option+Left/Right to cycle task tabs

[wise-toddler]

Summary

• Add Cmd+Option+Left / Cmd+Option+Right to cycle through open task tabs in the top tab bar (wrap-around at edges, skips the home tab).
• Suppress the new cycle shortcuts inside text inputs (INPUT, TEXTAREA, SELECT, contentEditable, role="textbox", CodeMirror, xterm, Milkdown, ProseMirror) so they don't hijack the macOS "move by word" cursor behavior.

Closes

Closes #98

Notes on the diff

This branch also includes two small unrelated fixes that the typecheck on main currently fails without:

• fix(transport): add missing resolve-task route stub — registers a 501 stub for the missing module imported by rest-api/index.ts.
• fix(app): add missing ws and @trpc/server deps for host-capability-server — adds runtime deps already used by packages/apps/app/src/main/host-capability-server.ts.

Happy to split these out into a separate PR if preferred.

Test plan

• pnpm typecheck passes
• pnpm --filter @slayzone/app test:e2e e2e/core/16-tab-management.spec.ts — 11/11 pass, including 4 new cases for the shortcuts above.
• Manual: with multiple task tabs open, Cmd+Option+Left and Cmd+Option+Right cycle through them and wrap at the edges.
• Manual: shortcuts do NOT fire while typing in an input, textarea, contentEditable field, CodeMirror editor, xterm terminal, Milkdown/ProseMirror editor, or native <select>.
• Manual: with only the home tab open, the cycle shortcuts are a no-op.

Greptile Summary

This PR adds keyboard cycling for task tabs and a few support fixes. The main changes are:

• New Cmd+Option+Left and Cmd+Option+Right task-tab shortcuts.
• Guarding those shortcuts while typing in common editor and input surfaces.
• E2E coverage for cycling, wrapping, home-tab jumps, and input suppression.
• A missing resolve-task REST route stub.
• Runtime dependencies for the app host capability server.

Confidence Score: 4/5

This is close, but the shortcut disabling path should be fixed before merging.

• The new tab-cycling behavior matches the visible-tab model.
• The new route stub follows the existing REST registration shape.
• A user can disable the new shortcuts in settings and still have the default keys switch tabs.

packages/apps/app/src/renderer/src/app-shell/useAppShortcuts.ts

Important Files Changed

Filename	Overview
packages/apps/app/src/renderer/src/app-shell/useAppShortcuts.ts	Adds guarded next and previous task-tab hotkeys, but disabled custom bindings can still fall back to their defaults.
packages/shared/shortcuts/src/definitions.ts	Adds customizable definitions for next and previous task-tab navigation.
packages/apps/app/e2e/core/16-tab-management.spec.ts	Adds tests for task-tab shortcut cycling, wrap behavior, home-tab behavior, and input suppression.
packages/shared/transport/src/server/http/rest-api/sessions/resolve-task.ts	Adds a 501 route stub that matches the surrounding REST route registration shape.
packages/apps/app/package.json	Adds host capability server dependencies used by the app package.
pnpm-lock.yaml	Updates locked dependency entries for the app package additions.

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
packages/apps/app/src/renderer/src/app-shell/useAppShortcuts.ts:213
**Disabled shortcuts still fire**

`next-task-tab` and `prev-task-tab` are registered as customizable shortcuts, but this call reads them through the local `getKeys()` helper that treats a `null` override as missing and falls back to the default key. When a user disables Cmd+Option+Right or Cmd+Option+Left in shortcut settings, the handler is still bound to the default and can still switch task tabs while the user expected it to be unbound. Please make this path preserve explicit `null` overrides instead of falling back to the default.

_{Reviews (2): Last reviewed commit: "revert(shortcuts): drop Cmd+1..9 changes..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

Context used:

• Context used - CLAUDE.md (source)
• Context used - AGENTS.md (source)

[greptile-apps]

Disabled shortcuts still fire

next-task-tab and prev-task-tab are registered as customizable shortcuts, but this call reads them through the local getKeys() helper that treats a null override as missing and falls back to the default key. When a user disables Cmd+Option+Right or Cmd+Option+Left in shortcut settings, the handler is still bound to the default and can still switch task tabs while the user expected it to be unbound. Please make this path preserve explicit null overrides instead of falling back to the default.

Prompt To Fix With AI

This is a comment left during a code review.
Path: packages/apps/app/src/renderer/src/app-shell/useAppShortcuts.ts
Line: 213

Comment:
**Disabled shortcuts still fire**

`next-task-tab` and `prev-task-tab` are registered as customizable shortcuts, but this call reads them through the local `getKeys()` helper that treats a `null` override as missing and falls back to the default key. When a user disables Cmd+Option+Right or Cmd+Option+Left in shortcut settings, the handler is still bound to the default and can still switch task tabs while the user expected it to be unbound. Please make this path preserve explicit `null` overrides instead of falling back to the default.

How can I resolve this? If you propose a fix, please make it concise.