fix(canvas): open channel-filed task notifications in /website

[raquelmsmith]

Problem

When a task needs action, the user gets a desktop notification. Clicking it always opened the task at /code/tasks/$taskId — even when the task was filed to a Project Bluebird channel, where it should open in the channel-organized view at /website/$channelId/tasks/$taskId (keeping the channels chrome), exactly like the command palette already does.

The notification click and posthog-code://task/<id> deep links both funnel through useTaskDeepLink, which called openTask(task) and unconditionally navigated to /code. Nothing consulted channel membership.

Change

• useOpenTask.ts — openTask now accepts an optional { channelId }. When present it navigates via navigateToChannelTask (→ /website); otherwise /code as before. Every other side effect (detail-cache seed, analytics, ensureWorkspaceForTask) is unchanged, so channel tasks still get workspace provisioning. Existing single-arg callers are unaffected.
• useTaskDeepLink.ts — resolves channel membership (gated behind PROJECT_BLUEBIRD_FLAG) via useChannels + useTaskChannelMap, mirrored into a ref so the stable handleOpenTask callback reads the current map without tearing down the onOpenTask subscription on each 30s channel poll.
• CommandMenu.tsx — collapsed its duplicated if/else branch onto the same parameterized openTask, so palette-opened channel tasks also get workspace binding.

This fixes both notification clicks and deep links, since they share the path.

Known limitation

Cold start (app launched by the click before the channel map has loaded) falls back to /code. Warm clicks — the dominant case for "needs action" notifications — route correctly.

Verification

• pnpm --filter @posthog/ui test run …/useTaskDeepLink.test.tsx — 4/4 pass (added cases: filed task → channel route; flag-off → /code).
• pnpm --filter @posthog/ui typecheck — clean.
• biome lint on changed files — clean.

🤖 Generated with Claude Code

[github-actions]

React Doctor found no issues in the changed files. 🎉

_{Reviewed by React Doctor for commit bb44140.}

[greptile-apps]

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/ui/src/features/deep-links/useTaskDeepLink.test.tsx:77-114
**Prefer parameterised tests for the routing dispatch cases**

The three cold-start routing assertions repeat the same setup (set `channelMapState.map`, mock `getPendingDeepLink`, `renderHook`, `waitFor`) and differ only in flag state, channel map contents, and the expected `routerOpenTask` args. Per the project rule, collapsing them into a single `it.each` would express the same ideas without duplication. A fourth row could cover the warm-start path (trigger via `onOpenTask`'s subscription callback rather than `getPendingDeepLink`) to close that coverage gap at the same time.

_{Reviews (1): Last reviewed commit: "fix(canvas): open channel-filed task not..." | Re-trigger Greptile}

[adamleithp]

LGTM

[raquelmsmith]

tested locally, works

[greptile-apps]

_{Reviews (2): Last reviewed commit: "test(canvas): parameterise task deep-lin..." | Re-trigger Greptile}