agent-platform release v4.68.1

A fresh install of the serving slice comes back Ready: components.kserve-runtime-configs.driftDetection ignores the configs’ /spec (giantswarm/agent-platform#508). Once Helm has applied the well-known LLMInferenceServiceConfigs, KServe writes the fields its API types default (spec.model.uri, a port’s protocol and appProtocol, an empty resources, a backendRef’s group) into kserve-config-llm-scheduler and -latency-predictor; helm-controller compared them with the chart’s manifest, corrected them on every reconcile and left the release Ready=Unknown, so a first install (agentlab up, a new slice through cluster-manager) never finished. A config that is gone is still re-created on the next reconcile. make verify-serving-slice asserts the rule.