@genex-ai/cli-demo 0.77.0-dev.197 → 0.77.1-dev.199

package/dist/index.js

@@ -1640,7 +1640,7 @@ function scanGlb(bytes) {
 }
 
 // ../../packages/mobile-scan/src/scan.ts
-var GENEX_GENERATION_URL_RE = /https:\/\/assets\.genex\.technology\/generations\/([A-Za-z0-9._-]+)\/([A-Za-z0-9._@-]+)/g;
+var GENEX_GENERATION_URL_RE = /https:\/\/[A-Za-z0-9.-]+\/generations\/([A-Za-z0-9._-]+)\/([A-Za-z0-9._@-]+)/g;
 var SKYBOX_ROLE = "skybox-equirect";
 var MOBILE_RUNG_SUFFIX_RE = /@(\d+)$/;
 var MOBILE_BUDGET_MB = { broad: 300, modern: 700 };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@genex-ai/cli-demo",
-  "version": "0.77.0-dev.197",
+  "version": "0.77.1-dev.199",
   "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/controllers/quality/pick-asset.ts

@@ -10,7 +10,12 @@
 // a rung failure, so the worst case is today's behavior — never a broken boot.
 import type { QualityTier } from './tier.ts';
 
-const GENEX_GENERATIONS_RE = /^https:\/\/assets\.genex\.technology\/generations\/[^/]+\/[^/@]+$/;
+// Host-agnostic on purpose: each stand serves generated assets from its own
+// domain (prod assets.genex.technology, dev assets.auras.cc), and baking one
+// host in would silently disable the whole ladder everywhere else — the
+// fallback contract makes a false positive harmless (404 rung -> warn ->
+// original), so the path shape is the only thing worth matching.
+const GENEX_GENERATIONS_RE = /^https:\/\/[^/]+\/generations\/[^/]+\/[^/@]+$/;
 
 /** Rung widths by role family — mirrors the server's ladder (store.ts MOBILE_RUNGS). */
 function rungWidthFor(url: string, tier: QualityTier): number | null {

package/templates/skills/genex-threejs-adaptive-quality/SKILL.md

@@ -68,10 +68,20 @@ const governor = new QualityGovernor(tier, {
     sun.shadow.map?.dispose(); sun.shadow.map = null; // realloc at the new size
   },
   setDrawDistanceScale: (m) => (scene.fog!.far = baseFogFar * tier.drawDistanceScale * m),
+  setFrameCap: (fps) => (frameCap = fps), // 0/undefined-safe: tier.frameCap restores it
 }, renderer);
 
-// In the render loop, with the same performance.now() delta the loop already computes:
-governor.frame(deltaMs);
+// In the render loop, with the same performance.now() delta the loop already
+// computes. Wire ALL the callbacks — every omitted one is a governor rung
+// that silently no-ops. The frame cap paces inside setAnimationLoop:
+let frameCap = tier.frameCap, lastFrame = 0;
+renderer.setAnimationLoop((t) => {
+  if (frameCap < 60 && t - lastFrame < 1000 / frameCap - 1) return; // skip: stable 30 > stuttery 45
+  const deltaMs = lastFrame ? t - lastFrame : 16;
+  lastFrame = t;
+  governor.frame(deltaMs);
+  // ...update + render
+});
 ```
 
 Sustained slow frames step down (DPR ×0.8 → post off → shadows reduced →

package/templates/skills/genex-threejs-adaptive-quality/references/adaptive-quality.md

@@ -56,10 +56,19 @@ Getting this wrong produces silent no-ops or a session stuck ugly:
 - **Load-time (fixed for the session once fetched):** asset rungs (skybox and
   texture resolutions), model LOD sets. `pickAsset` decides them from the tier
   at load; switching later means a re-fetch — treat as fixed.
+- **Scene-build-fixed: the light COUNT.** Three.js bakes the number of lights
+  of each type into every lit material's shader program; add, remove, or hide
+  a light (or a group containing one) mid-play and ALL lit materials recompile
+  synchronously on that frame — a multi-second freeze that boot-time
+  `compileAsync` cannot pre-warm because each new count is a new shader. A
+  pilot game froze ~3 s on every pickup exactly this way (each collected
+  relic's group hid a child PointLight). Drive `intensity` to 0 instead;
+  change the population only on full level swaps.
 - **Runtime-free (the governor's domain):** `setPixelRatio`, post passes on/off
   and their target resolutions, shadow map size (realloc), draw distance and
   fog, LOD bias, particle counts, mixer update rates, frame cap, remote-avatar
-  animation count.
+  animation count. Light `intensity` is runtime-free; light COUNT is not (see
+  above).
 
 ## Governor mechanics
 

package/templates/skills/genex-threejs-lighting-design/SKILL.md

@@ -101,6 +101,14 @@ kill-switch diagnostic.
 ## Rules
 
 - Every light names its cause; a light nothing explains is a bug, not mood.
+- **The light population is fixed at scene build — never add, remove, or hide
+  a light (or a group containing one) during play.** Three.js counts lights
+  into every lit material's shader; a changed count recompiles ALL of them
+  synchronously — a multi-second freeze on the exact frame a pickup, door, or
+  death "removes" a light (a real pilot game froze ~3 s per relic collected
+  this way). Turn a light off by driving `intensity` to 0 and leave it in the
+  graph; per-level swaps rebuild the whole scene anyway, which is the one
+  legitimate time the population changes.
 - Couple a practical to its emitter: one color, one envelope, one on/off state.
 - The key owns shadows; practicals cast none until a shot proves they must.
 - Tune intensities only after the renderer baseline is locked — retuning the