Swept into d5e0731 by the same stray `git add -u`. Unlike argocd-install
this one is synced, so it went live; reverting here rolls the cluster back
to connectionIdleTimeout 3600s with no retry block.
The content is still reachable at d5e0731 if it is wanted back.
The earlier rule covered creationTimestamp, volumeMode and status but missed
apiVersion and kind, which the API server also injects into
volumeClaimTemplates. Those two alone kept both StatefulSets permanently
OutOfSync: a sync would apply successfully and report Synced, then the very
next comparison flagged them again.