I have matching scripts on the old and rebuilt laptops, but the rebuilt one rejects an argument before contacting the controller; there are several SDK folders and no import record, so I want to compare the running environments before somebody edits a working read-only check to fit whichever copy happens to load.
Record the interpreter, imported module path and actual method signature from each running environment, including the ordinary shortcut. Folder names won't tell you whether either copy matches the package handover.
Old shortcut loads the handover environment; rebuilt laptop loads a similarly named SDK from the script directory, and the signatures differ. Maintainer is checking the package identification rather than choosing by folder date.
Keep the working laptop intact while they do that. We nearly lost our only useful comparison by tidying both machines at once, which was efficient in entirely the wrong direction.
Interpreter and package both identified from the handover; the rebuilt environment now matches and the normal shortcut returns the expected controller identity. The unrelated SDK is outside this script's import path.
Covering maintainer repeated it after signing in again, using the normal shortcut, and recorded the same loaded path and identity; thank you, Callum, that is now our completion check rather than my successful terminal run.
Linked from the bench desktop beside the identity-check shortcut, with the environment restore information and package reference; the old unlabelled instructions are archived, so nobody has to pick the most promising folder name.