@helix3/helix-cli 0.1.13-helix3.133 → 0.1.13-helix3.134

package/README.md

@@ -129,7 +129,10 @@ worktrees resolve through.
 `helix install` records platform-owned systems in `public/helix.runtime.json`.
 Compatible ranges such as `^0.2` are externalized and resolved to an active,
 immutable catalog module when a world launches, so a compatible platform fix can
-reach an already-published world without creator edits or republishing. Exact
+reach an already-published world without creator edits or republishing. A new
+runtime version reaches no world until the platform deliberately publishes it to
+the catalog and it goes active there — building or merging one changes nothing on
+its own, and there is no rolling "latest". Exact
 versions such as `0.2.43` map directly to the immutable catalog URL and remain
 pinned. A custom Vite config is never rewritten: install reports
 `legacy-bundled` until the creator explicitly externalizes `@helix/*`.
@@ -156,11 +159,46 @@ previous compatible resolver response during a transient outage; the descriptor'
 Without a cached resolver response, a cold resolver failure fails closed.
 
 Native features remain individually overridable without pinning the whole
-character runtime. `CharacterMultiplayer.create` accepts `emotes: false` to
-disable carried emotes, `emoteWheel: false` to keep emotes but draw a custom
-picker, and `localControl: false` when the World owns its own camera/input.
-Camera behavior can also be configured through the character camera config.
-Every other compatible native fix continues to update normally.
+character runtime. The character system's **native avatar features** — carried
+emotes and the radial wheel (including its Customize door), x-ray, pointing,
+sitting, the avatar camera, the two camera legs, and rendering each player's
+universal avatar — are constructed by the character chassis itself, so every
+character World has them whether it was built on `Character` or on
+`CharacterMultiplayer`, and a World published today receives ones added later on
+its next fresh launch.
+
+A World refuses what it does not want by NAME, in the character config it passes
+at create time — not in `helix.json`, and nothing here is a publish-time concern:
+
+```ts
+config: { character: { native: { disabled: ['xray', 'pointing'] } } }
+```
+
+Ids: `emotes`, `emote-wheel`, `xray`, `pointing`, `sitting`, `avatar-camera`,
+`camera-first-person`, `camera-third-person`, `universal-avatar`. It is a
+**blocklist, never an allow-list**, for the same reason this whole delivery
+contract exists: an allow-list would freeze every already-published World out of
+every feature added afterwards. A refusal also removes the feature's key,
+controller button, touch pad and prompt; `universal-avatar` is the top switch and
+takes emotes, the wheel, x-ray, pointing, sitting and the avatar camera with it
+(the camera legs survive — a World still needs a camera); refusing BOTH camera
+legs throws at create; and an unrecognised id is kept with a warning rather than
+rejected, because it may belong to a newer runtime. The older switches still
+work and route into the same resolver: `CharacterMultiplayer.create`'s
+`emotes: false`, `emoteWheel: false` and `universalAvatars: false`, and the
+config keys `character.emote.enabled`, `character.emote.wheel`,
+`character.xray.enabled`, `character.universalAvatar.enabled`. (`localControl:
+false` is not one of these — it declares a spectator body the World drives its
+own camera and input for.) Every other compatible native fix continues to update
+normally.
+
+This surface needs `@helix/humanoid-character` **0.2.54** or newer; an older
+runtime ignores `character.native.disabled` silently, so confirm against the
+resolved system's config schema rather than assuming. The full creator reference
+is the character world recipe in the HELIX MCP docs
+(`read_doc({ name: "character-world" })`, section 8g); the authoritative id list
+and defaults are that config schema, readable from the installed system
+manifest.
 
 The runtime descriptor is mandatory for bundles that declare systems. It makes
 the delivery boundary inspectable by the CLI, MCP, backend, and fleet census;

package/package.json

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