bitboss-ui 3.0.0-beta.66 → 3.0.0-beta.67

package/dist/ai/BbDatePicker.md

@@ -136,10 +136,11 @@ It mirrors `<input type="…">`, so the names should already be familiar:
 | ------------------ | -------------------- | --------------------- | ------------- |
 | `date` _(default)_ | the day grid         | `2026-08-14`          | ISO instant   |
 | `datetime`         | day grid + time rail | `2026-08-14` + `time` | ISO instant   |
+| `week`             | day grid, week rows  | `2026-W44`            | —             |
 | `month`            | the 12-month grid    | `2026-08`             | —             |
 | `year`             | the year list        | `2026`                | —             |
 
-`month` and `year` are **calendar labels, not instants**. A month has no
+`week`, `month` and `year` are **calendar labels, not instants**. A month has no
 timezone, and pinning one to an instant is how you lose it: the start of August
 in Rome is the 31st of July in UTC, so a value stored that way reads back as the
 wrong month. They force `floating`, ignore `utc`, and warn if you pass it.
@@ -163,6 +164,12 @@ selectable — it cannot silently delete the month you named.
 The month grid pages by year and the year list by decade; arrows, Home/End and
 PageUp/PageDown all keep working, one unit up.
 
+`type="week"` keeps the day grid and its keyboard, adds a week-number column
+(Monday first, always), and makes any day pick its ISO week: the value is
+`2026-W44`, the activator slot's `text` reads "Week 44, 2026", and `min` /
+`max` (a week or a date) enable a week only when all seven days are inside.
+See [BbCalendar § Weeks](./BbCalendar.md#weeks).
+
 ### Multi-selection
 
 `multiple` turns every pick into a toggle: the value is a **sorted array** and
@@ -357,7 +364,8 @@ desktop, the sheet itself on a phone — it also carries the sizing tokens, so
 bottom sheet on a phone only, applied after `panel`), `header` (the
 navigation bar), `arrow` (the previous / next buttons), `month` and `year`
 (the heading buttons), `cellColumnHeader` (each weekday letter), `day` (one whole
-day cell) and `dayButton` (the button inside it), `monthItem` and
+day cell) and `dayButton` (the button inside it), `week` (one row with
+`type="week"`) and `weekNumber` (its ISO week number), `monthItem` and
 `yearItem` (one button of the month / year panel).
 
 States: `open` follows the surface; `arrow` is `disabled` at a `min` / `max`
@@ -365,7 +373,9 @@ bound; `month` and `year` are `active` while their panel is open. The cells
 resolve per node — on `day` and `dayButton`: `selected`, `disabled`, `today`,
 `outside` (a day of the previous or next month), `rangeStart` / `rangeEnd` /
 `inRange` (a committed range) and `highlighted` (the keyboard cursor). The
-panel items carry the same set without `today` and `outside`.
+panel items carry the same set without `today` and `outside`; the week rows
+(`week`, `weekNumber`) carry `selected`, `rangeStart`, `rangeEnd` and
+`inRange`, per row.
 
 `day` is the whole cell and `dayButton` the rounded mark inside it: a
 background on `pt:day` paints the full cell square, so restyle the mark on
