A test read refuses a run whose outcome-neutral battery did not hold¶

# research(2026-10). The halt rule ("any outcome-neutral test failing halts the study") was enforced on the unplanted runs only for leakage, which writes halted into a run and partitions.partition_run_windows refuses; a failed positive control, manipulation check or non-degeneracy check was recorded in the run's battery and never read. Registered-report guidance applies a registered exclusion rule by the procedure fixed at Stage 1, never case by case (the TU Delft and JBEF Registered Reports guidelines), so the gate now does it: every run a test read takes must carry a battery that held (neutral.recorded_battery, neutral.battery_holds), the likelihood rescorings through the generation run named in scored_from, and cells.require_test_read refuses a report that does not record one for every run file. A rescoring borrows the battery only of the run it scored (neutral.SCORED_IDENTITY: model, rank, seeds, training size, corpora), and a planted run, check 5's, is refused as one of H1's runs. A development read records each run's battery without refusing. All 46 unplanted development runs resolve a battery that held, so no reading changes.