Integrate v0.9 common-population runners and evidence capture - #274
Merged
Merged
Conversation
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.
The v0.9 population is already registered, but the Swift runners still bind their Swift-only population, legacy adapters write fixed report paths, and freeze assembly omits the four opaque Swift cases outside
cases/. This integration gives the new release its common-population wrappers and isolated evidence capture, while preserving historical runner and evidence bytes.The prospective execution contract maps 84 serial groups to 92 reports under the exact 1,108-case revision. It records explicit child environments, keeps all new CodeQL partitions on 2.27.1, and preserves failed attempts. Execution remains disabled until the exact merged harness, query qualification, runtime identities, resource reservation and final plan review are bound.
Validation: all 286 Rust tests, formatting, optimized build, selected-population validation (1,108 cases), retained-report validation (92 reports), and argument parsing for all 84 planned commands pass. Focused Python integration checks cover population projection, capture provenance, contract mutation and environment selection. No release matrix run, freeze or publication is claimed by this PR.