Agents with a shell command restriction can't use PowerShell at all now.
What's wrong with this entry?
An agent spawned with a clamp restricting which shell commands it may run now has PowerShell refused outright, since PowerShell commands cannot be matched against Bash command forms. If the PowerShell permission check itself throws, it fails closed instead of running an unverified command. Agents without a clamp are unaffected.
this agent carries a per-spawn bashCommandClamp, which scopes shell execution to a
Strings lifted out of the shipped bundle, so the claim above can be checked against them.