Imported copy is beside an old classroom example. Not the folder I gave support.

Compare that with the working laptop before removing anything. Keep the exact exception and method signature too. A different location explains the confusion, but you still need to know which interface your unchanged script expects.

Does the exception name the argument, or merely say that the number of arguments is wrong? Please retain the original wording for the maintainer rather than summarising it as a connection failure.

Names a keyword it won't accept. Support has the full exception, not my earlier 'won't connect' description.

Has support matched the working method to its documentation now? Don't rename that keyword on a hunch. It could get past this error and read something you didn't intend.

Matched. Different documented signatures. Maintainer is rebuilding from the working environment's identified package, keeping the classroom copy apart.

Who owns the teaching examples after that? We had two tutors each keeping a helpful spare copy, then nobody knew which one a student had launched. Removing today's stray copy won't stop that happening again.

Priya, did you retain the examples as separate environments or make them use the teaching cell's supported package? I can see reasons for either if the lesson deliberately demonstrates an older interface.

New environment imports the intended copy. Identity read works. Normal desktop shortcut still needs checking.

Separate archived environment for the old lesson, Will. Normal classes use the maintained one. The snag was that the archived shortcut looked like the everyday shortcut, so we changed the labels and the tutor's opening check too.

The normal shortcut is worth checking with the ordinary account and working directory. I have seen a console test succeed because the person testing it had already selected a different environment. That selection was never part of the shortcut.

Desktop shortcut still points to the classroom directory. Console success was real, just not how students open it.

There it is. Has the maintainer corrected that launch too, or only explained it?

Keep the imported location visible in the diagnostic output after this is fixed. It is cheap information to collect and would have shortened this conversation considerably.

Corrected. Ordinary account, desktop launch, intended module and controller identity all agree. Thanks for insisting on that launch.

Tutor owns the normal example now. Archive has a separate label; its shortcut isn't beside the daily one.

That closes the mismatch you reported. Keep the working environment description with the teaching material so the next rebuild starts with an identified dependency, not a hunt through folders.