@hypersoniclabs/helix-cli 0.1.25-helix3.521 → 0.1.25-helix3.522

package/docs/item-lod.md

@@ -245,10 +245,10 @@ map, so a runtime cannot light it for the scene it stands in; the `gbuffer/1` im
 ### `gbuffer/1`: a runtime-lit impostor (`item-lod/5`, `hemi-oct/1`)
 
 `compileItemLods(glb, { source, shading: 'gbuffer/1' })` bakes what a light needs instead of a light: the surface, not its
-shading. It is a contract of its own because it is neither read like `lit/1` nor laid out like it, and it is **not served yet**:
-`'gbuffer/1'` is deliberately absent from `ITEM_LOD_SHADINGS`, so the CLI's `--shading` flag does not accept it and no published
-Package version has one. The backend compiles `item-lod/5` next to `/4` and `/3` and serves it to a read that declares `gbuffer/1`
-(phase 2 of the impostor-gbuffer lane); an engine before it keeps its `lit/1` or albedo rendition.
+shading. It is a contract of its own because it is neither read like `lit/1` nor laid out like it. `'gbuffer/1'` is listed in
+`ITEM_LOD_SHADINGS` (phase 2), which is what lets a backend worker bake it under `item-lod/5`: the worker refuses a contract whose
+shading the installed CLI does not list. The backend compiles `item-lod/5` next to `/4` and `/3` and serves it only to a read that
+declares `gbuffer/1`; an engine before it keeps its `lit/1` or albedo rendition.
 
 * **Layout `hemi-oct/1`** (`impostor.layout`): 8 x 8 views over the UPPER hemisphere only. Frame `(i, j)` has `u = 2i/7 - 1`,
   `v = 2j/7 - 1`, `x = (u + v)/2`, `z = (u - v)/2`, `y = 1 - |x| - |z|`, normalised. The outer ring of 28 frames lies exactly on the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hypersoniclabs/helix-cli",
-  "version": "0.1.25-helix3.521",
+  "version": "0.1.25-helix3.522",
   "description": "helix — the HELIX creator CLI: scaffold, validate, and publish Instant Worlds",
   "main": "dist/lib.js",
   "types": "dist/lib.d.ts",