Greptile Summary

This PR adds a tools.web.fetch.ssrfPolicy configuration option to web_fetch, mirroring the existing browser.ssrfPolicy and enabling operators using TUN-mode proxies (e.g. Clash Verge) that return fake private IPs to opt-in to allowing private-network resolution. The default remains strict, and enabling the feature requires an explicit dangerouslyAllowPrivateNetwork: true flag, consistent with the project's break-glass security model.

Key changes:

• New ssrfPolicy field in ToolsConfig, Zod runtime schema, help, and labels — all consistent with the existing browser.ssrfPolicy shape.
• resolveFetchSsrFPolicy() maps config to an SsrFPolicy and passes it as policy to fetchWithWebToolsNetworkGuard; because fetchWithSsrFGuard re-runs resolvePinnedHostnameWithPolicy at every redirect hop, the policy is enforced end-to-end including through redirects.
• The new test also adds a resolvePinnedHostnameWithPolicy spy to beforeEach, which corrects a pre-existing gap where the DNS mock wasn't actually intercepting calls from fetchWithSsrFGuard (which calls resolvePinnedHostnameWithPolicy directly, not resolvePinnedHostname).
• allowRfc2544BenchmarkRange is present in the type and Zod schema but has no schema.help.ts / schema.labels.ts entry — this matches the identical omission in browser.ssrfPolicy and so is intentional/consistent, and the help-parity quality test will still pass.

Confidence Score: 4/5

• Safe to merge; opt-in only, default remains strict, policy is enforced at every redirect hop, and no regression risk to existing behaviour.
• The implementation is clean and self-contained, directly mirrors the existing browser.ssrfPolicy pattern, and the SSRF policy is propagated correctly through the full redirect chain in fetchWithSsrFGuard. The new test adds useful coverage and incidentally fixes a pre-existing DNS-mock gap. One point is held back because the test only covers dangerouslyAllowPrivateNetwork; allowedHostnames and hostnameAllowlist integration paths lack dedicated tests.
• No files require special attention; all changes are low-risk additions with no modification of existing logic.

_{Last reviewed commit: 41025c7}

This not only affects the web_fetch tool, but also affects Discord connections. After the OpenCLAW gateway restart, it fetches the Discord server failed because of SSRF.