Repository navigation
docs: explain Drive project evidence through Memo - #139
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.
Project research through a connected Drive app does not retain those documents in Memo. The existing native guides now show how to select a narrow folder, sync it into the shared store and gather project evidence with
memo projects evidence ... --source drive:personal.The recipe explains recursive discovery versus bounded content reads, pending/skipped coverage, the default 60-day window, source modification dates, explicit source selection and separate project relationships. Usage and search link to the recipe. Examples are fictional; no ingestion or OAuth code changes.
Validation: isolated
pnpm docs:checkpasses links/sidebar, spelling and rumdl (19 files); explicit rumdl checks all three changed guide pages; gitleaks hook andgit diff --checkpass. Released Drive 0.17.1/Memo 0.75.0 help and the ten-check synthetic CLI/MCP acceptance in cli-testing#170 support the workflow. That proof excludes OAuth, live Google conversion, memory invalidation and proposal creation.The portal's release pins, sync outputs and translations are unchanged; this PR updates only owning English native guides.