Old shortcut imports the copy beside a classroom example. New laptop imports the installed package. The call signatures differ. I have asked our maintainer which documented package the delivered setup should use.

Keep the old working environment intact while they answer. It is useful evidence, not necessarily the package you should copy into another year's handover.

And check the shortcut itself after the change. A correct environment cannot fix a launch into another folder.

Maintainer identified the intended package and its documentation. Script updated to that contract; the old environment remains separate. The normal shortcut now imports the intended copy, with the actual read-only comparison still due.

Useful progress. Has someone else tried that normal shortcut from their own sign-in, or will that be part of the remaining comparison?