Repository navigation
Conversation
The README described the ungraded count but not that save() writes it, nor the top-level version key. A reader of the file now finds both next to the paragraph that already explains passed, failed, errors and ungraded.
This branch has not been deployed
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.
#132 added a top-level
"version": "1.0"toAuditResults.to_dict(), and #135 addedsummary.ungraded. The README explains theungradedcount but does not say thatsave()writes it, and it does not mentionversion.This adds one paragraph covering both keys under "Understanding Results", next to the existing paragraph on
passed + failed + errors + ungraded. Nothing else changes.The rule for
versioncomes from #114: "bumped explicitly whenever the serialized shape changes".AI disclosure: implemented with Claude Code.