Which SDK copy is our working FR10 shortcut actually loading?

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.

Does the handover identify the working interpreter too?

And compare the invocation, Aisha. A script launched from the right terminal can still have a desktop shortcut pointing somewhere else.

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.

Can the covering maintainer reproduce that from the revised notes after a fresh sign-in?

Callum, yes. Otherwise the handover is still Aisha's memory with a folder attached.

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.

Where does the next maintainer find those notes?

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.