@topolo/cli 0.7.4 → 0.8.0

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@topolo/cli",
-  "version": "0.7.4",
-  "topoloPublishedVersion": "0.7.4",
-  "description": "Command-line interface for Topolo developers, operators, and agents, with internal first-party scaffolding available under the topolo platform namespace.",
+  "version": "0.8.0",
+  "topoloPublishedVersion": "0.8.0",
+  "description": "Public command-line interface for Topolo customer organizations, developers, and agents.",
   "type": "module",
   "bin": {
     "topolo": "dist/index.js"
@@ -12,7 +12,7 @@
     "skills"
   ],
   "scripts": {
-    "build": "tsup && node scripts/vendor-generator.mjs",
+    "build": "tsup",
     "dev": "tsup --watch",
     "typecheck": "tsc --noEmit",
     "start": "node dist/index.js",
@@ -21,10 +21,12 @@
     "coverage": "vitest run --coverage"
   },
   "dependencies": {
+    "@modelcontextprotocol/sdk": "^1.0.0",
+    "@topolo/mcp": "0.11.0",
+    "@topolo/sdk": "0.11.0",
     "commander": "^12.1.0"
   },
   "devDependencies": {
-    "@topolo/sdk": "0.10.4",
     "@types/node": "^20.12.0",
     "@vitest/coverage-v8": "3.2.6",
     "tsup": "^8.0.0",

package/skills/topolo/SKILL.md

@@ -15,28 +15,23 @@ The CLI requires Node 20 or newer:
 
 ```bash
 command -v topolo || npm install -g @topolo/cli
-topolo skills install
+topolo setup
+topolo doctor
 ```
 
-`topolo skills install` installs this skill and registers the Topolo MCP server for Claude Code and Codex. Both use the same credential written by `topolo auth login`.
+`topolo setup` installs this skill and registers the exact MCP server bundled with the CLI for Claude Code and Codex. It does not depend on `npx`, `PATH`, a source checkout, or a second global package. Both surfaces use the same credential written by `topolo auth login`. `topolo doctor` then verifies the credential, MCP protocol handshake, tool discovery, and an identity call end to end.
 
-Before testing platform behavior, verify every installed agent surface against
-the package registry. Do not diagnose behavior with stale tooling:
+Before diagnosing behavior, verify the installed customer tooling against the package registry:
 
 ```bash
 topolo --version
-npm list -g --depth=0 @topolo/cli @topolo/mcp @topolo/sdk
+npm list -g --depth=0 @topolo/cli
 npm view @topolo/cli version
-npm view @topolo/mcp version
-npm view @topolo/sdk version
 ```
 
-If any version differs, install the three latest released versions together,
-run `topolo skills install`, and restart the MCP client before testing. Record
-the versions used with the results. Source builds may test a candidate fix, but
-must be labelled separately from released-tooling proof.
+If the CLI version differs, update `@topolo/cli`, run `topolo setup`, run `topolo doctor`, and restart the agent. The CLI owns compatible SDK and MCP versions; customers must not assemble that dependency set manually. Record the CLI version used with results.
 
-Production is the default. Use `--env staging` on every staging command, or set `TOPOLO_ENV=staging`. Never mix staging discovery with production execution.
+Production is the customer environment. Do not use internal development, staging, seed, deployment, audit, scaffold, or release workflows from this skill; those belong to the restricted `topolo-platform` toolchain.
 
 ## Authentication gate
 
@@ -247,7 +242,6 @@ Use `TOPOLO_DEBUG=1` only when diagnostics are needed. Preserve `X-Topolo-Reques
 ## Public references
 
 - Documentation: `https://docs.topolo.app`
-- Staging documentation: `https://docs.stg.topolo.us`
 - Developers console: `https://developers.topolo.app`
 - CLI help: `topolo --help` and `topolo <command> --help`