The ChatGPT transcript showed each CAMBS practice has its own SFTP
account (YSMD is YAM62682 on io.myallylogin.com:14147), not one shared
entity login - so the wizard needed a way to set those without hand-
writing nine practice.json files. Option 5 does that, and the settings
screen now lists which login each practice will actually use.
test-login.bat tests one account on its own, with the details typed in
rather than read from a config, which isolates the account from whatever
a script is doing to the credentials. It reports password length,
stray whitespace, and $ / backtick characters - the last being the usual
reason a login works in the WinSCP window but fails from a script, since
"$pass" interpolates in PowerShell while '$pass' does not. On failure it
prints the authentication methods the server offered.
check.sh runs what has actually caught bugs here: non-ASCII characters,
"$name?" (? is legal in an unbraced variable name, so it renders empty -
this bit twice), parse errors, 5.1 syntax compatibility, and JSON validity.
Melissa's date folders hold .tiff and .txt. A leftover
insurance_file_type of "tif" matches neither - -Filter is exact - so the
run reported "nothing to send" on a folder with six files in it, which
is indistinguishable from an empty folder and is the same blind spot
that hid the .pdf/.tif mismatch for weeks.
It now names what is actually in the folder and which setting to remove:
Nothing matched .tif, but 20260826\ holds 6 file(s): 3x .tiff, 3x .txt
-> insurance_file_type is set to 'tif' in entity.json. Remove that
line to send everything, or correct it.
Nothing in this repo ever updated Melissa's PC, so "it isn't working"
could not be told apart from "she is running last month's copy" - which
is what it turned out to be today.
report.bat writes one text file to the Desktop with the installed
version, which files are present, whether WinSCPnet.dll loads or is
blocked, every entity.json (passwords masked to ********), what is
actually sitting in today's date folders, and the tail of the last log.
A missing VERSION.txt is itself the answer: it means the copy predates
2026-08-26 and has no setup wizard.