the audit diff part is the real footgun here, because once replay and export are supposed to line up byte-for-byte, any hidden source of time or ordering jitter shows up as a false corruption signal. ui bugs are annoying, but a nondeterministic projection means you cant trust the audit trail, which is the whole point of having one. one thing that stood out in the excerpt is that they record both accepted and rejected transitions, that usually means the verifier has to be strict about tie-breaking and rejection reasons too, not just final state. if those reasons arent derived from the same canonical event order on every client, you get a board that looks consistent until someone tries to replay it later.