feat(canvas): file tasks to channels via desktop_file_system

[raquelmsmith]

Summary

• Persists task↔channel filing as channel-task rows on the project's desktop_file_system surface (mirrors how dashboards are stored), replacing the local Zustand mapping.
• New ChannelTasksService + tRPC router (list/file/unfile).
• "File to…" submenu wired in two places: right-click on a task row in the channels sidebar, and the native task context menu in the main tasks panel.
• Channels sidebar: drops the Backlog/Todo/etc. task-type rows and the inner "Tasks" Collapsible; filed tasks render flat with a code icon; Dashboards row gets a file icon; hover-revealed "+" button on the channel header opens the New task panel.

Test plan

• Restart Electron so the new tRPC router is picked up.
• Right-click a task in the channels sidebar → File to… → pick a channel → task appears under the target channel.
• Right-click a task in the main tasks panel → File to… → pick a channel → task appears under that channel in the canvas sidebar.
• Create a new task from a channel's "+" button → task is filed to that channel.
• Delete a channel → its filed channel-task rows are cleaned up.
• Reload the app → filed tasks survive (server-backed).

Note: branched off feat/canvas-file-tasks-to-channels, which isn't yet on remote, so the diff vs. main includes the prior canvas work as well.

🤖 Generated with Claude Code

[greptile-apps]

Prompt To Fix All With AI

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

---

### Issue 1 of 3
apps/code/src/main/services/channel-tasks/service.ts:75-84
**`file()` triggers two independent full-list scans**

`channelPath()` already performs a point-GET for the channel entry. The subsequent `this.list(input.channelId)` then calls `listAll()` — a full paginated scan of every FS entry — purely to check for duplicates. You can recover the path from that same scan, eliminating the `getEntry` round-trip, or alternatively do the idempotency check first so the path fetch only happens when a POST is actually needed.

### Issue 2 of 3
apps/code/src/renderer/features/canvas/components/ChannelsList.tsx:187-195
**"File to…" copies rather than moves**

`fileTask(targetChannelId, taskId)` files the task to the new channel but does nothing to remove it from `channelId` (the channel the task row lives under). The task will appear under both channels after the operation. If the intent is a move, an `unfileTask(existingRecord.id)` call for the source entry is needed alongside the new `file()` call.

### Issue 3 of 3
apps/code/src/main/services/channel-tasks/service.ts:32-63
**`fsFetch` / `listAll` / `getEntry` duplicated from `DashboardsService`**

These three private helpers are character-for-character copies of the identical methods in `apps/code/src/main/services/dashboards/service.ts` (same constant names, same pagination logic, same error messages). Extracting a shared `DesktopFileSystemClient` base class or utility would express this idea OnceAndOnlyOnce and prevent the two copies drifting apart.

_{Reviews (1): Last reviewed commit: "feat(canvas): file tasks to channels via..." | Re-trigger Greptile}

[greptile-apps]

file() triggers two independent full-list scans

channelPath() already performs a point-GET for the channel entry. The subsequent this.list(input.channelId) then calls listAll() — a full paginated scan of every FS entry — purely to check for duplicates. You can recover the path from that same scan, eliminating the getEntry round-trip, or alternatively do the idempotency check first so the path fetch only happens when a POST is actually needed.

Prompt To Fix With AI

This is a comment left during a code review.
Path: apps/code/src/main/services/channel-tasks/service.ts
Line: 75-84

Comment:
**`file()` triggers two independent full-list scans**

`channelPath()` already performs a point-GET for the channel entry. The subsequent `this.list(input.channelId)` then calls `listAll()` — a full paginated scan of every FS entry — purely to check for duplicates. You can recover the path from that same scan, eliminating the `getEntry` round-trip, or alternatively do the idempotency check first so the path fetch only happens when a POST is actually needed.

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

[greptile-apps]

"File to…" copies rather than moves

fileTask(targetChannelId, taskId) files the task to the new channel but does nothing to remove it from channelId (the channel the task row lives under). The task will appear under both channels after the operation. If the intent is a move, an unfileTask(existingRecord.id) call for the source entry is needed alongside the new file() call. Is "File to…" intended as copy-to-another-channel (task lives under both) or move (unfile from current, file to target)?

Prompt To Fix With AI

This is a comment left during a code review.
Path: apps/code/src/renderer/features/canvas/components/ChannelsList.tsx
Line: 187-195

Comment:
**"File to…" copies rather than moves**

`fileTask(targetChannelId, taskId)` files the task to the new channel but does nothing to remove it from `channelId` (the channel the task row lives under). The task will appear under both channels after the operation. If the intent is a move, an `unfileTask(existingRecord.id)` call for the source entry is needed alongside the new `file()` call. Is "File to…" intended as copy-to-another-channel (task lives under both) or move (unfile from current, file to target)?

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

[greptile-apps]

fsFetch / listAll / getEntry duplicated from DashboardsService

These three private helpers are character-for-character copies of the identical methods in apps/code/src/main/services/dashboards/service.ts (same constant names, same pagination logic, same error messages). Extracting a shared DesktopFileSystemClient base class or utility would express this idea OnceAndOnlyOnce and prevent the two copies drifting apart.

Prompt To Fix With AI

This is a comment left during a code review.
Path: apps/code/src/main/services/channel-tasks/service.ts
Line: 32-63

Comment:
**`fsFetch` / `listAll` / `getEntry` duplicated from `DashboardsService`**

These three private helpers are character-for-character copies of the identical methods in `apps/code/src/main/services/dashboards/service.ts` (same constant names, same pagination logic, same error messages). Extracting a shared `DesktopFileSystemClient` base class or utility would express this idea OnceAndOnlyOnce and prevent the two copies drifting apart.

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

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!