@genex-ai/cli-demo 0.7.0 → 0.10.0

package/README.md

@@ -39,14 +39,14 @@ genex texture "<prompt>"   # generate a texture   → assets/textures/
    dashboard's **My games** immediately.
 
 `genex preview` and `genex publish` share a build-aware deploy core: each runs
-`npm run build` (when the project has a build script), then pushes the built
-`dist/` **as the repo root** over the deploy key — no copying files or swapping
-`index.html` by hand. A `.nojekyll` marker is written so GitHub Pages serves the
-bundle verbatim, and the deploy never stages `genex_key` (the private key can't
-leak). Pass `--no-build` to deploy whatever is already built.
-
-- **`genex preview`** pushes the current build to the project's hosted draft URL
-  (`https://<user>.github.io/<slug>/`) without listing it publicly — re-run it
+`npm run build` (when the project has a build script), then uploads the built
+`dist/` to R2 through a short-lived scoped upload token and flips a live pointer;
+the editable source is pushed to the repo's single `main` branch (for Remix). Game
+bytes never pass through our API. Pass `--no-build` to deploy whatever is already
+built.
+
+- **`genex preview`** uploads the current build to the project's hosted draft URL
+  (`https://<slug>.genex.technology/`) without listing it publicly — re-run it
   after each change to update the shareable draft.
 - **`genex publish`** does the same deploy, then flips the project to
   **published** so it appears in the public gallery. The deploy and the gallery
@@ -69,10 +69,11 @@ command blocks until the asset is ready (poll loop), then writes the file(s):
 | `genex sfx "<prompt>" [--duration <s>]` | ElevenLabs | `assets/sfx/<slug>.mp3` |
 | `genex texture "<prompt>" [--terrain]` | Gemini | `assets/textures/<slug>/basecolor.<ext>` |
 
-Because the file lands in the project and `genex publish` commits the whole working
-directory, generated assets **ship inside the published GitHub Pages build** — load
-them by **relative** path (`./assets/...`) and players get them from the same origin
-(no CORS, no runtime dependency on this API). Each kind has a scaffolded
+Because the file lands in the project and `genex publish` uploads the whole built
+directory, generated assets **ship inside the published R2 bundle** — games serve
+at the domain root (`https://<slug>.genex.technology/`), so both absolute
+(`/assets/...`) and relative (`./assets/...`) paths resolve, and players get them
+from the same origin (no CORS, no runtime dependency on this API). Each kind has a scaffolded
 `genex-ai-<kind>` skill with the exact Three.js loader code.
 
 Auth reuses the existing `GENEX_TOKEN` (run `genex init` first). Server-side, each