agent-platform release v4.19.0

Added

• klaus-gateway’s traces go to the platform’s OTLP gateway by default, and the gateway’s egress rule to it renders (giantswarm/klaus-gateway#263). Until now klausGateway.observability.otlpEndpoint was empty on every installation, so the gateway’s tracer provider was a no-op, the A2A call carried no trace context and the kagent controller’s SendStreamingMessage trace in Tempo had no parent — a Slack round trip could only be reconstructed from five logs. klaus-gateway 1.10.0 opens one span per turn (slack.turn, the parent of the controller’s trace and of the actor’s spans under it), takes a URL endpoint and an otlpHeaders knob; the meta chart now sets both to the target kagent’s exporters use — http://otlp-gateway.kube-system.svc:4317 with X-Scope-OrgID: giantswarm — under a new klausGateway.observability.enabled: auto that follows the resolved global.observability.metrics.serviceMonitor.enabled the way kagent.otel.*.enabled does (an explicit true/false wins; off, the release gets an empty endpoint and no headers; the knob itself never reaches the klaus-gateway chart, whose closed observability block takes the endpoint and headers only — components.klaus-gateway.omitKeys). The connectivity chart renders -klausgateway-otlp-egress exactly while the endpoint is set — DNS plus the endpoint’s namespace on its port (the cluster entity for a host that is not an in-cluster Service), in both policy flavours — through the destination parsing and the rule the kagent controller’s and the actors’ OTLP egress already used, now shared as agent-platform.otlpTarget / agent-platform.otlpEgressRule. components.klaus-gateway.versionRange moves to >=1.10.0 <2.0.0 (the floor: an older chart’s schema refuses the headers knob) and the example BOM pins 1.10.0. make verify-klausgateway-otlp asserts the forwarding, the auto resolution and the overrides, both flavours of the policy, the guards, and that the kagent controller’s rule is unchanged. Every installation with the klaus-gateway component on rolls it once (the new chart and the two new arguments) and starts exporting one trace per Slack turn to its Tempo tenant.