agent-platform release v3.22.2

components.kagent.versionRange is >=0.2.0 <1.0.0 (was 0.2.x): the floor stays at the flattened chart the wiring needs, the ceiling moves to the next major, as for the other 0.x components. The giantswarm/kagent wrapper released 0.3.0 and 0.3.1 on 2026-09-09 from CI-only changes (giantswarm/kagent#73, a feat(ci) title — a minor bump to git-cliff — and the align run giantswarm/kagent#71) with a chart identical to 0.2.2 in templates, values and dependencies: only Chart.yaml’s version and its tag-derived annotation URLs differ. The 0.2.x range excluded both, so every installation would have stayed on 0.2.2 and missed every wrapper release from here on, the next fix included. Every installation with kagent on upgrades the kagent release 0.2.2 → 0.3.1 on its next reconcile: two labels change on every object (helm.sh/chart, app.kubernetes.io/version — the wrapper stamps its chart version as the app version) and the pod annotations that hash the labelled ConfigMaps and Secret change with them, so the kagent controller and UI pods roll once; nothing else in the render changes. The meta chart’s fleet render differs by the kagent OCIRepository’s semver line only. make verify-meta asserts the range; examples/customer-bom.yaml keeps its exact 0.2.0 pin.