@genex-ai/cli-demo 1.0.0-dev.305 → 1.2.0-dev.314

package/dist/index.js

@@ -4258,7 +4258,7 @@ async function deployGame(ctx, opts, log) {
     log.error("Couldn't upload your game \u2014 please try again.");
     return false;
   }
-  if (!await pushSource(cwd, ctx, log)) return false;
+  if (!await pushSource(cwd, ctx, log, opts.channel === "staging" ? "preview" : "main")) return false;
   log.step("Publishing\u2026");
   const published = await callPublish(ctx, commit, opts, log);
   if (!published) return false;
@@ -4499,21 +4499,22 @@ async function callPublish(ctx, commit, opts, log) {
   }
   return { url: body?.url ?? "" };
 }
-async function pushSource(cwd, ctx, log) {
+async function pushSource(cwd, ctx, log, branch = "main") {
   const target = await fetchPushUrl(ctx, log);
   if (!target) return false;
-  if (await pushWorktree(cwd, target.pushUrl, target.managed, log)) return true;
+  const ref = target.managed ? branch : "main";
+  if (await pushWorktree(cwd, target.pushUrl, target.managed, log, ref)) return true;
   if (!target.managed) return false;
   log.info("Retrying the source push\u2026");
   await new Promise((r) => setTimeout(r, 2e3));
   const fresh = await fetchPushUrl(ctx, log);
   if (!fresh) return false;
-  return pushWorktree(cwd, fresh.pushUrl, fresh.managed, log);
+  return pushWorktree(cwd, fresh.pushUrl, fresh.managed, log, ref);
 }
 function urlHasEmbeddedCredentials(pushUrl) {
   return /^[a-z][a-z0-9+.-]*:\/\/[^/@]+@/i.test(pushUrl);
 }
-async function pushWorktree(cwd, pushUrl, managed, log) {
+async function pushWorktree(cwd, pushUrl, managed, log, branch = "main") {
   const EMPTY_TREE = "4b825dc642cb6eb9a060e54bf8d69288fbee4904";
   const failed = () => {
     log.error("Couldn't save your game's source \u2014 please try again.");
@@ -4576,7 +4577,7 @@ async function pushWorktree(cwd, pushUrl, managed, log) {
     }
     const push = await run(
       "git",
-      ["-c", "http.postBuffer=536870912", "push", "-q", pushUrl, "+refs/heads/main:main"],
+      ["-c", "http.postBuffer=536870912", "push", "-q", pushUrl, `+refs/heads/main:${branch}`],
       base
     );
     if (push.code === 0) return true;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@genex-ai/cli-demo",
-  "version": "1.0.0-dev.305",
+  "version": "1.2.0-dev.314",
   "description": "Set up your project's agent workspace (.claude/.codex/.cursor in the game folder), authorize, create a game project, generate AI assets, and publish (genex CLI).",
   "type": "module",
   "bin": {

package/templates/skills/genex-game-director/SKILL.md

@@ -35,8 +35,8 @@ hosting, or deploy skills. **They are not Genex lanes.** All generated art,
 audio, video, characters, and UI come from `genex` commands unless the player
 explicitly asks for another tool by name. A local reference image is not a
 reason to switch tools: `genex image --edit` and `--inpaint` accept local
-paths. Building, previewing, and publishing use `genex preview` /
-`genex publish`; do not load a competing hosting workflow.
+paths. Building, previewing, promoting and publishing use `genex preview` /
+`genex promote` / `genex publish`; do not load a competing hosting workflow.
 
 ## 2. Route the latest request
 

package/templates/skills/genex-getting-started/SKILL.md

@@ -107,8 +107,11 @@ already serves a **standard placeholder world** — the owner's avatar in a smal
 playground, unrelated to your code. It is NOT in your repo; never treat it as a
 starting point or try to modify it. Your first `preview` replaces it automatically.
 
-`npx genex preview` deploys to your unlisted draft URL; `npx genex publish`
-lists the game in the public gallery. When publishing, pick 1–3 gallery
+`npx genex preview` deploys to your preview URL and **never touches the build
+players are on**; `npx genex promote` makes that exact build live for them (no
+rebuild). `npx genex publish` does build + make-live + lists the game in the
+public gallery, for the first release. So: preview, show the player, and promote
+once they are happy — don't promote every milestone by reflex. When publishing, pick 1–3 gallery
 categories from what you actually built — `games`, `assets`, `physics`,
 `terrain`, `lighting`, `vfx` — and pass them comma-separated:
 

package/templates/skills/genex-threejs-visual-validation/SKILL.md

@@ -53,8 +53,8 @@ translation may be normalized for Rapier.
 For plain game tasks — nothing from the procedural/visual-system pack loaded —
 this is the whole acceptance gate, and it is also the *ceiling*: a smoke check,
 not a certification. Run it ONCE per milestone, against that milestone's
-`genex preview` build — the player may already be walking around it while
-you check. Catch obvious
+`genex preview` build. That build is on the preview URL, not the one players
+are on, so checking it disturbs nobody. Catch obvious
 breakage, fix what's clearly broken, and hand the feel/polish judgment to the
 player — don't loop re-testing the same build, don't re-test after cosmetic
 tweaks (sounds, colors, tuning values), and don't try to exercise every button