@genex-ai/cli-demo 1.6.0-dev.403 → 1.6.0-dev.406

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@genex-ai/cli-demo",
-  "version": "1.6.0-dev.403",
+  "version": "1.6.0-dev.406",
   "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-monetization/SKILL.md

@@ -191,6 +191,12 @@ played before.
 ```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
@@ -206,8 +212,18 @@ the player loses one item — a support ticket. If you apply first and die befor
 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.
 
-`consumable` items are used up. `durable` items are owned permanently — consume
-them once, then record ownership in the player's save.
+**`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.
 
 ## Checklist