@keboola/design 13.2.0 → 15.0.0

package/AGENTS.md

@@ -79,6 +79,8 @@ This file answers **which** component to use; [`COMPONENT-API.md`](./COMPONENT-A
 
 **Never** use `Popover` for destructive confirmations (use `Popconfirm`) or hover-only previews (use `HoverCard`). **Never** hand-roll a confirmation from `Modal` + buttons — use `AlertModal`, which owns the confirm/cancel actions and the async loading state.
 
+**`Modal.Content` is centred by default.** Pass `align="top"` when the content changes height while in use (fields appear or drop as the user picks), so the modal stops re-centring and moving the field under the pointer. The legacy brand ignores it: its modals are always top-anchored.
+
 **Filters in a menu are menu items:** `DropdownMenu.RadioItem indicator="check"` for one value, `DropdownMenu.CheckboxItem indicator="checkbox"` for several, both `indicatorAlign="end"`. Never `RadioGroup` or `Checkbox` in a `DropdownMenu` or `Popover`.
 
 ### Inputs
@@ -236,12 +238,12 @@ Vertical rhythm: prefer `tw:gap-*` on a flex column parent over `tw:mt-*` on chi
 
 ### Navigation / flow
 
-| Use        | When                                                                                                                                        |
-| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Stepper`  | Linear progress through an ordered, finite sequence (multi-step form / wizard / pipeline). Argo-only. Set `onStepClick` for navigable flows |
-| `Tabs`     | Switching between sibling views of the same context                                                                                         |
-| `Timeline` | Unordered chronological log of events                                                                                                       |
-| `Progress` | Single percentage value of an in-flight task                                                                                                |
+| Use        | When                                                                                                                             |
+| ---------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| `Stepper`  | Linear progress through an ordered, finite sequence (multi-step form / wizard / pipeline). Set `onStepClick` for navigable flows |
+| `Tabs`     | Switching between sibling views of the same context                                                                              |
+| `Timeline` | Unordered chronological log of events                                                                                            |
+| `Progress` | Single percentage value of an in-flight task                                                                                     |
 
 **Never** use `Stepper` for branching navigation (use `Tabs`) or an unordered status list (use `Timeline`).
 
@@ -743,10 +745,12 @@ takes the node, and the chip lets it have the keyboard.
 />
 ```
 
-- A query overrides folding: every match shows, and a group with none disappears — so the group's row always stands for something the user can see.
+- A query opens every group with a match, and a group with none disappears — so the group's row always stands for something the user can see. A fold made under a query lasts until the query changes.
 - `value` holds items only. The row reads checked / mixed from them and never becomes a chip, so `allowSelectAll` and `renderChips` count what they always count.
 - Without `selectableGroups` / `groupToValue` a press on the row folds the group; with them, the chevron and `ArrowRight` / `ArrowLeft` do.
 - Don't hand-roll it from a flat list and an `onValueChange` that expands a parent into its children — the control owns the fold, the query override and the mixed state.
+- An item the user picked elsewhere and can't remove here (a table another mapping uses) is `itemToLocked`, not `itemToDisabled`: a locked row looks disabled but still takes the highlight, so `renderAside` describes it and its group still folds; a disabled row takes neither.
+- `renderAside={(highlighted) => …}` adds an inspector beside the list about the last row the pointer or the arrow keys were on — `{ kind: 'item' }`, `{ kind: 'group' }` or `null` before any. A button in the popup hides it (`asideOpen` / `onAsideOpenChange` to persist that), and it stays hidden while the popup is under 40rem. Reach for it when a row needs more detail than fits on it.
 
 **Long lists** — a `Combobox` or `MultiCombobox` whose options can run into the hundreds (tables, configurations, users) takes `virtualized="auto"`: past 30 options, grouped or not, only the rows in view reach the DOM. It is opt-in because a test that clicks a far row needs every option rendered.
 
@@ -794,9 +798,11 @@ An **opacity modifier composites over `transparent`, not over the element's own
 
 A tint also cannot carry a **state change** on a light surface — a brand-primary tint stays within ~1.5:1 of the surface at any opacity that still reads as a tint. Step the border for that, and keep the roles apart: hover steps the chrome border (`border-input` → `border-muted-foreground`), `focus-visible` owns the brand border.
 
-**Status — themeable under argo, with AA-legible defaults.** The four semantic states — `success`, `warning`, `info`, and `destructive` (used for "error") — are brand-overridable tokens, not fixed scales. Alert `variant`, `HelpBlock` / field-error state, `ErrorState`, and `Stepper` status read them, so a brand recolours every status surface at once. **Rule:** consume the token as **tint + text/icon** — `tw:bg-<role>/10` for the surface, `tw:text-<role>` / `tw:border-<role>/25` for the mark. The default token values ship dark enough to be AA (≥4.5:1) as text/icon on their own tint, in light **and** dark mode — a brand overriding them should preserve that. Avoid solid fills with a white foreground (`tw:bg-<role>` + white): the token flips light in dark mode, so white-on-token fails there. A brand _can_ recolour "error" away from red — that is now allowed; the accessible-on-tint contract is what must hold, not the hue. **Legacy exception:** the themeable treatment is gated to argo (`data-[argo=true]:` / `group-data-[argo=true]/…:`). Under legacy chrome (`useArgoDesign()` → `false`) Alert and `ErrorState` keep their original fixed status scales (`blue-*`/`green-*`/`warning-*`/`error-*`), and the legacy brand retains its original status token hues — so legacy status colour is unchanged.
+**Status — themeable, with AA-legible defaults.** The four semantic states — `success`, `warning`, `info`, and `destructive` (used for "error") — are brand-overridable tokens, not fixed scales. Alert `variant`, `HelpBlock` / field-error state, `ErrorState`, and `Stepper` status read them, so a brand recolours every status surface at once. **Rule:** consume the token as **tint + text/icon** — `tw:bg-<role>/10` for the surface, `tw:text-<role>` / `tw:border-<role>/25` for the mark. The default token values ship dark enough to be AA (≥4.5:1) as text/icon on their own tint, in light **and** dark mode — a brand overriding them should preserve that. Avoid solid fills with a white foreground (`tw:bg-<role>` + white): the token flips light in dark mode, so white-on-token fails there. A brand _can_ recolour "error" away from red — that is now allowed; the accessible-on-tint contract is what must hold, not the hue.
+
+**Status pastels.** Each state also has a pastel pair — `tw:bg-<role>-subtle` + `tw:text-<role>-subtle-foreground`, for `success` / `warning` / `info` / `destructive` and `neutral`. Unset, the fill is the status token at 10% and the text is the token 30% towards `foreground` (`neutral`: `muted` + `muted-foreground`), so the pair follows the brand and dark mode with no work and stays AA at badge size. A brand or app that wants its own pastel sets `--<role>-subtle` / `--<role>-subtle-foreground` to any CSS colour. `Badge color="<role>-subtle"` reads them.
 
-**Decorative — stays fixed across brands.** The non-semantic palette that encodes category rather than state: `Badge` decorative colours (`purple`, `cyan`, `teal`, `blue`, …), chart colours, decorative tag palette. **Rule:** keep using primitive scales (`purple-500`, `cyan-500`, …). These are an identity/category contract with the consumer and do not re-skin.
+**Decorative — stays fixed across brands.** The non-semantic palette that encodes category rather than state: `Badge` `color` hues (`purple`, `cyan`, `teal`, `blue`, …) — a state badge takes a status `color` (`success`, `warning-subtle`, …) instead — chart colours, decorative tag palette. **Rule:** keep using primitive scales (`purple-500`, `cyan-500`, …). These are an identity/category contract with the consumer and do not re-skin.
 
 **Heuristic.** A `variant` / `status` prop encoding one of the four states → **status token**. A `color` prop picking an arbitrary hue for categorisation → **decorative, fixed scale**. Everything else → **chrome, semantic token**.
 
@@ -829,20 +835,6 @@ import { keboola } from '@keboola/brand-registry';
 
 Read the resolved values with `useTheme()` (`brandId`, `currentTheme`, `themes`, `scheme`, `resolvedScheme`, and the setters). With no provider above it, it answers the defaults rather than throwing.
 
-### The argo/legacy switch is separate from the brand
-
-`ThemeProvider` does **not** decide whether a subtree renders the argo design language — that is a kbc-ui migration concern, so it rides its own context:
-
-```tsx
-import { ArgoDesignContext, useArgoDesign } from '@keboola/design';
-
-<ArgoDesignContext value={false}>{/* legacy chrome for this subtree */}</ArgoDesignContext>;
-```
-
-`ArgoDesignContext` defaults to `true` (argo — the modern default; legacy chrome is the exception), so an app that never provides it gets argo everywhere. kbc-ui provides `false` for its legacy brands and overrides per subtree as pages are migrated; components read it with `useArgoDesign()`. It is **temporary** and will be deleted once every kbc-ui surface is migrated — don't build on it in a new app.
-
-Because the value is read from the nearest provider, a nested override scopes to that subtree. The build ships a single instance of both contexts across every subpath entry, so a provider mounted from the root barrel is visible to components that ship in `@keboola/design/rjsf`, `/markdown-editor`, `/mermaid` and `/editors` too.
-
 Define a custom brand with `@keboola/brand-registry`'s `brandSchema` (Zod) and pass it in `brands`; or override the `--color-*` / `--radius-*` CSS variables directly on `:root`.
 
 **Interaction states and surface corners** are part of the same theme. Every one is optional and, unset, keeps the look the package ships:
@@ -865,7 +857,7 @@ Define a custom brand with `@keboola/brand-registry`'s `brandSchema` (Zod) and p
 - The state colours take **any CSS colour**, not the `R G B` channels the other colours use, so a wash can be translucent.
 - Each scheme falls back on its own: a value set in `colors` does not reach dark mode. Set `colorsDark` too.
 - Set `hover` and `hoverForeground` together, and `selected` and `selectedForeground`. Several components change the label on hover, and an unset foreground keeps the `accent-foreground` blue over whatever wash you chose.
-- Unset, a few components keep a hover or selected look of their own rather than `accent`: argo `DropdownMenu` (a `primary` tint), `Table` rows and `SectionNav` (`muted`). Once a theme sets the token, they follow it like the rest.
+- Unset, a few components keep a hover or selected look of their own rather than `accent`: `DropdownMenu` (a `primary` tint), `Table` rows and `SectionNav` (`muted`). Once a theme sets the token, they follow it like the rest.
 - `Sidebar` and `Navbar` sit on their own surface, so they take their own pair: `sidebarHover` for a hovered or open item, `sidebarSelected` for the current page. Set them inside `colors.sidebar` (and `colorsDark.sidebar`).
 - The fallbacks resolve where each class is used, so a brand that only re-points `accent` still moves hover and selected with it.
 

package/CHANGELOG.md

@@ -1,5 +1,199 @@
 # @keboola/design
 
+## 15.0.0
+
+### Major Changes
+
+- Text inputs, `Select` and `DateRangePicker` take no `variant` or `sizing` props: every field and trigger is 36 px tall in the same chrome.
+  - `InputGroup`, `TextInput`, `SearchInput`, `SearchInputWithNavigation`, `PasswordInput`, `NumberInput`, `Textarea`, `AutoSaveTextarea`, `DateInput`, `TimeInput`, `ColorInput`, `DateRangeInput`, `ChipEditor`, `Combobox`, `MultiCombobox`, the `FormGroup.*` inputs and the `field.*` connectors drop `variant` and `sizing`.
+  - `Select` and `Select.Trigger` drop `variant` and `sizing`; `inline` renders the text-like trigger with no field chrome.
+  - `DateRangePicker` drops `variant`.
+
+- Every component renders one design language — the one `useArgoDesign()` used to opt into — whatever the brand or context.
+  - `Button`'s `argoVariants` export is `buttonVariants`.
+  - `Tooltip` drops `chrome` and `Tooltip.Content` drops `argo`; tooltips are the light popover chrome.
+  - `Command` drops `variant`; `compact` keeps the dense search row and list padding for a menu inside a popover.
+  - `Switch` drops `size`.
+  - The `data-argo`, `data-design` and argo `data-variant` attributes are gone from Modal, AlertModal, Sheet, Toast, HoverCard, Tooltip, DropdownMenu, Command, Alert, Card and ErrorState.
+  - `ArgoDesignContext` and `useArgoDesign` are removed.
+  - `AlertModal`'s icon sits on its status token's tint (`info`, `warning`, `destructive`, `success`), so it follows the brand and dark mode.
+  - Kai's `Button variant="kai"` and `Toggle variant="ai-vivid"` take their label from `primary-foreground`; in dark their gradients are lighter, so a near-black label stays AA across the whole fill.
+  - Text, borders and surfaces in the form, editor, sidebar and input blocks use theme tokens, and `ModalIcon`, `Skeleton` and `Toggle variant="ai"` carry dark variants of their tints, so they stay legible in dark mode.
+
+- `kbcUi` (`kbc-ui`) is kbc-ui's brand, in place of `keboolaLegacySidebar` (`keboola-legacy-sidebar`).
+  - Light: the colours `keboola-legacy-sidebar` had — brand-blue `31 143 255`, bright status hues, a white sidebar.
+  - Dark: the `keboola` dark palette, pinned in full and tuned to WCAG AA — near-black labels on the bright primary and status fills, an input border at 3:1.
+  - Typography and radii: the `keboola` brand's.
+  - `@keboola/design` re-exports it under the same name.
+
+### Patch Changes
+
+- A pressed `Toggle variant="ai-vivid"` keeps its navy gradient in dark mode, so its white label stays legible.
+
+- Updated dependencies:
+  - @keboola/brand-registry@3.0.0
+
+## 14.0.0
+
+### Major Changes
+
+- `ToolCallApproval` v2 — redesigned around what an agent chat's approval card needs. It had no consumers, so the old API is replaced outright.
+  - Removed: `enableShortcuts` (Enter approve / Escape reject) and the `actions` override; `toolName` is now optional.
+  - Actions: `approveLabel` / `rejectLabel`, `approveVariant` (`'primary' | 'danger'`), an optional `extraAction` (e.g. "Always allow"), `pendingAction` (that button spins, every action disables), `isDisabled`.
+  - Header: `eyebrow` slot, optional `toolName`, `title`.
+  - Terminal states: `approved`, `rejected`, `expired`, `timed-out`, `cancelled`, `unattended`, with `statusLabel` / `statusMessage`, `resolvedBy` / `resolvedAt`, and `density="record"` for a one-line resolved record.
+  - Body: `children`, `notices` (warning / destructive / info rows), `aside` (beside the detail, stacked in a narrow container), `error`.
+  - Keyboard: `shortcutKey` (`'enter' | 'mod-enter' | 'none'`) approves from anywhere and shows the key on the button; `isShortcutHintOnly` shows it for an app that owns the shortcut.
+  - Stable test ids: `tool-call-approval`, `tool-approve-button`, `tool-decline-button`, `tool-extra-action-button`.
+
+### Minor Changes
+
+- `AnswerSources` and `SourceChip`: the provenance row under an answer. Chips carry a `verified` / `unverified` / `neutral` verdict and render as a link, button or label; the row collapses past six chips, summarises unverified ones once, states when none were declared and takes a `footnote` slot.
+
+- `ChatNotice`: a transcript notice row over `Alert` with `tone` (`error` / `warn` / `info`), an `action` slot, collapsible "Technical details" and an optional `retryAfter` countdown.
+
+- AI Kit composer chips: `AttachmentChip` (uploading / ready / error file chip with remove), `ContextChip` (quoted excerpt with "Show all" and images), `ModeChip` (removable animated mode pill) and `JumpToLatest` (scroll-to-latest button that pulses while the agent is working).
+
+- `SuggestedPrompt` takes `description` (a secondary line under the label), `trailing` (content pinned to the row's end, e.g. a badge) and `aria-label`. Without them it renders as before.
+
+- `PlanApproval` and `AnswerSummary` take an `expired` state for a card closed with no decision.
+  - `PlanApproval`: `status="expired"` (orange `Expired` pill, no actions), plus `statusLabel` to rename the pill and `statusMessage` shown under the title.
+  - `AnswerSummary`: `variant="expired"` (header ends `Expired`), plus `statusLabel` and a `statusMessage` shown first once expanded.
+
+- `PromptInput` takes `allowSendWhileBusy`: with it, a non-empty box sends while the conversation is `streaming` or `submitted` instead of refusing the keystroke, and Stop moves to a control of its own so cancelling never means emptying the box first. Off by default, so every existing composer behaves exactly as before.
+
+  Kai's composer turns that on. A message typed while Kai is working is queued and shown waiting rather than silently dropped, and a message typed under an open question answers it.
+
+- `AnswerActions` takes opt-in `onDownComment` (+ `commentPlaceholder`), a one-line comment input after a thumbs-down, and `onRegenerate` (+ `regenerateLabel`), an "Ask again" button; both are off by default
+
+- `FileDownloadChip` takes opt-in `onPreview` (split chip) and `actions`; new `FileGallery` block for image thumbnails (lazy, host-owned URLs and loading, capped with "+N more"). The default chip renders as before
+
+- `MessageBubble` takes opt-in `timestamp="visible"`, `quote`, `status` + `onRetry`, `author`, `collapseAfterPx` and `avatar`; without them it renders as before
+
+- `Modal.Content` takes `align="top"`: a new-design modal pinned to the top instead of centred, for a form whose height changes while it is in use. The legacy modal is always top-anchored.
+
+- `MultiCombobox` takes `renderAside`, a pane beside the list that describes the highlighted row, a group's own row included.
+
+  A combobox row's label fills the row, so content inside it can align to the row's end.
+
+  `MultiCombobox` takes `groupAppearance="banded"`, which puts each group, its row and open items, on a white card over a grey list.
+
+  A selectable group row reads checked or mixed from its locked items that are already selected.
+
+  `MultiCombobox` takes `collapseSelectedGroups`: each time the popup opens, a group whose items are all selected starts folded. A disabled group row still folds from its chevron.
+
+  `MultiCombobox` takes `asideOpen` and `onAsideOpenChange`: a button with a tooltip in the popup's bottom-right corner hides and shows the `renderAside` inspector. It is a grid column going from `0fr` to `1fr`, so the list narrows beside it rather than being covered, it keeps describing the last highlighted row until the popup closes, and it stays hidden, button included, while the popup is under 40rem wide.
+
+  A collapsible group's items fade and slide in as it unfolds and out as it folds, except under reduced motion. Banded rows are square inside their card, the first and last taking its corners, and enabled rows show a pointer.
+
+  `MultiCombobox` takes `defaultOpen` and `onOpenChange`, for a picker shown on demand with its list already open.
+
+  `MultiCombobox` takes `anchor`: with it there is no field, and the popup opens against that element with its search at the top. A banded popup is grey throughout, inspector included, with 8px of real space between group cards.
+
+  `MultiCombobox` takes `query`: search text typed elsewhere. With `anchor`, the popup then has no search of its own, and the host forwards the list keys to its hidden combobox input.
+
+  `Breadcrumb.Dropdown` takes `panelClassName`, for a panel background its search row shares with the list; the search row carries `data-slot="breadcrumb-dropdown-search"`.
+
+  A collapsible group's chevron, in `Combobox` / `MultiCombobox` and in `Breadcrumb.Dropdown.Group`, has a tooltip, and Cmd-click (Ctrl elsewhere) expands or collapses every group at once.
+
+  When a combobox group folds or unfolds, including all at once, the groups under it slide to their new place, and a windowed list keeps each row's measured height across a fold.
+
+  A query opens every collapsible group with a match, in `Combobox` / `MultiCombobox` and `Breadcrumb.Dropdown.Group`; a group folded under it stays folded until the query changes.
+
+  `MultiCombobox` takes `itemToLocked`: a selected item the user cannot remove looks disabled but still takes the highlight, so `renderAside` describes it and its group still folds; a group of only locked items locks its row.
+
+  An open `Combobox` / `MultiCombobox` popup marks `<body>` with `data-combobox-open`, counted across popups, so an app can lift the tooltips of the rows it lists. Combobox row labels carry `data-slot="combobox-item-label"`.
+
+- `PromptInput` takes `canSubmitEmpty`, so a composer whose attachments are the message can send with no text. Off by default.
+
+- `PromptInput` takes `blurOnEscape`, an `onKeyDown` that runs after its own key handling, `onPasteFiles` for files on the clipboard, and `busy` to hold the composer read-only while keeping focus. All opt-in.
+
+- `PromptInput`'s `/` menu picks the highlighted command on Tab, and opens with an empty or loading row (`commandsLoading`, `commandsEmptyText`) when `commands` is an empty list. New opt-in `slashTrigger="typed"` opens it only for a `/` typed into an empty composer.
+
+- Interaction-state and surface-corner tokens, so a theme can tell a hovered item from a selected one and round cards, menus and dialogs apart from controls. Unset, every token resolves to the value it replaced, so nothing changes until a theme sets one.
+  - `tw:bg-hover` / `tw:text-hover-foreground` (`--hover`, `--hover-foreground`) paint hover and keyboard highlight in Select, Combobox, Command, Breadcrumb, RadioGroup, Toggle, Calendar, DiffView, FileUpload, the markdown toolbar and AIKit. Unset: `accent` / `accent-foreground`. Argo `DropdownMenu` items, `Table` rows and `SectionNav` follow `--hover` too and, unset, keep their own `primary` / `muted` tint.
+  - `tw:bg-selected` / `tw:text-selected-foreground` (`--selected`, `--selected-foreground`) paint selected, checked and current in Table, Pagination, a checked `FieldBox`, the Calendar range, the active Breadcrumb item, SectionNav and a checked Command item. Unset: `accent` / `accent-foreground`. A checked argo `DropdownMenu` item follows `--selected` and, unset, keeps its `primary` tint.
+  - `tw:bg-pressed` (`--pressed`) is available for a pressed wash; no component paints it yet. Unset: `accent` a step towards its foreground.
+  - `tw:bg-scrim` (`--scrim`) is the `Modal`, `AlertModal` and `Sheet` backdrop. Unset: black at 50%.
+  - `tw:opacity-disabled` (`--disabled-opacity`) replaces every disabled `opacity-50`, `FieldBox` labels and `InputGroup` included. Unset: `0.5`. Controls disabled at 30%, 40% or 60% keep their own value.
+  - `--radius-card` rounds `Card`, `DashboardHero` and `tw:rounded-card`; unset, `Card` keeps `--radius-lg` and `rounded-card` keeps 10px. `--radius-popover` (`tw:rounded-popover`) rounds argo menus, popovers, hover cards and tooltips (unset 1rem). `--radius-modal` (`tw:rounded-modal`) rounds argo `Modal` and `AlertModal` (unset 1.5rem). `--radius-sheet` (`tw:rounded-sheet`) rounds the inner edge of an argo `Sheet` and `--radius-toast` (`tw:rounded-toast`) a `Toast`; unset, both keep `--radius-lg`.
+  - `tw:bg-sidebar-hover` / `tw:bg-sidebar-selected` (+ `-foreground`) split the `Sidebar` and `Navbar` hover from the current page, which both painted `sidebar-accent`. Unset, both are `sidebar-accent`; a current item keeps its selected fill while hovered.
+  - `ThemeProvider` emits all of them from a brand's `colors` / `colorsDark`, `radii` and `opacity`, and `BrandEditor` edits them.
+
+- `InlineStepLabel` takes opt-in `meta`, and `detail` + `defaultExpanded` for a collapsible per-row detail; `InlineStepGroup` takes an opt-in `footer`. Both render as before without them
+
+- `Tooltip.Title` heads a rich tooltip, and every floating overlay carries its own layer.
+  - `Tooltip.Title` is a small uppercase heading in the tooltip's text colour.
+  - `Tooltip` content spaces a nested `hr` and drops the last paragraph's bottom margin; on the legacy chrome a link takes the tooltip's text colour.
+  - `Tooltip` sits above `Modal` and every popup (1060); `HoverCard` sits with `Modal` (1051); a `DropdownMenu` submenu sits with its menu (1055).
+  - `Combobox` leaves `<body>` untouched while its popup is open.
+
+- `Markdown` gains opt-in streaming and code features; every default renders as before:
+  - `splitSealedBlocks(text)` and `withholdOpenTail(text, { diagram, tableHead })` — pure helpers for streaming an answer through `Markdown.Root` / memoised `Markdown.Block`s.
+  - `highlight` — colours fenced SQL, Python, JS/TS, JSON, shell and YAML through a lazily loaded highlighter.
+  - `sortable` (also on `MarkdownTable`) — header presses sort rows, numeric-aware, with `aria-sort`.
+  - `diagramActions` and `diagramDownload` — extra diagram toolbar controls and a built-in "Download SVG" action; `DiagramBlock` forwards `renderActions`.
+  - `ChatInlineIcon` also draws Lucide names (`icon:info`, `icon:trash-2`, …).
+
+- `Markdown` takes an opt-in `allowSvgFences`: an `svg fence, or an `xml / ```html fence whose body is a single SVG document, renders as a responsive chart instead of code. The SVG is sanitized with DOMPurify's SVG profile and loses scripts, event handlers, `foreignObject`, SMIL animation, `<style>` elements and every non-`#` reference. Raw inline HTML stays escaped, and the default is unchanged.
+
+  `ZoomableSvg` takes an opt-in `allowUse` to keep `<use>` (matplotlib draws every glyph with it) for markup whose `href`s are already limited to `#` references.
+
+- `PromptInput` takes `history`: the prompts already sent, oldest first. ↑ with the caret at the start of the text recalls them, newest first; ↓ steps back to the draft. Open `/` and `@` menus keep the arrows.
+
+- `Question` takes what an agent chat's question card needs. Additive; existing callers are unchanged.
+  - `isSubmitDisabled` keeps the answer from being sent, by click or ⌘/Ctrl+Enter.
+  - `isSubmitting` spins Submit and disables Skip.
+  - `error` shows why the last send failed, above the footer.
+  - `customAnswerMaxLength` caps the "Other" answer.
+  - An option's `badge` (e.g. `Recommended`) follows its label.
+  - `skipTooltip` replaces the Skip button's `Space` hint; `null` drops it.
+
+- `Table.Header` puts its row on the card surface, and `Table.SkeletonRows` draws placeholder rows in a table's own columns while its rows load.
+  - The header is `bg-card` with an `h-11` row and a border under it; `withShadow` and `className` work as before.
+  - The surface sits on `thead`, so `className="tw:bg-table-header"` (the former default tint) or any other `bg-*` replaces it at rest and on hover.
+  - `Table.SkeletonRows` takes `columns`, `noun` and `rows` (5 by default); the first row announces `Loading {noun}` to screen readers.
+  - Each column takes the real cell's `className` and `colSpan` and draws a `text` line, a `name` (icon, name and description lines) or nothing (`empty`).
+  - A width class can be a list, cycled over the rows; the name line varies in width from row to row unless given one.
+
+- `MermaidDiagram` renders with Pele, a dependency-free Mermaid renderer, in place of `mermaid` and `beautiful-mermaid`.
+  - Every Mermaid 12.1 diagram type; each type's code loads on first use, after which a diagram renders synchronously.
+  - Colours and font come from the DS tokens for the active scheme and are written into the SVG, so an exported SVG or PNG keeps them.
+  - `lucide:<name>` icons draw from the bundled Lucide pack; other icon packs draw no icon.
+  - A diagram cut off mid-stream shows the skeleton, and its source after 2 s without more input; invalid syntax shows the source.
+  - Layout and look follow Pele, not Mermaid.
+
+- `Table` puts its body on the card surface, the same `bg-card` as `Table.Header`.
+  - The fill sits on `<table>`, so a caller's `bg-*` in `className` replaces it.
+  - Row hover and selection tints draw over it as before.
+
+- `RjsfSchemaEditor` draws a `format: 'checkbox'` array as a group of DS `Checkbox`es.
+  - Each option toggles its value in the array; `readOnly` and `options.enumDisabled` disable them.
+  - `options.inline` lays the options out in a wrapping row.
+
+- `RjsfSchemaEditor` renders an array of enum values (`uniqueItems` + `items.enum`, no `format: 'checkbox'`) as a `MultiCombobox`.
+  - The default `async-multi-select` widget offers the `items.enum` options, labelled by `items.options.enum_titles`, and writes the selection back as an array of the typed enum values.
+  - A stored value outside `items.enum` shows as a chip labelled by the value and survives an edit.
+  - `readOnly` and `ui:disabled` disable it; options in `ui:enumDisabled` cannot be picked.
+  - It does not load `async` options, create `tags` / `creatable` values or read `enumSource`; a host widget passed under `async-multi-select` replaces it for that.
+
+### Patch Changes
+
+- `MultiCombobox`: while nothing matches, the inspector and its button go at once and the list takes the whole width, so the inspector never describes a row the list no longer shows.
+
+- `MultiCombobox`: with the inspector hidden, the list ends above the inspector button, so the button never covers a row at any scroll position.
+
+- `Markdown`'s `allowSvgFences` keeps only an allowlist of paint and text declarations in a fenced chart's `style` attributes, so `image-set()` can no longer load a URL and `position: fixed` can no longer lay an overlay over the page.
+
+- `Markdown`'s `allowSvgFences` caps the nodes a fence's `<use>` elements clone (20,000), not their count, so a few `<use>` aimed at a large group can no longer multiply into millions of rendered nodes.
+
+- `Table.SkeletonRows` takes `gapClassName` on a `name` column, the gap between its icon and lines (`tw:gap-3.5` by default), so a table's placeholder name starts where its real name does.
+
+- `Command.Item`'s keyboard highlight is the only row fill: a `checked` row shows a trailing check (or its checkbox / radio indicator), and rows no longer cross-fade on ↑/↓. The project switcher and Kai's chat history mark the current row this way (UT-5894)
+
+- Updated dependencies:
+  - @keboola/brand-registry@2.1.0
+
 ## 13.2.0
 
 ### Minor Changes