Repository navigation
test(projects): reproduce published Memo annotation hosts - #186
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 independent npm Memo0.83 CLI and actual stdio MCP acceptance for selected project annotations. The driver checks private export, explicit target preview, agent restore refusal, owner-labelled restore, repeat refusal, unknown-field and semantic errors, proposed state and unrelated records. It accepts no existing store and uses invented data only.
Retain the exact observed dependency graph, normalized to exact top-level pins, with a reproducible npm-ci command and package/source/integrity/entry hashes. The frozen-lock installation reproduces the same assertions. Memo's registry tarball matches the validated release artifact byte-for-byte. Source/target byte checks distinguish export/preview from normal MCP audit writes.
Share the synthetic fixture with the earlier SDK check without changing its assertions or frozen results. Validation: published npm installation and locked reproduction pass; shared SDK check passes; changed files pass Biome; docs checks and staged secret scan pass. No live reset, OAuth or retrieval/extraction quality claim.