Repository navigation
Add contract-driven native canary validation - #11
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.
Adds a manual-only, contents-read native validation workflow for exactly seven static-ready canary tools (14 native pairs). Includes deterministic plan/contract/fixture binding, bounded scientific checks, local OCI-to-SIF validation, schema-v1 identity, durable failures and exact terminal reconciliation. No publication path or package-write permission. Frozen reference factory and all 591 non-canary contracts unchanged. Local relevant suite: 765 passed. Full repository: 8307 passed, 13 skipped, zero failed. Ruff, actionlint and contract validator passed. Original local reference Dockerfile footprint commits deliberately excluded by basing this branch on origin/main.