Raised by Lockstep.Replay.run/2 when the replayed schedule cannot be
faithfully reproduced from the recorded trace. Almost always means the
user code under test depends on uncontrolled nondeterminism — raw RNG,
system time, ETS interleavings inside non-yielding handlers, NIFs, or
real I/O.