Repository navigation
Keep artifact verification bound to a stable contract - #42
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
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.
Artifact verification could report completion after the selected contract was replaced, deleted or edited during inspection. The CLI now binds regular-file identity and bytes for the check, and Workbench rechecks its own snapshot before accepting output or writing current history. Existing immutable history and the normalized v1 contract digest remain unchanged. The shared bounded reader also rejects a FIFO substituted after metadata inspection without blocking.
Validation: all eight original contract-race regressions reproduced before repair; the FIFO replacement timed out in a bounded child before repair. 709 tests passed, one existing skipped; typecheck, lint and build passed. Actual CLI/API/browser checks rejected replacement, retained input and old history, and passed mobile layout. No Skill execution, provider calls, release or deployment.