chore: adopt public chrono-harness beta.19 binaries - #12
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.
Adopt the public chrono-harness v0.1.0-beta.19 binaries for ordinary updates and align the README current-release references. The lock uses the published manifest and installer hashes; the initial profile, scoped DELTA policy, Git policy and generated macos-14 workflow bytes remain unchanged.
Anonymous macOS arm64 installation succeeded and all six installed binary hashes/sizes match the public manifest. The registered workflow verifier passed, and the clean fixed candidate passed the canonical ordinary DELTA check: inventory passed, zero selected business plans and zero business operations.
The parentless root 4ee7954 retains its beta.5 lock and original evidence. This parented upgrade runs ordinary base/candidate checks; it does not claim a new initial inventory, full governance, complete input closure or environment parity.