@wix/himalaya-cli 0.1453.0 → 0.1454.0

package/guides/himi-json-output.md

@@ -219,6 +219,22 @@ redirects, invalid data, source changes and disk errors remain failures.
   and the original failure is preserved if writing the failure manifest also fails
   (exit 1).
 
+## `himi one-app validate-topbar` codes
+
+Failures print `ok: false` and a top-level `code` on stderr. The validator reads
+authored header choices from `settings.topBarSettings`, falls back to the legacy
+`settings.showCartIconInTopBar` / `showChatIconInTopBar` values, and treats a
+choice that is absent from both locations as false.
+
+- `invalid_usage`: required options are missing, duplicated, or malformed (exit 2).
+- `evidence_invalid`: the evidence manifest or `raw-structure.json` is missing,
+  invalid, for another workflow, lacks a valid recorded raw-structure hash, or the
+  file does not match that hash (exit 1).
+- `config_uninspectable`: the target `config.ts` cannot be read or the relevant
+  `navigation.topBarDefault.actions` cannot be inspected (exit 1).
+- `topbar_coverage_failed`: an authored cart/chat control has no matching action
+  with a non-empty `onTap.actionId` (exit 1).
+
 ## `himi base44 entities` codes
 
 Covers `himi base44 adopt` and `himi base44 entities query` (#4557,

package/guides/one-app-to-himi-app.md

@@ -121,6 +121,13 @@ Apply these interpretation rules:
   end-user access policy. Never expose protected content beneath a visual gate.
 - Exclude `ntt.*` definitions and placements from coverage. Preserve configured
   header/top-bar intent; do not add unconfigured drawer or header surfaces.
+- Before publishing, run the migration-only authored-control check:
+  `himi one-app validate-topbar --evidence-dir .himi/one-app --content .`.
+  It reads each screen's `raw-structure.json` header settings and checks that
+  `navigation.topBarDefault.actions` has a matching tappable action for every
+  authored cart/chat control. It does not use the iOS/Android enriched views to
+  infer visibility, access, or membership rules. This check is specific to this
+  migration workflow; it does not change the behavior of `himi validate`.
 - For each configured Detailed header, import and call the shared
   `detailedHeader` builder from `@wix/himalaya/screens`. Do not recreate its
   component tree in the app. Resolve the source fallback and visibility rules

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.1453.0",
+  "version": "0.1454.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": "297fee15efe43307e066ee404fb90579178287997e8e01f43d6c03a3"
+  "falconPackageHash": "eefcf19354e83f21581f78ca930495b7ae70059df5480ba579c463cb"
 }