docs: fix public MCP install truth (#167)

Author: xiaojiou176

public-skills/README.md

@@ -11,7 +11,7 @@ Each bundle here must ship four things together:
 The bundle is only valid if an agent can answer all four questions without
 leaving this directory:
 
-1. How do I install the published OpenVibeCoding MCP package?
+1. How do I install the current live public OpenVibeCoding read-only MCP package?
 2. Which read-only tools does the MCP expose?
 3. Which lane should I choose first?
 4. Which claims remain out of bounds?

public-skills/openvibecoding-adoption-router/README.md

@@ -1,15 +1,16 @@
 # OpenVibeCoding Adoption Router
 
-This bundle teaches an agent how to connect the published OpenVibeCoding read-only
-MCP package and choose the right public adoption lane.
+This bundle teaches an agent how to connect the current live public OpenVibeCoding
+read-only MCP package and choose the right public adoption lane.
 
 This is OpenVibeCoding's secondary public adoption lane. The read-only MCP package
 plus the Official MCP Registry entry remain the primary machine-readable front
 door, and local coding-agent bundles stay example-only.
 
 ## What the agent learns here
 
-- how to install the published `openvibecoding-orchestrator==0.1.0a4` MCP package
+- how to install the current live legacy package
+  `cortexpilot-orchestrator==0.1.0a4` for the OpenVibeCoding read-only MCP
 - which read-only OpenVibeCoding tools exist and which are safe-first
 - how to choose between run/workflow inspection, queue/approval reads, and
   proof/incident reads
@@ -30,12 +31,17 @@ door, and local coding-agent bundles stay example-only.
 
 ## The shortest install path
 
-Use the published package, not a repo-local checkout:
+Use the live public package, not a repo-local checkout:
 
 ```bash
-uvx --from openvibecoding-orchestrator==0.1.0a4 openvibecoding-readonly-mcp
+uvx --from cortexpilot-orchestrator==0.1.0a4 openvibecoding-readonly-mcp
 ```
 
+Today the executable is already OpenVibeCoding-branded, but the published PyPI
+package still uses the legacy live name `cortexpilot-orchestrator`. Do not
+claim that the OpenVibeCoding-branded package name is live until the renamed
+publication actually exists.
+
 If the host needs a saved MCP config snippet, use the host-specific examples in
 `references/INSTALL.md`.
 

public-skills/openvibecoding-adoption-router/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: openvibecoding-adoption-router
-description: Teach the agent how to connect the published OpenVibeCoding read-only MCP package, choose the right public lane, and use the stable read-only tools without overclaiming hosted or write-capable support.
+description: Teach the agent how to connect the current live public package for the OpenVibeCoding read-only MCP, choose the right public lane, and use the stable read-only tools without overclaiming hosted or write-capable support.
 triggers:
   - openvibecoding
   - openvibecoding setup
@@ -15,7 +15,7 @@ Use this skill when the user needs the shortest truthful path into OpenVibeCodin
 
 ## What this skill teaches
 
-- how to install the published OpenVibeCoding MCP package
+- how to install the current live public package for the OpenVibeCoding read-only MCP
 - how to choose the right read-only tool for the current job
 - how to start with one public lane instead of mixing every surface together
 - how to keep the answer inside the current read-only public boundary
@@ -33,7 +33,7 @@ Use this skill when the user asks to:
 ## If the MCP is not connected yet
 
 Open `README.md` in this folder and follow `references/INSTALL.md`.
-Do not invent repo-local startup paths when the published package already
+Do not invent repo-local startup paths when the live public package already
 exists.
 
 ## Safe-first workflow

public-skills/openvibecoding-adoption-router/references/INSTALL.md

@@ -1,13 +1,21 @@
-# Install The Published OpenVibeCoding MCP
+# Install The Current Live Public OpenVibeCoding MCP
 
-Use the published PyPI package, not a repo-local checkout.
+Use the current live public PyPI package, not a repo-local checkout.
 
 ## Published package
 
-- package: `openvibecoding-orchestrator==0.1.0a4`
+- package: `cortexpilot-orchestrator==0.1.0a4`
 - executable: `openvibecoding-readonly-mcp`
 - transport: `stdio`
 
+Current truth:
+
+- the executable already uses the OpenVibeCoding name
+- the live published PyPI package still uses the legacy live name
+  `cortexpilot-orchestrator`
+- do not claim that `openvibecoding-orchestrator` is live until the renamed
+  package is actually published
+
 ## OpenHands example
 
 Use `OPENHANDS_MCP_CONFIG.json` as the starting point for your host config.

public-skills/openvibecoding-adoption-router/references/OPENCLAW_MCP_CONFIG.json

@@ -3,7 +3,7 @@
     "servers": {
       "openvibecoding-readonly": {
         "command": "uvx",
-        "args": ["--from", "openvibecoding-orchestrator==0.1.0a4", "openvibecoding-readonly-mcp"]
+        "args": ["--from", "cortexpilot-orchestrator==0.1.0a4", "openvibecoding-readonly-mcp"]
       }
     }
   }

public-skills/openvibecoding-adoption-router/references/OPENHANDS_MCP_CONFIG.json

@@ -2,7 +2,7 @@
   "mcpServers": {
     "openvibecoding-readonly": {
       "command": "uvx",
-      "args": ["--from", "openvibecoding-orchestrator==0.1.0a4", "openvibecoding-readonly-mcp"]
+      "args": ["--from", "cortexpilot-orchestrator==0.1.0a4", "openvibecoding-readonly-mcp"]
     }
   }
 }

public-skills/openvibecoding-adoption-router/references/mcp-install.md

@@ -1,21 +1,29 @@
-# Install The Published OpenVibeCoding MCP
+# Install The Current Live Public OpenVibeCoding MCP
 
-Use the published PyPI package, not a repo-local checkout.
+Use the current live public PyPI package, not a repo-local checkout.
 
 ## Published package
 
-- package: `openvibecoding-orchestrator==0.1.0a4`
+- package: `cortexpilot-orchestrator==0.1.0a4`
 - executable: `openvibecoding-readonly-mcp`
 - transport: `stdio`
 
+Current truth:
+
+- the executable already uses the OpenVibeCoding name
+- the live published PyPI package still uses the legacy live name
+  `cortexpilot-orchestrator`
+- do not claim that `openvibecoding-orchestrator` is live until the renamed
+  package is actually published
+
 ## OpenHands example
 
 Add the server to `~/.openhands/config.toml`:
 
 ```toml
 [mcp]
 stdio_servers = [
-  { name = "openvibecoding-readonly", command = "uvx", args = ["--from", "openvibecoding-orchestrator==0.1.0a4", "openvibecoding-readonly-mcp"] }
+  { name = "openvibecoding-readonly", command = "uvx", args = ["--from", "cortexpilot-orchestrator==0.1.0a4", "openvibecoding-readonly-mcp"] }
 ]
 ```
 
@@ -29,7 +37,7 @@ Add the server to your saved MCP server config:
     "servers": {
       "openvibecoding-readonly": {
         "command": "uvx",
-        "args": ["--from", "openvibecoding-orchestrator==0.1.0a4", "openvibecoding-readonly-mcp"]
+        "args": ["--from", "cortexpilot-orchestrator==0.1.0a4", "openvibecoding-readonly-mcp"]
       }
     }
   }