docs: clarify README and remove internal brand docs#4
Merged
Conversation
wengzige
marked this pull request as ready for review
July 14, 2026 03:42
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
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.
What changed
Public-content audit
Reviewed every file introduced since
156aea8, the currentgh-pagestree, and all uploaded v0.2.2 release assets. No private MCP source, internal planning notes, machine-local paths, tokens, or keys were found outside the removeddocs/branddocumentation. The Pages branch contains only the built site assets; the MCPB contains only its manifest and two platform binaries.The removed files remain reachable in existing Git history and the v0.2.2 tag until a separately approved history/tag rewrite is performed.
Checks
npm run typechecknpm test -- --run(277 tests passed)git diff --cached --check