The rebuilt FR10 laptop imports a copy from the handover folder

Would comparing the two desktop shortcuts be a cheap place to start, Felix, since that was where our technician hid the interpreter choice?

Yes, including their working directories. But capture the running process too. A shortcut can launch another script which changes the import path.

The shortcuts do launch different interpreters, and the working laptop imports from a separate environment, so our supposedly identical folder copy was never the whole setup

Can the person who prepared the handover explain why that spare SDK copy was included, because leaving two plausible copies without a note is a decent way to waste the next person's morning?

He included it as an archive, then the rebuilt shortcut put that archive on the search path; he has owned the mistake and is checking the supported environment against the controller information

Archive found. Is the rejected argument actually absent from that copy's signature?

And compare the documented call for the intended package. Removing an argument until the error goes away could silently change what the check asks for.

I nearly suggested exactly that, take the extra bit out and see, but yes I'd want to know what that bit meant first

David, the archived copy does lack that argument, while the intended package and its matching documentation agree with our unchanged call; support has confirmed the intended package for this bench

What will maintenance receive now, an environment they can restore or another folder called final?

A recorded launcher, dependency versions and package origin would be useful. They should be able to reproduce which code runs without knowing this discussion happened.

We have rebuilt the environment from the recorded package, corrected the launcher and moved the archive out of its search path; the argument error is gone, although the actual read-only check still needs its bench slot

Thanks for checking the signature, not just the folder name.

Naomi, does the handover also say which shortcut to use, because two similar desktop icons will undo a surprisingly good explanation?

There is now one labelled maintenance launcher, Lin, and our normal read-only connection check has passed from it with the expected controller identity; a second electrician reproduced the setup from the handover without my old laptop beside him

Good. The second electrician reproducing it is the part I'd want in the handover acceptance, not merely your successful run.