Repository navigation
test(projects): retain published snapshot SDK reproduction - #182
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.
Retain a reproducible invented-data check of the published Core0.373 snapshot SDK, with exact package/source/runtime/integrity metadata. The registry tarball matches the validated CI artifact byte-for-byte.
The driver checks alias provenance, stable repeats, proposed-state preservation, source-body/path omission, strict fields and missing/implicit-store refusal through public SDK exports. No owner data, provider login, model or existing store input is used. This is selected-snapshot acceptance, not a retrieval/restore score or full project backup. Link it from the project index/process; actual limits and reproduction command are documented.
Passed: published-package synthetic driver, focused lint, docs checks. Existing PR/main gates remain unchanged; this adds no routine CI suite or library runtime code.