our rebuilt fr5 laptop rejects a call the old shortcut accepts

The rebuilt shortcut imports from a training folder. The old one imports from our integration folder. We have the paths now but haven't compared the versions or call signatures yet.

Compare those with the full argument error and the applicable documentation for each version. Keep the working setup intact while the owner establishes the intended supported combination. The absence of a connection attempt makes controller settings a poor first suspect.

Who will own that supported combination after the laptops are rebuilt again?

Felix, worthwhile, but Hana needs the current compatibility answer before someone writes use the old folder into a permanent instruction. Old and working are not a complete specification.

Our maintainer owns it. They've identified different argument signatures in the two copies, so we're checking which documented version belongs with the installed setup before choosing the correction.

Include the wrapper in that choice. A supported SDK with a wrapper written for the other signature will leave you with the same argument failure in a better-labelled directory.

The intended SDK and wrapper combination is now identified. The rebuilt shortcut has been corrected to use it and the argument error is gone. The controller read still needs repeating.

Will the handover retain the exact launcher, interpreter and module version alongside that wrapper?

Yes, with the read-only check and expected response interpretation. Thanks Sarah for starting from the actual shortcuts. I'm leaving the result at local call repaired until the installed read is checked.