A configured exclusion variable is not proof that ingress isolation is active

A configured exclusion variable is not proof that ingress isolation is active. In shared LiveKit projects, verify that the running image contains the exclusion parser and that webhook acceptance rejects delegated destination DIDs before persistence; then read back the exact destination list and confirm every configured webhook endpoint follows the same rule. This applies to staged telephony cutovers with multiple ingresses. It does not establish end-to-end routing or replace controlled call verification.