@wix/himalaya-cli 0.1563.0 → 0.1565.0

package/dist/authoring-runtime/node_modules/@wix/himalaya/dist/_types/stdlib/flows/screens/src/index.d.ts

@@ -35,12 +35,12 @@ export interface DetailedHeaderOptions {
     collapsedHeight?: number;
 }
 /**
- * Build the shared Detailed header used by One App migrations.
+ * Build an optional Detailed cover header for screens that explicitly request one.
  *
  * The header uses Himalaya's cross-platform `CollapsingHeader` and standard
- * components for the detail card, logo, member strip, and actions. A migration
- * calls this builder instead of copying header layout into each app. Himalaya's
- * hero accepts one image, so pass the first source cover image here.
+ * components for the detail card, logo, member strip, and actions. The One App
+ * migration workflow uses native navigation bars and does not call this builder.
+ * Himalaya's hero accepts one image.
  */
 export declare function detailedHeader(opts: DetailedHeaderOptions): Node;
 export interface ScreenEnvelope {

package/guides/hhp.md

@@ -120,7 +120,9 @@ for the app's existing identity, tokens or capability declarations.
 The portable compiler stores its generated catalog as a deterministic gzip/base64
 envelope with a SHA-256 check. `himi hhp profile --json` returns the complete decoded
 metadata; the installed component guides and support decision source remain readable.
-`gen-v2.ts --check` verifies the envelope against the canonical schemas and SDK exports.
+`gen-v2.ts` builds the envelope from the canonical schemas and SDK exports, and refuses while any
+new field or export lacks a decision in `v2-support-decisions.json`. The catalog itself is refreshed
+on master (`authoring-refresh.yml`), so a PR commits the decisions file but not the catalog.
 
 ## CSS
 

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

@@ -147,7 +147,7 @@ Apply these interpretation rules:
   only when the resolved source top-bar settings show a title and Structure supplies
   its value; leave it empty when the source does not show a title or has no title.
   Do not create a title from the app name, business name, route ID, tab label or
-  section content. Keep a custom page header separate from the shell top bar.
+  section content. Apply the native-navigation policy below to source custom headers.
 - Keep navigation visibility, reachability and data access separate. Reevaluate
   membership/plan/badge gates at runtime; an operator's successful read is not an
   end-user access policy. Never expose protected content beneath a visual gate.
@@ -205,30 +205,34 @@ Apply these interpretation rules:
   explicitly rather than treating a pass as full design parity. A deliberate difference
   is waived only by a `design` coverage row with status `adapted` that cites the user's
   instruction and explains the change. This check compares values, not rendered screens.
-- 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
-  first, then pass the title, subtitle, first cover image, logo, permitted member
-  data, location label and configured actions. Set `collapsible: false` when the
-  source header is not collapsible. The shared hero supports one cover image; list
-  additional source carousel images as an adaptation gap.
-
-```ts
-import { detailedHeader } from "@wix/himalaya/screens";
-
-const header = detailedHeader({
-  id: "home.header",
-  title: "Studio name",
-  subtitle: "Source subtitle",
-  imageUrl: "https://example.test/cover.jpg",
-  primaryAction: {
-    label: "Join",
-    action: { actionId: "himi.open", params: { screenId: "membership" } },
-  },
-});
-```
-
-Add this returned component to the screen tree at the source header position.
+- **Native navigation is the migration target.** Use the shell's native top bar
+  and, for bottom-tab navigation, `navigation.tabBar.presentation: "native"`.
+  Do not recreate the source Detailed header, call `detailedHeader`, or insert a
+  `CollapsingHeader` hero/card above the page. This target adaptation supersedes
+  the older instruction to reproduce the source cover header; the source
+  research still explains how to interpret its settings.
+- Emit resolved native actions in `navigation.topBarDefault` or a complete
+  per-screen `topBar` override. The shell owns back/menu controls. Per-screen
+  actions support `hiddenPath` when `navigation.topBarDefault.actions` declares
+  the same action ID and binding, evaluated by `navigation.navLogicBundle`.
+  Keep that registration for screen overrides: screen-only paths are not
+  subscribed, and an unresolved path leaves the action visible. Do not invent
+  visibility fields. These bindings control presentation only and must not
+  authorize data or actions. Preserve runtime access checks, and report any source visibility
+  rule that the target cannot represent as a gap. Preserve the title rule above:
+  a source cover title does not by itself authorize a native top-bar title.
+- Account for source header content in `.himi/one-app/migration-report.md`.
+  Record the custom cover, carousel and overlapping card as an intentional
+  native-navigation adaptation there; do not invent header-presentation rows in
+  the derived coverage ledger. Preserve meaningful subtitle, location and configured CTA content
+  as ordinary page content or supported native actions, with the same runtime
+  access rules. Report unsupported avatar/logo/action behavior as a gap; do not
+  invent member data, drop a configured CTA silently, or add an in-page toolbar
+  to imitate a missing native control.
+- Verify the migrated app's native top bar, bottom tabs, back navigation and
+  configured actions on the affected devices, including RTL. A web screenshot
+  alone does not prove native navigation or control availability. Record any
+  unavailable device check as unverified.
 - Business context contains only `phoneNumber`, `website`, and `services`, with
   their permitted nested values. Structure wins on authored phone/URL/design.
   Installed services do not add features. Installation IDs are not record IDs.
@@ -257,8 +261,11 @@ reference's top-tabs row in R04 and its top-tabs acceptance case:
   in-screen top tabs.
 - `target.hiddenPages` become screens without a tab entry. Keep their routes for
   actions and links.
-- The first tab takes the source screen's header. The other tabs take a compact
-  default top bar, as the editor gives each new screen a default header.
+- The plan attaches the source screen's header settings to the first tab as
+  interpretation evidence; it does not require a custom header in the target.
+  Apply the native-navigation policy above to that tab too. Resolve every tab's
+  effective native top bar, with compact defaults for the other tabs as in the
+  editor conversion.
 - `target.initialTabId` is the first tab; the editor drops the source
   `initialTabId`. `initial_tab_changed` names the page that used to open first.
 - `target.showLabels` is the source label setting. Pilates hides labels when it

package/guides/one-app-viewer.md

@@ -127,11 +127,11 @@ Translate the resolved result to Himi. Its inspected schema says a per-screen `t
 - Resolve the effective source bar for every target screen, including screens created by a navigation conversion. Do not assume that a shared source header means every screen has the same effective bar.
 - When screens have the same effective actions and style, use one shared `TopBarConfig` value or builder for them. Use it as `top_bar_default` when it is the app-wide bar. Use a complete per-screen `top_bar` only when a screen differs.
 - Himi reads the bar title from `ScreenDescriptor.title`. Set this field only when the resolved source top-bar settings show a title and Structure supplies that title. For a dynamic source title, use the title resolved by the viewer rules. If the source does not show a title or has no title value, leave the target title empty. Do not invent a title from the app name, business name, route ID, tab label, or section content.
-- A source custom header is page content. It is not the shell's top bar. Keep the two surfaces separate. Reuse a page-header component only when multiple screens share that configured header content.
+- A source custom header is page content in the original viewer. It is not the shell's top bar. Apply the current migration's native-navigation adaptation in R09 rather than duplicating the source header above the native bar.
 
 ### R09. Treat header content as conditional, configured behavior
 
-Use supplied header inputs within the agreed shared-header scope. If the source config requires content beyond that scope, describe it and the needed target adaptation before expanding the implementation.
+The source rules below describe the original viewer. **For the current One App migration target, use native navigation bars, bottom tabs and the top bar; do not reproduce a custom Detailed cover header.** This target policy supersedes this reference's older shared-header recommendation. Keep the source facts as interpretation evidence and record the target adaptation explicitly.
 
 Relevant source behavior to preserve when applicable:
 
@@ -142,7 +142,9 @@ Relevant source behavior to preserve when applicable:
 - Logo, invite button, CTA, member count/avatars, and business-profile entry point have separate controls. A CTA needs both its configuration and its show flag.
 - Member visibility and restaurant/location behavior depend on runtime services and permissions. Structure does not contain the member records needed to populate them; the restricted business export is not a member directory.
 
-For a configured Detailed header, use `detailedHeader` from `@wix/himalaya/screens`. This shared builder uses Himalaya's cross-platform `CollapsingHeader`, a rounded detail card, and standard logo, member, and button components. Every migration must call this builder. Do not copy its component tree into an app. Pass the resolved title, subtitle, first cover image, logo, allowed member data, location label, configured actions, and the page nodes in `content`. Put the remaining screen content in `content` so it scrolls beneath the hero and the hero collapses with the page. Do not place those nodes as siblings of the returned header. Keep member data hidden when the source permissions or runtime services do not allow it. The current hero supports one cover image; keep the source order and record extra carousel images as an adaptation gap. If `isCollapsible` is false, pass `collapsible: false` so the hero keeps one height. [Header domain](https://github.com/wix-private/mobile-modules/blob/3a9713cf8bbb014ce4d3006d356a82a0f02db007/packages/libraries/pilates/src/domain/Header.ts) · [Header view model](https://github.com/wix-private/mobile-modules/blob/3a9713cf8bbb014ce4d3006d356a82a0f02db007/packages/libraries/pilates/src/elements/PilatesHeader/useViewModel.ts) · [Detailed header presenter](https://github.com/wix-private/mobile-modules/blob/3a9713cf8bbb014ce4d3006d356a82a0f02db007/packages/modules/wix-one-app-member-view/src/newStructure/elements/headers/detailedHeader/usePresenter.ts) · [Himi schema](https://github.com/wix-private/himalaya/blob/d3bc68c77151b678d337323615eb9889fa8e38c3/core/schema/core.proto)
+Do not call `detailedHeader` or add a `CollapsingHeader` hero/card in the migrated screen. Configure the shell through `navigation.topBarDefault`, complete per-screen `topBar` overrides, and `navigation.tabBar.presentation: "native"` for bottom tabs. Keep R08a's title and action-resolution rules; the shell owns back/menu controls. The `navigation-plan.json` first-tab source-header reference is evidence, not an instruction to render the old header.
+
+Record the omitted custom cover, carousel and overlapping card as an adaptation in `.himi/one-app/migration-report.md`; do not invent header-presentation rows in the derived coverage ledger. Preserve meaningful subtitle, location and configured CTA content as ordinary page content or supported native actions, subject to the original runtime access rules. Per-screen `topBar.actions` support `hiddenPath` when `navigation.topBarDefault.actions` declares the same action ID and binding, evaluated by `navigation.navLogicBundle`. Keep that registration for screen overrides: screen-only paths are not subscribed, and an unresolved path leaves the action visible. Preserve representable source visibility rules through these supported bindings; do not invent visibility fields. These bindings control presentation only, not authorization. Keep runtime access checks and report source visibility rules the target cannot represent as gaps. Unsupported leading avatars, logos or actions remain explicit gaps; do not invent member data or an in-page toolbar. Verify top bars, bottom tabs, back navigation and configured actions on affected native devices, including RTL; report unavailable checks as unverified. [Header domain](https://github.com/wix-private/mobile-modules/blob/3a9713cf8bbb014ce4d3006d356a82a0f02db007/packages/libraries/pilates/src/domain/Header.ts) · [Header view model](https://github.com/wix-private/mobile-modules/blob/3a9713cf8bbb014ce4d3006d356a82a0f02db007/packages/libraries/pilates/src/elements/PilatesHeader/useViewModel.ts) · [Detailed header presenter](https://github.com/wix-private/mobile-modules/blob/3a9713cf8bbb014ce4d3006d356a82a0f02db007/packages/modules/wix-one-app-member-view/src/newStructure/elements/headers/detailedHeader/usePresenter.ts) · [Himi schema](https://github.com/wix-private/himalaya/blob/d3bc68c77151b678d337323615eb9889fa8e38c3/core/schema/core.proto)
 
 ## Step 4 — Recreate each section envelope before its content
 

package/guides/sdk-reference.json

@@ -4117,7 +4117,7 @@
       {
         "name": "detailedHeader",
         "kind": "function",
-        "jsdoc": "/**\n * Build the shared Detailed header used by One App migrations.\n *\n * The header uses Himalaya's cross-platform `CollapsingHeader` and standard\n * components for the detail card, logo, member strip, and actions. A migration\n * calls this builder instead of copying header layout into each app. Himalaya's\n * hero accepts one image, so pass the first source cover image here.\n */",
+        "jsdoc": "/**\n * Build an optional Detailed cover header for screens that explicitly request one.\n *\n * The header uses Himalaya's cross-platform `CollapsingHeader` and standard\n * components for the detail card, logo, member strip, and actions. The One App\n * migration workflow uses native navigation bars and does not call this builder.\n * Himalaya's hero accepts one image.\n */",
         "decl": "export function detailedHeader(opts: DetailedHeaderOptions): Node;"
       },
       {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.1563.0",
+  "version": "0.1565.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": [
@@ -30,7 +30,7 @@
     "himi": "node --import tsx src/cli.ts",
     "gen:guides": "npm --prefix ../.. run authoring:gen",
     "build": "node --import tsx ../authoring-kit/gen-templates.mts && node ../authoring-kit/bundle.mjs && npm run build:dist",
-    "build:dist": "node scripts/bundle.mjs && node scripts/stage-authoring-runtime.mjs",
+    "build:dist": "node --import tsx ../html-to-t5/vocab-gen/gen-v2.ts && node scripts/bundle.mjs && node scripts/stage-authoring-runtime.mjs",
     "test": "node ../../tools/ci/run-tests.mjs --package tools/himi-cli --"
   },
   "dependencies": {
@@ -71,5 +71,5 @@
       "artifactId": "himalaya-cli"
     }
   },
-  "falconPackageHash": "4495e26cb984b5ce9679476ec39304566a0badf63ecae91eb884fe7d"
+  "falconPackageHash": "16b866eb8f71ec4f6b11fd676bbccd286b18aa734527d15c2f337eae"
 }