chore: sync deployment-operator CRDs

[github-actions]

Automated pull request to sync deployment-operator CRDs from console.

[greptile-apps]

Greptile Summary

This automated CRD synchronization exposes component SHA cache TTL configuration and adds PI as a supported agent runtime.

• Adds componentShaCacheTTL to AgentConfiguration.spec.
• Adds PI runtime configuration fields and admits PI in the AgentRuntime type enum.
• Leaves PI's AI-proxy model-prefix behavior undocumented.

Confidence Score: 4/5

The PR appears safe to merge, with a non-blocking documentation gap around PI model routing through the AI proxy.

The synchronized schemas consistently add the new fields, but PI users enabling aiProxy are not told how bare model identifiers are prefixed or whether provider/name form is required.

Files Needing Attention: charts/deployment-operator/crds/deployments.plural.sh_agentruntimes.yaml

Important Files Changed

Filename	Overview
charts/deployment-operator/crds/deployments.plural.sh_agentconfigurations.yaml	Adds an optional component SHA cache TTL string consistent with the CRD's existing duration-field schemas.
charts/deployment-operator/crds/deployments.plural.sh_agentruntimes.yaml	Adds PI runtime configuration and enum support, but the existing AI-proxy documentation does not explain PI's bare-model provider mapping.

_{Reviews (1): Last reviewed commit: "chore: sync deployment-operator CRDs" | Re-trigger Greptile}

[greptile-apps]

Document PI proxy model routing

The new PI runtime supports aiProxy, but the proxy documentation enumerates bare-model prefix behavior for every runtime except PI. Users therefore cannot determine whether PI model values are automatically prefixed or must use explicit provider/name form, leading to ambiguous or incorrectly routed configurations.

Knowledge Base Used: Deployment Operator Helm Chart

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!