The old launcher uses its own environment. My rebuilt laptop starts the system interpreter.

That is a concrete difference. Check the module paths too, then have the maintainer identify the supported environment rather than bending the call around whichever package the system interpreter finds.

And don't call it a network problem just because the robot is at the other end, Ivan; an argument rejected locally hasn't tested that connection at all.

Different imported packages confirmed. Maintainer has identified the intended version and is preparing the supported launcher.

Keep the source and version in the exercise notes. Then repeat only the documented read-only check through that launcher; matching imports alone doesn't establish the check passed.

Understood. Launcher preparation is still pending, not a successful connection. Thanks for separating those checks.

That distinction will save the next person some faff, especially if the rebuild fixes the local argument error and reveals a separate connection issue afterwards.