release: @proofable/mcp 0.1.3 - publish manifests matching the live MCP surface

[chrisjleal]

Why

@proofable/mcp@0.1.2 is on npm with content older than this repo. The published
server.json carries a superseded proofable_proofs_update description, while the live
hosted MCP already serves the current one:

LIVE  mcp.proofable.me : "Update a proof you own: title, tags, and visibility (public|unlisted|private)..."
REPO  mcp/server.json  : "Update a proof you own: title, tags, and visibility (public|unlisted|private)..."
NPM   0.1.2 server.json: "Update title/tags on a proof you own, or leave feedback..."   <- superseded

package.json and server.json in the published tarball hash differently from the repo:

server.json    pub=2480067b0eb6  repo=60e8fe5622b3   DIFFER
package.json   pub=d99be3084225  repo=80822974f4f2   DIFFER

So the service is correct and the published manifest is stale, under the same version
number — which is why npm view looks aligned.

What this does

Bumps all nine version carriers from 0.1.2 → 0.1.3:

package.json · package-lock.json · server.json
.cursor-plugin/marketplace.json · .claude-plugin/marketplace.json
.agents/plugins/marketplace.json
plugins/proofable-mcp/{.cursor-plugin,.claude-plugin,.codex-plugin}/plugin.json

Verified

prepublishOnly runs npm run validate; run before and after the bump:

Validation passed.
Official Cursor schema validation passed.
Cursor mcp.json validation passed.
Claude + Codex manifest validation passed.
Manifest SSOT: one description and version across 3 plugin manifests, 3 marketplaces, and package.json.
@proofable/mcp@0.1.3 validate:package  ->  passed
Smithery config validation passed.
exit 0

The SSOT validator is the one that would fail if any carrier were missed; it passes with all
nine at 0.1.3.