chore(closeout): finalize distribution prep

- replace the old weekly governance lane with the current manual plus runtime-gc model
- add concentrated distribution and integration truth surfaces
- align storefront closure checks with the live GitHub Pages, Issues, Discussions, and branch-protection truth

Author: xiaojiou176

.env.example

@@ -913,7 +913,7 @@ WEB_RUN_ID=
 # [tests] Tests
 # Governed env variable detected by automated env scan (tests scope).
 # policy: optional, non-sensitive
-WEEKLY_RUN_ID=
+MANUAL_RUN_ID=
 
 # [runtime] Runtime
 # Runtime cache directory override.

.github/workflows/ci.yml

@@ -96,7 +96,7 @@ jobs:
             ci_gatechain:
               - '.github/workflows/ci.yml'
               - '.github/workflows/nightly.yml'
-              - '.github/workflows/weekly.yml'
+              - '.github/workflows/manual.yml'
               - '.github/workflows/pre-commit.yml'
               - 'scripts/ci/*gate*'
               - 'scripts/ci/*truth*'

.github/workflows/weekly.yml .github/workflows/manual.yml.github/workflows/weekly.yml renamed to .github/workflows/manual.yml

@@ -1,15 +1,13 @@
-name: Runtime GC Weekly
+name: Runtime GC
 
 on:
-  schedule:
-    - cron: "0 9 * * 1"
   workflow_dispatch:
 
 permissions:
   contents: read
 
 concurrency:
-  group: runtime-gc-weekly-${{ github.workflow }}-${{ github.ref }}
+  group: runtime-gc-manual-${{ github.workflow }}-${{ github.ref }}
   cancel-in-progress: true
 
 jobs:

.github/workflows/runtime-gc-weekly.yml .github/workflows/runtime-gc.yml.github/workflows/runtime-gc-weekly.yml renamed to .github/workflows/runtime-gc.yml

@@ -0,0 +1,60 @@
+# Distribution Status
+
+This page separates **repo-ready surfaces** from **actual published registry
+state**.
+
+Current public release truth:
+
+- GitHub release/tag: `v0.1.1`
+- GitHub Pages storefront: `https://xiaojiou176-open.github.io/prooftrail/`
+- npm / PyPI / MCP Registry publication: **not yet published**
+
+## 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 (`@uiq/mcp-server`) | yes | no | no | The package exists for repo-local use, but `apps/mcp-server/package.json` is `private: true`. |
+| 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 | no | no | `pyproject.toml` exists, but this repo does not currently prove a PyPI release, and the Python package version is not release-synced with `v0.1.1`. |
+| MCP Registry listing | partial | no | no | The repo contains an MCP server implementation, but no registry publication or listing proof is materialized here. |
+| Skills / starter / plugin bundle metadata | no dedicated surface | no | no | This repo does not currently ship a dedicated skills package, starter bundle, or browser-plugin distribution surface. |
+
+## What "Ready" Means Here
+
+For this repository, "ready for final distribution prep" means:
+
+- the repo-side truth surface is explicit
+- the GitHub storefront and closure evidence are aligned
+- security and public-truth gates are green
+- registry publication is still a separate later action
+
+It does **not** mean that npm, PyPI, or MCP Registry publication has already
+happened.
+
+## Intentionally Deferred
+
+These remain outside the current repo-side closeout scope:
+
+- npm publication
+- PyPI publication
+- MCP Registry submission or listing verification
+- Chrome Web Store packaging or submission
+- social preview upload evidence
+- hosted / multi-tenant deployment rollout
+
+## Why There Is No `proof.html`
+
+This repo intentionally does **not** add a separate `proof.html` truth surface
+right now.
+
+Reason:
+
+- the README already owns the storefront story
+- `docs/index.md` already owns the public docs map
+- this page and `INTEGRATIONS.md` now own the distribution and integration truth
+- adding one more HTML proof page would create another drift-prone surface
+
+That keeps the truth surface lighter and easier to keep honest.

DISTRIBUTION.md

