agent-platform release v4.109.0

The data plane’s access log names the session of an agent’s model call: agent_instance_id (giantswarm/giantswarm#38023). The kagent line names the AgentInstance a turn runs in (a Dev Portal conversation, a Slack thread) in x-kagent-agent-instance-id on every model call of the turn (giantswarm/kagent-upstream#149). The connectivity chart renders a Gateway-scoped AgentgatewayPolicy <release>-access-log whose frontend.accessLog.attributes add that header as agent_instance_id, read behind the same Substrate egress predicate as the agent labels, so the cost of one conversation can be summed from the llm listener’s lines without one metric series per session. gateway.accessLog.attributes is a map of {expression, enabled} entries in both charts; make verify-access-log asserts it. Every installation with the agentgateway data plane gets one new object; no pod rolls.