@wix/himalaya-cli 0.873.0 → 0.875.0

package/guides/tier-5-add-a-screen.md

@@ -428,6 +428,35 @@ HTTPS endpoints; development may explicitly use a loopback HTTP fixture. See
 **`payload`**, pinned with `position:sticky` the same way ScreenHost / device hosts do.
 A sticky bar missing from `render` is a real bug in the descriptor or the renderer.
 
+#### When that `load()` rejects: the runtime-owned `_error` slot
+
+Module-eval `load()` is fire-and-forget, so **nobody awaits it** and a rejection has no
+caller to observe it. Since #2288 the runtime does the observing, identically on every
+surface (web, iOS, Android, and the local `himi test` / `himi render --live` loop):
+
+1. **It commits an error state**, so a descriptor's error branch can render instead of
+   the screen hanging on its declared `loading`. The rejection message lands in a
+   reserved `_error` key, and — *only when the service already declared them* — the
+   conventional discriminators are flipped to match: `status: "loading"` → `"error"`,
+   `loading: true` → `false`, and a `string` `error` slot receives the message. A
+   service that models failure some other way keeps its own shape and still gets
+   `_error`. Nothing is invented.
+2. **It emits `action_failed`** (`{ actionId: "tier5.<service>.<action>", source:
+   "worker", error }` — the same payload the dispatcher emits for a failed dispatch)
+   plus the `error_logged` central-log line, so the message reaches telemetry and
+   `himi logs` instead of vanishing.
+3. **It re-throws.** The failure is made *visible*, not caught and continued: an
+   awaiting bundle and the host's `unhandledrejection` net keep every signal they had.
+
+`_error` is **runtime-owned and transient**, exactly like `_nav` / `_stream` / `_poll`:
+your bundle never writes it, the next successful action's state spread clears it (so the
+idiomatic `{ ...s, status: "loading" }` retry cannot pin a stale failure on), and it is
+dropped when a persisted snapshot re-hydrates on a cold boot.
+
+This is what makes the fail-closed capability gates readable. `local_database: entity
+"X" is not declared in the app's dataSchema` is a message written to be read — before
+#2288 an author only ever saw an eternal spinner.
+
 ### Refresh on a cadence with `_poll` (the worker has no clock)
 
 A worker is a pure reducer with **no `setTimeout` and no `setInterval`** — its sandbox

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.873.0",
+  "version": "0.875.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": [
@@ -63,5 +63,5 @@
       "artifactId": "himalaya-cli"
     }
   },
-  "falconPackageHash": "e317363609876f9814b32d6a6ca7319bdd4527bfba2889d9027735e6"
+  "falconPackageHash": "ec18219dffbe81ace2bcd7eee3d3b546638087f0b2ea05f6e5b55258"
 }