Repository navigation
eval: commit pdf-inspector-eval runner + REPORT (artifact placement) - #40
Merged
Merged
Conversation
The 2026-09-02 pdf-inspector benchmark REPORT named its own reproducibility artifact path as eval/pdf-inspector-eval/ in this repo, but the runner never landed here -- only the narrative report lived in the docs repo. Extracted the embedded runner.py + build_corpus_extra.py + manifest.csv from the report's own §11 (Reproducibility) and verified byte-for-byte against the SHA-256s the report recorded when it ran: build_corpus_extra.py 157d47bc995224188622a4a9b444990ab944d75e063fa4078e9cf00a014f86ce (match) runner.py e5a25ebf0b76afb2da91933300bb79eebd543907ccd4c93a81258aca60395222 (match) manifest.csv is regenerated output (build_corpus_extra.py writes it) so a byte-diff there isn't a fidelity signal.
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.
Docs/eval-only, no code changes. Closes the artifact-placement gap the 2026-09-02 pdf-inspector benchmark REPORT's S5 grade was marked UNDER for: the report named its reproducibility artifact path as
eval/pdf-inspector-eval/in this repo, but only the narrative report lived in the docs repo. This PR landsrunner.py+build_corpus_extra.py(extracted from the report's own §11 and SHA-256-verified against the report's recorded hashes — both match exactly) +manifest.csv+REPORT.md.Opened by the pdfmux evolve-product pipeline, ledger item
2026-09-02-eval-artifact-placement.