@recursica/mantine-adapter 0.45.0 → 0.47.0

package/package.json

@@ -13,7 +13,7 @@
     "url": "git+https://github.com/borderux/recursica.git",
     "directory": "packages/mantine-adapter"
   },
-  "version": "0.45.0",
+  "version": "0.47.0",
   "type": "module",
   "main": "./dist/mantine-adapter.cjs",
   "module": "./dist/mantine-adapter.js",
@@ -94,7 +94,7 @@
     "vitest": "^3.2.4"
   },
   "dependencies": {
-    "@recursica/adapter-common": "^0.20.0",
+    "@recursica/adapter-common": "^0.22.0",
     "@recursica/official-release": "^2.8.0"
   },
   "peerDependencies": {

package/src/components/Accordion/Accordion.tsx

@@ -25,7 +25,7 @@ import {
 export type AccordionProps = RecursicaOverStyled<
   Omit<
     MantineAccordionProps,
-    "value" | "defaultValue" | "onChange" | "multiple" | "variant"
+    "value" | "defaultValue" | "multiple" | "variant"
   > &
     RecursicaAccordionProps
 >;

package/src/components/Checkbox/CheckboxGroup.tsx

@@ -19,7 +19,7 @@ import { type RecursicaCheckboxGroupProps as BaseRecursicaCheckboxGroupProps } f
 export interface RecursicaCheckboxGroupProps
   extends Omit<
       MantineCheckboxGroupProps,
-      "size" | "labelProps" | "defaultValue" | "value" | "onChange"
+      "size" | "labelProps" | "defaultValue" | "value"
     >,
     Omit<
       RecursicaFormControlWrapperProps,

package/src/components/Chip/CHIP_IMPLEMENTATION_NOTES.md

@@ -20,7 +20,7 @@ To achieve this without breaking Mantine's `Chip` input architecture, we wrapped
 <span className={styles.innerWrapper}>
   {icon}
   <span className={styles.children}>{children}</span>
-  {onRemove}
+  {onDelete}
 </span>
 ```
 
@@ -42,10 +42,10 @@ During implementation, the parsed Figma design tokens natively exported specific
 `.children` already had `text-overflow: ellipsis; overflow: hidden; white-space: nowrap;`, but
 neither it nor its parent `.innerWrapper` had `min-width: 0` — a flex child without that refuses
 to shrink below its intrinsic (full, unwrapped) content width, so `text-overflow: ellipsis` never
-actually engaged. A long label overflowed the flex row instead, and since `.removeIcon` had no
+actually engaged. A long label overflowed the flex row instead, and since `.deleteIcon` had no
 `flex-shrink: 0`, it got squeezed out of the clipped (`max-width`-bounded) chip entirely. Fixed by
 adding `min-width: 0` to `.innerWrapper`/`.children` and `flex-shrink: 0` to `.leadingIcon`/
-`.removeIcon`. Reproduces easily with `FileUpload`'s file list, since its chip `max-width`
+`.deleteIcon`. Reproduces easily with `FileUpload`'s file list, since its chip `max-width`
 (`--recursica_ui-kit_components_chip_properties_max-width`, 200px) is small enough that most real
 filenames overflow it.
 
@@ -63,24 +63,24 @@ y-axis has no visual side effect.
 
 ### Roving tabindex support for chip groups (Matt Massey, 2026-08-17)
 
-Added two optional pass-through props — `removeTabIndex` and `removeIconRef` — purely so a parent
+Added two optional pass-through props — `deleteTabIndex` and `deleteIconRef` — purely so a parent
 managing a _group_ of chips (e.g. `FileUpload`'s file list, see its own `IMPLEMENTATION_NOTES.md`)
-can implement roving-tabindex/arrow-key navigation across them: set `removeTabIndex={-1}` on every
-chip but the currently-active one, and use `removeIconRef` to move real DOM focus there
+can implement roving-tabindex/arrow-key navigation across them: set `deleteTabIndex={-1}` on every
+chip but the currently-active one, and use `deleteIconRef` to move real DOM focus there
 imperatively on arrow-key press. Both are no-ops for a standalone `Chip` (defaults: `tabIndex={0}`,
 no ref) — this doesn't change any existing single-chip behavior.
 
 ### `isInteractive` was measuring the wrong signal, and leaked a pointer cursor + phantom Tab stop (Matt Massey, 2026-08-18)
 
 A `Chip` rendered with `checked` but no real handler (e.g. `FileUpload`'s `readOnly` file list —
-`<Chip checked={false} tabIndex={-1}>`, no `onRemove`) still looked and behaved clickable, from two
+`<Chip checked={false} tabIndex={-1}>`, no `onDelete`) still looked and behaved clickable, from two
 separate bugs:
 
 - `isInteractive` treated `checked !== undefined` (even `false`) as proof of interactivity. That's
   the wrong signal — a `checked`-controlled chip with no `onChange` can't actually be toggled by a
   click (Mantine's `useUncontrolled` discards the click when `value` is externally controlled), so
   clicking it does nothing observable regardless. `isInteractive` now only looks at whether
-  something actually responds: `onRemove`, `onClick`, or `onChange`.
+  something actually responds: `onDelete`, `onClick`, or `onChange`.
 - `.label.label` never set its own `cursor`, so Mantine's base style (`cursor: pointer`, hardcoded
   on the underlying `mantine-Chip-label` class) always leaked through, independent of whether the
   chip was actually interactive. Reset it to `cursor: default` and added a `data-interactive`

package/src/components/Chip/Chip.module.css

@@ -55,7 +55,7 @@
   background: transparent; /* HARDCODE: Mantine forces background styling on label */
   cursor: default; /* HARDCODE: Mantine's own base styles hardcode cursor: pointer on this class —
     override it to plain default, then only re-enable it below for a chip with a real handler
-    (onRemove/onClick/onChange — see Chip.tsx's `isInteractive`). A display-only chip (e.g. a
+    (onDelete/onClick/onChange — see Chip.tsx's `isInteractive`). A display-only chip (e.g. a
     read-only FileUpload file list) has nothing for a click to do, so it shouldn't look clickable. */
   border-style: solid;
   border-width: var(--recursica_ui-kit_components_chip_properties_border-size);
@@ -224,11 +224,11 @@
   height: 100%;
 }
 
-.removeIcon {
+.deleteIcon {
   display: inline-flex;
   align-items: center;
   justify-content: center;
-  flex-shrink: 0; /* HARDCODE: keep the remove icon visible when the label truncates instead */
+  flex-shrink: 0; /* HARDCODE: keep the delete icon visible when the label truncates instead */
   color: var(--chip-close);
   width: var(--recursica_ui-kit_components_chip_properties_close-icon-size);
   height: var(--recursica_ui-kit_components_chip_properties_close-icon-size);
@@ -237,7 +237,7 @@
   outline: none;
 }
 
-.removeIcon:focus-visible {
+.deleteIcon:focus-visible {
   box-shadow:
     0 0 0 var(--recursica_brand_states_focus_border-size)
       var(--recursica_brand_states_focus_color),
@@ -246,7 +246,7 @@
       var(--recursica_brand_states_focus_color);
 }
 
-.removeIcon svg {
+.deleteIcon svg {
   width: 100%;
   height: 100%;
 }

package/src/components/Chip/Chip.stories.tsx

@@ -12,7 +12,7 @@ const meta: Meta<ChipStoryProps> = {
     docs: {
       description: {
         component:
-          "The Chip component is used to represent interactive selections, descriptive tags, or dynamic filters natively bounded to Recursica variables. It can be used as a toggleable input, can render a custom leading `icon`, and handles close constraints automatically via the `onRemove` property.",
+          "The Chip component is used to represent interactive selections, descriptive tags, or dynamic filters natively bounded to Recursica variables. It can be used as a toggleable input, can render a custom leading `icon`, and handles close constraints automatically via the `onDelete` property.",
       },
     },
   },
@@ -86,7 +86,7 @@ export const Removable: Story = {
   args: {
     children: "Dismissible",
     checked: false,
-    onRemove: () => console.log("Removal Action Triggered"),
+    onDelete: () => console.log("Removal Action Triggered"),
   },
   render: (args: ChipStoryProps) => <Chip {...args} />,
 };

package/src/components/Chip/Chip.tsx

@@ -41,10 +41,10 @@ export const Chip = forwardRef<HTMLInputElement, ChipProps>(function Chip(
   {
     error = false,
     icon,
-    onRemove,
-    removeLabel = "Remove",
-    removeTabIndex,
-    removeIconRef,
+    onDelete,
+    deleteLabel = "Delete",
+    deleteTabIndex,
+    deleteIconRef,
     children,
     overStyled = false,
     wrapperProps,
@@ -75,13 +75,13 @@ export const Chip = forwardRef<HTMLInputElement, ChipProps>(function Chip(
 
   // Determine state
   const dataError = error ? "" : undefined;
-  const isIconOnly = !children && (!!icon || !!onRemove);
+  const isIconOnly = !children && (!!icon || !!onDelete);
   // A chip only counts as interactive when something actually responds to it — merely passing a
   // `checked` value (e.g. to pin a display-only chip to a fixed visual state, as FileUpload's
   // read-only file list does) isn't itself an interaction, since clicking it with no onChange/
   // onClick wired does nothing observable.
   const isInteractive =
-    onRemove !== undefined ||
+    onDelete !== undefined ||
     restRecord.onClick !== undefined ||
     restRecord.onChange !== undefined;
 
@@ -119,27 +119,27 @@ export const Chip = forwardRef<HTMLInputElement, ChipProps>(function Chip(
 
         <span className={styles.children}>{children}</span>
 
-        {onRemove && (
+        {onDelete && (
           <span
-            ref={removeIconRef}
+            ref={deleteIconRef}
             role="button"
-            className={styles.removeIcon}
+            className={styles.deleteIcon}
             onClick={(e) => {
               e.preventDefault();
               e.stopPropagation();
-              onRemove(e);
+              onDelete(e);
             }}
-            aria-label={removeLabel}
+            aria-label={deleteLabel}
             onKeyDown={(e) => {
               if (e.key === "Enter" || e.key === " ") {
                 e.preventDefault();
                 e.stopPropagation();
-                onRemove(
+                onDelete(
                   e as unknown as React.MouseEvent<HTMLSpanElement, MouseEvent>,
                 );
               }
             }}
-            tabIndex={removeTabIndex ?? 0}
+            tabIndex={deleteTabIndex ?? 0}
           >
             <CloseIcon />
           </span>

package/src/components/Chip/USAGE.md

@@ -49,7 +49,7 @@ Chip does not support a `size` prop; chips render at a fixed size.
 
 ### Building a keyboard-navigable chip group
 
-`removeTabIndex` and `removeIconRef` are optional escape hatches for composing a _group_ of chips
+`deleteTabIndex` and `deleteIconRef` are optional escape hatches for composing a _group_ of chips
 with roving-tabindex keyboard navigation (Tab reaches one chip at a time, arrow keys move between
 them) — see `FileUpload`'s file list for a working example. Ignore both for a standalone chip; they
-default to a normal `tabIndex={0}` remove icon with no ref.
+default to a normal `tabIndex={0}` delete icon with no ref.

package/src/components/Dropdown/Dropdown.module.css

@@ -174,7 +174,7 @@
    hover background, neither of which is Recursica-token-driven. The double class selector (same
    specificity-boosting trick as Chip.module.css's `.root.root`) beats that default without
    needing `!important`. Same icon-size/trailing-icon tokens as the rest of this section, same
-   focus-visible ring technique as Chip's own `.removeIcon` — the established inline icon-button
+   focus-visible ring technique as Chip's own `.deleteIcon` — the established inline icon-button
    pattern elsewhere in this adapter. */
 .clearButton.clearButton {
   width: var(--recursica_ui-kit_components_dropdown_properties_icon-size);

package/src/components/FileInput/FILEINPUT_IMPLEMENTATION_NOTES.md

@@ -20,7 +20,7 @@ The control is one clickable, focusable `<div role="button">` containing:
    single- and multiple-file mode render identically here; only the selection/replace behavior
    differs (see "`multiple` defaults to `false`" below).
 3. **A trailing "clear" `Button`** — shown whenever a file is selected; clears the entire current
-   selection (see "Trailing clear button" below).
+   selection, icon overridable via `clearIcon` (see "Trailing clear button" below).
 4. **A hidden `<input type="file">`**, triggered programmatically — same approach as
    `FileUpload`'s dropzone, not the "invisible overlay input" pattern some styled file inputs use
    (that pattern would need every interactive child — chip remove icons, the clear icon — to sit
@@ -107,7 +107,9 @@ color/disabled states, so `file-input`'s own `properties_colors_trailing-icon` t
 entirely. Clicking/activating it calls `onFileRemove` once per currently-selected file (reusing
 the same callback `FileUpload`'s individual chip removal uses, rather than introducing a separate
 `onClear` prop) — in single-file mode that's one call; in multiple-file mode it clears everything
-at once, distinct from a chip's own individual remove icon.
+at once, distinct from a chip's own individual remove icon. The icon itself defaults to the
+built-in X glyph and is overridable via `clearIcon` — the same pattern as the leading `icon`,
+giving Forge's `leading-icon`/`trailing-icon` token pair a matching pair of override props.
 
 ## Why each chip is wrapped with its own `stopPropagation`
 
@@ -121,7 +123,7 @@ it needed no changes for this.
 
 ## Keyboard navigation for the chip row
 
-Same roving-tabindex model as `FileUpload`'s file list (`activeChipIndex`, `removeIconRefs`,
+Same roving-tabindex model as `FileUpload`'s file list (`activeChipIndex`, `deleteIconRefs`,
 Left/Right/Up/Down roving, focus-survives-removal `useEffect`) — reused rather than reinvented,
 and applies in single-file mode too (a one-chip roving group is a no-op but needs no special
 casing). The only addition specific to `FileInput` is that `Tab` reaches the root control itself
@@ -140,7 +142,7 @@ already made for `.value`'s ellipsis truncation.
 
 `readOnly` renders the same content (placeholder/filename/chip row) but the root loses its
 `role="button"` interactivity (no `tabIndex`, no click/keyboard/drag handlers), chips render with
-no `removeLabel`/`onRemove` (so `Chip` itself renders no remove icon, same as `FileUpload`'s
+no `deleteLabel`/`onDelete` (so `Chip` itself renders no delete icon, same as `FileUpload`'s
 read-only chips), and the trailing clear icon is omitted entirely. `disabled` keeps the control
 structurally the same but inert (`tabIndex={-1}`, `aria-disabled`, no handlers, native `<input>`
 disabled) — both are computed together as a single `interactive` flag used throughout, but remain

package/src/components/FileInput/FileInput.stories.tsx

@@ -63,6 +63,9 @@ The \`FileInput\` component is a single-line, \`TextField\`-shaped control for c
     icon: {
       table: { disable: true },
     },
+    clearIcon: {
+      table: { disable: true },
+    },
     files: {
       table: { disable: true },
     },

package/src/components/FileInput/FileInput.tsx

@@ -125,6 +125,7 @@ export const FileInput = forwardRef<HTMLDivElement, FileInputProps>(
         ? `Maximum of ${maxFiles} files allowed`
         : "Only one file is allowed",
       icon,
+      clearIcon,
       placeholder = "Select a file...",
       browseLabel = "Choose file",
       removeFileLabel = "Remove",
@@ -235,10 +236,10 @@ export const FileInput = forwardRef<HTMLDivElement, FileInputProps>(
     };
 
     // Roving tabindex across the file chip list (single- or multiple-file mode): only the
-    // "active" chip's remove icon is a tab stop, and Left/Right/Up/Down move it — same pattern
+    // "active" chip's delete icon is a tab stop, and Left/Right/Up/Down move it — same pattern
     // as FileUpload, see FILEINPUT_IMPLEMENTATION_NOTES.md.
     const [activeChipIndex, setActiveChipIndex] = useState(0);
-    const removeIconRefs = useRef<Array<HTMLSpanElement | null>>([]);
+    const deleteIconRefs = useRef<Array<HTMLSpanElement | null>>([]);
     const prevFileCountRef = useRef(files?.length ?? 0);
 
     useEffect(() => {
@@ -246,7 +247,7 @@ export const FileInput = forwardRef<HTMLDivElement, FileInputProps>(
       if (count > 0 && count < prevFileCountRef.current) {
         const nextIndex = Math.min(activeChipIndex, count - 1);
         setActiveChipIndex(nextIndex);
-        removeIconRefs.current[nextIndex]?.focus();
+        deleteIconRefs.current[nextIndex]?.focus();
       }
       prevFileCountRef.current = count;
       // Only react to the file list itself shrinking/growing, not to activeChipIndex changes.
@@ -268,7 +269,7 @@ export const FileInput = forwardRef<HTMLDivElement, FileInputProps>(
       event.preventDefault();
       event.stopPropagation();
       setActiveChipIndex(nextIndex);
-      removeIconRefs.current[nextIndex]?.focus();
+      deleteIconRefs.current[nextIndex]?.focus();
     };
 
     // The built-in `accept`/cap-mismatch message is only shown when the integrator hasn't
@@ -353,14 +354,14 @@ export const FileInput = forwardRef<HTMLDivElement, FileInputProps>(
                       <Chip
                         checked={false}
                         tabIndex={-1}
-                        removeLabel={readOnly ? undefined : removeFileLabel}
-                        removeTabIndex={
+                        deleteLabel={readOnly ? undefined : removeFileLabel}
+                        deleteTabIndex={
                           !readOnly && index === activeChipIndex ? 0 : -1
                         }
-                        removeIconRef={(el) => {
-                          removeIconRefs.current[index] = el;
+                        deleteIconRef={(el) => {
+                          deleteIconRefs.current[index] = el;
                         }}
-                        onRemove={
+                        onDelete={
                           readOnly || disabled
                             ? undefined
                             : () => onFileRemove?.(itemId)
@@ -380,7 +381,7 @@ export const FileInput = forwardRef<HTMLDivElement, FileInputProps>(
               overStyled
               variant="text"
               size="small"
-              icon={<ClearIcon />}
+              icon={clearIcon ?? <ClearIcon />}
               aria-label={clearLabel}
               className={styles.trailingIcon}
               disabled={disabled}

package/src/components/FileInput/USAGE.md

@@ -57,6 +57,7 @@ rather than appending — picking a new file in single-file mode always replaces
 | `invalidFileTypeMessage` | `React.ReactNode`           | Error message shown when a file is rejected for not matching `accept`. Defaults to `"File type not accepted"`. An explicit `error` prop always takes priority over this.                                                             |
 | `maxFilesMessage`        | `React.ReactNode`           | Error message shown when a file is rejected for exceeding the cap. Defaults to `"Maximum of {maxFiles} files allowed"` when `multiple`, or `"Only one file is allowed"` otherwise. An explicit `error` prop always wins.             |
 | `icon`                   | `React.ReactNode`           | Leading icon shown inside the control. Defaults to the built-in upload icon.                                                                                                                                                         |
+| `clearIcon`              | `React.ReactNode`           | Trailing clear-all icon shown once a file is selected. Defaults to the built-in X icon.                                                                                                                                              |
 | `placeholder`            | `React.ReactNode`           | Text shown when no file is selected. Defaults to `"Select a file..."`.                                                                                                                                                               |
 | `browseLabel`            | `string`                    | Screen-reader label for the control itself (it's the sole interactive/focusable surface, there being no separate "Browse" button). Defaults to `"Choose file"`.                                                                      |
 | `removeFileLabel`        | `string`                    | Screen-reader label for a file chip's remove button. Defaults to `"Remove"`.                                                                                                                                                         |

package/src/components/FileUpload/FILEUPLOAD_IMPLEMENTATION_NOTES.md

@@ -11,7 +11,7 @@ deliberately did not add — see "Why not `@mantine/dropzone`" below). The compo
    (`onDragOver`/`onDrop`), containing an upload icon, instructional text, and a hidden
    `<input type="file">` triggered by...
 2. **The browse button** — this adapter's own `<Button variant="outline" size="small">`.
-3. **The file list** — this adapter's own `<Chip>` component (with `onRemove`), one per entry in
+3. **The file list** — this adapter's own `<Chip>` component (with `onDelete`), one per entry in
    the controlled `files` prop.
 
 This shape is **not configurable** — there is no prop to render a bare native file input without
@@ -34,7 +34,7 @@ Massey, 2026-08-11.)
 (spacing between/around file entries) but **no color/border tokens of its own for the file
 entries themselves** — the visual design intentionally delegates that to the existing `Chip`
 component's own token namespace (`--recursica_ui-kit_components_chip_...`). Reusing `<Chip
-onRemove={...}>` directly (rather than reimplementing a similar-looking element) keeps that
+onDelete={...}>` directly (rather than reimplementing a similar-looking element) keeps that
 separation intact per the canonical guide's "Component Specificity" rule — `FileUpload.module.css`
 never reaches into `chip`'s namespace, and `Chip.module.css` never reaches into `file-upload`'s.
 
@@ -95,9 +95,9 @@ list's read-only form is the same chip list, just without the ability to remove
 `readOnly` is handled directly in `FileUpload.tsx` rather than reusing `WithReadOnlyWrapper`:
 
 - The dropzone (icon, instructional text, Browse button, hidden `<input>`) is omitted entirely.
-- Each `Chip` is rendered with no `onRemove` (and no `removeTabIndex`/`removeIconRef`/roving
+- Each `Chip` is rendered with no `onDelete` (and no `deleteTabIndex`/`deleteIconRef`/roving
   keyboard handlers, which only exist to manage the remove icon) — `Chip` itself already renders no
-  remove icon at all when `onRemove` is `undefined`, so this falls out for free rather than needing
+  remove icon at all when `onDelete` is `undefined`, so this falls out for free rather than needing
   a separate `readOnly` prop on `Chip`.
 - `disabled` is independent of `readOnly` and has no effect when `readOnly` is set (there's no
   dropzone/remove icon left for it to disable).
@@ -171,12 +171,12 @@ adapters).
 The file list previously had no group-level keyboard model at all — each chip's remove icon was
 simply the next `tabIndex={0}` element in natural DOM order (and, in the Mantine adapter, so was
 each chip's own hidden checkbox `<input>`, since `Chip`'s `isInteractive` check treats any chip
-with `onRemove` as tabbable-by-default — a second, redundant tab stop specific to this adapter).
+with `onDelete` as tabbable-by-default — a second, redundant tab stop specific to this adapter).
 Implemented a standard roving-tabindex pattern instead, matching `Tree`'s existing keyboard model
 (see `../Tree/IMPLEMENTATION_NOTES.md`) rather than inventing a new one:
 
 - **Tab reaches exactly one stop per chip list, landing on the first chip.** `FileUpload` tracks
-  `activeChipIndex` (initially `0`) and passes `removeTabIndex={index === activeChipIndex ? 0 : -1}`
+  `activeChipIndex` (initially `0`) and passes `deleteTabIndex={index === activeChipIndex ? 0 : -1}`
   to each `Chip` — a new pass-through prop added to `RecursicaChipProps`/both adapters' `Chip.tsx`
   (see `../Chip/CHIP_IMPLEMENTATION_NOTES.md`) that overrides the remove icon's own tabIndex. Every
   chip in the Mantine adapter is also given a plain `tabIndex={-1}` directly (flows through to
@@ -184,13 +184,13 @@ Implemented a standard roving-tabindex pattern instead, matching `Tree`'s existi
   kill that second, unwanted tab stop — the chip's label/checkbox was never meant to be
   interactive here (`checked={false}`, no `onChange`), only its remove icon is.
 - **Enter removes the focused chip, with focus already on its remove icon.** No new code needed —
-  `Chip`'s remove icon already calls `onRemove` on `Enter`/`Space`, and it's already the focused
+  `Chip`'s remove icon already calls `onDelete` on `Enter`/`Space`, and it's already the focused
   element by construction (see above), so "focus ring on the remove icon" falls out for free from
-  the existing `.removeIcon:focus-visible` style.
+  the existing `.deleteIcon:focus-visible` style.
 - **Left/Right or Up/Down move focus between chips.** A `onKeyDown` handler on the file list `<div>`
   (event delegation — it fires for keydowns on any focused chip inside it) computes the next index
-  (wrapping at both ends) and moves real DOM focus there via `removeIconRefs`, an array of refs
-  populated through the new `removeIconRef` prop on `Chip` (same PR as `removeTabIndex`).
+  (wrapping at both ends) and moves real DOM focus there via `deleteIconRefs`, an array of refs
+  populated through the new `deleteIconRef` prop on `Chip` (same PR as `deleteTabIndex`).
 - **Focus survives removal.** Since `files` is a controlled prop `FileUpload` doesn't mutate
   itself, removing a chip doesn't shrink `files` until the consumer's own state update flows back
   down as a new prop — a `useEffect` keyed on `files` detects the length decreasing, clamps
@@ -211,7 +211,7 @@ triggers both.
 ## Read-only chips were still interactive (Matt Massey, 2026-08-18)
 
 The `readOnly` file list (added 2026-08-18, see USAGE.md §7) rendered each filename as a
-`<Chip checked={false} tabIndex={-1}>` with no `onRemove`, expecting that to be fully inert. Two
+`<Chip checked={false} tabIndex={-1}>` with no `onDelete`, expecting that to be fully inert. Two
 separate, previously-latent bugs made it look and behave otherwise — both fixed in
 `Chip`/`Chip.module.css`, not `FileUpload` itself, so every consumer of a non-interactive `Chip`
 benefits, not just this one:
@@ -221,7 +221,7 @@ benefits, not just this one:
   the tabbable/exposed branch — but a `checked`-controlled chip with no `onChange` can't actually be
   toggled by a click (Mantine's `useUncontrolled` just ignores the click when `value` is externally
   controlled), so that heuristic was measuring the wrong thing. `isInteractive` now only looks at
-  whether something actually responds to interaction: `onRemove`, `onClick`, or `onChange`.
+  whether something actually responds to interaction: `onDelete`, `onClick`, or `onChange`.
 - **A read-only chip's cursor still showed `pointer` on hover.** Mantine's own base styles hardcode
   `cursor: pointer` on the chip label class; our CSS never overrode it, so it always leaked through
   regardless of the chip's actual behavior. `.label.label` now resets it to `cursor: default` and a

package/src/components/FileUpload/FileUpload.tsx

@@ -194,11 +194,11 @@ export const FileUpload = forwardRef<HTMLDivElement, FileUploadProps>(
       event.target.value = "";
     };
 
-    // Roving tabindex across the file chip list: only the "active" chip's remove icon is a tab
+    // Roving tabindex across the file chip list: only the "active" chip's delete icon is a tab
     // stop (Tab lands on the first chip), and Left/Right/Up/Down move it — see
     // FILEUPLOAD_IMPLEMENTATION_NOTES.md.
     const [activeChipIndex, setActiveChipIndex] = useState(0);
-    const removeIconRefs = useRef<Array<HTMLSpanElement | null>>([]);
+    const deleteIconRefs = useRef<Array<HTMLSpanElement | null>>([]);
     const prevFileCountRef = useRef(files?.length ?? 0);
 
     useEffect(() => {
@@ -208,7 +208,7 @@ export const FileUpload = forwardRef<HTMLDivElement, FileUploadProps>(
       if (count > 0 && count < prevFileCountRef.current) {
         const nextIndex = Math.min(activeChipIndex, count - 1);
         setActiveChipIndex(nextIndex);
-        removeIconRefs.current[nextIndex]?.focus();
+        deleteIconRefs.current[nextIndex]?.focus();
       }
       prevFileCountRef.current = count;
       // Only react to the file list itself shrinking/growing, not to activeChipIndex changes.
@@ -229,7 +229,7 @@ export const FileUpload = forwardRef<HTMLDivElement, FileUploadProps>(
       if (nextIndex === undefined) return;
       event.preventDefault();
       setActiveChipIndex(nextIndex);
-      removeIconRefs.current[nextIndex]?.focus();
+      deleteIconRefs.current[nextIndex]?.focus();
     };
 
     // The built-in `accept`-mismatch message is only shown when the integrator hasn't supplied
@@ -330,12 +330,12 @@ export const FileUpload = forwardRef<HTMLDivElement, FileUploadProps>(
                       key={itemId}
                       checked={false}
                       tabIndex={-1}
-                      removeLabel={removeFileLabel}
-                      removeTabIndex={index === activeChipIndex ? 0 : -1}
-                      removeIconRef={(el) => {
-                        removeIconRefs.current[index] = el;
+                      deleteLabel={removeFileLabel}
+                      deleteTabIndex={index === activeChipIndex ? 0 : -1}
+                      deleteIconRef={(el) => {
+                        deleteIconRefs.current[index] = el;
                       }}
-                      onRemove={
+                      onDelete={
                         disabled ? undefined : () => onFileRemove?.(itemId)
                       }
                     >

package/src/components/Radio/RadioGroup.tsx

@@ -19,7 +19,7 @@ import { type RecursicaRadioGroupProps as BaseRecursicaRadioGroupProps } from "@
 export interface RecursicaRadioGroupProps
   extends Omit<
       MantineRadioGroupProps,
-      "size" | "labelProps" | "defaultValue" | "value" | "onChange"
+      "size" | "labelProps" | "defaultValue" | "value"
     >,
     Omit<
       RecursicaFormControlWrapperProps,

package/src/components/SegmentedControl/IMPLEMENTATION_NOTES.md

@@ -15,3 +15,11 @@ Mantine uses an `::before` pseudo-element on the `.control` block to draw standa
 ## 4. Indicator Mapping
 
 The moving active background element (`.indicator`) is decoupled from the actual text label. It is styled natively with its own background color, border size, and elevation shadow variables to match the exact visual parity of a "floating active chip" as defined in the Recursica properties map.
+
+## 5. Per-item `icon`
+
+`RecursicaSegmentedControlProps.data` objects accept an optional `icon`. Mantine's own `data` item has no such slot, so this component `Omit`s Mantine's native `data` type and composes `icon`+`label` into a single `label` ReactNode before handing it to Mantine — Mantine's own `innerLabel` wrapper then lays it out using the icon-size/gap tokens already present in `SegmentedControl.module.css`.
+
+## 6. Whole-control `disabled`
+
+`RecursicaSegmentedControlProps.disabled` was previously typed `never` and stripped at runtime. It's now a real `boolean?`, passed straight through to Mantine's own native `disabled` — Mantine's `SegmentedControl` already disables every item when set. Per-item disabling via `data[].disabled` continues to work independently of it.

package/src/components/SegmentedControl/SegmentedControl.stories.tsx

@@ -21,7 +21,9 @@ const meta: Meta<typeof SegmentedControl> = {
     fullWidth: {
       control: "boolean",
     },
-    disabled: { table: { disable: true } },
+    disabled: {
+      control: "boolean",
+    },
     data: { table: { disable: true } },
     defaultChecked: { table: { disable: true } },
   },
@@ -64,6 +66,17 @@ export const Vertical: Story = {
   },
 };
 
+export const Disabled: Story = {
+  args: {
+    data: ["Preview", "Code", "Edit"],
+    disabled: true,
+  },
+  // eslint-disable-next-line @typescript-eslint/no-explicit-any, @typescript-eslint/no-unused-vars
+  render: ({ withLayer, layer, ...args }: any) => {
+    return <SegmentedControl {...args} />;
+  },
+};
+
 const CheckIcon = () => (
   <svg
     viewBox="0 0 24 24"
@@ -81,33 +94,9 @@ const CheckIcon = () => (
 export const WithIcons: Story = {
   args: {
     data: [
-      {
-        value: "daily",
-        label: (
-          <>
-            <CheckIcon />
-            <span>Daily</span>
-          </>
-        ),
-      },
-      {
-        value: "weekly",
-        label: (
-          <>
-            <CheckIcon />
-            <span>Weekly</span>
-          </>
-        ),
-      },
-      {
-        value: "monthly",
-        label: (
-          <>
-            <CheckIcon />
-            <span>Monthly</span>
-          </>
-        ),
-      },
+      { value: "daily", label: "Daily", icon: <CheckIcon /> },
+      { value: "weekly", label: "Weekly", icon: <CheckIcon /> },
+      { value: "monthly", label: "Monthly", icon: <CheckIcon /> },
     ],
   },
   // eslint-disable-next-line @typescript-eslint/no-explicit-any, @typescript-eslint/no-unused-vars