It loads the copy under an old training directory, not the one beside the script, and that copy accepts the arguments in our documented check.

That is a useful lead; compare the actual method definition and package identification in both copies before changing the script, since a folder can have been renamed without its contents changing.

Can whoever supplied the training laptop identify that package for you, including whether you're meant to keep using it?

The training contact found the package they issued and its matching example, and the newer folder was from a separate evaluation; I have asked them to identify the supported combination for our controller before I hand this to the technician.

We now have their identified package on the rebuilt laptop, and our documented read-only check returns the same controller identity as the working machine; the handover includes the loaded path and environment as well as the script, which was the missing part.