Permission resolution can now be told the host forbids bypass mode, but nothing reads it.
A bypassPermissionsBlockedByHost input is plumbed through permission-mode resolution but never read back in this build.
What's wrong with this entry?
The permission-mode resolver and its subprocess variant now accept a bypassPermissionsBlockedByHost input, carried alongside the existing skip-permissions and non-interactive flags. Nothing in this build reads the value back out, so it is plumbing ahead of the behaviour it is named for.
bypassPermissionsBlockedByHost
Strings lifted out of the shipped bundle, so the claim above can be checked against them.