prime-ui-kit 0.14.0 → 0.15.0

package/dist/skill/reference/components/modal/examples/enter-key.tsx

@@ -0,0 +1,116 @@
+/** Enter in a dialog: deleting a workspace takes a click, never Enter in its field; in the tags dialog Enter adds the typed tag instead of saving — `confirmOnEnter`, `onEnterConfirm`. */
+import { Badge, Button, Input, Modal } from "prime-ui-kit";
+import * as React from "react";
+
+import styles from "./examples.module.css";
+
+const WORKSPACE = "Отдел продаж";
+const INITIAL_TAGS = ["VIP", "Опт"];
+
+export default function ModalEnterKeyExample() {
+  const [deleteOpen, setDeleteOpen] = React.useState(false);
+  const [typed, setTyped] = React.useState("");
+  const [tags, setTags] = React.useState(INITIAL_TAGS);
+  const [draft, setDraft] = React.useState("");
+
+  const addTag = () => {
+    const tag = draft.trim();
+    if (tag && !tags.includes(tag)) setTags([...tags, tag]);
+    setDraft("");
+  };
+
+  return (
+    <>
+      <Modal.Root
+        open={deleteOpen}
+        onOpenChange={(next) => {
+          setDeleteOpen(next);
+          setTyped("");
+        }}
+        confirmOnEnter={false}
+      >
+        <Modal.Trigger>
+          <Button.Root variant="outline" tone="danger">
+            Удалить пространство
+          </Button.Root>
+        </Modal.Trigger>
+        <Modal.Content size="s">
+          <Modal.Header>
+            <Modal.Title>Удалить «{WORKSPACE}»?</Modal.Title>
+            <Modal.Description>
+              Сделки, клиенты и счета пространства удалятся без возможности восстановления.
+            </Modal.Description>
+          </Modal.Header>
+          <Modal.Body>
+            <Input.Root label={`Введите «${WORKSPACE}», чтобы подтвердить`}>
+              <Input.Wrapper>
+                <Input.Field value={typed} onValueChange={setTyped} autoComplete="off" />
+              </Input.Wrapper>
+            </Input.Root>
+          </Modal.Body>
+          <Modal.Footer>
+            <Modal.Close>
+              <Button.Root variant="outline" tone="neutral">
+                Отмена
+              </Button.Root>
+            </Modal.Close>
+            {/* The confirm button is a click target only: `confirmOnEnter={false}` keeps Enter off it. */}
+            <Modal.Confirm>
+              <Button.Root
+                tone="danger"
+                disabled={typed !== WORKSPACE}
+                onClick={() => setDeleteOpen(false)}
+              >
+                Удалить
+              </Button.Root>
+            </Modal.Confirm>
+          </Modal.Footer>
+        </Modal.Content>
+      </Modal.Root>
+
+      <Modal.Root
+        onOpenChange={() => setDraft("")}
+        onEnterConfirm={(event) => {
+          event.preventDefault();
+          addTag();
+        }}
+      >
+        <Modal.Trigger>
+          <Button.Root variant="soft" tone="neutral">
+            Теги клиента
+          </Button.Root>
+        </Modal.Trigger>
+        <Modal.Content size="s">
+          <Modal.Header>
+            <Modal.Title>Теги клиента</Modal.Title>
+            <Modal.Description>ООО «Северный ветер»</Modal.Description>
+          </Modal.Header>
+          <Modal.Body>
+            <div className={styles.tags}>
+              {tags.map((tag) => (
+                <Badge.Root key={tag} color="blue">
+                  {tag}
+                </Badge.Root>
+              ))}
+            </div>
+            <Input.Root label="Новый тег" hint="Enter добавляет тег">
+              <Input.Wrapper>
+                <Input.Field value={draft} onValueChange={setDraft} placeholder="Партнёр" />
+              </Input.Wrapper>
+            </Input.Root>
+          </Modal.Body>
+          <Modal.Footer>
+            <Modal.Close>
+              <Button.Root variant="outline" tone="neutral">
+                Отмена
+              </Button.Root>
+            </Modal.Close>
+            <Modal.Close>
+              <Button.Root>Сохранить</Button.Root>
+            </Modal.Close>
+          </Modal.Footer>
+        </Modal.Content>
+      </Modal.Root>
+    </>
+  );
+}