@@ -0,0 +1,55 @@
+# Integration Boundaries
+
+ProofTrail is a **browser-evidence and recovery layer**.
+
+It can sit behind coding-agent or operator workflows, but this repository does
+**not** currently claim:
+
+- an official Codex integration
+- an official Claude Code integration
+- an official OpenHands integration
+- an official OpenCode integration
+- an official OpenClaw integration
+- a browser plugin
+- a first-party hosted agent shell
+
+## Current Repo-Native Integration Surfaces
+
+| Surface | Exists in repo | Current status | Notes |
+| --- | --- | --- | --- |
+| HTTP API | yes | repo-native | The canonical API contract lives in `docs/reference/universal-api.md` and the checked-in generated client stays repo-local. |
+| MCP server | yes | repo-native | `apps/mcp-server/` provides the governed MCP surface for local or self-managed use. |
+| AI prompt contracts | yes | repo-native | `packages/ai-prompts/` exists as a private workspace package, not as a published registry surface. |
+| GitHub Pages storefront | yes | public-facing | Pages explains product fit and routes people into docs, but it is not a plugin or marketplace listing. |
+
+## Ecosystem Fit, Truthfully
+
+| Ecosystem | Current truthful fit | Best first path | Official plugin or listing today |
+| --- | --- | --- | --- |
+| Codex | API-first or hybrid browser-evidence layer | `docs/how-to/prooftrail-for-coding-agents.md` -> `docs/how-to/api-builder-quickstart.md` | no |
+| Claude Code | MCP-first browser-evidence side road | `docs/how-to/prooftrail-for-coding-agents.md` -> `docs/how-to/mcp-quickstart-1pager.md` | no |
+| OpenHands | browser subsystem behind a larger runtime | `docs/how-to/prooftrail-for-ai-agents.md` -> `docs/how-to/api-builder-quickstart.md` | no |
+| OpenCode | governed MCP browser surface | `docs/how-to/prooftrail-for-coding-agents.md` -> `docs/how-to/mcp-quickstart-1pager.md` | no |
+| OpenClaw | browser workflow backend behind a tool router | `docs/how-to/prooftrail-for-coding-agents.md` -> `docs/how-to/api-builder-quickstart.md` | no |
+
+## What Is Not Materialized Here Yet
+
+These surfaces are **not** currently materialized as dedicated publishable
+integration products in this repo:
+
+- vendor-specific plugins
+- official marketplace listings
+- starter template packages
+- dedicated skills registry packages
+- formal SDK packages
+
+## How To Read The Current Repo
+
+If you are evaluating ProofTrail for an external toolchain, the truthful order
+is:
+
+1. decide whether you need API-first or MCP-first control
+2. use the existing repo-native API or MCP surface
+3. treat any future registry publication or marketplace packaging as a later step
+
+That keeps current capability and future packaging clearly separated.

INTEGRATIONS.md

@@ -8,13 +8,24 @@ evidence, and guided recovery.
 ProofTrail is an auditable browser automation platform for teams that need
 browser execution to stay inspectable, replayable, and recoverable.
 
+Current public distribution and ecosystem boundaries:
+[DISTRIBUTION.md](DISTRIBUTION.md) | [INTEGRATIONS.md](INTEGRATIONS.md)
+
 It also fits teams using Codex, Claude Code, OpenHands, OpenCode, OpenClaw, or
 other agent shells that need a browser-evidence layer through API and governed
 MCP, not a generic browser bot.
 
-[Docs](docs/index.md) | [Quickstart](docs/getting-started/human-first-10-min.md) | [Minimal Success Case](docs/showcase/minimal-success-case.md) | [API Builder Quickstart](docs/how-to/api-builder-quickstart.md) | [ProofTrail for AI Agents](docs/how-to/prooftrail-for-ai-agents.md) | [ProofTrail for Coding Agents and Agent Ecosystems](docs/how-to/prooftrail-for-coding-agents.md) | [MCP for Browser Automation](docs/how-to/mcp-quickstart-1pager.md) | [AI Reconstruction](docs/how-to/ai-reconstruction-side-road.md) | [Evidence, Recovery, and Review Workspace](docs/how-to/evidence-recovery-review-workspace.md) | [Alternatives](docs/compare/prooftrail-vs-generic-browser-agents.md) | [Release Guide](docs/release/README.md)
+Quick paths:
+
+- [Docs](docs/index.md)
+- [Quickstart](docs/getting-started/human-first-10-min.md)
+- [ProofTrail for AI Agents](docs/how-to/prooftrail-for-ai-agents.md)
+- [ProofTrail for Coding Agents and Agent Ecosystems](docs/how-to/prooftrail-for-coding-agents.md)
+- [API Builder Quickstart](docs/how-to/api-builder-quickstart.md)
+- [Distribution Status](DISTRIBUTION.md)
+- [Integration Boundaries](INTEGRATIONS.md)
 
