bitboss-ui 3.0.0-beta.48 → 3.0.0-beta.49

package/dist/ai/composables/useBbDropdownContext.md

@@ -16,7 +16,7 @@ selected option, without template refs and without being in the dropdown's
 subtree.
 
 The point is chips and summaries **without a twin fetch**: the dropdown already
-resolved a pick's text when the user chose it, so `selectedOptions` hands it
+resolved a pick's label when the user chose it, so `selectedOptions` hands it
 back. It is the dropdown sibling of
 [`useBbTableContext`](./useBbTableContext.md) and
 [`useBbTabsContext`](./useBbTabsContext.md): same id-rendezvous pattern, same
@@ -47,16 +47,16 @@ const { isReady, open, groups } = useBbDropdownContext(id);
 
 Individual computed refs — safe to destructure. Nothing on it is writable.
 
-| Member    | Type                                                  | Description                                                                                     |
-| --------- | ----------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
-| `isReady` | `ComputedRef<boolean>`                                | A dropdown with this id is currently mounted.                                                   |
-| `open`    | `ComputedRef<boolean>`                                | The dropdown's panel / sheet is open (`false` until it mounts).                                 |
-| `groups`  | `ComputedRef<Record<string, BbDropdownContextGroup>>` | One entry per **selectable** group, keyed by the group's `key`. `{}` until the dropdown mounts. |
+| Member    | Type                                                  | Description                                                                                    |
+| --------- | ----------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
+| `isReady` | `ComputedRef<boolean>`                                | A dropdown with this id is currently mounted.                                                  |
+| `open`    | `ComputedRef<boolean>`                                | The dropdown's panel / sheet is open (`false` until it mounts).                                |
+| `groups`  | `ComputedRef<Record<string, BbDropdownContextGroup>>` | One entry per **selectable** group, keyed by the group's `id`. `{}` until the dropdown mounts. |
 
 ### A group entry (`BbDropdownContextGroup`)
 
 **The group config you declared, with live state on top.** Every field you
-passed in `items` rides through as-is (`key`, `label`, `hideLabel`, `filterBy`,
+passed in `items` rides through as-is (`id`, `label`, `hideLabel`, `filterBy`,
 `max`, `prepend:icon`, `variant`, …), so a chip can be rendered from one
 declaration. The live fields win over anything of the same name:
 
@@ -74,12 +74,12 @@ is a fetcher, and a state snapshot must never invite calling it.
 
 ### A selected option (`BbDropdownContextOption`)
 
-| Field         | Type      | Description                                                                              |
-| ------------- | --------- | ---------------------------------------------------------------------------------------- |
-| `value`       | `unknown` | The selection's value (the group's `itemValue`, or the row `key`). Always present.       |
-| `text`        | `string`  | Resolved display text, once the group has the item.                                      |
-| `description` | `string`  | The group's `itemProps.description` (or a literal row's `description`), when it has one. |
-| `original`    | `unknown` | The raw item behind the value, once resolved.                                            |
+| Field         | Type      | Description                                                                                                               |
+| ------------- | --------- | ------------------------------------------------------------------------------------------------------------------------- |
+| `value`       | `unknown` | The selection's value (the group's `itemValue`, by default the item's own `value`, or the row's `value`). Always present. |
+| `label`       | `string`  | Resolved display label, once the group has the item.                                                                      |
+| `description` | `string`  | The group's `itemProps.description` (or a literal row's `description`), when it has one.                                  |
+| `original`    | `unknown` | The raw item behind the value, once resolved.                                                                             |
 
 ## Usage example — picked assignees shown outside the menu
 
