Verify deterministic replay equivalence across execution backends — verify_cross_backend_replay

Backend-specific scheduling telemetry, worker identities, completion timing, and elapsed-time observations are intentionally excluded. Scientific state, accepted-result order, plan identity, artifacts, terminal outcomes, and canonical ledger semantics must remain deterministic.

Usage

verify_cross_backend_replay_equivalence(reference, candidate)

Arguments

reference: A complete execution result from the reference backend.
candidate: A complete execution result from another backend.

Value

A `PopgenVCFCrossBackendReplayEquivalence` verification report.