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

package/dist/ai/BbSelect.md

@@ -100,18 +100,14 @@ Prefer a sibling when the shape is simpler:
 
 ### Map options with `item-text` and `item-value`
 
-**Object items need `item-text`.** Without it each label is
-`JSON.stringify(item)`, and without `item-value` the whole object is the value.
-`{ label, value }` items take both:
+**`{ label, value }` and `{ text, value }` items work as they are; any other
+shape needs `item-text` / `item-value`.** With neither prop an option reads its
+own `label` (else its own `text`) and its own `value`, whatever it holds (`null`
+included). An object with none of those fields falls back to
+`JSON.stringify(item)` as text and the whole object as value.
 
 ```vue
-<BbSelect
-	v-model="plan"
-	label="Plan"
-	:items="plans"
-	item-text="label"
-	item-value="value"
-/>
+<BbSelect v-model="plan" label="Plan" :items="plans" />
 ```
 
 Pass your domain objects to `items` **as they are** and tell the component which
@@ -172,8 +168,9 @@ Value-identity rules (shared with every items-driven component — see the
 Options and Items playbook):
 
 - For primitive `items` (`string[]` / `number[]`) omit both mapping props — the
-  value is the primitive itself. For object items always set both: the defaults
-  are the whole item as value and `JSON.stringify(item)` as text.
+  value is the primitive itself. `{ label, value }` / `{ text, value }` objects
+  need none either; any other object shape needs both (its fallbacks are
+  `JSON.stringify(item)` as text and the whole item as value).
 - Matching compares **value hashes** (deep structural equality, not reference
   identity), so object values survive refetches — but prefer primitive ids:
   stable, unique, cheap to submit.
@@ -187,7 +184,8 @@ Options and Items playbook):
 
 #### Additional row fields: `item-props`
 
-`item-text` and `item-value` are the option's label and identity. Anything
+The option's text and value (from `item-text` / `item-value`, or the item's own
+`label` and `value`) are its label and identity. Anything
 **additional** about a row comes from `item-props`. Select options accept three
 fields:
 
@@ -461,8 +459,6 @@ model to `[]` (or `null` in single mode).
 			clearable
 			compact
 			hint="Pick up to 3 cities"
-			item-text="label"
-			item-value="value"
 			:items="options"
 			label="Cities"
 			:max="3"
@@ -552,8 +548,6 @@ v-model is yours:
 		<BbSelect
 			v-model="channels"
 			compact
-			item-text="label"
-			item-value="value"
 			:items="options"
 			label="Notify via"
 			:max-selected-labels="2"
@@ -723,7 +717,6 @@ on your setup:
 			v-model="city"
 			compact
 			:filter-by="['label', 'country']"
-			item-text="label"
 			item-value="id"
 			:items="cities"
 			label="City"
@@ -1074,8 +1067,6 @@ options to look, so you have to say so:
 		<BbSelect
 			v-model="location"
 			compact
-			item-text="label"
-			item-value="value"
 			:items="loadLocations"
 			label="Location"
 			placeholder="Select location…"
