Repository navigation
Host-accurate install copy across skills, README and example - #1
Closed
chrisjleal wants to merge 3 commits into
Closed
chrisjleal wants to merge 3 commits into
chrisjleal wants to merge 3 commits into
Conversation
Aligns the setup and trust-workflow skills, the plugin README, the guarded-agent example and smithery.config.json with the mcpInstallPaths SSOT: describe the step each host actually performs instead of naming a Connect control most hosts do not render. Keeps the plugin bundle, server.json discovery metadata and .cursor-plugin/.claude-plugin/.codex-plugin manifests unchanged. Co-authored-by: Cursor <cursoragent@cursor.com>
Replaces an unapproved phrase with approved vocabulary: 'To put Proofable behind your own product, start from github.com/proofable/sdk'. The language owner's blacklist and its rule against describing architecture as customer value both reject the original wording; the SDK is the integration path, not something a reader 'builds against'. Co-authored-by: Cursor <cursoragent@cursor.com>
…fault branch Pull-request CI compared mcp/skills/ against proofable/sdk checked out at its default branch, so the paired SDK pull request could never be green here and neither could this one - a deadlock across the two repositories. PR CI now proves what this repository can prove alone: canonical skills/ versus the bundled plugin copy (--plugin-only). The cross-repository comparison stays a hard gate where both sides are settled - prepublishOnly and the Release workflow - and release still fails on a real mismatch.
Contributor
Author
|
Superseded by #3. This branch predates the 0.1.3 SSOT frontmatter guard (ab667b6) and would revert the metadata block that validate-manifest-ssot.mjs now enforces, plus the plugin-only CI/release parity split. #3 rebases the same host-accurate install copy onto current main and keeps the SSOT frontmatter, so canonical skills/ matches the published @proofable/sdk copy. |
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.
Aligns the setup + trust-workflow skills, the plugin README, the guarded-agent example and
smithery.config.jsonwith themcpInstallPathsSSOT.Why: the four install sentences were hand-written in the product page, the Connect menus, the CLI hints, the docs and five READMEs. They drifted, and they were wrong the same way: they told every host to "Click Connect". Only Claude connectors and Devin render a control with that name. Everywhere else the user goes looking for a control that does not exist.
What changed: describe the step each host actually performs, in the host's own vocabulary. No manifest, bundle or discovery metadata changed (
.cursor-plugin,.claude-plugin,.codex-plugin,mcp.json,server.jsonuntouched).Coordinated with
neus6945eedf0,docsfc6c314andsdk25f6ada, which carry the same correction.Verified: no
.envstaged; manifests unchanged; markdown-only diff.