agent-platform release v4.101.1

atelet pins the platform’s runtime images on the fleet shape: the kagent release moves its ConfigMap kagent-images into gitops.namespace (giantswarm/agent-platform#745). Flux resolves a HelmRelease’s valuesFrom in the HelmRelease’s own namespace. With the HelmReleases in gitops.namespace (flux-giantswarm) and the kagent release in gitops.targetNamespace, the substrate release’s optional reference to kagent-images found nothing, and atelet ran without --image-cache-pinned-images: the image cache could evict the Harness image, and the first turn after an idle spell paid the cold pull. The new component key valuesSourceObjects lists the objects a sibling reads through valuesFromRefs. When the release installs into another namespace than its HelmRelease and no remote target is set, a kustomize postRenderer on the HelmRelease moves each listed object into gitops.namespace. components.kagent lists kagent-images. verify-engine asserts the move in the fleet shape, and verify-kagent-wiring asserts that no postRenderer is rendered when the namespaces agree. Installations act: none. On the fleet shape the ConfigMap moves on the next kagent reconcile, the substrate release picks up the pinned set, and the atelet DaemonSet rolls once.