agent-platform release v4.96.1

modelServing.imageVerification admits images signed by a scheduled CircleCI pipeline (giantswarm/agent-platform#740). A pipeline a legacy scheduled trigger starts has no pipeline definition, so its signing certificate’s subject ends in pipeline-definitions/nil. retagger’s nightly mirror run signs so, the storage-initializer every hf:// preset starts with among its images, and the default subjectRegExp accepted a UUID only: Kyverno denied every hf:// predictor pod (no matching signatures found). The default of both charts is now ^https://circleci\.com/api/v2/projects/[a-f0-9-]+/pipeline-definitions/([a-f0-9-]+|nil)$. make verify-model-serving-policies asserts it admits both subjects and keeps out null, a trailing path, a nil project and another host. An installation that sets its own attestors is unchanged.