Regenerate the parity matrix and baseline status from plan v26 #15
Loading…
Reference in a new issue
No description provided.
Delete branch "baseline-v26"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Scope
This is the post-merge refresh after #10–#14, with no code changes. It regenerates three files from plan v26, which is cut from main
e736978:docs/G1_PARITY_MATRIX.jsondocs/G1_PARITY_MATRIX.mddocs/G1_BASELINE_STATUS.jsonThe plan was cut with
--control-observer-ready --physical-output-source-ready --lfoa-modulation-ready. All four baseline worker shards and the full probe sweep were run against it.Testing
python3 -m unittest discover -s tests: 150 tests OK.tools/export_public.pyinto an empty directory verifies clean.23ba636.23ba636ande736978.e736978, and its three probes still pass, with error near 0.Probe verdicts
Parity stages
Stage moves from v25 to v26 are all upward, with no module dropping a stage:
Pass → fail check
Baseline status: 109 of 109 modules completed (106 completed and 3 unobservable before). Midpoints with signal on both engines rise from 104 to 107.
Impact Statement