A date range over a record field, which the corpus missed - #73
Merged
Merged
Conversation
… missed The corpus's date case remembered a scalar date and compared it. The shape a consumer actually writes is a date *field on a record* compared to a literal — `filter the events where starts-at is not below 2026-01-01` — and that goes down a different path in the analyzer. Found by porting: the TypeScript validator passed the corpus's date case and still refused the record-field form with "Unexpected value in condition", because the two operand paths are separate and only one had been taught about dates. Which is the same blindness one level up. The word-list gate could not see a behaviour change; a behavioural corpus cannot see a shape it does not contain. Coverage of the vocabulary is not coverage of the grammar, and the coverage gate only checks the first. 41 cases. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E6qcDj1e1dEYvc8jLnpGZy
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.
The corpus's date case remembered a scalar and compared it. The shape a consumer actually writes is a date field on a record compared to a literal:
That goes down a different operand path in the analyzer.
Found by porting. The TypeScript validator passed the corpus's date case and still refused the record-field form with
Unexpected value in condition, because the two paths are separate and only one had been taught about dates.Which is the same blindness one level up. The word-list gate could not see a behaviour change that added no word. A behavioural corpus cannot see a shape it does not contain. Coverage of the vocabulary is not coverage of the grammar — and the coverage gate only checks the first.
41 cases. The generator and the three staleness gates are unchanged.
🤖 Generated with Claude Code
https://claude.ai/code/session_01E6qcDj1e1dEYvc8jLnpGZy