[BUG] A slash command inside a ```bash code block is given a Run affordance that cannot work

When a response includes a fenced code block tagged bash whose content is a bare slash command (for example /done), the app renders it as a runnable shell block, with the same copy/expand/run affordances as any other shell snippet. But a slash command is chat input, not shell input — running it in a terminal fails. Elsewhere the app renders slash commands as an inline chip, so the same command has two very different presentations depending on how the response happened to format it.

The impact is worst on remote control. On a phone, the code block is the largest and most prominent element on screen, and it carries an affordance that does the wrong thing, while the actual question being asked sits above it as ordinary text. The user reads the loud control, not the quiet ask.

Repro: have a response emit a fenced block tagged bash containing only a slash command, and view it in the desktop app and on remote control.

Either behaviour would resolve it: suppress the shell/Run affordance when a block's content is a bare slash command, or render it using the slash-command chip the app already has.