@@ -1135,8 +1126,6 @@ locations" renders from the first paint:
 ```vue
 <BbSelect
 	v-model="state.location"
-	item-text="label"
-	item-value="value"
 	:items="[
 		{ label: 'All locations', value: null },
 		{ label: 'Milan', value: 'milan' },
@@ -1203,8 +1192,6 @@ disabled field still submits its value.
 			v-model="province"
 			clearable
 			compact
-			item-text="label"
-			item-value="value"
 			:items="provinces"
 			label="Province"
 			placeholder="Pick a province"
@@ -1217,8 +1204,6 @@ disabled field still submits its value.
 			:disabled="!province"
 			empty-text="Choose a province first"
 			enforce-coherence
-			item-text="label"
-			item-value="value"
 			:items="loadCities"
 			label="City"
 			:placeholder="province ? 'Pick a city' : 'Select a province first'"
@@ -1556,8 +1541,6 @@ lists window per row) or pre-chunk the data into smaller groups.
 			clearable
 			compact
 			group-by="department"
-			item-text="label"
-			item-value="value"
 			:items="roles"
 			label="Role"
 			placeholder="Pick a role"
@@ -1620,8 +1603,6 @@ compact control, so it keeps the compact rows on every device — turning
 		<BbSelect
 			v-model="assignee"
 			compact
-			item-text="label"
-			item-value="value"
 			:items="teammates"
 			label="Assignee"
 			placeholder="Choose a teammate"
@@ -1699,8 +1680,6 @@ once the chips outgrow the field — keep chips compact, or raise
 		<BbSelect
 			v-model="tags"
 			clearable
-			item-text="label"
-			item-value="value"
 			:items="tagItems"
 			label="Labels"
 			multiple
@@ -2080,8 +2059,9 @@ it: [passthrough guide § Typing `pt` in `<script>`](./guides/passthrough.md#typ
 
 ### Anti-patterns
 
-- Pre-mapping items to `{ label, value }`, or storing whole objects in the
-  model when an id is enough.
+- Pre-mapping domain rows into `{ label, value }` copies (name their fields with
+  `item-text` / `item-value` instead), or storing whole objects in the model
+  when an id is enough.
 - `watch(filter, refetch)` when `dependencies` exists; blind `model = null`
   resets when `enforce-coherence` would preserve still-valid values.
 - Hand-rolled debounce or loading refs around the provider.
@@ -2149,8 +2129,8 @@ it: [passthrough guide § Typing `pt` in `<script>`](./guides/passthrough.md#typ
 | `itemHeight` | `number \| undefined` | `28` |  | Height of the options in the listbox (px). Defaults to 28px (24px compact; 44px / 36px on mobile viewports). An explicit value wins on every viewport. |
 | `itemProps` | `BbSelectItemProps<T> \| undefined` |  |  | ADDITIONAL row fields resolved from each item — never its text or value (those stay on `itemText` / `itemValue`). Accepted fields: - `description` — a muted line under the option label. Setting it gives every row a fixed two-line height (the list is virtualized); the description stays on one line and ellipsizes. Announced as the option's description, never part of its name; matched by the search with the text when `filterBy` is empty. - `prepend:icon` — an icon before the label. - `append:icon` — an icon after the label; on the selected row the check takes its place. Either an object with a path or getter per field (`{ description: 'email', 'prepend:icon': 'icon' }`) or a function returning the fields (`(item) => ({ description: item.email })`). Without it no field renders — nothing is read off the item implicitly — and an empty value renders nothing for that item. Never shown in the trigger or the chips. To disable individual options use `selectable`. |
 | `items` | `T[] \| ((context: BbSelectItemsContext) => T[] \| Promise<T[]>)` |  | yes | The options: an array, or a provider function called with ONE context object and returning the rows, sync or async. The context carries: - `query` — what the user typed, `''` until they type; - `reason` — why this call happened: `'search'` (the user typed, and nothing else), `'initial'` (the first load, on mount or on the first open), `'dependencies'` (a `dependencies` entry or the `items` function changed; a retry arrives this way), `'model'` (the model changed from outside and the options cannot resolve it), `'reopen'` (the panel reopened over a searched list). To resolve the selection by id, branch on `reason !== 'search'`; - `modelValue` — the `v-model` as-is; - `signal` — an `AbortSignal`, aborted when a newer call starts or the component is disposed; pass it to every request. A provider signals a failure by THROWING, never by returning `[]`: the rows are cleared, nothing is pruned, and `#empty` receives the `error` (`failed-text` is shown). A newer call aborts the one in flight, and the aborted call's rejection or resolution is dropped silently. Zero-argument providers keep working. Annotate the parameter `BbSelectItemsContext`. |
