Prepare alpha.4 AC-014 verifier handoff - #59
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
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 changed
Why
Fix14 narrowly exceeded the unchanged wall ceiling after stale copied paths and a verification outcome was leased to the maker. This change makes relocation and Evidence preflight explicit, gives verification a distinct sealed lease, and measures the one-shot arm from an exact candidate SHA.
Validation
flow.rshub growthRemaining gated work
Remote Linux CI must produce fresh x86_64 and arm64 portability receipts for commit f14bfd2 before the one-shot AC-014 verification begins. Release publication remains blocked on a passing benchmark, release evaluation, exact-candidate approval, and post-publish smoke checks.