Guardrails webfetch permission blocks autonomous team runs #210

Problem

Guardrails profile sets permission.webfetch to ask. In direct interactive runs, parallel team workers that need public web evidence can stop on webfetch permission requests instead of continuing autonomously.

Observed in /Users/teradakousuke/Developer/persona-village-v2: a docs-only team run stopped on public GitHub WebFetch requests such as https://github.com/NousResearch/hermes-agent-self-evolution. The parent session then entered the Reject permission text field, and Ctrl+C did not reliably exit from that focused reject textarea.

Impact

• Implementation work can stall before workers start their assigned tasks.
• Parallel team runs abort sibling workers after one child hits the permission gate.
• The direct-mode reject field can trap the user in a state that is difficult to interrupt.

Expected

• Guardrails implementation/review/provider-eval workflows should be able to fetch public web evidence without a blocking prompt.
• Ctrl+C should still reach the direct-mode exit path even when the permission reject textarea is focused.

Verification target

• webfetch evaluates to allow in guardrails profile and managed config.
• Direct interactive demo permission reject input exits on Ctrl+C.
• Local guardrails deployment points to the fixed binary/profile.