The paths differ. Rebuilt laptop loads an older SDK from a copied exercise folder before the supported package. I've kept that folder intact for comparison and asked our maintainer to correct the operational import path.

Has the same documented call then succeeded, without dropping the disputed argument?

It now imports the intended SDK and passes local argument validation unchanged. The controller read still times out, so the import problem is fixed but the end-to-end check isn't. Network and service comparison is a separate open investigation.

Keep those two findings separate in the rebuild note. Local validation passing is not controller communication working.