@genex-ai/cli-demo 1.7.0-dev.446 → 1.7.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@genex-ai/cli-demo",
-  "version": "1.7.0-dev.446",
+  "version": "1.7.0",
   "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-ai-texture/SKILL.md

@@ -225,7 +225,7 @@ first one is the one a screenshot of the whole arena will not show you.
 
 ## Troubleshooting
 
-- **"Not authorized"** — run `npx @genex-ai/cli-demo@dev init` first (it writes your `GENEX_TOKEN`).
+- **"Not authorized"** — run `npx @genex-ai/cli-demo@latest init` first (it writes your `GENEX_TOKEN`).
 - **"Out of credits" (`insufficient_credits`)** — the account has no credits left for
   this texture generation. Tell the user the facts the CLI printed: their balance,
   this generation's cost, and when their credits refill. Then offer to continue the

package/templates/skills/genex-ai-video/SKILL.md

@@ -151,7 +151,7 @@ set belongs to `$genex-ai-hud` — both build on `npx genex image`/`video`.
 
 ## Troubleshooting
 
-- **"Not authorized"** — run `npx @genex-ai/cli-demo@dev init` first (it writes your `GENEX_TOKEN`).
+- **"Not authorized"** — run `npx @genex-ai/cli-demo@latest init` first (it writes your `GENEX_TOKEN`).
 - **"Prompt rejected"** — the provider's content-safety filter blocked the prompt.
   This is non-retryable; retrying the same wording fails again. Rewrite the prompt.
 - **Nothing plays / black surface** — the first `video.play()` must run inside a user

package/templates/skills/genex-game-director/references/routing-map.md

@@ -59,7 +59,6 @@ copy demo architecture.
 | in-world motion art or another requested video | `$genex-ai-video` |
 | sound effect, one looping music bed, or a short spoken line | `$genex-ai-sfx`, `$genex-ai-music`, or `$genex-ai-voice` |
 | requested UI/HUD/menu/interface work, a visible UI problem, or an interface you decided this game wants built with generated art | `$genex-threejs-game-ui` |
-| selling anything for platform coin: a shop, an item catalog, boosts, cosmetics, "make it earn"; also any request for a loot box, gacha, wager, casino mechanic or donation prompt, which that skill refuses and replaces | `$genex-monetization` |
 | cinematic menu/title/pause/victory/defeat/lobby/credits video treatment | `$genex-ai-menu` |
 | drawn HUD chrome the game's style wants—one element or a matched set of frames, masks, and icons | `$genex-ai-hud` |
 | the game works but feels flat, floaty, or unresponsive: input response, camera, impacts, cooldowns, difficulty, fail/retry | `$genex-threejs-game-feel` |

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

