Add deterministic recipe parser fuzz gate - #54
Merged
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
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.
Summary
RecipeValidationErrorcategories, canonical identity, reproducibility, and iteration budgets.check.v1optional tolerance validation sois_closewithNonefails closed asinvalid_checkinstead of leaking anAttributeError.Why this is needed
Parser fuzzing is an explicit Phase 2 release gate. The first 2,000-case run found a real edge-case defect in the
tolerance: Decimal | Nonevalidator: aNonevalue called the non-optional decimal validator and escaped as an uncaughtAttributeError. The optional validator now preserves the typed contract and the regression test locks the stable failure category.Validation
--iterations 2000 --seed 20260728 --json --strict): 158 accepted, 1,842 rejected, 0 unexpected exceptions.compileallandgit diff --checkpassed.Release-gate status
This closes deterministic parser-fuzz evidence. Artifact security review, resource/watchdog accounting, external review, and production lifecycle health/wiring remain explicit blockers before provider enablement.
Cortex.pyprojwas intentionally excluded because it contains an unrelated user edit.Builds on merged PR #53.