@wix/himalaya-cli 0.1538.0 → 0.1540.0

package/guides/recipe-search.md

@@ -32,11 +32,12 @@ The dedicated flow has two renderers for one search model:
   new non-empty token when the screen opens; that focuses the field and opens
   the keyboard. If the screen has no worker, seed the token through local state.
 - **Debounce.** Let `onChange` update the query and start the search after the
-  user pauses. The proposed native slot uses 250 ms when `debounceMs` is zero
-  or unset; a pending change flushes before `onSubmit`, so the submitted query
-  is current.
-  For the existing inline `SearchField`, set `debounceMs` explicitly (150–300 ms
-  for local filtering; 300–400 ms for a network search).
+  user pauses. `SearchField` (and the proposed native slot) uses 250 ms when
+  `debounceMs` is zero or unset, on every renderer; a pending change flushes
+  before `onSubmit`, so the submitted query is current. Set `debounceMs`
+  explicitly to tune it (150–300 ms for local filtering; 300–400 ms for a
+  network search). A `TextField` used as a search box debounces only when
+  `debounceMs` is set — unset, it sends every change.
 - **Clear.** Clear sets the query to `""`, runs `onChange` with the empty value,
   and returns to the initial state. It is not cancellation and must not invoke
   `onCancel`.
@@ -151,8 +152,9 @@ first; this recipe only adds the query layer.
 }
 ```
 
-- `debounceMs` batches keystrokes — 150–300ms is the sweet spot; without it every
-  character dispatches a worker action.
+- `debounceMs` batches keystrokes — 150–300ms is the sweet spot. Unset (or 0), a
+  `SearchField` waits 250 ms after the last keystroke; emptying the field sends `""`
+  at once.
 - `onSubmit` (keyboard search key) is optional when `onChange` already filters live.
 - For category/facet filtering alongside text search, add `FilterChips` with
   `optionsPath: "$service:posts.categories"` and a `selectCategory` action — same

package/guides/release-notes.md

@@ -16,6 +16,13 @@ areas, always in the same order, so you can skim for the one you care about.
 
 ## 2026-11-02
 
+### Getting started & the CLI
+
+- The `restaurant`, `podcast-creator` and `podcast-creator-owner` starter templates no longer paint
+  their cream text on a light grey search field, segmented control and chips. Their `dark-luxe` kit
+  had no `surfaceTertiary`, so the base app's light value showed through at 1.04:1. The kit now
+  ships a dark `surfaceTertiary`. (#4999)
+
 ### Validate & test
 
 - **`himi validate` now judges `textPrimary` on card surfaces.** Body text was judged only against
@@ -25,6 +32,16 @@ areas, always in the same order, so you can skim for the one you care about.
   with an error (also for `textPrimary` on the page); below WCAG AA 4.5:1 it is a warning. The
   finding says when the page and the card sit on opposite sides of mid-grey, so no single text
   colour can serve both. (#4999)
+- **`himi validate` now judges `textSecondary` too, and on every surface that text sits on.** Both
+  body text colours are judged against `surfaceSecondary` and `surfaceElevated` (cards, sheets, list
+  rows), `surfaceTertiary` (search fields, segmented controls, chips, badges) and `surfaceSubtle`
+  (Android's Material low containers). Below 1.5:1 validate fails with an error, on the page too;
+  below 4.5:1 it is a warning. (#4999)
+
+### Branded Lite & Owner Lite
+
+- Branded Lite's dark-theme secondary text is now `#8B949E`. It clears 4.5:1 on the app's cards and
+  its search field; before, it was 4.31:1 on the search field. (#4999)
 
 ## 2026-11-01