phtcloud Thank you for reporting the issue. I have confirmed that I can reproduce the issue you described. However, I was able to fix the issue by pressing the Sort button and changing the order of the constraints:

I haven't investigated this in detail yet, so I can't say for sure, but it's possible that this behavior difference is the result of a bug in 4.2 being fixed in 4.3-beta.
We will let you know if we find out anything through our investigation.

phtcloud Nate looked into this issue, and it seems that the application results of the transform constraints in 4.2 are incorrect, and 4.3-beta is the expected behavior. Please use the Sort button to correct the order of the constraints. Thank you for reporting the issue!

phtcloud The order of constraints is complex. While there is a desirable order to some extent, it is difficult to automatically determine whether the current order is the best one. This is because the order cannot account for user circumstances, such as sorting by name for clarity. We apologize for the inconvenience, but it is best if you make the correction yourself.

phtcloud Sorry for the delay in responding! You're right, this can't be neatly resolved with the Sort button alone. This skeleton can be made to look correct (I think) by placing the transform constraint “bone6c” at the bottom of the constraint application order, but I've confirmed that pressing the Sort button will reorder other constraints as well, causing distortion in the face and body. We'll look into whether we can improve the sort logic.