APVTS, UndoManager, thread safety

It seems to me that calls to APVTS::copyState() (through flushParameterValuesToValueTree()) may cause a race condition on the undoManager, any time it’s called from a non-message thread while an action is being performed. This may come from the outside but also from the inside when an action is undone -then it also affects the tree. I don’t think I’ve hit this and it’s a tiny window, just seemed worth to mention.