docs: switch @org placeholder from @nkzw to @acme across the feature

`@nkzw` is a real GitHub/npm org (Christoph Pojer's), and seeing it in
`vp create @nkzw` examples risks readers trying to run the command
expecting a working picker. Swap to `@acme` — the classic
placeholder-company handle already used elsewhere in the RFC — so
examples read as clearly hypothetical.

Touched: the RFC, docs/guide/create.md, docs/config/create.md,
packages/cli/src/create/{bin.ts, define-config.ts}, all four org
snap-tests, and the three org unit test specs. Four snap outputs
regenerated; 263 unit tests still pass.

The real dependency import in `packages/cli/src/create/random-name.ts`
(`@nkzw/safe-word-list`) and the team bio in `docs/_data/team.js` are
legitimate references and were left alone.

Author: fengmk2

docs/config/create.md

@@ -11,12 +11,12 @@ import { defineConfig } from 'vite-plus';
 
 export default defineConfig({
   create: {
-    defaultTemplate: '@nkzw',
+    defaultTemplate: '@acme',
   },
 });
 ```
 
-Any value accepted by `vp create` as a first argument works here — `@nkzw` for an org picker, `@nkzw/web` for a direct manifest entry, `vite:application` for a built-in, etc.
+Any value accepted by `vp create` as a first argument works here — `@acme` for an org picker, `@acme/web` for a direct manifest entry, `vite:application` for a built-in, etc.
 
 ## Precedence
 

docs/guide/create.md

@@ -94,11 +94,11 @@ An organization can publish a curated set of templates under a single npm scope
 ### Pick from an org
 
 ```bash
-# Open an interactive picker over @nkzw/create's manifest
-vp create @nkzw
+# Open an interactive picker over @acme/create's manifest
+vp create @acme
 
 # Run a specific manifest entry directly
-vp create @nkzw/web
+vp create @acme/web
 
 # Set the org as the default for a repo (see create.defaultTemplate config)
 vp create
@@ -113,7 +113,7 @@ There are two common layouts. Pick the one that matches the org's template count
 **Bundled (recommended for most orgs).** All templates live as subdirectories of `@org/create` itself. Manifest entries use relative `./path` values. One repo, one publish, one versioning story — the same pattern used by `create-vite` and `create-next-app`.
 
 ```
-@nkzw/create/
+@acme/create/
 ├── package.json              # "vp": { "templates": [{ "template": "./templates/web" }, ...] }
 ├── templates/
 │   ├── web/
@@ -126,8 +126,8 @@ There are two common layouts. Pick the one that matches the org's template count
 **Manifest-only.** When the org already publishes independent `@org/template-*` packages (or hosts them on GitHub), `@org/create` stays a thin index.
 
 ```
-@nkzw/create/
-├── package.json              # "vp": { "templates": [{ "template": "@nkzw/template-web" }, ...] }
+@acme/create/
+├── package.json              # "vp": { "templates": [{ "template": "@acme/template-web" }, ...] }
 └── README.md
 ```
 
@@ -141,20 +141,20 @@ The manifest lives at `vp.templates` in `@org/create`'s `package.json`:
 
 ```json
 {
-  "name": "@nkzw/create",
+  "name": "@acme/create",
   "version": "1.0.0",
   "vp": {
     "templates": [
       {
         "name": "monorepo",
-        "description": "Full Nakazawa Tech monorepo",
-        "template": "@nkzw/template-monorepo",
+        "description": "Full Acme Corp monorepo",
+        "template": "@acme/template-monorepo",
         "monorepo": true
       },
       {
         "name": "web",
         "description": "Web app template (Vite + React)",
-        "template": "@nkzw/template-web",
+        "template": "@acme/template-web",
         "keywords": ["web", "react", "app"]
       },
       {
@@ -177,7 +177,7 @@ Each entry supports:
 | `keywords`    | no       | Filter terms for picker search.                                                                                                                                                                                                              |
 | `monorepo`    | no       | If `true`, marks this entry as a monorepo-creating template. Hidden from the picker when `vp create` runs inside an existing monorepo, mirroring the built-in `vite:monorepo` filter.                                                        |
 
-An invalid manifest is a hard error, not a silent fall-through — a maintainer who shipped a manifest should hear about the offending field, e.g. `@nkzw/create: vp.templates[2].template must be a non-empty string`.
+An invalid manifest is a hard error, not a silent fall-through — a maintainer who shipped a manifest should hear about the offending field, e.g. `@acme/create: vp.templates[2].template must be a non-empty string`.
 
 ### Bundled subdirectory templates
 
@@ -191,11 +191,11 @@ Commit this in `vite.config.ts` at the project root:
 import { defineConfig } from 'vite-plus';
 
 export default defineConfig({
-  create: { defaultTemplate: '@nkzw' },
+  create: { defaultTemplate: '@acme' },
 });
 ```
 
-Now `vp create` (with no argument) drops straight into the `@nkzw` picker. See [`create.defaultTemplate`](/config/create) for details.
+Now `vp create` (with no argument) drops straight into the `@acme` picker. See [`create.defaultTemplate`](/config/create) for details.
 
 The picker always appends a trailing **Vite+ built-in templates** entry so `vite:monorepo` / `vite:application` / `vite:library` / `vite:generator` stay reachable from the picker — selecting it routes to the standard built-in flow. For scripts and CI, explicit specifiers (`vp create vite:library`) bypass the configured default.
 
@@ -204,16 +204,16 @@ The picker always appends a trailing **Vite+ built-in templates** entry so `vite
 `vp create @org --no-interactive` prints a stable, fixed-column table of the manifest (name, description, resolved template specifier) and exits 1. The output is machine-parseable, so scripts and AI agents can recover the list without a separate `--list` flag:
 
 ```
-error: vp create @nkzw requires a template selection in non-interactive mode.
+error: vp create @acme requires a template selection in non-interactive mode.
 
-available templates from @nkzw/create:
+available templates from @acme/create:
 
   NAME     DESCRIPTION                          TEMPLATE
-  web      Web app template (Vite + React)      @nkzw/template-web
-  library  TypeScript library template          @nkzw/template-library
+  web      Web app template (Vite + React)      @acme/template-web
+  library  TypeScript library template          @acme/template-library
   demo     Bundled demo template                ./templates/demo
 
-hint: rerun with an explicit selection, e.g. `vp create @nkzw/web`,
+hint: rerun with an explicit selection, e.g. `vp create @acme/web`,
       or use a Vite+ built-in template like `vp create vite:application`.
 ```
 

packages/cli/snap-tests/create-org-bundled/mock-manifest.json

@@ -1,12 +1,12 @@
 {
-  "@nkzw/create": {
-    "name": "@nkzw/create",
+  "@acme/create": {
+    "name": "@acme/create",
     "dist-tags": { "latest": "1.0.0" },
     "versions": {
       "1.0.0": {
         "version": "1.0.0",
         "dist": {
-          "tarball": "{REGISTRY}/@nkzw/create/-/create-1.0.0.tgz",
+          "tarball": "{REGISTRY}/@acme/create/-/create-1.0.0.tgz",
           "integrity": "sha512-h4Q9x+aUa2RUJGBe7JCZnWpGMyd8VHXPfL9+EBxrA2EWRV8rlmMCP45B3woZ8xA2fmkE/jUy1W7OM2GCjoPWQA=="
         },
         "vp": {

packages/cli/snap-tests/create-org-bundled/mock-server.mjs

@@ -1,6 +1,6 @@
 // Minimal mock npm registry used by `create-org-*` snap-tests.
 //
-// Reads `./mock-manifest.json` (keyed by URL path, e.g. `"@nkzw/create"`) and
+// Reads `./mock-manifest.json` (keyed by URL path, e.g. `"@acme/create"`) and
 // optionally serves `.tgz` tarballs from `./tarballs/<name>`. Picks an
 // ephemeral port, sets `NPM_CONFIG_REGISTRY` on the child environment, spawns
 // the wrapped command, and tears down when the child exits.

packages/cli/snap-tests/create-org-bundled/snap.txt

@@ -1,6 +1,6 @@
-> node mock-server.mjs -- vp create @nkzw/demo --no-interactive --directory my-demo-app # bundled template: extract tarball, copy subdir
+> node mock-server.mjs -- vp create @acme/demo --no-interactive --directory my-demo-app # bundled template: extract tarball, copy subdir
 
-selected 'demo' from @nkzw/create
+selected 'demo' from @acme/create
 ◇ Scaffolded my-demo-app
 • Node <semver>  pnpm <semver>
 → Next: cd my-demo-app && vp run

packages/cli/snap-tests/create-org-bundled/steps.json

@@ -1,6 +1,6 @@
 {
   "commands": [
-    "node mock-server.mjs -- vp create @nkzw/demo --no-interactive --directory my-demo-app # bundled template: extract tarball, copy subdir",
+    "node mock-server.mjs -- vp create @acme/demo --no-interactive --directory my-demo-app # bundled template: extract tarball, copy subdir",
     "cat my-demo-app/package.json # verify package.json name was rewritten",
     "cat my-demo-app/src/index.ts # verify bundled source copied",
     "ls my-demo-app/README.md # verify README copied"

packages/cli/snap-tests/create-org-invalid-manifest/mock-manifest.json

@@ -1,12 +1,12 @@
 {
-  "@nkzw/create": {
-    "name": "@nkzw/create",
+  "@acme/create": {
+    "name": "@acme/create",
     "dist-tags": { "latest": "1.0.0" },
     "versions": {
       "1.0.0": {
         "version": "1.0.0",
         "dist": {
-          "tarball": "{REGISTRY}/@nkzw/create/-/create-1.0.0.tgz",
+          "tarball": "{REGISTRY}/@acme/create/-/create-1.0.0.tgz",
           "integrity": "sha512-fake"
         },
         "vp": {

packages/cli/snap-tests/create-org-invalid-manifest/mock-server.mjs

@@ -1,6 +1,6 @@
 // Minimal mock npm registry used by `create-org-*` snap-tests.
 //
-// Reads `./mock-manifest.json` (keyed by URL path, e.g. `"@nkzw/create"`) and
+// Reads `./mock-manifest.json` (keyed by URL path, e.g. `"@acme/create"`) and
 // optionally serves `.tgz` tarballs from `./tarballs/<name>`. Picks an
 // ephemeral port, sets `NPM_CONFIG_REGISTRY` on the child environment, spawns
 // the wrapped command, and tears down when the child exits.

packages/cli/snap-tests/create-org-invalid-manifest/snap.txt

@@ -1,5 +1,5 @@
-[1]> node mock-server.mjs -- vp create @nkzw --no-interactive # invalid manifest -> schema error
+[1]> node mock-server.mjs -- vp create @acme --no-interactive # invalid manifest -> schema error
 
-@nkzw/create: vp.templates[0].template must be a non-empty string
+@acme/create: vp.templates[0].template must be a non-empty string
 Failed to resolve org template manifest
 

packages/cli/snap-tests/create-org-invalid-manifest/steps.json

@@ -1,5 +1,5 @@
 {
   "commands": [
-    "node mock-server.mjs -- vp create @nkzw --no-interactive # invalid manifest -> schema error"
+    "node mock-server.mjs -- vp create @acme --no-interactive # invalid manifest -> schema error"
   ]
 }