Verify recovery equivalence against an uninterrupted execution

Recovery-specific bookkeeping and volatile runtime observations such as checkpoint reuse flags, timestamps, timings, messages, and execution-engine metadata are intentionally excluded. Scientific results, inputs, samples, variants, configuration, context, artifacts, plan identity, module order, and terminal outcomes must remain deterministic after canonical serialization.

Usage

verify_runtime_recovery_equivalence(reference, recovered)

Arguments

reference

A complete uninterrupted analysis execution result.

recovered

A complete execution result resumed from a checkpoint.

Value

A `PopgenVCFRuntimeRecoveryEquivalence` verification report.