-| `itemText` | `ItemAccessor<T, string> \| undefined` | `JSON.stringify(item)` |  | Defines a path that returns a property of the object to use as text or a function that returns a string. |
-| `itemValue` | `ItemAccessor<T> \| undefined` | `the whole item` |  | Defines a path that returns a property of the object to use as value or a function that returns any value. |
+| `itemText` | `ItemAccessor<T, string> \| undefined` | `own `label`, else `text`, else `JSON.stringify(item)`` |  | Defines a path that returns a property of the object to use as text or a function that returns a string. Unset: own `label`, else `text` (`{ label, value }` needs no accessor). |
+| `itemValue` | `ItemAccessor<T> \| undefined` | `own `value`, else the whole item` |  | Defines a path that returns a property of the object to use as value or a function that returns any value. Unset: own `value`, even `null`. |
 | `label` | `string` |  | yes | Text content of the label of the element. |
 | `labelAlign` | `'top'` \| `'center'` \| `'bottom'` |  |  | Vertical position of the label block in a side-by-side row; not `labelPosition`, the horizontal one. Omitted, the label's first line meets the control's. |
 | `labelMode` | `"outside" \| "floating" \| "inside" \| undefined` |  |  | Label rendering mode. |

package/dist/ai/BbSelectPopover.md

@@ -60,17 +60,14 @@ driving a trigger you render yourself.
 
 ### Map options with `item-text` / `item-value`
 
-**Object items need `item-text`.** Without it each label is
-`JSON.stringify(item)`, and without `item-value` the whole object is the value.
-`{ label, value }` items take both:
+**`{ label, value }` and `{ text, value }` items work as they are; any other
+shape needs `item-text` / `item-value`.** With neither prop an option reads its
+own `label` (else its own `text`) and its own `value`, whatever it holds (`null`
+included). An object with none of those fields falls back to
+`JSON.stringify(item)` as text and the whole object as value.
 
 ```vue
-<BbSelectPopover
-	v-model="plan"
-	:items="plans"
-	item-text="label"
-	item-value="value"
-/>
+<BbSelectPopover v-model="plan" :items="plans" />
 ```
 
 Pass your domain objects to `items` as they are and name the display/value
@@ -78,8 +75,9 @@ fields with `item-text` / `item-value` (dot-paths or extractor functions). The
 `v-model` holds the resolved **value**, not the whole object. The value-identity
 rules are the shared ones (see the Options and Items playbook), in brief:
 
-- Primitive `items` (`string[]` / `number[]`) need no mapping props; for object
-  items always set both.
+- Primitive `items` (`string[]` / `number[]`) and `{ label, value }` /
+  `{ text, value }` objects need no mapping props; any other object shape needs
+  both.
 - Matching compares **value hashes** (deep structural equality), so object
   values survive refetches — but prefer stable primitive ids.
 - Options resolving to a **duplicate value are silently dropped** (first wins).
@@ -91,7 +89,8 @@ rules are the shared ones (see the Options and Items playbook), in brief:
 
 #### Additional row fields: `item-props`
 
-`item-text` and `item-value` are the option's label and identity. Anything
+The option's text and value (from `item-text` / `item-value`, or the item's own
+`label` and `value`) are its label and identity. Anything
 **additional** about a row comes from `item-props`. Select options accept three
 fields:
 
@@ -373,8 +372,6 @@ height wins everywhere.
 			v-model="owner"
 			compact
 			:item-height="48"
-			item-text="label"
-			item-value="value"
 			:items="people"
 			width="240px"
 		>
@@ -460,8 +457,6 @@ and edit forms, `signal`, failure — is in the BbSelect guide.
 			v-model="destination"
 			compact
 			empty-text="No city found"
-			item-text="label"
-			item-value="value"
 			:items="searchCities"
 			loading-text="Searching…"
 			:query-debounce-time="250"
@@ -800,8 +795,6 @@ row, including the hundreds nobody ever opens.
 					<BbSelectPopover
 						compact
 						disable-writing
-						item-text="label"
-						item-value="value"
 						:items="statuses"
 						:model-value="valueOf(item, 'status')"
 						width="180px"
@@ -1055,8 +1048,6 @@ option. Identical to `BbSelect`, anchored to your trigger.
 			v-model="role"
 			compact
 			group-by="department"
-			item-text="label"
-			item-value="value"
 			:items="roles"
 			width="240px"
 		>
@@ -1286,14 +1277,7 @@ their string equivalents `loading-text` / `empty-text`.
 		<span class="pr-1 text-xs font-medium text-(--bb-text-muted)"
 			>Destination</span
 		>