-<img src="assets/storefront/prooftrail-readme-hero.svg" alt="ProofTrail canonical proof loop showing one public command, one retained evidence bundle, and one exact recovery path." />
+![ProofTrail proof loop hero](assets/storefront/prooftrail-readme-hero.svg)
 
 ![ProofTrail command center showing the canonical run path, evidence-focused navigation, and operator parameter rail](assets/storefront/prooftrail-hero.png)
 
@@ -137,7 +148,7 @@ board:
 - **Codex**, **OpenHands**, and **OpenClaw** usually start API-first or hybrid
 - **ProofTrail** stays the browser-evidence and recovery layer in all cases
 
-<img src="assets/storefront/prooftrail-agent-ecosystem-map.svg" alt="ProofTrail ecosystem fit map showing Codex, Claude Code, OpenHands, OpenCode, and OpenClaw with API-first and MCP-first entry roads." />
+![ProofTrail ecosystem fit map](assets/storefront/prooftrail-agent-ecosystem-map.svg)
 
 ## Explore the Product Surface
 
@@ -186,11 +197,17 @@ so the public story and the integration story stay connected.
 
 Choose the shortest path that matches what you want to confirm first:
 
-| I want to... | Run this first | What I get |
-| --- | --- | --- |
-| produce one canonical run | `just setup && just run` | a new run directory under `.runtime-cache/artifacts/runs/<runId>/` with manifest and proof reports |
-| know what good evidence should look like | [docs/reference/run-evidence-example.md](docs/reference/run-evidence-example.md) | the concrete report shape you should expect from a healthy run |
-| follow the guided operator path | [docs/getting-started/human-first-10-min.md](docs/getting-started/human-first-10-min.md) | the shortest human-readable route from fresh checkout to inspectable proof |
+- If you want to produce one canonical run:
+  Start with `just setup && just run`.
+  You should get a new run directory under
+  `.runtime-cache/artifacts/runs/<runId>/` with manifest and proof reports.
+- If you want to know what good evidence should look like:
+  Start with [docs/reference/run-evidence-example.md](docs/reference/run-evidence-example.md).
+  That page shows the concrete report shape a healthy run should produce.
+- If you want to follow the guided operator path:
+  Start with [docs/getting-started/human-first-10-min.md](docs/getting-started/human-first-10-min.md).
+  That is the shortest human-readable route from fresh checkout to inspectable
+  proof.
 
 ## 15-Minute Evaluation Path
 
@@ -246,7 +263,8 @@ The canonical public mainline is:
 2. run `just run`
 3. inspect `.runtime-cache/artifacts/runs/<runId>/`
 
-`just run` is the canonical public mainline wrapper for `pnpm uiq run --profile pr --target web.local`.
+`just run` is the canonical public mainline wrapper for
+`pnpm uiq run --profile pr --target web.local`.
 
 `just run-legacy` remains available for lower-level workshop troubleshooting,
 but it is not the canonical public mainline.
@@ -279,13 +297,13 @@ Requirements:
 just setup
 ```
 
-2. Run the canonical workflow.
+1. Run the canonical workflow.
 
 ```bash
 just run
 ```
 
-3. Inspect the resulting evidence bundle.
+1. Inspect the resulting evidence bundle.
 
 ```bash
 ls .runtime-cache/artifacts/runs
@@ -300,7 +318,8 @@ What good looks like:
   `reports/proof.gaps.json`, and `reports/proof.repro.json`
 - `manifest.json` points back to those proof artifacts through both
   `manifest.proof` and `manifest.reports`
-- the same orchestrator-first chain is reachable through `pnpm uiq run --profile pr --target web.local`
+- the same orchestrator-first chain is reachable through
+  `pnpm uiq run --profile pr --target web.local`
 - even when the PR gate fails, `reports/summary.json` still tells you why
   instead of leaving you with a silent shell failure
 
