Possible good news - Claris is reporting that they have identified and (possibly) fixed one of the critical bugs, and are doing beta testing now, and hope to have the fix in the next release (this was from 2 weeks ago: Link)
Engineering has worked with a few impacted customers, and has identified some fixes that resolve the issue for those customers. Because of the specific nature of the problem, we are not yet 100% confident that the issue is resolved for every customer in every circumstance. However, it's resolved for every case we are able to test against currently.
A build with these changes has been made, and provided to Customer Care for distribution to any affected customers. The changes will be in the next public releases as well. We'll continue to test to see if we can uncover any other scenarios where the bug surfaces.