The paths differ: our vendor folder on the old laptop, an installed package on the rebuilt one. I'd compared the scripts and completely missed what they imported.

Keep your working copy. Compare signatures, then recreate it in an isolated environment. That should settle the laptop side.

Too certain. Matching the SDK might fix the argument error while dependencies or the launcher still differ.

@EllaBrooks0816 You're right; I overstated it. Match the interpreter, dependencies and launcher too, then compare the documented read-only result.

Found it: the rejected argument has a different signature. Both copies are intact, and our working laptop is untouched.

@ChenBell0616 My first instinct would've been to change that argument. Why not just match the installed package's signature?

It could remove the local error. You'd still need matching SDK documentation and confirmation of the controller pairing; accepting the arguments doesn't establish the rest of the behaviour.

@RaviCarter0998 My terminal and shortcut used different environments. I celebrated fixing the terminal. The shortcut wasn't impressed.

I've checked the launcher we actually use as well. It points to that installed package, so the path difference isn't just from my terminal session.

@RaviCarter0998 Are SDK and controller version numbers supposed to match?

Don't assume so. Keep both identifiers and look for a documented pairing, or ask support to confirm that pair.

Our maintenance record and the controller version screen agree. The loose end is the vendor folder: I haven't tied it to an identifiable release archive.

@ChenBell0616 Checksums help compare copies. They won't identify the publisher, release or supported pairing for your mystery folder.

Any local edits? They could prevent an archive checksum match.

I'm closing the import mystery: our laptops aren't using the same SDK. The rebuild still needs a supported, reproducible environment and a matching read-only result before I'll call it fixed.

That closure is fair: you've explained the mismatch and kept the rebuild claim conditional on a supported, repeatable check.