@@ -121,7 +121,7 @@ declare const api: { members: { list: () => Promise<Member[]> } };
 const assignees = ref<string[]>([]);
 const items: BbDropdownItem[] = [
 	{
-		key: 'assignees',
+		id: 'assignees',
 		label: 'Assign to',
 		multiple: true,
 		items: () => api.members.list(),
@@ -148,11 +148,11 @@ const emails = computed(() =>
   (which you own) — the context never mutates.
 - **Lazy: reading never fetches.** A seeded value in a group that has not
   loaded yet (a pipeline group the user never opened, a search-first group)
-  stays `{ value }` with no `text` until the group loads. Set `prefill: true` on
+  stays `{ value }` with no `label` until the group loads. Set `prefill: true` on
   that group to resolve a seeded selection eagerly.
 - **Callable before the dropdown mounts.** The handle starts at stable
   baselines (`isReady` / `open` `false`, `groups` `{}`) and fills in when the
-  dropdown renders. Guard group lookups with `?.` — a key is absent until then.
+  dropdown renders. Guard group lookups with `?.` — an id is absent until then.
 - **The id is a rendezvous key.** A typo does not error — `isReady` simply never
   turns `true`. Check the spelling against the dropdown's `id` prop first.
 - **Client-side only.** During SSR the handle is detached and empty; wire

package/dist/ai/composables/useBbFormField.md

@@ -136,8 +136,12 @@ Returns:
   `aria-required` when a `required` rule or the schema makes it mandatory
   (bind them on a role that supports it: textbox, combobox, listbox,
   radiogroup, checkbox) and the marker a failed submit uses to focus the
-  first invalid field.
+  first invalid field. While the form saves it also carries `aria-readonly`.
 - `errorAttrs` — bind on the element that shows the message (its stable id).
+- `readonly` — `true` while the form saves (a `@submit` promise is pending
+  and the form has no `disable-submit-lock`). Act read-only meanwhile: keep
+  the control focusable and its value visible, refuse changes. Writes to
+  `value` are ignored until it is `false` again.
 
 ## Related
 

package/dist/ai/composables/useBbTabsContext.md

@@ -33,21 +33,21 @@ const tabs = useBbTabsContext<K>(id); // `K` is optional and defaults to `string
 - **`id`** — must match the `id` prop on `<BbTabs id="…">` or
   `<BbTabsRoot id="…">`. Give the component an explicit `id`; auto-generated
   ids are not addressable.
-- **`K`** — optional union of the tab keys, narrowing `current` and `select`.
+- **`K`** — optional union of the tab values, narrowing `current` and `select`.
 
 ### Returned handle (`BbTabsContextHandle<K>`)
 
 Individual computed refs and functions — safe to destructure.
 
-| Member         | Type                                                     | Description                                                                                                                                                                         |
-| -------------- | -------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `isReady`      | `ComputedRef<boolean>`                                   | Whether a tabs instance with this id is currently mounted.                                                                                                                          |
-| `current`      | `WritableComputedRef<K \| null>`                         | Active tab key (`null` until the tabs mount). **Writable**: assigning a key selects it, exactly like `select(key)`. Setting `null` warns and is ignored — a tab is always selected. |
-| `currentIndex` | `ComputedRef<number>`                                    | Zero-based index of the active tab (`-1` until mount).                                                                                                                              |
-| `isFirst`      | `ComputedRef<boolean>`                                   | Active tab is the first item.                                                                                                                                                       |
-| `isLast`       | `ComputedRef<boolean>`                                   | Active tab is the last item.                                                                                                                                                        |
-| `goTo`         | `(t: 'first' \| 'previous' \| 'next' \| 'last') => void` | Relative navigation; skips `disabled` tabs.                                                                                                                                         |
-| `select`       | `(key: K) => void`                                       | Select by key. Unknown keys warn and leave the selection untouched.                                                                                                                 |
+| Member         | Type                                                     | Description                                                                                                                                                                               |
+| -------------- | -------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `isReady`      | `ComputedRef<boolean>`                                   | Whether a tabs instance with this id is currently mounted.                                                                                                                                |
+| `current`      | `WritableComputedRef<K \| null>`                         | Active tab value (`null` until the tabs mount). **Writable**: assigning a value selects it, exactly like `select(value)`. Setting `null` warns and is ignored — a tab is always selected. |
+| `currentIndex` | `ComputedRef<number>`                                    | Zero-based index of the active tab (`-1` until mount).                                                                                                                                    |
+| `isFirst`      | `ComputedRef<boolean>`                                   | Active tab is the first item.                                                                                                                                                             |
+| `isLast`       | `ComputedRef<boolean>`                                   | Active tab is the last item.                                                                                                                                                              |
+| `goTo`         | `(t: 'first' \| 'previous' \| 'next' \| 'last') => void` | Relative navigation; skips `disabled` tabs.                                                                                                                                               |
+| `select`       | `(value: K) => void`                                     | Select by value. Unknown values warn and leave the selection untouched.                                                                                                                   |
 
 Selection through the handle goes through the tabs' full pipeline: the
 component's `v-model` is emitted, and URL / Inertia navigation runs when the
@@ -73,12 +73,12 @@ tabs have `navigation` — identical to clicking the trigger.
 	<BbTabs
 		id="settings-tabs"
 		:items="[
-			{ key: 'general', label: 'General' },
-			{ key: 'security', label: 'Security' },
-			{ key: 'billing', label: 'Billing' },
+			{ value: 'general', label: 'General' },
+			{ value: 'security', label: 'Security' },
+			{ value: 'billing', label: 'Billing' },
 		]"
 	>
-		<!-- one pane slot per key -->
+		<!-- one pane slot per value -->
 	</BbTabs>
 </template>
 

package/dist/ai/guides/agent-contract.md

@@ -12,32 +12,32 @@ Use this contract before generating any UI code with `bitboss-ui`.
 The names agents guess most often, and the real ones. There are no aliases:
 a guessed name is an error (`npx bitboss-ui check` or `vue-tsc` says so).
 
-| You'd guess                                                                                  | bitboss-ui                                                                                                                              |
-| -------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
-| `toast.success('Saved')`, `{ message }`, `{ description }`, `type`                           | `const { toast } = useToast(); toast({ title, text, variant: 'success' })`; variants `default` `success` `info` `warning` `destructive` |
-| `<BbToastStack>`, a toaster per page                                                         | one `<BbToast />` (and one `<BbConfirm />` for `useConfirm`) at the app root                                                            |
-| BbDialog `v-model:open`, `:open`                                                             | `v-model` (a boolean)                                                                                                                   |
-| BbDialog `@close`, `@confirm`, `@cancel`, `#actions`                                         | `@hide` (closing starts) / `@hidden` (closed); your own buttons in `#footer="{ close }"`                                                |
-| BbTable `sortable`, `v-model:sorted`, `sort-order`, `@sort`                                  | `sortable: true` per column + `v-model:sort` (a `BbTableSortEntry[]`, `[key, 'asc' \| 'desc']`); the table never sorts: you do          |
-| `@row-click`, `@row:click`                                                                   | `@click:row="(event, item) => …"`                                                                                                       |
-| `row-key`                                                                                    | `item-value`                                                                                                                            |
-| column `title`, `header`                                                                     | column `label`                                                                                                                          |
-| `#cell:createdAt`, `#createdAt`, `{ row }`                                                   | `#<key>` in kebab-case (`createdAt` → `#created-at`), scope `{ item, value }`                                                           |
-| a column keyed `actions`                                                                     | reserved: the `#actions="{ item }"` slot creates the actions column                                                                     |
-| BbPagination `current-page`, `v-model:page`, `page-size`                                     | `v-model` (the 1-based page) + `per-page` + `total-items` (or `total-pages`)                                                            |
-| `BbDateInput`                                                                                | `BbDatePickerInput`                                                                                                                     |
-| `<BbDropdownItem>`, `<BbTableColumn>`                                                        | types, not components: rows are `items` objects (`{ key, text, onClick }`), columns are `columns` objects                               |
-| BbDropdown `#trigger`, `#button`                                                             | `#activator="{ props }"`, spread `v-bind="props"` on your button                                                                        |
-| a menu row's click via `@select` / `@item:selected`                                          | the item's `onClick` (or `href` / `to`); `@item:selected` fires only for `selectable` groups                                            |
-| `icon` on BbTextInput / BbDropdownButton, `#icon` on BbButton                                | `prepend:icon` / `append:icon`; BbButton's `icon` is the icon-only button                                                               |
-| badge `success` / `warning` / `info` / `danger`                                              | built-ins `primary` `secondary` `destructive` `outline`; register more (§ Variants Rule)                                                |
-| BbBadge `text` / `label` prop                                                                | the default slot: `<BbBadge>Paid</BbBadge>`                                                                                             |
-| `label` on BbCheckboxGroup / BbRadioGroup / BbSwitchGroup / BbRating, a `selectable` BbTable | `legend` (they render a `<fieldset>`; the legend is its name)                                                                           |
-| `{ label, value }` items as they are                                                         | `item-text="label" item-value="value"` (BbSelect, BbSelectPopover, the groups); without them each option reads as JSON                  |
-| BbSelect `searchable`                                                                        | search is on by default; `disable-writing` hides it; `multiple` for a multi-select                                                      |
-| a native `<input>` in a filter bar (to skip the label)                                       | `<BbTextInput label="Search" hide-label />`: the label stays for screen readers                                                         |
-| `--bb-text-secondary`                                                                        | `--bb-text-muted`                                                                                                                       |
-| a 422 through each field's `errors` prop                                                     | inside `BbForm`: `setErrors(errors)` ([validated-forms § 4](./validated-forms.md#4-server-errors-seterrors-fields-unmatchederrors))     |
+| You'd guess                                                                                  | bitboss-ui                                                                                                                                   |
+| -------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
+| `toast.success('Saved')`, `{ message }`, `{ description }`, `type`                           | `const { toast } = useToast(); toast({ title, text, variant: 'success' })`; variants `default` `success` `info` `warning` `destructive`      |
+| `<BbToastStack>`, a toaster per page                                                         | one `<BbToast />` (and one `<BbConfirm />` for `useConfirm`) at the app root                                                                 |
+| BbDialog `v-model:open`, `:open`                                                             | `v-model` (a boolean)                                                                                                                        |
+| BbDialog `@close`, `@confirm`, `@cancel`, `#actions`                                         | `@hide` (closing starts) / `@hidden` (closed); your own buttons in `#footer="{ close }"`                                                     |
+| BbTable `sortable`, `v-model:sorted`, `sort-order`, `@sort`                                  | `sortable: true` per column + `v-model:sort` (a `BbTableSortEntry[]`, `[key, 'asc' \| 'desc']`); the table never sorts: you do               |
+| `@row-click`, `@row:click`                                                                   | `@click:row="(event, item) => …"`                                                                                                            |
+| `row-key`                                                                                    | `item-value`                                                                                                                                 |
+| column `title`, `header`                                                                     | column `label`                                                                                                                               |
+| `#cell:createdAt`, `#createdAt`, `{ row }`                                                   | `#<key>` in kebab-case (`createdAt` → `#created-at`), scope `{ item, value }`                                                                |
+| a column keyed `actions`                                                                     | reserved: the `#actions="{ item }"` slot creates the actions column                                                                          |
+| BbPagination `current-page`, `v-model:page`, `page-size`                                     | `v-model` (the 1-based page) + `per-page` + `total-items` (or `total-pages`)                                                                 |
+| `BbDateInput`                                                                                | `BbDatePickerInput`                                                                                                                          |
+| `<BbDropdownItem>`, `<BbTableColumn>`                                                        | types, not components: rows are `items` objects (`{ value, label, onClick }`), columns are `columns` objects                                 |
+| BbDropdown `#trigger`, `#button`                                                             | `#activator="{ props }"`, spread `v-bind="props"` on your button                                                                             |
+| a menu row's click via `@select` / `@item:selected`                                          | the item's `onClick` (or `href` / `to`); `@item:selected` fires only for `selectable` groups                                                 |
+| `icon` on BbTextInput / BbDropdownButton, `#icon` on BbButton                                | `prepend:icon` / `append:icon`; BbButton's `icon` is the icon-only button                                                                    |
+| badge `success` / `warning` / `info` / `danger`                                              | built-ins `primary` `secondary` `destructive` `outline`; register more (§ Variants Rule)                                                     |
+| BbBadge `text` / `label` prop                                                                | the default slot: `<BbBadge>Paid</BbBadge>`                                                                                                  |
+| `label` on BbCheckboxGroup / BbRadioGroup / BbSwitchGroup / BbRating, a `selectable` BbTable | `legend` (they render a `<fieldset>`; the legend is its name)                                                                                |
+| `{ label, value }` items as they are                                                         | they work as they are, and so do `{ text, value }`: any other shape needs `item-text` / `item-value` (BbSelect, BbSelectPopover, the groups) |
+| BbSelect `searchable`                                                                        | search is on by default; `disable-writing` hides it; `multiple` for a multi-select                                                           |
+| a native `<input>` in a filter bar (to skip the label)                                       | `<BbTextInput label="Search" hide-label />`: the label stays for screen readers                                                              |
+| `--bb-text-secondary`                                                                        | `--bb-text-muted`                                                                                                                            |
+| a 422 through each field's `errors` prop                                                     | inside `BbForm`: `setErrors(errors)` ([validated-forms § 4](./validated-forms.md#4-server-errors-seterrors-fields-unmatchederrors))          |
 
 ## Default API Boundary
 
@@ -213,7 +213,7 @@ recipe's conformance checklist.
 
 For components accepting `items`:
 
-- prefer declarative mapping with `item-text` and `item-value`;
+- prefer declarative mapping with `item-text` and `item-value` (none when the items already carry `label` and `value`: never restate the default);
 - use `dependencies` and `deps-debounce-time` for tied fields;
 - use `enforce-coherence` instead of custom watchers for stale model cleanup;
 - to style a row BY ITS DATA (a destructive entry, a tile by tier, a row by

package/dist/ai/guides/ai-router.md

@@ -102,7 +102,7 @@ inline-edit playbook) instead of inventing a new shape.
 | ⌘K / Ctrl+K global command palette                                                                                   | [BbSelectPopover](../BbSelectPopover.md#a-k-command-palette) § A ⌘K command palette                                                                                                                                                                                                                                                                                                                           |
 | Tied selects / stale model cleanup                                                                                   | [coherence-playbook](./coherence-playbook.md)                                                                                                                                                                                                                                                                                                                                                                 |
 | Async `items` providers / prefill                                                                                    | [fetch-items-playbook](./fetch-items-playbook.md)                                                                                                                                                                                                                                                                                                                                                             |
-| `item-text` / `item-value` / disabled                                                                                | [options-items-playbook](./options-items-playbook.md)                                                                                                                                                                                                                                                                                                                                                         |
+| `item-text` / `item-value` / the default `label` / `value` keys / disabled                                           | [options-items-playbook](./options-items-playbook.md)                                                                                                                                                                                                                                                                                                                                                         |
 | Table cell edit ownership                                                                                            | [inline-edit-playbook](./inline-edit-playbook.md)                                                                                                                                                                                                                                                                                                                                                             |
 | Table row → detail (identity cells)                                                                                  | [agent-contract](./agent-contract.md) § Inline Links                                                                                                                                                                                                                                                                                                                                                          |
 | Peek that drills into related records                                                                                | [agent-contract](./agent-contract.md) § Consult-Stack                                                                                                                                                                                                                                                                                                                                                         |

package/dist/ai/guides/component-picker.md

@@ -254,7 +254,7 @@ compose it or write it yourself.
 | `useLiveFeed` / any polling or cross-tab feed helper                                             | Does not exist, and neither does a cross-tab helper — `useBroadcastChannelInstance` was removed (cross-tab messaging is not a UI concern). Use `useBroadcastChannel` from `@vueuse/core`; the polling and the merge are yours.                                                                                                                                                                                                                                                         |
 | `BbStepper` / `BbWizard`                                                                         | Does not exist as a component; the wizard-form recipe under `recipes/<platform>/wizard-form.md` ([Vue](../recipes/vue/wizard-form.md) · [Nuxt](../recipes/nuxt/wizard-form.md) · [Inertia](../recipes/inertia/wizard-form.md)) composes one.                                                                                                                                                                                                                                           |
 | `BbSkeleton` (standalone)                                                                        | Only `BbTable` ships skeletons, via the column `skeleton` field.                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| `BbWorkspaceSwitcher` / `BbTeamSwitcher` / `BbAccountSwitcher` / org, tenant or project switcher | Does not exist as a component — it is a [BbDropdown](../BbDropdown.md) pattern: a row for the current record whose submenu is a `selectable` (single), `searchable`, fetched group bound to the current id with `<BbDropdownGroup v-model>`. Carry each record to the slots with `meta` (`itemProps: (w) => ({ meta: w })`) and draw it with `#<groupKey>:item:prepend`, so the other rows keep their icons. See BbDropdown.md § Rows that stand for records.                          |
+| `BbWorkspaceSwitcher` / `BbTeamSwitcher` / `BbAccountSwitcher` / org, tenant or project switcher | Does not exist as a component — it is a [BbDropdown](../BbDropdown.md) pattern: a row for the current record whose submenu is a `selectable` (single), `searchable`, fetched group bound to the current id with `<BbDropdownGroup v-model>`. Carry each record to the slots with `meta` (`itemProps: (w) => ({ meta: w })`) and draw it with `#<groupId>:item:prepend`, so the other rows keep their icons. See BbDropdown.md § Rows that stand for records.                           |
 | `BbCommand` / command palette                                                                    | Does not exist. Compose `BbDialog` + `BbSelectPopover` — do not hand-roll the search: [BbSelectPopover § A ⌘K command palette](../BbSelectPopover.md#a-k-command-palette) is the worked example (⌘K / Ctrl+K, grouped server results, debouncing and race protection from the popover, navigation per platform).                                                                                                                                                                       |
 | `BbSeatMap` / `BbSeatPicker` / `BbSeatGrid` / a seat map, desk or parking-bay picker             | Does not exist, on purpose (a niche need), and there is no recipe for it. Build it in your app as a WAI-ARIA grid with one tab stop (roving `tabindex`, arrow keys move between positions) styled with the library tokens; do not give every seat its own tab stop.                                                                                                                                                                                                                    |
 | `BbCalendar` as a scheduling / events view                                                       | [BbCalendar](../BbCalendar.md) is the picker's calendar rendered in place — a value control (day, range, set, month, year, datetime), not an events grid. Put per-day content in its `#day` / `#day:append` slots; an agenda or booking board is your own layout around it.                                                                                                                                                                                                            |
@@ -273,13 +273,13 @@ recipe under `recipes/<platform>/layout-scaffold.md` ([Vue](../recipes/vue/layou
 
 ## Item-Driven Components
 
-The following components accept an `items` prop (array or async provider function) with `item-text`/`item-value` mapping. Consult the items playbooks before wiring them:
+The following components accept an `items` prop (array or async provider function): object items are read through their own `label` (else `text`) and `value`, or through `item-text`/`item-value` when your fields are named otherwise. Consult the items playbooks before wiring them:
 
 - [BbSelect](../BbSelect.md), [BbSelectPopover](../BbSelectPopover.md)
 - [BbCheckboxGroup](../BbCheckboxGroup.md), [BbRadioGroup](../BbRadioGroup.md), [BbSwitchGroup](../BbSwitchGroup.md)
 - [BbTable](../BbTable.md)
 
-`BbDropdown`, `BbBreadcrumbs`, `BbTabs`, and `BbTree` are also declared through `items`, but with typed item objects (label/key/href/…) rather than arbitrary domain objects. `BbDropdown` bridges the two: a fetched group maps domain objects through `itemText` / `itemValue` / `itemProps`, and any row carries its domain object to the slots in `meta`.
+`BbDropdown`, `BbBreadcrumbs`, `BbTabs`, and `BbTree` are also declared through `items`, but with typed item objects (`value`/`label`/`href`/…) rather than arbitrary domain objects. `BbDropdown` bridges the two: a fetched group reads `label` / `value` like the pickers, or maps domain objects through `itemText` / `itemValue` / `itemProps`, and any row carries its domain object to the slots in `meta`.
 
 See:
 

package/dist/ai/guides/fetch-items-playbook.md

@@ -116,7 +116,7 @@ const searchMembers = async ({
 };
 ```
 
-Single select: normalize before the ids request — `const ids = Array.isArray(modelValue) ? modelValue : modelValue == null || modelValue === '' ? [] : [modelValue]`. Search-first: `if (reason === 'search' && !query.trim()) return []`. Dedupe on the field you pass as `item-value`. **The merge is select-only**: a table provider returns the page as it is.
+Single select: normalize before the ids request — `const ids = Array.isArray(modelValue) ? modelValue : modelValue == null || modelValue === '' ? [] : [modelValue]`. Search-first: `if (reason === 'search' && !query.trim()) return []`. Dedupe on the field that is the option's value (`item-value`, or the own `value` key when you pass none). **The merge is select-only**: a table provider returns the page as it is.
 
 ### `signal`
 

package/dist/ai/guides/icons-policy.md

@@ -128,7 +128,7 @@ exists.
 ```html
 <BbDropdownButton
 	prepend:icon="lucide:download"
-	:items="[{ key: 'export', text: 'Export' }, ...exportFormats]"
+	:items="[{ value: 'export', label: 'Export' }, ...exportFormats]"
 />
 ```
 
@@ -187,10 +187,10 @@ clear/stepper/toggle controls — prefer `prepend:icon` when in doubt):
 
 ```ts
 const memberActions = [
-	{ key: 'edit', text: 'Edit member', 'prepend:icon': 'lucide:pencil' },
+	{ value: 'edit', label: 'Edit member', 'prepend:icon': 'lucide:pencil' },
 	{
-		key: 'delete',
-		text: 'Delete',
+		value: 'delete',
+		label: 'Delete',
 		variant: 'destructive',
 		'prepend:icon': 'lucide:trash-2',
 	},
@@ -205,19 +205,19 @@ the same way.
 These surfaces take arbitrary content, so you place a `BbIcon` (or richer
 markup) yourself:
 
-- `BbTabs` / `BbTabsList` — per-tab `<key>:label` slot (or the generic `label`
+- `BbTabs` / `BbTabsList` — per-tab `<value>:label` slot (or the generic `label`
   fallback):
 
 ```html
 <BbTabs v-model="tab" :items="tabs">
-	<template #billing:label="{ text }">
-		<BbIcon icon="lucide:file-text" size="sm" /> {{ text }}
+	<template #billing:label="{ label }">
+		<BbIcon icon="lucide:file-text" size="sm" /> {{ label }}
 	</template>
 </BbTabs>
 ```
 
 - `BbBreadcrumbs` — `item:prepend` / `item:append` around every item, or a
-  named slot per `item.key` to replace one item's content:
+  named slot per `item.value` to replace one item's content:
 
 ```html
 <BbBreadcrumbs :items="trail">
@@ -242,8 +242,8 @@ markup) yourself:
 - `BbSwitch` — the `icon` slot replaces the toggle track visual (rarely
   needed; the default track is correct for almost every case).
 - `BbDropdown` — `item:prepend` / `item:append`, one group's
-  `<groupKey>:item:prepend` / `:append`, or per-entry `<key>:prepend` /
-  `<key>:append` slots, when an entry's leading/trailing region needs more than
+  `<groupId>:item:prepend` / `:append`, or per-entry `<value>:prepend` /
+  `<value>:append` slots, when an entry's leading/trailing region needs more than
   a named icon (e.g. an avatar). A slot replaces the icon, never sits beside it.
 
 ## Sizing and color