Repository navigation
test(drive): verify released knowledge and source retirement lifecycle - #66
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.
Verify the released Drive 0.7.0 knowledge workflow through its installed binary: explicitly link/filter a person, edit a note and refuse its old revision, create/confirm a source-backed work memory, and check scope/source search. Then remove the synthetic selected root and reconcile, proving source browsing/search/snapshots retire, the confirmed memory becomes stale and the owner note remains. Repeating reconciliation removes nothing.
Extend the existing installed acceptance script instead of adding another store or CLI path. Synthetic people are seeded and final persisted notes/memories inspected through cli-core public store APIs. Every CLI process uses isolated state and the existing HTTP/browser/keyring denial wrapper. The only non-offline invocations are sync after there are no selected roots; an unexpected provider or keyring access would fail. No real account, remote write, model request or Drive source import is used.
Validation: exact npm Drive 0.7.0/Core 0.278.0/base 0.28.2 passed the existing 8 initial and 8 baseline checks plus all 7 new lifecycle groups on Linux/Node 24.19.0. Explicit Biome and Markdown (14 files) passed; staged lint/secrets passed. Reproduction, outcomes and limits are in performance/documents/offline-catalog/README.md. Native Google change propagation, automatic editor identity association and AI/provider fidelity remain unmeasured.