-		<BbSelectPopover
-			v-model="city"
-			compact
-			item-text="label"
-			item-value="value"
-			:items="cities"
-			width="240px"
-		>
+		<BbSelectPopover v-model="city" compact :items="cities" width="240px">
 			<template #activator="{ props }">
 				<BbBadge
 					append:icon="lucide:chevron-down"
@@ -1793,8 +1777,8 @@ A `pt` value written in `<script>` (a constant, a preset, a wrapper's
 | `itemHeight` | `number \| undefined` | `28` |  | Height of the options in the listbox (px). Defaults to 28px (24px compact; 44px / 36px on mobile viewports). An explicit value wins on every viewport. |
 | `itemProps` | `BbSelectItemProps<Item> \| undefined` |  |  | ADDITIONAL row fields resolved from each item — never its text or value (those stay on `itemText` / `itemValue`). Accepted fields: - `description` — a muted line under the option label. Setting it gives every row a fixed two-line height (the list is virtualized); the description stays on one line and ellipsizes. Announced as the option's description, never part of its name; matched by the search with the text when `filterBy` is empty. - `prepend:icon` — an icon before the label. - `append:icon` — an icon after the label; on the selected row the check takes its place. Either an object with a path or getter per field (`{ description: 'email', 'prepend:icon': 'icon' }`) or a function returning the fields (`(item) => ({ description: item.email })`). Without it no field renders — nothing is read off the item implicitly — and an empty value renders nothing for that item. Never shown in the trigger or the chips. To disable individual options use `selectable`. |
 | `items` | `Item[] \| ((context: BbSelectPopoverItemsContext) => Item[] \| Promise<Item[]>)` | `[]` | yes | The options: an array, or a provider function called with ONE context object and returning the rows, sync or async. The context carries: - `query` — what the user typed, `''` until they type; - `reason` — why this call happened: `'search'` (the user typed, and nothing else), `'initial'` (the first load, on mount or on the first open), `'dependencies'` (a `dependencies` entry or the `items` function changed; a retry arrives this way), `'model'` (the model changed from outside and the options cannot resolve it), `'reopen'` (the panel reopened over a searched list). To resolve the selection by id, branch on `reason !== 'search'`; - `modelValue` — the raw v-model: an array in `multiple` mode, the raw model value (possibly `null`) in single mode; - `signal` — an `AbortSignal`, aborted when a newer call starts or the component is disposed; pass it to every request. A provider signals a failure by THROWING, never by returning `[]`: the rows are cleared, nothing is pruned, and `#empty` receives the `error` (`failed-text` is shown). A newer call aborts the one in flight, and the aborted call's rejection or resolution is dropped silently. Zero-argument providers keep working. Annotate the parameter `BbSelectPopoverItemsContext`. |
-| `itemText` | `ItemAccessor<Item, string> \| undefined` | `JSON.stringify(item)` |  | Path to item property for display text or function to extract it. |
-| `itemValue` | `ItemAccessor<Item> \| undefined` | `the whole item` |  | Path to item property for value or function to extract it. |
+| `itemText` | `ItemAccessor<Item, string> \| undefined` | `own `label`, else `text`, else `JSON.stringify(item)`` |  | Path to item property for display text or function to extract it. Unset: own `label`, else `text` (`{ label, value }` needs no accessor). |
+| `itemValue` | `ItemAccessor<Item> \| undefined` | `own `value`, else the whole item` |  | Path to item property for value or function to extract it. Unset: own `value`, even `null`. |
 | `loading` | `boolean \| undefined` | `false` |  | Display the loading state styles. |
 | `loadingText` | `string \| undefined` |  |  | Message shown while items are being loaded. |
 | `max` | `number \| undefined` | `Infinity` |  | Maximum number of selectable items (limits selection when `multiple` is true). |

package/dist/ai/BbSmoothHeight.md

@@ -125,7 +125,6 @@ controls above and the actions below stay put while the middle animates.
 		<BbRadioGroup
 			v-model="method"
 			compact
-			item-text="label"
 			item-value="id"
 			:items="methods"
 			legend="Payment method"
@@ -485,7 +484,6 @@ the box.
 		<BbRadioGroup
 			v-model="method"
 			compact
-			item-text="label"
 			item-value="id"
 			:items="methods"
 			legend="Payment method"

package/dist/ai/BbSwitchGroup.md

@@ -67,18 +67,14 @@ Choose on what the flip _means_, not on whether a Save button exists.
 
 ### Items are your domain objects
 
-**Object items need `item-text`.** Without it each label is
-`JSON.stringify(item)`, and without `item-value` the whole object is the value.
-`{ label, value }` items take both:
+**`{ label, value }` and `{ text, value }` items work as they are; any other
+shape needs `item-text` / `item-value`.** With neither prop an option reads its
+own `label` (else its own `text`) and its own `value`, whatever it holds (`null`
+included). An object with none of those fields falls back to
+`JSON.stringify(item)` as text and the whole object as value.
 
 ```vue
-<BbSwitchGroup
-	v-model="enabled"
-	legend="Features"
-	:items="options"
-	item-text="label"
-	item-value="value"
-/>
+<BbSwitchGroup v-model="enabled" legend="Features" :items="options" />
 ```
 
 `BbSwitchGroup` is items-driven and shares the checkbox group's mapping API.
@@ -97,7 +93,6 @@ stored value with `item-text` / `item-value` — never pre-map into
 			v-model="channels"
 			compact
 			description="Each channel applies the moment you flip it."
-			item-text="label"
 			item-value="id"
 			:items="options"
 			legend="Where should we reach you?"
@@ -138,7 +133,8 @@ keep values unique — prefer stable primitive ids.
 
 #### Additional row fields: `item-props`
 
-`item-text` and `item-value` are the option's label and identity. Anything
+The option's text and value (from `item-text` / `item-value`, or the item's own
+`label` and `value`) are its label and identity. Anything
 **additional** about a row comes from `item-props` — for option groups that is
 one field, `description`: a muted line **under** the switch's label, beside the
 control.
