@wix/himalaya-cli 0.1361.0 → 0.1362.0

package/dist/cli.mjs

@@ -7650,7 +7650,6 @@ function buttonVariant(style) {
 var SYSTEM_FONT_FAMILY, TONAL_ELEVATION_ALPHA, BUTTON_MIN_HIT_TARGET, nonNegative, nonEmpty, own, COLOR_TOKEN_PROPS, TYPOGRAPHY_TOKEN_PROPS, BUTTON_VARIANTS;
 var init_tokens = __esm({
   "../../core/ts/src/tokens.ts"() {
-    "use strict";
     SYSTEM_FONT_FAMILY = "$system";
     TONAL_ELEVATION_ALPHA = [0, 0.05, 0.08, 0.11, 0.12, 0.14];
     BUTTON_MIN_HIT_TARGET = 44;
@@ -7706,7 +7705,6 @@ function resolveTranslation(value, catalog3, sourceCatalog) {
 var BINDING_SIGILS, BINDING_SIGIL_RE, TRANSLATION_PREFIX, TRANSLATION_KEY_RE;
 var init_bindings = __esm({
   "../../core/ts/src/bindings.ts"() {
-    "use strict";
     BINDING_SIGILS = ["service", "flag", "item", "t"];
     BINDING_SIGIL_RE = new RegExp(
       `^\\$(?:${BINDING_SIGILS.filter((s2) => s2 !== "t").join("|")})\\b|^\\$t:`

package/guides/capabilities.md

@@ -22,10 +22,35 @@ himi capabilities --shell branded-lite # what that one binary serves
 
 ```
 camera  —  import from @himalaya/camera
-  exports:  capturePhoto, pickDocument, scanQR
-  declare:  config.ts `capabilities` AND each calling screen's `logicBundle.declaredCapabilities`
-  binary:   needs a NATIVE build — iOS NSCameraUsageDescription; Android android.permission.CAMERA …
-  shells:   served by owner-lite, player; `himi dist` adds it to base44, branded-lite, brandy; NOT in the demo-app binary
+  about:    Tier-5 typed binding to the platform's camera capability.
+  exports:  capturePhoto, pickDocument, scanQR, version
+  verbs:    capability.camera.capture, capability.camera.pickDocument, capability.camera.scanQR
+  declare:  config.ts `capabilities` (the app-level list a binary is built with) AND each calling screen's `logicBundle.declaredCapabilities` (the runtime gate)
+  binary:   needs a NATIVE build — iOS NSCameraUsageDescription, NSPhotoLibraryUsageDescription; Android android.permission.CAMERA, android.hardware.camera. An OTA push cannot add it.
+  module:   none — its native code is in the core runtime
+  dist:     a `himi dist` build can add it to an extensible shell
+  shells:   served by owner-lite, player; `himi dist` adds it to base44, branded-lite, brandy; NOT in the demo-app binary (a fixed binary — only a new demo-app build adds it; a content package cannot)
+  remedy:   a NEW binary (`himi dist`) — declare it in config.ts `capabilities`, or list it in `capabilityEnvelope` to build it in now and turn it on later over the air. An OTA push alone cannot add it.
+```
+
+The per-id output also answers three build questions (the JSON and MCP forms carry the same fields as
+`modules`, `components`, `distAddable` and `distAddRefusal`):
+
+- `module:` — the native module the capability links into a binary (its SwiftPM product and Gradle
+  project), and the SDUI components that need that module too (`animation` — also needed by the Lottie, Rive components).
+- `dist:` — whether a `himi dist` build can add the capability to an extensible shell, and if not,
+  why.
+- `remedy:` — what to do about it. It takes the shell you passed with `--shell` into account.
+
+A capability a build cannot add shows the refusal reason, for example (`himi capabilities live_activity`,
+abridged):
+
+```
+live_activity  —  import from @himalaya/live-activity
+  module:   live_activity (iOS HimalayaCoreLiveActivity, Android :core-runtime-live-update)
+  dist:     cannot be added at dist — live_activity needs a WidgetKit extension target in the shell's project, which a build cannot add
+  shells:   served by branded-lite, demo-app, owner-lite; NOT in the base44, brandy binary (a dist build cannot add it …); NOT in the player binary (one shared binary …)
+  remedy:   pick a shell whose binary already serves it (branded-lite, demo-app, owner-lite) — a dist build cannot add it (live_activity needs a WidgetKit extension target in the shell's project, which a build cannot add).
 ```
 
 Agents: the same data is the `himi_capabilities` MCP tool. `himi sdk <name>` also prints the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.1361.0",
+  "version": "0.1362.0",
   "type": "module",
   "description": "himi — the Himalaya authoring CLI. Build a Tier-5 content package on your own machine, push it to the production serve as a draft, preview it on web + Himi Player, and read worker logs back — the remote dev loop. Wraps @himalaya/serve-cli for transport.",
   "keywords": [
@@ -71,5 +71,5 @@
       "artifactId": "himalaya-cli"
     }
   },
-  "falconPackageHash": "b5d19122c31f70fd18ec1b8a2e6d66e67ad3c2ffb5a4545a8bc432a1"
+  "falconPackageHash": "6f8e9ebff2033817c8121233af0096191f0d147fc9d49e65d9e6f02d"
 }