@vgai/cli 0.5.5 → 0.5.6

package/README.md

@@ -13,7 +13,7 @@ It talks to the editor dev server's HTTP/SSE control API via
 npx @vgai/cli@latest create my-game
 ```
 
-This creates a standalone registry-backed project, installs it, opens its
+This creates a standalone project with normal versioned dependencies, installs it, opens its
 visual editor, and prints the actual editor URL. Node.js 22 or newer is
 required.
 
@@ -24,9 +24,8 @@ npm install --global @vgai/cli
 vgai create my-game
 ```
 
-An installed CLI defaults to versioned registry dependencies. A CLI built
-inside the VGAI source checkout defaults to contributor-oriented `file:`
-links; `--registry` and `--link` override that choice explicitly.
+Every CLI produces the same portable project shape. A checkout never changes
+a project's dependency specs implicitly.
 
 To remix a shipped reference project instead of starting blank:
 
@@ -41,7 +40,7 @@ the packaged reference or this repository.
 
 ```
 vgai create <name> [location] [--template default|react] [--example <id>]
-            [--registry|--link] [--no-edit]
+            [--no-edit] [--no-git]
 vgai examples [--json]         list reference projects available to --example
 vgai edit [project-path]        launch the editor for a project (default: cwd)
 vgai worktrees [folder]        list repository branches, worktrees, dirtiness, and sessions
@@ -78,9 +77,9 @@ vgai validate [folder]          in-process: validate vgai.project.json, check ev
                                 entry/scene/entryHtml/bundleUrl file exists, print the engine
                                 pin (default: cwd) — no monorepo Vite/editor stack required
                                 Exit codes: 0 valid, 1 invalid manifest or missing file, 2 usage
-vgai deploy [folder]            build a first-party game folder and direct-upload
-                                to Cloudflare Pages (hard-refuses roots the
-                                hosted tier can't serve)
+npm run vgai -- add deploy-vercel      add project-owned Vercel scripts/config
+npm run vgai -- add deploy-cloudflare  add project-owned Wrangler scripts/config
+npm run deploy                         run the selected provider's native CLI
 
 --url <url> (or VGAI_EDITOR_URL) targets an exact editor URL
 --port <n> / VGAI_EDITOR_PORT overrides the machine-local worktree allocation
@@ -137,15 +136,24 @@ another clone.
 Contributors can build and link the current checkout:
 
 ```bash
-npm run build -w @vgai/cli
-(cd packages/vgai-cli && npm link)
-vgai create my-game --link
+# engine checkout
+npm run dev:packages
+
+# existing game project; package.json and package-lock.json stay versioned
+VGAI_ENGINE_ROOT=/absolute/path/to/vgai-engine
+npm link --no-save "$VGAI_ENGINE_ROOT/packages/engine" \
+  "$VGAI_ENGINE_ROOT/packages/vgai-cli" \
+  "$VGAI_ENGINE_ROOT/packages/editor" \
+  "$VGAI_ENGINE_ROOT/packages/vgai-live" \
+  "$VGAI_ENGINE_ROOT/packages/vgai-sdk" \
+  "$VGAI_ENGINE_ROOT/packages/editor-sdk" \
+  "$VGAI_ENGINE_ROOT/packages/p2p-colyseus"
 ```
 
 The bundle inlines the shared private scaffolder, so the public CLI and the
 editor's New Project route use the same `scaffoldProject` implementation.
-Registry projects remain portable without the checkout; link projects are
-deliberately tied to it.
+`vgai status` identifies the package as linked and prints its source path.
+`npm install` restores the registry graph.
 
 Learn and manual: https://vgai-learn.pages.dev