Hook-supplied permissionDecisionReason renders as one alarming block

When a PreToolUse hook returns "ask" with a permissionDecisionReason, the terminal renders the hook's reason and the harness's own confirmation line together in the warning style. Engineers read the two as one alarming block, and a deny reason carrying instructions for the agent arrives as a wall of red error text — for the one reader who cannot act on it.

We worked around it by shortening every reason to one line and writing the detail to a file the agent reads, but the hook cannot say which parts a person needs.

Please render hook-supplied reason text as ordinary output, or accept a hint such as reasonStyle, and keep the warning highlight for the confirmation question itself. Deliberate hook prompts would then read differently from genuine errors.