agent-platform release v4.19.2

Changed

• The kagent line moves to v0.11.0-gs.16: context compaction in the Go ADK runtime and spec.context.compaction on the AgentTemplate (giantswarm/giantswarm#37792). After prompt caching (4.16.0) the remaining cost of a long agent turn was the model’s first pass over new tokens: every tool result stayed in the history verbatim and every later model call of the turn re-read it — on gazelle the status question’s ten calls grew from 6 k to 62 k input tokens, waited 9.2 s for the first token after 16 k new tool-result tokens and 18.8 s after 21.9 k, model time 59 s of the turn’s 68 s. kagent 0.11.0-gs.16 carries kagent-dev/kagent#2790 (giantswarm/kagent-upstream#41): google.golang.org/adk/v2 v2.3.0 with its native session/compaction, spec.context.compaction on the v1alpha3 AgentTemplate CRD (tokenThreshold / eventRetentionSize for tail retention inside a turn, compactionInterval / overlapSize for a sliding window over turns, an optional summarizer.modelConfig + promptTemplate, CEL for the half configurations), the kagent compiler writing it into config.json and the Go runtime handing it to the ADK runner (context compaction enabled … in the actor’s startup log). components.kagent / components.kagent-crds move to >=0.11.0-gs.16 <0.11.1-0: the floor, because the platform’s agent chart (giantswarm/agent 1.3.0) renders a compaction default on every platform agent — tail retention at 24 000 prompt tokens keeping the last four events, the summaries on the agent’s own model — and an older CRD would prune the field at admission, leaving every long turn re-reading its whole history in silence. The meta chart renders no AgentTemplate itself; the default and its knobs (context.compaction.*, enabled: false to opt out) live in the agent chart, which every agent HelmRelease follows on range 1.x. tests/verify-kagent-crds.py validates the connectivity chart’s kagent objects against the gs.16 CRDs; the BOM example and tests/verify-components.py follow the pin. Every installation rolls kagent once (the controller, then the platform Harness recompiles every admitted AgentTemplate; about 20 s per template) and, once the agent chart release is admitted, every agent recompiles once more with its spec.context — UPGRADE.md.