Summary

• Adds a fifth Type facet to the task board's filter menu (TaskFilterMenu), alongside the existing Task group / Channel / Deal stage / CRM sync facets, filtering tasks by which playbook (AOP) their underlying deal belongs to.
• Follows the exact Deal stage precedent: the facet keys off a field already hydrated onto the task's conversation object (aopId), rather than a hardcoded static option list.
• Options are fetched dynamically per-user, the same way the Task group facet does, via useAOPs() , the same hook CRMFilterBar.tsx's own "Type" (AOP) multi-select already uses, so there is only ever one AOP-list query in the app rather than a second, competing fetch.
• This is a general Cedar feature (any user with multiple AOPs can use it), not specific to any one customer.

Why

A customer is about to split their pipeline into two playbooks by deal origin. They need to filter their task board by playbook independently of the existing pipeline filter, and this should work for any user with more than one AOP.

Changes

1. apps/server/src/trpc/routes/user-tasks.ts

   • TaskConversationHeader gains aopId: string | null and aopName: string | null.
   • hydrateTaskConversations() selects crmConversations.aopId, then resolves the distinct AOP ids in the batch to their names via a small parallel query (agentOperatingProcedures), matching the file's existing Promise.all([priorityOptions, openTasks]) idiom.
   • conversationHeaders needed no changes , it shares hydrateTaskConversations and inherits the new fields automatically.

2. apps/mail/modules/userTasks/utils/task-filters.ts

   • FilterableTask.conversation gains aopId?: string | null.
   • New NO_TYPE_KEY constant ('__no_type__'), mirroring NO_STATUS_KEY.
   • TaskFilters.filterTypes: string[], a new 'types' member on TaskFacet/TASK_FACETS, and a types entry in FACET_DEFS (keyOf: (t) => t.conversation?.aopId ?? NO_TYPE_KEY).
   • makeTaskFilter / taskFacetCounts needed no changes , confirmed they're fully generic over TASK_FACETS.

3. apps/mail/modules/userTasks/components/TaskFilterMenu.tsx

   • New "Type" FacetSubmenu, sourced from useAOPs() (not a hardcoded array like STAGE_OPTIONS/CRM_OPTIONS), with a trailing "No type" option using NO_TYPE_KEY.
   • Docstring updated from "four filter facets" to "five".

4. apps/mail/modules/userTasks/hooks/use-task-list-view-options.ts

   • filterTypes added as a URL-persisted param (filterTypes), following the exact pattern of filterCrm/filterStatuses.

5. TaskKanbanBoard.tsx / TaskListView.tsx / use-task-group-buckets.ts

   • Threaded filterTypes through the three existing makeTaskFilter({...}) call sites, which the compiler caught as newly required once TaskFilters.filterTypes became non-optional.

Test plan

• pnpm --filter @zero/server run types , clean.
• pnpm --filter @zero/mail run types , clean for every file touched by this diff (remaining failures are pre-existing generated-file errors , @/paraglide/*, ./+types/* , unrelated to this change, present in a fresh worktree before any codegen step runs).
• Manually: on an account with 2+ AOPs, open the task board, open Filter → Type, confirm each AOP appears with its own colour dot and a live count, confirm "No type" catches tasks whose deal has no AOP, confirm selecting one or more types filters both the List and Board views consistently, and confirm the selection round-trips through the URL (filterTypes=...) and survives a refresh.
• Manually: confirm "Clear filters" also clears the Type selection.

🤖 Generated with Claude Code

https://claude.ai/code/session_019jTe7TuDHKYaFL6Ny2Z5h6

Greptile Summary

This PR hydrates task conversations with their playbook identity and adds a URL-persisted Type facet across the task l