bench provenance: -dirty on every commit line when the tree differs from HEAD (#186) - #233
Merged
Conversation
…m HEAD — closes #186 The 2026-08-15 rust-read CSVs recorded a clean-looking commit while measuring uncommitted work, which cost the later archaeology its premise. commit_of now appends -dirty (git diff-index against HEAD, tracked changes) for schema and every sibling runtime line, and §3.5 requires it. Proven both directions live: a clean sibling prints the bare sha, the working clone carrying this very edit prints -dirty. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
2 participants
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.
Closes #186.
commit_ofappends-dirty(git diff-index --quiet HEAD, tracked changes only) to the schema line and every sibling runtime line, and BENCH-STANDARD §3.5 now requires it — a sweep of uncommitted work says so in its own preamble instead of leaving a clean-looking sha for a later archaeology to trust. The §3.5 path verifier is untouched (it proves paths, not sha strings — checked). Controls: clean sibling → bare sha; the clone carrying this edit →-dirty.bash -nclean; the x86 sweep (#218) flagged the same hole independently.🤖 Generated with Claude Code