I rebuilt the maintenance laptop and our read-only FR10 response-inspection script now rejects an argument locally. The old laptop still runs it. Several SDK folders are present and nobody recorded the loaded copy. What comparison will tell me which environment I am actually using?
We had an old shortcut launching a different environment after a rebuild. Record the actual interpreter and imported module path from each running script, plus version information and the documented signature of the failing method. Folder names alone won't establish the loaded copy.
The paths differ. The new launcher imports a copy from another SDK directory, and its method signature differs from the one on the working laptop. I have left the controller settings alone.
That explains the local rejection more directly. Compare both copies against the controller's supported combination before selecting one, then record how the launcher chooses it. Did the maintenance handover include those compatibility details anywhere?