@wix/himalaya-cli 0.1632.0 → 0.1634.0

package/fixtures/wix-canned.json

@@ -1230,6 +1230,36 @@
       "count": 2
     }
   },
+  "POST /badges/v4/assignments/query": {
+    "badgeAssignments": [
+      {
+        "id": "asg-0001",
+        "badgeId": "bdg-0001",
+        "memberId": "mem-0001"
+      }
+    ],
+    "pagingMetadata": {
+      "count": 1,
+      "hasNext": false
+    }
+  },
+  "POST https://apps.wix.com/_api/members-one-app/api/members": {
+    "items": [
+      {
+        "id": "mem-0001",
+        "displayName": "Dana R.",
+        "member": {
+          "role": "MEMBER",
+          "online": false,
+          "lastOpenApp": {
+            "amount": 3,
+            "unit": "hour"
+          }
+        }
+      }
+    ],
+    "total": 1
+  },
   "POST /badges/v4/badges/query": {
     "badges": [
       {
@@ -1408,7 +1438,7 @@
       ]
     }
   },
-  "POST /members-feed-viewer/v1/members-viewer-feed-notifications/query": {
+  "POST /_api/members-feed-viewer/v1/members-viewer-feed-notifications/query": {
     "viewerFeedNotifications": [
       {
         "id": "ntf-0001",
@@ -2323,5 +2353,8 @@
         "balance": 25
       }
     }
+  },
+  "POST /_api/referral-rewards/v1/referral-rewards/query": {
+    "referralRewards": []
   }
 }

package/guides/getting-started.md

@@ -495,7 +495,8 @@ select the deployed customer target explicitly:
 ```sh
 himi login --browser --target wix
 wix login
-# no browser? export WIX_API_KEY, then run himi login --wix --target wix instead of the two lines above
+# no browser here? pipe the owner's held Wix token: printf '%s' "$TOKEN" | himi login --wix --wix-token-stdin --target wix
+# (or export WIX_API_KEY on a server, then himi login --wix --target wix) instead of the two lines above
 himi dist --app <app> --release <release-id> --site <owned-site-id> \
   --platform ios,android --signing byo --android-signing qa-keystore --wait --target wix
 ```

package/guides/himi-json-output.md

@@ -14,6 +14,12 @@ require those fields. Existing error-only push refusals now also carry `ok: fals
 Output channels and process exit codes are unchanged. Read JSON failures on both
 stdout and stderr; progress/warnings are not failure envelopes.
 
+## `himi sdk unverified` codes
+
+| Code | Meaning |
+| --- | --- |
+| `sdk_verification_unknown` | A cached SDK reference has one or more exports without verification metadata (an older or mixed catalog), so the unverified list cannot be trusted. Refresh the catalog (unpin an older kit first if needed). Exit 2. |
+
 ## `himi store preflight` / `himi store upload` / `himi testflight` config failures
 
 | Code | Meaning |
@@ -106,6 +112,7 @@ return an empty array.
 | `identity_source_unverified` | Collected source hashes or the business display name cannot be verified. Recollect older evidence that did not save business identity. |
 | `identity_target_unverified` | The technical app slug, target compilation or complete built descriptors are unavailable. |
 | `literal_slug_visible` | Built display text or the known business-chat identity seed contains the technical slug instead of the collected business identity, without matching exact authored source copy. |
+| `app_name_is_slug` | `config.ts`'s `name` (the launcher label and the screens that show the app name) is still the technical slug, while the built display text has no literal slug to report. The result carries `appName` with a `hint`; `--fix` writes the collected business name into `config.ts` (only a literal equal to the slug is rewritten, never a name the author chose). |
 
 The check reads built descriptors, not every possible runtime string. A passing
 result does not verify dynamic live data, translations, branding images or device
@@ -133,6 +140,7 @@ is a positional screen ID; use `--deep=<value>` to diagnose a nonnumeric depth.
 | `ux_evidence_unreadable` | The UX evidence artifact cannot be read. |
 | `lint_errors` | Build/lint validation found errors. |
 | `depth_budget_exceeded` | A screen or a bound list/grid row template nests deeper, or has more components, than the depth budget (`depth-budget` validator pass), or any of its JSON — props, modifiers, `input`, action `args` — nests past the raw-JSON ceiling of 256 levels. Each `issues[]` entry with `pass: "depth-budget"` carries the JSON `path` of the deepest node (the tree root for a node count, the first value past the ceiling for raw JSON), the `limit` and the `actual` value. Takes precedence over `lint_errors`, and `--force` does not override it: content over the budget overflows the renderer's stack on devices already in the field. Flatten the layout and push again. `himi patch screen` refuses an over-deep raw descriptor with the same code, before any network request, and `himi pack` / `himi template publish` refuse with it even under `--force`. |
+| `placeholder_site_binding` | The app declares `wix_api` and uses the `wix-consumer` auth provider, but its resolved auth still has the scaffold placeholder `clientId` (`YOUR_WIX_CLIENT_ID`) or `siteUrl` (`https://your-site.example.com`), and it is not bound to a source site through the One App identity. Nothing is published: every Wix call would fail. Bind the site (`himi one-app provision` for a One App migration; otherwise a real clientId and siteUrl). `--force` does not override it. |
 | `one_app_readiness_failed` | Reserved legacy refusal code. One App migration readiness is now advisory: publish and promotion report structured warnings instead. Other independent release checks may still refuse a push. |
 | `control_token_expired` | The selected control token has expired. |
 | `app_source_contains_secrets` | Source archiving detected a possible credential. |

