agent-platform release v4.67.1

A well-known LLMInferenceServiceConfig that went missing is re-created on the release’s next reconcile: components.kserve-runtime-configs.driftDetection.mode: enabled by default (giantswarm/agent-platform#508). The kserve-runtime-configs HelmRelease carried no drift detection, so helm-controller judged it by its Helm storage alone: a slice torn down at once left the ten configs terminating under the llm-d controller’s finalizer, the next install adopted them, the new controller then finished their deletion, and the release stayed “in-sync” with no config behind it — every LLMInferenceService composed from them failed PresetsCombined=False ConfigNotFound until flux reconcile helmrelease kserve-runtime-configs --force. With spec.driftDetection.mode: enabled helm-controller compares the release manifest with the cluster on every reconcile (gitops.interval) and re-applies a missing or changed config as a server-side apply, without a Helm revision. No ignore rule: the configs are configuration only, the controller’s finalizer survives the apply and no webhook mutates them. The third release to carry it, after kagent and muster; the other serving releases keep helm-controller’s default. examples/serving-slice.yaml shows the setting; tests/verify-serving-slice.py asserts it on the slice’s render and on no other release of the slice, tests/verify-kagent-wiring.py adds it to the set of releases that carry drift detection.