Repository navigation
refactor(automation): separate evaluation parsing and node policy - #405
Merged
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
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.
Browser evaluation validation now separates expression parsing and node rejection policy from traversal. The exported validator retains parse-before-allocation, lazy property reads, mutation-error precedence and traversal-before-root validation.
Validation: 16 owning tests in three files, automation build/typecheck/lint, and the full enabled pre-commit gate passed. The default public provider exercised 12 literal cases over a real owned WebSocket with a simulated CDP peer; all full results and 52 request/response frames matched the original. The peer did not execute JavaScript.
The file is 496 lines (previously 488); the validator is 48 lines (previously 85). Added private helper calls change stack frames; no performance or stack-trace identity claim. No tests, exclusions, defaults or public API changed.