@@ -341,7 +360,8 @@ Use the product surfaces in this order:
    - Ask: "Do I need help rebuilding a flow from artifacts?"
    - Use it only after artifacts already exist; it is an optional advanced helper.
 5. **MCP**
-   - Ask: "Do I need an external AI client to inspect runs or operate this repo safely?"
+   - Ask: "Do I need an external AI client to inspect runs or operate this
+     repo safely?"
    - Treat it as an integration side road, not as a replacement for `just run`.
 6. **Review Workspace**
    - Ask: "Do I need one review-ready packet before I hand this run to another maintainer?"
@@ -362,7 +382,9 @@ Use this mental model when you explain ProofTrail to a new evaluator:
 
 - **What it is**: evidence-first browser automation with recovery and MCP
 - **Who it helps**: AI agents and human operators who need trustworthy browser workflows
-- **Why it feels different**: the product does not stop at “the automation ran”; it keeps the evidence, recovery path, and handoff surfaces attached to the run
+- **Why it feels different**: the product does not stop at
+  “the automation ran”; it keeps the evidence, recovery path, and handoff
+  surfaces attached to the run
 - **Where AI fits**: AI reconstruction helps after artifacts already exist
 - **Where MCP fits**: MCP exposes the same governed surfaces to external AI clients
 
@@ -372,7 +394,8 @@ Suitable for:
 
 - teams standardizing browser automation runs across operators and environments
 - maintainers who need inspectable evidence instead of ad-hoc shell output
-- workflows where replay, diagnostics, and recovery matter as much as first-run success
+- workflows where replay, diagnostics, and recovery matter as much as
+  first-run success
 
 Not suitable for:
 
@@ -395,9 +418,13 @@ governance checks.
 
 Public collaboration contract:
 
-- external pull requests stay on GitHub-hosted, low-risk governance and build lanes
-- live, external, and owner-secret workflows are manual-only and require the protected `owner-approved-sensitive` environment
-- macOS-only smoke and regression lanes use GitHub-hosted `macos-latest`; `self-hosted` / `shared-pool` are not part of the public collaboration contract
+- external pull requests stay on GitHub-hosted, low-risk governance and build
+  lanes
+- live, external, and owner-secret workflows are manual-only and require the
+  protected `owner-approved-sensitive` environment
+- macOS-only smoke and regression lanes use GitHub-hosted `macos-latest`;
+  `self-hosted` / `shared-pool` are not part of the public collaboration
+  contract
 
 ## Maintainer Space Hygiene
 

README.md

@@ -10,6 +10,7 @@ const NEW_TOOL_NAMES = [
   "uiq_api_workflow",
   "uiq_catalog",
   "uiq_compare_perf",
+  "uiq_evidence_runs",
   "uiq_list_runs",
   "uiq_model_target_capabilities",
   "uiq_proof",
@@ -94,8 +95,12 @@ nodeTest("mcp resources expose both latest manifest and summary", { timeout: 30_
     const uris = listed.resources.map((r) => r.uri).sort()
     assert.deepEqual(uris, ["uiq://runs/latest/manifest", "uiq://runs/latest/summary"])
 
-    const manifest = await harness.client.readResource({ uri: "uiq://runs/latest/manifest" })
-    const summary = await harness.client.readResource({ uri: "uiq://runs/latest/summary" })
+    const manifest = await harness.client.readResource({
+      uri: "uiq://runs/latest/manifest",
+    })
+    const summary = await harness.client.readResource({
+      uri: "uiq://runs/latest/summary",
+    })
 
     const manifestText =
       manifest.contents.find((c): c is { uri: string; text: string } => "text" in c)?.text ?? ""

apps/mcp-server/tests/mcp-smoke.test.ts

@@ -84,7 +84,7 @@
           "workflow recovery"
         ],
         "sameAs": [
-          "https://github.com/xiaojiou176-open/prooftrail/blob/main/docs/index.md"
+          "https://xiaojiou176-open.github.io/prooftrail/"
         ]
       }
     </script>

apps/web/index.html

@@ -1679,7 +1679,7 @@ variables:
     required: false
     sensitive: false
     description: "Governed env variable detected by automated env scan (runtime scope)."
-  - name: WEEKLY_RUN_ID
+  - name: MANUAL_RUN_ID
     section: tests
     default: ""
     required: false