docs(README): fix stale version + 'future' mobile-mcp wording#118
Merged
Conversation
Two inaccuracies surfaced by an audit against the code: - Contributing section said "stable now (v0.1.x)" and "CONTRIBUTING.md will land alongside v0.2" — but the package is 0.2.1 (tags v0.2.0/ v0.2.1 exist) and the header already says "0.2.1 stable". Update to v0.2.x and drop the shipped-version reference. - Security section listed "the future mobile-mcp client" among scrubbed subprocesses, but mobile-mcp is already spawned with scrubbedEnv() (src/mobile.ts:89). Drop "future".
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.
What
Audit of the README against the codebase surfaced two factual inaccuracies (most of the doc checked out clean —
db:seed_fu, rubric constants, env-scrub key list,adbresolution order, model id, and LOC table all match the source).Fixed
CONTRIBUTING.md"will land alongside v0.2" — butpackage.jsonis0.2.1(tagsv0.2.0/v0.2.1exist) and the header already says "0.2.1 stable". v0.2 has shipped; updated to v0.2.x.scrubbedEnv()(src/mobile.ts:89). Dropped "future".Flagged, not changed
package.jsonpins^0.2.114. Left as-is: 0.2.111 is the stated Opus-4.7 feature floor (matchesCLAUDE.md); the package merely pins higher. Not a contradiction.🤖 Generated with Claude Code