docs(site): check the example report line for line against its command - #23
Merged
Merged
Conversation
The build compared only the ECE line, while the README called the whole report "unedited" output. Every line is now compared with a fresh run of the recorded command, with only the generation date and the dataset path's separators normalized, and the README states that check instead. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
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 README called
docs/example-report.md"real, unedited output", and #21 hand-edited it. Until now the site build only compared the report's ECE line with a fresh run of its recorded command, so the claim wasn't enforced.What I found. A fresh run of the recorded command reproduces all 49 report lines exactly, latency included: the mock's latencies are simulated from its seed. #21's hand edits are identical to what the code now prints. Two lines would differ in CI or on another day:
Generated <date>and the dataset path, which the committed report wrote with Windows separators.The check.
build_site.pynow compares every line of the committed report with the fresh run, after normalizing only those two things. On any difference it refuses and prints the line number with both versions. Tested locally: changingp50 37.7msto37.8msis refused, and changing the date passes.Wording.
Daterow now matches itsGeneratedline (2026-09-22; the row said 2026-09-21).🤖 Generated with Claude Code