agent-platform release v3.20.4

Fixed

• gateway.parameters.dataPlaneResources is settable through the meta chart (#303). The connectivity chart reads the key (the agentgateway data-plane container’s ephemeral-storage requests and limits, merged onto the container through AgentgatewayParameters) and its schema declares it, but the meta chart’s values.yaml did not, so the meta chart’s generated values.schema.json (gateway.parameters is additionalProperties: false) refused it at render time — additional properties 'dataPlaneResources' not allowed — although forwardAllValues would have carried it to the connectivity release unchanged; an installation migrating from the standalone chart, whose umbrella accepted the key, hit it. The meta chart now declares the key with the connectivity chart’s defaults (requests.ephemeral-storage: 50Mi, limits.ephemeral-storage: 512Mi), so the rendered platform objects are unchanged until an installation overrides them. make verify-meta’s schema-symmetry check compared the two charts’ top-level keys only and missed the nested key; it is now tests/verify-schema-symmetry.py, which walks the connectivity schema’s properties (and array items) under every block the meta chart forwards and fails on any nested key the meta schema rejects — and the other way round, on any forwarded meta key the connectivity schema does not declare (the roster travels as components.<name>.enabled only) — with negative cases proving both directions fail, naming the path. The walk found no other gap.