docs: record archived legacy distribution truth (#196)

Co-authored-by: tester <test@example.com>

Author: xiaojiou176

README.md

@@ -101,10 +101,12 @@ The shortest truthful answer today is:
 > `openvibecoding-orchestrator==0.1.0a4` PyPI package plus the live
 > `io.github.xiaojiou176-open/openvibecoding-readonly@0.1.0a4` Official MCP
 > Registry entry for that same read-only runtime, and a live ClawHub skill.
-> The older `cortexpilot-orchestrator==0.1.0a4` package and
-> `io.github.xiaojiou176-open/cortexpilot-readonly@0.1.0a4` registry entry
-> still remain online as legacy compatibility surfaces; the OpenVibeCoding names
-> are canonical, while the legacy MCP entry is now explicitly deprecated.
+> The older `cortexpilot-orchestrator==0.1.0a4` package has now been archived on
+> PyPI as a legacy compatibility lane, which keeps the old release reachable by
+> direct URL while removing it from PyPI search and blocking new uploads. The
+> older `io.github.xiaojiou176-open/cortexpilot-readonly@0.1.0a4` registry entry
+> still remains online as a deprecated compatibility surface. The OpenVibeCoding
+> names are canonical, while the legacy MCP entry is explicitly deprecated.
 > Local coding-agent starters and bundle examples remain helper materials, not
 > the primary public front door. MCP.so still has an open external submission
 > receipt, while the previous OpenHands/extensions submission is closed without
@@ -114,7 +116,7 @@ The shortest truthful answer today is:
 Use these buckets:
 
 - **Shipped now**: repo, Pages, proof-first docs, read-only MCP, live OpenVibeCoding PyPI package + Official MCP Registry entry, ClawHub skill
-- **Legacy compatibility still live**: `cortexpilot-orchestrator==0.1.0a4` and `io.github.xiaojiou176-open/cortexpilot-readonly@0.1.0a4` remain reachable; treat them as compatibility lanes rather than the canonical front door
+- **Legacy compatibility**: `cortexpilot-orchestrator==0.1.0a4` is now archived on PyPI, and `io.github.xiaojiou176-open/cortexpilot-readonly@0.1.0a4` remains reachable as a deprecated MCP compatibility entry
 - **Starter-only / example lane**: Codex / Claude Code / OpenClaw local starter kits and local coding-agent bundle examples
 - **Submitted externally**: `chatmcp/mcpso#1559` is still open; `OpenHands/extensions#151` remains a public receipt but is closed without a live listing
 - **Publish-ready but deferred**:

docs/distribution/index.html

@@ -354,7 +354,7 @@ <h1>Exact distribution status for OpenVibeCoding.</h1>
         </p>
         <div class="pill-row">
           <span class="pill">Shipped now: repo, Pages, first proven workflow, read-only MCP, live OpenVibeCoding PyPI + Official MCP Registry entry, ClawHub skill</span>
-          <span class="pill">Legacy compatibility still live: CortexPilot PyPI + deprecated MCP entry remain reachable while OpenVibeCoding stays canonical</span>
+          <span class="pill">Legacy compatibility: archived CortexPilot PyPI + deprecated MCP entry remain reachable while OpenVibeCoding stays canonical</span>
           <span class="pill">Starter/example lane: Codex / Claude Code config seeds and the local coding-agent bundle</span>
           <span class="pill">External receipts: MCP.so is still open; OpenHands/extensions is a closed receipt without a live listing</span>
           <span class="pill">Publish-ready but deferred: frontend-api-client and frontend-api-contract; frontend-shared stays workspace-only</span>
@@ -452,18 +452,18 @@ <h2>Current distribution matrix</h2>
               <tr>
                 <td><strong>PyPI package</strong></td>
                 <td><span class="badge shipped">shipped</span></td>
-                <td><code>openvibecoding-orchestrator==0.1.0a4</code> is the live canonical package for the public read-only MCP runtime. The older <code>cortexpilot-orchestrator==0.1.0a4</code> package still remains reachable as a legacy compatibility lane.</td>
+                <td><code>openvibecoding-orchestrator==0.1.0a4</code> is the live canonical package for the public read-only MCP runtime. The older <code>cortexpilot-orchestrator==0.1.0a4</code> package is now archived on PyPI as a legacy compatibility lane, which keeps the direct package page reachable while removing it from search and blocking new uploads.</td>
                 <td><a href="https://pypi.org/project/openvibecoding-orchestrator/0.1.0a4/">PyPI package</a></td>
                 <td>Package install only</td>
-                <td>Keep public docs and starter snippets aligned to the OpenVibeCoding install path, and do not imply that the legacy compatibility package has already disappeared.</td>
+                <td>Keep public docs and starter snippets aligned to the OpenVibeCoding install path, and describe the archived CortexPilot package as compatibility-only rather than an active front door.</td>
               </tr>
               <tr>
                 <td><strong>Official MCP Registry</strong></td>
                 <td><span class="badge shipped">shipped</span></td>
                 <td>The live canonical registry entry uses <code>io.github.xiaojiou176-open/openvibecoding-readonly</code>. The older <code>io.github.xiaojiou176-open/cortexpilot-readonly</code> entry still remains reachable, but it is now marked deprecated.</td>
                 <td><a href="https://registry.modelcontextprotocol.io/v0/servers?search=io.github.xiaojiou176-open/openvibecoding-readonly">Registry entry</a></td>
                 <td>Registry discovery, stdio package install</td>
-                <td>Keep the repo-side manifest and public MCP docs aligned to the OpenVibeCoding registry entry, while describing the older CortexPilot entry as deprecated compatibility rather than pretending it is gone.</td>
+                <td>Keep the repo-side manifest and public MCP docs aligned to the OpenVibeCoding registry entry, while describing the older CortexPilot entry as deprecated compatibility rather than pretending it is gone or trying to hard-delete it without a supported registry path.</td>
               </tr>
               <tr>
                 <td><strong>Codex starter</strong></td>