@@ -453,7 +463,7 @@ and digit typeahead; the time rail exposes labelled columns. Always pass a
 
 | 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: `arrow`, `cellColumnHeader`, `day`, `dayButton`, `header`, `item`, `month`, `monthItem`, `panel`, `root`, `sheet`, `year`, `yearItem`. States: `active`, `disabled`, `highlighted`, `inRange`, `open`, `outside`, `rangeEnd`, `rangeStart`, `selected`, `today`. 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 `BbDatePickerProps['pt']` (`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: `arrow`, `cellColumnHeader`, `day`, `dayButton`, `header`, `item`, `month`, `monthItem`, `panel`, `root`, `sheet`, `week`, `weekNumber`, `year`, `yearItem`. States: `disabled`, `open`, `highlighted`, `inRange`, `outside`, `rangeEnd`, `rangeStart`, `selected`, `today`, `active`. 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 `BbDatePickerProps['pt']` (`PtValue` is not exported): § Typing `pt` in `<script>`. |
 | `activator` | `ElementOrComponentRef \| undefined` |  |  | External activator element or component ref. When provided, the `activator` slot is not rendered and click + ARIA are attached programmatically to the referenced element — mirroring the `BbColorPalette` activator API. |
 | `activeSegment` | `'start'` \| `'end'` |  |  | Which end the time rail edits in range + `type="datetime"` (`v-model:active-segment`). Standalone use manages this internally; an embedding host (the date input) drives it from its focused field. Ignored outside range + datetime. |
 | `adaptive` | `boolean \| undefined` | ``config.adaptive` (`true`)` |  | On mobile, open in a bottom off-canvas sheet instead of a floating popover. When unset, falls back to the global `config.adaptive`. |
@@ -463,13 +473,13 @@ and digit typeahead; the time rail exposes labelled columns. Always pass a
 | `disabled` | `boolean \| undefined` | `false` |  | Disables the activator and the calendar. |
 | `disableFlip` | `boolean \| undefined` | `false` |  | Disable the automatic flip to the opposite side on overflow. |
 | `eager` | `boolean \| undefined` | `false` |  | Render popover content before it is first shown. |
-| `firstDayOfWeek` | `0 \| 1 \| 2 \| 3 \| 4 \| 5 \| 6 \| undefined` | `the locale's week start` |  | First day of the week (0 = Sunday … 6 = Saturday). Omitted, the active locale's week start: Monday for `it`, `de`, `fr`, `en-gb`…, Sunday for bare `en` (US) and `pt` (Brazil). |
-| `floating` | `boolean \| undefined` | `false` |  | Emit plain calendar strings instead of zoned ISO instants. Implied (and forced) by `type="month"` and `type="year"`. |
+| `firstDayOfWeek` | `0 \| 1 \| 2 \| 3 \| 4 \| 5 \| 6 \| undefined` | `the locale's week start` |  | First day of the week (0 = Sunday … 6 = Saturday). Omitted, the active locale's week start: Monday for `it`, `de`, `fr`, `en-gb`…, Sunday for bare `en` (US) and `pt` (Brazil). Ignored under `type="week"`: ISO weeks run Monday to Sunday, so a week grid always starts on Monday. |
+| `floating` | `boolean \| undefined` | `false` |  | Emit plain calendar strings instead of zoned ISO instants. Implied (and forced) by `type="week"`, `type="month"` and `type="year"`. |
 | `label` | `string \| undefined` |  |  | Accessible label. The activator is named by it followed by the activator's own text ("Due date 12 Sep"), through `aria-labelledby`. |
-| `max` | `string \| undefined` |  |  | Maximum selectable value, in this `type`'s shape. A finer bound is accepted and ceiled to the unit, with a warning. |
-| `min` | `string \| undefined` |  |  | Minimum selectable value, in this `type`'s shape — `YYYY-MM-DD` (`YYYY-MM-DDTHH:mm` with `datetime`, `YYYY-MM` with `month`, `YYYY` with `year`). A finer bound is accepted and floored to the unit, with a warning. |
-| `modelValue` | `string \| string[] \| null` |  | yes | v-model: `null` when empty, a string, a `[start, end]` pair with `range`, or a sorted array with `multiple`. The string is `YYYY-MM-DD` when `floating` (`YYYY-MM` / `YYYY` for `month` / `year`), otherwise a zoned ISO instant (carrying the time under `datetime`). |
-| `multiple` | `boolean` | `false` |  | Multi-selection: each pick toggles a value in a sorted array (days, months or years), and the panel stays open until dismissed. Needs an array `modelValue` (`[]` when empty, never `null`). Throws with `range` or `type="datetime"`. |
+| `max` | `string \| undefined` |  |  | Maximum selectable value, in this `type`'s shape. A finer bound is accepted and ceiled to the unit, with a warning (`week`: as `min`). |
+| `min` | `string \| undefined` |  |  | Minimum selectable value, in this `type`'s shape — `YYYY-MM-DD` (`YYYY-MM-DDTHH:mm` with `datetime`, `YYYY-MM` with `month`, `YYYY` with `year`; a week or a date with `week`, whole weeks only). A finer bound is accepted and floored to the unit, with a warning. |
+| `modelValue` | `string \| string[] \| null` |  | yes | v-model: `null` when empty, a string, a `[start, end]` pair with `range`, or a sorted array with `multiple`. The string is `YYYY-MM-DD` when `floating` (`YYYY-Www` / `YYYY-MM` / `YYYY` for `week` / `month` / `year`), otherwise a zoned ISO instant (carrying the time under `datetime`). |
+| `multiple` | `boolean` | `false` |  | Multi-selection: each pick toggles a value in a sorted array (days, weeks, months or years), and the panel stays open until dismissed. Needs an array `modelValue` (`[]` when empty, never `null`). Throws with `range` or `type="datetime"`. |
 | `numberOfMonths` | `number \| undefined` | `1` |  | How many months the popover shows side by side (day grids only); the phone sheet always shows one. Too narrow for them all, the months wrap. |
 | `offCanvasProps` | `Partial<BbOffCanvasProps> \| undefined` |  |  | Props for the phone sheet (the `BbOffCanvas` that `adaptive` renders on mobile), spread over its defaults. A `pt` inside it styles only the sheet (passthrough guide § Inside the sheet). The sheet hides its ✕; `{ hideClose: false }` brings it back. |
 | `offset` | `number \| undefined` | `4` |  | Space the popover keeps from the activator. |
@@ -478,12 +488,12 @@ and digit typeahead; the time rail exposes labelled columns. Always pass a
 | `range` | `boolean` | `false` |  | Enables range selection (`[start, end]`). |
 | `readonly` | `boolean \| undefined` | `false` |  | Prevents opening while keeping the activator visible. |
 | `seconds` | `boolean \| undefined` | `false` |  | Adds the seconds column (requires `type="datetime"`). |
-| `selectable` | `((date: string) => boolean) \| undefined` |  |  | Predicate invoked per candidate; return `false` to disable it. Receives the value in this `type`'s shape — `YYYY-MM` under `month`, `YYYY` under `year`. |
+| `selectable` | `((date: string) => boolean) \| undefined` |  |  | Predicate invoked per candidate; return `false` to disable it. Receives the value in this `type`'s shape — `YYYY-Www` under `week` (so a week is enabled or disabled whole), `YYYY-MM` under `month`, `YYYY` under `year`. |
 | `step` | `number \| undefined` | `1` |  | Minute-column granularity and arrow stepping (requires `type="datetime"`). |
 | `time` | `string \| string[] \| null \| undefined` |  |  | Companion time model (`v-model:time`), 24-hour `HH:mm` / `HH:mm:ss`. With `floating` it is the only carrier of the time; otherwise it mirrors the time inside `modelValue`. Requires `type="datetime"`. |
 | `transitionDuration` | `number \| undefined` | `250` |  | Popover/sheet transition duration in milliseconds. |
-| `type` | `'date'` \| `'month'` \| `'year'` \| `'datetime'` | `"date"` |  | What the picker selects and emits: `date` (a day), `datetime` (a day plus a time rail), `month` (`YYYY-MM`) or `year` (`YYYY`). `month` / `year` force `floating`, ignore `utc`, and leave the time props inert. |
-| `utc` | `boolean \| undefined` | `false` |  | Emit UTC (`...Z`) instead of the local offset. Ignored with `floating`, and therefore with `type="month"`/`type="year"`. |
+| `type` | `'date'` \| `'month'` \| `'year'` \| `'week'` \| `'datetime'` | `"date"` |  | What the picker selects and emits: `date` (a day), `datetime` (a day plus a time rail), `week` (an ISO week, `YYYY-Www`: any day of a row picks its week), `month` (`YYYY-MM`) or `year` (`YYYY`). `week` / `month` / `year` force `floating`, ignore `utc`, and leave the time props inert. |
+| `utc` | `boolean \| undefined` | `false` |  | Emit UTC (`...Z`) instead of the local offset. Ignored with `floating`, and therefore with `type="week"`/`type="month"`/`type="year"`. |
 
 ## Passthrough parts and states
 
@@ -497,6 +507,8 @@ and digit typeahead; the time rail exposes labelled columns. Always pass a
 | `month` | The month heading button; it opens the month panel. |
 | `year` | The year heading button; it opens the year panel. |
 | `cellColumnHeader` | Each weekday letter above the grid — a broadcast. |
+| `week` | One row of seven days with `type="week"` — the band a picked week paints and the hover outline. A broadcast resolved per row. |
+| `weekNumber` | The ISO week number heading each row with `type="week"` — a broadcast resolved per row. |
 | `day` | One whole day cell — a broadcast resolved per day. A background here paints the full cell square; restyle the round mark on `dayButton`. |
 | `dayButton` | The button inside a day cell — the mark that shows selection. A broadcast resolved per day. |
 | `monthItem` | One month button of the month panel (the home grid of `type="month"`) — a broadcast resolved per month. |
@@ -511,10 +523,10 @@ States are listed in precedence order: when two are on at once and their entries
 | --- | --- |
 | `outside` | Per node, on `day` / `dayButton`: a day of the previous or next month, shown to fill the grid. |
 | `today` | Per node, on `day` / `dayButton`: today. |
-| `inRange` | Per node, on the cells (`day`, `dayButton`, `monthItem`, `yearItem`): inside a committed range, between its ends. |
-| `selected` | Per node, on the cells: a chosen day, month or year; on `item`, the picked time's entry in each column. |
-| `rangeStart` | Per node, on the cells: a committed range's first day, month or year. |
-| `rangeEnd` | Per node, on the cells: a committed range's last day, month or year. |
+| `inRange` | Per node, on the cells (`day`, `dayButton`, `monthItem`, `yearItem`) and the week rows (`week`, `weekNumber`): inside a committed range, between its ends. |
+| `selected` | Per node, on the cells: a chosen day, month or year; on `week` / `weekNumber`, a chosen week (a range's ends too, as on its days); on `item`, the picked time's entry in each column. |
+| `rangeStart` | Per node, on the cells and the week rows: a committed range's first day, week, month or year. |
+| `rangeEnd` | Per node, on the cells and the week rows: a committed range's last day, week, month or year. |
 | `disabled` | Component-wide while the picker is `disabled`. Also per node: on the cells, one outside `min` / `max` or refused by `selectable`; on `arrow`, at a bound or while the month / year panel is open. |
 | `active` | Per node, on `month` / `year`: its panel is open. |
 | `open` | Component-wide: the calendar is showing. |
@@ -574,7 +586,7 @@ Set these on the element, or on a class you put on it, to retune this component
 - Listed nodes are the ones `BbDatePicker`'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/BbDatePicker.tree.json`.
 
 - `BbDatePicker` _(this component)_ — its own template binds: `panel` → `div`; hands `BbCalendar` the pt map ` passthrough.forward(DATE_PICKER_CALENDAR_PARTS, BB_CALENDAR_PT.states) ` (ours → theirs); hands `BbOffCanvas` the pt map `{ panel: 'root', sheet: 'root' }` (ours → theirs)
-  - `BbCalendar` _(public — [contract](./BbCalendar.md))_ — its own pt parts (`BbCalendar`): `header` → `div.bb-calendar__header`, `arrow` → `BbBaseButton`, `month` → `BbBaseButton`, `year` → `BbBaseButton`, `day` → `div.bb-calendar__day`, `dayButton` → `button.bb-calendar__day-button`; documented CSS variables: `--cell`, `--unit-row`; also mounts `ScaleFade`, `Slide`, `CalendarMonthPanel`, `CalendarYearPanel`
+  - `BbCalendar` _(public — [contract](./BbCalendar.md))_ — its own pt parts (`BbCalendar`): `header` → `div.bb-calendar__header`, `arrow` → `BbBaseButton`, `month` → `BbBaseButton`, `year` → `BbBaseButton`, `week` → `div.bb-calendar__week`, `weekNumber` → `div.bb-calendar__week-number`, `day` → `div.bb-calendar__day`, `dayButton` → `button.bb-calendar__day-button`; documented CSS variables: `--cell`, `--unit-row`, `--wk`; also mounts `ScaleFade`, `Slide`, `CalendarMonthPanel`, `CalendarYearPanel`
     - `BbBaseButton` _(public — [contract](./BbBaseButton.md))_ — its own pt parts (`BbBaseButton`): `root` → `RouterComponent`, `root` → `a`, `root` → `component`; also mounts `RouterComponent`
     - `CommonTimeSelector` _(internal — not importable, reach it through `BbCalendar`)_ — its own pt parts (`BbCalendar`): `header` → `div.bb-time-selector__header`, `cellColumnHeader` → `div.bb-time-selector__cell-column-header`, `item` → `BbBaseButton`; documented CSS variables: `--time-mark`; also mounts `BbBaseButton`
   - `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`

package/dist/ai/BbDatePickerInput.md

@@ -40,7 +40,7 @@
 | `--border-focus` | `pt:box` | `CommonFieldInput` | frame while focused, or --active |
 | `--ring-size` | `pt:box` | `CommonFieldInput` | ring width; 0 is a variant declining the ring |
 | `--ring-color` | `pt:box` | `CommonFieldInput` | ring colour; state owns it, not variants |
-| `--elev` | `pt:box` | `CommonFieldInput` | Resting lift, alone in `box-shadow`: the ring is the box's outline (Q81.6), so a theme's `--elev: none` never takes the ring with it. |
+| `--elev` | `pt:box` | `CommonFieldInput` | Resting lift, alone in `box-shadow`: the ring is the box's outline, so a theme's `--elev: none` never takes the ring with it. |
 | `--frost` | `pt:box` | `CommonFieldInput` | Plate frost — a full `backdrop-filter` value (see --bb-surface-filter). Routed through a local rather than read from the token directly, so a chrome-less variant can decline it: frosting a ghost field gives it the plate it is contractually not supposed to have. |
 | `--inside-label-clearance` | `pt:box`, `pt:prefix`, `pt:suffix` | `CommonFieldInput` | Height and top padding added above the text for a label rendered inside the box. Zero here; the `--inside-label` rules at the bottom of this file raise it to one label line, or two with a description. |
 | `--w` | `pt:icon` | `BbIcon` | `--w` is set inline by BbIcon from the size prop. The `initial` default seals it: without it an ancestor's `--w` (e.g. a dropdown's width bridge) would inherit in and size the icon. The `--size` indirection stays so higher-specificity rules (e.g. `.bb-badge .bb-icon`) can re-point it. |
@@ -412,17 +412,18 @@ const setPreset = (days: number) => {
 </script>
 ```
 
-### `type` — day, month, year, or day + time
+### `type` — day, week, month, year, or day + time
 
 `type` decides which segments the field renders and what it emits. It mirrors
 `<input type="…">`:
 
-| `type`             | segments       | emits                 | range emits              |
-| ------------------ | -------------- | --------------------- | ------------------------ |
-| `date` _(default)_ | `DD/MM/YYYY`   | ISO / `YYYY-MM-DD`    | `[start, end]`           |
-| `datetime`         | + `HH:mm(:ss)` | ISO carrying the time | `[start, end]`           |
-| `month`            | `MM/YYYY`      | `2026-08`             | `['2026-01', '2026-03']` |
-| `year`             | `YYYY`         | `2026`                | `['2026', '2028']`       |
+| `type`             | segments       | emits                 | range emits                |
+| ------------------ | -------------- | --------------------- | -------------------------- |
+| `date` _(default)_ | `DD/MM/YYYY`   | ISO / `YYYY-MM-DD`    | `[start, end]`             |
+| `datetime`         | + `HH:mm(:ss)` | ISO carrying the time | `[start, end]`             |
+| `week`             | `W44 2026`     | `2026-W44`            | `['2026-W41', '2026-W43']` |
+| `month`            | `MM/YYYY`      | `2026-08`             | `['2026-01', '2026-03']`   |
+| `year`             | `YYYY`         | `2026`                | `['2026', '2028']`         |
 
 ```vue
 <BbDatePickerInput v-model="period" label="Reporting period" type="month" />
@@ -435,7 +436,7 @@ promising `DD/MM/YYYY` to a two-segment field would be worse than no hint at
 all. The calendar button opens the matching terminal grid, so typing and
 picking always produce the same shape.
 
-`month` and `year` are **calendar labels, not instants**: they force `floating`,
+`week`, `month` and `year` are **calendar labels, not instants**: they force `floating`,
 ignore `utc`, and make the time props inert. This is deliberate rather than
 squeamish — the start of August in Rome is the 31st of July in UTC, so a month
 stored as an instant reads back as the wrong month for half the world.
@@ -446,6 +447,60 @@ a DEV warning, so `min="2026-03-15"` under `type="month"` leaves the whole of
 March selectable instead of quietly deleting it. `selectable` receives the same
 shape it emits.
 
+#### Weeks
+
+`type="week"` types and emits an ISO 8601 week. The field shows a literal `W`,
+a week segment and a year segment (`W44 2026`, in every locale), and the
+calendar picks the whole week of any day you click, with a week-number column
+and Monday-first rows. The year segment is the **ISO week-year**: the week of
+29 December 2025 is `W01 2026`. A typed `W53` in a year with 52 weeks snaps
+to `W52` when the field is read, as 31 February snaps to the 28th.
+
+`min` / `max` take a week (`max="2026-W52"`) or a date, and a week counts only
+when all seven days are inside: `min="2026-10-28"` (a Wednesday) leaves that
+week out, and a typed week below it moves to the first whole week inside, with
+the usual `error` event. The trigger's accessible name reads the week and its
+dates ("week 44, October 26 – November 1, 2026"); the dates are never shown.
+The calendar side — the week rows, the hover outline, ranges of weeks — is
+[BbCalendar § Weeks](./BbCalendar.md#weeks), and `pt:week` /
+`pt:week-number` restyle its rows from this field.
+
+**A delivery week and a sprint of weeks**
+
+```vue
+<template>
+	<div class="grid max-w-xs gap-4">
+		<BbDatePickerInput
+			v-model="delivery"
+			description="Orders ship on the Monday of the week you pick."
+			label="Delivery week"
+			min="2026-10-28"
+			type="week"
+		/>
+		<BbDatePickerInput
+			v-model="sprint"
+			label="Sprint"
+			max="2026-W52"
+			range
+			type="week"
+		/>
+	</div>
+</template>
+
+<script setup lang="ts">
+import { ref } from 'vue';
+import { BbDatePickerInput } from 'bitboss-ui';
+
+/**
+ * `type="week"`: the value is the ISO week, `YYYY-Www`. Any day of a calendar
+ * row picks its week; the field types it as `W44 2026`. `min` on a Wednesday
+ * leaves that week out, because a week counts only when all seven days fit.
+ */
+const delivery = ref<string | null>('2026-W45');
+const sprint = ref<string[]>(['2026-W45', '2026-W46']);
+</script>
+```
+
 ### Time selection
 
 Set `type="datetime"` and the field grows 24-hour `HH:mm` segments after the date
@@ -764,12 +819,17 @@ table cell (`<BbDatePickerInput compact hide-label variant="ghost" />`) — no
 register through the plugin's `inputVariants` option. The full ladder is in
 the `BbTextInput` guide.
 
+The calendar panel renders inside the field, so it reads the field's
+`--bb-radius`, capped at half a control height: a pill field
+(`style="--bb-radius: 999px"`) gets a rounded panel, never a clipped one, and a
+`0px` app stays square.
+
 ### Restyling with passthrough
 
 `pt` reaches a named part of the control with a class list — or, in the
 object form, a style and attributes — optionally only while a state is on.
-Parts: `root` (the container), `label`, `description`, `message` (the errors / warnings region — one node each, only one ever shows), `hint` (the helper line — shown on focus, or always with `persistent-hint`), `box` (the bordered field box), `input` (the native control), `icon` (`prepend:icon` + `append:icon` — a broadcast; the state glyphs are chrome), `spinner` (the spinner shown while `loading`), `prefix`, `suffix`, `clear` (the ✕ that empties the field). Plus `panel` (the calendar surface you see — the popover's painted bubble on desktop, the sheet itself on a phone; it carries the sizing tokens, so `pt:panel="[--px:2px]"` tightens it), `sheet` (the bottom sheet on a phone only) and the calendar's own parts, forwarded to it: `header`, `arrow`, `month`, `year`, `cellColumnHeader`, `day` (the whole cell), `dayButton` (the mark inside it), `monthItem` and `yearItem` — the `BbDatePicker` guide describes each node. `input` is every segment field; the calendar trigger is `activator`.
-States: `errors`, `warnings` (never beside errors), `loading`, `disabled`, `readonly`, `hasValue` (written `pt:box:has-value`). Plus `open` (the calendar is showing), and the calendar's per-node states: `selected`, `disabled`, `today`, `outside`, `rangeStart` / `rangeEnd` / `inRange` and `highlighted` on the cells, `active` on `month` / `year`. A name outside that list is a type error and an
+Parts: `root` (the container), `label`, `description`, `message` (the errors / warnings region — one node each, only one ever shows), `hint` (the helper line — shown on focus, or always with `persistent-hint`), `box` (the bordered field box), `input` (the native control), `icon` (`prepend:icon` + `append:icon` — a broadcast; the state glyphs are chrome), `spinner` (the spinner shown while `loading`), `prefix`, `suffix`, `clear` (the ✕ that empties the field). Plus `panel` (the calendar surface you see — the popover's painted bubble on desktop, the sheet itself on a phone; it carries the sizing tokens, so `pt:panel="[--px:2px]"` tightens it), `sheet` (the bottom sheet on a phone only) and the calendar's own parts, forwarded to it: `header`, `arrow`, `month`, `year`, `cellColumnHeader`, `day` (the whole cell), `dayButton` (the mark inside it), `week` (one row with `type="week"`), `weekNumber` (its ISO week number), `monthItem` and `yearItem` — the `BbDatePicker` guide describes each node. `input` is every segment field; the calendar trigger is `activator`.
+States: `errors`, `warnings` (never beside errors), `loading`, `disabled`, `readonly`, `hasValue` (written `pt:box:has-value`). Plus `open` (the calendar is showing), and the calendar's per-node states: `selected`, `disabled`, `today`, `outside`, `rangeStart` / `rangeEnd` / `inRange` and `highlighted` on the cells, `selected` / `rangeStart` / `rangeEnd` / `inRange` on the week rows (`pt:week:selected`, `pt:week-number`), `active` on `month` / `year`. A name outside that list is a type error and an
 ESLint error.
 
 The invoice due-date field above, restyled through those parts: a muted
@@ -909,7 +969,7 @@ label>')` matches nothing; query each segment by its own label instead. See
 
 | 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: `activator`, `arrow`, `box`, `cellColumnHeader`, `clear`, `day`, `dayButton`, `description`, `header`, `hint`, `icon`, `input`, `item`, `label`, `message`, `month`, `monthItem`, `panel`, `prefix`, `root`, `sheet`, `spinner`, `suffix`, `year`, `yearItem`. States: `active`, `disabled`, `errors`, `ghost`, `hasValue`, `highlighted`, `inRange`, `loading`, `open`, `outline`, `outside`, `rangeEnd`, `rangeStart`, `readonly`, `secondary`, `selected`, `today`, `warnings`. 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 `BbDatePickerInputProps['pt']` (`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: `activator`, `arrow`, `box`, `cellColumnHeader`, `clear`, `day`, `dayButton`, `description`, `header`, `hint`, `icon`, `input`, `item`, `label`, `message`, `month`, `monthItem`, `panel`, `prefix`, `root`, `sheet`, `spinner`, `suffix`, `week`, `weekNumber`, `year`, `yearItem`. States: `disabled`, `errors`, `ghost`, `hasValue`, `loading`, `open`, `outline`, `readonly`, `secondary`, `warnings`, `highlighted`, `inRange`, `outside`, `rangeEnd`, `rangeStart`, `selected`, `today`, `active`. 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 `BbDatePickerInputProps['pt']` (`PtValue` is not exported): § Typing `pt` in `<script>`. |
 | `adaptive` | `boolean \| undefined` | ``config.adaptive` (`true`)` |  | On mobile the calendar opens inside a bottom off-canvas sheet instead of a floating popover, mirroring the adaptive behaviour of `BbPopover`/`BbSelect`. When unset, falls back to the global `config.adaptive`. |
 | `ampm` | `boolean \| undefined` | `false` |  | 12-hour display with an AM/PM segment (requires `type="datetime"`). Purely a field-composition concern: `modelValue` and the `time` model stay 24-hour regardless. Type `A`/`P` (or ArrowUp/Down) to set the meridiem. |
 | `append:icon` | `string \| undefined` |  |  | Name of the icon to be added at the end of the input. |
@@ -922,7 +982,7 @@ label>')` matches nothing; query each segment by its own label instead. See
 | `disabled` | `boolean \| undefined` | `false` |  | Disables the component. |
 | `disableWriting` | `boolean \| "mobile" \| "desktop" \| undefined` | `false` |  | Disables typing into the input. Use `'mobile'` to disable typing only on mobile, `'desktop'` to disable typing only on desktop. |
 | `errors` | `string \| string[] \| undefined` |  |  | Error messages under the field, a string or array, in an `aria-live="polite"` region and first in the control's `aria-describedby`, so they are re-read when it regains focus. |
-| `firstDayOfWeek` | `0 \| 1 \| 2 \| 3 \| 4 \| 5 \| 6 \| undefined` | `the locale's week start` |  | First day of the week (0 = Sunday … 6 = Saturday). Omitted, the active locale's week start: Monday for `it`, `de`, `fr`, `en-gb`…, Sunday for bare `en` (US) and `pt` (Brazil). |
+| `firstDayOfWeek` | `0 \| 1 \| 2 \| 3 \| 4 \| 5 \| 6 \| undefined` | `the locale's week start` |  | First day of the week (0 = Sunday … 6 = Saturday). Omitted, the active locale's week start: Monday for `it`, `de`, `fr`, `en-gb`…, Sunday for bare `en` (US) and `pt` (Brazil). Ignored under `type="week"`: ISO weeks run Monday to Sunday, so a week grid always starts on Monday. |
 | `floating` | `boolean \| undefined` | `false` |  | If true the date will have a format YYYY-MM-DD instead of the default ISO string. |
 | `formless` | `boolean \| undefined` | `false` |  | Keep this control out of the enclosing `BbForm` entirely: not submitted, not dirty, not reset, not validated. For a control that is not form data (a filter, a "show advanced" switch). |
 | `hasErrors` | `boolean \| undefined` | `false` |  | Define if the component should be in an error state. It usually attaches a CSS class for styling purposes. |
@@ -937,8 +997,8 @@ label>')` matches nothing; query each segment by its own label instead. See
 | `labelPosition` | `"left" \| "center" \| "right" \| undefined` |  |  | Sets the text alignment of the label. |
 | `layout` | `Responsive<FieldLayout> \| undefined` |  |  | How label and input sit together: `'vertical'`, `'horizontal'` (50/50), `'auto'`, `'label-fill'`, `'input-fill'`, a ratio like `'xx xxxxx'`, or a per-breakpoint map (`{ default: 'vertical', md: 'xx xxxxx' }`). |
 | `loading` | `boolean \| undefined` | `false` |  | Sets the component in a loading state, usually triggering some visual styles. |
-| `max` | `string \| undefined` |  |  | Maximum selectable date in `YYYY-MM-DD` format — or, with `type="datetime"`, `YYYY-MM-DDTHH:mm` to tighten the boundary day to a minute. Values outside both patterns throw during setup to surface configuration mistakes. |
-| `min` | `string \| undefined` |  |  | Minimum selectable date in `YYYY-MM-DD` format — or, with `type="datetime"`, `YYYY-MM-DDTHH:mm` to tighten the boundary day to a minute. Values outside both patterns throw during setup to surface configuration mistakes. |
+| `max` | `string \| undefined` |  |  | Maximum selectable date in `YYYY-MM-DD` format — or, with `type="datetime"`, `YYYY-MM-DDTHH:mm` to tighten the boundary day to a minute. Values outside both patterns throw during setup to surface configuration mistakes. `type="week"`: a week (`YYYY-Www`) or a date, whole weeks only. |
+| `min` | `string \| undefined` |  |  | Minimum selectable date in `YYYY-MM-DD` format — or, with `type="datetime"`, `YYYY-MM-DDTHH:mm` to tighten the boundary day to a minute. Values outside both patterns throw during setup to surface configuration mistakes. `type="week"`: a week (`YYYY-Www`) or a date, whole weeks only. |
 | `modelValue` | `string \| string[] \| null \| undefined` |  |  | Used by v-model. Can be null, a single string, or an array of strings based on whether a range or single date is needed. |
 | `name` | `string \| undefined` |  |  | Defines the name of the input. |
 | `numberOfMonths` | `number \| undefined` | `1` |  | How many months the calendar popover shows side by side (day grids only); the phone sheet always shows one. Too narrow for them all, the months wrap. |
@@ -952,11 +1012,11 @@ label>')` matches nothing; query each segment by its own label instead. See
 | `reverse` | `boolean \| undefined` | `false` |  | Reverses the layout. Applicable in every direction the order of the label and the input is swapped. |
 | `rules` | `RuleExpression<string \| string[] \| null>` |  |  | vee-validate rules for this field. Only inside a `BbForm`. |
 | `seconds` | `boolean \| undefined` | `false` |  | Adds the seconds segment (requires `type="datetime"`). Without it, an incoming value carrying seconds displays truncated and is left untouched until the user commits an edit, at which point seconds zero out. |
-| `selectable` | `((date: string) => boolean) \| undefined` |  |  | Function that accepts a `string` object and returns a boolean. `false` meaning the date cannot be selected. |
+| `selectable` | `((date: string) => boolean) \| undefined` |  |  | Function that accepts a `string` object and returns a boolean. `false` meaning the date cannot be selected. Under `type="week"` it receives the week value (`2026-W44`). |
 | `step` | `number \| undefined` | `1` |  | Minute granularity for the calendar's minute column and arrow stepping (requires `type="datetime"`). Constrains what the component produces, never what it accepts: a typed off-grid value (e.g. `10:07` with `step: 15`) is emitted verbatim, and no column row highlights for it. |
 | `time` | `string \| string[] \| null \| undefined` |  |  | `v-model:time`: the time part, always 24-hour `HH:mm` / `HH:mm:ss`. With `floating` it is the only carrier of the time; otherwise it mirrors `modelValue`'s, and writing it rewrites that. Requires `type="datetime"`. |
 | `transitionDuration` | `number \| undefined` |  |  | Transition duration, in milliseconds, for the popover appearance. |
-| `type` | `'date'` \| `'month'` \| `'year'` \| `'datetime'` | `"date"` |  | What the field edits, and so its segments and emitted shape: `date` (`DD/MM/YYYY`), `datetime` (adds the time segments and rail), `month` (`MM/YYYY`, emits `YYYY-MM`) or `year` (`YYYY`). `month` / `year` force `floating`, ignore `utc`, and leave the time props inert. |
+| `type` | `'date'` \| `'month'` \| `'year'` \| `'week'` \| `'datetime'` | `"date"` |  | What the field edits, so its segments and emitted shape: `date` (`DD/MM/YYYY`), `datetime` (adds the time segments and rail), `week` (`W44 2026`, emits `2026-W44`), `month` (`MM/YYYY`, emits `YYYY-MM`) or `year` (`YYYY`). The last three force `floating` and ignore `utc` and the time props. |
 | `utc` | `boolean \| undefined` | `false` |  | Emits UTC ISO strings (`…Z`) instead of the local offset (`…+01:00`). Emission only: incoming values parse the same either way, and the field always displays local time. Ignored with `floating`. |
 | `validationLabel` | `string \| undefined` |  |  | The field's name in validation messages (`{field}`): "Email is not valid". Defaults to the `label` (or `legend`), then "This field"; never the `name`. Set it when the label is hidden or reads badly in a sentence (icon-only, a question). `BbForm` only. |
 | `validationMode` | `'aggressive'` \| `'balanced'` \| `'lazy'` \| `'submit-only'` \| `'submit-live'` |  |  | When the field validates: `aggressive` (each change), `balanced` (on leave, then live while in error), `lazy` (on leave), `submit-only`, `submit-live`. Unset: the `BbForm`'s `validation-mode`, then `formControls.validationMode` (`'balanced'`). `BbForm` only. |
@@ -989,6 +1049,8 @@ label>')` matches nothing; query each segment by its own label instead. See
 | `month` | The month heading button; it opens the month panel. |
 | `year` | The year heading button; it opens the year panel. |
 | `cellColumnHeader` | Each weekday letter above the grid — a broadcast. |
+| `week` | One row of seven days with `type="week"` — the band a picked week paints and the hover outline. A broadcast resolved per row. |
+| `weekNumber` | The ISO week number heading each row with `type="week"` — a broadcast resolved per row. |
 | `day` | One whole day cell — a broadcast resolved per day. A background here paints the full cell square; restyle the round mark on `dayButton`. |
 | `dayButton` | The button inside a day cell — the mark that shows selection. A broadcast resolved per day. |
 | `monthItem` | One month button of the month panel (the home grid of `type="month"`) — a broadcast resolved per month. |
@@ -1002,10 +1064,10 @@ States are listed in precedence order: when two are on at once and their entries
 | `hasValue` | Component-wide: the control holds a value, by its own rule (`0` counts on `BbNumberInput`, `''` on `BbColorInput`). |
 | `outside` | Per node, on `day` / `dayButton`: a day of the previous or next month, shown to fill the grid. |
 | `today` | Per node, on `day` / `dayButton`: today. |
-| `inRange` | Per node, on the cells (`day`, `dayButton`, `monthItem`, `yearItem`): inside a committed range, between its ends. |
-| `selected` | Per node, on the cells: a chosen day, month or year; on `item`, the picked time's entry in each column. |
-| `rangeStart` | Per node, on the cells: a committed range's first day, month or year. |
-| `rangeEnd` | Per node, on the cells: a committed range's last day, month or year. |
+| `inRange` | Per node, on the cells (`day`, `dayButton`, `monthItem`, `yearItem`) and the week rows (`week`, `weekNumber`): inside a committed range, between its ends. |
+| `selected` | Per node, on the cells: a chosen day, month or year; on `week` / `weekNumber`, a chosen week (a range's ends too, as on its days); on `item`, the picked time's entry in each column. |
+| `rangeStart` | Per node, on the cells and the week rows: a committed range's first day, week, month or year. |
+| `rangeEnd` | Per node, on the cells and the week rows: a committed range's last day, week, month or year. |
 | `readonly` | Component-wide: the control is `readonly` — shown, focusable, not editable. |
 | `disabled` | Component-wide while the input is `disabled`. Also per node, on the calendar's cells: one outside `min` / `max` or refused by `selectable`; on `arrow`, at a bound or while the month / year panel is open. |
 | `warnings` | Component-wide: the control is in its warning state (`warnings` / `has-warnings`) and not in an error state — errors win, so the two are never on together. |
@@ -1065,7 +1127,7 @@ Set these on the element, or on a class you put on it, to retune this component
 
 - `BbDatePickerInput` _(this component)_ — its own template binds: `controlAttrs` → `input.bb-segmented-field__input`, `input` → `input.bb-segmented-field__input`, `activator` → `button.bb-segmented-field__activator`, `suffix` → `span.bb-field-input__suffix`; hands `BbDatePicker` the pt map `passthrough.forward(PICKER_PARTS, BB_DATE_PICKER_PT.states)` (ours → theirs)
   - `BbDatePicker` _(public — [contract](./BbDatePicker.md))_ — its own pt parts (`BbDatePicker`): `panel` → `div`; hands `BbCalendar` the pt map ` passthrough.forward(DATE_PICKER_CALENDAR_PARTS, BB_CALENDAR_PT.states) ` (ours → theirs); hands `BbOffCanvas` the pt map `{ panel: 'root', sheet: 'root' }` (ours → theirs); documented CSS variables: `--cell`, `--unit-row`; also mounts `CommonPopover`
-    - `BbCalendar` _(public — [contract](./BbCalendar.md))_ — its own pt parts (`BbCalendar`): `header` → `div.bb-calendar__header`, `arrow` → `BbBaseButton`, `month` → `BbBaseButton`, `year` → `BbBaseButton`, `day` → `div.bb-calendar__day`, `dayButton` → `button.bb-calendar__day-button`; documented CSS variables: `--cell`, `--unit-row`; also mounts `ScaleFade`, `Slide`, `CalendarMonthPanel`, `CalendarYearPanel`
+    - `BbCalendar` _(public — [contract](./BbCalendar.md))_ — its own pt parts (`BbCalendar`): `header` → `div.bb-calendar__header`, `arrow` → `BbBaseButton`, `month` → `BbBaseButton`, `year` → `BbBaseButton`, `week` → `div.bb-calendar__week`, `weekNumber` → `div.bb-calendar__week-number`, `day` → `div.bb-calendar__day`, `dayButton` → `button.bb-calendar__day-button`; documented CSS variables: `--cell`, `--unit-row`, `--wk`; also mounts `ScaleFade`, `Slide`, `CalendarMonthPanel`, `CalendarYearPanel`
       - `BbBaseButton` _(public — [contract](./BbBaseButton.md))_ — its own pt parts (`BbBaseButton`): `root` → `RouterComponent`, `root` → `a`, `root` → `component`; also mounts `RouterComponent`
       - `CommonTimeSelector` _(internal — not importable, reach it through `BbCalendar`)_ — its own pt parts (`BbCalendar`): `header` → `div.bb-time-selector__header`, `cellColumnHeader` → `div.bb-time-selector__cell-column-header`, `item` → `BbBaseButton`; documented CSS variables: `--time-mark`; also mounts `BbBaseButton`
     - `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`

package/dist/ai/BbDialog.md

@@ -575,6 +575,9 @@ const save = (saved: Member) => {
   writes it, so a module constant is safe.
 - An edit-only dialog, always opened with a row, needs no `default-data` and no
   guard: its body exists only while an opening holds data.
+- **`data` is typed by your annotation, not by `default-data`.** Write the slot
+  type on the template: `<template #default="{ data }: { data: Member }">`, and
+  `vue-tsc` catches `data.nmae`.
 
 **Whose surroundings the dialog takes.** The directive sits on the trigger in
 the template, so the dialog it opens follows the trigger's surroundings: a
@@ -1797,7 +1800,7 @@ A `pt` value written in `<script>` (a constant, a preset, a wrapper's
 | `queryKey` | `string \| undefined` | `"dialog"` |  | The query key `navigation` writes. |
 | `replace` | `boolean \| undefined` | `false` |  | With `navigation`, replaces the history entry instead of pushing one, so Back leaves the page instead of closing the dialog. |
 | `size` | `Responsive<NonNullable<number \| CssSize \| keyof BbDialogSizes \| undefined>> \| undefined` | `"sm"` |  | Controls the maximum width of the dialog. Accepts named presets from `'xs'` to `'2xl'`, a custom CSS width string, or a numeric pixel value — or a per-breakpoint map (e.g. `{ default: 'sm', lg: 'lg' }`) to switch width responsively. |
-| `snap` | `BbSnapPoint \| undefined` |  |  | The phone sheet's snap stop (Q71.8), one of the `snapPoints` entries. The desktop dialog ignores it. |
+| `snap` | `BbSnapPoint \| undefined` |  |  | The phone sheet's snap stop, one of the `snapPoints` entries. The desktop dialog ignores it. |
 | `snapPoints` | `BbSnapPoint[] \| undefined` |  |  | Heights the phone sheet rests at, smallest first: a screen fraction (`0.5`; `1` = as tall as it gets) or pixels (`'240px'`). The first is the opening height; `v-model:snap` reads and sets the stop. Sheet only: the centred dialog ignores it. |
 | `stack` | `string \| undefined` |  |  | Name of this dialog's stack. Dialogs with the same `stack` replace one another: only the latest opened shows, the rest of the stack hide beneath it. Dialogs in different stacks, or with no `stack`, never affect each other and stay fully visible. |
 | `title` | `string \| undefined` |  |  | Title text announced to assistive technologies. If omitted, no header is rendered (unless a `header` slot is supplied) and accessibility must be handled manually. |
@@ -1828,7 +1831,7 @@ States are listed in precedence order: when two are on at once and their entries
 ## Events
 
 - `hidden` — `(): void` — Emitted after the close transition completes and the dialog is fully dismissed.
-- `hide` — `(result: BbDialogResult): void` — Emitted as soon as the dialog starts to close (model becomes false), with the opening's result: the same object its promise settles with, `{ completed: true, value }` or `{ completed: false, reason }` (Q73.6).
+- `hide` — `(result: BbDialogResult): void` — Emitted as soon as the dialog starts to close (model becomes false), with the opening's result: the same object its promise settles with, `{ completed: true, value }` or `{ completed: false, reason }`.
 - `show` — `(): void` — Emitted as soon as the dialog starts to open (model becomes true).
 - `shown` — `(): void` — Emitted once the open transition has run (symmetric with `hidden`): the dialog is settled, so code that measures or anchors to its content sees the final layout. Not emitted for a dialog closed before it finished opening.
 - `update:modelValue` — `(value: boolean): void` — Emitted with the new value whenever `v-model` changes.
@@ -1854,7 +1857,7 @@ Set these on the element, or on a class you put on it, to retune this component
 | `--transition-timing-function` | `.bb-dialog` | `var(--bb-ease)` |  |
 | `--bg` | `.bb-dialog` | `var(--bb-panel)` |  |
 | `--fg` | `.bb-dialog` | `var(--bb-text)` |  |
-| `--close-size` | `.bb-dialog__header` | `28px` | Shared by the close control and by the space the title reserves for it, * so the two can never drift apart. |
+| `--close-size` | `.bb-dialog__header` | `28px` | Shared by the close control and by the space the title reserves for it, so the two can never drift apart. |
 | `--gap` | `.bb-dialog__footer` | `8px` |  |
 
 ## Component tree

package/dist/ai/BbDropdown.md

@@ -1363,7 +1363,7 @@ const items: BbDropdownItem[] = [
 ];
 
 /** Status glyph per workspace row — color inherits via currentColor. */
-// `value` is optional on a row (Q53.17), so a slot reading it may see none.
+// `value` is optional on a row, so a slot reading it may see none.
 const envIcon = (key?: string): IconType => {
 	if (key === 'production') return 'lucide:circle-check';
 	if (key === 'staging') return 'lucide:circle-dashed';
@@ -1808,8 +1808,8 @@ long lists.
 
 `compact` walks the same ladder `BbSelect` does, so a dense toolbar can hold a
 select and a menu that agree: flyout rows go 28px → 24px, sheet rows 44px →
-36px. The label does not shrink — density here is height, exactly as it is for a
-select.
+36px, and the flyout's `header` / `footer` pad 6px instead of 8px. The label
+does not shrink — density here is height, exactly as it is for a select.
 
 The sheet stops at 36px and never follows the flyout down to 24px. A menu row is
 a touch target whose mis-tap fires the neighbouring **command**, where a
@@ -2325,7 +2325,7 @@ it, and at the top level closes the sheet.
 
 | 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: `footer`, `header`, `input`, `item`, `itemDescription`, `itemIcon`, `itemText`, `list`, `panel`, `root`, `sheet`. States: `activeLink`, `disabled`, `exactActiveLink`, `open`, `selected`, `default`, `destructive`. 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 `BbDropdownProps['pt']` (`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: `footer`, `header`, `input`, `item`, `itemDescription`, `itemIcon`, `itemText`, `list`, `panel`, `root`, `sheet`. States: `open`, `activeLink`, `default`, `destructive`, `disabled`, `exactActiveLink`, `selected`. 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 `BbDropdownProps['pt']` (`PtValue` is not exported): § Typing `pt` in `<script>`. |
 | `activator` | `Record<string, any> \| HTMLElement \| null \| undefined` |  |  | An external activator element or component ref: the activator slot is not rendered, and the listeners and ARIA (`aria-haspopup` / `aria-expanded` / `aria-controls`) are attached to it; don't add your own. |
 | `adaptive` | `boolean \| undefined` | ``config.adaptive` (`true`)` |  | On mobile (below `config.mobileMaxWidth`), renders the menu as a bottom sheet that drills into submenus one level at a time instead of hover flyouts; slots and selection are unchanged. Unset: the global `config.adaptive`. |
 | `anchor` | `Record<string, any> \| HTMLElement \| null \| undefined` | `the activator element` |  | The element the panel positions against when it should differ from the activator (a wrapper the activator is part of); an HTMLElement or component ref. It also drives a percentage `width`. Ignored with `placement="cursor"`. |
@@ -2415,7 +2415,7 @@ Set these on the element, or on a class you put on it, to retune this component
 | Property | Set on | Default | What it is |
 | --- | --- | --- | --- |
 | `--bg` | `.bb-dropdown__group-search` | `var(--bb-panel)` |  |
-| `--menu-inset` | `.bb-dropdown` | `4px` | Inset between the menu's outer chrome and its first item — owned here and * consumed by both `.bb-dropdown__list`'s padding and the submenu * lead-in below, so the two can never drift apart. |
+| `--menu-inset` | `.bb-dropdown` | `4px` | Inset between the menu's outer chrome and its first item — owned here and consumed by both `.bb-dropdown__list`'s padding and the submenu lead-in below, so the two can never drift apart. |
 
 ## Component tree
 

package/dist/ai/BbDropdownButton.md

@@ -622,6 +622,9 @@ A `pt` value written in `<script>` (a constant, a preset, a wrapper's
 
 ### Accessibility
 
+- On a touch screen the toggle's invisible hit area reaches 44×44 outward
+  (never across into the main button) when the split button has no element
+  beside it; beside another control it follows BbButton's 4px rule.
 - The chevron toggle carries its own localized `aria-label` (from the
   `locale` config) and reflects open state via `aria-expanded` — no extra
   wiring needed.
@@ -694,7 +697,7 @@ A `pt` value written in `<script>` (a constant, a preset, a wrapper's
 | `tag` | `'button'` \| `'div'` \| `'span'` \| `'label'` | `'button'` |  | Element to render for the plain (non-link, non-router) button: `'button'` (default), `'div'`/`'span'` when nesting inside another button or link, or `'label'` for a file-upload trigger. Ignored when `href`/`to` make the button render as a link. |
 | `target` | `string \| undefined` |  |  | Sets or retrieves the window or frame at which to target content. |
 | `text` | `string \| undefined` |  |  | Text content of the component. |
-| `to` | `string \| wt \| bt \| undefined` |  |  | Route Location the link should navigate to when clicked on. |
+| `to` | `string \| et \| X \| undefined` |  |  | Route Location the link should navigate to when clicked on. |
 | `toggle:icon` | `string \| undefined` |  |  | Replaces the chevron shown inside the dropdown toggle button. A constrained alternative to a slot: only the toggle's icon changes, so the button keeps its semantics. Named after the part it sits in (the `toggle`), the way `prepend:icon` / `append:icon` name theirs. |
 | `transitionDuration` | `number \| undefined` | `150` |  | How long the transition has to last in milliseconds. Menus use the fast transition (150) rather than the medium one (250) the other popovers default to: a menu is opened to pick one command and is gone again, so it answers faster than a panel the user reads or edits in. |
 | `type` | `"button" \| "reset" \| "submit" \| undefined` |  |  | Gets the classification and default behavior of the button. |

package/dist/ai/BbForm.md

@@ -83,7 +83,7 @@ submitted, counts toward `dirty`, is reset and is validated if it has rules.
 Describe the whole form once, in the schema library you already use, and hand
 it to the `schema` prop. There is no adapter to import and no extra package
 to install: any [Standard Schema](https://standardschema.dev) works, which
-covers Zod 3.24+ and 4, Valibot 1, ArkType 2 and Yup 1.7+.
+covers Zod 4, Valibot 1, ArkType 2 and Yup 1.7+.
 
 **Sign-up form with a Zod schema**
 
@@ -1338,7 +1338,7 @@ the control, the form's own state and whatever ref you bound all agree
 afterwards.
 The same holds for vee-validate's `resetField` and `setFieldValue`.
 
-> Fixed in 3.0.0-beta.15 (Q18.4). Before that the value pipe only ran one way:
+> Fixed in 3.0.0-beta.15. Before that the value pipe only ran one way:
 > a reset moved the form's internal value but never told your model, so the
 > form reported itself pristine while the user's text was still on screen.
 
@@ -1856,8 +1856,8 @@ renders a red asterisk beside its label ([`BbAsterisk`](./BbAsterisk.md) does th
 With a `schema`, the schema decides, with every Standard Schema
 library above: a field gets the asterisk when its key is required in the
 schema (not optional, no default, not nullable, and its parent object required
-too). Zod 4, ArkType and Joi are read through their JSON Schema; Zod 3, Yup,
-Valibot and Effect through their own schema shape — nothing to wrap, no
+too). Zod 4, ArkType and Joi are read through their JSON Schema; Yup, Valibot
+and Effect through their own schema shape — nothing to wrap, no
 `required` to add. The
 marker follows a per-step schema as it changes, and a field the schema (or a
 `required` rule) requires gets `aria-required="true"`, so assistive tech hears

package/dist/ai/BbNumberInput.md

@@ -41,7 +41,7 @@
 | `--border-focus` | `pt:box` | `CommonFieldInput` | frame while focused, or --active |
 | `--ring-size` | `pt:box` | `CommonFieldInput` | ring width; 0 is a variant declining the ring |
 | `--ring-color` | `pt:box` | `CommonFieldInput` | ring colour; state owns it, not variants |
-| `--elev` | `pt:box` | `CommonFieldInput` | Resting lift, alone in `box-shadow`: the ring is the box's outline (Q81.6), so a theme's `--elev: none` never takes the ring with it. |
+| `--elev` | `pt:box` | `CommonFieldInput` | Resting lift, alone in `box-shadow`: the ring is the box's outline, so a theme's `--elev: none` never takes the ring with it. |
 | `--frost` | `pt:box` | `CommonFieldInput` | Plate frost — a full `backdrop-filter` value (see --bb-surface-filter). Routed through a local rather than read from the token directly, so a chrome-less variant can decline it: frosting a ghost field gives it the plate it is contractually not supposed to have. |
 | `--inside-label-clearance` | `pt:box`, `pt:prefix`, `pt:suffix` | `CommonFieldInput` | Height and top padding added above the text for a label rendered inside the box. Zero here; the `--inside-label` rules at the bottom of this file raise it to one label line, or two with a description. |
 | `--w` | `pt:icon` | `BbIcon` | `--w` is set inline by BbIcon from the size prop. The `initial` default seals it: without it an ancestor's `--w` (e.g. a dropdown's width bridge) would inherit in and size the icon. The `--size` indirection stays so higher-specificity rules (e.g. `.bb-badge .bb-icon`) can re-point it. |
@@ -302,8 +302,9 @@ const temperature = ref<number | null>(21);
 - the **`increase()` / `decrease()`** scope functions.
 
 Those functions are handed to the `prepend` / `append` / `prefix` / `suffix`
-slots as scope props, so you build a plus/minus stepper without wiring any state
-yourself. For a stepper rendered _outside_ the field, drive `v-model` directly
+slots as scope props, with **`increaseDisabled` / `decreaseDisabled`** (true at
+`max` / `min` and while `disabled` or `readonly`), so you build a plus/minus
+stepper without wiring any state yourself. For a stepper rendered _outside_ the field, drive `v-model` directly
 (`model += step`) rather than reaching for a template ref. Stepping respects
 `min`/`max`/`maxPrecision` and is a no-op while `disabled` or `readonly`.
 
@@ -329,18 +330,20 @@ stays free while the buttons move in fixed increments.
 			:min="1"
 			name="quantity"
 		>
-			<template #prepend="{ decrease }">
+			<template #prepend="{ decrease, decreaseDisabled }">
 				<BbButton
 					aria-label="Decrease quantity"
+					:disabled="decreaseDisabled"
 					icon="lucide:minus"
 					size="xs"
 					variant="ghost"
 					@click="decrease"
 				/>
 			</template>
-			<template #append="{ increase }">
+			<template #append="{ increase, increaseDisabled }">
 				<BbButton
 					aria-label="Increase quantity"
+					:disabled="increaseDisabled"
 					icon="lucide:plus"
 					size="xs"
 					variant="ghost"
@@ -444,7 +447,8 @@ icon (`hasWarnings`) shares the error icon's slot — shown when `hasWarnings` i
 and there is no error.
 
 Every content slot (`prefix`, `suffix`, `prepend`, `append`, `prepend:outer`,
-`append:outer`) receives `{ increase, decrease }` scope, so stepper buttons can
+`append:outer`) receives `{ increase, decrease, increaseDisabled, decreaseDisabled }`
+scope, so stepper buttons can
 live anywhere in the ring. Put interactive controls in the _outer_ slots or use
 the scoped callbacks; plain `prefix`/`suffix` text is decoration only.
 
@@ -955,14 +959,14 @@ States are listed in precedence order: when two are on at once and their entries
 
 ## Slots
 
-- `append` — scope: `BbNumberInputStepSlotProps` `{ increase: () => void; decrease: () => void }` — Content rendered after the number input, at the end of the inner container. Typically used to place increment/decrement buttons next to the input.
-- `append:outer` — scope: `BbNumberInputStepSlotProps` `{ increase: () => void; decrease: () => void }` — Content rendered after the entire input control, outside the input chrome.
+- `append` — scope: `BbNumberInputStepSlotProps` `{ increase: () => void; decrease: () => void; increaseDisabled: boolean; decreaseDisabled: boolean }` — Content rendered after the number input, at the end of the inner container. Typically used to place increment/decrement buttons next to the input.
+- `append:outer` — scope: `BbNumberInputStepSlotProps` `{ increase: () => void; decrease: () => void; increaseDisabled: boolean; decreaseDisabled: boolean }` — Content rendered after the entire input control, outside the input chrome.
 - `description` — scope: `BbNumberInputDescriptionSlotProps` `{ text: string; hasErrors: boolean; hasWarnings: boolean }` — Replaces the description text. Provided alone (no `description` prop) it still renders the description region and wires it into `aria-describedby`.
 - `label` — scope: `BbNumberInputLabelSlotProps` `{ showAsterisk?: boolean; text: string; hasErrors: boolean; hasWarnings: boolean }` — Replaces the default label text rendered above the number input.
-- `prefix` — scope: `BbNumberInputStepSlotProps` `{ increase: () => void; decrease: () => void }` — Inline content rendered at the start of the input field area, before the typed number.
-- `prepend` — scope: `BbNumberInputStepSlotProps` `{ increase: () => void; decrease: () => void }` — Content rendered before the number input, at the start of the inner container.
-- `prepend:outer` — scope: `BbNumberInputStepSlotProps` `{ increase: () => void; decrease: () => void }` — Content rendered before the entire input control, outside the input chrome.
-- `suffix` — scope: `BbNumberInputStepSlotProps` `{ increase: () => void; decrease: () => void }` — Inline content rendered at the end of the input field area, after the typed number.
+- `prefix` — scope: `BbNumberInputStepSlotProps` `{ increase: () => void; decrease: () => void; increaseDisabled: boolean; decreaseDisabled: boolean }` — Inline content rendered at the start of the input field area, before the typed number.
+- `prepend` — scope: `BbNumberInputStepSlotProps` `{ increase: () => void; decrease: () => void; increaseDisabled: boolean; decreaseDisabled: boolean }` — Content rendered before the number input, at the start of the inner container.
+- `prepend:outer` — scope: `BbNumberInputStepSlotProps` `{ increase: () => void; decrease: () => void; increaseDisabled: boolean; decreaseDisabled: boolean }` — Content rendered before the entire input control, outside the input chrome.
+- `suffix` — scope: `BbNumberInputStepSlotProps` `{ increase: () => void; decrease: () => void; increaseDisabled: boolean; decreaseDisabled: boolean }` — Inline content rendered at the end of the input field area, after the typed number.
 
 ## CSS custom properties