package/guides/himi-skill.md

@@ -518,7 +518,8 @@ select the deployed customer target explicitly:
 ```sh
 himi login --browser --target wix
 wix login
-# no browser? export WIX_API_KEY, then run himi login --wix --target wix instead of the two lines above
+# no browser here? pipe the owner's held Wix token: printf '%s' "$TOKEN" | himi login --wix --wix-token-stdin --target wix
+# (or export WIX_API_KEY on a server, then himi login --wix --target wix) instead of the two lines above
 himi dist --app <app> --release <release-id> --site <owned-site-id> \
   --platform ios,android --signing byo --android-signing qa-keystore --wait --target wix
 ```

package/guides/iap-screen-adoption.md

@@ -14,7 +14,7 @@ and generated templates. Historical receipts retain their recorded amounts.
 | `himi-branded-lite-plans` | Pricing Plan ID; `priceLine` | Shared Apple pricing and existing Join action through `pricingPlanOrders`; only one-time unlimited Plans can start Apple checkout |
 | `wix-spaces-plan-detail` | Pricing Plan ID; `price` | Shared pricing; remains read-only |
 | `createCheckoutService` / `checkoutScreen` | Pricing Plan ID; `priceLine` | Same shared Plans pricing and purchase; existing options, copy, login destination and factory shape retained |
