Shell command permission checks were tightened in several places

Before running a shell command, Claude Code reads it to decide whether it can run automatically or needs your approval. Several parts of that reading changed:

• The check for sudo options that open a shell, such as -s, -i, --shell and --login, now considers where the option sits in the command.
• A variable set in front of a command with +=, which appends to it, is now recorded as an append.
• The handling of command -v moved into its own check.
• A new check counts whether a run of backslashes is odd or even, which decides whether the next character is escaped.
• The message shown for a ${ …@P } expansion is now shorter.