Worktree-isolation refusals all carry a fixed "run without the redirect" remedy, even when there is no redirect

Description

Refusals from the worktree-isolation Bash checker carry the same closing remedy regardless of cause:

Run the equivalent from <worktree path> without the redirect

Every refusal we saw ends with this line, including refusals that have nothing to do with redirects — e.g. a command refused for being a compound command (a for loop or && chain with no redirect anywhere in it) still tells the user to re-run "without the redirect". For those cases the remedy names an action that does not exist, which reads as a bug in whatever tooling the user suspects, sending debugging toward the wrong component.

Suggestion

Make the remedy reason-specific: refusals for command complexity should say "break into separate simple commands" (which the inner message already does — the closing line then contradicts it), redirect refusals should mention the redirect, and path refusals the path. Even just omitting the closing line when the refusal reason contains its own remedy would fix the confusing cases.

Environment

• Claude Code 2.1.235, macOS
• Attribution: the remedy text above appears verbatim in the Claude Code 2.1.235 distribution and in none of the locally installed hooks or tools, so it is not coming from user configuration.