MAV-MCC / LHCb Request #91 — JUDGE Run #1 Interruption Audit and Deterministic Run #2 Relaunch Record

Technical recovery and relaunch record for the MAV-MCC / LHCb Request #91 H1 JUDGE execution. The primary scientific freeze for this analysis was previously published as DOI 10.5281/zenodo.22650072 and is not modified by this record. During the first JUDGE execution, an unplanned Windows update caused the analysis laptop to reboot before any JUDGE verdict was produced or inspected. The interrupted workspace was preserved byte-for-byte before any relaunch action. A complete 400-file snapshot matched the original workspace in file count, total bytes and per-file SHA-256: PASS_400_OF_400_SHA256_MATCH The interrupted execution is therefore classified as: JUDGE RUN #1 = INTERRUPTED / NO RESULT A separate interruption manifest and relaunch manifest were generated before Run #2. The original STEP5 execution package, execution lock, launch lock, scientific freeze and event-split manifest were re-verified. The recovery self-test passed with no scientific changes. Run #2 is authorized only as a full restart of the frozen pipeline from VALIDATE through automatic JUDGE, using the original locked code, configuration, hashes and decision rule. No partial JUDGE computation from Run #1 may be resumed or reused. At the time of this public deposit: Run #2 has not yet been launched. No JUDGE verdict is known or included in this record. This record documents technical provenance only. It does not alter the frozen H1 hypothesis, statistic, null construction, thresholds, PASS/FAIL rule, dataset split or interpretation boundaries defined in the primary scientific freeze.