OK, where would I forward it? Attach to this thread?
Ultimately the demonstration should be as simple as making a child VI reentrant and setting up a parent VI to run it a couple of times using the Call Async and observing that sometimes it is called as a clone, and other times it's not (e.g. it's just called as a traditional VI with shared state across the callers) depending on some sequence of editing, saving (as older version), and running the parent.
I have also seen the issue with Actor Framework actors not behaving correctly, probably for the same reason (because under the hood, AF should be calling multiple reentrant Actor Cores asynchronously as clones but is instead calling the same instance).
As mentioned in the original post, this appears to happen when the editor/app is 2024 but the save version is older. This is the case with my project as well, but I have not yet found time to confirm that if I update the save version to 2024 then the issue goes away. The issue does NOT occur when I use LV 2023 app to run VI files saved in 2023 format (which is how I'm able to continue my work now unimpeded by this issue).
