chore(brand): align category to Care Intelligence Platform + npm hygiene#11
Merged
Merged
Conversation
Coherence sweep across Upstream-family repos surfaced:
1. README intro paragraph and footer both said "Payer intelligence
Platform" (lowercase 'i', wrong category). Canon per
_config/BRAND.md and _config/CONSISTENCY.md is "Care Intelligence
Platform" — established as the category framing on 2026-05-03 and
used by upstream-skills, upstream-community, and the org profile.
Fixed both occurrences.
2. package.json description was generic ("MCP server for Upstream
care intelligence"). Replaced with category-aligned, npm-shopfront
ready copy. No em dash (forbidden in outbound copy per VOICE.md).
3. Added standard npm registry hygiene fields the published v0.2.0
package was missing: keywords, author, license (was implicit via
LICENSE file), homepage, repository, bugs, engines (node >=20 per
CI), files allowlist. None of these change runtime behavior; they
surface on npmjs.com/package/@upstream-intelligence/mcp.
4. Added npm version badge to README so release state is visible at
a glance.
No version bump (coherence sweep, not a release). Build clean, 9/9
tests pass.
Co-Authored-By: Claude Opus 4.7 (1M context) <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.
Summary
Coherence sweep across the Upstream-family repos surfaced two drift items:
Category alignment. README intro paragraph and footer both said "Payer intelligence Platform" (lowercase 'i', wrong category framing). Canon per
_config/BRAND.mdand_config/CONSISTENCY.mdis "Care Intelligence Platform" — the category framing established 2026-05-03 and used by sibling repos. Fixed both occurrences.npm registry hygiene. v0.2.0 was published to npm but the package.json was missing standard registry fields. Added
keywords,author,license,homepage,repository,bugs,engines, andfilesallowlist. The description was generic ("MCP server for Upstream care intelligence") and is now category-aligned shopfront copy. Avoided em dashes per VOICE.md.npm version badge added to README so release state is visible alongside license / issues / upstream.cx / newsletter badges.
No version bump (coherence sweep, not a release). Build clean (
tsc), 9/9 vitest tests pass.Test plan
npm view @upstream-intelligence/mcpwill show the new metadata after the next publish🤖 Generated with Claude Code