Status Summary
At main commit 58a730a26ab6f82e5eaa5b66c124cc130c42a82c, newly added codec-regression-v1 paths run through the official candidate binding. Candidate verification is still selected from Git paths classified as added. Policy evolution permits adding fixture selectors, so a tracked fixture that existed outside the base selector can become newly counted evidence through a policy-only selector expansion without being classified as an added path. A rename into a selected path has the same gap when Git reports it as a rename. With no guarded implementation change, the newly admitted evidence can increase the corpus without candidate execution.
How to fix
Derive candidate-verification paths from codec fixtures newly admitted relative to the base policy and inventory, not only from Git added-path status. Run every such Python fixture through the official candidate binding. Preserve defective-base failure as the additional requirement for guarded codec implementation changes.
Acceptance Criteria
- A policy-only selector expansion that admits a pre-existing codec fixture runs that fixture through the official Python candidate binding.
- A rename or move into a selected codec fixture path cannot bypass candidate execution.
- Newly admitted evidence that the candidate runner cannot load or execute cannot increase the corpus.
- Valid fixture-only growth remains supported, and guarded codec changes still require candidate success plus defective-base failure.
- Focused tests cover selector expansion and rename/admission paths.
Delete when
Delete when every codec-regression-v1 fixture absent from the base evidence set but admitted by the current policy passes official candidate execution regardless of Git path status or selector evolution.
Status Summary
At
maincommit58a730a26ab6f82e5eaa5b66c124cc130c42a82c, newly addedcodec-regression-v1paths run through the official candidate binding. Candidate verification is still selected from Git paths classified as added. Policy evolution permits adding fixture selectors, so a tracked fixture that existed outside the base selector can become newly counted evidence through a policy-only selector expansion without being classified as an added path. A rename into a selected path has the same gap when Git reports it as a rename. With no guarded implementation change, the newly admitted evidence can increase the corpus without candidate execution.How to fix
Derive candidate-verification paths from codec fixtures newly admitted relative to the base policy and inventory, not only from Git added-path status. Run every such Python fixture through the official candidate binding. Preserve defective-base failure as the additional requirement for guarded codec implementation changes.
Acceptance Criteria
Delete when
Delete when every
codec-regression-v1fixture absent from the base evidence set but admitted by the current policy passes official candidate execution regardless of Git path status or selector evolution.