ACP command discovery is refactored to return one merged command set (built-ins + recipes + skills) so clients use a single source of truth for slash-command availability, instead of separate paths for each command type.
Scattered source updates, isolated context, and manual follow-up across multiple feeds.
Introduces a unified slash-command aggregation path so ACP exposes a single command catalog across built-in, skill, and recipe commands, with explicit collision precedence and shared slash-command handling for skills/recipes, reducing inconsistent command discovery behavior.
Clients and operators using ACP can now discover and invoke slash commands more reliably from a single unified list instead of treating built-ins, skills, and recipes as separate, inconsistent surfaces, which reduces user-visible failures when a command is present but not shown through one command surface. The implementation merges command sources in `available_commands_update` using builtin > recipe > skill precedence and aligns skill/recipe invocation behavior, but teams should monitor for stale command lists when skills/recipes change (or working directories switch), because the PR notes no robust event-driven refresh path yet and stale catalogs can still cause wrong or missing suggestions.
Clients and operators using ACP can now discover and invoke slash commands more reliably from a single unified list instead of treating built-ins, skills, and recipes as separate, inconsistent surfaces, which reduces user-visible failures when a command is present but not shown through one command surface. The implementation merges command sources in `available_commands_update` using builtin > recipe > skill precedence and aligns skill/recipe invocation behavior, but teams should monitor for stale command lists when skills/recipes change (or working directories switch), because the PR notes no robust event-driven refresh path yet and stale catalogs can still cause wrong or missing suggestions.