Given its own broken script and the real error, it produced the correct fix but explained --no-overwrite away as 'introduced in a later version of rsync'. No rsync version has ever had that flag, and the operator is on current 3.4.4 — so the repair was right and the diagnosis was a second fabrication that would send someone hunting a nonexistent upgrade.