feat(lab): MobilePowerSearch gains the Core PowerSearch sheet's behavior

packages/lab/src/MobilePowerSearch/MobilePowerSearch.doc.mjs

@@ -70,14 +70,14 @@ export const docs = {
       name: 'hasClear',
       type: 'boolean',
       description:
-        'Shows Clear all in the Filters sheet footer. Read-only filters are never cleared.',
+        'Shows Clear all in the Filters sheet footer. Clear all removes every filter, read-only ones included, as the Core PowerSearch clear control does, and reports one `remove` change at the last index.',
       default: 'true',
     },
     {
       name: 'timezoneID',
       type: 'string',
       description:
-        'IANA timezone for date values. Used by tokens, Filters rows, and the date editors alike, so a boundary date reads the same everywhere.',
+        'IANA timezone, accepted for API parity with Core PowerSearch. Dates follow Core: tokens and Filters rows show a date_absolute as the Core token does (its day in the browser zone, no time of day) and the date editors read and write the UTC day, so this prop does not change a date value today.',
     },
     {
       name: 'maxSearchResults',
@@ -107,7 +107,7 @@ export const docs = {
   ],
   usage: {
     description:
-      'Lab prototype for trying the touch PowerSearch flow. Choose it explicitly on touch layouts (for example `const Search = isTouch ? MobilePowerSearch : PowerSearch`); it never switches on pointer type by itself. The whole field is one Manage filters trigger showing display-only tokens. Tapping it opens a tall Filters sheet listing each filter as a chevron row with its value in bold, Add filter at the top right, and sticky Clear all and Done actions. Opening a row edits that filter in a sheet with Cancel, Apply, and Remove. Add filter opens directly when no filter exists; when the config names a content-search field it carries that search with inline suggestions. Creating a filter drills field → operator (radios, only when a field has more than one) → value. Each step is its own BottomSheet; moving between steps is a BottomSheet replace handoff (the entering step rises above the leaving one under the one scrim), so the steps need no BottomSheetSwitcher. Single and multi-value choices are full-width rows with trailing checks; other value types use the matching Astryx input. Fields whose only operators are nested are left out with a development warning.',
+      'Lab prototype for trying the touch PowerSearch flow. Choose it explicitly on touch layouts (for example `const Search = isTouch ? MobilePowerSearch : PowerSearch`); it never switches on pointer type by itself. The whole field is one Manage filters trigger showing display-only tokens. Tapping it opens a tall Filters sheet listing each filter as a chevron row with its value in bold, Add filter at the top right, and sticky Clear all and Done actions. Opening a row edits that filter in a sheet with Cancel, Apply, and Remove. Add filter opens directly when no filter exists; when the config names a content-search field it carries that search with inline suggestions. Creating a filter drills field → operator (radios, only when a field has more than one) → value. Each step is its own BottomSheet; moving between steps is a BottomSheet replace handoff (the entering step rises above the leaving one under the one scrim), so the steps need no BottomSheetSwitcher. Single and multi-value choices are full-width rows with trailing checks; other value types use the matching Astryx input. Announcements made while a sheet is open — an added or removed filter, a result count, an empty-result message — are spoken inside the open sheet; Clear all removes every filter and is announced once the flow has closed. A filter whose field or operator the config no longer knows still lists by its raw keys, and its step offers Remove. Fields whose only operators are nested are left out with a development warning.',
     bestPractices: [
       {
         guidance: true,
@@ -117,7 +117,7 @@ export const docs = {
       {
         guidance: true,
         description:
-          'Pass timezoneID whenever filters carry dates, so tokens, rows, and editors agree on the calendar day.',
+          'A date_absolute value is the UTC midnight of the chosen day, as Core PowerSearch stores it, and tokens and rows show it as the Core token does, so a filter reads and means the same in both components.',
       },
       {
         guidance: false,