Repository navigation
Refresh harness baseline for the merged signature tests - #3
Merged
Merged
Conversation
The military-signature P0/P1 tests (tests/test_signature_p0.py: 32, tests/test_signature_admission.py: 13) arrived through merge bef43c9 without the human-only baseline refresh that CURRENT_STATUS.md flagged as required. The canary correctly failed red (723 vs 678 cast, 756 vs 711 baseline). This is the owed refresh, regenerated by the user-authorized scripts/refresh_harness_baseline.py run in the main checkout at bef43c9. Both graded selections verified green after the refresh: cast 723, baseline 756. Frozen-file hashes unchanged (7 files). Note: the line-by-line review of the two merged signature test files flagged by experiments/military_signature/CURRENT_STATUS.md remains owed before their next suite change.
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.
What
The canary baseline refresh that PR #2 needed: the 45 signature tests (
tests/test_signature_p0.py: 32,tests/test_signature_admission.py: 13) arrived on main via PR #2 without their human-only baseline refresh, so both CI jobs fail the count canary:This PR regenerates
tests/harness_baseline.jsonviascripts/refresh_harness_baseline.py(measures both environments in isolated uv subprocesses) at the merged tree: cast 678 → 723, baseline 711 → 756. Exactly the two count lines change; frozen-file hashes unchanged.Verification
Both graded selections verified green locally after the refresh (cast exit 0, baseline exit 0). Accounting: 723 − 678 = 32 + 13 signature tests, nothing unexplained.
Still owed (unchanged by this PR)
experiments/military_signature/CURRENT_STATUS.mdbefore the merge); summaries prepared indocs/CODE_REVIEW_PENDING.md.cast4b/joint-metric-fixtures) will need its own same-commit refresh (+12 tests) when reviewed and merged.