prooftrail

Distribution Status

This page separates repo-ready surfaces from actual published registry state.

Current public release truth:

Current Distribution Ledger

Surface Materialized in repo Publish-ready today Published / listed today Notes
GitHub release/tag yes yes yes Current live release/tag is v0.1.1.
GitHub Pages storefront yes yes yes Current live homepage points to GitHub Pages and returns HTTP 200.
Root npm package (prooftrail) yes no no Root package.json is private: true, so the repo does not currently expose a publishable npm package.
MCP npm package (@prooftrail/mcp-server) yes yes no The package now has a publish-ready contract, but it is not yet published.
AI prompts npm package (@uiq/ai-prompts) yes no no The package exists for repo-local use, but packages/ai-prompts/package.json is private: true.
PyPI package (prooftrail) yes yes no pyproject.toml and uv.lock now both declare 0.1.1, so the repo-owned Python packaging contract is release-synced. The remaining gap is upstream publication/read-back, not repo-owned metadata drift.
MCP Registry listing partial no no The repo now materializes apps/mcp-server/server.json as the registry submission artifact, but the npm package is still unpublished and no upstream listing proof exists.
Goose Skills Marketplace yes yes no External review receipt exists at PR #26; this is a real upstream submission, but not a listed-live marketplace entry yet.
agent-skill.co source repo yes yes no External review receipt exists at PR #182; this is a real index submission, but not a listed-live directory entry yet.
awesome-opencode project entry yes yes no External review receipt exists at PR #275; this is a real curated project submission, not a listed-live project entry yet.
OpenHands/extensions lane yes yes no External receipt exists at PR #161, but the lane is now closed-not-accepted; it is not review-pending, and maintainers pointed contributors to a custom marketplace.json alternative instead.
ClawHub skill page yes yes yes The ProofTrail MCP skill page can be read back live at https://clawhub.ai/skills/prooftrail-mcp. This is a live public discovery page for the skill packet, not proof of a hosted MCP endpoint or generic skill-registry publication.
Repo-owned ProofTrail MCP install skill yes yes no skills/prooftrail-mcp/ is materialized in the repo, and its current external receipts are now split across ClawHub live, Goose review-pending, agent-skill review-pending, awesome-opencode review-pending, and OpenHands closed-not-accepted.
MCP Docker image (ghcr.io/xiaojiou176-open/prooftrail-mcp-server:0.1.1) yes yes no The repo defines the GHCR container contract, but today https://github.com/orgs/xiaojiou176-open/packages/container/package/prooftrail-mcp-server returns 404 and https://github.com/orgs/xiaojiou176-open/packages?repo_name=prooftrail reports 0 packages. Plain-English boundary: repo-ready container docs do not prove a live public GHCR package.
Starter / plugin bundle metadata no dedicated surface no no This repo still does not ship a dedicated starter bundle or browser-plugin distribution surface.

What “Ready” Means Here

For this repository, “ready for final distribution prep” means:

It does not mean that npm, PyPI, Official MCP Registry, generic skill registry publication, or the GHCR public package surface are already live just because the repo carries a Docker image contract or a live ClawHub skill page.

Publication Receipt Bundle

If you need the shortest receipt-first map for the next heavy lane, open docs/release/publication-receipt-bundle.md.

If you need the current registry / marketplace / owner-manual cockpit, open llms-install.md and docs/release/mcp-listings-cockpit.md.

That page separates:

Intentionally Deferred

These remain outside the current repo-side closeout scope:

Why There Is No proof.html

This repo intentionally does not add a separate proof.html truth surface right now.

Reason:

That keeps the truth surface lighter and easier to keep honest.