On a rebuilt logging laptop I would also preserve the working environment details before tidying folders, because deleting the duplicate first can remove the explanation you need.

The shortcut imports from a folder I had not been checking. Old laptop loads another copy. Exception names an unexpected keyword in the identity call; neither run has reached a connection attempt.

That reminds me of a sample I kept beside a newer package and assumed was current. Do your two copies come with matching examples, or is the script separate?

Would changing the shortcut to the old copy settle it, then? Or would that just reproduce the older environment without explaining the intended one?

It would be a comparison, not the final repair. Jamie needs the documented call for the copy they intend to support. Check its return contract as well as its accepted arguments, so passing the first line does not leave the status collector reading the wrong thing.

The script was separate. Its call matches the old package example, not the documentation shipped with the intended copy. I have kept both environment reports and changed only the read-only call in a test copy.

Does the test launch use the same account and shortcut environment as the actual collector?

It does now. The test returned the expected identity from our controller and handled a failed read without displaying it as current status. I repeated that through the normal shortcut after restart, with the loaded path recorded.

Good, that shortcut comparison was worth doing. Are the unused samples still somewhere they could be mistaken for the supported collector?