OpenShell's Z3 policy prover misses the cloud metadata address in 29 checks

A developer built Nvidia's openshell-prover CLI from source and ran 29 candidate/boundary policy pairs against it. The SMT-based check catches most privilege escalations but passes access to 169.254.169.254 and other link-local and loopback addresses, which are excluded from the containment model in ip.rs.

• 29 checks: privilege escalation and protocol swaps caught, metadata address missed
• 169.254.169.254 passes even against an empty boundary with no network access
• Loopback, link-local and 0.0.0.0 are excluded from the model in ip.rs
• The runtime proxy blocks these ranges separately, but the CLI output doesn't say so