@mightybot/mbcli 0.5.417 → 0.6.0

package/README.md

@@ -8,60 +8,36 @@ a per-platform optional dependency (`@mightybot/mbcli-<platform>`), and npm
 installs only the one matching your machine.
 
 
-## Run — two ways
+## Start here — one command
 
-The actual command is always **`mb`**; the package name (`@mightybot/mbcli`)
-is just what npm fetches. Pick whichever fits:
-
-### Option A — `npx` (no install, always newest)
+With Node.js 16+, this one command is the entire setup — it signs you in and
+registers the MCP server with your AI agents:
 
 ```bash
-npx @mightybot/mbcli@latest version       # prod (stable)
-npx @mightybot/mbcli@latest auth login
-npx @mightybot/mbcli@preprod version      # preprod (newest build, pre-promotion)
+npx @mightybot/mbcli@latest setup
 ```
 
-npm fetches + caches only your platform's binary on first run; `@latest` /
-`@preprod` makes npx re-check the registry each run, so you always get the
-newest build for that channel. Nothing to upgrade.
+`setup` = `mb auth login` (browser sign-in) + `mb mcp install --agent all`.
+`npx` fetches the right platform binary on demand — nothing to install first.
 
-### Option B — global install (`mb` on PATH, shorter commands)
+Run any other command the same way:
 
 ```bash
-npm i -g @mightybot/mbcli@latest          # or @preprod
-mb version
-mb auth login
-mb setup
+npx @mightybot/mbcli@latest workflow list
+npx @mightybot/mbcli@latest version
 ```
 
-Puts a real `mb` command on your PATH — no `npx`, no scope prefix. Faster
-(no per-run resolution), but it does **not** auto-update: you are pinned to the
-version installed until you re-run the install to upgrade:
-
-```bash
-npm i -g @mightybot/mbcli@latest          # upgrade to newest latest
-npm i -g @mightybot/mbcli@preprod         # or newest preprod
-```
-
-| | `npx …@latest` | `npm i -g …@latest` |
-|---|---|---|
-| Command | `npx @mightybot/mbcli@latest <cmd>` | `mb <cmd>` |
-| Always newest | ✅ auto | ❌ frozen at install — re-install to upgrade |
-| Per-run overhead | small | none |
-
-Either way the one-time `~/.npmrc` (above) is required, and `mb setup` works the
-same — it installs the MCP server to the stable `~/.mightybot/mcp/mb`,
-independent of how you run the CLI.
+> Prefer a permanent `mb` on your PATH? `npm i -g @mightybot/mbcli@latest`,
+> then run `mb <cmd>` (re-run the install to upgrade). The MCP server installs to
+> the stable `~/.mightybot/mcp/mb` either way.
 
 ### Release channels
 
-| Tag | Published when | Who uses it |
-|-----|----------------|-------------|
-| `preprod` | every `master` merge (version `0.5.<run>`) | testers validating a build |
-| `latest` | manual promotion of a tested `preprod` version (no rebuild) | everyone |
+- **`@latest`** — the stable release. Use this. *(recommended for everyone)*
+- **`@preprod`** — the newest build, ahead of `@latest`; use it to try the most
+  recent changes before they're promoted.
 
-Promotion moves the `latest` dist-tag onto the exact `preprod` artifact that was
-tested — same bytes, no rebuild.
+`@latest` is promoted from a tested `@preprod` build — same bytes, no rebuild.
 
 ### Always getting the newest
 
@@ -75,11 +51,11 @@ npx --prefer-online @mightybot/mbcli version  # revalidates cache against the re
 
 ### Release-age cooldown
 
-If your npm config sets `min-release-age` (the MightyBot repo `.npmrc` sets
-`min-release-age=7` as a supply-chain guard), npm refuses any version published
-in the last N days — so a **same-day release fails with `ENOVERSIONS` / "No
-versions available for @mightybot/mbcli"** even though it published fine.
-Override the cooldown to install a fresh build:
+If your npm config (or your organization's `.npmrc`) sets `min-release-age` as a
+supply-chain guard, npm refuses any version published in the last N days — so a
+**same-day release fails with `ENOVERSIONS` / "No versions available for
+@mightybot/mbcli"** even though it published fine. Override the cooldown to
+install a fresh build:
 
 ```bash
 npx --min-release-age=0 @mightybot/mbcli@latest          # CLI flag, or
@@ -90,18 +66,6 @@ Once the build is older than the cooldown window, plain `npx …` works with no
 flag. (This guard is intentional — it protects against installing a
 freshly-compromised package; the override is only for trusted same-day builds.)
 
-## One-step setup (auth + MCP)
-
-After installing, run **one** command to get fully provisioned — it logs you in
-and registers the MCP server with Codex / Claude Code / OpenCode:
-
-```bash
-npx @mightybot/mbcli@latest setup
-```
-
-`mb setup` = `mb auth login` (browser device auth) + `mb mcp install --agent all`.
-Auth flags pass through, e.g. `setup --base-url https://platform-dev.mightybot.ai`.
-
 ## Commands
 
 Every example below uses the bare `mb` (after a global install or inside
@@ -130,7 +94,7 @@ mb setup [auth flags]   # mb auth login + mb mcp install --agent all
 ```
 
 Logs in (browser device auth) and registers the MCP server with all detected
-agents. Auth flags pass through (e.g. `--base-url https://platform-dev.mightybot.ai`).
+agents. Auth flags pass through (e.g. `--base-url <your-platform-url>`).
 
 ### `mb auth` — platform authentication
 
@@ -175,7 +139,6 @@ mb surface step          # step-level detail
 | `mb workflow create` / `update` / `duplicate` / `delete` | Manage definitions. |
 | `mb workflow export <id>` | Export a definition (e.g. for diffing/backup). |
 | `mb workflow diff` | Diff two definitions/versions. |
-| `mb workflow validate <id>` | Validate a definition. |
 | `mb workflow versions` / `version` / `version-history` / `version-diff` | Inspect version history and compare versions. |
 
 ### `mb git` — git ↔ workflow sync state

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@mightybot/mbcli",
-  "version": "0.5.417",
-  "description": "MightyBot mb CLI and local design-time MCP server",
+  "version": "0.6.00",
+  "description": "MightyBot mb CLI and local MCP server",
   "bin": {
     "mb": "bin/mb.js"
   },
@@ -15,11 +15,11 @@
   "license": "UNLICENSED",
   "private": false,
   "optionalDependencies": {
-    "@mightybot/mbcli-darwin-arm64": "0.5.417",
-    "@mightybot/mbcli-darwin-x64": "0.5.417",
-    "@mightybot/mbcli-linux-x64": "0.5.417",
-    "@mightybot/mbcli-linux-arm64": "0.5.417",
-    "@mightybot/mbcli-win32-x64": "0.5.417"
+    "@mightybot/mbcli-darwin-arm64": "0.6.00",
+    "@mightybot/mbcli-darwin-x64": "0.6.00",
+    "@mightybot/mbcli-linux-x64": "0.6.00",
+    "@mightybot/mbcli-linux-arm64": "0.6.00",
+    "@mightybot/mbcli-win32-x64": "0.6.00"
   },
   "homepage": "https://mightybot.ai"
 }