@wix/himalaya-cli 0.1026.0 → 0.1028.0

package/guides/app-config.md

@@ -34,6 +34,12 @@ A content package configures itself in three layers:
 
 - `tabBar.items[]` — bottom-tab / rail items (`id`, `screenId?`, `label?`, `icon?`,
   `selectedIcon?` (the filled/active-tab variant of `icon`), `badge?`).
+- `tabBar.presentation?` — who draws the bottom bar. `"native"` (the default; absent or
+  unknown means the same) is the platform's own bar: SwiftUI `TabView` on iOS (Liquid Glass
+  on iOS 26), Material 3 `NavigationBar` on Android, and on the web preview, the imitation of
+  whichever platform is previewed. It takes only the kit's tab-bar colours. `"kit"` is the
+  kit-styled `KitTabBar` (floating capsule, gradient, indicator, motion). It is served OTA, so a
+  release can switch an app between them without a new binary.
 - `drawer` / `sidebar` — slide-in panel / nav-rail config.
 - `linkableScreens[]` — the deep-link targets. `himalaya://screen/<id>` resolves **only** if
   the screen is listed here (each entry needs a `screenId`).

package/guides/headless-loop.md

@@ -99,7 +99,9 @@ reloading. The board answers each real change and nothing else: a new screen dev
 one dips, the phone pulses with "Rebuilt in 2.3 s · home" (red when a save did not build), a step
 fills, and a published draft or the handover is celebrated once. The tab title carries the step
 ("(5/8) salon"), and the owner can switch on Sound and desktop notices from the board itself — both
-start off, so never promise them either. `himi test` writes one PNG per
+start off, so never promise them either. The board can also rewind the whole build — drag its timeline or
+press Replay for a thirty-second making-of, checks included — pop the live phone out into an
+always-on-top window, and show the owner their website next to their app the moment the brand lands. `himi test` writes one PNG per
 screen to `.himi/shots/` on every run, so take the new screens from there instead of rendering each
 one again; a bare `--png` on `himi render` writes `.himi/shots/<id>.png`. `himi progress` copies each image into `.himi/history/`
 as it was when you journaled it, so a later render cannot change what the record says the owner saw;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.1026.0",
+  "version": "0.1028.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": [
@@ -65,5 +65,5 @@
       "artifactId": "himalaya-cli"
     }
   },
-  "falconPackageHash": "7697d5497f3decfef92c0b07e21a8dd59a19989b5556baf7509f4a26"
+  "falconPackageHash": "59c5cc0524f87f37cc078c95033304d90d56388bf25c7622625cbe9c"
 }