docs: align npm package metadata with the new positioning - #81
Open
TheAmericanMaker wants to merge 1 commit into
Open
docs: align npm package metadata with the new positioning#81TheAmericanMaker wants to merge 1 commit into
TheAmericanMaker wants to merge 1 commit into
Conversation
npm is the largest discovery surface here (~1,800 installs/month) and its description still carried the pre-#77 pitch: "Evidence-backed reverse engineering and human-gated software planning for Pi and MCP coding agents." Same stale positioning already fixed in the README, the website, and the MCP Registry entry. Also adds the five keywords set as GitHub repo topics in #77 — codebase, ai-agent, context-engineering, code-understanding, spec-driven — so the npm and GitHub discovery surfaces match. The test asserted the literal marketing sentence, which is why the copy went stale: updating the description looked like breaking a test, so nobody did. It now asserts the two product directions the check actually cares about (analysis and planning) rather than exact phrasing, and requires the new keywords. Verified the keyword check fails when one is removed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Found while finishing #80. The npm listing is the largest discovery surface here — ~1,800 installs/month — and it still carried the pre-#77 pitch:
That's the same stale positioning already corrected in the README (#77), the website (Website#16), and the registry entry (#80). npm was the last one left.
Why it went stale
The test asserted the literal marketing sentence:
So updating the description looked like breaking a test, and nobody did. The check now asserts the two product directions it actually cares about — analysis and planning — instead of exact phrasing. Same failure it was designed to catch, without freezing the copy.
This is worth calling out as a pattern: the website had the identical problem (its test pinned the hero to
Evidence-backed software cartography · vX.Y.Z), fixed the same way in Website#16. A test that pins marketing copy doesn't protect the copy — it preserves it past its expiry.Keywords
Adds the five topics set on the GitHub repo in #77 so the npm and GitHub surfaces match:
codebase·ai-agent·context-engineering·code-understanding·spec-drivenExisting keywords are unchanged, and the test still requires them.
Verification
Ships with the next release, since the description only updates on publish.
🤖 Generated with Claude Code