@@ -406,7 +402,6 @@ explains why:
 	<div class="grid max-w-sm gap-2 rounded-(--bb-radius) border p-3">
 		<BbSwitchGroup
 			compact
-			item-text="label"
 			item-value="id"
 			:items="flags"
 			legend="Feature flags"
@@ -503,7 +498,6 @@ involved. See the [fetch-items](../../ai/guides/fetch-items-playbook.md) and
 		<BbRadioGroup
 			v-model="plan"
 			compact
-			item-text="label"
 			item-value="id"
 			:items="plans"
 			legend="Workspace plan"
@@ -517,7 +511,6 @@ involved. See the [fetch-items](../../ai/guides/fetch-items-playbook.md) and
 			:deps-debounce-time="150"
 			enforce-coherence
 			hint="Channels outside the current plan turn off automatically."
-			item-text="label"
 			item-value="id"
 			:items="loadChannels"
 			legend="Alert channels"
@@ -639,7 +632,6 @@ broadcast over every row, `pt:item:checked` resolves per row.
 			v-model="channels"
 			class="w-full"
 			description="Each channel applies the moment you flip it."
-			item-text="label"
 			item-value="id"
 			:items="options"
 			legend="Notifications"
@@ -713,8 +705,9 @@ for a preset that fits any row type (never `<any>`), not an imported
 - A `disabled` field on an item object does nothing — it is inert data. Gate
   options with the `selectable` predicate, or disable the whole group with
   `disabled`.
-- Don't pre-map `items` into `{ label, value }` — pass raw rows and resolve with
-  `item-text` / `item-value`.
+- Don't pre-map domain rows into `{ label, value }` copies — pass raw rows and
+  resolve with `item-text` / `item-value` (a list that already is
+  `{ label, value }` needs neither).
 - A native (non-JS) form post needs `name`: the group generates none, unlike
   `BbRadioGroup`, where the name is what ties the options together. Independent
   switches need no tie, so with `v-model` alone leave it off.
