Every GitOps setup meets the same moment: something is on fire, someone runs kubectl scale on prod, and the fix works. What happens next depends on two settings that rarely get checked before an incident: self-healing on the GitRepo, and pause on the cluster. I ran all three combinations in a lab on Rancher 2.15.1 with Fleet (biased, I work at SUSE).