agent-platform release v4.61.0

The data plane’s buffer is the platform’s own number: gateway.http.maxBufferSize, 8Mi, rendered as the Gateway-scoped <release>-http AgentgatewayPolicy (frontend.http.maxBufferSize) (giantswarm/agent-platform#630). The MCP path reads every tool answer of every server behind muster whole before it forwards it, and an answer above the limit is refused with agentgateway’s body exceeded buffer limit — at the 2 MiB default a whole-registry dry run of the platform manager was lost this way, an error naming neither the size nor the limit. 8Mi is sized from what the platform’s tools answer (the manager’s own 1 MiB bound wrapped once more by muster’s call_tool, with the same room several times over for a server that bounds nothing) and stays inside the data plane’s 512Mi memory limit a dozen times over. A quantity or a byte count; empty leaves agentgateway’s default in force; frontend policies merge field by field, so this policy owns frontend.http alone (make verify-dataplane-buffer). Both charts carry the default. README “The data plane’s buffer”.