Repository navigation
test(drive): verify released decision history and local guards - #92
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 whether published Drive 0.13.0 preserves decision history through its installed executable. A reproducible runner seeds two synthetic documents and account profiles through Core's public store, then makes 24 guarded CLI invocations. It checks replacement/confirmation/reversal, event time, wrong document/account refusal, history queries, read-only, dry-run, offline and unknown arguments.
The committed result comes from a fresh npm installation, with npm integrity and exact dependency pins. Child HTTP/fetch, raw sockets, browser subprocesses and keyring construction are denied. No real Google account or AI provider was used. Source tests separately cover MCP filtering; this report measures executable CLI behavior.
Validation: all 24 invocations pass; staged Biome, Markdown and secret checks pass. Area index and Unreleased notes updated.