Repository navigation
test(review): add the revert cases' fixture archives - #13225
kyle-sexton wants to merge 2 commits into
Conversation
Closes #12939 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Held. This PR holds only the 16 |
|
Hold update. Q10 is answered: option (a), commit no binary fixtures (owner, recorded in melodic-software/architecture#28, relayed by the hub). This PR stays held under |
|
Superseded by #13299, merged 2026-11-04T18:44:47Z, which builds the revert cases from text fixtures. Owner decision Q10 (a): no binary fixture archives are committed, so this PR will not merge. |
Closes #12939
Summary
Part B of the split of #13097: only the 16
fixtures.tar.gzarchives the revert cases scaffold from. They are binary, so the review lanes count them but cannot read them. Held until the owner answers the open question on review gaps for binary-only pull requests (Automation Lanes' Q10).Fix
Adds one
plugins/review/evals/revert-*/fixtures.tar.gzper case. Each holds byte copies of the files at the commits itscase.yamlnames, plus the original commit message as the pull request context.Verification
A verifier agent scanned the unpacked files of all 16 for home paths and token shapes and found none; the only account-linked text is public commit metadata and session URLs already in public history. The contents can be read from the commits each
case.yamlnames, and the results are in part A. One case ran through the harness from its archive: VALID.Left out: review-lane coverage of the archives, which is the question this PR waits on.
Related
Draft: waits on the owner's answer to the binary-only review question
🤖 Generated with Claude Code