well…
might not be the exact same bug, but it seems to have happened again, even after NodeBB reverted the Conversation type back to an OrderedCollection…