chore: rename public command references to stackfoundry

Prefer the stackfoundry command in docs, examples, package scripts, and generated registry guidance while keeping internal implementation paths unchanged.

Author: jesseoue

README.md

@@ -108,27 +108,27 @@ pnpm registry:presets
 pnpm stackfoundry add preset next-saas --target ./my-app --dry-run
 ```
 
-## CLI
+## StackFoundry Command
 
-The CLI intentionally stays on Node + pnpm. It is a small registry/install engine, not an interactive component wizard.
+The `stackfoundry` command intentionally stays on Node + pnpm. It is a small registry/install engine, not an interactive component wizard.
 
 ```bash
-pnpm cli categories
-pnpm cli list --category billing
-pnpm cli list --status experimental
-pnpm cli search webhook
-pnpm cli info stripe-billing
-pnpm cli add api-keys --target ./my-app --dry-run
-pnpm cli diff api-keys --target ./my-app
-pnpm cli build
-pnpm cli doctor
+pnpm stackfoundry categories
+pnpm stackfoundry list --category billing
+pnpm stackfoundry list --status experimental
+pnpm stackfoundry search webhook
+pnpm stackfoundry info stripe-billing
+pnpm stackfoundry add api-keys --target ./my-app --dry-run
+pnpm stackfoundry diff api-keys --target ./my-app
+pnpm stackfoundry build
+pnpm stackfoundry doctor
 ```
 
-Why Node instead of Bun or a larger CLI framework:
+Why Node instead of Bun or a larger command framework:
 
 - the repository already targets Node `>=22 <25`
 - Vercel builds use Node and pnpm cleanly
-- the CLI surface is validation, discovery, install, diff, and build
+- the command surface is validation, discovery, install, diff, and build
 - avoiding another runtime keeps module consumption simpler
 
 ## Registry Model
@@ -227,7 +227,7 @@ pnpm build:web
 
 ```text
 apps/
-  cli/                 # StackFoundry CLI
+  cli/                 # StackFoundry command source
   web/                 # public site and registry host
 docs/                  # product, registry, and maintainer docs
 examples/              # reproducible install walkthroughs
@@ -258,7 +258,7 @@ See [`docs/repository.md`](./docs/repository.md) for ownership rules.
 
 ## Status
 
-StackFoundry is experimental. The registry, CLI, public registry output, and website are active. Module APIs and file targets can still change while the registry is being shaped.
+StackFoundry is experimental. The registry, command, public registry output, and website are active. Module APIs and file targets can still change while the registry is being shaped.
 
 ## Contributing
 

apps/cli/README.md

@@ -1,6 +1,6 @@
-# StackFoundry CLI
+# StackFoundry Command
 
-The CLI is the local install engine for StackFoundry registry modules.
+The `stackfoundry` command is the local install engine for StackFoundry registry modules.
 
 ## Responsibilities
 
@@ -23,18 +23,18 @@ Shared logic is imported through workspace package aliases:
 ## Useful Commands
 
 ```bash
-pnpm cli list
-pnpm cli categories
-pnpm cli list --category billing
-pnpm cli search webhook
-pnpm cli info stripe-billing
-pnpm cli presets
-pnpm cli doctor
-pnpm cli build
-pnpm cli add api-keys --target /tmp/app --dry-run
-pnpm cli add preset provider-adapters --target /tmp/app --dry-run
-pnpm cli add https://stackfoundry.dev/r/api-keys.json --target /tmp/app --dry-run
-pnpm cli diff api-keys --target /tmp/app
+pnpm stackfoundry list
+pnpm stackfoundry categories
+pnpm stackfoundry list --category billing
+pnpm stackfoundry search webhook
+pnpm stackfoundry info stripe-billing
+pnpm stackfoundry presets
+pnpm stackfoundry doctor
+pnpm stackfoundry build
+pnpm stackfoundry add api-keys --target /tmp/app --dry-run
+pnpm stackfoundry add preset provider-adapters --target /tmp/app --dry-run
+pnpm stackfoundry add https://stackfoundry.dev/r/api-keys.json --target /tmp/app --dry-run
+pnpm stackfoundry diff api-keys --target /tmp/app
 ```
 
 ## Quality Gate

apps/web/app/docs/page.tsx

