fix: name consistent with spec and test files - #402
Draft
vjaganat90 wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
test: honest oracle-vetting taxonomy and registry cleanup
Rename mislabeled tests to SPEC kinds (oracle / regression / mechanics), fold the 3D
_coveragesweep into_regression, and split real oracle goldens out of regression files (e.g. GLCM PyRadiomics, IH analytic, firstorder analytic/matlab). Run an honest registry sweep: keepstatus=vettedonly when a dim-correcttest_*_<oracle>body actually covers the feature—demote filename-only links, empty shells that#includeregression, and 3D rows falsely pinned to 2D IBSI (all3GLDZM_*/3NGLDM_*). Headline coverage becomes ~471/758 vetted (was ~620 inflated). Tightencheck_coverage.pyso CI rejects shell/filename-only “oracle” evidence. Analytic closed-form remains a first-class oracle token. Generators unchanged (out of scope).