Built-in /review command silently collides with pre-existing user command — no way to win precedence

Claude Code shipped a built-in /review command that collides with a custom command I've had in ~/.claude/commands/review.md for months. Now /review always shows a disambiguation picker, and I have to eyeball descriptions to pick my own command every single time.

What makes this genuinely bad:

• User commands don't override built-in commands. The documented precedence (personal > project > bundled) only applies to bundled skills. Built-in commands always win a collision into a picker. So the command I authored first has no way to take its own name back.
• There's no way to disable a built-in command. disableBundledSkills exists for bundled skills, but there's no disabledSlashCommands or per-command toggle for built-ins.
• Net effect: Anthropic can claim any slash-command name at any time, and existing user commands of that name get demoted to a picker entry with no recourse except renaming my command.

Asks (any one would fix it):

1. Let user commands in ~/.claude/commands/ override built-in commands of the same name (least-surprise precedence).
2. Add a setting to disable/hide specific built-in commands.
3. At minimum, warn at startup when a newly-shipped built-in collides with an existing user command, instead of silently inserting a picker.