feat(command): add channels to cmd-k and show task filing

[raquelmsmith]

Context

Channels (top-level Home-space folders) were only reachable by clicking them in the ChannelsList sidebar — no command-palette entry, no keyboard path. This makes them findable in cmd-k and clarifies where tasks live.

Changes

• Channels in cmd-k — CommandMenu gains a searchable Channels section sourced from useChannels, navigating to /website/$channelId via a new navigateToChannel bridge helper.
• Sidebar follows the route — ChannelSection auto-expands when the active route is inside that channel (cmd-k, deep links, Canvases nav), while keeping manual collapse/expand intact.
• Task filing shown — task entries render the channel they're filed to as a muted · #channel suffix. A new useTaskChannelMap hook builds a taskId → channel map (a task is filed to at most one channel) by fanning out channelTasks.list per channel, gated on menu open and sharing the sidebar's query cache. Channel name is added to keywords so searching it surfaces filed tasks.
• Added "open-channel" to the CommandMenuAction analytics union.

Verification

• pnpm lint clean; pnpm typecheck passes (pre-commit hook ran it).
• Open cmd-k → Channels section lists channels; Enter navigates and the sidebar opens that channel. Filed tasks show Title · #channel; searching a channel name surfaces its tasks.

---

Created with PostHog Code

[github-actions]

React Doctor found 3 issues in 2 files · 3 warnings.

3 warnings

src/features/canvas/components/ChannelsList.tsx

• ⚠️ src/features/canvas/components/ChannelsList.tsx:340 Event logic handled in an effect no-event-handler
• ⚠️ src/features/canvas/components/ChannelsList.tsx:347 Derived value copied into state no-derived-state

src/features/command/CommandMenu.tsx

• ⚠️ src/features/command/CommandMenu.tsx:96 Large component is hard to read and change no-giant-component

_{Reviewed by React Doctor for commit a3288b6.}

[greptile-apps]

Prompt To Fix All With AI

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

---

### Issue 1 of 2
packages/ui/src/features/canvas/hooks/useTaskChannelMap.ts:30-40
**`useMemo` dependency is always stale due to `channels` reference instability**

`useChannels` computes the `channels` array inline — `filter(...).map(...).sort(...)` — without memoizing it, so every render of `useChannels` produces a new array reference even when the underlying data hasn't changed. Because `channels` is in the `useMemo` dependency array here, the Map is rebuilt on every render while the menu is open. That rebuilt Map is a new reference, so `taskSections` in `CommandMenu` also recomputes on every render. With a small channel count and a short open-window this rarely matters in practice, but the cascade is worth closing. Using the `combine` option on `useQueries` to fold `channels` into the result in a stable way, or memoizing `channels` inside `useChannels`, would break the chain.

### Issue 2 of 2
packages/ui/src/features/command/CommandMenu.tsx:98-99
**Dual `useChannels` subscriptions — one always-on, one gated**

`CommandMenu` subscribes to `useChannels()` at line 98 (always enabled) and `useTaskChannelMap({ enabled: open })` internally also calls `useChannels({ enabled: open })`. The two subscriptions share the same React Query cache key so no extra network requests occur, but there are now two live subscriptions returning independently-computed (new-reference-each-render) arrays from the same underlying data. Passing the already-fetched `channels` into `useTaskChannelMap` as a parameter would remove the internal `useChannels` call, make the hook's inputs explicit, and resolve the reference-instability cascade noted on the hook itself.

_{Reviews (1): Last reviewed commit: "feat(command): add channels to cmd-k and..." | Re-trigger Greptile}