fix(eval): verify Markdown arrow citations - #1
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.
The question grader rejected correct file-and-line citations separated from their exact quoted contents by a Markdown arrow. Accept Unicode and ASCII arrows while retaining the existing fixture-based checks for file existence, line number, exact text and complete occurrence coverage.
Validation: lint and 1,411 runtime tests passed; script suites passed 100 tests with one existing skip after making the worktree's web dependencies available. Negative controls reject wrong files, lines and invented strings in both arrow formats. The preserved live answer passes a supplementary regrade; its original failing result and the running baseline's frozen grader remain unchanged.
Keep this separate from the ongoing baseline until its frozen run completes. No runtime deployment is required for the grader change.