@mushi-mushi/cli 0.17.0 → 0.17.2

package/README.md

@@ -100,6 +100,10 @@ Reads `package.json`, checks the npm registry for each installed
 `@mushi-mushi/*` package, and runs the right install command for your package
 manager (npm / pnpm / yarn / bun) to bump them to the latest stable release.
 
+**Console equivalent:** **Connect & Update → Create Upgrade PR** opens a GitHub
+draft PR for the linked repo (backed by `sdk-upgrade-worker`). Use the CLI for
+local bumps; use the PR flow when you want review + CI on the dependency change.
+
 ```bash
 mushi upgrade               # plan + install
 mushi upgrade --dry-run     # print the install command without running it
@@ -152,16 +156,23 @@ real-catalog regression guard).
 
 ### `mushi doctor`
 
-Checks CLI and SDK health.  Without flags it verifies local config and endpoint
-reachability only.
+Checks CLI and SDK health. **Ingest and dispatch (server) checks run by
+default** — pass `--no-server` / `--no-ingest` to limit it to local checks.
 
 ```bash
-mushi doctor                  # local checks only
-mushi doctor --server         # + calls /preflight on the backend (all 4 dispatch checks)
-mushi doctor --ingest         # + calls /v1/sync/ingest-setup (API key → heartbeat → first report)
+mushi doctor                  # local + ingest + dispatch readiness (the full picture)
+mushi doctor --no-server      # skip the dispatch-readiness /preflight checks
+mushi doctor --no-ingest      # skip the ingest-setup checks (SDK heartbeat, first report)
+mushi doctor --fix            # apply safe local fixes, then re-run and report the post-fix state
 mushi doctor --json           # machine-readable JSON output (exits 1 if any check fails)
+mushi doctor --qa-stories     # also flag enabled QA stories with setup issues (needs server creds)
+mushi doctor --host-app       # also verify host-app wiring (env vars, Cursor MCP, Capacitor notes)
 ```
 
+`--fix` writes any missing `.env.local` lines and wires the Cursor MCP config
+(via `mushi connect`), then re-runs every check so the printed result and exit
+code reflect the post-fix state rather than the stale pre-fix failures.
+
 Local checks performed:
 
 | Check | What it verifies |
@@ -170,9 +181,10 @@ Local checks performed:
 | Endpoint reachability | `GET /v1/sdk/config?project_id=...` returns 200 |
 | SDK install | `@mushi-mushi/web` or framework-specific SDK is in `node_modules` |
 
-With `--server`, also calls `GET /v1/admin/projects/:id/preflight` (same 4 checks
-the admin console dispatch popover uses) and merges the results.  The four
-server checks (`key` values returned by the endpoint):
+The dispatch-readiness checks (on by default; skip with `--no-server`) call
+`GET /v1/admin/projects/:id/preflight` (the same 4 checks the admin console
+dispatch popover uses) and merge the results.  The four server checks (`key`
+values returned by the endpoint):
 
 | `key` | What it verifies |
 |---|---|
@@ -181,15 +193,16 @@ server checks (`key` values returned by the endpoint):
 | `anthropic` | A BYOK Anthropic key is stored in Supabase Vault (`project_settings.byok_anthropic_key_ref`) |
 | `autofix` | The autofix toggle is ON (`project_settings.autofix_enabled = true`) |
 
-`--server` requires `adminOrApiKey` credentials — set `MUSHI_API_KEY` to an
-admin key (not a public SDK key).
+The dispatch-readiness checks require `adminOrApiKey` credentials — set
+`MUSHI_API_KEY` to an admin key (not a public SDK key). If you only have an SDK
+key, pass `--no-server` to skip them.
 
-With `--ingest`, also calls `GET /v1/sync/ingest-setup` (authenticated with the
-SDK API key) and reports each **required ingest step** — project exists, active
-API key, SDK heartbeat, at least one ingested report — plus a
-`Last SDK heartbeat` diagnostic with the timestamp and endpoint host. This is
-the same payload `mushi connect --wait` polls, so a failing step here tells you
-exactly why the banner isn't showing up.
+The ingest checks (on by default; skip with `--no-ingest`) call
+`GET /v1/sync/ingest-setup` (authenticated with the SDK API key) and report each
+**required ingest step** — project exists, active API key, SDK heartbeat, at
+least one ingested report — plus a `Last SDK heartbeat` diagnostic with the
+timestamp and endpoint host. This is the same payload `mushi connect --wait`
+polls, so a failing step here tells you exactly why the banner isn't showing up.
 
 ### `mushi reset <projectId>`
 
@@ -301,4 +314,4 @@ MIT
 <!-- mushi-readme-stats-footer -->
 ---
 
-<sub>Monorepo scale (June 2026): 43 edge functions · 234 SQL migrations · 13 outbound plugins · 11 inbound adapters. Canonical counts: <a href="https://github.com/kensaurus/mushi-mushi/blob/master/docs/stats.md">docs/stats.md</a> · <code>pnpm docs-stats</code></sub>
+<sub>Monorepo scale (June 2026): 47 edge functions · 256 SQL migrations · 13 outbound plugins · 11 inbound adapters · 18 pipeline agents. Canonical counts: <a href="https://github.com/kensaurus/mushi-mushi/blob/master/docs/stats.md">docs/stats.md</a> · <code>pnpm docs-stats</code></sub>

package/dist/chunk-EEQI5AFX.js

@@ -0,0 +1,6 @@
+// src/version.ts
+var MUSHI_CLI_VERSION = true ? "0.17.2" : "0.0.0-dev";
+
+export {
+  MUSHI_CLI_VERSION
+};

package/dist/{chunk-NYPX5KXR.js → chunk-S4WQHEGH.js}

@@ -273,6 +273,7 @@ function detectFramework(cwd, pkg) {
   if (deps.has("@angular/core")) return FRAMEWORKS.angular;
   if (deps.has("expo")) return FRAMEWORKS.expo;
   if (deps.has("react-native")) return FRAMEWORKS["react-native"];
+  if (deps.has("@capacitor/core") && deps.has("react")) return FRAMEWORKS.react;
   if (deps.has("@capacitor/core")) return FRAMEWORKS.capacitor;
   if (deps.has("svelte")) return FRAMEWORKS.svelte;
   if (deps.has("vue")) return FRAMEWORKS.vue;

package/dist/detect.js

@@ -7,7 +7,7 @@ import {
   installCommand,
   isFrameworkId,
   readPackageJson
-} from "./chunk-NYPX5KXR.js";
+} from "./chunk-S4WQHEGH.js";
 export {
   FRAMEWORKS,
   FRAMEWORK_IDS,