docs: align storefront and alpha.3 release truth (#55)

* docs: align storefront and alpha.3 release truth

* chore: allow root nvmrc in hygiene policy

Author: xiaojiou176

.nvmrc

@@ -0,0 +1 @@
+20.19.0

DISTRIBUTION.md

@@ -60,8 +60,8 @@ MCP / npm package release.
 
 ## Version And Release Truth
 
-- The latest live GitHub release is `v0.1.0-alpha.2`.
-- `v0.1.0-alpha.2` is the current published prerelease baseline and is meant to
+- 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.1` remains the historical first public baseline, not the latest
   release truth.

README.md

@@ -1,11 +1,11 @@
 # CortexPilot
 
-AI Work Command Tower for Codex and Claude Code workflows with Model Context
-Protocol (MCP)-readable proof, replay, and Workflow Cases.
+One request. One command tower. One proof pack you can inspect before you
+trust the run.
 
-CortexPilot gives Codex / Claude Code teams one governed path from the PM
-request to the Workflow Case to Proof & Replay, instead of scattered agents,
-logs, and local scripts.
+CortexPilot gives Codex / Claude Code teams one governed operator path from the
+PM request to the Workflow Case to Proof & Replay instead of scattered agents,
+local scripts, and after-the-fact logs.
 
 CortexPilot is a contract-first multi-agent orchestration repository.
 
@@ -20,6 +20,8 @@ not a hosted product, and the shipped MCP surface remains **read-only**.
 
 [Quickstart](#quickstart) · [First Proven Workflow](https://xiaojiou176-open.github.io/CortexPilot-public/use-cases/) · [Compatibility Matrix](https://xiaojiou176-open.github.io/CortexPilot-public/compatibility/) · [Distribution Contract](DISTRIBUTION.md) · [Distribution Status](https://xiaojiou176-open.github.io/CortexPilot-public/distribution/) · [Docs](docs/README.md) · [Architecture](docs/architecture/runtime-topology.md) · [AI + MCP + API Surfaces](https://xiaojiou176-open.github.io/CortexPilot-public/ai-surfaces/) · [Builder Quickstart](https://xiaojiou176-open.github.io/CortexPilot-public/builders/) · [Releases](https://github.com/xiaojiou176-open/CortexPilot-public/releases)
 
+![CortexPilot command tower showcase card](docs/assets/storefront/command-tower-showcase-card.svg)
+
 ## Official Distribution Story
 
 The shortest truthful answer today is:
@@ -46,6 +48,8 @@ mirror.
 
 ![CortexPilot command tower flow](docs/assets/storefront/hero-command-tower.svg)
 
+![CortexPilot first-loop storyboard](docs/assets/storefront/first-loop-storyboard.gif)
+
 ## Open The Right Door
 
 | If you're here to... | Open this first |
@@ -691,22 +695,22 @@ gates can trace the maintenance decision end to end.
 The public release surface now has a live baseline. Use these entrypoints:
 
 - [GitHub Releases page](https://github.com/xiaojiou176-open/CortexPilot-public/releases)
-- [Live GitHub Release `v0.1.0-alpha.2`](https://github.com/xiaojiou176-open/CortexPilot-public/releases/tag/v0.1.0-alpha.2)
+- [Live GitHub Release `v0.1.0-alpha.3`](https://github.com/xiaojiou176-open/CortexPilot-public/releases/tag/v0.1.0-alpha.3)
 - [Live GitHub Pages site](https://xiaojiou176-open.github.io/CortexPilot-public/)
 - [Changelog](CHANGELOG.md)
 - [Public release checklist](docs/runbooks/public-release-checklist.md)
-- [Current release notes source](docs/releases/v0.1.0-alpha.2.md)
+- [Current release notes source](docs/releases/v0.1.0-alpha.3.md)
 - [First public release draft](docs/releases/first-public-release-draft.md)
 - [Tracked healthy `news_digest` proof summary](docs/releases/assets/news-digest-healthy-proof-2026-03-27.md)
 - [Tracked `news_digest` baseline summary](docs/releases/assets/news-digest-benchmark-summary-2026-03-27.md)
 - [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.2` is the current published prerelease
+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
 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
-[docs/releases/v0.1.0-alpha.2.md](docs/releases/v0.1.0-alpha.2.md).
+[docs/releases/v0.1.0-alpha.3.md](docs/releases/v0.1.0-alpha.3.md).
 
 Public repo hygiene stays fail-closed as well: token-like fixture coverage must
 use synthetic string assembly, and public path fixtures must use generic

configs/docs_nav_registry.json

@@ -93,7 +93,7 @@
       "listed_in_primary_navigation": false
     },
     {
-      "path": "docs/releases/v0.1.0-alpha.2.md",
+      "path": "docs/releases/v0.1.0-alpha.3.md",
       "kind": "reference",
       "status": "active",
       "canonical": true,

configs/root_allowlist.json

@@ -10,6 +10,7 @@
     ".gitignore",
     ".gitleaks.toml",
     ".gitleaksignore",
+    ".nvmrc",
     ".pre-commit-config.yaml",
     ".runtime-cache",
     "AGENTS.md",

docs/README.md

@@ -66,7 +66,7 @@ navigation set.
 1. [runbooks/public-release-checklist.md](runbooks/public-release-checklist.md)
 2. [runbooks/storefront-share-kit.md](runbooks/storefront-share-kit.md)
 3. [runbooks/github-storefront-manual-steps.md](runbooks/github-storefront-manual-steps.md)
-4. [releases/v0.1.0-alpha.2.md](releases/v0.1.0-alpha.2.md)
+4. [releases/v0.1.0-alpha.3.md](releases/v0.1.0-alpha.3.md)
 5. [releases/first-public-release-draft.md](releases/first-public-release-draft.md)
 6. [assets/storefront/demo-status.md](assets/storefront/demo-status.md)
 7. [assets/storefront/benchmark-methodology.md](assets/storefront/benchmark-methodology.md)
@@ -88,7 +88,7 @@ navigation set.
 - `docs/runbooks/public-release-checklist.md`: user-facing GitHub release preparation checklist
 - `docs/runbooks/storefront-share-kit.md`: tracked punchline and sharing kit for storefront work
 - `docs/runbooks/github-storefront-manual-steps.md`: exact GitHub UI values and manual storefront steps
-- `docs/releases/v0.1.0-alpha.2.md`: repo-side draft source for the current published prerelease notes
+- `docs/releases/v0.1.0-alpha.3.md`: repo-side draft source for the current published prerelease notes
 - `docs/releases/first-public-release-draft.md`: repo-side draft source for the first public GitHub Release
 - `docs/assets/storefront/demo-status.md`: status ledger for tracked public demo and proof assets
 - `docs/assets/storefront/proof-pack-index.json`: machine-readable public proof bundle index for proven and showcase storefront slices

docs/assets/storefront/command-tower-showcase-card.svg

@@ -6,6 +6,7 @@ ones that still need a real capture pass.
 ## Present Today: Explainers And Supporting Assets
 
 - `hero-command-tower.svg`: public hero image
+- `command-tower-showcase-card.svg`: README and storefront showcase card
 - `first-loop-storyboard.svg`: shareable storyboard of the PM -> Command Tower -> Runs loop
 - `first-loop-storyboard.png`: static storyboard export
 - `first-loop-storyboard.gif`: storyboard animation export
@@ -34,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.2` 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 and current released `main` snapshot |
 
 ## Still Missing
 

docs/assets/storefront/demo-status.md

@@ -255,7 +255,7 @@ <h2>Release truth</h2>
           <article class="card">
             <span class="badge shipped">Published today</span>
             <h3>Latest GitHub release</h3>
-            <p><code>v0.1.0-alpha.2</code> is the latest published GitHub Release and the latest public semver tag.</p>
+            <p><code>v0.1.0-alpha.3</code> is the latest published GitHub Release and the latest public semver tag.</p>
           </article>
           <article class="card">
             <span class="badge deferred">Important boundary</span>
@@ -265,7 +265,7 @@ <h3>Current release and main are aligned</h3>
           <article class="card">
             <span class="badge shipped">Repo-side draft</span>
             <h3>Current release notes source</h3>
-            <p>Use <a href="https://github.com/xiaojiou176-open/CortexPilot-public/blob/main/docs/releases/v0.1.0-alpha.2.md"><code>docs/releases/v0.1.0-alpha.2.md</code></a> as the tracked repo-side release draft. Keep <code>first-public-release-draft.md</code> as the historical alpha.1 baseline.</p>
+            <p>Use <a href="https://github.com/xiaojiou176-open/CortexPilot-public/blob/main/docs/releases/v0.1.0-alpha.3.md"><code>docs/releases/v0.1.0-alpha.3.md</code></a> as the tracked repo-side release draft. Keep <code>first-public-release-draft.md</code> as the historical alpha.1 baseline.</p>
           </article>
         </div>
       </section>

docs/distribution/index.html

@@ -273,26 +273,27 @@
           <a href="https://github.com/xiaojiou176-open/CortexPilot-public">Repository</a>
           <a href="https://github.com/xiaojiou176-open/CortexPilot-public/releases">Releases</a>
         </nav>
-        <h1>Command Tower for Codex and Claude Code workflows.</h1>
+        <h1>One request. One command tower. One proof pack you can inspect.</h1>
         <p class="lede">
-          Start with one proven workflow, confirm the Workflow Case, then inspect Proof &amp; Replay.
-          CortexPilot gives Codex- and Claude Code-style teams one governed operator path instead
-          of scattered prompts, local scripts, and after-the-fact logs.
+          CortexPilot turns PM request -&gt; Workflow Case -&gt; Proof &amp; Replay into one governed
+          operator loop for Codex and Claude Code teams, so the first impression feels like a
+          flagship product story instead of a documentation directory.
         </p>
         <p class="caption">
           Current boundary: this is a repo-backed operator control plane, not a hosted product, and the
           shipped MCP surface remains read-only.
         </p>
         <p class="caption">
-          Official distribution today is the public repo, the Pages front door, one proven workflow baseline,
-          the repo-local read-only MCP server, and local starter or bundle material. The thin client and
-          contract packages are publish-ready but not published yet, while the shared package stays workspace-only,
-          so no public package release, hosted operator, Docker image, or public write-capable MCP is live today.
+          Official distribution today is the public repo, the Pages front door, one proven workflow
+          baseline, the repo-local read-only MCP server, and local starter or bundle material. The
+          thin client and contract packages are publish-ready but not published yet, while the shared
+          package stays workspace-only, so no public package release, hosted operator, Docker image,
+          or public write-capable MCP is live today.
         </p>
         <div class="actions">
           <a class="primary" href="./use-cases/">See the first proven workflow</a>
-          <a class="secondary" href="./compatibility/">Choose the right adoption path</a>
           <a class="secondary" href="./distribution/">Open distribution status</a>
+          <a class="secondary" href="./compatibility/">Choose the right adoption path</a>
         </div>
         <p class="caption">
           After those two doors, go deeper through
@@ -307,12 +308,25 @@ <h1>Command Tower for Codex and Claude Code workflows.</h1>
         <div class="panel">
           <img
             class="hero-image"
-            src="./assets/storefront/hero-command-tower.svg"
-            alt="CortexPilot flow from PM request to Command Tower to evidence and replay"
+            src="./assets/storefront/command-tower-showcase-card.svg"
+            alt="CortexPilot showcase card showing PM request, Command Tower, and Proof and Replay"
+          />
+          <p class="caption">
+            The public story should stay simple: one request enters, one Workflow Case becomes
+            visible, and one Proof &amp; Replay surface stays inspectable before you trust the
+            result.
+          </p>
+        </div>
+
+        <div class="panel">
+          <img
+            class="hero-image"
+            src="./assets/storefront/first-loop-storyboard.gif"
+            alt="CortexPilot storyboard showing the first public loop from PM request to evidence"
           />
           <p class="caption">
-            The public story should stay simple: send one request, watch it move through Command Tower,
-            confirm the Workflow Case, then inspect Proof &amp; Replay before you trust the result.
+            This tracked storyboard is the shareable first-loop asset: it shows the same public
+            path the README, Pages, and release notes are promising.
           </p>
         </div>
       </section>