What is the architecture of a GitOps agent, such as Argo CD? How does it ensure cluster state consistency with the repository under high Kubernetes API load?