Vouch request: [PurpleCHOIms]

[PurpleCHOIms]

What do you want to work on?

I'd like to fix #5193. Policies that mix named endpoints with hostless
allowed_ips (CIDR) endpoints on the same ports get rejected by the
ambiguity validator, and even when validation is relaxed the runtime
matchers misbehave: a named connection that resolves outside the CIDR
range gets kernel-denied because the hostless matcher claims every
hostname on the port. My PR #5198 (3 commits) separates the two
destination classes end to end: the validator stops treating named vs
hostless as competing selectors, and the approval + metadata matchers
in sandbox-policy.rego are scoped to raw-IP destinations only. Hostless
vs hostless competition is preserved, so two hostless endpoints with
different allowed_ips are still rejected.

Why this change?

I work on a red-team agent platform that compiles operator RoE scopes
into OpenShell sandbox policies. Real scopes almost always mix named
targets with IP ranges, so today we either drop the CIDR entries or
refuse the engagement, which is not great. With this fix the common
case compiles into one policy and enforces correctly on a live kernel:
named requests follow named endpoints, raw-IP connections follow the
hostless endpoint, out-of-range and IMDS are denied.

Checklist

• I wrote this request myself (not AI-generated)
• I have read CONTRIBUTING.md