bitboss-ui 3.0.0-beta.62 → 3.0.0-beta.63

package/dist/ai/BbConfirm.md

@@ -72,23 +72,21 @@ first — this is that gate.
 Mount `<BbHost />` **exactly once, at the app root** (`App.vue` under Vue,
 `app.vue` under Nuxt, the `createInertiaApp` render root under Inertia) — a
 single instance serves the whole app, and `confirm()` can then be called from
-anywhere, components and stores alike. **Calls do not queue — a new
-`confirm()` supersedes the open one**, and the superseded promise settles
-`false` (an implicit dismiss; no callback runs). So two `confirm()` calls in a
-row show only the second, and the first silently answers "no". If you need both
-questions asked, `await` the first before opening the second.
+anywhere, components and stores alike. **Every call opens its own dialog**,
+and a new one covers the open one, which stays pending and comes back when
+the newer one closes (see [Several confirms at once](#several-confirms-at-once)).
 A second host renders nothing (a dev-mode console warning says so). With no
 host, `await confirm(...)` resolves `false` after one second, with a dev
 warning. A host that unmounts while its dialog is open (a layout the user
 navigated out of) gets the same second to come back; after that the open
 confirm resolves `false` without running a callback, so it never hangs.
 
-**Areas with their own look.** The dialog takes the passthrough scope and the
-tokens of the place its HOST is mounted. When the app is split into areas that
-each wrap their pages in `<BbPtScope>` ([passthrough guide](./guides/passthrough.md) § Named scopes),
-mount one `<BbHost />` inside each area's layout, within its scope, and none
-at the app root — which holds only if **every** page renders inside exactly one
-of those layouts, so there is still one host at a time.
+**Areas with their own look.** A confirm takes the passthrough scope and the
+tokens of the component that called `useConfirm()`, wherever the host is
+mounted: a page inside a `<BbPtScope>` ([passthrough guide](./guides/passthrough.md) § Named scopes)
+gets confirms in its area's look with nothing to set up. A component portal
+injects from that component's tree too. A `useConfirm()` called outside a
+component (a store, module level) takes the host's.
 
 ```vue
 <template>
@@ -105,10 +103,9 @@ import { BbHost } from 'bitboss-ui';
 standalone example has no app root to mount it in.** In a real app the host is
 already mounted at the root; a page that calls `confirm()` mounts nothing.
 
-The component itself takes almost no props: everything — content, buttons,
-behavior — travels in the message you pass to `confirm()`. The one exception is
-`size`, a host-wide default width every confirm inherits unless its message
-sets its own (see [Size, fullscreen and focus](#size-fullscreen-and-focus)).
+Everything — content, buttons, behavior — travels in the message you pass to
+`confirm()`; the width every confirm defaults to is the plugin's
+`confirm.defaultSize` (see [Size, fullscreen and focus](#size-fullscreen-and-focus)).
 At least one of `title`, `text`, `portal` should be set (dev warning
 otherwise).
 
@@ -402,7 +399,7 @@ the promise `false`, so your `if (ok)` branch is never reached accidentally.
 decline-only behavior in `no.onClick`, not in the `if (!ok)` branch. The rule
 that decides whether `no.onClick` runs: **user-initiated** dismissals
 (backdrop, `Escape`, the X) honor `dismissAsNo`; **system-initiated** ones
-(`duration` timeout, owner unmount, a superseding `confirm()`, `dismissAll()`)
+(`duration` timeout, owner unmount, `dismissAll()`)
 always resolve quietly, never running any callback. The knobs:
 
 - `dismissAsNo` (default `true`) — user-initiated implicit dismissals also run
@@ -435,7 +432,7 @@ the peek closes. For app-lifetime confirms that survive any unmount, call
 `useConfirm()` outside a component scope (app setup, a store, module level).
 
 `useConfirm()` also returns `dismissAll()` — an imperative escape hatch that
-quietly dismisses the open dialog regardless of owner, for
+quietly dismisses every open confirm regardless of owner, for
 app-level events like logout or a global error boundary.
 
 The classic case for `persistent` is the unsaved-changes prompt: an accidental
@@ -511,6 +508,8 @@ By default the dialog closes as soon as the promise settles. Set
 - `close()` only hides the dialog; **it never resolves anything**. Calling it
   on a dialog whose buttons haven't run yet leaves that `confirm()` promise
   pending forever — it is a flow terminator, not a substitute for the buttons.
+- `close()` hides the newest open confirm opened through the **same**
+  `useConfirm()`, never another component's.
 
 **Keep the dialog open across steps**
 
@@ -585,6 +584,31 @@ const exportWorkspace = async () => {
 </script>
 ```
 
+### Several confirms at once
+
+Confirms stack. A `confirm()` while another is open (from a button's
+`onClick`, or two calls without an `await` between them) covers the open one
+in place; the one beneath stays pending, and comes back, still waiting for
+its answer, when the newer one closes. Escape and the backdrop answer only
+the one on top. Two un-awaited calls are therefore both asked, newest first:
+`await` each one when the order matters.
+
+`stack` picks the `BbDialog` stack a confirm joins (every confirm joins the
+confirms' own by default). Name a dialog's `stack` and the confirm replaces
+that dialog's view while it is open, as a drill-in step would ([BbDialog](./BbDialog.md)
+§ Stacked dialogs); a name no other dialog uses shows it on top of the other
+confirms, each dimming the one beneath.
+
+```ts
+// An unsaved-changes question that takes the editor's place, not a layer on it.
+const discard = await confirm({
+	title: 'Discard your changes?',
+	stack: 'editor', // the editor's <BbDialog stack="editor">
+	variant: 'destructive',
+	yes: 'Discard',
+});
+```
+
 ### Rich content with portals
 
 When plain `text` isn't enough, render custom content in the dialog body via a
@@ -740,9 +764,9 @@ The map is typed where you write it by `definePt`, never with an imported
 
 - **Don't hand-build a yes/no dialog** out of `BbDialog` + buttons — busy
   states, dismissal semantics, ownership and focus handling already live here.
-- **Don't fire two `confirm()` calls without awaiting the first.** The second
-  supersedes the first, which settles `false` — so a "delete these two things"
-  flow written as two un-awaited confirms deletes nothing and asks once.
+- **Two `confirm()` calls without an `await` between them ask both, newest
+  first** — the second covers the first. `await` each one when the questions
+  must come in order.
 - **Don't forget the `await`** — `confirm(...)` without it never gates
   anything.
 - **Don't call `close()` to "cancel"** a dialog whose buttons haven't run —
@@ -753,8 +777,8 @@ The map is typed where you write it by `definePt`, never with an imported
 - With `returning: true`, an implicit dismiss under the default
   `dismissAsNo: true` resolves with `no.onClick`'s return value — give No a
   callback that returns a sensible "declined" value.
-  System dismissals (`duration`, `dismissAll()`, a superseding `confirm()`,
-  owner unmount) still resolve `false`, so handle `false` too.
+  System dismissals (`duration`, `dismissAll()`, owner unmount) still resolve
+  `false`, so handle `false` too.
 - `confirm()` rejects keys `BbConfirmMessage` doesn't declare, also on a
   message built in a variable first: build it from `BbConfirmMessage` fields
   only (spread a wider object and the extra keys fail to type-check).

package/dist/ai/BbForm.md

@@ -1076,7 +1076,11 @@ const bodyRules = computed(() => (publishing.value ? 'required' : ''));
 ```
 
 Both switch live: the next validation uses the new schema or rules, and
-switching back lets a submit through that was blocked a moment ago.
+switching back lets a submit through that was blocked a moment ago. A message
+already on screen is not taken down by the switch: it stays until the field
+validates again (an edit, a blur, the next submit). If the condition lives in
+another field and the stale message would mislead, show it through
+[`field-errors`](#a-message-of-your-own-that-comes-and-goes) instead.
 
 ### While it saves
 
@@ -1353,6 +1357,54 @@ async function save(values: Record<string, unknown>) {
 }
 ```
 
+##### A message of your own that comes and goes
+
+The object does not have to come from a server. A check that spans fields is
+a `computed`: its message shows exactly while the check fails, with no code to
+clear it. Gate it on a submit attempt so it does not greet an empty form:
+
+```vue
+<script setup lang="ts">
+import { computed, ref } from 'vue';
+import { BbButton, BbDatePickerInput, BbForm, BbSelect } from 'bitboss-ui';
+
+const patients = [
+	{ label: 'Anna Rossi', value: 1 },
+	{ label: 'Luca Bianchi', value: 2 },
+];
+const visit = ref<{ patient: number | null; date: string | null }>({
+	patient: null,
+	date: null,
+});
+const tried = ref(false);
+const missingDate = computed(() => !visit.value.patient && !visit.value.date);
+
+const ownErrors = computed(() => ({
+	date:
+		tried.value && missingDate.value
+			? 'Pick a date when no patient is selected.'
+			: undefined,
+}));
+
+const save = (values: Record<string, unknown>) => {
+	tried.value = true;
+	if (missingDate.value) return; // field-errors never block a submit
+	console.log('book', values);
+};
+</script>
+
+<template>
+	<BbForm :model="visit" :field-errors="ownErrors" @submit="save">
+		<BbSelect label="Patient" name="patient" :items="patients" clearable />
+		<BbDatePickerInput label="Date" name="date" />
+		<BbButton type="submit">Book</BbButton>
+	</BbForm>
+</template>
+```
+
+Picking a patient takes the message down at once. When the page also holds
+server errors, pass both: `:field-errors="{ ...form.errors, ...ownErrors }"`.
+
 - **The page owns them.** Editing the field does not hide its message; the
   next object does (Inertia replaces `form.errors` on every answer and clears
   it on success). Want it gone as the user types? Clear it yourself
@@ -1449,9 +1501,19 @@ const save = async (values: Record<string, unknown>) => {
 - A request-level message (Laravel's `message`, a 403) has no path: give it a
   key no field uses IN THE SAME CALL, `form.setErrors({ ...body.errors, _request: [body.message] })`, and it
   shows in the same summary.
-- **Each `setErrors` call replaces the last one's errors** (it is one server
-  answer). Two calls in a row keep only the second: merge everything into one
-  map first.
+- **`setErrors` hands over one server answer; it never takes a message
+  back.** A field's message stays until the user edits the field or it is
+  validated again. A submit validates every field, so a submit → 422 →
+  `setErrors` round always starts clean. A second call without a submit
+  between them replaces `unmatchedErrors` only: the first call's field
+  messages stay, and `null` or a missing key clears nothing. So put
+  everything one answer says into one map.
+- **Don't use `setErrors` for a message you will take back yourself**, like
+  your own cross-field check ("a date is required when no patient is
+  selected"). Compute it into [`field-errors`](#a-message-of-your-own-that-comes-and-goes)
+  instead: it shows while its key holds a message and goes the moment it
+  does not. Calling `validate()` to wipe a `setErrors` message runs every
+  rule on every field, so it puts messages on fields the user never touched.
 - `setErrors` does not emit `invalid`. It does move focus to the first failing
   field on screen, like a failed submit (`{ focus: false }` opts out; see
   [A failed submit focuses the first invalid field](#a-failed-submit-focuses-the-first-invalid-field)).

package/dist/ai/BbHost.md

@@ -87,12 +87,13 @@ The same keys go in the build plugin (`bitbossUi({ confirm, toastPosition })`).
 
 ### Areas with their own look
 
-The host paints confirms and toasts where it is mounted, so they take the
-passthrough scope and tokens of the place the HOST sits. When the app is split
-into areas that each wrap their pages in `<BbPtScope>`
-([passthrough guide](./guides/passthrough.md) § Named scopes), mount one
-`<BbHost />` inside each area's layout, within its scope, and none at the app
-root. That holds only if **every** page renders inside exactly one of those
+A confirm takes the passthrough scope and tokens of the component that called
+`useConfirm()`, wherever the host sits: nothing to set up. Toasts take the
+scope and tokens of the place the HOST sits. When the app is split into areas
+that each wrap their pages in `<BbPtScope>`
+([passthrough guide](./guides/passthrough.md) § Named scopes) and toasts need
+each area's look, mount one `<BbHost />` inside each area's layout, within its
+scope, and none at the app root. That holds only if **every** page renders inside exactly one of those
 layouts, so there is still one host at a time. See
 [Agent Contract § Global Host Rule](./guides/agent-contract.md).
 
@@ -142,14 +143,11 @@ without a mismatch.
 - Listed nodes are the ones `BbHost`'s API reaches or that declare a documented CSS variable; the rest fold into "also mounts". The complete tree, repeats and undocumented locals included, is `manifest/components/BbHost.tree.json`.
 
 - `BbHost` _(this component)_
-  - `BbConfirm` _(internal — not importable, reach it through `BbConfirm`)_ — its own pt parts (`BbConfirm`): `text` → `div.bb-confirm__text`, `action` → `BbButton`; hands `BbDialog` the pt map `passthrough.forward(DIALOG_PARTS, BB_DIALOG_PT.states)` (ours → theirs)
-    - `BbDialog` _(public — [contract](./BbDialog.md))_ — its own pt parts (`BbDialog`): `header` → `div.bb-dialog__header`, `title` → `span.bb-dialog__title`, `description` → `p.bb-dialog__description`, `close` → `CloseButton`, `content` → `div.bb-dialog__content`, `footer` → `div.bb-dialog__footer`; hands `BbOffCanvas` the pt map `{ root: 'root', header: 'header', title: 'title', description: 'description', content: 'content', footer: 'footer', close: 'close', sheet: 'root', }` (ours → theirs); documented CSS variables: `--px`, `--close-size`
-      - `CloseButton` _(internal — not importable, reach it through `BbDialog`)_ — documented CSS variables: `--size`, `--p`
-      - `BbOffCanvas` _(public — [contract](./BbOffCanvas.md))_ — its own pt parts (`BbOffCanvas`): `header` → `div.bb-offcanvas__header`, `title` → `span.bb-offcanvas__title`, `description` → `p.bb-offcanvas__description`, `close` → `CloseButton`, `content` → `div.bb-offcanvas__content`, `footer` → `div.bb-offcanvas__footer`; documented CSS variables: `--stack-x`, `--snap-y`, `--stack-fill`, `--stack-transition-duration`, `--px`, `--handle-w`, `--handle-h`, `--handle-bg`, `--safe-top`, `--close-size`; also mounts `CloseButton`
-    - `BbButton` _(public — [contract](./BbButton.md))_ — its own pt parts (`BbButton`): `root` → `BbBaseButton`, `spinner` → `BbSpinner`, `icon` → `BbIcon`, `text` → `span.bb-button__text`; documented CSS variables: `--h-xs`, `--h`, `--icon-size`, `--px`, `--fs`, `--r`, `--gap`, `--bg`, `--bg-hover`, `--bg-pressed`, `--fg`, `--border-color`, `--ring-color`, `--ring-size`, `--bw`, `--fg-hover`, `--border-hover`, `--fg-pressed`, `--border-pressed`, `--bg-disabled`, `--fg-disabled`, `--border-disabled`, `--opacity-disabled`, `--elev-tier`, `--elev`; also mounts `BbIcon`, `BbSpinner`
-      - `BbBaseButton` _(public — [contract](./BbBaseButton.md))_ — its own pt parts (`BbBaseButton`): `root` → `RouterComponent`, `root` → `a`, `root` → `component`; also mounts `RouterComponent`
   - `BbToast` _(internal — not importable, reach it through `BbToast`)_ — documented CSS variables: `--gap`, `--offset`, `--width`, `--lift`, `--stack-y`, `--stack-scale`, `--enter-y`, `--swipe-amount`, `--z`, `--r`, `--ring-size`, `--bg`, `--border-color`, `--fg`, `--icon-color`
-    - `BbToastRegion` _(internal — not importable, reach it through `BbToast`)_ — its own pt parts (`BbToast`): `root` → `ol.bb-toast`; also mounts `BbToastMessage`
+    - `BbToastRegion` _(internal — not importable, reach it through `BbToast`)_ — its own pt parts (`BbToast`): `root` → `ol.bb-toast`
+      - `BbToastMessage` _(internal — not importable, reach it through `BbToast`)_ — also mounts `BbIcon`, `BbSpinner`
+        - `BbButton` _(public — [contract](./BbButton.md))_ — its own pt parts (`BbButton`): `root` → `BbBaseButton`, `spinner` → `BbSpinner`, `icon` → `BbIcon`, `text` → `span.bb-button__text`; documented CSS variables: `--h-xs`, `--h`, `--icon-size`, `--px`, `--fs`, `--r`, `--gap`, `--bg`, `--bg-hover`, `--bg-pressed`, `--fg`, `--border-color`, `--ring-color`, `--ring-size`, `--bw`, `--fg-hover`, `--border-hover`, `--fg-pressed`, `--border-pressed`, `--bg-disabled`, `--fg-disabled`, `--border-disabled`, `--opacity-disabled`, `--elev-tier`, `--elev`; also mounts `BbIcon`, `BbSpinner`
+          - `BbBaseButton` _(public — [contract](./BbBaseButton.md))_ — its own pt parts (`BbBaseButton`): `root` → `RouterComponent`, `root` → `a`, `root` → `component`; also mounts `RouterComponent`
 
 ## See Also
 

package/dist/ai/BbPtScope.md

@@ -96,9 +96,10 @@ The scope follows the **component tree**, not the DOM:
   in. A directive written directly in `<BbPtScope>`'s slot, in the same
   template as the scope, sees the scope above it instead — keep the scope in a
   layout or a parent component.
-- `<BbHost />` renders every toast and confirm where it is mounted. For toasts
-  and confirms in the area's look, mount one `<BbHost />` inside
-  each area's layout, within its scope, and none at the app root — valid only
+- A `confirm()` takes the scope of the component that called `useConfirm()`,
+  wherever `<BbHost />` is mounted. Toasts take the scope where the host is
+  mounted: for toasts in the area's look, mount one `<BbHost />` inside each
+  area's layout, within its scope, and none at the app root — valid only
   when every page renders inside exactly one of those layouts (see
   [Agent Contract § Global Host Rule](./guides/agent-contract.md)).
 
@@ -112,7 +113,8 @@ The scope follows the **component tree**, not the DOM:
 
 ### Works well with
 
-- `BbHost` — mount one inside each scoped area layout.
+- `BbHost` — mount one inside each scoped area layout when toasts need the
+  area's look.
 - The [passthrough guide](./guides/passthrough.md) — grammar, merging and the
   full parts table.
 

package/dist/ai/BbTable.md

@@ -78,7 +78,9 @@ needs is declared here, not in markup:
   even when the value is nullish, so a virtual column whose `key` matches no
   field can still compute from `item`; set `formatOnNull: false` when a
   formatter must only see real values.
-- **`placeholder`** fills the cell when the pipeline still ends nullish.
+- **`placeholder`** fills the cell when the pipeline still ends nullish. Its
+  cell carries `--placeholder`, a cell with a value `--value`: style a blank
+  through those, not a slot ([Empty cells](#empty-cells-value-and-placeholder)).
 - **`align`** (`'left' | 'center' | 'right'`) per column; the table-level
   `align` prop sets the default for the whole table (`left`).
 - **`width`** freezes the column: numbers and bare numeric strings are px
@@ -102,7 +104,8 @@ needs is declared here, not in markup:
   takes them, once, when the page hydrates.) The floors read every row up
   to 2,000; past that, the first 1,000 and a sample across the rest (a
   `virtual` table has no floors at all). No floor on `fixed` or
-  `virtual` tables, slot columns, or under a custom `#thead`. A grid keyword or function is the track as written:
+  `virtual` tables, slot columns, or under a custom `#thead`, so never slot a
+  column only to restyle its blank: use [`--placeholder`](#empty-cells-value-and-placeholder). A grid keyword or function is the track as written:
   `'auto'`, `'2fr'`, `'minmax(0, 1fr)'` (a share that may shrink below its
   content), `'fit-content(200px)'`. When _every_ column declares a length, the
   lengths become floors and the surplus is shared in proportion to their
@@ -3529,6 +3532,60 @@ root (`--cue-w: 0px` turns it off):
 }
 ```
 
+#### Empty cells: `--value` and `--placeholder`
+
+Every data cell says what the column's pipeline (`formatter`, then
+`placeholder`) produced: **`bb-table__cell--value`** when it shows a value,
+**`bb-table__cell--placeholder`** when the value was empty and the
+column's `placeholder` shows instead. The same two are `pt` states on
+`cell`. The class names the outcome, not the text, so a placeholder can read
+"–", "N/D" or anything else and the styling holds. A cell whose value is empty
+with no `placeholder` has neither. Slot cells carry it too (the class follows
+the `content` the slot is handed); the select, drag and actions cells never
+do.
+
+```vue
+<script setup lang="ts">
+import { BbTable, type BbTableColumn } from 'bitboss-ui';
+
+type Person = { id: number; name: string; email: string | null; city: string };
+
+const blank = (value: unknown) =>
+	typeof value === 'string' && value.trim() === '' ? null : value;
+
+const columns: Array<BbTableColumn<Person>> = [
+	{ key: 'name', label: 'Nome' },
+	{ key: 'email', label: 'Email', placeholder: 'N/D' },
+	{ key: 'city', label: 'Provincia', placeholder: '–', formatter: blank },
+];
+
+const people: Person[] = [
+	{ id: 1, name: 'Giulia Bianchi', email: null, city: 'Milano' },
+	{ id: 2, name: 'Marco Rossi', email: 'marco@example.com', city: '  ' },
+];
+</script>
+
+<template>
+	<BbTable
+		:columns="columns"
+		item-value="id"
+		:items="people"
+		pt:cell:placeholder="text-(--bb-text-muted)"
+	/>
+</template>
+```
+
+Or in CSS, once for the whole app:
+`.bb-table__cell--placeholder { color: var(--bb-text-muted); }`.
+
+- **The placeholder shows only for `null` / `undefined`.** An empty or
+  whitespace-only string is a value. To treat it as blank, return `null` from
+  the `formatter` (`blank` above), and the placeholder takes over.
+- **Don't slot a column just to restyle its blank.** A slot column gets no
+  width floor (see Columns), so a wrapper that slots every column to print a
+  muted dash costs every column its floor. `placeholder` plus the class does
+  the same with none of that.
+
 #### The table as a card
 
 The root paints no background, border or radius of its own — it is the
@@ -3578,7 +3635,7 @@ through element names, which match nothing:
 | header cell      | `.bb-table__cell-column-header` (+ `--select`, `--actions`)                                                                                                                          | `columnheader`                                 |
 | body group       | `.bb-table__body`                                                                                                                                                                    | `rowgroup`                                     |
 | data row         | `.bb-table__row` (+ `--highlighted`)                                                                                                                                                 | `row`                                          |
-| data cell        | `.bb-table__cell` (+ `--select`)                                                                                                                                                     | `cell` (`gridcell` with `keyboard-navigation`) |
+| data cell        | `.bb-table__cell` (+ `--select`; `--value` / `--placeholder`: what the pipeline produced)                                                                                            | `cell` (`gridcell` with `keyboard-navigation`) |
 | actions cell     | `.bb-table__cell--actions`                                                                                                                                                           | `cell` (`gridcell` with `keyboard-navigation`) |
 | expand row       | `.bb-table-expand__row` > `.bb-table-expand__cell`                                                                                                                                   | `row` > `cell` (`gridcell`)                    |
 | empty state      | `.bb-table-empty__row` > `.bb-table-empty__cell`                                                                                                                                     | `row` > `cell`                                 |
@@ -3721,7 +3778,8 @@ three glyphs: `sort-icon`, `select-icon` (each row's checkbox or radio and
 the select-all) and `drag-icon` (on the chip a column drag carries). The grid
 is `div`s with ARIA roles, so these are parts, not `th` / `td` selectors.
 
-States: `loading` and `empty` (the table); `selected`, `highlighted`,
+States: `loading` and `empty` (the table); `value` / `placeholder` per data
+cell (what its pipeline produced, see [Empty cells](#empty-cells-value-and-placeholder)); `selected`, `highlighted`,
 `expanded` and `disabled` resolved per row — a cell takes its row's states,
 a row's `select-icon` its `selected` / `disabled`, and its `expand` its
 `selected` / `highlighted` / `expanded`; `sorted` /
@@ -4176,7 +4234,7 @@ for a preset that fits any row type (never `<any>`), not an imported
 
 | Prop | Type | Default | Required | Description |
 | --- | --- | --- | --- | --- |
-| `pt:<part>`, `pt:<part>:<state>`, `pt` | `PtValue` | | | Passthrough — a class list, or `{ class, style, attrs }`, bound to one named part of the component; the state form applies only while that state is on. Parts: `body`, `caption`, `cell`, `cellColumnHeader`, `dragHandle`, `dragIcon`, `expand`, `firstRow`, `foot`, `head`, `headerRow`, `lastRow`, `root`, `row`, `selectIcon`, `sortIcon`, `table`. States: `disabled`, `empty`, `expanded`, `highlighted`, `indeterminate`, `loading`, `selected`, `sorted`, `sortedDesc`. What each one is: _Passthrough parts and states_ below. `pt` is the object form with the same keys minus the prefix (`{ icon: '…', 'icon:loading': '…' }`). See `guides/passthrough.md`. In `<script>` a `pt` value is typed `BbTableProps<Row>['pt']` (`BbTableProps['pt']` for a preset that fits any row type, never `<any>`) (`PtValue` is not exported): § Typing `pt` in `<script>`. |
+| `pt:<part>`, `pt:<part>:<state>`, `pt` | `PtValue` | | | Passthrough — a class list, or `{ class, style, attrs }`, bound to one named part of the component; the state form applies only while that state is on. Parts: `body`, `caption`, `cell`, `cellColumnHeader`, `dragHandle`, `dragIcon`, `expand`, `firstRow`, `foot`, `head`, `headerRow`, `lastRow`, `root`, `row`, `selectIcon`, `sortIcon`, `table`. States: `disabled`, `empty`, `expanded`, `highlighted`, `indeterminate`, `loading`, `placeholder`, `selected`, `sorted`, `sortedDesc`, `value`. What each one is: _Passthrough parts and states_ below. `pt` is the object form with the same keys minus the prefix (`{ icon: '…', 'icon:loading': '…' }`). See `guides/passthrough.md`. In `<script>` a `pt` value is typed `BbTableProps<Row>['pt']` (`BbTableProps['pt']` for a preset that fits any row type, never `<any>`) (`PtValue` is not exported): § Typing `pt` in `<script>`. |
 | `accessibleLabel` | `((columns: MappedCell[], item: any) => string) \| undefined` |  |  | The label of each row's selection checkbox, from `(columns, item)`. Unset: the row's name in the locale's select template (its `rowHeader` cells, else its first column: "Select INV-1041"). The cells arrive in render order: look one up by `key`, never by position. |
 | `actionsText` | `string \| undefined` |  |  | Label used in the header of the actions column. |
 | `align` | `"left" \| "center" \| "right" \| undefined` | `"left"` |  | Text alignment of the columns. |
@@ -4263,6 +4321,8 @@ States are listed in precedence order: when two are on at once and their entries
 
 | State | When it is on |
 | --- | --- |
+| `value` | Per node, on a DATA `cell`: the formatter / placeholder pipeline produced a value (not `null` / `undefined`), slot cells included (`bb-table__cell--value`). Not on the select, drag or actions cells. |
+| `placeholder` | Per node, on a DATA `cell`: the value was empty and the column's `placeholder` shows instead, whatever its text (`bb-table__cell--placeholder`). A cell with an empty value and no `placeholder` has neither state. |
 | `empty` | Component-wide: there are no rows (`bb-table--empty`). |
 | `sorted` | Per node, on `cellColumnHeader` and `sortIcon`: the column is sorted, either direction (`bb-table__cell-column-header--sorted`). |
 | `sortedDesc` | Per node, on `cellColumnHeader` and `sortIcon`: sorted descending (`bb-table__cell-column-header--sorted-desc`). Ascending is `sorted` alone. |

package/dist/ai/changelog.json

@@ -1,7 +1,7 @@
 {
 	"schemaVersion": 3,
 	"library": "bitboss-ui",
-	"version": "3.0.0-beta.62",
+	"version": "3.0.0-beta.63",
 	"upgrade": "v2-to-v3",
 	"guide": "ai/guides/migration/v2-to-v3.md",
 	"legend": {
@@ -72,7 +72,8 @@
 		"3.0.0-beta.59",
 		"3.0.0-beta.60",
 		"3.0.0-beta.61",
-		"3.0.0-beta.62"
+		"3.0.0-beta.62",
+		"3.0.0-beta.63"
 	],
 	"unpublished": [
 		"3.0.0-alpha.2",
@@ -95,7 +96,7 @@
 	],
 	"summary": {
 		"renames": 220,
-		"behaviourBreaks": 230,
+		"behaviourBreaks": 231,
 		"bySurface": {
 			"prop": 15,
 			"option": 1,
@@ -106,7 +107,7 @@
 			"class": 138
 		},
 		"unreleased": 0,
-		"added": 414
+		"added": 416
 	},
 	"added": {
 		"3.0.0-alpha.1": [
@@ -2085,6 +2086,16 @@
 			},
 			"table · keep short multi-word values on one line",
 			"table · sortable headers describe shift+enter"
+		],
+		"3.0.0-beta.63": [
+			"table · cells name what the pipeline produced, value or placeholder",
+			{
+				"text": "confirm · every confirm() call opens its own dialog",
+				"components": [
+					"BbHost",
+					"BbPtScope"
+				]
+			}
 		]
 	},
 	"breaking": [
@@ -8487,6 +8498,19 @@
 			"ruling": "owner 2026-10-16 (Q75.3) + 2026-10-21 (Q76.9 e)",
 			"guide": "v2-to-v3.md § 6 item 96 + BbTable.md § Columns, § Column resize",
 			"firstReleasedIn": "3.0.0-beta.62"
+		},
+		{
+			"id": "f370",
+			"kind": "behaviour",
+			"summary": "confirm(): every call opens its own dialog; a new one covers the open one instead of resolving it false; it takes the caller's pt scope; new stack option",
+			"components": [
+				"BbConfirm",
+				"BbHost"
+			],
+			"description": "confirm(): every call opens its own dialog, under the caller's provides. A call while another confirm is open COVERS it (a shared confirm BbDialog stack) instead of resolving it false: the first stays pending and comes back when the newer one closes, so two un-awaited calls ask both, newest first; Escape and the backdrop answer only the top one. close() hides the newest open confirm opened through the same useConfirm() (it used to hide THE confirm); dismissAll() dismisses every open one. The dialog takes the <BbPtScope> and tokens of the component that called useConfirm() (a store's: the host's), so areas need no host of their own for confirms; a component portal injects from the caller's tree. New message option stack (join a dialog's stack: the confirm replaces its view)",
+			"ruling": "owner 2026-10-22 (Q75.9)",
+			"guide": "v2-to-v3.md § 6 item 97 + components/use-confirm.md + components/bb-host.md + BbConfirm.md § Several confirms at once + useConfirm.md",
+			"firstReleasedIn": "3.0.0-beta.63"
 		}
 	]
 }