Advance the real-project-v2 candidate registry to Bifrost v0.10.8 - #192
Merged
Conversation
The v2 slice's execution identities are frozen in a versioned registry, and the registry the freeze selected still pinned Bifrost v0.10.2 -- so every v2 freeze re-measured the analyzer of a month ago by construction. The slice's own README states the doctrine for moving forward: a later Bifrost run is evidence for a subsequent release, never a replacement for v0.3.0 evidence. `candidates-v0.3.4.json` is that subsequent identity set. It advances the measured Bifrost to v0.10.8 at `8ddf1362`, the same identity the active development registry pins, and changes nothing else: every reference-server identity is byte-identical to the v0.3.0 registry, and the corpus, protocol, selection, and reviewed ground truth are untouched. `candidates-v0.3.0.json` stays byte-identical as the immutable record of what v0.3.0 measured. The freeze workflow selects the new registry for evaluation snapshots. Shard identities hash both registries and read candidate identity from the current one. The reproduction contract now asserts the superseding registry's Bifrost matches the active development pin and that no non-Bifrost identity moved, alongside its existing assertions that the historical registry is unchanged. Expected effect on the next v2 freeze, from the repository-tree measurement under v0.10.8: 12 of v0.3.0's 17 failures resolve, 5 remain (#181, #182, #183), none appear. The freeze that publishes this is the real acceptance test, and its aggregate counts -- not this prediction -- are what the release approval should be checked against. Requires the scan-budget capability fix (#191), without which a v0.10.8 evaluation freeze would error every usage scan. Closes #185 Co-Authored-By: Claude Opus 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
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.
Closes #185, recast: the published v2 result understates Bifrost not because a
re-freeze is missing, but because the slice's frozen candidate registry still
pins v0.10.2 — every v2 freeze re-measures last month's analyzer by
construction (v0.3.2/v0.3.3 demonstrated exactly this). The slice's own README
states the doctrine:
The change
candidates-v0.3.4.json— a new frozen identity set, not an edit:8ddf1362, the same identity the activedevelopment registry pins.
identities, profiles, hashes. The corpus, protocol, selection, and reviewed
ground truth are untouched.
candidates-v0.3.0.jsonstays byte-identical as the immutable record of whatv0.3.0 measured.
Consumers: the freeze workflow selects the new registry for evaluation
snapshots; shard identities hash both registries and read candidate identity
from the current one; the reproduction contract asserts the superseding
registry's Bifrost matches the active pin and that no non-Bifrost identity
moved, alongside its existing guard that the historical registry is unchanged.
Tests cover the "advances only the Bifrost pin" property directly, in both the
Python and Rust suites.
CITATION.cffmoves to 0.3.4 for freeze preflight.Expected effect on the next v2 freeze
From the repository-tree measurement under v0.10.8: 12 of v0.3.0's 17
failures resolve, 5 remain (#181 ×2, #182 ×2, #183), 0 new. The freeze is
the real acceptance test — please check the aggregate's counts against this at
the release approval gate rather than taking the prediction on trust; in
particular, any
reason=time_budgetdiagnostic means the scan-budget fixregressed and the run should not be approved.
Depends on #191 (merged): without the capability fix, a v0.10.8 evaluation
freeze errors every usage scan.
Verification
cargo test --locked— 257 passed (1 new), 0 failedvalidate-reproduction-contract.sh— exit 0🤖 Generated with Claude Code