agent-platform release v4.78.0

model-manager, agent-manager, vm-manager, cluster-manager, the portal and mcp-kubernetes export their traces to the platform’s OTLP collector (giantswarm/giantswarm#36711). <component>.observability.otel.{endpoint,protocol,headers} of the four managers and backstage, and mcp-kubernetes.mcpKubernetes.instrumentation.{tracingExporter,otlpEndpoint,otlpInsecure,otlpProtocol,otlpHeaders}, are auto and follow global.observability.traces.otlp like the other exporters: the endpoint (host:port for mcp-kubernetes, with otlpInsecure from the scheme and tracingExporter: otlp while it is set), the protocol, and the tenant as X-Scope-OrgID next to headers. The connectivity chart’s egress policy of each manager and of the portal opens the resolved endpoint (its namespace and port, or the cluster entity / any address outside the cluster); mcp-kubernetes’ own policy already admits the cluster. The ranges move to the first releases that export: model-manager >=1.3.0, agent-manager >=1.2.0 <2.0.0, vm-manager >=0.24.0, cluster-manager >=0.19.0, backstage >=2.68.0, mcp-kubernetes >=1.3.0 (giantswarm/model-manager#183, giantswarm/agent-manager#69, giantswarm/vm-manager#112, giantswarm/cluster-manager#111, giantswarm/backstage#2601, giantswarm/mcp-kubernetes#649). make verify-otlp-global asserts the derivation and the egress rules. UPGRADE.md.