@wssto2/vue-core 0.4.21 → 0.4.23

package/CHANGELOG.md

@@ -0,0 +1,460 @@
+# Changelog
+
+## 0.4.23 — 2026-10-11
+
+Test and tooling only; no change to the library's code or behaviour. Two items, one commit each.
+
+### Requires
+- go-core unchanged: **`v1.7.0`**; **`vue` 3.5.19 or later**.
+
+### Fixed
+- **The notifications gear test no longer fails on a loaded machine.** `notificationsFeature > has a gear in the inbox…` waited for the lazy settings page inside `waitFor`'s 1s default, and the first import of `SettingsPage.vue` is a cold transform (about 800ms idle, several seconds under load), so it ended on `home`. The page is now imported in a `beforeAll`. It was never tied to the clock: it passes at 00:30, 06:00, 12:00 and 23:50 UTC under `TZ=UTC` and `TZ=Europe/Zagreb`.
+- **`npm run lint` ignores `.claude/`.** An agent worktree inside the checkout was linted as part of the project and failed `npm run check` (and so `prepublishOnly`).
+
+### Changes to existing behaviour
+- None.
+
+## 0.4.22 — 2026-10-11
+
+An empty month/year says so, and a question is the only thing on the form. From the ARV cleanup run on 0.4.21. Three items, one commit each. `CHANGELOG.md` now ships in the package.
+
+### Requires
+- go-core unchanged: **`v1.7.0`**; **`vue` 3.5.19 or later**.
+
+### Added
+- **`placeholder` on `MonthYearField`**, shown while both month and year are empty, in the muted placeholder style at every width. By default it is the library's "Choose…" (`core.form.select.choose`, the wording `DateField` and `SelectField` use: en "Choose…", hr "Odaberite…", bs and sr-Latn "Izaberite…", sl "Izberite…"). Read mode is unchanged. ARV: `components/vehicle-entry/EntryVinStep.vue` (Prva registracija, step 1), `features/vehicles/components/VehicleEntrySection.vue` and `VehicleBasicSection.vue` now show "Odaberite…" in an empty field; none passes a placeholder, none needs to.
+- **`icon?: IconName` on `CommandQuestion`**, passed to the question's `AlertDialog` (its default still follows the tone). ARV: `features/vehicles/components/phase/DeliverSheet.vue` gives Isporuka's question `icon: "archive2Fill"` when it moves to 0.4.22.
+
+### Fixed
+- **A question no longer sits over a stale failure.** `form.validate()` clears `form.failure` when the inputs check out, as it already cleared the errors. A command with `ask` that was refused once ("Check the marked fields and try again."), then fixed and pressed again, showed the question over the old banner. A command without `ask` already cleared it (its call does); a test pins both. Chosen in `useForm`, not `useCommand.run()`: `run()` only sees a read-only `failure`, and every caller of `validate()` gets the right behaviour (a successful check means the earlier refusal no longer holds). ARV: the only `ask` is Isporuka; ARV's own `form.validate()` calls are its form core's, not this one.
+
+### Changes to existing behaviour
+- **An empty `MonthYearField` shows "Choose…"** where it showed an empty pill.
+- **`useForm().validate()` clears the failure on success.**
+- **Pinned by tests that were updated:** none; no test pinned an old default.
+
+## 0.4.21 — 2026-10-10
+
+A step opens at its top, and a command can ask before it runs. From ARV wave 3 (vehicle entry at 390, Isporuka). Two items, one commit each.
+
+### Requires
+- go-core unchanged: **`v1.7.0`**; **`vue` 3.5.19 or later**.
+
+### Added
+- **`ask` on `useCommand`**: `ask: (input) => ({ title, message?, confirmLabel?, tone? }) | null`. After the inputs check out and before anything is sent, `CommandDialog` puts the question in an `AlertDialog` over the filled form. Yes calls with the usual idempotency key; Cancel returns to the form untouched and sends nothing; a refusal after Yes (422, conflict) lands on the form like any other. `null` asks nothing this time. The question may depend on the input and on what the caller holds. An invalid form is not asked about: its errors go on the fields as before. New on the command: `question` (a ref, set instead of calling) and `answer(yes)`; `confirm()` skips the question (it is the answer). The type of `CommandDialog`'s `command` takes `question` and `answer` as optional, so a hand-made adapter still type-checks. ARV: `features/vehicles/components/phase/DeliverSheet.vue` (the `ask()` wrapper, the `sheet` adapter, `runDeliver` and its own `AlertDialog`) becomes `ask: () => ({ title, message: payments.confirmBody(...), confirmLabel, tone: "neutral" })` on `deliver` and `:command="deliver"`. It is the only form-then-question flow in ARV; the other `AlertDialog`s ask without inputs.
+
+### Fixed
+- **`StepForm` opens a step at its top.** It focused the step body on every step change without `preventScroll`, so a sheet on a phone scrolled the body into view and the progress went out of view (vehicle entry › Podaci o vozilu at 390). Focus now goes to the step with `preventScroll`, and when the form's top is scrolled out above its container (a sheet's body, else the page) it is brought back to the top; a page that shows its top does not jump. Next and Back alike. A refused Next still scrolls to and focuses the first field in error. ARV: none; the vehicle entry step at 390 is re-shot after adopting.
+
+### Changes to existing behaviour
+- **`StepForm` scrolls on a step change** when the form's top is out of view (see above), and focuses the step without scrolling.
+- **Pinned by tests that were updated:** none; no test pinned an old default.
+
+## 0.4.20 — 2026-10-10
+
+The notes from ARV's wave 2: what each ARV screen had to build by hand around the fields. Six items, one commit each.
+
+### Requires
+- go-core unchanged: **`v1.7.0`**; **`vue` 3.5.19 or later**.
+
+### Added
+- **`blur` and `focus` events** (the `FocusEvent`) on `TextField`, `NumberField`, `MoneyField`, `TextareaField`, `ComboField`, `DateField`, `DateTimeField` and `TimeField`: `<TextField @blur="check" />`. A typed date or time is committed first and a combo has put its chosen label back, so the listener reads what the field now holds. (`DateTimeField` emits for its date text; its clock input is part of the same control and does not.) `SelectField`, `MultiSelectField` and the other fields have none. ARV: `VehicleBasicSection.vue` (`vinEvents`), `VehicleEntrySection.vue` (`entryVinEvents`) and `arvvehicledefinition/components/VersionForm.vue` (`codeBlur`) bind `onFocusout` through `v-bind`; each becomes `@blur`.
+- **`blank-zero` on `NumberField` and `MoneyField`** (default off): a value of 0 reads as an empty field, editing and reading; the value stays 0 and what is emitted is unchanged. A 0 the user types stays visible while the field has focus and reads blank once it is left. ARV: the `blank()` / `asBlank()` helpers of `arvvehicledefinition/components/PriceRuleTab.vue` (costs and the calculator's four samples) and the offers of `used_vehicles/evaluations/views/Offers.vue` become `blank-zero` and are deleted.
+- **`#value` slot on `SelectField` and `ComboField`**: the chosen option's own content, `{ option }` typed like `#option`'s (with the `meta` the options carry; type `ValueSlotScope` exported from `@wssto2/vue-core/form`). A select replaces the chosen text with it, in the control (desktop and phone) and in read mode; a combo shows it before the text it keeps editable, and in read mode instead of the text. Only while an option is chosen; the placeholder is not the slot's. Default rendering unchanged. ARV: `VehicleBasicSection.vue` passes `VehicleColorSwatch` in `#option` only; the chosen colour gets the same in `#value`.
+- **`data-group` on `FormGroup`** (the group's name, on the section only; its Edit button is inside it): a spec finds a group's Edit with `[data-group=contact] [data-test=group-edit]`. ARV: `groupMark()` in `features/vehicles/utils.ts` and its `v-bind="groupMark('…')"` on the `FormGroup`s of `VehicleBasicSection.vue`, `VehicleCharacteristicsSection.vue`, `VehicleEntrySection.vue`, `VehicleRsPanel.vue`, `VehicleSiPanel.vue` and `VehicleStatusSection.vue` are deleted.
+- **Tests for colour contrast and touch size** (`src/tokens.test.ts`): the `--app-*` colour pairs (text, muted, destructive and brand on the four surfaces, on-tint, inverse, status tones on their surfaces, the nine category tones, control borders) meet WCAG AA in light and dark, computed from `theme.css` with no browser; the hit area and row are 44 px on touch and narrow screens, and Button (all sizes), SwitchField, PopupButton and DateButton carry `hit-target`.
+
+### Fixed
+- **Clearing a `NumberField` or `MoneyField` always emits `null`.** Two causes. On focus the formatted text (`120.00`) became the typed text (`120`) only on Vue's next render; Playwright's `fill("")` selects, focuses, and presses Delete, and the render collapsed the selection, so Delete cleared nothing and no update was sent (select-all + Backspace by hand worked). The text is now swapped in the focus handler, and the `select` event that follows a swap with the caret collapsed selects the text again (until the first key or pointer press). And `defineModel` drops an update equal to the value the parent passed, so a parent that shows a 0 as empty (`null`) never heard the clear; `NumberField` emits every change itself. A paste of nothing, a cut and Backspace were already emitting and are tested.
+
+### Changes to existing behaviour
+- **`NumberField` emits `update:modelValue` on every change of its text, including one equal to the value it was given** (it used `defineModel`, which dropped those). A parent that counts updates sees more of them; no ARV call site does (every `NumberField` / `MoneyField` is `v-model` or `form.bind`). `MoneyField` passes them on the same way.
+- **Declaring `focus` and `blur` means a listener bound with `v-bind` or `@blur` on these fields is now the component's event**; before, `blur` (which does not bubble) never reached it. ARV's `onFocusout` listeners are unaffected until moved to `@blur`.
+- **Pinned by tests that were updated:** none; no test pinned an old default.
+
+## 0.4.19 — 2026-10-10
+
+Pickers with rich rows in narrow columns, a date-time that stays inside its row on a phone, and a flag before a translation. Found moving ARV's vehicle and customer pickers onto the `#option` slot.
+
+### Requires
+- go-core unchanged: **`v1.7.0`**; **`vue` 3.5.19 or later**.
+
+### Added
+- **`row-layout?: "setting" | "stacked"` on `ComboField` and `SelectField`**, typed as on `SegmentedField`: `stacked` puts the control under its label at the row's full width (a picker in a ~230 px column), `setting` at the end of the row; without it the row is a label column and the control, as before. `MultiSelectField` is always stacked and has no option.
+- **`#prefix` slot on `TextField`**: an icon or image before the value, inside the control while editing and in front of the value while reading (not before "not entered"); `Field` has the same `prefix` slot for a control of your own. For a country's flag before its translation (ARV katalog › Verzija). The text `prefix` prop is unchanged. A decorative image takes `alt=""`; one that carries meaning brings its own `alt`.
+- **`OptionSlotScope` and `OptionWithMeta` are exported from `@wssto2/vue-core/form`**, the types an `#option` slot receives.
+
+### Fixed
+- **`DateTimeField` on a phone no longer runs past its row**: the capsule kept "12.10.2026. 10:00" on one line inside a button narrower than its text (about 33 px past the card at 390 with a long label). The date and the time are now two unbreakable words and the capsule wraps between them, right-aligned.
+
+### Changes to existing behaviour
+- **The list under a `ComboField` (and a `TextField` with `suggestions`) is at least 20rem wide** and never wider than the screen: the field's width when that is more, aligned to the field's start. On a phone (viewport under 640 px) it spans the screen minus an 8 px gutter, so `#option` rows keep their photo and badge; it stays a list under the input (a sheet would hide the text being typed). Before it was exactly as wide as the field. ARV call sites it touches (no code change; lists only get wider where the field was under 20rem): the 11 files with a `ComboField` (`lead/views/Vehicle.vue`, `offer/components/OfferVehicleSection.vue` and `OfferCustomerSection.vue`, `contract/components/ContractTradeInGroup.vue`, `lead/components/LeadModalImproved.vue`, `customer/components/CustomerCreateModal.vue`, `transportlist/components/DraftForm.vue`, `evaluations/components/EvaluationCustomerField.vue`, `vehicles/components/phase/DeliverSheet.vue` and `RecordSaleSheet.vue`, `used/takeover/views/PurchaseContract.vue`) and the `TextField :suggestions` of `lead/views/Customer.vue` and `customer/views/General.vue`.
+- **The `SelectField` and `MultiSelectField` popover is at least 20rem wide** (was 18rem; every ARV select, no code change). Phones keep the sheet.
+- **A stacked `ComboField` aligns its text left on a phone** (a field in a label column still aligns it right).
+- **`DateButton` text is right-aligned** (visible only when it wraps). ARV's `DateTimeField` call sites (`lead/views/General.vue`, `offer/components/OfferDetailsSection.vue` and the others) need no change.
+
+## 0.4.18 — 2026-10-10
+
+One record in a dialog, and selects whose options load that say they can come back empty. Found moving ARV's admin dialogs and vehicle forms.
+
+### Requires
+- go-core unchanged: **`v1.7.0`**; **`vue` 3.5.19 or later**.
+
+### Added
+- **`useRecordDialog({ defaults, validator, toValues?, create, update?, done? })`** (`@wssto2/vue-core/form`): the dialog that adds and edits one small record, on `useCommand` and `CommandDialog`. Returns `{ command, form, editing, create(), edit(row) }`. `create()` presents the defaults; `edit(row)` presents `toValues(row)` over them; `editing` is the row or `null` (the title, a field only a new record has, "Save and add another" via `#actions`, a delete button of an edit); a save calls `create(input, { idempotencyKey })` or `update(row, input, { idempotencyKey })` by it; `done(result, { editing })` is told which row was saved (`null` for a new one). The recipe "One record in a dialog" is rewritten on it (the wiring drops from about 30 lines to about 14).
+
+- **An `#option` slot on `SelectField`, `MultiSelectField` and `ComboField`**, `{ option, active, selected }`: it replaces what a row says (an icon, a photo, a badge, a VIN); the row, its check, keys and roles stay, and without the slot nothing changes. `TextField` suggestions are unchanged.
+- **`SelectOption<Value, Meta = undefined>` with `meta?: Meta`**: the row's own data, typed through `useOptions`, the three fields and the slot, so `#option="{ option }"` reads `option.meta.vin` without a cast. `Meta` is a new last type parameter of `SelectOption`, `AsyncOptions`, `OptionsSource` and `useOptions`; options without `meta` are `SelectOption<Value>` as before. Give every option a `meta` when the slot reads it (the slot's type says it is there). Recent choices of a `ComboField` keep their `meta` in the recents store.
+
+### Fixed
+- **A `DateField`, `DateTimeField` or `TimeField` in a narrow grouped row no longer runs past the card** (a date-time control in a half-width column overflowed by about 116 px): the popover's inline trigger wrappers now shrink (`max-w-full min-w-0`). `MonthYearField` shares the popover and fits too.
+- **The `FileField` dropzone reads "Izaberi datoteku ili prevucite datoteku ovdje"**, in every locale: the space between the two messages was lost by the template (it read "datotekuili prevucite").
+
+### Changes to existing behaviour
+- **`SelectField` with options from `useOptions` emits `Value | null`**, whatever `clearable` says (it clears a value the new options lack). Before it was typed `Value` unless `clearable`. A draft field bound to such a select must now be able to hold `null` (`make: null as string | null`); a field typed without `null` no longer compiles. A list of options and `clearable` keep the 0.4.15 rule. `SelectField` gained a third type parameter (`Source`, inferred from `options`). `ComboField` (always `Value | null`) and `MultiSelectField` (a list) already told the truth. No ARV call site passes `useOptions` today.
+
+## 0.4.17 — 2026-10-10
+
+Bosnian numbers and dates in every browser, and a command dialog whose primary action can wait. Found in ARV's Bosnian market on screens already moved to the library.
+
+### Requires
+- go-core unchanged: **`v1.7.0`**; **`vue` 3.5.19 or later**.
+
+### Changes to existing behaviour
+- **`bs` is formatted with `sr-Latn-BA` data.** Chromium (Chrome, Edge, Playwright) ships no Bosnian `Intl` data: it formatted `bs` as English (`400,000.50`, `BAM 1,234.50`, `2026 M10 10, Sat`, "Germany") while still reporting `bs`. Every `Intl` call in the library now goes through one internal function that gives `Intl` `sr-Latn-BA` for `bs` (`400.000,50`, `1.234,50 KM`, `oktobar 2026.`, "Njemačka") and every other locale unchanged: the default formatters (`date`, `dateTime`, `time`, `number`, `money`, `relative`), the calendar and date sheet (month and weekday names, first weekday), the `ResourceHeader` count, phone country names and search, and the language names on `I18nField` tabs (named in the UI language). A language's own name (`languageName`) still asks for `bs`. Nothing to configure; a custom `formatters` entry still receives the app's locale (`bs`). An application with its own `Intl` calls for `bs` can drop its workaround.
+
+### Added
+- `CommandDialog` **`confirmDisabled`**: while true the primary action is disabled and `run()` does nothing; the fields, Cancel and the leave guard work as before, and the primary works again when it clears.
+
+## 0.4.16 — 2026-10-09
+
+Bosnian and Serbian in the library's own words, a trailing slot on every field, and numbers as written. Found when ARV's dealer, location and follow-up forms moved onto the library.
+
+### Requires
+- go-core unchanged: **`v1.7.0`**; **`vue` 3.5.19 or later**.
+
+### Added
+- **`sr-Latn`: the library's Serbian** (ekavian, Latin script), every `core` key, registered beside `bs` in `coreMessages`. The default `locale.supported` is now `en`, `hr`, `bs`, `sl`, `sr-Latn`. Name the locale `sr-Latn` (a bare `sr` prints Cyrillic) and `bs`, not a market code (`ba`, `rs`). Before, an application that listed `sr-Latn` showed the `fallback` language's library texts; now it shows Serbian.
+- **`#trailing`, `#labelTrailing` and `#readonly` on every field**, as `Field` has them: `TextField`, `TextareaField`, `NumberField`, `MoneyField`, `SelectField`, `MultiSelectField`, `ComboField`, `SegmentedField`, `ChoiceChips`, `CardSelectField`, `SwitchField`, `DateField`, `DateTimeField`, `TimeField`, `MonthYearField`, `FileField` (`PhotoField` and `I18nField` pass the ones they do not use themselves). Until now every field swallowed them, so a per-row Save beside a select was not possible. Typed as `FieldSlots` (`@wssto2/vue-core/form`).
+- `NumberField` **`minDecimals`**: the fraction digits always shown, at most `decimals` (default `decimals`, so an amount still reads `1.50`). `:decimals="7" :min-decimals="0"` reads `43.566139`, not `43.5661390`.
+- `NumberField` **`mono`**: the monospaced face of `TextField mono`, editing and reading.
+
+### Changes to existing behaviour
+- **The `bs` texts are Bosnian**: 70 of 688 values changed, to the words ARV's own Bosnian screens use (`Sačuvaj`, `Nesačuvane promjene`, `Izaberite…`, `Ova sedmica`, `Obavještenja`, `ovlaštenja`, `opseg`, `Popis`). Keys, placeholders and `|` counts are unchanged. An application that overrode a key to say the Bosnian word is unaffected; one that pins a Croatian word in a `bs` test is not.
+- **A `Field` on its own renders `#trailing`** beside the control (it used to render it only in a group's row).
+- The language tab of an `I18nField` for `sr-Latn` reads `SR-LATN`.
+
+## 0.4.15 — 2026-10-09
+
+Six gaps in forms, found when the first two ARV forms moved onto the library.
+
+### Requires
+- go-core unchanged: **`v1.7.0`**; **`vue` 3.5.19 or later**.
+
+### Added
+- `SelectField` without `clearable` emits `Value`, not `Value | null`, so a draft field typed `1 | 2 | 3` binds to it (a second generic, `Clearable`). With `clearable` it still emits `Value | null`. It still takes `null` as the value it is given.
+- `labelHidden` on every field: the label stays the control's accessible name (and the read row's) but is not drawn, and the row lays out without a label column.
+- `NumberField` `maxDigits`: the most digits the field takes (fraction digits count; sign, separators and decimal mark do not). A digit past the limit is not accepted; a pasted longer number keeps its first digits.
+- `useSaveChrome`: `disabledWhileClean` (default `true`), and `cancel` is optional (without it there is no Cancel).
+- `useHiddenFieldErrors({ form, root })` returns the errors whose field is not on screen, as `ComputedRef<readonly { field, message }[]>`. `FormErrors` uses it.
+- `createApplication({ describeFieldError })`: the application's one sentence for a server field message, `(message, field) => string`, asked by every `useForm`, `useResourceForm` and `useCommand` that has none of its own. Without either, messages show as sent.
+
+### Changes to existing behaviour
+- **`useSaveChrome` disables Save while the form has no changes.** `EditorPage` and the new-role editor pass `disabledWhileClean: false` (a create page submits an untouched form to learn what is missing); the user's General section and an edited role start with Save disabled.
+- **The form option `translate` is renamed `describeFieldError`**, to match the application's. `useServerMessages()` returns `describeFieldError` instead of `translate`.
+
+## 0.4.14 — 2026-10-09
+
+An app can say its own error sentences once, and a load can be abandoned.
+
+### Requires
+- go-core unchanged: **`v1.7.0`**; **`vue` 3.5.19 or later**.
+
+### Added
+- `createApplication({ describeError })`: the app's own sentence for an error, asked before the library's. `useDescribeError` and the default failure text of `useLoad` and `useResource` all use it. Return `undefined` to leave an error to the library. This is for error types the library does not know, such as an older HTTP client's.
+- `useLoad`'s context has `abandon()`. It ends the load with nothing to show and no error, for a page that is leaving instead (a 403 that redirects). The state stays as it was.
+
+### Changes to existing behaviour
+- None without `describeError`.
+
+## 0.4.13 — 2026-10-08
+
+A record can open on its own hub.
+
+### Requires
+- go-core unchanged: **`v1.7.0`**; **`vue` 3.5.19 or later**.
+
+### Added
+- `SectionNavigator` takes `desktop="hub"` and `compact="hub"`. This is for a workflow record whose first section already leads to the others (its to-dos, each a row into a section). The navigator shows no navigation, every other section gets a back link to the first, and a long form in a section lists its own sections beside it on wide screens. The summary shows on the first section only, as with drill-in rows.
+
+### Changes to existing behaviour
+- None.
+
+## 0.4.12 — 2026-10-08
+
+Back to the list keeps the user's place in more cases.
+
+### Requires
+- go-core unchanged: **`v1.7.0`**; **`vue` 3.5.19 or later**.
+
+### Added
+- `useCollectionBack(definition, { list, backLabel })`: back to the list a record was opened from, with the list's state from `?from=`, for a record page without a pager. It asks nothing of the list. Pass it as `ResourcePage`'s `list`.
+
+### Fixed
+- `useCollectionNeighbors` led back to the plain list when the record was no longer in it (sold, removed, filtered out), dropping the user's page, filters and sort. Back now keeps the state the record was opened with.
+
+### Changes to existing behaviour
+- `listRoute` is set as soon as the state is read, also when the record is not found; it stays null without list state.
+
+## 0.4.11 — 2026-10-08
+
+A record page can say what a missing record means.
+
+### Requires
+- go-core unchanged: **`v1.7.0`**; **`vue` 3.5.19 or later**.
+
+### Added
+- `ResourcePage` takes a `#not-found` slot. It replaces the generic not-found state (404 or an invalid address) where a missing record means something, such as a vehicle sold or given to someone else, and offers the way on. Without the slot nothing changes.
+
+### Changes to existing behaviour
+- None.
+
+## 0.4.10 — 2026-10-07
+
+The record pager follows the page to another section.
+
+### Requires
+- go-core unchanged: **`v1.7.0`**; **`vue` 3.5.19 or later**.
+
+### Fixed
+- `useCollectionNeighbors` built each neighbor's `to` once, from the route when the neighbors resolved. After the page moved to another section (or hash) of the same record, previous and next still linked to the section it was opened on. `to` now reads the current route.
+
+### Changes to existing behaviour
+- None, apart from the fix.
+
+## 0.4.9 — 2026-10-07
+
+A cell slot a page adds after the first render now shows.
+
+### Requires
+- go-core unchanged: **`v1.7.0`**; **`vue` 3.5.19 or later**.
+
+### Fixed
+- `DataTable`, `CollectionTable` and `CollectionPage` read their slots once, on the first render, and passed only those on to the rows. A `#cell-<key>` slot the page adds later (a column added while editing, one slot per line with `v-for`) never rendered. They read them on every render now.
+
+### Changes to existing behaviour
+- None, apart from the fix.
+
+## 0.4.8 — 2026-10-07
+
+A list you pick from: `pick` mode on the collection's table, for modals that assign or select.
+
+### Requires
+- go-core unchanged: **`v1.7.0`**; **`vue` 3.5.19 or later**.
+
+### Added
+- `pick?: (row) => void` on `CollectionTable`, `CollectionPage` and `DataTable`, and `pickLabel?: string` (the choices' accessible name, default "Choose one"; `core.collection.pick_label` in `hr`, `bs`, `sl`, `en`). Instead of `recordRoute` and the open-record link: a row is a choice or a link, never both.
+  - **Pointer:** a click or tap anywhere on the row picks it; a button or link inside the row keeps its own click (as in record rows). Hover and press are visible. Row actions still work if the caller gives them; otherwise there is no long press and no swipe.
+  - **Keyboard:** the rows are one listbox with one tab stop. Down and Up (Home, End) move the current row, which shows the focus ring; Enter or Space picks it. In the search field, Down moves into the rows, and Enter picks the only row when exactly one is shown (the list loaded, the search applied, no further page); with none, several, a pending search or a loading list it does nothing. Escape is not handled: the dialog closes as usual.
+  - **ARIA:** `role="listbox"` (named) with `role="option"` rows and `aria-activedescendant`, on the table (the table itself is `presentation` while picking) and on the phone rows.
+- Recipe "Picking a row" (`docs/recipes/list-page.md`); playground `/customers/pick`, a picker dialog with a search.
+
+### Changes to existing behaviour
+- None: a list without `pick` renders and behaves as in 0.4.7.
+
+## 0.4.7 — 2026-10-06
+
+An empty list under its own start says what it is empty for and offers the way out.
+
+### Requires
+- go-core unchanged: **`v1.7.0`**; **`vue` 3.5.19 or later**.
+
+### Added
+- The library's empty state under a `useCollection` start: when `display` is `"empty"`, the list has no `#empty` slot and starting filters (`defaults.filters`) still apply, it reads "No data" and "Showing only: Location: Zagreb - Jankomir" (the filters named as the toolbar chip names them) and offers one **Show all** button. On desktop and phone; `hr`, `bs`, `sl`, `en` (`core.collection.empty.start_description`, `show_all`).
+- `Collection.startFilters` (`ComputedRef<readonly Filter[]>`): the starting filters that still apply (a filter the user changed or cleared is not listed), and `Collection.clearStart()`: clears exactly those and keeps the search, other filters, view and sort. Not `reset()`, which would bring the start back. A consumer's `#empty` slot can offer the same action (see the list recipe).
+- Playground `/customers/local`: a toggle to drop the page's own `#empty` slot and show the library state.
+
+### Changes to existing behaviour
+- Only the empty state of a list that has `defaults.filters` and no `#empty` slot changes (it was "No data / No results found for your search."). A list without `defaults`, a list with an empty start, a list with its own `#empty` slot, and `no-matches` are unchanged.
+
+## 0.4.6 — 2026-10-06
+
+A list's own starting values: the state it opens on and that Reset returns to, which is not a search the user ran.
+
+### Requires
+- go-core unchanged: **`v1.7.0`**; **`vue` 3.5.19 or later**.
+
+### Added
+- `useCollection` option `defaults?: { filters?, search?, view?, sort?, direction? }`, typed by the definition's keys, each field given replacing the definition's own `defaults` field. It is the state the list starts from when the URL (or a saved view without that field) holds none, and the state `reset()` returns to. The starting filter is sent to the backend like any filter. A URL with an explicit state, and `linked` params (`"any"` clears a starting filter), win over it. It is checked against the query contract like the definition's defaults (a filter or sort the contract does not list throws at creation).
+- `isFiltered`, and so `display`, count a filter or the search as narrowing only when it differs from the use's `defaults`: a list that opens on the user's own location and has nothing there is `"empty"` (the `#empty` first-use content), and becomes `"no-matches"` only after the user changes the filter or searches. A cleared starting filter shows everything and does not read as a search. A view never counted.
+- The URL state is written so it reads back the same with and without the start (a record page's `?from=` is decoded against the bare definition): a field either side defaults is written even when the user emptied it (`f` as `{}`, `s` as `""`, `w` as `""`).
+
+### Changes to existing behaviour
+- A list without `defaults` behaves exactly as in 0.4.5; the definition's own `defaults` still count as narrowing. One internal difference: with `display` `"empty"`, `CollectionTable` no longer draws the no-results chips (nothing could be narrowing then before, so nothing changes without `defaults`).
+- **API change:** `useDatePresetFilter(key, label?)` returns a `ComputedRef<FilterDescriptor<Filter>>` instead of a descriptor, and `label` is a `MaybeRefOrGetter<string>`. It takes `t` from `useI18n()` at setup, and the label and option labels follow the locale (a `label` getter such as `() => t("…")` follows it too). Call it once at setup and put `.value` in the computed: `const created = useDatePresetFilter("created_at"); const filters = computed(() => [created.value, …]);`. Callers add `.value` (arv-next's lists do).
+
+### Fixes
+- The `useDatePresetFilter` doc comment (and the list recipe, and the playground) told callers to call it inside the `filters` computed. It uses `useI18n`, which exists only during setup: it threw when the computed ran again, and options that load later never appeared. Call it once at setup. Calling it once, though, left the labels in the old language when the user changed language while a list was open, so it is now reactive (below).
+
+## 0.4.5 — 2026-10-06
+
+The quiet row tile, a phone row subtitle that is a subtitle, and a status dot in a filter option.
+
+### Requires
+- go-core unchanged: **`v1.7.0`**; **`vue` 3.5.19 or later**.
+
+### Added
+- `IconTile` `weight="soft"` (default `solid`, so nothing existing changes): a light tint of the tone with its glyph and a hairline ring instead of the solid fill, light and dark. `brand` uses new tokens (`--app-tile-brand-soft`, `--app-tile-brand-soft-foreground`, derived from the primary palette, so a re-brand follows); `anchor` is the soft brand tint with the link colour, `neutral` the fill with the muted colour. The recipe for a list says a `#leading` slot is `<IconTile weight="soft" size="sm" icon="…" />`.
+- `IconTile` `size="sm"`: 32 px (`size-8`), the leading tile of a list row. `row` is unchanged (22 px desktop, 29 px compact): it is the metric of grouped rows and navigation.
+- `FilterOption.dot?: Tone`, `MenuItem.dot?: Tone` and `SelectOption.dot?: Tone`: a small status dot (a tone of the status roles, `positive` = success, `warning`, `critical`, `info`, `neutral`) before the label, in the toolbar filter menu and the capsule of the applied option, the desktop filter panel's select (list and trigger), and on phones the chips, the drill-down rows and the row that names the chosen option. Options merged by `dependsOn` keep the first one's dot. The applied-filter tokens that list a panel filter's value stay text.
+
+### Changes to existing behaviour
+- The phone row (`CollectionRows`, columns with `mobile` roles `primary` and `accessory`): when the primary column is a standard `identity` cell (no cell slot), the accessory sits beside the title only; the subtitle is regular weight (it inherited the title's semibold through the row's wrapper) and muted, and runs under both on the full width, ending in an ellipsis only at the card's edge. A primary column with a cell slot, a non-identity primary column, and several primary columns lay out as before. `text-row-subtitle` is now explicitly `font-normal`. The desktop table and `RecordIdentity` on its own are unchanged (`RecordIdentity` gains `spread`, used by the phone row).
+
+## 0.4.4 — 2026-10-05
+
+Back to a list returns focus to the row you left from, also when the list keeps its state in the URL.
+
+### Requires
+- go-core unchanged: **`v1.7.0`**; **`vue` 3.5.19 or later**.
+
+### Fixes
+- `AdaptivePageShell` (and so `CollectionPage`) remembered the focused link under the URL the page had when it mounted. A list that keeps its state in the query rewrites the URL right after mounting (`/customers` → `/customers?query=…`), so Back from a row never found the memory: the row lost its focus. The memory is now kept under the URL the page shows when it goes away; query changes on the same route are followed, the navigation that leaves the page is not.
+
+## 0.4.3 — 2026-10-05
+
+A plain toast, and a typed `onDismiss`.
+
+### Requires
+- go-core unchanged: **`v1.7.0`**; **`vue` 3.5.19 or later**.
+
+### Added
+- `toast.message(message, options?)`: the plain toast, no status icon, for a neutral fact usually with an action (`toast.message(t("filterDeleted"), { action: { label: t("undo"), onClick: undo }, onDismiss: commit })`). `success`, `info`, `warning`, `error` and `loading` keep their icons.
+- `ToastOptions.onDismiss(id)`, on every toast kind: runs when the user swipes the toast away (or closes it, where a close button is shown). It does not run when the toast times out, when its action is pressed, or when code calls `toast.dismiss(id)`. It receives the toast's id (Sonner itself passes the whole toast).
+
+### Fixes
+- `keepSessionAlive` no longer reads the session back after a `renew` that ended it. An app that expired the session on a refused refresh was signed straight back in by that read (the access token was still valid), and the new session renewed at once: arv-next called `/auth/me` and `/auth/refresh` every ~150 ms until the access token ran out or the rate limiter answered 429. A `renew` that leaves the session signed in is read back as before.
+
+## 0.4.2 — 2026-10-05
+
+A checked menu item now shows its tick.
+
+### Requires
+- go-core unchanged: **`v1.7.0`**; **`vue` 3.5.19 or later**.
+
+### Changes to existing behaviour
+- A `Menu` item with `checked: true` draws a tick (the same one the account menu uses for its selected row) at the trailing end, after the label and before a `shortcut`; on phones it sits at the trailing end beside the icon. Unchecked items reserve nothing. The role stays `menuitemradio` with `aria-checked`; the tick is `aria-hidden`. This shows the current choice in every `CollectionFilterMenu` and in a location switcher built on `Menu`.
+
+## 0.4.1 — 2026-10-05
+
+Shell fixes for the arv-next cutover: a search place in the shell, pull to refresh, and the dev-mode readonly warnings gone.
+
+### Requires
+- go-core unchanged: **`v1.7.0`**.
+- **`vue` 3.5.19 or later** (peer, was 3.5.0). Before 3.5.19 Vue wrote the element into the readonly ref `useTemplateRef` returns, so every first mount of a dev build logged `Set operation on key "value" failed: target is readonly` (about ten times in the shell, once at a sign-in route). Upgrade `vue` to clear them.
+
+### Added
+- The shell's `search` slot: a contribution `{ slot: "search", component }` renders at the top of the sidebar, under the brand, and at the top of the phone drawer. Nothing contributed, nothing rendered. `backofficeShell()` offers it; a custom shell lists `"search"` in its `slots` and renders `<ShellOutlet name="search" />`, or marks the contribution `optional`.
+- `useOptionalPageChrome` is exported from `@wssto2/vue-core/page` (the page chrome, or `null`, for a component that may be mounted without the application, e.g. in a unit test).
+
+### Changes to existing behaviour
+- Pull to refresh is on in `BackofficeShell` whenever the application runs installed (`display-mode: standalone`, or iOS `navigator.standalone`): pulling down from the top of the page reloads the page only (the shell's page outlet remounts; the sidebar, top bar, drawer and open popovers stay). Vertical downward drags from the scroll top only; never with a dialog or the drawer open; threshold 72, resistance 0.5, the indicator spins at least 600 ms, reduced motion keeps it still; unsaved changes ask first. Turn it off with `backofficeShell({ pullToRefresh: false })`. An application that had its own pull to refresh should remove it.
+- The readonly warnings above are gone with the `vue` peer bump; no source change.
+
+## 0.4.0 — 2026-10-04
+
+The screens for go-core's notification module (in-app notifications, e-mail settings and quiet hours) and the failed events of its event queue. Built and checked against go-core `v1.7.0`.
+
+### Requires
+- go-core **`v1.7.0`** or later on the server (`package.json` `"goCore"`); the committed module types are now written by it (`src/modules/notification`, `src/modules/events`; identity and access are unchanged). `Item.category` is a plain string; `GET /v1/events/consumers` needs `events.deadletter:view`.
+
+### Notifications (`/notifications`, new)
+- `notificationsFeature({ categories?, deadLetters?, settings? })`: the bell in the shell's `headerActions` (unread count, `99+`), the inbox it opens (a popover on wide screens, a bottom sheet on phones: newest first, "Show older" by `before_id`, unread marked, relative time, a category icon and hue; a tap marks the notification read and opens its link through the router; "Mark all as read" sends the newest id the inbox shows, so one that arrives meanwhile stays unread) and the live stream behind it. The stream is read with `fetch` through the session's cookies, reconnects with a 1 s to 30 s backoff after refetching the count, drops a connection silent for two heartbeats, catches up when the page returns to the foreground or the network returns, and is ended and cleared with the session (sign-out, expiry, signing in as somebody else).
+- The failed events page (`/events/dead-letters`, route `events.deadletters`, `events.deadletter:view`): the dead letters of every consumer with a consumer filter and paging; "Retry" and "Retry all for this consumer" (after a question) behind `events.deadletter:retry`. `deadLettersRoutes`, `notificationRoutes`, `eventsRoutes` and the wire types are exported; `deadLetters: { destination }` binds the menu, `deadLetters: false` leaves the page out.
+- Notification settings (`settings`, default true): the page `/profile/notifications` (route `notifications.settings`, target `notificationSettingsRoutes.index`) for any signed-in person, from the account menu ("Notification settings") and from a gear in the inbox (beside the close button in the sheet's header on phones). "E-mail me about": a switch per category go-core lists, saved as it is switched (at once, taken back with a message when refused); a setting someone else enforces is a locked row, "Set by your organisation"; without e-mail on the server one sentence and no switches; in-app listed as always on. Quiet hours: on or off, from and to (`TimeField`), a line in words with the server's time zone, over midnight allowed, equal times refused on the field. The names of the categories are the application's texts `notifications.categories.<code>.label` (and `.description`), the code split at its dots, falling back to the code. `settings: false` leaves the page, the entry and the gear out.
+- The "Consumer" filter of Failed events is a choice among the consumers `GET /v1/events/consumers` lists (a text field if they cannot be read).
+- Texts `core.notifications.*`, `core.notifications.settings.*` and `core.notifications.dead_letters.*`, and go-core's reasons `core.errors.notification.*`, in en, hr, bs, sl. Playground: `identity.html` has the bell and "Send a test notification". Recipe "Notifications".
+- Core icons `notification3Line`, `checkDoubleLine`, `settings3Line` and `moonLine`.
+- `Sheet` has an `actions` slot: buttons in its default header, just before the close button.
+
+### Changes to existing behaviour
+- `defineCollection({ query: { search: false } })` leaves the search field out of the toolbar (`collection.searchable`); the default is unchanged.
+- The desktop sidebar is stacked above the page toolbar (`z-30`), so a popover opened from the rail is not painted under the page.
+- A context menu that closes while it is being positioned no longer throws (`Menu`).
+
+## 0.3.0 — 2026-10-03
+
+The screens for go-core's identity and access modules: sign-in, the session-expiry prompt, impersonation, users and "my profile", a person's activity, roles and access; and typed routes on the HTTP client. Built and checked against go-core `v1.6.0`.
+
+### Requires
+- go-core **`v1.6.0`** or later on the server (`package.json` `"goCore"` names the version the committed module types come from).
+- `zod` is an optional peer dependency: only needed when you use the generated input schemas.
+
+### Changes to existing behaviour
+- `HttpClient` gained `request(route, input)`: a hand-written `HttpClient` implementation must add it.
+- `createPlatform({ renewSession })` is called with the platform's client as a second argument (`(session, http) => …`); one-argument functions keep working.
+- A custom shell must render `<ShellOutlet name="banner" />` (the impersonation strip) and keep a `host` slot to use `identityFeature`; it fails at start-up otherwise. `backofficeShell()` has both.
+- `identityPlatform({ parseUser })` needs the user to keep a `login` (the session-expiry prompt shows it).
+- An expired session can now be held on its page (`defineFeature({ holdsExpiredSession })`); apps without such a feature behave as before.
+
+### Identity and access (`/identity`, `/access`, new)
+- go-core's module contracts, committed under `src/modules/` (`cmd/modulets`): entity types, input types (`Inputs.*`, types only) and the route tables `identityRoutes` / `accessRoutes`. `npm run modules:sync -- <go-core checkout>` rewrites them; `npm run check:modules` (part of `npm run check`) fails on another go-core version than `package.json` `"goCore"` or a hand edit. `zod` is an optional peer dependency (the declarations of the input types name it).
+- `identityFeature({ home? })`: the sign-in page at `/login` (route `login`; required fields, generic failure, the lock with the time it ends, 429), session upkeep (`keepSessionAlive`), and the person's language kept in step with the server (the saved language applied when the session begins, a language chosen in the account menu saved with `change-locale`).
+- `identityPlatform({ parseUser? })`: `createPlatform({ config, ...identityPlatform() })` wires the session to `/v1/auth/*` (read `me`, with one refresh when the access token ran out; sign-out) and the refresh on a 401. `signIn`, `lockedUntil`, `identitySessionAdapter`, `renewIdentityTokens`, `parseIdentityUser` for applications with their own page. Checked against go-core's session payload fixture.
+- Texts: `core.identity.signin.*`, `core.errors.identity.*` (signin failed / locked / inactive, session invalid, locale invalid, impersonation disabled, account not found / inactive) in en, hr, bs, sl.
+- Playground: `identity.html` signs in against go-core's dev server (`go run github.com/wssto2/go-core/cmd/devserver`, Vite proxies `/api`). Recipe "Sign-in".
+- The session-expiry prompt (`docs/design/SessionExpiry.dc.html`): a session that expires while someone works stays on its page; a dialog (wide screens) or bottom sheet (phones) asks for the password with the login fixed, drafts survive, Escape does nothing, "Sign out instead" asks the unsaved-changes question first. Not held when the session was an impersonation. Behind it: `defineFeature({ holdsExpiredSession })`, `session.holdExpired(enabled)` (set by `createApplication`), `heldSession(state)` and `previous` on the anonymous/expired state (`/platform`); the shell, menu, navigation and permissions follow the held session; `installRouterGuards({ holdExpired })`.
+- Impersonation (`docs/design/Impersonation.dc.html`): `SessionSnapshot.impersonator` (`{ id, name }`, read from go-core's payload); a warning strip in the new `banner` shell slot, sticky at the top (the sidebar, top bar, page toolbars and side navigators start below it through `--shell-banner-h`) ("Return to my account" calls `login-as/return`, then home; not dismissible); `SignInAsButton` (only with the permission you name, never for oneself or while impersonating); `signInAs`, `returnToOwnAccount`. Custom shells render `<ShellOutlet name="banner" />`; `identityFeature` fails at start-up in a shell without a `banner` or `host` slot.
+- `src/modules` contains no `any`, so it is linted like the rest.
+- `identityPlatform({ parseUser })` needs the user to keep a `login` (the expiry prompt shows it).
+
+### Users and "my profile" (`/identity`)
+- `usersFeature({ people?, profile?, signInAs?, destination?, sections? })`: the users list (`/users`: views active / locked / inactive / all, search, sort, paging, state in the URL, "New user") and a person's record (`/users/:id`: details edited in place, sign-in with the lock / unlock / new password / `SignInAsButton`, sessions, sign-in history, changes with before and after; deactivate with confirmation and the reason of the application's hook, activate), and "my profile" (`/profile`: name and phone, password, e-mail change by code with `OtpInput`, resend with the server's cooldown, resume or cancel; own sessions with this device marked; own sign-ins; an account-menu entry). Every screen and action is behind the permission go-core checks; `people: false` / `profile: false` leave a part out, `destination` binds the list to the menu, `sections` adds sections of the application's own to the record (a `PersonSection`: child route, `props` from the person, route meta). Typed targets `usersRoutes`, `profileRoutes`. Server field errors land on the fields, forms guard unsaved changes, refusals are said in words: `core.errors.identity.*` (all of go-core's reasons for these routes) in en, hr, bs, sl. Texts `core.users.*`, `core.profile.*`, `core.account.*`.
+- Activity section on a person's record (`iam.user.activity:view`, go-core `GET /v1/iam/users/:id/activity`): area tabs with the server's counts, a date range, rows by day, the "signed in as" mark; `usersFeature({ activityAreas })` names the application's areas.
+- New core icons (`listCheck`, `user3Line`, `key2Line`, `deviceLine`, `timeFill`, `edit`, `lockLine`, `checkCircle`, `addLine`, `mailUnreadFill`, `eyeOff`).
+- Playground: `identity.html` shows both sides against go-core's dev server. Recipe "Users and profile".
+- History rows carry `{ id, name }` (`PersonRef`) as `actor`, `opened_by`, `signed_in_as`; the screens show those names (empty name, a deleted person, reads "somebody else") and `useActorNames` with its per-person lookups is gone, so "my profile" names who signed in as the person too. `ListResult.meta.views` is typed `readonly ViewCount[]` (`{ key, count }`, `ViewCount` exported from `/client`): the users list, activity, sign-in and changes tabs read their counts with no cast. New tabs with counts: sign-ins **All / Failed** (record and "my profile"), changes **All / Access / Details**; the `view` input is a typed enum (invalid: 422 `identity.list.view_invalid` / `identity.history.view_invalid`).
+
+### Roles and access screens (`/access`)
+- `accessFeature({ catalogue, subjectRoute?, scopes?, destination? })`: the roles list (`/iam/roles`, kinds and search), a role's page with the editor, holders, *Copy* (`/iam/roles/new?copy=`), *Compare with a predefined role*, *Replace* (its holders move; all or none) and *Delete* (its own permission), a new role. The permission tree is the application's `authzts` catalogue: modules as tabs, screens as groups, requirements kept consistent (a role that lacks what its permissions need is completed on load, with a note), *whose* held once per record type, sensitive / system / whole-organization marks. Pages and actions behind `iam.role:view|manage|delete` and `iam.user:view|manage`; typed targets `accessPages`.
+- `PersonAccess` (a person's roles with *Add role* and *Remove*, and *What {name} can do* with *Why*), `BindingRow`, `personRolesSection` (the `meta` for a record section). *Add role* reads the places from the server (`/scopes`), derives the hierarchy from them (no level names in the library), asks level and place only where the hierarchy has levels, and lists the roles the actor may give there; with one level it asks nothing, and the root level is the `root_level` the server reports.
+- `authz.*` refusals in words in en, hr, bs, sl (`core.errors.authz.*`, overridable with `errors.authz.*`): `useRefusalMessage()` for a form's `failureMessage`.
+- Texts under `core.access.*`; the application supplies a permission's label (its catalogue's keys), `access.modules.*`, `access.resources.*`, `access.ownable.*`, `access.roles.<key>`, `access.levels.*`. Icons `shieldStarFill`, `addLine`, `swapBoxLine` join the library's own.
+- Playground: `identity.html` edits roles and binds them to people against go-core's dev server. Recipe "Roles and access".
+
+### Client (`/client`)
+- `route<In, Out>(method, path, options?)` and `route.raw(...)`: plain typed route values, the shape go-core's generator emits (`permission`, `public`). Raw routes (streams, files) keep method and path for links and are not callable through `request`.
+- `client.request(route, input, options?)`: `:params` filled from `input` (encoded), the rest the query for GET/DELETE and the JSON body for POST/PUT/PATCH; resolves to `ApiResult` as `get`/`post` (`data: null` for a `void` route). A missing path parameter throws a plain `Error` naming the route, before sending. Path parameters are checked by go-core, not by TypeScript.
+- `ListResult<Row>`: the wire type of go-core's datatable result; `readListPage` (`/collection`) takes it with `Row` inferred.
+- Recipe "Typed routes". Type fixtures from go-core's generated route tables in `test-data/go-core` (go-core 727a37b), run by `npm run typecheck:fixtures` (adds `zod` as a dev dependency).
+
+## 0.2.0 — 2026-10-02
+
+What arv-next needs before it can switch to the library. Additions only; nothing public was removed or renamed.
+
+### Forms (`/form`)
+- `useOptions({ for, load })`: select options that load from the server. `SelectField` and `MultiSelectField` take them in `options`: a spinner in the field while loading, a "Loading…" row, a failed row with "Try again", the latest input wins (older requests are aborted). A value is cleared only when options arrive for a different input (the user picked another make), never on the first load, so an edit form keeps a saved value the list no longer offers.
+- `selected` on `SelectField` / `MultiSelectField`: the label of the current value before the options arrive.
+- `NumberField :grouping="false"`: no thousands separator (years, coordinates).
+- The select list is at least as wide as its field (`Popover` `matchTriggerWidth`).
+- `CommandDialog` `#actions` slot and `run({ addAnother: true })`: save and add another. Recipe "One record in a dialog (create and edit)".
+
+### App, state and shell
+- `AccessGate` (`/platform`): shows its content only when the user holds `permission`, `any` or `all`; `#fallback`.
+- `useLoad(load, { watch })` (`/state`): one load with latest-wins, `reload()`, `update(value)`; pairs with `AsyncSection`.
+- `useDescribeError()` (`/i18n`): an `ApiError` (or any error) as a sentence for the user; app `errors.<code>` keys win over `core.errors.*`.
+- `useOpenDialogCount()` (`/overlay`), `modalPlacementKey` and `Modal` `placement` (`/modal`): for an app shown inside another page's frame.
+- Keyboard shortcuts take `group` and `label`; `useShortcutRegistry()`, `shortcutKeys()` (`/button`) and the `ShortcutHelp` "?" dialog (`/modal`). The library's own shortcuts are listed.
+- `createApplication({ locale: { flags } })`: the language menu shows a flag and the language's own name.
+- `Badge hue="…"`: nine category colours (amber, lime, teal, cyan, blue, indigo, violet, fuchsia, pink), separate from the status tones, AA contrast in light and dark; tinted or `appearance="dot"`.
+
+### Tables (`/collection`)
+- `DataTable`: a table over an array (no fetching, paging or URL state), built from the same parts as `CollectionTable`, with phone rows for columns that have `mobile` roles.
+- `RowActions`: the row's action buttons from the same `RowAction[]` as swipe and the context menu.
+
+### Testing (`/testing`, new)
+- `createTestPlatform`, `createTestApp`, `withSetup`, `stubRoutes`, `scriptedTransport`, `routedTransport`, `jsonResponse`, `fakeLoader`, `listPage`, `createTestI18n`, `testFormatting`, `settle`, `deferred`, `mockMedia`. No test-runner dependency. Recipe: `docs/recipes/testing.md`.
+
+## 0.1.0 — 2026-10-01
+
+First release: shell, routing, permissions, lists, record pages, forms and fields, dates and times, phone numbers, suggestions, per-language text, photo viewer, step forms.

package/dist/{Activity-DX-RK9xj.js → Activity-Cu_mAn_m.js}

@@ -6,7 +6,7 @@ import { u as O } from "./format-D8X4zsx6.js";
 import { _ as U } from "./DateField.vue_vue_type_script_setup_true_lang-CpuH0WTl.js";
 import { _ as T } from "./FormGroup.vue_vue_type_script_setup_true_lang-DSwSRsA5.js";
 import { e as z } from "./control-B4SdblL6.js";
-import { P as G, c as H, i as J } from "./index-DiEoRV9D.js";
+import { P as G, c as H, i as J } from "./index--CxZ33h0.js";
 import { u as K } from "./platform-q3cjODLx.js";
 import { b as M } from "./routeResource-DlTsGTg_.js";
 import { _ as Q } from "./AsyncSection.vue_vue_type_script_setup_true_lang-Blj6KgCr.js";

package/dist/{Changes-_nARQ9IC.js → Changes-DW_3-MwX.js}

@@ -1,6 +1,6 @@
 import { defineComponent as k, computed as N, openBlock as n, createBlock as u, unref as a, withCtx as g, createElementBlock as p, Fragment as _, renderList as $, createElementVNode as i, toDisplayString as h, createCommentVNode as C, ref as x, watch as b, createVNode as y } from "vue";
 import { useI18n as E } from "vue-i18n";
-import { P as V, i as R } from "./index-DiEoRV9D.js";
+import { P as V, i as R } from "./index--CxZ33h0.js";
 import { u as S } from "./platform-q3cjODLx.js";
 import { b as B } from "./routeResource-DlTsGTg_.js";
 import { _ as F } from "./AsyncSection.vue_vue_type_script_setup_true_lang-Blj6KgCr.js";

package/dist/{DeadLetters-O6QReswO.js → DeadLetters-CpcMccCc.js}

@@ -4,7 +4,7 @@ import { a as k } from "./error-CD7x0Jrz.js";
 import { u as V, _ as N } from "./CollectionPage.vue_vue_type_script_setup_true_lang-BNM_cbXa.js";
 import { u as P } from "./describeError-B-NMa--w.js";
 import { u as I } from "./format-D8X4zsx6.js";
-import { e as a, R as O } from "./index-D-0JNiFF.js";
+import { e as a, R as O } from "./index-DBTK_iMB.js";
 import { _ as W } from "./AlertDialog.vue_vue_type_script_setup_true_lang-whA4WLdl.js";
 import { t as i } from "./toast-CqSDTWRX.js";
 import { u as Y } from "./useLoad-M7V-AVwR.js";