Publication Receipt Bundle
This page is the receipt wall for ProofTrail’s later publication lanes.
Use it when you need to answer a plain question:
Which receipts are already real, which ones are only review receipts, and
which ones are still contract-only boxes waiting for a later heavy push?
Think of it like a loading dock.
Some boxes already have signed delivery slips, some only have a courier pickup
ticket, and some are still packed but have not left the warehouse.
Receipt layers
GitHub release/tag
- strongest current receipt:
- current status:
- repo-owned source of truth:
docs/release/README.md
DISTRIBUTION.md
- what this receipt does not prove:
- npm, GHCR, or Official MCP Registry publication
GitHub Pages storefront
- strongest current receipt:
- current status:
- repo-owned source of truth:
README.md
docs/index.md
DISTRIBUTION.md
- what this receipt does not prove:
- package publication or hosted MCP
ClawHub skill page
- strongest current receipt:
https://clawhub.ai/skills/prooftrail-mcp
- current status:
listed-live for the packet discovery page
- repo-owned source of truth:
skills/prooftrail-mcp/README.md
docs/reference/mcp-distribution-contract.md
- what this receipt does not prove:
- generic skill-registry publication
- official plugin status
- hosted endpoint
OpenHands/extensions
- strongest current receipt:
- current status:
- repo-owned source of truth:
skills/prooftrail-mcp/README.md
docs/reference/mcp-distribution-contract.md
- what this receipt does not prove:
- a live listing
- an active upstream review queue
Goose Skills Marketplace
- strongest current receipt:
https://github.com/block/agent-skills/pull/26
- current status:
- repo-owned source of truth:
skills/prooftrail-mcp/README.md
skills/prooftrail-mcp/SKILL.md
- what this receipt does not prove:
- a listed-live marketplace entry
Agent Skill Index
- strongest current receipt:
https://github.com/heilcheng/awesome-agent-skills/pull/182
- current status:
- repo-owned source of truth:
skills/prooftrail-mcp/README.md
skills/prooftrail-mcp/SKILL.md
- what this receipt does not prove:
- a listed-live directory entry
awesome-opencode project entry
- strongest current receipt:
https://github.com/awesome-opencode/awesome-opencode/pull/275
- current status:
- repo-owned source of truth:
README.md
docs/release/publication-receipt-bundle.md
- what this receipt does not prove:
- an accepted or listed-live project entry
npm package @prooftrail/mcp-server
- strongest current receipt:
- repo-owned package metadata only
- current status:
packet-ready / not published
- repo-owned source of truth:
apps/mcp-server/package.json
apps/mcp-server/server.json
- what this receipt does not prove:
- installable upstream package
Official MCP Registry
- strongest current receipt:
- repo-owned descriptor only
- current status:
packet-ready / not submitted-live
- repo-owned source of truth:
apps/mcp-server/server.json
docs/reference/mcp-distribution-contract.md
- what this receipt does not prove:
- registry acceptance or search read-back
GHCR image ghcr.io/xiaojiou176-open/prooftrail-mcp-server:0.1.1
- strongest current receipt:
- repo-owned container contract, but public page read-back is absent
- current status:
contract-only / not published
- repo-owned source of truth:
DISTRIBUTION.md
docs/reference/mcp-distribution-contract.md
- what this receipt does not prove:
- public container listing or hosted service
Repo-owned packet for the next heavy lane
If the next worker needs one reviewable repo-owned bundle before pushing
publication again, start with these files:
DISTRIBUTION.md
llms-install.md
docs/reference/mcp-distribution-contract.md
apps/mcp-server/package.json
apps/mcp-server/server.json
skills/prooftrail-mcp/README.md
docs/release/README.md
docs/release/mcp-listings-cockpit.md
That bundle keeps four truths separate:
- release/live storefront receipts
- packet-discovery receipts
- review receipts
- contract-only later lanes
Current order for later heavy work
The clean order is:
- keep the release/tag, Pages, and packet docs aligned
- treat ClawHub as packet-discovery truth only
- treat OpenHands as a review receipt only
- publish
@prooftrail/mcp-server before claiming Official MCP Registry
progress
- keep GHCR in the contract-only bucket until public read-back stops saying
404 / 0 packages
What not to mix into this wall
Do not rewrite these receipts as proof that:
- ProofTrail already has a live generic skill-registry listing
- the npm package is already installable from upstream
- the Official MCP Registry already lists the repo
- the GHCR package is publicly available
- the repo now needs new Docker/runtime code to “look more real”
Theater C’s current job here is clearer paperwork, not bigger machinery.