@uni-design-system/uni-angular 9.0.1 → 10.1.0

package/CHANGELOG.md

@@ -1,5 +1,548 @@
 # @uni-design-system/uni-angular
 
+## 10.1.0
+
+### Minor Changes
+
+- [`f28c951`](https://github.com/uni-design-system/uni/commit/f28c95117f2844b58a265b59c2ea8b9715156670) Thanks [@gaenglish](https://github.com/gaenglish)! - `uni-drawer` gains the API an editor panel needs, and a close it can refuse.
+
+  **Closing can now be vetoed.** Escape, the backdrop, the header's close button
+  and the footer's cancel all funnel through one decision that emits
+  `closeRequest` with a `reason` — `'escape' | 'backdrop' | 'close-button'`. Set
+  `disableAutoClose` and the drawer stops acting on its own: it asks, and waits
+  for you to set `open`.
+
+  That split exists because the confirmation it has to accommodate is
+  _asynchronous_. A synchronous veto — a preventable event — cannot express
+  "ask the user, then decide", so every consumer would prevent unconditionally
+  and close manually anyway. Leave `disableAutoClose` off and behaviour is
+  unchanged, so adding a listener alone breaks nothing.
+
+  ```html
+  <uni-drawer [(open)]="open" [disableAutoClose]="form.dirty()" (closeRequest)="confirmDiscard()" />
+  ```
+
+  New inputs: `width` (per-instance override of the theme's width — a nav drawer
+  is 280 and an editor panel 480, and both live in one app), `headline` and
+  `defaultCloseButton` for the header row, and `initialFocus`, a selector resolved
+  inside the panel when it opens.
+
+  **`ariaLabel` no longer defaults to `'Navigation'`.** A drawer with a header is
+  labelled by that header via `aria-labelledby`; without one, `ariaLabel` is used;
+  with neither, the drawer is unnamed. The old default meant every drawer that
+  wasn't a nav drawer announced itself as one, and a wrong accessible name is
+  worse than a missing one — the missing one is at least caught by an audit. If
+  you relied on it, set `ariaLabel="Navigation"` explicitly.
+
+  **`scrim` turns the dimming off** without changing the modality. As a `scrim`
+  input or a `drawer.behavior.scrim` theme option, false leaves `::backdrop`
+  transparent so the page behind stays legible — an editor panel beside a board
+  the user is still reading. Focus is still trapped and the page behind is still
+  inert: it is a visibility choice, not a modality one. `background` joins it,
+  selecting `solid`, `glass` or `gradient` as a token choice rather than per-app
+  CSS.
+
+  **Fixed: a closed overlay drawer rendered in normal flow behind the page.** The
+  panel's `display: flex` outranks the UA stylesheet's
+  `dialog:not([open]) { display: none }`, so the drawer was visible on first
+  paint and reappeared behind the content after every close. An explicit
+  `&:not([open])` rule restores it. The closing animation is unaffected — `open`
+  is only removed once it ends.
+
+- [`f28c951`](https://github.com/uni-design-system/uni/commit/f28c95117f2844b58a265b59c2ea8b9715156670) Thanks [@gaenglish](https://github.com/gaenglish)! - `uni-drawer` is a three-row panel, and is no longer its own scroll container.
+
+  **The `<dialog>` used to be the scroller.** `over` mode set `overflowY: 'auto'`
+  on the panel and put the theme's padding there too, which made a pinned header
+  or footer impossible: padding on a scrolling box scrolls away with its content,
+  and any row you pinned against it could not sit flush to the panel edge. It also
+  set only the one axis — and a single explicit overflow axis computes the other
+  to `auto`, which is exactly how a container becomes an accidental scroller.
+  `side` had it right already, setting both.
+
+  The panel is now a flex column of three rows — an optional
+  `[uni-drawer-header]`, the projected body, an optional `[uni-drawer-buttons]`
+  (alias `[drawer-buttons]`) — and **only the body scrolls**. The panel itself is
+  `overflow: clip` on both axes, explicitly, never the shorthand. The body carries
+  `overscroll-behavior: contain`, so scrolling to its end does not start scrolling
+  the page behind it, and `position: relative`, so a stray absolutely positioned
+  descendant is contained rather than re-homed into an ancestor.
+
+  Those two must travel together: a positioned body _without_ a clipped shell is
+  worse than the status quo, because it pulls phantom overflow into the scroller
+  instead of out of the panel.
+
+  **`drawer.behavior.padding` is now the body's padding, not the panel's.** A
+  drawer with no header or footer looks the same as before. One that gains either
+  gets rows flush to the panel edge, which is the point.
+
+  Two new theme entries, `drawerHeader` and `drawerButtons`, mirror the dialog
+  pair knob for knob but default to a panel's posture rather than a dialog's: the
+  header's title is left-aligned rather than centered, and the footer trails its
+  actions rather than centering them.
+
+  Note one deliberate divergence from `[dialog-buttons]`: the drawer footer's
+  **confirm button does not close the drawer**. A panel's save is usually async
+  and can fail, so closing is left to the consumer via `(confirmed)`.
+
+- [`67e17ea`](https://github.com/uni-design-system/uni/commit/67e17ea927e3ca24b7abecdcccf134d53ac3656b) Thanks [@gaenglish](https://github.com/gaenglish)! - `uni-toggle` honours `size`, and the checked colour has a theme home.
+
+  **`size` did nothing.** `uni-toggle` inherits a bindable `size` input from
+  `BaseComponent`, but its geometry came from a single `toggle.behavior.size`
+  number, so `<uni-toggle size="sm">` compiled, read as deliberate, and rendered
+  identically to every other switch. The theme now carries a `sizes` block and the
+  input selects from it.
+
+  **Geometry is stated per size, not derived from ratios.** Each size token is a
+  `width` / `height` / `padding` triple — `padding` being the knob's inset — and
+  the rest falls out: knob is `height - 2 * padding`, travel is `width - height`,
+  radius is `height / 2`. Real switch designs do not hold a constant proportion
+  across sizes (a consumer's 32x18 and 28x16 pair differs in both track and knob
+  ratio), so a single ratio token could match one size or the other but never
+  both.
+
+  `lg` is `BaseComponent`'s default and reproduces the previous geometry exactly —
+  40x20, knob 16 — so **no existing toggle moves**. A theme still setting the
+  legacy `toggle.behavior.size` number keeps the old derived-ratio behaviour; that
+  option is now deprecated in favour of the `sizes` block.
+
+  **Fixed: the knob would have overhung the track at any other proportion.** The
+  checked transform was hardcoded to translate by one track height, which is only
+  correct while the track is `2x` wide and the knob `0.8x`. It is now derived, so
+  the knob lands the same distance from each edge at every size.
+
+  **New `checkedColor`, as an input and a theme option.** The on-state used to be
+  the instance's `variant`, which meant an app wanting one switch colour repeated
+  an attribute on every call site. `toggle.behavior.checkedColor` sets it once;
+  the input overrides per instance; `variant` remains the fallback when neither is
+  set. The focus ring follows the resolved colour rather than staying on `variant`.
+  An input as well as an option is necessary because `variant` defaults to
+  `'primary'` and so cannot be distinguished from unset — without one, a themed
+  `checkedColor` would have silently made `variant` inert with no way back.
+
+  **Toggle transitions are a motion token.** It hardcoded `0.3s ease` while
+  `uni-radio` already read `theme.motion(options.motion ?? 'control')`, so a theme
+  setting a motion scale moved the radio and not the switch.
+
+### Patch Changes
+
+- [`f28c951`](https://github.com/uni-design-system/uni/commit/f28c95117f2844b58a265b59c2ea8b9715156670) Thanks [@gaenglish](https://github.com/gaenglish)! - Document the drawer as an editor panel, and assert the layout that makes it one.
+
+  Both existing Drawer stories were navigation shells, so the shape that actually
+  stresses the component — a pinned header, a long scrolling form, a pinned save
+  bar — had no worked example. `EditorPanel` is that example, with a
+  `uni-number-input` and a `uni-quantity-stepper` near the bottom of the scroll,
+  where the sr-only overflow bug used to surface.
+
+  It carries a play function that asserts the scroll geometry: the panel's
+  `scrollHeight` equals its `clientHeight`, setting `scrollTop` on it does
+  nothing, the footer has no scrollable content of its own, the body scrolls to
+  its last element and stops, and no descendant has escaped its scroll container
+  to land on the panel. Those assertions live in the story rather than the unit
+  spec on purpose — jsdom has no layout engine, so every one of them would pass
+  vacuously there.
+
+  The MDX gains the three-row layout, the close-request contract, an input table,
+  and theme-option blocks for the two new component entries.
+
+- [`8f85b48`](https://github.com/uni-design-system/uni/commit/8f85b48b06f67e7f44ce29149dd32aae856e2f19) Thanks [@gaenglish](https://github.com/gaenglish)! - New **Experiments → Forms layout pressure** docs page: every form control in an
+  `auto 1fr` grid, with a bar showing what it left for its sibling.
+
+  It exists to make one class of bug visible, because nothing else can see it. A
+  `1fr` track is `minmax(auto, 1fr)`, and that `auto` floor is the control's own
+  min-content size — so a control reporting a larger intrinsic width than it needs
+  quietly steals track width from whatever sits beside it, while still looking
+  correct in isolation. That shipped once: `uni-quantity-stepper`'s value cell is a
+  native `<input>` defaulting to `size="20"`, so it measured ~230px instead of
+  ~92px and collapsed a consumer's grid column.
+
+  Neither the specs nor `build-storybook` catch it — the specs assert computed
+  styles and ARIA, and jsdom does not do layout — so it took a consumer report.
+  The page is deliberately width-constrained, since on a wide canvas nothing
+  competes for the track and the defect cannot appear. The measurements are live
+  and update as the viewport changes.
+
+- [`67e17ea`](https://github.com/uni-design-system/uni/commit/67e17ea927e3ca24b7abecdcccf134d53ac3656b) Thanks [@gaenglish](https://github.com/gaenglish)! - Signal Forms docs said `[field]`; the directive is `[formField]`.
+
+  `[field]` was the selector in the Angular 21.0 Signal Forms preview and was
+  renamed before release. In 21.2 the directive is `FormField`, selector
+  `[formField]`, with its required input aliased to `formField` — `[field]` does
+  not exist at all. Every form control in this library was documented with the
+  name that had been removed, across seven component doc comments and five MDX
+  files, and all of it flowed into the MCP index and the generated API reference.
+  A consuming app found this, not us.
+
+  Nothing about the components changed: they already satisfy `FormValueControl` /
+  `FormCheckboxControl` and always bound correctly.
+
+  **The reason it rotted is that nothing compiled a binding.** No spec or story in
+  the library imported `@angular/forms/signals` — the toggle's "Form Signals" story
+  hand-bound `[checked]` and `[touched]` as plain props, which demonstrates
+  nothing about Signal Forms and would keep passing through any rename. There is
+  now a spec that binds a real `form()` to `uni-toggle` through `[formField]` and
+  asserts the round trip in both directions, plus `touched` and `required`
+  propagation, so the next rename fails CI instead of the docs. The story binds a
+  real form too.
+
+- [`f28c951`](https://github.com/uni-design-system/uni/commit/f28c95117f2844b58a265b59c2ea8b9715156670) Thanks [@gaenglish](https://github.com/gaenglish)! - Visually hidden text no longer inflates a consuming app's scroll containers.
+
+  **Eighteen controls quietly added scrollable distance to whatever box happened
+  to be above them.** `visuallyHidden` was `position: absolute`, and the controls
+  that emit it — `uni-number-input`, `uni-quantity-stepper`, the toggle's hidden
+  `<input>`, and fifteen others — are `position: static`. An absolutely positioned
+  box resolves its containing block to the nearest _positioned_ ancestor, so each
+  1x1 span skipped every `overflow: auto` between it and that ancestor and landed
+  in the distant ancestor's scrollable overflow. A consumer reported a fixed side
+  panel measuring `scrollHeight: 1891` against `clientHeight: 793` — the whole
+  1098px difference came from seven invisible spans that had escaped the panel's
+  body scroller.
+
+  The helper is now `position: fixed`, whose containing block is the viewport, so
+  it joins no ancestor's scrollable overflow at all. The element stays 1x1 and
+  clipped to nothing, so screen reader behaviour is unchanged. Inside a
+  `transform`ed ancestor a fixed box re-anchors to that ancestor, which is
+  harmless here: where the box lands never mattered, only what it overflowed.
+
+  This class of bug is invisible in isolation — it needs a consumer to nest the
+  control inside a scrolling shell before it appears — so it is now covered by a
+  test that renders the emitting controls and asserts what actually reaches the
+  DOM, not just the recipe.
+
+- [`7545ff3`](https://github.com/uni-design-system/uni/commit/7545ff3e6dd85d29157963488f75f9e3681947c7) Thanks [@gaenglish](https://github.com/gaenglish)! - Stepper buttons now leave focus in their field, and `uni-quantity-stepper`
+  follows the theme's field chrome.
+
+  **Clicking `+` or `−` focused nothing.** Taking pointer capture means calling
+  `preventDefault()` on `pointerdown`, which also suppresses the browser's default
+  focus handling — and the buttons carry `tabindex="-1"`, so focus landed on
+  `<body>`. The arrow keys then did nothing, exactly when a user reaching for `+`
+  is most likely to try them. `createPressRepeat` gained a `focus` callback,
+  invoked on press and handed the pressed button; `uni-number-input` and
+  `uni-quantity-stepper` point it at their text field, the way a native spinner
+  does. Where there is no field — a read-only quantity stepper, whose buttons are
+  themselves the tab stops — focus goes to the button instead. **This affected
+  `uni-number-input` as well**, not just the stepper.
+
+  **`uni-quantity-stepper` ignored a theme's field styling.** It carried its own
+  `color` / `border` / `borderRadius` tokens, so a theme that restyles `input` —
+  Wellsourced fills its fields `#F3F2EF` — left the stepper stark white beside
+  them. Those three now default to the shared `input` chrome and are unset in the
+  base theme, so the stepper tracks whatever a theme does to its fields; they
+  remain available as per-component overrides for parting them deliberately. With
+  the focus indicator and the dividers already sourced this way, the container is
+  now consistently the field chrome unless a theme says otherwise.
+
+- [`8f85b48`](https://github.com/uni-design-system/uni/commit/8f85b48b06f67e7f44ce29149dd32aae856e2f19) Thanks [@gaenglish](https://github.com/gaenglish)! - `uni-quantity-stepper` no longer claims ~230px of width it does not need.
+
+  The value cell is a native `<input>`, which defaults to `size="20"`. Its
+  `flex: 1 1 auto` meant `flex-basis` resolved to that intrinsic ~20-character
+  width rather than to `valueWidth`, so the control measured ~230px instead of the
+  ~92px its buttons and a 3ch value actually need. Worse, that inflated width is
+  the control's `auto` size, and a `1fr` grid track is `minmax(auto, 1fr)` — so a
+  stepper stole track width from whatever sat beside it in a grid. Reported by
+  Wellsourced, who worked around it with `uni-quantity-stepper input { width: 0 }`.
+
+  The input is now sized from its content (`size` bound to the rendered value's
+  length), so the intrinsic width tells the truth. `valueWidth` stays the floor via
+  `min-width`, which is what keeps stepping 9 → 10 from reflowing the row, and the
+  cell still grows past it with the digits — measured at 92px for one to three
+  digits, 116px at `12,000`, 140px at `1,234,567`.
+
+  This is deliberately not the `width`-instead-of-`min-width` fix that was also
+  suggested: a fixed cell would have pinned the value at `valueWidth` and clipped
+  longer numbers, losing the growth the option documents.
+
+  **For consumers carrying the workaround:** it is safe to leave in place — the
+  control measures the same 92px either way — but remove it to get the growth
+  back, since `width: 0` forces `flex-basis: 0` and pins the cell at the floor.
+
+## 10.0.0
+
+### Major Changes
+
+- [`21b655d`](https://github.com/uni-design-system/uni/commit/21b655df0f93e2e2de6a22ccf38050b474d4e5ab) Thanks [@gaenglish](https://github.com/gaenglish)! - `uni-slider` is rebuilt on custom thumbs instead of `<input type="range">`,
+  gaining range mode, marks, a value readout and an exact decimal step model. This
+  is a breaking change to both the component's value shape and its theme options.
+
+  **Why it could not stay native.** One `<input type="range">` cannot carry two
+  thumbs, so range mode, thumb crossing and per-thumb ARIA bounds were all
+  unreachable; marks and a value tooltip were unstyleable through it. The
+  alternative — a second component for the range case — would have meant two
+  keyboard implementations to keep in step, which is the drift the shared step
+  model exists to prevent. What the platform was giving us (the slider ARIA
+  pattern and the keyboard map) is reimplemented explicitly and covered by 29
+  specs.
+
+  **Breaking: value shape.**
+
+  ```ts
+  // before
+  value = model<number>(0);
+  // after — the shape follows `mode`, and `null` is empty
+  value = model<number | UniNumberRange | null>(null);
+  ```
+
+  A `single` slider still reads and writes a plain number, so
+  `[(value)]="volume"` is unchanged. Code that relied on `value()` being
+  non-nullable, or that read it without narrowing, now needs to handle `null` and
+  the `{ start, end }` range.
+
+  **Breaking: theme options.** `slider.options.color` is **removed**. Fill and
+  thumb colour now come from the `variant` role pair, the rule every other
+  component follows, so `variant="warn"` recolours a slider with no theme edit. A
+  theme that set `color` should delete it and pass `variant` at the call site.
+  `trackColor` now defaults to `primary-container` rather than `surface-variant`.
+
+  New options: `thumbBorderRadius`, `minTouchTarget`, `markSize`, `markColor`,
+  `labelTypeface`, `labelColor`, `tooltipColor`, `tooltipTextColor`,
+  `tooltipShadow`, `tooltipBorderRadius`, `transitionMs`. `trackHeight`,
+  `thumbSize` and `borderRadius` are unchanged.
+
+  **New capability.**
+  - `mode="range"` — two thumbs, a `{ start, end }` value, `minGap` to fence the
+    ends apart. Thumbs may cross and swap, and the dragged one keeps focus.
+  - `marks` and `snapToMarks` — labelled stops, spoken in place of the number.
+  - `valueDisplay` — `none`, `inline`, `tooltip`, or `input`, which seats a
+    compact `uni-number-input` at the trailing edge, two-way bound to the same
+    value: drag for the ballpark, type for the exact figure. Single mode only.
+  - `origin` — anchor the fill somewhere other than `min`, for sliders spanning ±.
+  - `sliding` and `changed` outputs, replacing an implicit per-frame model write.
+    **Bind `changed` in forms**; `sliding` fires every frame of a drag.
+  - `largeStep`, defaulting to a tenth of the range, for `PageUp`/`PageDown` and
+    `Shift+Arrow`.
+  - Right-to-left support: the horizontal arrows and the track mirror; the value
+    does not.
+
+  **Also new: the `cdk/number` primitives** this is built on, shared with the
+  numeric input family still to come — exact scaled-`BigInt` decimal arithmetic
+  (`stepDecimal`, `roundDecimal`, `clampDecimal`), locale-aware
+  `parseNumber`/`formatNumber` over `Intl`, and `createPressRepeat` for
+  hold-to-repeat stepper buttons. Stepping `0.1` twenty times from `0` now lands
+  on exactly `2`, and `1.15` rounds to `1.2` where `(1.15).toFixed(1)` gives
+  `'1.1'`.
+
+### Minor Changes
+
+- [`2a79bb8`](https://github.com/uni-design-system/uni/commit/2a79bb8ebd8fd0b5cd792697972b6f48b444c80f) Thanks [@gaenglish](https://github.com/gaenglish)! - New `uni-number-input`: the field for a quantity, a price, a percentage or a
+  measurement, with locale-aware parsing, `Intl` formatting on commit,
+  prefix/suffix adornments, min/max/step fences and steppers that hold to repeat.
+
+  ```html
+  <uni-number-input label="Quantity" [(value)]="qty" [min]="1" />
+  <uni-number-input label="Unit price" currency="USD" [(value)]="price" />
+  ```
+
+  **Why not `<input type="number">`.** Per the HTML value sanitization algorithm,
+  a number input whose text is not a valid floating-point number reports
+  `value === ''`. Type `12,50` as most of Europe does, or paste `1,234.56` from a
+  spreadsheet, and the app reads an empty field with no way to tell that from a
+  blank one — a data-loss bug, and the reason this is `type="text"` with
+  `role="spinbutton"`. The platform control also cannot group thousands, cannot
+  place an affix outside the editable text, has ~10px unstyleable spinners below
+  the WCAG 2.2 target minimum, changes value on the scroll wheel while focused,
+  and steps in floats.
+
+  **What it does instead.**
+  - **Presets** — `decimal`, `integer`, `currency`, `percent` — supply decimals,
+    grouping, affix and `inputmode` together, so a money field is `label`,
+    `currency="USD"`, `[(value)]`. `numberFormat` is the escape hatch, merged over
+    the preset.
+  - **Parses what people actually type**: canonical ASCII always, locale grouping
+    (`1.234,56` in German), pasted affixes and currency symbols, accounting
+    negatives `(1,234.56)`, localized digit systems, compact `1.5k`, and — behind
+    `allowExpressions` — spreadsheet arithmetic like `12*3`, via a shunting-yard
+    parser that never calls `eval`.
+  - **Unreadable text stays in the field**, flagged with a dashed underline and a
+    `rejected` event, rather than being silently swallowed.
+  - **Exact arithmetic.** Stepping `0.1` twenty times from `0` lands on exactly
+    `2`; `1.15` rounds to `1.2` where `(1.15).toFixed(1)` gives `'1.1'`. A second
+    `valueAsString` model carries digits a `number` cannot, and a dev-mode warning
+    fires when a bound `value` cannot round-trip.
+  - **Percent never divides behind your back**: `preset="percent"` shows `15%` for
+    `15`. Models that really are fractions set `valueIsFraction`.
+  - Clamping on commit rather than per keystroke, visible fences that disable the
+    matching stepper and announce, `wrap` for cyclic fields, `emptyStepValue`,
+    four stepper layouts, and hold-to-repeat that announces once on release.
+
+  `uni-slider` gains `valueDisplay="input"`, which seats one of these as its
+  readout — drag for the ballpark, type for the exact value.
+
+  Adds `numberInput` to `ComponentName` with a theme entry. Field chrome is not
+  duplicated there: colour, border, radius and focus come from the shared `input`
+  options via `uni-input-box`, so a number field restyles with every other field.
+
+  `uni-input-box` gains a `managedInset` input. The themed leading inset normally
+  rides the inner `<input>`, which is right while the text is the field's leading
+  edge and wrong the moment an adornment sits in front — a currency prefix would
+  hug the border while the number it belongs to sat indented past it. A field with
+  adornments sets `managedInset` and places the inset on whichever element is
+  actually first. Existing fields are unaffected: the default is `false`.
+
+- [`e7875ee`](https://github.com/uni-design-system/uni/commit/e7875ee81030a703f4ca1904bb94cb8ddc7f57b9) Thanks [@gaenglish](https://github.com/gaenglish)! - New `uni-number-range-input`: two linked numeric fields in one chrome with a
+  single `{ start, end }` value — price filters, thresholds, tolerances. This
+  completes the numeric family alongside `uni-number-input`,
+  `uni-quantity-stepper` and the rebuilt `uni-slider`.
+
+  ```html
+  <uni-number-range-input label="Price range" currency="USD" [(value)]="price" [minGap]="50" />
+  ```
+
+  `start`/`end` deliberately match `UniDateRange`, so the library has one range
+  vocabulary, and they never collide with the `min`/`max` **inputs**, which mean
+  the fence rather than the value.
+
+  **The rules that make it one field rather than two glued together:**
+  - **Either end alone is a valid value.** `{ start: 50 }` means "50 and up",
+    which is a real filter. This is where it diverges from `uni-date-time-input`,
+    whose two parts are two halves of one answer.
+  - **Stepping is fenced; typing swaps.** A stepper can never walk one end through
+    the other — its wall is the other end, held off by `minGap`, and each end's
+    `aria-valuemin`/`aria-valuemax` report that wall rather than the outer bounds.
+    A _typed_ backwards commit is swapped and announced instead, the rule
+    `uni-calendar` applies to a backwards date range: clamping against the other
+    end would destroy the number just entered.
+  - **`minGap` pushes the end you edited**, not the other one, which is what makes
+    stepping behave as a fence rather than dragging the range along.
+  - A refused draft flags only the end it was typed into; the other stays valid.
+  - `preset`, `currency`, `prefix`, `suffix`, `decimals`, `grouping`, `locale` and
+    `roundingMode` are forwarded to both ends so the halves always read alike.
+
+  It owns its commit path rather than nesting two `uni-number-input`s, because the
+  two behaviours above need _different_ bounds — a stepper must be fenced at the
+  other end while a typed commit must arrive un-clamped — and a child field
+  applies one bound pair to both. The arithmetic, parsing and formatting are still
+  the shared `cdk/number` primitives.
+
+  Adds `numberRangeInput` to `ComponentName` with a theme entry (`partGap`,
+  `dividerText`, `dividerColor`). Field chrome is not duplicated there: colour,
+  border, radius and focus come from the shared `input` options via
+  `uni-input-box`. `dividerText` is literal punctuation rather than an icon token —
+  an en dash between two numbers is not a glyph a theme swaps artwork for.
+
+- [`589cecb`](https://github.com/uni-design-system/uni/commit/589cecb178d9119eea3fbc3f3cd9149eefdaa036) Thanks [@gaenglish](https://github.com/gaenglish)! - New `uni-quantity-stepper`: `− 3 +` for cart lines, table cells and seat counts
+  — the numeric core with no field chrome, no label and no room for either.
+
+  ```html
+  <uni-quantity-stepper label="Quantity, Blue T-shirt (M)" [(value)]="qty" [min]="1" />
+  ```
+
+  A separate component rather than a `chrome="bare"` flag on `uni-number-input`,
+  because this control is defined by what it does _not_ have — presets, affixes,
+  expressions, four stepper layouts — and eight inputs are easier to write
+  correctly than forty plus a list of which ones to leave alone. The arithmetic,
+  parsing and hold-to-repeat come from the same `cdk/number` primitives, so
+  `1,200` and the keyboard map behave identically in both.
+  - **`deleteAtMin`** is the cart pattern in one attribute: at the floor the
+    decrement becomes a remove affordance, renamed `Remove {label}`, and emits
+    `removed` rather than stepping to zero. Without it every shop reimplements the
+    same `value === 1 ? remove() : step(-1)` branch outside the component. (The
+    spec called this output `emptied`; that is a native `HTMLMediaElement` event
+    name, which `@angular-eslint/no-output-native` rightly rejects, and `removed`
+    is already what `uni-tag` calls the same request.)
+  - The middle is a real input by default — typing `12` beats tapping `+` eleven
+    times, and it takes the same grouped and locale-aware entry the field does.
+    `editable=false` renders the number as text for read-mostly tables, and the
+    buttons become the tab stops since there is nothing else to focus.
+  - `size` is `sm` / `md` / `lg` at 24 / 32 / 40px _outer_ height, so an `md`
+    stepper lines up with a 32px field beside it, with the buttons square at that
+    height. `md` and `lg` clear the 24×24 pointer target of WCAG 2.2 SC 2.5.8;
+    `sm` leaves 22px inside its border and is the dense desktop option.
+
+  Adds `quantityStepper` to `ComponentName` with a theme entry. Unlike the other
+  numeric controls it does **not** inherit the shared `input` chrome — it is not a
+  field — so it carries its own container tokens, defaulted to the same values
+  `input` uses so a cart stepper and a form field look related out of the box.
+  Height comes from the entry's `sizes` block rather than an option.
+
+### Patch Changes
+
+- [`ce94c8a`](https://github.com/uni-design-system/uni/commit/ce94c8a6acb5c70351fecfaca3469c46727c2aa4) Thanks [@gaenglish](https://github.com/gaenglish)! - `uni-angular`'s build now runs `tsc --noEmit` first, closing the last gap left
+  by the earlier "typecheck the builds" change — core and react already did this,
+  angular did not.
+
+  `ng-packagr` alone does not surface every type error in the package. A real one
+  reached a Storybook build unnoticed: a form control declaring
+  `min = input(0)` where `FormValueControl` types the property as
+  `InputSignal<number | undefined>` (Signal Forms syncs it from `min()`
+  validators), which is a variance error `pnpm build` reported as success. Every
+  form control must declare `min`/`max` as `input<number | undefined>(…)` and read
+  a `resolvedMin()` computed internally.
+
+  Also here:
+  - A `type-check` script, matching core and react, so `turbo type-check` covers
+    the whole workspace.
+  - `prototypes/**` is excluded from the package tsconfig. Those are standalone
+    design explorations that reference modules and dependencies which do not
+    exist in this package — excluding them is what makes a real typecheck
+    possible over the code that ships.
+  - Three latent type errors fixed: `vitest.config.ts` took `defineConfig` from
+    `vite`, whose overload does not accept the `test` block (it comes from
+    `vitest/config`); `spacing.spec.ts` lost callback inference through an
+    untyped `vi.spyOn` return; and `radio.motion.spec.ts` typed a `motion`
+    argument as `Record<string, unknown>` rather than `Motions`.
+
+- [`5cf120b`](https://github.com/uni-design-system/uni/commit/5cf120b9cb268e74a2ed062d8df2cf5cf9749750) Thanks [@gaenglish](https://github.com/gaenglish)! - Lint MDX prose for stray `{`, which MDX compiles to a JSX expression.
+
+  Writing `named "Increase {label}"` in a docs bullet makes `label` a reference to
+  an undefined variable, and the page dies at runtime with
+  `ReferenceError: label is not defined` under Storybook's "The component failed to
+  render properly" banner. Nothing caught it: it is a React render error rather
+  than a compile error, so **`build-storybook` passes**, and `check-doc-links.mjs`
+  only validates link ids. Only opening the page found it — twice.
+
+  `scripts/check-mdx-braces.mjs` now runs as part of the package's `lint` script,
+  so `turbo run lint` (and therefore CI) fails on it. It skips the four places a
+  brace is legitimate — fenced code blocks, inline code spans including ones that
+  soft-wrap across a line, ESM `import`/`export` statements, and JSX tags such as
+  `of={Stories.X}` or `rows={[…]}` — plus MDX comment containers. Hits are
+  reported as `file:line:column` with the offending line and the fix: backtick the
+  text, or escape the brace as `\{`.
+
+  Also available on its own as `pnpm lint:mdx`.
+
+- [`05f991f`](https://github.com/uni-design-system/uni/commit/05f991f0cc6b0895777763ede7605b5e274dc0a1) Thanks [@gaenglish](https://github.com/gaenglish)! - Three cosmetic fixes in the numeric family.
+
+  **`uni-quantity-stepper`'s dividers were heavier than its frame.** The rules
+  either side of the value took `dividerColor: 'outline'` — a solid grey — against
+  an outer border of the 8%-alpha `light` token, so the control read as three
+  pieces stuck together rather than one frame. They now take the **same `border`
+  token as the container** and move with it on focus, so a focused stepper is not
+  accented on the outside and grey down the middle. `dividerColor` remains as an
+  opt-in override for a deliberately distinct rule, and is unset in the base theme.
+
+  **`uni-quantity-stepper` had no focus state.** Every other field gets its focus
+  chrome from `uni-input-box`, which the stepper deliberately does not use — and
+  its inner input clears its own outline via `removeInputPlatformStyling`, so
+  focusing the middle showed nothing at all. The container now carries the same
+  `:has(input:focus)` rule and the same `input` theme tokens the box applies
+  (`focusOutline`, `focusOutlineOffset`, and the optional `focusBorder` /
+  `focusShadow` / `focusColor`), so a stepper highlights exactly like the field
+  beside it — including in themes such as Wellsourced that express focus as a
+  border and ring rather than an outline. Error state still wins, keeping a
+  flagged control visibly flagged while it is corrected.
+
+  **A trailing suffix sat against the right border.** The leading inset was
+  already handled, so the two sides did not match. `uni-number-range-input` — which
+  has no steppers — now insets both edges of its row, and `uni-number-input` insets
+  the trailing edge whenever no stepper occupies it (`stepperLayout="none"`, or a
+  read-only field). Where a stepper _is_ present the trailing edge is still left
+  to it, because a button is meant to reach the border.
+
+  Both insets ride the row rather than the `<input>`: `uni-input-box` styles
+  `& input` at a higher specificity than a component class can reach, so padding
+  set on the input itself is silently dropped.
+
+- [`1fe8941`](https://github.com/uni-design-system/uni/commit/1fe89415c65d38c97d610fb5725e8a050432192f) Thanks [@gaenglish](https://github.com/gaenglish)! - `uni-tag-input`'s first chip no longer rides the left border.
+
+  The themed leading inset was applied by `uni-input-box` to the inner `<input>`,
+  which is the field's leading edge only while it is empty. Once a chip existed,
+  the chip sat flush against the border while the text after it stayed indented.
+  The chip row now owns the inset — it is the leading content — via the
+  `managedInset` input added alongside `uni-number-input`, so the first chip and
+  an empty field's placeholder both start at the same 8px as every other field's
+  text. Wrapped chip rows are unaffected; vertical padding already handled those.
+
+- Updated dependencies [[`2a79bb8`](https://github.com/uni-design-system/uni/commit/2a79bb8ebd8fd0b5cd792697972b6f48b444c80f), [`e7875ee`](https://github.com/uni-design-system/uni/commit/e7875ee81030a703f4ca1904bb94cb8ddc7f57b9), [`589cecb`](https://github.com/uni-design-system/uni/commit/589cecb178d9119eea3fbc3f3cd9149eefdaa036), [`21b655d`](https://github.com/uni-design-system/uni/commit/21b655df0f93e2e2de6a22ccf38050b474d4e5ab)]:
+  - @uni-design-system/uni-core@10.0.0
+
 ## 9.0.1
 
 ## 9.0.0