Permission dialog presents machine-composed commands as unreadable monochrome text

The bash-approval dialog renders dense compound commands in a small plain-text box: no syntax coloring, no structural line-breaking, no path/verb emphasis — inside VS Code, whose native TextMate/semantic highlighting the extension bypasses on exactly this surface. The result defeats the dialog's purpose: an unreadable consent prompt produces ratification-by-fatigue, not review — the final human safety check fires without any checking happening. The fix is available at composition time: the extension composed the command, so it knows the intent and structure. Render a one-line plain-language summary of what the command does above the raw text, break compound commands at pipes and && (one operation per line), highlight paths and write-verbs, and pass the raw text through the host's existing shell grammar. Summarize-then-show is already how Claude Code's own reports work; the approval dialog is the one surface that forgot the doctrine.

No files, tests, or entry points are named in the issue. Start by locating the bash-approval dialog and how composed commands are passed into it, then trace whether VS Code shell highlighting can be reused there. Done means the dialog shows a plain-language summary, splits compound commands at pipes and &&, emphasizes paths/write verbs, and still displays the raw command.

Written by the indexing model from the issue text.