@@ -150,55 +150,23 @@ If unsure, use `games` (also the server's fallback for anything unrecognized).
 Your own files were left untouched. `genex init` only adds missing files and
 refreshes the genex-owned ones.
 
-## Working on one game from more than one machine
+## Reconnecting an existing game (`genex link`)
 
-A game's connection to its live page is folder-local (`.genex/project.json`), so
-a new machine — or a folder that got deleted — has no link. **Never run `init`
-to "recover" a game**: that creates a brand-new game at a new URL.
-
-**Picking the game up somewhere new** — run `link` in an EMPTY folder and it
-downloads the game too, binary assets and all:
+Each game's connection to its live page is folder-local (`.genex/project.json`).
+If that folder is gone — deleted, or the game
+was built on another machine — **don't run `init` to "recover" it**: that
+creates a brand-new game at a new URL. Instead, clone the game's source repo
+and re-link the clone to the same live game:
 
 ```bash
-mkdir my-game && cd my-game
-npx @genex-ai/cli-demo@dev link <slug>   # slug = the name in the play URL
+git clone <the game's repo url> my-game && cd my-game
 npm install
+npx @genex-ai/cli-demo@latest link <slug>   # slug = the name in the play URL
 ```
 
 Don't know the slug? **`npx genex list`** prints every game on your account —
-slug, status, and page link for each. In a folder that already has files, `link`
-writes the link and downloads nothing, so it can never overwrite work.
-
-**Catching a folder up** — `npx genex pull` replaces this folder with the
-game's current draft. It refuses if the folder holds changes you never deployed,
-because there is nothing to merge them against.
-
-**If two machines have both moved on**, `preview` refuses rather than
-overwriting the other one, and tells you both ways forward:
-
-```
-✗ my-game was updated from another device — nothing was deployed.
-  npx genex pull — take the other device's work (refuses if you have unshipped changes)
-  npx genex preview --force — keep yours and replace theirs
-```
-
-**Prefer taking their work and redoing yours on top.** You know what you just
-changed, so you can re-apply it — which no merge tool could do for you, and which
-loses nothing:
-
-```bash
-npx genex pull --force   # takes their version; keeps what was here under .genex/replaced-*
-# redo your change on the new base, then:
-npx genex preview
-```
-
-`pull --force` never deletes: what was in the folder is copied to
-`.genex/replaced-<timestamp>/` first, so you can diff against it while re-applying.
-
-Use `preview --force` instead only when the user says their side should win.
-Either way **say which version you are keeping before you run it** — both commands
-are irreversible for one side, and the user may know something you don't about what
-is on the other machine.
+slug, status, and page link for each — signing you in first if needed. Find the
+game there, then `link` its slug.
 
 `link` never creates a project: it signs in if needed (the browser opens once)
 and rewrites the local link (source pushes authorize over HTTPS, so there's no
@@ -220,7 +188,7 @@ Safe to run any time — genex-owned skills are refreshed to the latest version,
 and your own files are never touched:
 
 ```bash
-npx @genex-ai/cli-demo@dev init
+npx @genex-ai/cli-demo@latest init
 ```
 
 Use `--force` only if you intentionally want your own existing files overwritten

package/templates/skills/genex-threejs-multiplayer/SKILL.md

@@ -36,15 +36,18 @@ calling multiplayer done, run the mandatory
 ## Install
 
 ```bash
-npm i @genex-ai/multiplayer@^0.12.0
+npm i @genex-ai/multiplayer@^0.16.0
 ```
 
-> Pin `@^0.12.0` (not a bare `npm i`): cross-region invites can select the inviter's exact
-> relay with the optional `url` override; unowned object writes warn instead of failing silently;
-> live connected-player presence, supplier-form `connect()`
-> auth, regional relay selection (`getColyseusUrls()` + `urls`)
-> landed in 0.10; confirmed object controls, snaps, host-tick teardown, and reconnect rebasing
-> in 0.9. An older resolve does not have those.
+> Pin `@^0.16.0` (not a bare `npm i`, and not an older range): automatic TURN — the thing that
+> lets players behind symmetric NAT or carrier CGNAT be heard at all — landed in 0.16, mesh voice
+> in 0.15, room text chat in 0.14, host-only `setRoomOpen()` in 0.13; cross-region invites can
+> select the inviter's exact relay with the optional `url` override since 0.11; unowned object
+> writes warn instead of failing silently, live connected-player presence, supplier-form
+> `connect()` auth and regional relay selection (`getColyseusUrls()` + `urls`) landed in 0.10;
+> confirmed object controls, snaps, host-tick teardown, and reconnect rebasing in 0.9. An older
+> resolve does not have those — and because this package is still `0.x`, a caret range is
+> minor-locked, so `^0.12.0` would resolve to 0.12.x and give you no voice at all.
 
 This skill targets `@genex-ai/multiplayer` **≥ 0.16.0** (`objects`/`host` since 0.4; verified per-player `avatarUrl` since 0.12;
 room text chat via `room.chat` since 0.14; mesh voice via `room.voice` since 0.15;
@@ -1021,7 +1024,7 @@ host-driven saving works as long as ANY account is in the room.
 
 ## Checklist
 
-- [ ] `npm i @genex-ai/multiplayer@^0.12.0` (connected presence, supplier auth, confirmed controls, snap epochs, reconnect-safe host ticks, unowned-write warnings, cross-region exact-relay overrides); config wired into the build.
+- [ ] `npm i @genex-ai/multiplayer@^0.16.0` (automatic TURN, mesh voice, room text chat, connected presence, supplier auth, confirmed controls, snap epochs, reconnect-safe host ticks, unowned-write warnings, cross-region exact-relay overrides); config wired into the build.
 - [ ] The plan names one net model, the player-experience reason, start/quorum, late-join/backfill,
       and below-quorum/end behavior. The agent inferred it unless the experience was genuinely ambiguous.
 - [ ] `reconnecting`/`reconnected`/`disconnect` render an overlay (don't tear the scene down).

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

@@ -134,13 +134,9 @@ everything twice.
    visible; the lock may only ever engage from the Play/Resume click or a
    gameplay canvas click (the phase binding `setPaused(phase !== "playing")` is
    what guarantees this — check it rides `setPhase`, not the render loop).
-   Headless caveat, measured on Chromium 151: `requestPointerLock` does NOT
-   throw — it locks, with or without a user gesture, so the lock and the
-   unlocked cue ARE yours to assert headless. What does not survive is the
-   both-axes look check: synthesised mouse movement cancels to a net zero
-   delta, so turning right then left proves nothing about direction. Assert the
-   wiring and the cue in a screenshot, and say plainly that confirming which way
-   the view turns needs one manual pass with a real mouse.
+   Headless caveat: `requestPointerLock` throws in headless Chromium —
+   assert the wiring and the unlocked cue in a screenshot, and say plainly that
+   the lock itself needs one manual click (do the both-axes look check there).
 7. **Ask the scene the three things the screenshot cannot answer** (below). Run it
    once, in the same browser you already have open.
 

package/templates/skills/genex-updates/SKILL.md

@@ -38,7 +38,7 @@ update, so update immediately.)
 Run exactly the command the nudge printed, from the game project root:
 
 ```bash
-npm i -D @genex-ai/cli-demo@dev   # the genex CLI (a dev dependency)
+npm i -D @genex-ai/cli-demo@latest   # the genex CLI (a dev dependency)
 npm i @genex-ai/embed-sdk@latest     # identity/saves SDK (ships inside the game)
 npm i @genex-ai/multiplayer@latest   # multiplayer SDK (only if the game uses it)
 ```

package/templates/skills/genex-monetization/SKILL.md

@@ -1,292 +0,0 @@
----
-name: genex-monetization
-description: Build an in-game shop that sells for platform coin — item catalog, purchase flow, delivery, and the per-game soft-currency economy a purchase attaches to. Use when the player asks to sell things, add a shop, monetize, or make the game earn. Carries the hard rules: no paid randomness, no gambling in coin, no donation mechanics, and a real-money price beside every coin price.
----
-
-# Genex Monetization
-
-Games on Genex can sell things for **coin**, the platform currency. The player
-buys coin with real money once; spending it inside a game is a ledger movement
-the game never touches. You design what is for sale; the platform owns the
-wallet, the confirmation, and the money.
-
-Load this when the game should sell something. Ask first if it should — a game
-with no loop worth monetizing is better without a shop (see §1).
-
-## The hard rules, and the test that generalizes them
-
-Before you build ANY purchasable thing, run this test:
-
-> **Does the player pay?** (with coin, or with anything bought with coin —
-> directly or indirectly, including a per-game token or key that coin bought.)
-> **Is the outcome uncertain when they pay?**
-> **Is there a prize** — an item, currency, or advantage they wanted?
->
-> **All three yes = paid randomness. Build the deterministic version instead.**
-
-That triad is the test used by every app store to identify gambling, and it
-catches mechanics that do not exist yet — which a list of banned names cannot.
-
-Four things are never built, whatever the request:
-
-1. **No paid randomness.** No loot boxes, gacha, mystery boxes, crates, packs,
-   prize wheels, raffles, "spin for a bonus", "chance to double your coins".
-   Directly or indirectly.
-2. **No gambling in coin.** No wagering, staking, betting, coinflips, casino or
-   slot mechanics denominated in coin or in anything coin buys.
-3. **No donation or begging mechanics.** No "donate to me" prompts, tip jars, or
-   player-to-player coin transfers. Coin buys goods; it never just moves.
-4. **No pressure.** No countdown timers, "ends in", "limited time", "only N
-   left", or stock counters anywhere in the shop.
-
-**Randomness the player EARNS by playing is gameplay, not commerce, and is
-completely fine**: an enemy dropping a random item, a chest you found in the
-level, a procedural layout, a critical-hit roll, a shuffled deck. The line is
-what triggered the roll — play, or payment. Build those freely.
-
-Genex refuses paid randomness outright rather than allowing it with disclosed
-odds. That is stricter than any app store, and it is why no Genex game needs an
-odds table, an age gate, or a per-country check.
-
-### When a request crosses a line
-
-Answer in exactly three parts, then build:
-
-1. **Name it.** "A loot crate is paid randomness — the player pays before
-   knowing what they get."
-2. **Why.** One sentence. "Genex doesn't sell chance; it's a purchase the player
-   can't price, and it's what regulators fine studios over."
-3. **Offer the alternative,** concretely enough to start on, and build that.
-
-Never build the banned version "as an option", never build a partial one, and
-never ask the user to confirm they want it. If they insist, restate the rule
-once and build the compliant version. There is no escalation path.
-
-**What to build instead:**
-
-| They asked for | Build |
-| --- | --- |
-| Loot box, crate, mystery box, card pack | A direct-purchase shop: every item listed at a fixed price, contents visible. For the collecting feel, add a **visible catalog with a completion track** — any purchase advances a meter to a stated milestone reward. |
-| Gacha, banner, pull, summon | A **deterministic unlock**: the character costs a fixed price, or unlocks at a stated number of runs. Coin may buy a stated, visible number of those points. |
-| Prize wheel, spin-to-win, slot machine | A **free spin earned by finishing a run** (never bought), or a **"pick one of three"** screen where all three are visible and the player chooses. Keeps the moment, drops the wager. |
-| Casino game, blackjack, poker, roulette | The same game with **chips that are granted free each session, reset on restart, cannot be bought and cannot become coin**. It becomes a card game. Sell cosmetics — table felt, card backs — for coin. |
-| Coinflip, double-or-nothing, wager my coins | A **skill-based risk/reward inside the run**: a harder route with a bigger payout, staking the run's own score, which was never purchasable. |
-| Betting on matches, PvP wagers | **Leaderboards with a fixed cosmetic reward for placement**, paid by the game. Nobody's balance goes down. |
-| Donate button, tip jar, "pls donate" | A **gift that is a purchase**: they buy a specific item at a stated price and give it. Or a **supporter cosmetic** — a badge or aura at a normal price, where what's delivered is visible. |
-| Pay to remove a wait / energy gate | **Delete the gate** and sell a permanent upgrade or a cosmetic. Pace with difficulty, not with a timer. |
-| Limited-time offer, flash sale | A **permanent tiered ladder** — the value comes from volume, not from a clock. |
-| Pay-to-win stat boost in a competitive game | **Cosmetics**, or a boost that only applies in single-player content. |
-
-## Designing a shop worth buying from
-
-Nine checks. Each one is answerable about your actual design.
-
-1. **The shop attaches to a progression that already exists.** Name the screen
-   it opens from and the meter a purchase moves. Build the loop first; a shop in
-   a game with nothing to want is furniture.
-2. **A boost shortens a grind the player has already felt.** State it in one
-   sentence: "this skips the ore-gathering they've done four times." If you
-   can't, it isn't a boost, it's a number.
-3. **Nothing sold invalidates the core loop.** If a paying and a non-paying
-   player both reach the end, the payer must not have skipped the part that IS
-   the game.
-4. **No manufactured friction.** If the annoyance wouldn't exist without the
-   shop, remove the annoyance instead of selling the cure.
-5. **Everything sold is reachable free.** Spending is a shortcut or a
-   decoration, never the only path.
-6. **Prices land on the grid.** Item prices use 50 / 100 / 200 / 500 / 1000 coin
-   so every coin pack divides evenly into them and nobody is left holding change
-   they cannot spend.
-7. **Every price shows real money next to it.** The server sends
-   `priceDisplayUsdCents` with every item — render it. `250 coins ($2.49)`.
-8. **One currency layer between money and goods.** Coin buys items. A per-game
-   earned currency buys per-game upgrades. They never convert into each other.
-9. **Purchases never expire and survive a reinstall.** Entitlements live on the
-   server; the game re-reads them on every boot.
-
-For a per-game earned currency, the load-bearing number is **minutes of play per
-unit earned**. Set it, then price the cheapest meaningful item at one to three
-sessions of earning. Everything else follows. Spend sinks come in three kinds —
-permanent upgrades, refills, cosmetics — and cosmetics are what absorbs late-game
-currency without touching balance.
-
-## Stocking the shop
-
-Items live on the platform, not in the game's code. You create them with the CLI,
-and the game names them by id — which is what stops a game inventing its own
-items or repricing them.
-
-```bash
-npx genex shop add "Iron Key" --price 100 --type durable
-#   → id: sku_a1b2c3   ← what the game passes to buy()
-
-npx genex shop list                    # what this game sells, and the valid prices
-npx genex shop set sku_a1b2c3 --price 200
-npx genex shop remove sku_a1b2c3       # retires it; players who bought it keep it
-```
-
-`--type consumable` (default) is spent on use; `durable` is owned permanently.
-
-**Prices come off a fixed grid** — `genex shop list` prints it, and an off-grid
-price is refused. The grid exists so every coin pack divides evenly by the
-cheapest item, which is what stops a player being left holding change too small
-to spend. Pick the nearest grid price rather than working around it.
-
-Record the ids in `DESIGN.md` next to what each item does. They are the one
-thing the game's code cannot regenerate for itself.
-
-## The API
-
-From `@genex-ai/embed-sdk`, already installed. `initEmbed()` must have run.
-
-```ts
-import { getShop, buy, getEntitlements, consumeEntitlement } from '@genex-ai/embed-sdk';
-
-const items = await getShop();
-// [{ id, type, name, iconUrl, priceCoins, priceDisplayUsdCents }]
-```
-
-Render `name`, `iconUrl`, `priceCoins` **and** `priceDisplayUsdCents`. Never
-hardcode a price: the server charges what its own catalog says, so a hardcoded
-number can silently disagree with what the player is charged.
-
-`getShop()` works for a **guest** and inside a **preview** build, so the shop
-window renders for everyone — that is the point of showing it to a signed-out
-player at all. Buying is what needs an account.
-
-**Your game cannot read the player's coin balance, and no HUD should show one.**
-The wallet spans every game on the platform, so an untrusted game is not told how
-much a player can spend. Show what you *can* know — what they own, from
-`getEntitlements()` — and let `buy()` report `insufficient_balance` if it comes
-to that.
-
-### Buying
-
-```ts
-buyButton.addEventListener('click', async () => {   // must be a real click
-  const result = await buy({ skuId: item.id });
-  if (result.status === 'canceled') return;         // normal — say nothing
-  if (result.status !== 'succeeded') {
-    showMessage(result.message ?? 'That did not go through.');
-    return;
-  }
-  await deliverPending();
-});
-```
-
-**Call `buy()` synchronously from the click handler.** On the game's own origin
-the confirmation is a popup, and browsers only allow one while a user gesture is
-live — an `await` before it loses the gesture and nothing opens.
-
-`buy()` resolves when the SERVER says what happened, not when a window closes.
-Statuses: `succeeded`, `canceled`, `expired`, `insufficient_balance`, `failed`.
-
-The player confirms on a Genex-drawn surface — your game does not render the
-price sheet, cannot skin it, and cannot complete a purchase itself. That is
-deliberate: it is what lets a player trust a purchase in a game they have never
-played before.
-
-### Delivering
-
-```ts
-async function deliverPending() {
-  for (const e of await getEntitlements({ excludeConsumed: true })) {
-    // Branch on skuType (consumable | durable), NEVER on type — `type` is how
-    // it was acquired (purchase/gift/test/free) and can't answer this.
-    if (e.skuType === 'durable') {
-      wear(e.name);            // ownership, re-applied on every boot. Do not consume.
-      continue;
-    }
-    const { alreadyConsumed } = await consumeEntitlement(e.id);
-    if (alreadyConsumed) continue;                  // someone got there first
-    applyItem(e.skuId);                             // AFTER the consume
-    await savePlayerState(currentSave());
-  }
-}
-```
-
-**Consume first, apply second, and run `deliverPending()` on every boot.**
-
-That order is not stylistic. If the game dies between consuming and applying,
-the player loses one item — a support ticket. If you apply first and die before
-consuming, every boot re-delivers it forever — an exploit. Re-listing on boot is
-what makes a purchase survive a crash, a refresh, or a closed tab.
-
-**`e.skuType` is the field that decides this, not `e.type`.** `type` says how the
-player got it (`purchase`/`gift`/`test`/`free`); `skuType` says what it is
-(`consumable`/`durable`).
-
-A **consumable** is spent: consume it, then apply the effect once.
-
-A **durable** is owned forever, and you have two honest ways to handle it. If the
-effect is ownership — a cosmetic, a skin, an unlock — do **not** consume it: the
-row's presence in the list IS the ownership, it survives reinstalls, and there is
-no local save to drift out of sync. Only consume a durable when it grants
-something once and non-idempotently (a permanent +100 gold), and then record it
-in the player's save, because re-applying that on every boot would be a bug.
-
-### Testing the shop you just built
-
-```bash
-npx genex shop test <sku-id>     # a free copy, for the owner only
-```
-
-That grants the entitlement without a sale — no coin moves — so the delivery
-path, the inventory and the effect all run exactly as they would after a real
-purchase. Reload the game and it should be there.
-
-You *can* also just buy your own item, but it costs you the full price and pays
-you nothing: your share of a sale you funded goes to the platform, never into
-your own earnings. Use the test grant instead.
-
-## Checklist
-
-- [ ] Items exist (`npx genex shop list`) before the shop UI is written
-- [ ] Delivery was verified with `npx genex shop test`, not by trying to buy your own item
-- [ ] The game has a loop and a progression before it has a shop
-- [ ] Every item price is on the 50/100/200/500/1000 grid
-- [ ] Every price renders `priceDisplayUsdCents` beside the coin figure
-- [ ] `buy()` is called synchronously inside a click/tap handler
-- [ ] `canceled` is silent; only real failures show a message
-- [ ] `deliverPending()` runs on every boot, before the player can act
-- [ ] `consumeEntitlement()` is awaited BEFORE the effect is applied
-- [ ] `alreadyConsumed: true` skips the effect
-- [ ] Durable purchases are written to the player's save
-- [ ] No timer, "limited", "ends in", or stock counter anywhere
-- [ ] Nothing sold is unreachable without paying
-- [ ] No paid randomness, no coin wagering, no donation prompt
-
-## Troubleshooting
-
-**`buy()` returns `failed` with "the confirmation window was blocked"** — `buy()`
-was not called inside a user gesture, or an `await` ran before it. Move it to the
-first line of the click handler.
-
-**The purchase succeeded but the player got nothing** — the game applied the
-effect without consuming, or never ran `deliverPending()` on boot. The
-entitlement is still there; re-list it.
-
-**The player got the item twice** — the effect was applied before consuming, or
-`alreadyConsumed` was ignored. Both are the same bug.
-
-**`unauthorized` from `getShop()`** — no player identity yet. `initEmbed()` must
-have run and `waitForPlayer()` resolved. See `$genex-threejs-embed-auth`.
-
-**`guest_no_wallet`** — guests play but hold no wallet. Show the shop as
-sign-in-to-buy rather than hiding it.
-
-**`staging_no_purchase`** — a `genex preview` build cannot spend real coin. Test
-the shop's layout on staging; test a purchase after `genex promote`.
-
-**`getShop()` returns nothing** — the game has no items yet. `npx genex shop add
-"<name>" --price <coin>` and use the id it prints.
-
-**`price_off_grid`** — that price isn't on the platform's grid. `npx genex shop
-list` prints the valid ones; pick the nearest.
-
-**Everything coin-related 404s** — in-game purchases aren't enabled on this
-environment. Nothing to fix in the game; say so and build the rest.
-
-**Purchases do nothing in local testing** — local test mode has no wallet and no
-server. `buy()` returns `failed` immediately by design. Test purchases on a
-preview or published build.