Skip to content

Export mcp-install-paths; host-accurate setup copy - #1

Open
chrisjleal wants to merge 4 commits into
mainfrom
feat/mcp-install-paths-export
Open

chrisjleal wants to merge 4 commits into
mainfrom
feat/mcp-install-paths-export

Conversation

@chrisjleal

Copy link
Copy Markdown
Contributor

Publishes the MCP install-path truth table as a package export so the product, docs and marketplace manifests read one table instead of hand-writing host instructions.

Added: mcp-install-paths.js + test/mcp-install-paths.test.js, exported as @proofable/sdk/mcp-install-paths.

Why it matters: this file is the drift anchor. neus/utils/mcpInstallPaths.js must stay a byte-identical mirror, enforced by install-page-contract.test.ts. Hand-copying it is what let the two drift 68/45 lines apart, which is how "Click Connect" survived in copy for hosts that render no such control.

Also aligns the setup + trust-workflow skills with the table, and updates the README.

Dependencies: registry-only. No file:, link: or local tarball mappings.

Coordinated with neus 6945eedf0, docs fc6c314 and mcp 15c17ac.

chrisjleal and others added 4 commits September 26, 2026 20:12
Publishes the MCP install-path truth table as a package export so the product, docs and marketplace manifests read one table instead of hand-writing host instructions. Adds the mcp-install-paths test and aligns the setup/trust skills with it.

Registry-only dependencies; no file:, link: or local tarball mappings.

Co-authored-by: Cursor <cursoragent@cursor.com>
A stray working-tree edit had replaced this file with the MCP README, making sdk/README.md byte-identical to mcp/README.md. Restored to the origin/main content; this PR is the mcp-install-paths export, not a README rewrite.

Co-authored-by: Cursor <cursoragent@cursor.com>
…l requests

This check compared skills/ against proofable/mcp checked out at its default
branch, so an open pull request here could never be green - and the paired mcp
pull request could not be either. That deadlock blocked both.

The check is now informational by default (prints the mismatch, exits 0) and
becomes the hard gate in the Release workflow via --require, where the sibling
is tagged and settled. Pull-request CI keeps every check it can prove alone.
An earlier edit joined the PROOFABLE_MCP_SKILLS_ROOT value and the following
npm ci step onto one line, which made the workflow unparseable. GitHub reported
the run as a failure with no jobs, so no log was available to explain it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant