agent-platform release v4.76.0

The model pods export their traces to the platform’s OTLP collector: the kserve-config-llm-tracing preset follows global.observability.traces.otlp, and <release>-model-serving-otlp-egress opens its endpoint (giantswarm/giantswarm#36711, giantswarm/kserve#99). The llm-d controller emits no spans; vLLM and the endpoint picker of an LLMInferenceService whose spec carries tracing export to the preset’s endpoint, which upstream hardcodes to http://otel-collector:4317. kserve-runtime-configs.kserve.llmisvcConfigs.tracing.exporterEndpoint and its podLabels tenant label are auto, written from the global endpoint and tenant by agent-platform.shape.otlp; an explicit value wins, and an http/protobuf global protocol fails the render while the endpoint is auto (gRPC only). The connectivity chart opens the model pods’ egress, both flavours, to modelServing.networkPolicy.otlpEndpoint (auto), where the meta chart writes the preset’s resolved endpoint. Nothing exports until a service carries tracing: {} (README “The model pods’ traces”). Pin first: components.kserve-runtime-configs.versionRange is 0.6.x and examples/customer-bom.yaml pins 0.6.0, the release that opens the key; verify-serving-slice and verify-model-serving-policies hold the resolution, the guards and the egress.