@mushi-mushi/cli 0.17.1 → 0.18.0

package/CONTRIBUTING.md

@@ -63,7 +63,7 @@ packages/
   verify/        Fix verification (BSL)
 apps/
   admin/         Admin dashboard (React + Tailwind)
-  docs/          Documentation site (planned)
+  docs/          Documentation site (Nextra — apps/docs)
 tooling/
   eslint-config/ Shared ESLint flat config
   tsconfig/      Shared TypeScript configs
@@ -81,6 +81,28 @@ tooling/
    ```
 6. Open a pull request
 
+### Documentation (docs-as-code)
+
+If your PR changes **user-visible SDK or CLI behavior**, update docs in the **same PR**:
+
+| Surface | When to update |
+| --- | --- |
+| `packages/*/README.md` | npm-facing install/API/config changes for that package |
+| `apps/docs/content/**/*.mdx` | Long-form guides, quickstarts, admin console docs |
+| Root `README.md` | Marketing stats only when counts change — run `pnpm check:docs-stats` |
+
+Guardrails (run locally before pushing):
+
+```bash
+pnpm check:docs-stats          # root README stat badges
+pnpm check:sdk-version-matrix  # apps/docs/content/sdks/index.mdx versions
+pnpm check:internal-doc-links  # dead /foo links in MDX
+pnpm check:bundle-docs         # @mushi-mushi/web size-limit vs README
+pnpm gen:llms-txt              # regenerate apps/docs/public/llms.txt after nav changes
+```
+
+README changes on npm packages only appear on [npmjs.com](https://www.npmjs.com) after the next **Changesets publish**.
+
 ## Changesets
 
 We use [Changesets](https://github.com/changesets/changesets) for versioning. If your PR modifies a published package (`core`, `web`, `react`, `vue`, `svelte`, `angular`, `react-native`, `cli`, `mcp`), add a changeset:

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
@@ -302,6 +306,16 @@ mushi slack test
 - The `--api-key` flag leaks into `ps -ef` — prefer the interactive prompt on shared machines.
 - Full stack traces on error: `DEBUG=mushi mushi init`.
 
+## Programmatic imports
+
+The CLI is also importable for tooling (used by `create-mushi-mushi`):
+
+| Subpath | Exports |
+| --- | --- |
+| `@mushi-mushi/cli/init` | `runInit`, `InitOptions` |
+| `@mushi-mushi/cli/detect` | Framework / package-manager detection |
+| `@mushi-mushi/cli/version` | `MUSHI_CLI_VERSION` |
+
 ## License
 
 MIT
@@ -310,4 +324,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-ZB6ITDCQ.js

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