feat(sidebar): scoped command palette for task search

[posthog]

Summary

Task search lives in the command palette. The Search nav item and the Tasks-section search button both open one unified palette listing commands and tasks together.

Context https://posthog.slack.com/archives/C09G8Q32R6F/p1779108205662669

Changes

• Sidebar nav: nothing => new Search nav item; opens the command palette
• Tasks section: search icon button next to the label => opens the command palette
• Command palette: separate command list => one merged list of commands + tasks (no scope picker)
  • Task rows render the same status icon as the sidebar (cloud / PR / branch / state)
  • Long task names wrap instead of truncating (min-height, not fixed height)
• TaskIcon: inline icon logic in TaskItem => extracted shared component used by both sidebar and palette
• Icon colors: text-* classes => phosphor color prop (SVG fill), so they survive quill's highlighted-row color reset
• Nav item shortcuts: hidden => keyboard shortcut Kbd revealed on hover (⌘K Search, ⌘N New task, ⌘I Inbox)
• Inbox: tooltip shortcut= prop => inline hover Kbd; @components/ui/Badge color="amber" => quill Badge variant="warning"
• useTaskPrStatus: TaskData param => minimal Pick<TaskData, "id" | "cloudPrUrl">
• CommandMenuAction: added "open-task"

Notes

• The earlier inline-search-header approach and the scope-Select were both reverted along the way.
• The palette fires getTaskPrStatus per task so task rows show PR/branch status with full parity to the sidebar — a query per task on open for large workspaces.
• Couldn't verify in a running Electron build.

🤖 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/renderer/features/sidebar/components/items/SearchItem.tsx:14-19
**`⌘K` hint opens Commands scope, not Tasks scope**

The Search nav item's `onClick` calls `openCommandMenu("tasks")`, correctly landing in the Tasks scope. However, the shortcut hint `SHORTCUTS.COMMAND_MENU` (`⌘K`) is wired to `toggle()` in the store, which always resets `scope` to `"commands"` when opening. Hovering this item implies `⌘K` replicates the click, but it doesn't — the user lands in Commands scope instead. Either use a dedicated shortcut for task search or omit the hint until a dedicated shortcut exists.

### Issue 2 of 3
apps/code/src/renderer/features/command/components/CommandMenu.tsx:286-302
**Empty-task state shows misleading "No tasks match """ message**

When `tasks.length === 0` the memo returns `[]`, so `AutocompleteStatus` renders its `emptyContent` regardless of `query`. With an empty query this produces "No tasks match **""**", implying tasks exist but nothing matched. A distinct empty-state path (e.g. checking `tasks.length === 0 && !query`) would let you show "No tasks yet" or similar instead.

### Issue 3 of 3
apps/code/src/renderer/features/command/components/CommandMenu.tsx:99-102
The "Commands" and "Tasks" label strings inside `SelectItem` duplicate what's already in `SCOPE_LABELS`. By the OnceAndOnlyOnce principle these can be derived from the constant directly, so a future rename only needs one change.

```suggestion
        <SelectGroup>
          {(Object.keys(SCOPE_LABELS) as CommandMenuScope[]).map((s) => (
            <SelectItem key={s} value={s}>
              {SCOPE_LABELS[s]}
            </SelectItem>
          ))}
        </SelectGroup>
```

_{Reviews (1): Last reviewed commit: "feat(sidebar): scoped command palette fo..." | Re-trigger Greptile}

[jonathanlab]

Love it!