docs: align public release lag wording (#65)

Author: xiaojiou176

DISTRIBUTION.md

@@ -74,16 +74,16 @@ Lane order today is:
 ## Version And Release Truth
 
 - The latest live GitHub release is `v0.1.0-alpha.3`.
-- `v0.1.0-alpha.3` is the current published prerelease baseline and is meant to
-  match the current released `main` snapshot.
+- `v0.1.0-alpha.3` is the current published prerelease baseline, but it is no
+  longer the current `main` snapshot.
 - The latest published public package for the read-only MCP is
   `cortexpilot-orchestrator==0.1.0a4`.
 - The latest Official MCP Registry entry points to
   `io.github.xiaojiou176-open/cortexpilot-readonly@0.1.0a4`.
 - `v0.1.0-alpha.1` remains the historical first public baseline, not the latest
   release truth.
-- If `main` moves again after this release, README, Pages, and docs must return
-  to explicit lag wording until the next tag is cut.
+- README, Pages, and manifest surfaces must keep explicit lag wording whenever
+  the published release tag trails `main`.
 
 ## Canonical MCP Truth
 

README.md

@@ -713,7 +713,9 @@ The public release surface now has a live baseline. Use these entrypoints:
 - [Tracked `news_digest` Workflow Case recap](docs/releases/assets/news-digest-workflow-case-recap-2026-03-27.md)
 
 Release truth note: `v0.1.0-alpha.3` is the current published prerelease
-baseline and is intended to match the current released `main` snapshot. The
+baseline, but the local `main` branch has already moved ahead of that tag. Use
+it as the latest published snapshot, not as proof that the current `main`
+snapshot is already released. The
 historical first-baseline draft remains
 [docs/releases/first-public-release-draft.md](docs/releases/first-public-release-draft.md),
 while the current release note source is
@@ -735,9 +737,10 @@ Feedback.
 ## What’s Next
 
 - configure the GitHub social preview with the tracked PNG asset
-- add a tracked healthy demo/GIF
 - expand the current single-run benchmark baseline into a broader public
   benchmark artifact
+- cut the next GitHub Release when maintainers want the published tag to catch
+  up with the newer `main` snapshot
 - publish a verified fallback private security reporting channel if maintainers
   want the public security surface to be fully closed
 

configs/mcp_public_manifest.json

@@ -5,7 +5,7 @@
   "status": "shipped",
   "version": "0.1.0-alpha.4",
   "version_truth": "This is the latest published public read-only MCP package version for registry and package-manager installs. The latest GitHub release tag can differ; re-check PyPI, Official MCP Registry, and the repo release page before broadening claims.",
-  "release_represents_current_main": true,
+  "release_represents_current_main": false,
   "description": "Repo-owned read-only MCP server for CortexPilot runs, workflows, approvals, compare, proof, and incident summaries.",
   "homepage": "https://xiaojiou176-open.github.io/CortexPilot-public/mcp/",
   "distribution_page": "https://github.com/xiaojiou176-open/CortexPilot-public/blob/main/DISTRIBUTION.md",

docs/assets/storefront/demo-status.md

@@ -35,7 +35,7 @@ ones that still need a real capture pass.
 | Healthy backend-backed `news_digest` public proof set | present | tracked proof summary: `docs/releases/assets/news-digest-healthy-proof-2026-03-27.md` |
 | Public benchmark artifact from a real tracked run | present | first tracked single-run baseline: `docs/releases/assets/news-digest-benchmark-summary-2026-03-27.md` |
 | Share-ready Workflow Case recap asset | present | tracked recap asset: `docs/releases/assets/news-digest-workflow-case-recap-2026-03-27.md` |
-| Published GitHub Release page/card | present | live release `v0.1.0-alpha.3` is the latest published prerelease baseline and current released `main` snapshot |
+| Published GitHub Release page/card | present | live release `v0.1.0-alpha.3` is the latest published prerelease baseline, but the repo has moved ahead and the tag now represents a lagging published snapshot |
 
 ## Still Missing
 
@@ -64,8 +64,8 @@ The public storytelling shorthand is now:
 - `social-preview-1280x640.png` is a repo-tracked upload candidate for the GitHub social preview setting, not proof that the live GitHub setting has already been applied.
 - `docs/releases/first-public-release-draft.md` remains the repo-side draft source that fed the published release notes.
 - the live GitHub Release page currently represents the latest published public
-  baseline and current released `main` snapshot; if later commits land, repo
-  docs must restore explicit lag wording until the next tag is cut.
+  baseline, not the current `main` snapshot; keep explicit lag wording in repo
+  docs until the next tag is cut.
 - `docs/releases/assets/news-digest-healthy-proof-2026-03-27.md` and the two
   copied screenshots are repo-tracked evidence from a successful local run,
   not proof that the live GitHub Release page has already been published.

docs/distribution/index.html

@@ -265,8 +265,8 @@ <h3>Latest GitHub release</h3>
           </article>
           <article class="card">
             <span class="badge deferred">Important boundary</span>
-            <h3>Current release and main are aligned</h3>
-            <p>The current prerelease is meant to match the current released <code>main</code> snapshot. If later commits land, restore explicit lag wording until the next tag is cut.</p>
+            <h3>Current main is ahead of the latest release</h3>
+            <p><code>v0.1.0-alpha.3</code> is still the latest published prerelease, but it should be treated as a lagging public snapshot until the next tag catches up with <code>main</code>.</p>
           </article>
           <article class="card">
             <span class="badge shipped">Repo-side draft</span>

docs/runbooks/github-storefront-manual-steps.md

@@ -71,10 +71,10 @@ Live release:
 
 Truth note:
 
-- treat `v0.1.0-alpha.3` as the latest published public baseline and current
-  released `main` snapshot
+- treat `v0.1.0-alpha.3` as the latest published public baseline, but not as
+  proof that the current `main` snapshot is already released
 - keep `v0.1.0-alpha.1` as the historical first public baseline
-- if current `main` moves ahead again, keep `README.md` and `DISTRIBUTION.md`
+- keep `README.md`, `DISTRIBUTION.md`, and the Pages distribution mirror
   explicit about that lag until the next release is cut
 
 ## 6. Pages / Landing