@genex-ai/cli-demo 1.32.1-dev.671 → 1.32.2-dev.673

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@genex-ai/cli-demo",
-  "version": "1.32.1-dev.671",
+  "version": "1.32.2-dev.673",
   "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-threejs-adaptive-quality/SKILL.md

@@ -68,6 +68,16 @@ const renderer = new THREE.WebGLRenderer({
   ...depthRendererOptions(), // reversed-Z: distant surfaces stop z-fighting, early-Z kept
 });
 renderer.setPixelRatio(Math.min(window.devicePixelRatio, tier.dprCap));
+// Shadows: PCF, never PCFSoft. three r186 REMOVED PCFSoftShadowMap; it warns
+// once and downgrades on the first shadow pass — and with the static-scene
+// rule (shadowMap.autoUpdate = false) that pass comes after your materials
+// compiled, so the driver rejects every shadow-receiving draw call and the
+// world is an empty fog behind a working HUD (measured 2026-09-11 on a
+// published village). Mechanism + console check: $genex-threejs-shadow-systems.
+renderer.shadowMap.enabled = tier.shadowMapSize > 0;
+renderer.shadowMap.type = THREE.PCFShadowMap;
+renderer.shadowMap.autoUpdate = false;  // static scene: re-render shadows on demand (needsUpdate = true when casters move)
+renderer.shadowMap.needsUpdate = true;  // primed: the maps exist before any receiver draws (2 rejected boot frames otherwise)
 // Camera range comes from the WORLD, never from a docs example (0.1/1000):
 const { near, far } = cameraNearFar({ closest: 1.5, farthest: 800 });
 const camera = new THREE.PerspectiveCamera(60, innerWidth / innerHeight, near, far);
@@ -249,7 +259,10 @@ not the player's account. Default Auto.
 ## Budgets that ride the tier (not separate rules)
 
 - Shadows: `tier.shadowMapSize`, `shadow.autoUpdate = false` for static scenes,
-  at most 2 cascades on phones (`$genex-threejs-shadow-systems`).
+  at most 2 cascades on phones, and `shadowMap.type = THREE.PCFShadowMap` —
+  PCFSoft was removed in three r186 and, together with `autoUpdate = false`,
+  blanks every shadow receiver (`$genex-threejs-shadow-systems` has the
+  mechanism and the console check).
 - Post: phone floor is a BUILT tone-mapping/output pass (`postLevel: 'light'`
   adds FXAA/vignette); SSAO, volumetrics, and DoF are desktop-tier only
   (`$genex-game-director`'s routing map owns the floor wording).

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

@@ -33,7 +33,7 @@ cost of guessing high is a dead page.
 `desktop-low` is the weak-desktop demotion (Intel iGPU MacBooks, old integrated
 AMD): desktop GPU renderer strings are UNMASKED (unlike iOS), so one boot probe
 separates a 2015 Intel Air from an M3 Max. The full desktop path on those
-machines — DPR 2 + 4× MSAA + 2048 PCFSoft shadows + full bloom — is the classic
+machines — DPR 2 + 4× MSAA + 2048 PCF shadows + full bloom — is the classic
 "huge lags on a MacBook" recipe, and two of its costs (context MSAA, shadow
 budget) were previously invisible to the governor.
 

package/templates/skills/genex-threejs-shadow-systems/SKILL.md

@@ -18,6 +18,37 @@ shadow maps ≤1024² on phones (512² on the low tier — a 4096² map alone is
 4, and `shadowMap.autoUpdate = false` for static scenes (re-render on demand:
 a shadow pass is a full extra scene render every frame otherwise).
 
+## Shadow map type — PCF, and verify it
+
+`renderer.shadowMap.type = THREE.PCFShadowMap`, in every scene, bounded or not.
+`PCFSoftShadowMap` was REMOVED in three r186: the renderer logs
+`WebGLShadowMap: PCFSoftShadowMap has been removed` once and downgrades on the
+first shadow pass. Under `shadowMap.autoUpdate = true` that is one warning and a
+crisper shadow. Under the static-scene rule above (`autoUpdate = false`,
+`needsUpdate` on demand) the first pass lands AFTER your materials compiled:
+they keep a `sampler2D` program, the depth textures that pass allocates are
+comparison textures, three's recompile-on-type-change never fires (its
+"previous type" was captured before you assigned the removed value), and the
+driver rejects every shadow-receiving draw call — `GL_INVALID_OPERATION:
+glDrawElements: Mismatch between texture format and sampler type
+(signed/unsigned/float/shadow)`, one line per mesh per frame. The world is an
+empty fog; the DOM HUD still draws. Measured 2026-09-11 on a published village:
+one "removed" line, 200+ rejections, no ground, no buildings, while the same
+warning in a second game that had left `autoUpdate` on cost nothing.
+
+Prime the frozen map too: `shadowMap.needsUpdate = true` before the first
+frame, so the maps exist before any receiver draws — measured on a three
+0.186.0 repro, `PCFShadowMap` + `autoUpdate = false` alone still lost its
+first two frames to the same rejection (0 with the prime; 10 of 12 with
+PCFSoft).
+
+Verify it inside the smoke check (`$genex-threejs-visual-validation`): after
+the first few frames the console must contain neither `PCFSoftShadowMap` nor
+`GL_INVALID_OPERATION: glDraw`. Both arrive as WARNINGS, so "no console
+errors" does not cover them — read the warnings. A software-rasteriser tier
+that runs with shadows off cannot show this bug; a green check there says
+nothing about the desktop tier players get.
+
 ## Cached clipmap workflow
 
 1. Define concentric light-space square levels.

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

@@ -70,7 +70,9 @@ The player deciding "does it feel right?" is faster and truer than you clicking
 everything twice.
 
 1. Load the page in a real browser; the canvas renders (no black screen, no
-   console errors). For an unpublished draft, open the dev server in local
+   console errors — and no console WARNING naming a removed three.js API or
+   `GL_INVALID_OPERATION`: those arrive at warn level and each one is a mesh
+   the driver refused to draw, `$genex-threejs-shadow-systems` has the case). For an unpublished draft, open the dev server in local
    test mode — `http://localhost:5173/?genex_local_test=1` (the embed-auth
    skill's "Self-testing a draft" section) — so you see the game, not the
    sign-in gate. Then hit-test the screen that is up (title now, pause later):