Summary

RootConfig now carries a git_clone: GitCloneNetworkPolicy field and GitCloneTool.__init__ accepts a network_policy parameter, but the engine layer does not pass the config-supplied policy when instantiating GitCloneTool. The tool always uses the default policy (GitCloneNetworkPolicy()), making the YAML-configured hostname_allowlist non-functional.

Context

Added in #505 (SSRF prevention for git clone URLs). The tools layer is complete — this is engine-layer wiring.

Scope

• In whatever engine/workspace component instantiates git tools, pass config.git_clone as the network_policy argument when constructing GitCloneTool
• Add integration test verifying the config flows through

Design Spec Reference

• §11.1.1 Built-in git tools

Notes

The default policy is maximally restrictive (block all private IPs, empty allowlist), so this is not a security regression. It means the allowlist cannot be used until this wiring is added.