@@ -771,8 +764,8 @@ for a preset that fits any row type (never `<any>`), not an imported
 | `itemProps` | `BbOptionGroupItemProps<T> \| undefined` |  |  | ADDITIONAL row fields resolved from each item — never its text or value (those stay on `itemText` / `itemValue`). Option groups accept one field: - `description` — a muted line under the option label, beside the control; it may wrap. Either an object with a path or getter per field (`{ description: 'email' }`) or a function returning the fields (`(item) => ({ description: item.email })`). Without it no field renders — an item's own `description` is never read implicitly — and an empty value renders nothing for that item. The description is announced as the option's description, never part of its name. To disable individual options use `selectable`. |
 | `itemReverse` | `boolean \| undefined` | `false` |  | Swaps each row's input and label from their natural order (input first), in every `item-layout`. `reverse` swaps the legend and the options instead. |
 | `items` | `T[] \| ((context: BbCheckboxGroupItemsContext) => T[] \| Promise<T[]>)` |  | yes | The options: an array, or a provider function called with ONE context object and returning the rows, sync or async. The context carries: - `reason` — why this call happened: `'initial'` (the first load, on mount), `'dependencies'` (a `dependencies` entry or the `items` function changed; a retry arrives this way) or `'model'` (the model changed from outside and the options cannot resolve it). The group has no search field, so it never passes `query`; - `modelValue` — the `v-model` as-is; - `signal` — an `AbortSignal`, aborted when a newer call starts or the group is disposed; pass it to every request. A provider signals a failure by THROWING, never by returning `[]`: the rows are cleared, nothing is pruned, and `#empty` receives the `error` (`failed-text` is shown). Zero-argument providers keep working. Annotate the parameter `BbCheckboxGroupItemsContext` (`BbSwitchGroupItemsContext` on a switch group, the same shape). |
-| `itemText` | `ItemAccessor<T, string> \| undefined` | `JSON.stringify(item)` |  | Defines a path that returns a property of the object to use as text or a function that returns a string. |
-| `itemValue` | `ItemAccessor<T> \| undefined` | `the whole item` |  | Defines a path that returns a property of the object to use as value or a function that returns any value. |
+| `itemText` | `ItemAccessor<T, string> \| undefined` | `own `label`, else `text`, else `JSON.stringify(item)`` |  | Defines a path that returns a property of the object to use as text or a function that returns a string. Unset: own `label`, else `text` (`{ label, value }` needs no accessor). |
+| `itemValue` | `ItemAccessor<T> \| undefined` | `own `value`, else the whole item` |  | Defines a path that returns a property of the object to use as value or a function that returns any value. Unset: own `value`, even `null`. |
 | `labelAlign` | `'top'` \| `'center'` \| `'bottom'` |  |  | Vertical position of the label block in a side-by-side row; not `labelPosition`, the horizontal one. Omitted, the label's first line meets the control's. |
 | `layout` | `FieldLayout \| undefined` |  |  | How the label and the input sit together: `'vertical'`, `'horizontal'` (50/50), `'auto'`, `'label-fill'` (the label takes the free space, the input keeps its size), `'input-fill'` (the other way round), or a two-word ratio pattern like `'xx xxxxx'`. |
 | `legend` | `string` |  | yes | Text content of the legend. |

package/dist/ai/BbTable.md

@@ -376,7 +376,7 @@ plus `columnKey` (the raw column key) so a table-wide template can branch per
 column. When both a per-column and the table-wide slot are provided for the
 same side, the per-column one wins for that column — they never stack. Affixes
 render even beside a full `#<key>:header` replacement (the same rule as
-BbDropdown's `#<key>:prepend/append`). The key always comes first, so a
+BbDropdown's `#<value>:prepend/append`). The key always comes first, so a
 column keyed `prepend` still owns `#prepend:header`, and `#header:prepend`
 stays the table-wide slot.
 
@@ -648,7 +648,9 @@ const euro = (value: number) =>
 ```
 
 `#tfoot` stays for footers that are not column-shaped (a note spanning the
-table, a legend).
+table, a legend). Its `role="row"` elements are rows of the table too: the
+table gives each the next `aria-rowindex` after the body and counts them in
+`aria-rowcount` (an `aria-rowindex` you write yourself is kept).
 
 ### Loading and empty states
 
@@ -2694,8 +2696,6 @@ rollback on failure, and overlay retirement inside the items function.
 					<BbSelectPopover
 						compact
 						disable-writing
-						item-text="label"
-						item-value="value"
 						:items="statuses"
 						:model-value="valueOf(item, 'status')"
 						width="170px"
