Repository navigation
fix: require explicit parity evidence for SDK facts export - #40
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.
Missing audit rows previously became MATCH* exports, and struct inference could include unaudited source declarations. Require unique manifest/source identities and explicit recorded EXACT/RELOC evidence across all three SDK exports, apply the existing purity and class-label policies, reject conflicting inferred layouts, and abort if eligible source bytes change during inference.
Select the current checkout by default, support an explicit --root, and make sibling copying opt-in with --mirror-dir. Every payload documents its assurance limits: legacy audits do not establish current source/dependency freshness, behavioral certification, signatures or independently proven layouts. Source hashes identify only the exported snapshot. Existing SDK JSON remains unchanged and is labeled historical in a new README.
Validation: 18 synthetic regression tests plus 13 subtests passed, including reproduction of the missing-audit false export before the fix. The broader source-only Python suite passed 196 tests and 135 subtests (33 skipped, 10 deselected). README consistency and documentation-link checks passed. The native owner independently reviewed the exact exporter, tests and contract hashes and found no blockers. No real SDK export, private source/proof read or sibling mirror write was performed.