fix: enable cmdk filtering for > queries

Fixed an issue where typing `>abc` wouldn't filter commands because
`shouldUseCmdkFilter` was set to false for command queries. Now cmdk
filtering is enabled for `>` queries so users can search through all commands.

Addresses Codex review comment about unsearchable "all commands" mode.

**Before:**
- `shouldFilter={false}` for `>` queries
- Custom filter was never called
- Typing `>abc` showed all commands unfiltered

**After:**
- `shouldFilter={true}` for `>` queries
- Custom filter strips `>` prefix and filters normally
- Typing `>abc` narrows down to matching commands

Author: ammar-agent

src/components/CommandPalette.tsx

@@ -5,7 +5,6 @@ import type { CommandAction } from "@/contexts/CommandRegistryContext";
 import { formatKeybind, KEYBINDS, isEditableElement, matchesKeybind } from "@/utils/ui/keybinds";
 import { getSlashCommandSuggestions } from "@/utils/slashCommands/suggestions";
 import { CUSTOM_EVENTS } from "@/constants/events";
-import { COMMAND_SECTIONS } from "@/utils/commands/sources";
 
 interface CommandPaletteProps {
   getSlashContext?: () => { providerNames: string[]; workspaceId?: string };
@@ -312,9 +311,8 @@ export const CommandPalette: React.FC<CommandPaletteProps> = ({ getSlashContext
 
   const isSlashQuery = !currentField && query.trim().startsWith("/");
   const isCommandQuery = !currentField && query.trim().startsWith(">");
-  const shouldUseCmdkFilter = currentField
-    ? currentField.type === "select"
-    : !isSlashQuery && !isCommandQuery;
+  // Enable cmdk filtering for all cases except slash queries (which we handle manually)
+  const shouldUseCmdkFilter = currentField ? currentField.type === "select" : !isSlashQuery;
 
   let groups: PaletteGroup[] = generalResults.groups;
   let emptyText: string | undefined = generalResults.emptyText;