package/dist/skill/reference/components/modal/examples/examples.module.css

@@ -1,21 +1,15 @@
 /* Layout of the Modal scenarios: semantic tokens only. */
 
+/* enter-key.tsx: the client's tags in a wrapping row. */
+.tags {
+  display: flex;
+  flex-wrap: wrap;
+  gap: var(--prime-space-2);
+}
+
 /* in-form.tsx: field → field 20 (foundation §1). */
 .form {
   display: flex;
   flex-direction: column;
   gap: var(--prime-space-5);
 }
-
-/* custom-container.tsx: a bounded block (§4) takes the host's card fill so it reads in both themes. */
-.portalHost {
-  position: relative;
-  box-sizing: border-box;
-  display: flex;
-  justify-content: center;
-  width: 100%;
-  padding: var(--prime-space-4);
-  border-radius: var(--prime-card-radius);
-  background: var(--prime-color-layer-nested);
-  box-shadow: var(--prime-shadow-raised);
-}

package/dist/skill/reference/components/modal/examples/structure.tsx

@@ -1,5 +1,5 @@
-/** Optional parts: an icon tile with a header-only notice, and a header with a footer but no body — `Modal.Icon`, `Modal.Body`, `Modal.Footer`. */
-import { Button, Icon, Modal } from "prime-ui-kit";
+/** Optional parts: an icon tile with a header-only notice, and a header with a status before the close button and a footer but no body — `Modal.Icon`, `Modal.Actions`, `Modal.Body`, `Modal.Footer`. */
+import { Badge, Button, Icon, Modal } from "prime-ui-kit";
 
 export default function ModalStructureExample() {
   return (
@@ -35,6 +35,9 @@ export default function ModalStructureExample() {
             <Modal.Description>
               Новые клиенты увидят тариф сразу после публикации.
             </Modal.Description>
+            <Modal.Actions>
+              <Badge.Root color="gray">Черновик</Badge.Root>
+            </Modal.Actions>
           </Modal.Header>
           <Modal.Footer>
             <Modal.Close>

package/dist/skill/reference/components/native-select/COMPONENT.md

@@ -115,7 +115,7 @@ One look, the Select trigger's: field fill, inset control border, tier radius; t
 |---|---|
 | [overview.tsx](examples/overview.tsx) | A labelled system select with a hint; the OS picker opens on phones — `label`, `hint`. |
 | [sizes.tsx](examples/sizes.tsx) | Every size tier; the label and the hint follow the field tier — `size`. |
-| [states.tsx](examples/states.tsx) | A default field next to a disabled and an invalid one — `disabled`, `invalid`. |
+| [states.tsx](examples/states.tsx) | A default field next to a disabled and an invalid one, and one whose focus shows without the ring — `disabled`, `invalid`, `focusRing`. |
 | [validation.tsx](examples/validation.tsx) | Live validation: unassigning the owner shakes the field and drops the error in, picking someone clears it; required and optional markers and a hint — `required`, `optional`, `hint`, `error`. |
 | [option-groups.tsx](examples/option-groups.tsx) | Options under group headings with the native optgroup, and a placeholder while nothing is picked — `placeholder`. |
 | [controlled.tsx](examples/controlled.tsx) | The parent owns the value: the plan drives the price under the field — `value`, `onValueChange`. |

package/dist/skill/reference/components/native-select/examples/states.tsx

@@ -1,4 +1,4 @@
-/** A default field next to a disabled and an invalid one — `disabled`, `invalid`. */
+/** A default field next to a disabled and an invalid one, and one whose focus shows without the ring — `disabled`, `invalid`, `focusRing`. */
 import { NativeSelect } from "prime-ui-kit";
 
 export default function NativeSelectStatesExample() {
@@ -16,6 +16,10 @@ export default function NativeSelectStatesExample() {
         <option value="viewer">Наблюдатель</option>
         <option value="editor">Редактор</option>
       </NativeSelect>
+      <NativeSelect label="focusRing={false}" defaultValue="editor" focusRing={false}>
+        <option value="viewer">Наблюдатель</option>
+        <option value="editor">Редактор</option>
+      </NativeSelect>
     </>
   );
 }

package/dist/skill/reference/components/notification/COMPONENT.md

@@ -178,7 +178,7 @@ Collapsed stacks show up to 3 cards peeking behind each other. Hover or keyboard
 | [tones.tsx](examples/tones.tsx) | The four tones: the icon carries the meaning; danger and warning are announced at once — `tone`. |
 | [stacking.tsx](examples/stacking.tsx) | Toasts of one position and tone stack; hover expands the stack and pauses the timers — `max`, `items`, `dismissAll`. |
 | [undo.tsx](examples/undo.tsx) | Delete at once and offer to undo: the row leaves the list, the toast brings it back, and the deletion is sent only when the toast leaves without an undo — `onDismiss`, `action`. |
-| [dismiss.tsx](examples/dismiss.tsx) | A short timer, a toast that stays until closed, and one without a close button — `duration`, `persistent`, `closable`. |
+| [dismiss.tsx](examples/dismiss.tsx) | A short timer, a toast that stays until closed, and one without a close button; the close button's name comes from labels — `duration`, `persistent`, `closable`, `labels`. |
 | [in-form.tsx](examples/in-form.tsx) | Saving a form: the button shows loading, then a success toast or an error toast with a retry action — `notify`, `action`. |
 
 ## Mistakes

package/dist/skill/reference/components/notification/examples/dismiss.tsx

@@ -1,4 +1,4 @@
-/** A short timer, a toast that stays until closed, and one without a close button — `duration`, `persistent`, `closable`. */
+/** A short timer, a toast that stays until closed, and one without a close button; the close button's name comes from labels — `duration`, `persistent`, `closable`, `labels`. */
 import { Button, NotificationProvider, useNotifications } from "prime-ui-kit";
 
 import styles from "./examples.module.css";
@@ -43,7 +43,7 @@ function DismissButtons() {
 export default function NotificationDismissExample() {
   // In an app NotificationProvider wraps the root once; here it keeps the example self-contained.
   return (
-    <NotificationProvider>
+    <NotificationProvider labels={{ close: "Скрыть уведомление" }}>
       <DismissButtons />
     </NotificationProvider>
   );

package/dist/skill/reference/components/page-content/COMPONENT.md

@@ -254,6 +254,7 @@ One `PageContent.Title` (`<h1>`) per page; a topic inside Body is a `PageContent
 | [sections.tsx](examples/sections.tsx) | A page with titled sections: tiles of one screen close together, a new topic set off by air, a link at the end of the heading, a heading column beside a panel — `PageContent.Section`, `label`, `description`, `PageContent.Actions`, `layout`. |
 | [list-detail.tsx](examples/list-detail.tsx) | A support inbox as list + detail on a full-height page: side by side on a wide panel, one pane at a time with a back button on a narrow one — `PageContent.Split`, `PageContent.BackButton`, `fill`. |
 | [narrow.tsx](examples/narrow.tsx) | In a phone-width column the page actions wrap under the heading instead of squeezing it. |
+| [screen.tsx](examples/screen.tsx) | A settings page: sections with a heading column and a panel, a form saved by its own button, switches that apply at once and a danger zone with a confirm — `layout`, `maxWidth`. |
 
 ## Mistakes
 - Padding on `PageContent.Root` to imitate gutters → gutters come from `AppShell.Main`.

package/dist/skill/reference/components/page-content/examples/list-detail.tsx

@@ -45,9 +45,6 @@ export default function PageContentListDetailExample() {
   return (
     <div className={styles.fillMain}>
       <PageContent.Root fill>
-        <PageContent.Header>
-          <PageContent.Title>Обращения</PageContent.Title>
-        </PageContent.Header>
         <PageContent.Body>
           <PageContent.Split
             open={dialogId !== null}

package/dist/skill/{patterns/settings-page.tsx → reference/components/page-content/examples/screen.tsx}

@@ -1,4 +1,4 @@
-/** A settings page: sections with a heading column and a panel, a form saved by its own button, switches that apply at once and a danger zone with a confirm. */
+/** A settings page: sections with a heading column and a panel, a form saved by its own button, switches that apply at once and a danger zone with a confirm — `layout`, `maxWidth`. */
 import {
   Button,
   Card,
@@ -13,7 +13,7 @@ import {
 } from "prime-ui-kit";
 import * as React from "react";
 
-import styles from "./settings-page.module.css";
+import styles from "./screen.module.css";
 
 const TIMEZONES = [
   { value: "Europe/Kaliningrad", label: "Калининград (UTC+2)" },
@@ -45,7 +45,7 @@ const ALERTS = [
   },
 ];
 
-export default function SettingsPagePattern() {
+export default function PageContentScreenExample() {
   const [innError, setInnError] = React.useState<string>();
   const [saving, setSaving] = React.useState(false);
   const [saved, setSaved] = React.useState(false);

package/dist/skill/reference/components/page-content/examples/variants.tsx

@@ -4,24 +4,17 @@ import { Card, PageContent, Typography } from "prime-ui-kit";
 import styles from "./examples.module.css";
 
 const WIDTHS = [
-  { value: "full", title: "Сделки", text: "Колонка занимает всю ширину main." },
-  { value: "wide", title: "Дашборд продаж", text: "Не шире ширины контента, по центру." },
-  {
-    value: "readable",
-    title: "Условия использования",
-    text: "Не шире колонки для чтения, по центру.",
-  },
+  { value: "full", text: "Сделки: колонка занимает всю ширину main." },
+  { value: "wide", text: "Дашборд продаж: не шире ширины контента, по центру." },
+  { value: "readable", text: "Условия использования: не шире колонки для чтения, по центру." },
 ] as const;
 
 export default function PageContentVariantsExample() {
   return (
     <div className={styles.main}>
       <div className={styles.stack}>
-        {WIDTHS.map(({ value, title, text }) => (
+        {WIDTHS.map(({ value, text }) => (
           <PageContent.Root key={value} maxWidth={value}>
-            <PageContent.Header>
-              <PageContent.Title>{title}</PageContent.Title>
-            </PageContent.Header>
             <PageContent.Body>
               <Card.Root>
                 <Card.Body>

package/dist/skill/reference/components/page-toolbar/COMPONENT.md

@@ -3,7 +3,7 @@
 **Category:** page
 **Kind:** layout
 
-> The panel at the top of a page — sections, filter and search, view options and the primary action — laid out from its own width: one row when wide, stacked rows when narrow, search and filter always first with the active filters under them.
+> The panel at the top of a page — sections, filter and search, view options and the primary action — laid out from its own width: one row when wide, stacked rows when narrow, search and filter always first with the active filters under the top row.
 
 ## When to use
 - A list, registry or dashboard page whose top holds several of: sections with counts, a filter and search, a period or view switch, the primary action.
@@ -11,7 +11,7 @@
 - Any page that has to work from 320px with the same controls as on desktop — nothing is hidden, the slots only move.
 
 ## When not to use
-- A page with a title, a description and one or two buttons → [PageContent](../page-content/COMPONENT.md) `Header` with `Actions`.
+- One or two buttons of the page and nothing else → `AppHeader.Actions` in the [AppHeader](../../layout/app-header/COMPONENT.md) title row.
 - Tools that belong to one table → the DataTable `toolbar` slot.
 - Switching panels inside a card or a section → [Tabs](../tabs/COMPONENT.md).
 - App-level navigation → [Sidebar](../../layout/sidebar/COMPONENT.md).
@@ -28,7 +28,7 @@ PageToolbar.Root                 container: its own width picks the layout
 ├─ PageToolbar.Sections          sections of the page: a fullWidth SegmentedControl with counts
 ├─ PageToolbar.View              period, table / cards, columns
 ├─ PageToolbar.Actions           the primary action (and its secondary twin, e.g. «Отменить»)
-└─ PageToolbar.Chips             active filters: SmartFilter.Chips, a row right under the search
+└─ PageToolbar.Chips             active filters: SmartFilter.Chips, a row under the top row
 ```
 
 ## API
@@ -50,7 +50,7 @@ PageToolbar.Root                 container: its own width picks the layout
 | `…rest` | `HTMLAttributes<HTMLDivElement>` | — | `children`, `className` and the other div attributes. |
 
 ### PageToolbar.Tools
-`ref` → `HTMLDivElement`. Search and filter button (`SmartFilter.Toolbar`): always the first slot and the stretchy one, the Chips right under it.
+`ref` → `HTMLDivElement`. Search and filter button (`SmartFilter.Toolbar`): always the first slot and the stretchy one; it gives way first when the row runs short.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
@@ -64,14 +64,14 @@ PageToolbar.Root                 container: its own width picks the layout
 | `…rest` | `HTMLAttributes<HTMLDivElement>` | — | `children`, `className` and the other div attributes. |
 
 ### PageToolbar.Actions
-`ref` → `HTMLDivElement`. The primary action of the page: at the end of the top row at every width, never wraps down.
+`ref` → `HTMLDivElement`. The primary action of the page: at the end of the top row; on a phone, when the search would get less than 18rem beside it, its own full row right under the search.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
 | `…rest` | `HTMLAttributes<HTMLDivElement>` | — | `children`, `className` and the other div attributes. |
 
 ### PageToolbar.Chips
-`ref` → `HTMLDivElement`. Active filters (`SmartFilter.Chips`) in their own row right under the search and filter; the row takes no space while it is empty.
+`ref` → `HTMLDivElement`. Active filters (`SmartFilter.Chips`) in their own row under the top row; the row takes no space while it is empty.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
@@ -83,26 +83,28 @@ PageToolbar has no variants: the layout follows the toolbar's width.
 ### Layout by width
 | Toolbar width | Looks like | Default |
 |---|---|---|
-| `≥ 56rem` | one row that never wraps: Tools (stretch, at least 18rem — a 9rem search and the filter button on one line) · Sections (content width) · View (content width) · Actions; Chips under it; short of room the Tools give way first, then the Sections shrink and scroll inside | |
+| `≥ 56rem` | one row that never wraps: Tools (stretch) · Sections (content width) · View (content width) · Actions; Chips under it; short of room the Tools give way first, down to 12rem, so the Sections keep their items and counts whole; only then the Sections shrink and scroll inside | |
 | `< 56rem` | rows: Tools (stretch) + Actions; Chips; Sections (full row); View (full row) | yes (mobile first) |
-| any | Chips right under the search and filter, only while there are chips | |
+| phone (Tools would get < 18rem beside the Actions) | rows: Tools (full row); Actions (full row, its buttons share it); Chips; Sections; View — the search is never squeezed; an icon-only action still fits beside the Tools | |
+| any | Chips under the top row, only while there are chips | |
 
 ## States
 | State | Driven by | DOM |
 |---|---|---|
 | wide | container ≥ 56rem | one flex row, no wrapping; Chips rendered under the bar |
-| narrow | container < 56rem | a grid of real rows only (`order` + grid columns): a missing slot makes no row, every row is 12 from the next |
-| no Tools | Sections without Tools | the Sections take the Tools' place: first and stretchy, beside the action |
+| narrow | container < 56rem | one wrapping flex line of real rows only (`order` + full-row slots): a missing slot makes no row, every row is 12 from the next |
+| action on its own row | narrow, and the Tools (or the Sections in their place) would get less than 18rem beside the Actions | the Actions wrap under them and stretch across the row; an Actions slot alone in the toolbar keeps its buttons at the end |
+| no Tools | Sections without Tools; View without Tools and Sections | that slot takes the Tools' place: first and stretchy, beside the action, so the action stays at the top row's end |
 | alone in a row | Tools or Sections without Actions; View when narrow | that slot stretches to the full row; the View's controls share it equally |
 | no chips | `PageToolbar.Chips` empty (`SmartFilter.Chips` renders nothing) | the chips row takes no space |
 
 ## Layout & spacing
-- 8 inside a slot. No padding or fill of its own: it sits at the top of `PageContent.Body` (or replaces `PageContent.Header` on dense pages that keep their `h1` in the shell).
-- The order is fixed: search and filter first, then the sections, the view and the primary action; the active filters always sit right under the search and filter, never under the sections. The primary action is at the end of the top row at every width and never wraps down.
+- 8 inside a slot. No padding or fill of its own: on an app page it is the page's tools row in `AppHeader.Tools`, under the page title; tools of one table go into that table's `toolbar`.
+- The order is fixed: search and filter first, then the sections, the view and the primary action; the active filters sit under the top row, never under the sections. The primary action is at the end of the top row; on a phone, where the search would get less than 18rem beside it, it takes its own row right under the search — still above the sections and the view.
 - Every gap is one step: 12 between slots and between every pair of rows, at any width — no row is ever further from the next.
 - Sections take a `fullWidth` SegmentedControl: the toolbar decides when it stretches (content width when wide, the full row when narrow), its items tend to equal width and it scrolls inside itself when they do not fit.
 - All controls share one tier, so they share one height and wrapped rows stay level: leave `size` off the controls (default `m`); for a denser page wrap the toolbar in `<ControlSizeProvider value="s">`.
-- On a phone the primary action may drop its text and keep the icon with `aria-label`; never remove it.
+- On a phone the primary action takes its own row by itself; an icon-only action with `aria-label` stays beside the search instead. Never remove it.
 - The toolbar breaks by its own width, so it behaves the same with the sidebar open or closed.
 
 ## Accessibility
@@ -113,7 +115,7 @@ No keyboard interaction.
 ### ARIA
 - A plain `<div>`: when a page has more than one panel, give each `role="group"` and an `aria-label` (a name on a `<div>` without a role is ignored by assistive tech).
 - Slots move only visually (`order`); the Tab order is the JSX order. Write the slots in the reading order of the wide layout — Tools, Sections, View, Actions, Chips. In the narrow layout the action is shown beside the tools but reached after the view.
-- An icon-only primary action on a narrow page carries `aria-label`.
+- An icon-only primary action carries `aria-label`.
 
 ### Labels
 <!-- Generated from api.ts by `bun run docs:build`. Edit api.ts, not this section. -->
@@ -126,7 +128,7 @@ No `labels`.
 | [overview.tsx](examples/overview.tsx) | The panel of an orders page: search and filter, sections with counts, the period and the primary action in one row; active filters right under the search — `PageToolbar.Tools`, `PageToolbar.Sections`, `PageToolbar.View`, `PageToolbar.Actions`, `PageToolbar.Chips`. |
 | [without-search.tsx](examples/without-search.tsx) | A dashboard panel without search on a tablet-width column: the sections fill the top row, the period selector alone in the bottom row stretches to the full width — `PageToolbar.Sections`, `PageToolbar.View`. |
 | [save-changes.tsx](examples/save-changes.tsx) | A settings page: sections of the form on the left, the save action with the number of changes at the end of the top row — never a sticky bar at the bottom of a phone screen — `PageToolbar.Actions`. |
-| [narrow.tsx](examples/narrow.tsx) | A phone-width column: search, filter and the primary action on top, the active filters under them, then the sections and the period, every row 12 apart — `PageToolbar.Root`. |
+| [narrow.tsx](examples/narrow.tsx) | A phone-width column: search and filter on top, the primary action on its own row under them, then the active filters, the sections and the period, every row 12 apart — `PageToolbar.Root`. |
 
 ## Mistakes
 - A hand-built flex row of tabs, search and buttons with `flex-wrap` → rows wrap «as they come», the action drifts down; use `PageToolbar`.

package/dist/skill/reference/components/page-toolbar/examples/narrow.tsx

@@ -1,4 +1,4 @@
-/** A phone-width column: search, filter and the primary action on top, the active filters under them, then the sections and the period, every row 12 apart — `PageToolbar.Root`. */
+/** A phone-width column: search and filter on top, the primary action on its own row under them, then the active filters, the sections and the period, every row 12 apart — `PageToolbar.Root`. */
 import {
   Button,
   Icon,
@@ -38,7 +38,9 @@ const FIELDS: SmartFilterField[] = [
 export default function PageToolbarNarrowExample() {
   const [section, setSection] = React.useState("all");
   const [period, setPeriod] = React.useState("7d");
-  const [filter, setFilter] = React.useState<SmartFilterValue>({});
+  const [filter, setFilter] = React.useState<SmartFilterValue>({
+    city: { include: ["msk"], exclude: [] },
+  });
   const [search, setSearch] = React.useState("");
 
   return (
@@ -87,10 +89,11 @@ export default function PageToolbarNarrowExample() {
             </Select.Root>
           </PageToolbar.View>
           <PageToolbar.Actions>
-            <Button.Root aria-label="Новый заказ">
+            <Button.Root>
               <Button.Icon>
                 <Icon name="action.add" />
               </Button.Icon>
+              Новый заказ
             </Button.Root>
           </PageToolbar.Actions>
           <PageToolbar.Chips>

package/dist/skill/reference/components/pagination/examples/controlled.tsx

@@ -16,36 +16,36 @@ export default function PaginationControlledExample() {
 
   return (
     <Card.Root>
-      <div className={styles.footer}>
-        <Typography as="span" variant="body-s" tone="secondary">
-          Счета {from}–{to} из {TOTAL_INVOICES}
-        </Typography>
-        <div className={styles.controls}>
-          <Select.Root
-            size="s"
-            value={perPage}
-            onValueChange={(next) => {
-              setPerPage(next);
-              setPage(1);
-            }}
-          >
-            <Select.Trigger aria-label="Строк на странице">
-              <Select.Value />
-            </Select.Trigger>
-            <Select.Content>
-              <Select.Item value="10">10 строк</Select.Item>
-              <Select.Item value="25">25 строк</Select.Item>
-              <Select.Item value="50">50 строк</Select.Item>
-            </Select.Content>
-          </Select.Root>
-          <Pagination
-            size="s"
-            value={page}
-            onValueChange={setPage}
-            totalPages={Math.ceil(TOTAL_INVOICES / pageSize)}
-          />
+      <Card.Body>
+        <div className={styles.footer}>
+          <Typography as="span" variant="body-s" tone="secondary">
+            Счета {from}–{to} из {TOTAL_INVOICES}
+          </Typography>
+          <div className={styles.controls}>
+            <Select.Root
+              value={perPage}
+              onValueChange={(next) => {
+                setPerPage(next);
+                setPage(1);
+              }}
+            >
+              <Select.Trigger aria-label="Строк на странице">
+                <Select.Value />
+              </Select.Trigger>
+              <Select.Content>
+                <Select.Item value="10">10 строк</Select.Item>
+                <Select.Item value="25">25 строк</Select.Item>
+                <Select.Item value="50">50 строк</Select.Item>
+              </Select.Content>
+            </Select.Root>
+            <Pagination
+              value={page}
+              onValueChange={setPage}
+              totalPages={Math.ceil(TOTAL_INVOICES / pageSize)}
+            />
+          </div>
         </div>
-      </div>
+      </Card.Body>
     </Card.Root>
   );
 }

package/dist/skill/reference/components/pagination/examples/examples.module.css

@@ -2,13 +2,11 @@
 
 /* A list footer in a Card: the range on the left, rows per page and pages on the right; wraps when narrow. */
 .footer {
-  box-sizing: border-box;
   display: flex;
   flex-wrap: wrap;
   align-items: center;
   justify-content: space-between;
   gap: var(--prime-space-3);
-  padding: var(--prime-space-3) var(--prime-space-4);
 }
 
 .controls {

package/dist/skill/reference/components/progress-bar/COMPONENT.md

@@ -177,7 +177,7 @@ No keyboard interaction.
 | [sizes.tsx](examples/sizes.tsx) | Every tier: the line grows from 4 to 8 px like the Slider track — `size`. |
 | [states.tsx](examples/states.tsx) | Loading takes the bar's own geometry, so the data lands without a jump — `loading`. |
 | [custom-max.tsx](examples/custom-max.tsx) | A scale of steps instead of percent: 3 of 5 profile steps — `max`. |
-| [segments.tsx](examples/segments.tsx) | Parts of a whole in one bar: joined or separate pills, free capacity up to `max` and an empty list — `segments`, `segmentGap`, `max`. |
+| [segments.tsx](examples/segments.tsx) | Parts of a whole in one bar: joined or separate pills, free capacity up to `max` and an empty list with its own spoken text — `segments`, `segmentGap`, `max`, `labels`. |
 | [legend.tsx](examples/legend.tsx) | Shares of categories in their chart colors with a legend of color · name · value · share — `color`, `legend`, `formatValue`. |
 | [ranking.tsx](examples/ranking.tsx) | Rankings as rows of label · value · share over a bar: top cities against the leader and a funnel against its first step — `layout`, `scale`. |
 | [steps.tsx](examples/steps.tsx) | The scale as whole cells that fill one after another: 2 of 5 onboarding steps, forward and back — `steps`, `max`. |

package/dist/skill/reference/components/progress-bar/examples/segments.tsx

@@ -1,4 +1,4 @@
-/** Parts of a whole in one bar: joined or separate pills, free capacity up to `max` and an empty list — `segments`, `segmentGap`, `max`. */
+/** Parts of a whole in one bar: joined or separate pills, free capacity up to `max` and an empty list with its own spoken text — `segments`, `segmentGap`, `max`, `labels`. */
 import { ProgressBar, type ProgressSegment } from "prime-ui-kit";
 
 import styles from "./examples.module.css";
@@ -26,7 +26,7 @@ export default function ProgressBarSegmentsExample() {
         label="Хранилище: 71 из 100 ГБ"
         showValue
       />
-      <ProgressBar segments={[]} label="Нет данных за период" />
+      <ProgressBar segments={[]} label="Заявки за ноябрь" labels={{ empty: "Заявок пока нет" }} />
     </div>
   );
 }

package/dist/skill/reference/components/progress-circle/COMPONENT.md

@@ -171,7 +171,7 @@ No keyboard interaction.
 | [states.tsx](examples/states.tsx) | Loading is a Skeleton ring of the same diameter and stroke; the number in the centre waits for the data — `loading`. |
 | [inner-content.tsx](examples/inner-content.tsx) | The center holds a percentage, a count on its own scale or an icon — `children`, `max`. |
 | [under-way.tsx](examples/under-way.tsx) | An import whose share is not known yet turns a quarter arc, then fills and swaps its icon; a sync turns while its share grows — `value`, `spin`, `children`. |
-| [segments.tsx](examples/segments.tsx) | Parts of a whole clockwise from the top: a closed ring, free capacity up to `max`, separate arcs and an empty list — `segments`, `segmentGap`. |
+| [segments.tsx](examples/segments.tsx) | Parts of a whole clockwise from the top: a closed ring, free capacity up to `max`, separate arcs and an empty list with its own spoken text — `segments`, `segmentGap`, `labels`. |
 | [legend.tsx](examples/legend.tsx) | A ring of category shares with a legend beside it, in the categories' chart colors — `color`, `legend`, `formatValue`. |
 
 ## Mistakes

package/dist/skill/reference/components/progress-circle/examples/segments.tsx

@@ -1,4 +1,4 @@
-/** Parts of a whole clockwise from the top: a closed ring, free capacity up to `max`, separate arcs and an empty list — `segments`, `segmentGap`. */
+/** Parts of a whole clockwise from the top: a closed ring, free capacity up to `max`, separate arcs and an empty list with its own spoken text — `segments`, `segmentGap`, `labels`. */
 import { ProgressCircle, type ProgressSegment, Typography } from "prime-ui-kit";
 
 import styles from "./examples.module.css";
@@ -54,9 +54,14 @@ export default function ProgressCircleSegmentsExample() {
         </Typography>
       </div>
       <div className={styles.item}>
-        <ProgressCircle size="xl" segments={[]} aria-label="Нет данных" />
+        <ProgressCircle
+          size="xl"
+          segments={[]}
+          aria-label="Заявки за ноябрь"
+          labels={{ empty: "Заявок пока нет" }}
+        />
         <Typography as="span" variant="caption" tone="muted">
-          Нет данных
+          Заявки за ноябрь
         </Typography>
       </div>
     </div>

package/dist/skill/reference/components/radio/COMPONENT.md

@@ -152,6 +152,7 @@ The radiogroup carries `data-size`, `data-orientation`, `aria-orientation`, `ari
 | [group.tsx](examples/group.tsx) | A required group with option descriptions and the group's error under the options — `label`, `required`, `hint`, `error`. |
 | [orientation.tsx](examples/orientation.tsx) | Options stacked in a column and laid out in a wrapping row — `orientation`. |
 | [controlled.tsx](examples/controlled.tsx) | The parent owns the chosen plan and shows it in the hint — `value`, `onValueChange`. |
+| [in-form.tsx](examples/in-form.tsx) | Choices of an order form: a required group shows its error after a submit without a choice, an optional one is marked — `name`, `required`, `optional`, `error`. |
 
 ## Mistakes
 - `Radio.Root` outside `Radio.Group` → it throws; every option needs the group.

package/dist/skill/reference/components/radio/examples/examples.module.css

@@ -0,0 +1,14 @@
+/* Layout of the Radio scenarios: semantic tokens only. */
+
+/* in-form.tsx: groups, then actions (group → actions 32). */
+.form {
+  display: flex;
+  flex-direction: column;
+  gap: var(--prime-space-6);
+  width: min(100%, var(--prime-modal-width-s));
+}
+
+.formActions {
+  display: flex;
+  margin-top: var(--prime-space-2);
+}