Repository navigation
test(drive): record published AI extraction and dependency proof - #90
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.
Record fresh npm Drive 0.12.2 extraction validation with exact Core 0.294.0 / Base 0.35.0 pins. The executable runner now checks the final quote-permission wording, runtime dependency versions and one Base instance; published results include compiled hashes and npm integrity values. Historical baseline and local-candidate results remain explicitly separate.
Fresh npm results: 59 CLI commands and 12 loopback provider requests pass for preview, tab isolation, scoped proposals/review, invalid or failed responses, guards before network and a real sync during extraction. Real model quality, factual entailment and accepted-fact freshness are outside this test. No owner account, store, document or model credential is used.
Validation: baseline and packed-candidate reruns, fresh npm executable run, targeted Biome, docs:check and staged secrets all pass. Drive’s released source separately passed 195 tests, contracts/upgrades, standards/generation/leak checks and Node/Bun installed acceptance. Both Core and Drive publishing workflows completed successfully; the report links their exact sources.