@@ -3,7 +3,7 @@ import type { Metadata } from "next";
 export const metadata: Metadata = {
   title: "Docs",
   description:
-    "Install production SaaS modules as editable source code with StackFoundry's registry, CLI, presets, and provider adapters.",
+    "Install production SaaS modules as editable source code with StackFoundry's registry, command, presets, and provider adapters.",
   alternates: {
     canonical: "/docs",
   },
@@ -445,7 +445,7 @@ export default function DocsPage() {
             <span className="docs-brand-chip">Docs</span>
           </a>
           <div className="docs-search" aria-hidden="true">
-            <span>Search docs, modules, CLI</span>
+            <span>Search docs, modules, command</span>
             <kbd>⌘</kbd>
             <kbd>K</kbd>
           </div>
@@ -560,9 +560,9 @@ export default function DocsPage() {
               2. Add to an existing app <Anchor id="install-existing" />
             </h2>
             <p>
-              Existing apps should start with a dry run. The CLI resolves registry dependencies,
-              prints the proposed file changes, shows env notes, and leaves the review decision with
-              you. After install, the source is yours to edit like any other code.
+              Existing apps should start with a dry run. The StackFoundry command resolves registry
+              dependencies, prints the proposed file changes, shows env notes, and leaves the review
+              decision with you. After install, the source is yours to edit like any other code.
             </p>
             <CodeBlock label="terminal">{`$ pnpm stackfoundry add stripe-billing --target ./my-app --dry-run
 · resolving registry dependency drizzle-postgres

docs/registry-compat.md

@@ -6,7 +6,7 @@ The goal is to publish production SaaS modules as editable source: a registry it
 
 ## Install a StackFoundry Block
 
-With the StackFoundry CLI:
+With the StackFoundry command:
 
 ```bash
 pnpm stackfoundry add https://stackfoundry.dev/r/api-keys.json --target ./my-app
@@ -39,7 +39,7 @@ pnpm stackfoundry add http://localhost:3000/r/api-keys.json --target /tmp/app
 - Internal module dependencies are emitted as full `https://stackfoundry.dev/r/<dependency>.json` registry URLs.
 - Env requirements are emitted as `envVars` and retained in `meta.env`.
 - Module and shared technology skills are emitted as `maintenanceSkills` so registry URL installs include maintenance guidance.
-- StackFoundry CLI can install generated module items directly, including aggregate preset blocks such as `/r/provider-adapters.json`.
+- The StackFoundry command can install generated module items directly, including aggregate preset blocks such as `/r/provider-adapters.json`.
 - `/r/presets/*.json` files are StackFoundry preset manifests for tooling and inspection. They are intentionally not shadcn registry item documents; use `/r/<preset>.json` for installable preset payloads.
 
 ## StackFoundry Rules

docs/repository.md

@@ -7,10 +7,10 @@ StackFoundry is a source registry. Every directory should either own product sou
 - `apps/` contains runnable applications.
 - `docs/` contains product and maintainer documentation.
 - `examples/` contains install targets and walkthroughs used to prove registry modules in realistic app shapes.
-- `packages/` is reserved for extracted library packages when CLI, registry loading, schema validation, and shared utilities outgrow `apps/cli`.
+- `packages/` is reserved for extracted library packages when command behavior, registry loading, schema validation, and shared utilities outgrow `apps/cli`.
 - `public/r/` contains generated registry output. Do not edit it by hand.
 - `registry/` contains source modules and presets. This is the product surface.
-- `scripts/` is reserved for standalone maintenance scripts that should not live inside the CLI.
+- `scripts/` is reserved for standalone maintenance scripts that should not live inside the StackFoundry command.
 
 ## Applications
 
@@ -42,4 +42,4 @@ Run:
 pnpm check
 ```
 
-This runs registry validation, CLI syntax checks, dry-run installs, real install smoke tests, registry generation, compatibility verification, and the web build.
+This runs registry validation, command syntax checks, dry-run installs, real install smoke tests, registry generation, compatibility verification, and the web build.

examples/next-saas/README.md

@@ -9,13 +9,13 @@ The example is command-driven so it stays reproducible and does not duplicate a
 ```bash
 rm -rf /tmp/stackfoundry-next-saas
 mkdir -p /tmp/stackfoundry-next-saas
-pnpm cli add preset next-saas --target /tmp/stackfoundry-next-saas
+pnpm stackfoundry add preset next-saas --target /tmp/stackfoundry-next-saas
 ```
 
 ## Dry Run
 
 ```bash
-pnpm cli add preset next-saas --target /tmp/stackfoundry-next-saas --dry-run
+pnpm stackfoundry add preset next-saas --target /tmp/stackfoundry-next-saas --dry-run
 ```
 
 ## What This Proves

examples/saas-coverage/README.md

@@ -14,13 +14,13 @@ This example proves the broad SaaS coverage preset:
 ```bash
 rm -rf /tmp/stackfoundry-saas-coverage
 mkdir -p /tmp/stackfoundry-saas-coverage
-pnpm cli add preset saas-coverage --target /tmp/stackfoundry-saas-coverage
+pnpm stackfoundry add preset saas-coverage --target /tmp/stackfoundry-saas-coverage
 ```
 
 ## Dry Run
 
 ```bash
-pnpm cli add preset saas-coverage --target /tmp/stackfoundry-saas-coverage --dry-run
+pnpm stackfoundry add preset saas-coverage --target /tmp/stackfoundry-saas-coverage --dry-run
 ```
 
 ## What This Proves

package.json

@@ -16,43 +16,43 @@
     "dev": "pnpm dev:web",
     "build": "pnpm registry:build && pnpm build:web",
     "check": "pnpm check:registry && pnpm check:web",
-    "check:registry": "pnpm registry:doctor && pnpm lint:cli && pnpm lint:packages && pnpm registry:build && pnpm registry:compat && pnpm test:brand && pnpm test:registry",
+    "check:registry": "pnpm registry:doctor && pnpm lint:command && pnpm lint:packages && pnpm registry:build && pnpm registry:compat && pnpm test:brand && pnpm test:registry",
     "check:web": "pnpm lint:web && pnpm typecheck:web && pnpm build:web",
-    "lint": "pnpm lint:cli && pnpm lint:packages && pnpm lint:web",
-    "lint:cli": "node --check apps/cli/src/cli.mjs",
+    "lint": "pnpm lint:command && pnpm lint:packages && pnpm lint:web",
     "lint:web": "biome check apps/web",
     "lint:web:fix": "biome check --write apps/web",
     "typecheck:web": "pnpm --filter @stackfoundry/web typecheck",
     "test": "pnpm test:registry",
     "test:brand": "node scripts/smoke-brand.mjs",
     "test:registry": "pnpm test:registry:dry && pnpm test:registry:install",
-    "test:registry:dry": "rm -rf /tmp/stackfoundry-test && mkdir -p /tmp/stackfoundry-test && pnpm cli list >/dev/null && pnpm cli presets >/dev/null && pnpm cli add next-saas-shell --target /tmp/stackfoundry-test/next-saas-module >/dev/null && test -f /tmp/stackfoundry-test/next-saas-module/apps/web/src/components/stackfoundry/app-shell.tsx && pnpm cli add auth-core --target /tmp/stackfoundry-test/auth-core >/dev/null && test -f /tmp/stackfoundry-test/auth-core/docs/auth-architecture.md && pnpm cli add cloudflare-pages --target /tmp/stackfoundry-test/cloudflare-pages >/dev/null && test -f /tmp/stackfoundry-test/cloudflare-pages/apps/web/src/lib/stackfoundry/providers/cloudflare-pages.ts && pnpm cli add railway-deploy --target /tmp/stackfoundry-test/railway-deploy >/dev/null && test -f /tmp/stackfoundry-test/railway-deploy/apps/web/src/lib/stackfoundry/providers/railway-deploy.ts && pnpm cli add api-keys --target /tmp/stackfoundry-test >/dev/null && pnpm cli diff api-keys --target /tmp/stackfoundry-test >/dev/null && pnpm cli add preset next-saas --target /tmp/stackfoundry-test --dry-run >/dev/null && pnpm cli add preset provider-adapters --target /tmp/stackfoundry-test --dry-run >/dev/null && pnpm cli add preset saas-coverage --target /tmp/stackfoundry-test --dry-run >/dev/null && pnpm cli add public/r/api-keys.json --target /tmp/stackfoundry-test --dry-run >/dev/null && pnpm cli add public/r/provider-adapters.json --target /tmp/stackfoundry-test --dry-run >/dev/null",
-    "test:registry:install": "rm -rf /tmp/stackfoundry-install && mkdir -p /tmp/stackfoundry-install/next-saas /tmp/stackfoundry-install/provider-adapters /tmp/stackfoundry-install/cloudflare-native /tmp/stackfoundry-install/vercel-native /tmp/stackfoundry-install/saas-coverage /tmp/stackfoundry-install/registry-api-keys /tmp/stackfoundry-install/registry-adapters /tmp/stackfoundry-install/url-api-keys /tmp/stackfoundry-install/url-adapters && pnpm cli add preset next-saas --target /tmp/stackfoundry-install/next-saas >/dev/null && pnpm cli add preset provider-adapters --target /tmp/stackfoundry-install/provider-adapters >/dev/null && pnpm cli add preset cloudflare-native --target /tmp/stackfoundry-install/cloudflare-native >/dev/null && pnpm cli add preset vercel-native --target /tmp/stackfoundry-install/vercel-native >/dev/null && pnpm cli add preset saas-coverage --target /tmp/stackfoundry-install/saas-coverage >/dev/null && pnpm cli add public/r/api-keys.json --target /tmp/stackfoundry-install/registry-api-keys >/dev/null && pnpm cli add public/r/provider-adapters.json --target /tmp/stackfoundry-install/registry-adapters >/dev/null && pnpm cli add https://stackfoundry.dev/r/api-keys.json --target /tmp/stackfoundry-install/url-api-keys >/dev/null && pnpm cli add https://stackfoundry.dev/r/provider-adapters.json --target /tmp/stackfoundry-install/url-adapters >/dev/null",
-    "cli": "node apps/cli/src/cli.mjs",
-    "registry:list": "pnpm cli list",
-    "registry:categories": "pnpm cli categories",
-    "registry:presets": "pnpm cli presets",
-    "registry:doctor": "pnpm cli doctor",
+    "test:registry:dry": "rm -rf /tmp/stackfoundry-test && mkdir -p /tmp/stackfoundry-test && pnpm stackfoundry list >/dev/null && pnpm stackfoundry presets >/dev/null && pnpm stackfoundry add next-saas-shell --target /tmp/stackfoundry-test/next-saas-module >/dev/null && test -f /tmp/stackfoundry-test/next-saas-module/apps/web/src/components/stackfoundry/app-shell.tsx && pnpm stackfoundry add auth-core --target /tmp/stackfoundry-test/auth-core >/dev/null && test -f /tmp/stackfoundry-test/auth-core/docs/auth-architecture.md && pnpm stackfoundry add cloudflare-pages --target /tmp/stackfoundry-test/cloudflare-pages >/dev/null && test -f /tmp/stackfoundry-test/cloudflare-pages/apps/web/src/lib/stackfoundry/providers/cloudflare-pages.ts && pnpm stackfoundry add railway-deploy --target /tmp/stackfoundry-test/railway-deploy >/dev/null && test -f /tmp/stackfoundry-test/railway-deploy/apps/web/src/lib/stackfoundry/providers/railway-deploy.ts && pnpm stackfoundry add api-keys --target /tmp/stackfoundry-test >/dev/null && pnpm stackfoundry diff api-keys --target /tmp/stackfoundry-test >/dev/null && pnpm stackfoundry add preset next-saas --target /tmp/stackfoundry-test --dry-run >/dev/null && pnpm stackfoundry add preset provider-adapters --target /tmp/stackfoundry-test --dry-run >/dev/null && pnpm stackfoundry add preset saas-coverage --target /tmp/stackfoundry-test --dry-run >/dev/null && pnpm stackfoundry add public/r/api-keys.json --target /tmp/stackfoundry-test --dry-run >/dev/null && pnpm stackfoundry add public/r/provider-adapters.json --target /tmp/stackfoundry-test --dry-run >/dev/null",
+    "test:registry:install": "rm -rf /tmp/stackfoundry-install && mkdir -p /tmp/stackfoundry-install/next-saas /tmp/stackfoundry-install/provider-adapters /tmp/stackfoundry-install/cloudflare-native /tmp/stackfoundry-install/vercel-native /tmp/stackfoundry-install/saas-coverage /tmp/stackfoundry-install/registry-api-keys /tmp/stackfoundry-install/registry-adapters /tmp/stackfoundry-install/url-api-keys /tmp/stackfoundry-install/url-adapters && pnpm stackfoundry add preset next-saas --target /tmp/stackfoundry-install/next-saas >/dev/null && pnpm stackfoundry add preset provider-adapters --target /tmp/stackfoundry-install/provider-adapters >/dev/null && pnpm stackfoundry add preset cloudflare-native --target /tmp/stackfoundry-install/cloudflare-native >/dev/null && pnpm stackfoundry add preset vercel-native --target /tmp/stackfoundry-install/vercel-native >/dev/null && pnpm stackfoundry add preset saas-coverage --target /tmp/stackfoundry-install/saas-coverage >/dev/null && pnpm stackfoundry add public/r/api-keys.json --target /tmp/stackfoundry-install/registry-api-keys >/dev/null && pnpm stackfoundry add public/r/provider-adapters.json --target /tmp/stackfoundry-install/registry-adapters >/dev/null && pnpm stackfoundry add https://stackfoundry.dev/r/api-keys.json --target /tmp/stackfoundry-install/url-api-keys >/dev/null && pnpm stackfoundry add https://stackfoundry.dev/r/provider-adapters.json --target /tmp/stackfoundry-install/url-adapters >/dev/null",
+    "registry:list": "pnpm stackfoundry list",
+    "registry:categories": "pnpm stackfoundry categories",
+    "registry:presets": "pnpm stackfoundry presets",
+    "registry:doctor": "pnpm stackfoundry doctor",
     "validate": "pnpm registry:doctor",
-    "registry:build": "pnpm cli build",
+    "registry:build": "pnpm stackfoundry build",
     "registry:verify": "pnpm registry:doctor && pnpm registry:build",
-    "registry:add:next-saas": "pnpm cli add preset next-saas",
-    "registry:add:adapters": "pnpm cli add preset provider-adapters",
-    "registry:dry:next-saas": "pnpm cli add preset next-saas --dry-run",
-    "registry:dry:adapters": "pnpm cli add preset provider-adapters --dry-run",
-    "registry:diff:api-keys": "pnpm cli diff api-keys",
+    "registry:add:next-saas": "pnpm stackfoundry add preset next-saas",
+    "registry:add:adapters": "pnpm stackfoundry add preset provider-adapters",
+    "registry:dry:next-saas": "pnpm stackfoundry add preset next-saas --dry-run",
+    "registry:dry:adapters": "pnpm stackfoundry add preset provider-adapters --dry-run",
+    "registry:diff:api-keys": "pnpm stackfoundry diff api-keys",
     "dev:web": "pnpm --dir apps/web dev",
     "build:web": "pnpm --filter @stackfoundry/web build",
     "start:web": "pnpm --dir apps/web start",
     "clean": "rm -rf apps/web/.next apps/web/public/r public/r /tmp/stackfoundry-test /tmp/stackfoundry-install",
     "registry:compat": "node scripts/check-registry-compat.mjs",
-    "registry:add:block:api-keys": "pnpm cli add https://stackfoundry.dev/r/api-keys.json",
-    "registry:add:block:adapters": "pnpm cli add https://stackfoundry.dev/r/provider-adapters.json",
-    "registry:dry:block:api-keys": "pnpm cli add https://stackfoundry.dev/r/api-keys.json --dry-run",
-    "registry:dry:block:adapters": "pnpm cli add https://stackfoundry.dev/r/provider-adapters.json --dry-run",
+    "registry:add:block:api-keys": "pnpm stackfoundry add https://stackfoundry.dev/r/api-keys.json",
+    "registry:add:block:adapters": "pnpm stackfoundry add https://stackfoundry.dev/r/provider-adapters.json",
+    "registry:dry:block:api-keys": "pnpm stackfoundry add https://stackfoundry.dev/r/api-keys.json --dry-run",
+    "registry:dry:block:adapters": "pnpm stackfoundry add https://stackfoundry.dev/r/provider-adapters.json --dry-run",
     "lint:packages": "node --check packages/schema/src/index.mjs && node --check packages/utils/src/index.mjs && node --check packages/registry/src/index.mjs && node --check packages/generator/src/index.mjs",
-    "registry:add:coverage": "pnpm cli add preset saas-coverage",
-    "registry:dry:coverage": "pnpm cli add preset saas-coverage --dry-run"
+    "registry:add:coverage": "pnpm stackfoundry add preset saas-coverage",
+    "registry:dry:coverage": "pnpm stackfoundry add preset saas-coverage --dry-run",
+    "stackfoundry": "node apps/cli/src/cli.mjs",
+    "lint:command": "node --check apps/cli/src/cli.mjs"
   },
   "dependencies": {
     "next": "latest",
@@ -74,7 +74,7 @@
     "registry-blocks",
     "editable-source",
     "modules",
-    "cli",
+    "command",
     "stripe",
     "clerk",
     "vercel",

packages/README.md

@@ -1,6 +1,6 @@
 # Packages
 
-This directory contains reusable internals for the StackFoundry CLI and registry build pipeline.
+This directory contains reusable internals for the StackFoundry command and registry build pipeline.
 
 The split mirrors the shape of mature source registry CLIs: the executable stays thin, while schema rules, registry IO, generation helpers, and utilities live behind package boundaries.
 
@@ -17,4 +17,4 @@ The split mirrors the shape of mature source registry CLIs: the executable stays
 - Keep IO helpers in `registry`.
 - Keep write safety in `generator`.
 - Keep validation constants in `schema`.
-- Move CLI code into packages only when it reduces coupling or is needed by more than one caller.
+- Move command code into packages only when it reduces coupling or is needed by more than one caller.