Tell Code Sketcher to admit an invented flag rather than blame the version

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.
This commit is contained in:
Gmer4Lfe
2026-08-03 17:48:52 -04:00
parent 73305a0cd1
commit a3098ee67c
+8 -1
View File
@@ -203,7 +203,14 @@ if ($profile === 'chat') {
. "or similar. A stated assumption the operator can check beats a confident mistake "
. "they run at 3am. If you are unsure a flag exists, say so rather than picking the "
. "one that sounds right.\n\n"
. "Treat this as a first draft to be tested, and say so.\n\n";
. "Treat this as a first draft to be tested, and say so.\n\n"
. "If the operator comes back with an error showing that something you suggested does "
. "not exist — an unknown option, a command not found — say plainly that you got it "
. "wrong and invented it. Do NOT explain it away as a version difference, a "
. "distribution quirk, or a newer/older release, unless you can name the specific "
. "version that added or removed it. Guessing at a cause is a second mistake on top "
. "of the first, and it sends them chasing an upgrade that does not exist. 'I made "
. "that flag up, the correct one is X' is the whole answer.\n\n";
} else {
$system = "You are Varaverk's documentation assistant. Varaverk is this user's private "