@OliverChen1146 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.

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

I've found a signature difference exactly where the argument is rejected. Both SDK copies are preserved, and our working laptop is still untouched.

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

It might pass the argument check. You still need that SDK's documentation and a confirmed controller pairing to establish the rest.

@OliverChen1146 The different import paths give me a useful starting point. I still haven't established the supported environment we need to finish the rebuild.

Different imports are a useful lead. Keeping the rebuild open until the supported environment is established matches what you've found.