-| `himi-store-product` | Stores product ID; `price` | Shared pricing; physical options/add/save retained. With Stores Apple sales enabled, a mapped digital product without options offers Buy now through the app-owned eCom order; `STORES_ITEM_PAYMENT_ENABLED` selects StartItemPayment instead ([checkout](iap-wix-checkout.md#wix-stores-items-through-startitempayment-off)) |
+| `himi-store-product` | Stores product ID; `price` | Shared pricing; physical options/add/save retained. With Stores Apple sales enabled, a mapped digital product without options offers Buy now through wix-iap StartItemPayment, which places and charges the eCom order server-side ([checkout](iap-wix-checkout.md#wix-stores-items-through-startitempayment)) |
 | `himi-store-shop` | Stores product ID; price in `subtitle` | Batched visible pricing, including paged results; saved/cache metadata retains the commerce price rather than an Apple offer |
 | `himi-store-saved` | Stored product ID; `price` | Reprices saved rows through the shared source when shown; no added purchase action |
 | `himi-branded-lite-home` | Stores product IDs; hero and rail prices | Shared pricing on visible product offers; navigation-only Program cards remain unchanged |
@@ -44,9 +44,9 @@ withdraw the shared checkout's access state; reading existing access never creat
 The existing Stores adapter reads `paymentStatus: PAID` as granted. That proves payment,
 not usable delivery of a download or course. It also lacks a verified member-scoped
 existing-ownership read. Only the product screen installs `storesProductOrders` for sales, while
-`storesAppleSalesEnabled()` is true. As shipped, `STORES_APPLE_SALES_ENABLED` is on and
-`STORES_ITEM_PAYMENT_ENABLED` is off, so mapped digital products without options use the app-owned
-eCom checkout and order before the Apple charge. Live digital fulfillment remains unverified.
+`storesAppleSalesEnabled()` is true. As shipped, `STORES_APPLE_SALES_ENABLED` is on, so mapped digital
+products without options are paid through wix-iap StartItemPayment: the device opens no eCom checkout
+and makes no cashier charge. Live digital fulfillment remains unverified.
 The cart and list screens do not start Apple sales. A confirmed physical product retains its
 regular checkout.
 Unknown product facts, unsupported catalog apps and missing routing fail closed.

package/guides/importable-sdks.md

@@ -36,7 +36,7 @@ package in one greppable file) or `GET /v1/sdk/<name>` over HTTP; in the CLI,
 - `@himalaya/hhp` — —
 - `@himalaya/himi-apps` — Tier-5 typed binding for cross-app open / host queries.
 - `@himalaya/iap` — Tier-5 typed binding to the platform's in-app-purchase capability.
-- `@himalaya/iap-checkout` — @wix/himalaya/iap-checkout — the ONE shared flow that sells a digital Wix item through the App Store, for any screen: a vertical order, its `appleIAP` cashier charge, mobile-apps-wix-iap's payment, the managed StoreKit purchase and the vertical's own access read.
+- `@himalaya/iap-checkout` — @wix/himalaya/iap-checkout — the ONE shared flow that sells a digital Wix item through the App Store, for any screen: mobile-apps-wix-iap's payment, the managed StoreKit purchase and the vertical's own access read.
 - `@himalaya/keyboard` — Tier-5 typed binding for the platform's keyboard capability.
 - `@himalaya/kyber-api` — narrow Tier-5 binding for Kyber BO HTTP calls.
 - `@himalaya/l10n` — synchronous app-catalog copy (SDK foundation; requires host integration).

package/guides/one-app-section-mappings.md

@@ -159,8 +159,8 @@ carousel placement remain separate gaps; the mappings above stay Partial.
 
 | Source sectionDefinitionId | Source viewer component | Himalaya implementation | Placement / reuse | Class | Settings, actions and gaps |
 | --- | --- | --- | --- | --- | --- |
-| `loyalty_status_section` | `loyalty.components.StatusSection` | [himi_loyalty member card](https://github.com/wix-private/himalaya/blob/adf4c8b47fd237307b278a5dbb8198a94b7feb69/apps/himi-branded-lite/dev/index.ts) (`buildLoyalty` points card) + [loyalty worker](https://github.com/wix-private/himalaya/blob/adf4c8b47fd237307b278a5dbb8198a94b7feb69/core/dev-server/tier5-bundles-src/himi-branded-lite-loyalty/index.ts "audience-lint-ok: optional pinned upstream evidence, not a local authoring dependency") | Existing base; adaptation needed | Partial | The member card on `himi_loyalty` reads the signed-in member's balance (`getCurrentMemberLoyaltyAccount`) and, beside it, the tiers program and the claimed coupons; it shows the balance, the tier name, the points-expiry line and `Rewards available (N)` (rewards the balance covers on the member's tier + ACTIVE claimed coupons), each blank when its read fails. Visitors get the sign-in gate. Not carried over: the referral-coupon share of the count (no referral spec in codegen) and the one-app `View` link (the catalog it opens is on the same screen). |
-| `loyalty_offering_section` | `loyalty.components.OfferingSection` | [himi_loyalty](https://github.com/wix-private/himalaya/blob/97f1542f2f7d6e8cb7a902b912c87dcaa37e5a67/apps/himi-branded-lite/dev/index.ts) + [rewards worker](https://github.com/wix-private/himalaya/blob/97f1542f2f7d6e8cb7a902b912c87dcaa37e5a67/core/dev-server/tier5-bundles-src/himi-branded-lite-loyalty/index.ts "audience-lint-ok: optional pinned upstream evidence, not a local authoring dependency") | Existing base; adaptation needed | Partial | Reuse program/reward reads and required-points presentation. Preserve offering selection. Member earning/redemption operations are not established by this read-only rewards list. |
+| `loyalty_status_section` | `loyalty.components.StatusSection` | [himi_loyalty member card](https://github.com/wix-private/himalaya/blob/e5d1313654a200084499ec74eb68fa77992d096e/apps/himi-branded-lite/dev/index.ts) (`buildLoyalty` points card) + [loyalty worker](https://github.com/wix-private/himalaya/blob/e5d1313654a200084499ec74eb68fa77992d096e/core/dev-server/tier5-bundles-src/himi-branded-lite-loyalty/index.ts "audience-lint-ok: optional pinned upstream evidence, not a local authoring dependency") | Existing base; adaptation needed | Partial | Member-only points, tier, expiry and the reward count are implemented in the shared screen. The count includes affordable active rewards, active claimed loyalty coupons and active referral coupons; failed reads leave the total unknown. View opens `himi_loyalty_reward`, with current-member eligibility, a confirmation step, coupon redemption and balance refresh. Private fields never hydrate or persist. Source-widget placement still requires adaptation; successful member REST recordings remain required for migration acceptance. |
+| `loyalty_offering_section` | `loyalty.components.OfferingSection` | [himi_loyalty](https://github.com/wix-private/himalaya/blob/e5d1313654a200084499ec74eb68fa77992d096e/apps/himi-branded-lite/dev/index.ts) + [rewards worker](https://github.com/wix-private/himalaya/blob/e5d1313654a200084499ec74eb68fa77992d096e/core/dev-server/tier5-bundles-src/himi-branded-lite-loyalty/index.ts "audience-lint-ok: optional pinned upstream evidence, not a local authoring dependency") | Existing base; adaptation needed | Partial | Shared `himi_loyalty` supports base/custom tier offerings, exact tier configurations, benefit descriptions and Show all after three tier cards. Active birthday rules expose member birthday editing; active social-follow rules expose configured supported HTTPS channels. The published test app has four Loyalty instances with empty settings, and neither definition declares settingsData, so no offering-selection field is inferred. Source-widget placement and source rollout flags still need per-app review; the Himi controls follow active rule/channel configuration. |
 
 ### 8. referrals-section-definitions.json
 
@@ -425,7 +425,7 @@ These rows have reusable code, but their remaining requirements must not disappe
 - [Photo Albums worker](https://github.com/wix-private/himalaya/blob/97f1542f2f7d6e8cb7a902b912c87dcaa37e5a67/core/dev-server/tier5-bundles-src/wix-spaces-photo-albums/index.ts "audience-lint-ok: optional pinned upstream evidence, not a local authoring dependency") explicitly says no album API is wired and renders an empty state.
 - [Restaurant basket worker](https://github.com/wix-private/himalaya/blob/97f1542f2f7d6e8cb7a902b912c87dcaa37e5a67/core/dev-server/tier5-bundles-src/wix-spaces-food-orders/index.ts "audience-lint-ok: optional pinned upstream evidence, not a local authoring dependency") explicitly avoids the owner-capable Orders API and supplies no placed-order history.
 - [Saved products worker](https://github.com/wix-private/himalaya/blob/97f1542f2f7d6e8cb7a902b912c87dcaa37e5a67/core/dev-server/tier5-bundles-src/himi-store-saved/index.ts "audience-lint-ok: optional pinned upstream evidence, not a local authoring dependency") uses device-local saves; it does not establish an account-backed wishlist mapping.
-- [Loyalty worker](https://github.com/wix-private/himalaya/blob/97f1542f2f7d6e8cb7a902b912c87dcaa37e5a67/core/dev-server/tier5-bundles-src/himi-branded-lite-loyalty/index.ts "audience-lint-ok: optional pinned upstream evidence, not a local authoring dependency") reads the program and reward catalog, not the current member's points balance.
+- The shared Loyalty worker now includes member status and links to a separate member reward/coupon journey. This does not automatically implement an arbitrary source section placement; keep member credentials and rendered evidence in the migration acceptance record.
 - [Events detail worker](https://github.com/wix-private/himalaya/blob/97f1542f2f7d6e8cb7a902b912c87dcaa37e5a67/core/dev-server/tier5-bundles-src/himi-events-detail/index.ts "audience-lint-ok: optional pinned upstream evidence, not a local authoring dependency") documents the owner-scoped, best-effort attendee read; it does not supply a full consumer guest list.
 - [Groups feed worker](https://github.com/wix-private/himalaya/blob/97f1542f2f7d6e8cb7a902b912c87dcaa37e5a67/core/dev-server/tier5-bundles-src/himi-branded-lite-feed/index.ts "audience-lint-ok: optional pinned upstream evidence, not a local authoring dependency") chooses its group internally; it does not accept a fixed source group selection.
 - [Program detail worker](https://github.com/wix-private/himalaya/blob/97f1542f2f7d6e8cb7a902b912c87dcaa37e5a67/core/dev-server/tier5-bundles-src/himi-branded-lite-program/index.ts "audience-lint-ok: optional pinned upstream evidence, not a local authoring dependency") explicitly identifies the legacy CHALLENGES app ID, supporting the Online Programs family mapping; it does not provide the missing participating-program carousel.

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

@@ -163,6 +163,7 @@ The CLI's versioned native-widget inventory supplies these rows automatically.
 | `achievements_carousel_section` | The same Program state/display rules, default limit 5 and page dots. |
 | `newBlog_postlist_vertical_section`, `newBlog_compact_post_list_vertical_section` | Row display options, unlimited paging or a limited count with See All Posts, and layout. Coverage derives these per placement from the authored settings: see "Generate blog post lists from their settings". |
 | `events_list_section` | Date badge, Share and the appropriate RSVP/ticket action. |
+| `platform_elements_image_section` | Press behavior. `onPressType: "openAsModal"` opens the image full screen: tap it with the reserved `himi.lightbox` action and `args.images` set to `[{ "url": <the image url>, "alt": <its accessibility label> }]`. `nothing` and a `none` action need no tap. Coverage derives the row per placement from the authored value. |
 | `platform_general_members_section`, `platform_general_members_section_bp` | Effective member strip and directory journey: totals/search, alphabetical sections, Follow, activity/privacy. Distinguish badge chips from actual viewed-member program progress. |
 | `file_share_section` | Signed-in-only file/folder section. Preserve access rules, instance settings and View All (`media.openFileShareListScreen`); a media gallery is not File Share. |
 | `events_guests_section` | Signed-in-only guests for the configured event, preserving the event selector, guest privacy and display settings; an avatar summary is not the full guest list. |
@@ -282,7 +283,10 @@ the same values:
 - **Row facts.** Every `displayOptions` key set to `true` is shown: `author` (avatar, name and the
   admin badge), `comments` (comment count), `likes`, `times_viewed`, `post_date`, `reading_time`,
   `cover_image`. Bind each from the post and its metrics. A row that shows a fixed subset such as
-  date, views and likes is a gap. A key that is `false` or absent stays hidden.
+  date, views and likes is a gap. A key that is `false` or absent stays hidden. Blog v3 `queryPosts` returns no
+  view, like or comment counts unless the request asks for `fieldsets: ["METRICS"]` (without it every count reads
+  0), and only the author's `memberId`: resolve the name and photo with `getMember` and show the author only when
+  the member resolves. A count the API did not return stays hidden, never 0.
 - **Unlimited.** `contentSettings.postsPerCategory: "unlimited"` follows the page cursor to the last
   post. Bind `pagination.cursor` and `pagination.onLoadMore` as described in `himi docs
   designing-himi-screens`; a fixed first page (for example 20 posts) is not an unlimited list.
@@ -427,7 +431,9 @@ Apply these interpretation rules:
   It resolves the effective source theme with the reader the source app instance
   actually uses, then compares the resolved primary, background and content colors,
   each button's `borderRadius` and `outlineWidth`, and resolved heading/body font families
-  against the app's `tokens.json`.
+  against the app's `tokens.json`. A Branded theme that stores only `primaryColor`
+  (no `colors`) is still compared: that value is the app's brand color, so the template's
+  default accent fails the check until `--fix` writes it.
   Hex case and shorthand are normalized; an absent button token is compared with the
   value the renderer draws (an outline only on `secondary`; a radius of `radius.pill`,
   else 24), not called a difference. A variant without its own radius must draw the
@@ -504,6 +510,22 @@ Apply these interpretation rules:
   list then shows no Ended label for a time without an offset, which is correct, and a
   `business_time_zone_unavailable` warning says so. A re-apply keeps the zone for the same site and
   drops it for another.
+- **Write the verified values with the CLI.** Run `himi one-app provision --evidence-dir .himi/one-app --content .`
+  after scaffolding. From the collected evidence it sets `currency` on `himi_loyalty` and `businessTimeZone` on
+  `himi_services`, `himi_service` and `himi_time` (a value it could not verify stays as the template ships it;
+  nothing is invented). It writes the business name into `config.ts`'s `name` and over the slug `himi init` baked
+  into displayed names (display slots only, never ids or URLs; a name you chose is kept), so the normal flow needs
+  no `validate-identity --fix`. It states the bottom bar as native (`navigation.tabBar.presentation: "native"`; an
+  explicit `"kit"` is kept; the output's `tabBar` reports `set`, `unchanged` or `absent`). When the collection
+  recorded `memberChat: true` (never a guess), it opens the member Inbox from every baked door (the top-bar chat
+  action, the drawer's Inbox item, the chat thread's parent and "Back to inbox", the Profile link) if the scaffold
+  contains `himi_inbox`; otherwise the output's `chat` says `unverified` and the doors keep opening
+  `himi_business_chat`. `himi one-app header-badges` writes the top-bar action, so run provision again after it.
+  It also **binds the app to the source site**: the scaffold's `WixConsumerAuthProvider` carries placeholders
+  (`YOUR_WIX_CLIENT_ID`, `your-site.example.com`) that make every Wix read fail, so provision writes
+  `visitorSource: "one-app"`, the collected `metaSiteId` and `siteUrl` (a real clientId you set is kept;
+  `siteBinding` reports `set`, `unchanged`, `unverified` or `absent`). `himi push` refuses a Wix-backed app that
+  still has the placeholders (code `placeholder_site_binding`, no `--force`). It is safe to run again.
 - **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
@@ -536,6 +558,20 @@ Apply these interpretation rules:
   totals. A collected total is a source snapshot. Only use an injected live
   count reader when its public, site-bound permission path has been verified.
   See the screens SDK's downloadable business-contact guide for the full recipe.
+- **Chat opens the Inbox when the source allows member chat.** The source top-bar chat
+  button opens a member-to-business room only when the branded app's `inbox.chatType`
+  is `MEMBER_TO_BUSINESS`; in every other case, including an app whose config has no
+  `inbox` at all, it opens the Inbox: a list of the member's conversations with the
+  business and with other members, plus a way to start a new chat with a member.
+  `collect` reads that setting from the app's public mobile config, as a Visitor, and
+  records it in `inbox-settings.json` (`chatType` and its `source`) and `manifest.json`
+  `memberChat`: `true` or `false`, or `null` when it could not be read or the source is
+  a free One App (warning `inbox_chat_type_unknown`). Carry it: when `memberChat` is
+  `true`, set provisioning `memberChat: true` and point the top-bar chat action at
+  `himi_inbox`; every other Inbox entry (tab, drawer, Explore, Profile) follows the same
+  flag. When it is `false` or `null` leave `memberChat` unset and keep the top-bar chat
+  on `himi_business_chat`. Never turn member chat on from a guess: an owner who limited
+  the app to the business must not gain a member chat.
 - 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
@@ -682,8 +718,9 @@ Apply these interpretation rules:
   output against the source. A persistent nav worker needs a supported refresh
   path; a screen-only load, page-row count or foreground push receipt count is
   insufficient. The source Member notification aggregate is MOBILE/UNSEEN, capped
-  at100. `countUnseenNotifications({ site: boundMetaSiteId })` reads that aggregate
-  through the source Member route. It requires the updated native core, rebuilt
+  at100. `countUnseenNotifications()` reads that aggregate through the source Member
+  route. Name no site: a bound host sends its own, and the multi-tenant Player (no
+  bound site) lets the Member credential decide and refuses any named one. It requires the updated native core, rebuilt
   consuming binaries and published SDK; default web and old binaries remain
   unavailable for this reader. Never replace that refusal with zero.
   Chat counts unread rooms, while legacy cart counters can include unsynced local
@@ -1257,6 +1294,24 @@ function call in the literal makes them fail with "expected a `"<screenId>": {`
 authored descriptor". Blank lines and whole-line `//` comments between entries are
 accepted.
 
+Do not write a generator of your own. `himi one-app generate --evidence-dir .himi/one-app --content .` turns each
+source page into a screen descriptor from the collected evidence alone: the screen id and title come from the page's
+source label, and styles, alignment, buttons, images and their tap (`openAsModal` opens full screen), the contact
+section and the business description are read from the source. A section it has no mapping for is reported with
+`sections_unmapped` and nothing stands in for it. Data sections use shared modules and recipes
+(`recipes/*.json`) when the scaffold ships them; the current starter ships none, so today they take the fallback
+below. A page with such modules gets ONE worker, `tier5-src/page-<screen>/index.ts`, that registers the modules
+its sections use (blog list, programs carousel, inline events). A page that is only a template vertical (programs list,
+members, loyalty, shop, groups feed) opens the template's screen, and a groups feed passes the source's own title,
+"Group list" label and post count. A data section never vanishes: when the shared modules cannot honor its settings
+(featured-only lists, another post layout, events or groups limited to a chosen set) or its recipe is missing from the
+scaffold, it keeps its place as the source's title and a "See All" button that opens the page showing that data,
+and the reason is listed in `gaps`, never approximated as the real list. Only a section with no mapping at all stays
+in `unmapped`. The first four visible pages become the bottom tabs and the rest the More screen. The output names the
+published `revision` and `fetchedAt` of the evidence it read, so a migration generated from older evidence shows the
+old value: run `himi one-app migrate` again to refresh it before the final check. The file it writes is the
+`--upsert` input below.
+
 So generate descriptors as data and write them with the CLI:
 
 ```sh
@@ -1266,11 +1321,27 @@ himi template screens --upsert --from .himi/one-app/gen/screens.json
 The file is one JSON object, `{ "<screenId>": <ScreenDescriptor>, … }`. Each existing
 id is replaced in place; each new id is added and registered in
 `navigation.linkableScreens`. One invalid entry refuses the batch and restores every
-file. A builder call such as `detailedHeader(...)` written inline in `dev/index.ts`
+file. A screen that starts with an empty slot (a `Spacer`, a container with no children, an
+`Image` with no url) is refused: when a source header is dropped, do not leave its place behind,
+because the slot paints a blank band under the toolbar. A builder call such as `detailedHeader(...)` written inline in `dev/index.ts`
 cannot be inspected: call the builder in your generator and serialize the value it
 returns. Run the generator inside the app (after `npm install`), so
 `@wix/himalaya/screens` resolves to the app's own dependency.
 
+### Repoint the template's tab ids
+
+The template's `navigation.linkableScreens` entries and its home and profile tabs carry its own tab ids (`"home"`,
+`"profile"`, the vertical tabs). Your `navigation.tabBar` replaces those tabs, so every entry whose `tabId` is not
+one of yours is a leftover. `himi validate --strict` reports each as `nav-linkable-tab-unknown` and lists your real
+ids; nothing repoints them, because the right tab depends on where the source shows the screen:
+
+- a screen the source opens from a tab keeps that tab's id;
+- a screen reached from the overflow list takes the id of the **More** tab only if you created one; a template with no More tab uses `""`;
+- a screen with no tab owner takes `""`, the default stack.
+
+Check `homeScreenId` and any `himi.open` target that still names a template screen (`"home"`, `"profile"`) the same
+way: it must be a screen your `SCREENS` map defines.
+
 ### Preserve the template features the source exposes
 
 Treat trimming as a source-feature decision, not a list of screens reached during
@@ -1292,6 +1363,11 @@ After applying identity and before claiming completion, run:
 himi one-app validate-identity --evidence-dir .himi/one-app --content . --json
 ```
 
+`himi init` names a scaffold after its technical slug, and `config.ts`'s `name` is the app's
+display name (launcher label and the screens that show it). The command also fails with
+`app_name_is_slug` while that name is still the slug; `--fix` writes the collected business
+name into it (only a literal equal to the slug is rewritten, never a name you chose).
+
 The command verifies the collected business-name hash, builds the current content,
 and checks emitted screen titles, supported component display fields and the known
 business-chat identity seed for accidental literal slugs. It ignores route IDs,