@@ -3295,10 +3295,11 @@ reader.
 
 ### Config and platform
 
-- **Locale.** The plugin's `locale` (`it`/`en`) drives the built-in strings:
+- **Locale.** The plugin's `locale` (`en`, `it`, `de` or any other shipped locale) drives the built-in strings:
   the empty text, the select-all label, the single-select header text, and
-  the "Select" prefix of each row's accessible selection label. Override any
-  of them per table via `empty-text` / `select-all-label` / `select-text`.
+  each row's accessible selection label ("Select …" in `en`, "… auswählen" in
+  `de`). Override the first three per table via `empty-text` /
+  `select-all-label` / `select-text`, the row label via `accessible-label`.
 - **`actions-text` is localized** like the other built-in strings (`it` →
   `Azioni`, `en` → `Actions`). Seeing `Actions` in an Italian app means the
   plugin is still on the default locale, which is `en` — set the plugin's
@@ -3649,8 +3650,8 @@ for a preset that fits any row type (never `<any>`), not an imported
 - `loading-text` is `sr-only` — it is announced, never painted. The visible
   loading signal is the skeleton (or your `#loading` slot). It defaults to the
   localized `common.loadingText`, so an unset value still announces.
-- Row selection labels default to the localized "select" word plus every
-  cell's content. `accessible-label` overrides that per row — it is called
+- Row selection labels default to every cell's content inside the locale's
+  "select" template (`Select {0}`, `{0} auswählen`). `accessible-label` overrides that per row — it is called
   `(columns, item)` with the mapped cells (in **render** order — look them up
   by `key`, never by position) and the raw record, and whatever it returns
   becomes the checkbox's label.
@@ -3892,7 +3893,7 @@ States are listed in precedence order: when two are on at once and their entries
 - `tbody` — scope: `object` — Replaces the content of the body row group (`.bb-table__body`). Use when you need full control over the body markup. Provide role-complete rows — `<div role="row">` holding one `<div role="cell">` per column — never a `<tr>`/`<td>`. A full-width cell spans with `grid-column: 1 / -1`.
 - `tfoot` — scope: `{ columnCount: number; }` — Fills the footer row group (`.bb-table__foot`). Use when you need a footer. Provide role-complete rows — `<div role="row">` holding `<div role="cell">` elements — never a `<tr>`/`<td>`.
 - `thead` — scope: `object` — Replaces the content of the header row group (`.bb-table__head`). Use when you need full control over the header markup. The table is a CSS grid, not a `<table>`: provide role-complete rows — `<div role="row">` holding one `<div role="columnheader">` per column — and never a `<tr>`/`<th>`. Rows are subgrid rows, so each cell lands on the matching column track.
-- `#<key>` (named from data) — scope: `object` — One column's body cell in every row, by the column `key` through `slotKey`. Scope: `{ item, value, content, selected, expanded, highlighted, classes, sortOrder, toggleSelected, toggleExpanded, toggleHighlighted, expandProps }`. Reserved keys (their slot is one of this component's own, so a key spelled like them is an error): `actions`, `empty`, `expand`, `loading`, `select`, `tbody`, `tfoot`, `thead`.
+- `#<key>` (named from data) — scope: `object` — One column's body cell in every row, by the column `key` through `slotKey`. Scope: `{ item, value, content, selected, expanded, highlighted, classes, sortOrder, toggleSelected, toggleExpanded, toggleHighlighted, expandProps }`. Reserved names (their slot is one of this component's own, so an item value or column key spelled like them is an error): `actions`, `empty`, `expand`, `loading`, `select`, `tbody`, `tfoot`, `thead`.
 - `#<key>:header` (named from data) — scope: `object` — One column's header content, replacing its label and the built-in sort button. Scope: `{ label, items, sortable, sortOrder, toggleSort, hideColumn, classes }`.
 - `#<key>:header:prepend` (named from data) — scope: `BbTableHeaderAffixSlotProps<Item>` — Content before one column's header, keeping the sort button; beats `header:prepend` (they never stack).
 - `#<key>:header:append` (named from data) — scope: `BbTableHeaderAffixSlotProps<Item>` — Content after one column's header, keeping the sort button; beats `header:append` (they never stack).