Clearer reasons when a shell command needs your permission

Before running a shell command without asking, Claude Code checks what the command will do. When it cannot, it asks your permission and shows a reason. Several of those reasons have been reworded:

• A command with an option it does not recognise now reads "command has an option or value (...) that cannot be checked in advance". It used to say the command with that flag "cannot be statically analyzed".
• timeout with an option it cannot check now reads "timeout has an option or value (...) that cannot be checked in advance".
• timeout with a duration it cannot read now reads "timeout has a duration ('...') that cannot be checked in advance".
• jobs -x now reads "'jobs -x' runs its argument as a command, so what it will run cannot be checked in advance".