Paths differ. The rebuilt laptop imports a teaching copy from beside the script, even though the supported SDK is installed in its environment. I hadn't considered that local folder part of the launcher problem.

Keep the teaching copy out of the operational import path. Don't edit away the rejected argument until the call happens to run; compare the intended request with the supported signature first.

And repeat under the saved shortcut, Bruno, since a terminal using the right interpreter can still leave the ordinary launch importing that neighbour folder.

The supported signatures agree with our unchanged call. We separated the teaching folder and corrected the shortcut's working environment. Both launch routes now import the same identified SDK; the controller check is next.

Documented read-only check succeeds from the normal shortcut after reopening, with the intended controller identified. We recorded the interpreter, module path and SDK reference beside the exercise. No controller changes or argument removal needed.

Include the local-folder shadowing in the rebuild note. Installing the correct package was not enough here, and the next person could otherwise repeat the installation several times with great determination.