@ids-group-ltd/ids-design-system 0.11.0 → 0.11.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (50) hide show
  1. package/CHANGELOG.md +1368 -1021
  2. package/components.md +49 -26
  3. package/design-system.md +18 -18
  4. package/fesm2022/ids-group-ltd-ids-design-system.mjs +1750 -598
  5. package/fesm2022/ids-group-ltd-ids-design-system.mjs.map +1 -1
  6. package/migrations/0.10.0.json +19 -19
  7. package/migrations/0.10.1.json +20 -7
  8. package/migrations/0.10.2.json +8 -8
  9. package/migrations/0.10.3.json +2 -2
  10. package/migrations/0.11.0.json +9 -54
  11. package/migrations/0.11.1.json +279 -0
  12. package/migrations/0.11.2.json +158 -0
  13. package/migrations/0.2.0.json +17 -5
  14. package/migrations/0.2.2.json +1 -1
  15. package/migrations/0.3.0.json +1 -1
  16. package/migrations/0.4.0.json +1 -1
  17. package/migrations/0.5.1/badge-statuses.md +1 -3
  18. package/migrations/0.5.1.json +1 -1
  19. package/migrations/0.6.3.json +1 -1
  20. package/migrations/0.7.1.json +6 -6
  21. package/migrations/0.8.0.json +5 -5
  22. package/migrations/0.9.0.json +12 -11
  23. package/migrations/0.9.1.json +2 -2
  24. package/migrations/README.md +34 -52
  25. package/package.json +1 -1
  26. package/styles/_dropdown-overlay.scss +64 -23
  27. package/styles/_ds-color.scss +3 -3
  28. package/styles/_field-box.scss +2 -6
  29. package/styles/_field-label.scss +5 -10
  30. package/styles/_field-state.scss +3 -2
  31. package/styles/_focus.scss +0 -2
  32. package/styles/_layout-utils.scss +2 -2
  33. package/styles/_overlay-motion.scss +2 -3
  34. package/styles/_press.scss +3 -5
  35. package/styles/_reset.scss +0 -1
  36. package/styles/_scrollbar.scss +1 -3
  37. package/styles/_status.scss +1 -2
  38. package/styles/_surface-motion.scss +3 -4
  39. package/styles/_text-clip.scss +1 -1
  40. package/styles/_theme-activation.scss +1 -1
  41. package/styles/_tokens-charts.scss +1 -3
  42. package/styles/_tokens.scss +5 -4
  43. package/styles/_typography.scss +2 -2
  44. package/themes/README.md +6 -6
  45. package/themes/_base-palette.scss +2 -2
  46. package/themes/_semantic.scss +2 -2
  47. package/themes/dark/_palette.scss +1 -2
  48. package/themes/light/_palette.scss +1 -1
  49. package/themes/light/_theme.scss +1 -1
  50. package/types/ids-group-ltd-ids-design-system.d.ts +608 -72
@@ -34,10 +34,10 @@
34
34
  "kind": "behavior",
35
35
  "old": "extends AutocompleteComponent",
36
36
  "new": null,
37
- "action": "Run `npm run class-surface v0.9.1 v0.10.0` for the authoritative list, then per member: rename your own, or add `override` where the base semantics genuinely match. For the lost ones, drop the override and use the public API — `runExport()`, `exporting()`, `exportStatus()`, `status`.",
37
+ "action": "Build after upgrading — the compiler enumerates every collision, including the three shapes in `pitfall` below that a member-by-member diff does not show. Then per member: rename your own, or add `override` where the base semantics genuinely match. For the lost ones, drop the override and use the public API — `runExport()`, `exporting()`, `exportStatus()`, `status`.",
38
38
  "appliesWhen": "Only a consumer that EXTENDS a DS component class. Subclassing is unsupported (design-system.md § Components); template users need nothing.",
39
- "pitfall": "Three shapes the report cannot show you. (1) `TableComponent.exporting` and `.exportStatus` keep their NAMES but are public readonly signals now instead of the protected writable ones a subclass could set — assigning to them stops compiling and nothing in the diff says so. (2) SearchComponent also declares the plain private fields `pending` and `pushed`; class-surface matches `readonly` fields and methods, and a redeclared private still fails with TS2415. (3) Four classes LOST members — ModalComponent `error` and `onBackdrop`, ModalCardComponent `error`, BottomSheetComponent `stop`, InputComponent `floating` — so an `override` there now overrides nothing.",
40
- "note": "Thirty classes gained members. The `controlState` additions on the nine bordered fields were invisible to class-surface until its field pattern was widened in this same release: it matched only `readonly x = call(…)`, and `controlState` is assigned from a property.",
39
+ "pitfall": "Three shapes a member-by-member diff will not show you. (1) `TableComponent.exporting` and `.exportStatus` keep their NAMES but are public readonly signals now instead of the protected writable ones a subclass could set — assigning to them stops compiling and nothing in the diff says so. (2) SearchComponent also declares the plain private fields `pending` and `pushed`; a member diff matches `readonly` fields and methods, and a redeclared private still fails with TS2415. (3) Four classes LOST members — ModalComponent `error` and `onBackdrop`, ModalCardComponent `error`, BottomSheetComponent `stop`, InputComponent `floating` — so an `override` there now overrides nothing.",
40
+ "note": "Thirty classes gained members, including `controlState` on the nine bordered fields; this release's CHANGELOG block lists them by class.",
41
41
  "searchHints": [
42
42
  "extends ButtonComponent",
43
43
  "extends TableComponent",
@@ -92,7 +92,7 @@
92
92
  "action": "Either accept the new parameter values, or declare `value` on each `ds-tab` to pin the names permanently — the better fix regardless, since a slug is still derived from display copy and renaming a tab still moves the link.",
93
93
  "appliesWhen": "Only consumers who adopted `urlParam` in 0.9.0 AND left `value` off their tabs. A label with nothing sluggable in it — CJK, bare punctuation — keeps its raw text.",
94
94
  "pitfall": "Existing links stop matching and land on the first tab, and nothing throws: it is indistinguishable from a stale bookmark. Note too that `tabClosed` still emits the RAW label — the two identifiers are deliberately different now, and the docs said they were the same until this release.",
95
- "note": "`?tab=License%20Verification%20Status` becomes `?tab=license-verification-status`: kebab, lowercased, diacritics decomposed and dropped.",
95
+ "note": "`?tab=Recent%20Activity` becomes `?tab=recent-activity`: kebab, lowercased, diacritics decomposed and dropped.",
96
96
  "searchHints": [
97
97
  "urlParam",
98
98
  "ds-tabs",
@@ -299,7 +299,7 @@
299
299
  "new": null,
300
300
  "action": "Nothing for most, and a wide trigger still shows exactly N. You are affected only if you relied on a numeric cap to guarantee a fixed chip COUNT regardless of width.",
301
301
  "appliesWhen": "ds-autocomplete and ds-multi-select alike. `null` remains the only mode that never measures.",
302
- "pitfall": "The stale wording is still in the wild and it contradicts this item: the input's own JSDoc in both components, and the generated docs API table built from it, still say \"A NUMBER caps at exactly that many\". The manifest and the CHANGELOG are correct; those are not.",
302
+ "pitfall": "The stale wording is still in the wild and it contradicts this item: the input's own JSDoc in both components, and the generated docs API table built from it, still say \"A NUMBER caps at exactly that many\". That wording is stale; this item describes the behaviour.",
303
303
  "note": "A number is a CEILING that is then measured. `[maxVisibleChips]=\"2\"` means at most two, and fewer when the trigger is too narrow to hold them beside the \"+N more\" marker. Exactly-N is what made a capped trigger on a phone run out of room and wrap the text input onto a second line — the growth the cap exists to prevent. The single-line height is guaranteed instead.",
304
304
  "searchHints": [
305
305
  "maxVisibleChips",
@@ -396,7 +396,7 @@
396
396
  "old": "ds-input[error]",
397
397
  "new": null,
398
398
  "action": "Nothing if you bound `[invalid]` alongside it. If you bound `error` ALONE and relied on the box staying neutral, move that text to `warning` for an advisory message, or to `hint`, and leave `error` empty.",
399
- "appliesWhen": "The fourteen field components that route through resolveFieldMessage — border and fill on the nine bordered ones, aria-invalid and the message state on the other five.",
399
+ "appliesWhen": "All fourteen field components — border and fill on the nine bordered ones, aria-invalid and the message state on the other five.",
400
400
  "pitfall": "The precedence ladder is error → warning → success now, so a ds-input carrying both `[success]=\"true\"` and a warning string paints the WARNING, where it used to paint success and ignore the warning.",
401
401
  "note": "An `error` string marks the field invalid on its own. It used to colour only the message and leave the control neutral; it drives the error border, the tinted fill, the error focus ring and aria-invalid now.",
402
402
  "searchHints": [
@@ -422,7 +422,7 @@
422
422
  "new": null,
423
423
  "action": "Only if you deliberately relied on an element having NO focus indicator: give it `box-shadow: none` explicitly. The rule also sets `outline: none`, so an element relying on the BROWSER outline loses it — declare your own if that is what you wanted.",
424
424
  "appliesWhen": "Written with `:where()`, so every component rule and every app rule still out-ranks it, and the `data-focus` switch is unaffected.",
425
- "pitfall": "The case that actually bites: an app rule that styles `:focus-visible` with an OUTLINE ONLY. It keeps winning on outline, but it says nothing about box-shadow, so the base rule still supplies one and the element renders BOTH — a second ring in your colour around the DS ring. The app rule looks untouched because it is, so neither the build nor a grep for the change finds it; one consumer hit it fourteen times. FIND IT by grepping your styles for `:focus-visible` and reading each rule: one that sets outline (or outline-color / outline-offset) and no box-shadow is a hit. Add `box-shadow: none`, or better, delete the rule and retint the DS ring through `--ds-control-focus-shadow`.",
425
+ "pitfall": "The case that actually bites: an app rule that styles `:focus-visible` with an OUTLINE ONLY. It keeps winning on outline, but it says nothing about box-shadow, so the base rule still supplies one and the element renders BOTH — a second ring in your colour around the DS ring. The app rule looks untouched because it is, so neither the build nor a grep for the change finds it. FIND IT by grepping your styles for `:focus-visible` and reading each rule: one that sets outline (or outline-color / outline-offset) and no box-shadow is a hit. Add `box-shadow: none`, or better, delete the rule and retint the DS ring through `--ds-control-focus-shadow`.",
426
426
  "note": "One zero-specificity base rule — `:where(:focus-visible) { outline: none; box-shadow: var(--ds-control-focus-shadow) }` — gives the DS ring to any focusable element that does not style focus itself, including your own bare `<button>`, a link in projected content, and the close buttons inside ds-alert, ds-banner and ds-drawer. They fell through to the browser default before.",
427
427
  "searchHints": [
428
428
  ":focus-visible",
@@ -571,7 +571,7 @@
571
571
  "action": "Retype the declaration to the widened union, or drop the explicit annotation and let inference carry it. A subclass override is the unsupported case — rename the member or retype it to match.",
572
572
  "appliesWhen": "Templates and plain bindings are unaffected. This entry is the TYPE-LEVEL counterpart of `control-size-input-becomes-nullable` and `nullable-boolean-inputs-treat-null-as-unset`, which carry the value semantics.",
573
573
  "pitfall": "These declarations stop compiling even where the VALUES are compatible, because the type-parameter position of InputSignal / InputSignalWithTransform is invariant: TS2416 on a subclass override, TS2322 on an assignment to an explicitly typed variable, viewChild target or helper parameter.",
574
- "note": "Widened here, per `npm run class-surface v0.9.1 v0.10.0`: `size` to `DsSize | null` on fourteen controls; ds-icon `size` to `number | null`; ds-table `bordered` and `stickyScrollbar`, ds-badge `withDot` and `dividers` on both modals to `boolean | null`; ds-table `loading` to `boolean | 'skeleton' | 'overlay'`; ds-card `elevation` to `CardElevation | null`; ds-modal-card `dialogRole` nullable; `brand` / `logoLetter` / `tagline` on ds-auth-layout and ds-sidenav to `string | null`; `maxVisibleChips` to `number | 'fit' | null`.",
574
+ "note": "Widened here: `size` to `DsSize | null` on fourteen controls; ds-icon `size` to `number | null`; ds-table `bordered` and `stickyScrollbar`, ds-badge `withDot` and `dividers` on both modals to `boolean | null`; ds-table `loading` to `boolean | 'skeleton' | 'overlay'`; ds-card `elevation` to `CardElevation | null`; ds-modal-card `dialogRole` nullable; `brand` / `logoLetter` / `tagline` on ds-auth-layout and ds-sidenav to `string | null`; `maxVisibleChips` to `number | 'fit' | null`.",
575
575
  "searchHints": [
576
576
  "InputSignal",
577
577
  "InputSignalWithTransform",
@@ -613,7 +613,7 @@
613
613
  "The measurement behind maxVisibleChips=\"fit\" reads the TRIGGER's width, never the chip row's own - a row cannot measure a box whose size the cut changes. Widths are cached per selection and a geometry guard skips re-measuring when neither width nor count moved, so a page of pickers measures once, not once per chip. [maxVisibleChips]=\"null\" opts out of measuring entirely.",
614
614
  "ds-sidenav's brand row fixes, none of which need action: an astral first character (emoji, rarer CJK) no longer paints as tofu in the letter-mark; the mark is aria-hidden, so a screen reader reads the wordmark once instead of announcing the glyph then the name; and a logoLetter set WITHOUT a brand string now renders its tile at all, where an outer gate used to drop the whole lockup.",
615
615
  "env(safe-area-inset-*) reads 0 unless YOUR index.html sets viewport-fit=cover in its viewport meta — a notched device alone is not enough, and this library cannot set it for you. ds-auth-layout pads by all four insets and ds-bottom-sheet by the bottom one, so both are plain-padded until you opt in; the docs site now sets it and both component pages state it. ds-bottom-sheet's env() also gained the `, 0px` fallback its siblings had: an unknown env() variable invalidates the entire declaration, which would have taken that sheet's horizontal padding with it.",
616
- "The ds-select and ds-autocomplete panels now resolve --ds-dropdown-panel-radius, defaulting to the --ds-radius-panel role so nothing moves until you set it. TWO panels, not three: ds-multi-select's panel hardcodes border-radius: var(--radius-md) on its own .panel element, which is not the .dropdown-panel the shared rule targets, so neither this token nor --ds-radius-panel reaches it - it stays at 8px whatever you set, and that is a gap rather than a decision. This is the lever 0.9.0 notes promised as --ds-select-panel-radius, which never existed - that note is corrected in migrations/0.9.0.json. Deliberately panel-level rather than per-component: retuning ONE picker is not a thing the library encourages, and --ds-radius-panel moves modal, popover and date-picker with it. Scope it with a selector - ds-select { --ds-dropdown-panel-radius: 8px } - and only that panel moves, since the token is forwarded onto the portaled pane.",
616
+ "The ds-select and ds-autocomplete panels now resolve --ds-dropdown-panel-radius, defaulting to the --ds-radius-panel role so nothing moves until you set it. TWO panels, not three: ds-multi-select's panel hardcodes border-radius: var(--radius-md) on its own .panel element, which is not the .dropdown-panel the shared rule targets, so neither this token nor --ds-radius-panel reaches it - it stays at 8px whatever you set, and that is a gap rather than a decision. Deliberately panel-level rather than per-component: retuning ONE picker is not a thing the library encourages, and --ds-radius-panel moves modal, popover and date-picker with it. Scope it with a selector - ds-select { --ds-dropdown-panel-radius: 8px } - and only that panel moves, since the token is forwarded onto the portaled pane.",
617
617
  "A single-select ds-autocomplete no longer keeps the text typed to filter. Since 0.9.0 that text was also INVISIBLE - the filter input collapses to zero width once a chosen label is on show - while it still narrowed the list, so reopening a settled picker offered one option of four with nothing on screen to explain it. Cleared now whenever the panel closes over a displayed label, which covers both picking and dismissing after typing over a settled value. Multi-select is unchanged on purpose: its input never collapses, so the text stays visible and useful for the next pick. No action - query was component-private and could not be reset from an app.",
618
618
  "The global .link class now resets a <button>: appearance, padding, border, background, font-family, font-size, line-height and text-align. It was written for anchors and touched none of them, yet ds-button warns variant=\"text\" off in favour of .link and an action that is not navigation has to be a button - so a button.link rendered at 13.3px inside 14px text with 1px 6px of padding and an outset border. font-weight is untouched so .quiet/.standalone still decide it, and display stays inline-block. Scoped with :where(), so the reset sits at .link specificity and a consumer rule still wins on source order.",
619
619
  "ds-stat gained --ds-stat-value-white-space and --ds-stat-value-font-size, both defaulting to what the tile already rendered (nowrap, and h2/h4/h1 by size), so no existing tile moves. They exist because a value that is a PHRASE - a date range, a status - spilled straight past the tile edge under the nowrap that suits a number - the card sets no overflow, so it is not clipped, it escapes. The size hook now applies at every size input: the sm and lg variants move this token instead of restating font-size on .value, where they out-ranked any override and made such a hook work at md only.",
@@ -629,26 +629,26 @@
629
629
  "ds-multi-select and ds-autocomplete render an option's `icon` before its label at 16px, which previously only ds-select did. The three option types now extend one exported DsOption<T> - they were three near-identical interfaces, which is why the icon field existed on one picker for a release - and each keeps its own exported name, so no import changes. Nothing to do: options without an icon render as before. Only ds-select repeats the icon in its TRIGGER, because its trigger is a button showing one label; the autocomplete trigger is a text input whose leading slot belongs to [dsAutocompletePrefix], and multi-select chips stay text-only so the label keeps the width.",
630
630
  "provideDsConfig gained five sections, so an app can state a whole-app opinion once instead of on every element: control.size (button, icon-button, input, textarea, select, autocomplete, search, date/time picker, number stepper, checkbox, radio, switch, field-group), card.elevation, card.padding, table.stickyScrollbar, table.bordered, icon.size and badge.withDot. Precedence is input -> config -> built-in, and NO built-in default moved: an app that provides nothing renders exactly as it did.",
631
631
  "DS_CONFIG.control.size is NOT the same axis as [data-density]. The density tier rewrites hit targets and padding in CSS for a route subtree; control.size picks which of the three declared sizes (sm/md/lg) a control renders at. An app can set both, and they compose.",
632
- "MEASURED IN A CONSUMER, worth checking on your own side: 46 of its ds-icon elements bind [size]=\"16\", which is already the ds-icon default - dead bindings, not a gap. Config or no config, those can go.",
632
+ "Worth checking on your own side: a [size]=\"16\" binding on ds-icon restates the default, so it is a dead binding rather than a gap.",
633
633
  "ds-modal and ds-bottom-sheet no longer dismiss when the mouse is RELEASED on the backdrop after a press that started inside the dialog (selecting text and letting go past the edge, or overshooting a slider). Their backdrop wraps the dialog, so the browser fires click at the nearest common ancestor - the backdrop itself - which the target===currentTarget guard could not tell apart. Dismissal now requires the press AND the release to land on the backdrop. Nothing to do on adoption. ONE EXCEPTION: a test that dismisses a dialog with backdropElement.click() must now dispatch pointerdown + pointerup on the backdrop; a real mouse or touch always sends both. ds-drawer and the ModalService confirm were never affected - their scrim is a sibling of the panel - and are unchanged.",
634
634
  "ds-table gained one projection slot, [toolbar], for controls that act on THAT table (a search box, a status filter, a refresh) — the row the export button already lived in, which until now existed only while exportButton was on. Project several controls and the row lays them out (flex, wrap, 8px gap); project a single element of your own and it takes the full row width, so your own layout is the only one in play. Visually additive: the row COLLAPSES when nothing filled it and exportButton is off, so a table that uses neither is pixel-identical. It is not DOM-identical - <div class=\"table-toolbar\"><div class=\"toolbar-slot\"> is now rendered unconditionally and hidden with display:none, so a ds-table > :first-child selector or a DOM snapshot sees it. Page-level filters still belong in a ds-filter-bar above the table.",
635
635
  "ds-table now exposes runExport(), exporting() and exportStatus() publicly, so an Export button placed anywhere (page header, filter bar, the new toolbar slot) runs the same path as the built-in one: the exportFetcher call, the download, the in-flight state and the live-region announcement.",
636
- "ds-table no longer renders its empty row while loading is anything but false. Previously only loading=\"skeleton\" suppressed it, so an overlay reload with zero rows painted the empty state under the spinner. Nothing to do on adoption, and you can delete the @if(!loading) guard around your own empty template — worth checking whether you have one at all: of one consumer 14 overlay-loading tables, 9 shipped \"no rows\" copy during a load. (delete list: table-empty-template-loading-guard)",
636
+ "ds-table no longer renders its empty row while loading is anything but false. Previously only loading=\"skeleton\" suppressed it, so an overlay reload with zero rows painted the empty state under the spinner. Nothing to do on adoption, and you can delete the @if(!loading) guard around your own empty template — worth checking whether you have one at all. (delete list: table-empty-template-loading-guard)",
637
637
  "ds-table no longer loses its sort indicator when a host answers a cleared sort with its own default. Angular writes an input only when the bound expression changed (it diffs against the last value it wrote, which an internal .set() never updates), so whichever half of the host default equalled the last bound value was skipped: a host defaulting to desc had its desc dropped and the header marked nothing over sorted rows, while a host defaulting to asc was restored — the reason the same three clicks worked on one screen and not another. The marked state is now a linkedSignal over BOTH inputs. Nothing to do on adoption; you can delete any workaround that re-bound the sort after a clear. (delete list: table-sort-rebind-after-clear)",
638
638
  "ds-table accepts [loading]=\"true\" and resolves the treatment itself: skeleton rows while filteredData is empty, overlay once rows are on screen. The existing values are untouched — false, 'skeleton' and 'overlay' behave exactly as before, so nothing changes on adoption.",
639
639
  "Disabled rows and triggers are no longer dimmed twice. ds-select, ds-date-picker, ds-time-picker, ds-menu-item and the shared dropdown row each applied --text-disabled AND opacity 0.6 on top of it, which measured 1.68:1 against the surface where the colour alone gives 2.53:1 (an enabled control is 17.32:1). The opacity is gone from those five and the colour carries the state. A disabled calendar day and ds-toggle-button, where opacity is the ONLY signal, moved from --opacity-muted (0.6) to --opacity-disabled (0.5).",
640
640
  "ds-button and ds-icon-button use ONE disabled-label recipe for every variant now: oklch(from accent 70% 0.035 h), replacing the 58% base plus the 52% overrides that tonal and outline carried. Reason, measured across the full variant x colour x state matrix: the old lightness sat where a saturated accent already is, so on primary and error the disabled label differed from the live one by 1.16-1.60:1 on four of the five variants (neutral was fine because its enabled label is nearly black). It is now 2.40-2.71:1 on the coloured variants, and up to 6.46:1 on neutral. The disabled label is FAINTER against its own background than before (2.1-2.7:1 where it was 3.4-5.2) - that is the intended trade, and disabled text is exempt from the WCAG contrast floor. Nothing to do on adoption; --ds-button-label-color-disabled and --ds-icon-button-icon-color-disabled still override per component.",
641
- "components.md — the API digest copied into dist/ds for a consumer's agents — was two renames behind: 46 of the 92 --ds-* tokens it named no longer existed (the bg->bg-color and fg->text/label/icon-color renames, plus --ds-pagehdr-* -> --ds-page-header-*), ds-button was documented with its pre-2026-06 single `variant` axis rather than color x variant, and the topbar section described a --ds-topbar-margin-b that has never existed in the shipped component. All names now verified against src/lib. If your agents or your notes were built from an older copy of this file, re-read it after the bump: token names you may have copied from it are dead.",
641
+ "components.md — the API digest this package carries for a consumer's agents — was two renames behind: 46 of the 92 --ds-* tokens it named no longer existed (the bg->bg-color and fg->text/label/icon-color renames, plus --ds-pagehdr-* -> --ds-page-header-*), ds-button was documented with its pre-2026-06 single `variant` axis rather than color x variant, and the topbar section described a --ds-topbar-margin-b that has never existed in the shipped component. All names now verified against the shipped components. If your agents or your notes were built from an older copy of this file, re-read it after the bump: token names you may have copied from it are dead.",
642
642
  "Focus indicators are now universal: a single base rule, :where(:focus-visible) { outline: none; box-shadow: var(--ds-control-focus-shadow) }, gives the DS ring to anything focusable that does not style focus itself — the close buttons in ds-alert / ds-banner / ds-drawer, links in projected content, and an app's own bare <button>. Before this they fell through to the browser default (a black outline: auto in Chrome). Zero specificity via :where(), so every component rule and every app rule still wins, and the data-focus switch (ring / field / edge / outline) behaves exactly as before. ACTION only if you relied on an element having NO focus indicator: set box-shadow: none on it explicitly.",
643
- "AutocompleteOption now extends the shared DsOption shape, so it gains `disabled?: boolean`, which it never had before — and ds-autocomplete acts on it: the row carries the .is-disabled class and aria-disabled, ignores the click, and the arrow keys skip it (as does the initial active row when the panel opens or the filter re-runs). Behaviourally this matches ds-select and ds-multi-select, which already honoured the flag. The row greys out as well - measured in the open panel at rgb(155,163,180) against rgb(22,26,40) for an enabled row.",
643
+ "AutocompleteOption now extends the shared DsOption shape, so it gains `disabled?: boolean`, which it never had before — and ds-autocomplete acts on it: the row carries the .is-disabled class and aria-disabled, ignores the click, and the arrow keys skip it (as does the initial active row when the panel opens or the filter re-runs). Behaviourally this matches ds-select and ds-multi-select, which already honoured the flag. The row greys out as well.",
644
644
  "TableColumn.width now accepts the literal 'content' in addition to a pixel number: the column sizes to its widest cell and stops wrapping, leaving the remaining width to the other columns. Purely additive — a numeric width and an unset width behave exactly as before.",
645
- "maxVisibleChips as a NUMBER is now a ceiling rather than an exact count on ds-autocomplete and ds-multi-select: at most N chips, and fewer when the trigger is too narrow to hold them beside the '+N more' marker and whatever follows (the text input, the chevron). Reported from a phone: [maxVisibleChips]=\"2\" showed two chips, ran out of width and wrapped the text input onto a second line — the growth the cap exists to prevent. Nothing to change on adoption; a wide trigger still shows exactly N. null is untouched and remains the only mode that does not measure. If you relied on a numeric cap to guarantee a fixed chip COUNT regardless of width, that guarantee is gone by design — the trigger's height is the thing being guaranteed instead.",
645
+ "maxVisibleChips as a NUMBER is now a ceiling rather than an exact count on ds-autocomplete and ds-multi-select: at most N chips, and fewer when the trigger is too narrow to hold them beside the '+N more' marker and whatever follows (the text input, the chevron). On a narrow trigger, [maxVisibleChips]=\"2\" showed two chips, ran out of width and wrapped the text input onto a second line — the growth the cap exists to prevent. Nothing to change on adoption; a wide trigger still shows exactly N. null is untouched and remains the only mode that does not measure. If you relied on a numeric cap to guarantee a fixed chip COUNT regardless of width, that guarantee is gone by design — the trigger's height is the thing being guaranteed instead.",
646
646
  "ds-field-group segments now centre their value vertically. Every segment except ds-button pinned its value to the top of the row: the group stretches the segment, but the host is a block, so the height: 100% each control set on its bordered box resolved against `auto` and the box kept its own content height (a 19.6px line box inside a 40px row at md). Nothing to change on adoption. ACTION only if you had a ::ng-deep override compensating for it -- e.g. ds-field-group ds-input .control { align-items: center } or a padding-top nudge -- which is now double-applied; delete it.",
647
- "An `error` string now marks the field invalid on its own, across all 14 field components that route through resolveFieldMessage (ds-input, ds-textarea, ds-select, ds-autocomplete, ds-multi-select, ds-date-picker, ds-time-picker, ds-color-picker, ds-otp-input, ds-slider, ds-checkbox, ds-radio, ds-radio-group, ds-switch). Before, error=\"...\" coloured only the message and left the control neutral; it now drives the error border, fill, focus ring and aria-invalid, which is what the input always documented. Nothing to do if you bound [invalid] alongside it. ACTION only if you bound `error` on its own and WANTED a neutral box: move that text to `warning` (advisory) or to `hint`.",
647
+ "An `error` string now marks the field invalid on its own, across all 14 field components (ds-input, ds-textarea, ds-select, ds-autocomplete, ds-multi-select, ds-date-picker, ds-time-picker, ds-color-picker, ds-otp-input, ds-slider, ds-checkbox, ds-radio, ds-radio-group, ds-switch). Before, error=\"...\" coloured only the message and left the control neutral; it now drives the error border, fill, focus ring and aria-invalid, which is what the input always documented. Nothing to do if you bound [invalid] alongside it. ACTION only if you bound `error` on its own and WANTED a neutral box: move that text to `warning` (advisory) or to `hint`.",
648
648
  "A `warning` string now paints the control, not only the message line: a --warning-text border (#8A7400, 4.59:1 on a white field) on all nine bordered fields -- ds-input, ds-textarea, ds-select, ds-autocomplete, ds-multi-select, ds-date-picker, ds-time-picker, ds-color-picker, ds-otp-input. Success keeps its border-only treatment and error keeps border + tinted fill, so the three states stay ranked. Two visual corrections ride along and need no action: an invalid ds-autocomplete drew a near-black border because it read a --border-error token that has never existed, and ds-multi-select / ds-color-picker / ds-otp-input had the error border but not the fill their siblings had. Every per-component override token (--ds-input-bg-color-error, --ds-select-focus-shadow-error, and the rest) still applies.",
649
649
  "ds-otp-input no longer leaves two characters in one cell when a second character is typed into an already-filled cell. The value the component reported was always correct -- only the rendered cell was stale -- so nothing to change on adoption. ACTION only if you worked around it by reading the cell inputs from the DOM instead of the component's value.",
650
650
  "ds-password-rules: its screen-reader-only per-row text ('- not met') was rendering VISIBLY, because the .visually-hidden class it used was defined by no stylesheet -- ds-table, ds-date-picker and ds-stepper each declared their own private copy. One shared mixin now backs all four. The leaked text is also what wrapped every label in the two-column layout. Separately, the pending glyph changed from `minus` to a new `circle` icon and the row now transitions its colour over --duration-base. Nothing to change on adoption. ACTION only if you targeted the pending row's glyph by name, or added your own .visually-hidden definition to work around the leak -- that override is now redundant (DELETE-LIST). (delete list: private-visually-hidden-definition)",
651
- "The migration manifests themselves changed: 0.9.0.json gained a class-member-collision item it never had (fifteen classes plus four newly exported symbols), 0.8.0.json now names the private saveLayout/restoreLayout that actually stopped a consumer build, and 0.6.1 / 0.6.2 / 0.9.1 were written for the first time. Every released version now ships a manifest, so the auto-update planner no longer falls back to re-deriving a plan from changelog prose on those three. 0.6.2 turned out to carry something actionable nobody had in machine-readable form: a ds-bottom-sheet with nothing focusable inside it stopped closing on Escape.",
651
+ "The migration manifests themselves changed: 0.9.0.json gained a class-member-collision item it never had (fifteen classes plus four newly exported symbols), 0.8.0.json now names the private saveLayout/restoreLayout, and 0.6.1 / 0.6.2 / 0.9.1 were written for the first time. Every released version now ships a manifest, so an upgrade tool no longer falls back to re-deriving a plan from changelog prose on those three. 0.6.2 carries an actionable change that no machine-readable file had stated: a ds-bottom-sheet with nothing focusable inside it stopped closing on Escape.",
652
652
  "ds-modal gained three public title tokens for the new statuses - --ds-modal-title-text-color-warning, -success and -info, defaulting to --warning-text / --success-text / --info-text - joining the -error that already existed. Additive: nothing moves until you set one.",
653
653
  "The [empty] slot is now unreachable during ANY load, not just a skeleton one: the empty row is withheld whenever loading is not false, and the projection lives inside that branch. Copy you want a reader to see WHILE a load runs has to come from your own page, above or around the table.",
654
654
  "runExport() without an exportFetcher falls through to exportCsv() synchronously and never touches exporting/exportStatus - so an external Export button bound to [loading]=\"table.exporting()\" shows no progress in that configuration. Bind exportFetcher if you want the in-flight state.",
@@ -778,7 +778,7 @@
778
778
  ".modal > .header",
779
779
  "!important"
780
780
  ],
781
- "why": "`[dividers]=\"false\"` repeated on every modal (one consumer had 41), or a reach into `.modal > .header` / `.body` / `.actions` with `!important` because hiding the rules left the padding stacked.",
781
+ "why": "`[dividers]=\"false\"` repeated on every modal, or a reach into `.modal > .header` / `.body` / `.actions` with `!important` because hiding the rules left the padding stacked.",
782
782
  "replaceWith": "`provideDsConfig({ modal: { dividers: false } })`, which drops the rules AND the padding that existed to clear them"
783
783
  },
784
784
  {
@@ -822,7 +822,7 @@
822
822
  "[stickyScrollbar]=\"true\"",
823
823
  "size=\"sm\""
824
824
  ],
825
- "why": "An attribute repeated identically on every element - one consumer binds `[stickyScrollbar]=\"true\"` on all 35 of its tables and `size=\"sm\"` on 146 buttons.",
825
+ "why": "An attribute repeated identically on every element - `[stickyScrollbar]=\"true\"` on every table, `size=\"sm\"` on every button.",
826
826
  "replaceWith": "`provideDsConfig` with the matching section (`table`, `control.size`, …)"
827
827
  },
828
828
  {
@@ -842,7 +842,7 @@
842
842
  "'skeleton'",
843
843
  "'overlay'"
844
844
  ],
845
- "why": "The computed beside every list table - `items().length > 0 ? 'overlay' : 'skeleton'` - one consumer feature carried three copies of it.",
845
+ "why": "The computed beside every list table - `items().length > 0 ? 'overlay' : 'skeleton'`.",
846
846
  "replaceWith": "`[loading]=\"true\"`, which resolves the treatment itself; pin a value only where you mean to override the rule"
847
847
  },
848
848
  {
@@ -127,16 +127,19 @@
127
127
  "new": null,
128
128
  "action": "Only if you SUBCLASS a DS field and declare a member named `hint`, `error`, `warning`, `errors`, `invalid`, `touched` or `reserveMessage`: it is an inherited member now rather than an own member, so an incompatible re-declaration fails where it may previously have shadowed. Redeclaring with the same shape still works.",
129
129
  "appliesWhen": "No public API changed — every input keeps its name, type, default and documentation, and the generated docs reference lost nothing. `success`, `label`, `required` and `optional` were deliberately NOT lifted and remain per-component.",
130
- "pitfall": "Beware the REPORT here, not just the code. `npm run class-surface` lists those seven names as LOST from fourteen field components, which is an artefact of counting declarations per FILE — they moved UP into DsFieldBase and every field still has them by inheritance. AUTHORING already flags a member that moved to a base class as something the tool cannot see. The genuine new collision is different: `success` is a NEW member on the eight bordered fields that lacked it, so a subclass of any of those declaring `success` fails with TS4114.",
131
- "note": "The seven shared inputs and the `reserveMessageResolved` helper are declared once on a new `DsFieldBase` instead of being hand-copied into each of the fourteen fields. Both CVA bases extend it, and ds-radio extends it directly.",
130
+ "pitfall": "Seven members were not lost, they moved UP onto an internal shared base, and every field still has them by inheritance — so an override of one of those needs no change. The genuine new collision is different: `success` is a NEW member on the eight bordered fields that lacked it, so a subclass of any of those declaring `success` fails with TS4114.",
131
+ "note": "The seven shared inputs and the `reserveMessageResolved` helper are declared once on a new internal shared base instead of being hand-copied into each of the fourteen fields. Every field reaches them by inheritance.",
132
132
  "searchHints": [
133
133
  "extends TextareaComponent",
134
134
  "extends InputComponent",
135
- "DsFieldBase",
136
- "DsControlValueAccessor",
137
135
  "reserveMessage",
138
136
  "reserveMessageResolved",
139
- "touched"
137
+ "touched",
138
+ "extends DsFieldBase",
139
+ "extends DsControlValueAccessor",
140
+ "extends DsBooleanControlValueAccessor",
141
+ "DsFieldBase",
142
+ "DsControlValueAccessor"
140
143
  ],
141
144
  "surface": "typescript",
142
145
  "detect": [
@@ -206,7 +209,7 @@
206
209
  "action": "Only for a `::ng-deep` rule that treated the HOST as the pill — a background, a border-radius, a `display: grid`, a border. Retarget it at `ds-segmented .track`.",
207
210
  "appliesWhen": "A token override (`--ds-segmented-*`) is unaffected and needs nothing: the pill's custom properties stayed on `:host` and inherit down.",
208
211
  "pitfall": "Left alone, such a rule now paints the whole STACK — label, pill and message row — instead of the control.",
209
- "note": "ds-segmented stacks a label, the pill and a message row now, so the pill moved off `:host` onto an inner `.track`. Additive alongside: the component provides NG_VALUE_ACCESSOR and resolves its message through resolveFieldMessage, so both form systems and the label / hint / error / warning / errors inputs work as on the other fields.",
212
+ "note": "ds-segmented stacks a label, the pill and a message row now, so the pill moved off `:host` onto an inner `.track`. Additive alongside: the component provides NG_VALUE_ACCESSOR and resolves its message the same way the fields do, so both form systems and the label / hint / error / warning / errors inputs work as on the other fields.",
210
213
  "searchHints": [
211
214
  "ds-segmented",
212
215
  "::ng-deep",
@@ -230,7 +233,7 @@
230
233
  "Message inputs absorb null and undefined instead of crashing. hint, error, warning and success took a bare string and the resolver called .trim() on whatever arrived, so [error]=\"form.errors?.message\" pushed null in and threw a TypeError during render whenever the expression was empty. All four now transform at the input boundary — trimmed, with null/undefined becoming ''.",
231
234
  "A disabled ds-icon-button variant=\"standard\" mixes its glyph toward the surface: color-mix(in srgb, <icon> 40%, var(--surface-default)), replacing the shared fixed-lightness recipe. It is the only variant with neither a fill nor a border, so the glyph carries the whole state, and the old recipe left it 1.46:1 from the enabled icon in dark (light 4.17 -> 5.19:1, dark 1.46 -> 3.58:1). Scoped to standard on purpose: filled's icon is --c-on, and white mixed into a white surface does not move. --ds-icon-button-icon-color-disabled is the same hook and still wins; only the default under it changed.",
232
235
  "ds-field-message: the `state` input never picked an icon, though its docblock and the generated API reference both said it did (`state` \"decides colour and icon\"; `icon` \"overrides the glyph the state would pick\"). `icon` is a plain input<IconName|null>(null) with no per-state default. Behaviour is unchanged — only the documentation was wrong. If you left `icon` unset expecting a glyph from the state, pass one explicitly.",
233
- "SegmentedComponent gained eight members when it joined the form systems (label, disabled, isDisabled, message, invalidResolved, fieldMessage, hintId, uid), so it is the tenth class in this release's class-surface report and the only genuinely new collision surface beyond `success`. A subclass of it declaring any of those names now fails with TS4114."
236
+ "SegmentedComponent gained eight members when it joined the form systems (label, disabled, isDisabled, message, invalidResolved, fieldMessage, hintId, uid), which is the only genuinely new collision surface beyond `success`. A subclass of it declaring any of those names now fails with TS4114."
234
237
  ],
235
238
  "deleteList": [
236
239
  {
@@ -242,6 +245,16 @@
242
245
  ],
243
246
  "why": "A `?? ''` guard wrapped around a message binding - `[error]=\"form.errors?.message ?? ''\"` - added because a null pushed into `hint` / `error` / `warning` / `success` threw a TypeError during render.",
244
247
  "replaceWith": "nothing - bind the expression directly, the inputs absorb null now"
248
+ },
249
+ {
250
+ "id": "modal-teardown-to-reset-date-picker",
251
+ "surface": "template",
252
+ "find": [
253
+ "(closed)",
254
+ "@if (open())"
255
+ ],
256
+ "why": "A modal body torn down on `(closed)` — or guarded behind the open flag — purely so a re-opened `ds-date-picker` starts without the previous attempt's error. The picker clears its own stale error and text on the value-to-text effect now. The teardown never worked reliably anyway: reopening inside the 300 ms leave animation cancels the close, so `closed` never fires.",
257
+ "replaceWith": "nothing - keep the body mounted"
245
258
  }
246
259
  ]
247
260
  }
@@ -167,7 +167,7 @@
167
167
  "kind": "behavior",
168
168
  "old": "extends TableComponent",
169
169
  "new": null,
170
- "action": "Run `npm run class-surface v0.10.1 v0.10.2` for the authoritative list, then per member: rename your own, or add `override` where the base semantics genuinely match.",
170
+ "action": "Build after upgrading: the compiler enumerates every collision, and that list is authoritative. Then per member: rename your own, or add `override` where the base semantics genuinely match.",
171
171
  "appliesWhen": "Only a consumer that EXTENDS a DS component class. Subclassing is unsupported (design-system.md § Components); template users of the `<ds-…>` elements need nothing. No members were lost this release.",
172
172
  "pitfall": "A redeclared PRIVATE fails with TS2415 exactly like a public collision, which is why `TimePickerComponent.insideATrigger` counts here at all. And `FieldMessageComponent` gained `iconResolved` and `config` but is internal and not exported, so those matter only to a fork.",
173
173
  "note": "Gained: AutocompleteComponent and MultiSelectComponent (`chipsMode`, `showsEveryChip`); MenuItemComponent (`description`, `descriptionId`); SearchComponent (`bridge`, `disabled`, `formDisabled`, `hidden`, `isDisabled`, `markTouched`, `registerOnChange`, `registerOnTouched`, `setDisabledState`, `writeValue` — it declares the control-value-accessor surface itself now); SidenavComponent (`rail`); SidenavItemComponent (`rail`, `railResolved`); TableComponent (`actionReason`, `actionsFor`, `hasActionsFor`, `visibleRowActions`); TimePickerComponent (private `insideATrigger`); and `messageIcon` on all fifteen field components. TS4114 demands `override`, TS2415 fires on a redeclared private. The protected-to-public sweep across fourteen classes is the separate `resolved-readbacks-are-public` entry and collides the same way.",
@@ -226,7 +226,7 @@
226
226
  "kind": "behavior",
227
227
  "old": "TimeColumnsComponent.onKey",
228
228
  "new": null,
229
- "action": "Read the current declaration in `time-columns.component.ts` and match it, or drop the override.",
229
+ "action": "Read the current signature of the internal `TimeColumnsComponent.onKey` from the package's type declarations and match it, or drop the override.",
230
230
  "appliesWhen": "It is `protected`, so no consumer calls it and templates are unaffected. The component is internal to ds-time-picker and subclassing it was never supported.",
231
231
  "note": "The parameter list changed, so an overriding subclass has a signature that no longer matches the base (TS2416).",
232
232
  "searchHints": [
@@ -240,7 +240,7 @@
240
240
  "onKey(",
241
241
  "extends TimeColumnsComponent"
242
242
  ],
243
- "verify": "No TimeColumnsComponent subclass overrides `onKey` with the old parameter list."
243
+ "verify": "No subclass of the internal TimeColumnsComponent overrides `onKey` with the old parameter list."
244
244
  },
245
245
  {
246
246
  "id": "overlay-outside-guard-tests-the-trigger",
@@ -369,7 +369,7 @@
369
369
  "new": null,
370
370
  "action": "Only if you worked around it: a `padding-block` or `line-height` override added to an option label, a table cell clip or a breadcrumb to get the descenders back can go.",
371
371
  "appliesWhen": "No geometry change — option row 30px, multi-select 36px, table row 38px are all unchanged. For your own CSS of the same shape: `overflow: clip` keeps `text-overflow: ellipsis` working and keeps `scrollWidth > clientWidth` reporting true, both checked in Chromium, so a clip-detection test needs no change. Where `overflow-clip-margin` is unsupported, clip degrades to exactly the old shave.",
372
- "note": "Every clipped label sat in a `line-height: 1` box with no padding, so 2.13px above the cap line and 1.47px below the baseline were cut (MBP-245). They use `overflow: clip` with a `--space-1` clip margin now.",
372
+ "note": "Every clipped label sat in a `line-height: 1` box with no padding, so 2.13px above the cap line and 1.47px below the baseline were cut. They use `overflow: clip` with a `--space-1` clip margin now.",
373
373
  "surface": "style",
374
374
  "verify": "An option list, a clipped table cell and a breadcrumb render full descenders (the tail of a g is complete) at unchanged row heights.",
375
375
  "searchHints": [
@@ -386,16 +386,16 @@
386
386
  "ds-menu-item: new `description` input renders a standing second line and wires `aria-describedby`. If you hand-rolled that line by projecting your own span into the item, move it to the input -- yours lands INSIDE the accessible name, the input's does not.",
387
387
  "ds-search: `clear()` is now public. A host-owned Clear button should call it rather than writing '' into `value`, which does not cancel an armed debounce when the text already matches what the control last pushed.",
388
388
  "ds-multi-select: its panel now honours `--ds-dropdown-panel-radius` (it was hardcoded at 8px). If you set that token and wondered why one of the three connected panels ignored it, this is why -- no action needed beyond re-checking the value looks right on all three.",
389
- "ds-search joins both form systems: NG_VALUE_ACCESSOR + DsControlValueAccessor, so [(ngModel)], formControlName and a signal form now bind it, and a new `disabled` input folds together with the form's own disabled state (the shell paints the disabled surface, which it never did). Its own [(value)] is unchanged. Deliberately NO label and no message row - a toolbar filter is not a validated field.",
389
+ "ds-search joins both form systems — it provides NG_VALUE_ACCESSOR and takes the same value plumbing the fields use — so [(ngModel)], formControlName and a signal form now bind it, and a new `disabled` input folds together with the form's own disabled state (the shell paints the disabled surface, which it never did). Its own [(value)] is unchanged. Deliberately NO label and no message row - a toolbar filter is not a validated field.",
390
390
  "ds-menu: new --ds-menu-radius, defaulting to --radius-md, which is what the component hardcoded. Nothing moves. Inside a ds-popover the menu still clips to --ds-menu-clip-radius, published by the popover.",
391
391
  "maxVisibleChips gained an 'all' mode on ds-autocomplete and ds-multi-select - render every chip, no measuring. Additive on its own; the actionable half is that null no longer means that (see max-visible-chips-null-is-unset-*).",
392
392
  "ds-button variant=\"tonal\": the disabled label now uses the same 40% mix toward --surface-default as ghost / text / outline, instead of the shared oklch(from accent 70% ...) recipe. Visual only, no action. It fixes the dark theme, where the old recipe left the disabled label 1.11:1 from the enabled one (a hue going grey and nothing else); the state gap is now 2.90:1 dark and 3.39:1 light, and the label keeps its hue. --ds-button-label-color-disabled still overrides it.",
393
393
  "ds-table: TableColumn gained `interactive?: boolean`. The marked column's cell takes --ds-table-cell-link-color (default --accent) and --ds-table-cell-link-decoration (default underline) while its row is hovered, on a rowInteractive table only. Purely additive - an existing column config renders exactly as before. Reach for it on the cell whose TEXT names what the row opens; the row tint says the row is clickable and nothing else said which text was the target.",
394
394
  "ds fields on the SIGNAL FORMS path: they threw once per field (NgControl bridge has no events stream) and then displayed the first validation failure forever, because the frozen snapshot was the fallback whenever live errors went empty. Fixed - the NgControl path now bows out when it has no live stream. No consumer action: if you bind [field] on a DS control, upgrade and the console noise and the stale message both go. Reactive and template-driven forms are unchanged.",
395
- "DS_CONFIG: provideDsConfig() must be called ONCE per injector. Two calls in the same `providers` array do not merge - both resolve their parent with skipSelf, so the later wins and the earlier is silently lost. Merging happens across injector LEVELS (a route or component inheriting the app's config), not within one array. Documented on the function after it bit us in our own docs app.",
395
+ "DS_CONFIG: provideDsConfig() must be called ONCE per injector. Two calls in the same `providers` array do not merge - both resolve their parent with skipSelf, so the later wins and the earlier is silently lost. Merging happens across injector LEVELS (a route or component inheriting the app's config), not within one array.",
396
396
  "data-focus=\"inset\" draws the focus ring INSIDE the border box, for a subtree under an overflow:hidden ancestor that would otherwise clip it away and leave the element focusable with no indicator at all. Unlike the other focus styles it is NOT pinned to :root - set the attribute on the clipping element and the declarations inherit into the subtree.",
397
- "migrations/<version>.json - the files dist/ds/migrations carries into node_modules - now carry `surface`, `detect`, `verify`, `restore`, `supersedes` and a structured `deleteList` on every published release. Read `surface` for which artifact to search, `detect` plus searchHints to find it, `verify` for the positive assertion a re-check can test, and deleteList[].find for code that is now redundant. `supersedes` points BACKWARD only: a manifest never references a later version, and the lint rejects one that tries.",
398
- "components.md - the digest tools/build-schematics.mjs copies into dist/ds for a consumer's own agent to read - was missing ds-app-layout and ds-auth-layout entirely, and named --primary, --text-on-primary and --secondary as the active sidenav item defaults, which this release replaced with the wash. Both corrected. If you hand-rolled an app shell or a sign-in screen because the digest did not list one, or overrode those three tokens to restyle the active item, re-read those entries."
397
+ "migrations/<version>.json - the files this package carries in node_modules - now carry `surface`, `detect`, `verify`, `restore`, `supersedes` and a structured `deleteList` on every published release. Read `surface` for which artifact to search, `detect` plus searchHints to find it, `verify` for the positive assertion a re-check can test, and deleteList[].find for code that is now redundant. `supersedes` points BACKWARD only: a manifest never references a later version.",
398
+ "components.md - the digest shipped in the package for a consumer's own agent to read - was missing ds-app-layout and ds-auth-layout entirely, and named --primary, --text-on-primary and --secondary as the active sidenav item defaults, which this release replaced with the wash. Both corrected. If you hand-rolled an app shell or a sign-in screen because the digest did not list one, or overrode those three tokens to restyle the active item, re-read those entries."
399
399
  ],
400
400
  "deleteList": [
401
401
  {
@@ -56,10 +56,10 @@
56
56
  }
57
57
  ],
58
58
  "informational": [
59
- "The shell list in styles/_focus.scss is now maintained from a measurement, not from a read of the code: it had been wrong for two releases. If you add a component that paints its own ring on :focus-within, suppress the base rule on the control it speaks for - `outline: 0` cannot do it, because the base indicator is a box-shadow.",
59
+ "If you add a component that paints its own ring on :focus-within, suppress the base rule on the control it speaks for - `outline: 0` cannot do it, because the base indicator is a box-shadow.",
60
60
  "Two authoring mixins are now documented for consumers building their own composite controls: `focus.owns-the-focus-ring($control)` in styles/focus, and `text-clip.single-line-ellipsis` in styles/text-clip. Both are opt-in - no existing code changes.",
61
61
  "A private --_* token declared on :host does not reach a CDK-portaled panel, and an unresolvable var() silently becomes the property's initial value - none for box-shadow, 0 for border-radius. If you style a DS panel from your own CSS, read the PUBLIC --ds-* token there, not the private one.",
62
- "Fourteen public tokens were always overridable but never reached the token reference, because the extractor searched for the literal `var(--ds-` and a resolver wrapped across lines put a newline inside it: --ds-container-pad-x, --ds-multi-select-border-color (+-focus), --ds-segmented-selected-bg-color / -label-color / --ds-segmented-radius, --ds-time-picker-option-bg-color-selected / -text-color-selected / -bg-color-hover, --ds-time-picker-trigger-bg-color / -border / -color, --ds-field-message-icon-offset, --ds-time-picker-focus-shadow. Nothing changed in the components - if you hand-rolled around one of these because it looked unsupported, the override is supported and is the way to do it."
62
+ "Fourteen public tokens were always overridable but never reached the token reference: --ds-container-pad-x, --ds-multi-select-border-color (+-focus), --ds-segmented-selected-bg-color / -label-color / --ds-segmented-radius, --ds-time-picker-option-bg-color-selected / -text-color-selected / -bg-color-hover, --ds-time-picker-trigger-bg-color / -border / -color, --ds-field-message-icon-offset, --ds-time-picker-focus-shadow. Nothing changed in the components - if you hand-rolled around one of these because it looked unsupported, the override is supported and is the way to do it."
63
63
  ],
64
64
  "deleteList": [
65
65
  {
@@ -4,19 +4,18 @@
4
4
  {
5
5
  "id": "exported-class-members-grew",
6
6
  "kind": "behavior",
7
- "old": "class MyTable extends TableComponent, class MyButton extends ButtonComponent, class MyField extends DsFieldBase (or any DS component/base you subclass)",
7
+ "old": "class MyTable extends TableComponent, class MyButton extends ButtonComponent (or any exported DS component you subclass)",
8
8
  "new": null,
9
9
  "action": "Only if you extend one of these and already declare one of the GAINED names: rename yours, or add `override` if you meant to replace ours. Build after upgrading — the compiler enumerates every collision.",
10
10
  "appliesWhen": "Subclassing a DS component is unsupported, but consumers do it. Template users of the `<ds-…>` elements need nothing.",
11
- "pitfall": "`protected` is no protection: a redeclared protected member collides exactly as a public one does. And read the report carefully — `hint`, `error`, `warning`, `messageIcon`, `reserveMessage` and `reserveMessageResolved` MOVED from DsFieldBase to a new DsMessageBase that DsFieldBase extends, so class-surface reports them as LOST from one and GAINED on the other. They still resolve through DsFieldBase with the same names, types and defaults, and `override` still works because it accepts a member from any ancestor. Nothing to do for those.",
12
- "note": "Measured with `npm run class-surface` against 0.10.3. Gained: TableComponent `cellLink`; ButtonComponent `disabledReason`, `ariaDescribedBy`, `softDisabled`, `message`, `fieldMessage`, `hasMessageRow`, `describedBy`, `hintId`, `reasonId`, `uid`; IconButtonComponent `ariaDescribedBy`; SidenavComponent `brandRoute`, `brandLinkLabel` and the protected `brandAriaLabel`; CheckboxComponent and RadioGroupComponent each the protected `controlState`. TS4114 asks for an `override` modifier, TS2415 fires where the signature differs.",
11
+ "pitfall": "`protected` is no protection: a redeclared protected member collides exactly as a public one does. Six members — `hint`, `error`, `warning`, `messageIcon`, `reserveMessage` and `reserveMessageResolved` — moved one level up between two internal base classes, so a member-by-member diff can report them as lost and regained. They still reach your subclass with the same names, types and defaults, and an existing `override` still works because it accepts a member from any ancestor. Nothing to do for those; only the GAINED names below can collide.",
12
+ "note": "Compared against 0.10.3. Gained: TableComponent `cellLink`; ButtonComponent `disabledReason`, `ariaDescribedBy`, `softDisabled`, `message`, `fieldMessage`, `hasMessageRow`, `describedBy`, `hintId`, `reasonId`, `uid`; IconButtonComponent `ariaDescribedBy`; SidenavComponent `brandRoute`, `brandLinkLabel` and the protected `brandAriaLabel`; CheckboxComponent and RadioGroupComponent each the protected `controlState`. TS4114 asks for an `override` modifier, TS2415 fires where the signature differs.",
13
13
  "surface": "typescript",
14
- "verify": "Build your app: no TS4114 or TS2415 is raised against a class that extends a DS component or DsFieldBase.",
14
+ "verify": "Build your app: no TS4114 or TS2415 is raised against a class that extends a DS component.",
15
15
  "searchHints": [
16
16
  "extends TableComponent",
17
17
  "extends ButtonComponent",
18
18
  "extends IconButtonComponent",
19
- "extends DsFieldBase",
20
19
  "cellLink",
21
20
  "disabledReason",
22
21
  "ariaDescribedBy",
@@ -28,13 +27,14 @@
28
27
  "brandRoute",
29
28
  "brandLinkLabel",
30
29
  "brandAriaLabel",
31
- "controlState"
30
+ "controlState",
31
+ "extends DsFieldBase",
32
+ "extends DsMessageBase"
32
33
  ],
33
34
  "detect": [
34
35
  "extends TableComponent",
35
36
  "extends ButtonComponent",
36
37
  "extends IconButtonComponent",
37
- "extends DsFieldBase",
38
38
  "cellLink",
39
39
  "disabledReason",
40
40
  "ariaDescribedBy",
@@ -71,51 +71,6 @@
71
71
  "--ds-menu-divider-spacing"
72
72
  ]
73
73
  },
74
- {
75
- "id": "published-manifests-corrected",
76
- "kind": "behavior",
77
- "old": "A repo whose last @ids-group-ltd/ids-design-system upgrade ran before this release and crossed 0.2.0, 0.5.1, 0.7.1, 0.8.0, 0.9.0 or 0.10.0",
78
- "new": null,
79
- "action": "Re-run these items, now corrected in migrations/<version>.json: 0.2.0#surface-subtle-token-rename, 0.5.1#progress-variant-remap, 0.5.1#badge-variant-to-status-rename, 0.7.1#surface-motion-partial-a-la-carte, 0.7.1#modal-title-flex-moved-to-heading, 0.8.0#table-client-sort-replaced-by-sort-mode, 0.9.0#input-signal-types-widened-by-transforms, 0.10.0#input-floating-removed, 0.10.0#modal-confirm-error-tone-paints-a-badge. Nothing else in those files changed meaning.",
80
- "appliesWhen": "Only for a repo that already stepped through one of those six versions. A first-time consumer, or one whose upgrade runs from here on, reads the corrected files and needs none of this. The six defects are independent - crossing 0.7.1 says nothing about 0.9.0.",
81
- "pitfall": "Two of these UNDO work rather than adding it. 0.7.1 filed the modal `.title` as a rename to `.heading`; no rename ever happened, so a repo that renamed it on our word must put it back - `.title` still paints the heading text. And 0.7.1 handed out bare `styles/…` @use specifiers that resolve only inside the design-system repo: the line looks right and fails at build from an app. The 0.8.0 one is the silent case - an unset sortMode was documented as resolving to server when it resolves to client, so a server-paged table passes every check while sorting only the rows already on screen.",
82
- "note": "Nine data defects found by auditing each published manifest against the code of its own release: three changes that had no item, two wrong instructions, one verify that certified a bug, and three items whose surface named too few file types.",
83
- "surface": [
84
- "style",
85
- "template",
86
- "typescript"
87
- ],
88
- "verify": "No `--surface-subtle` remains in any stylesheet. No bare `@use 'styles/…'` of a design-system partial remains - each is package-qualified. Every ds-table that binds [total] declares sortMode=\"server\" explicitly. No `variant` remains on ds-badge or ds-progress in any file type. No stylesheet sets --field-h-floating, --field-floating-label-fs, --field-floating-label-lh, --field-floating-label-top or --field-floating-pad-t. The app builds with no TS2322 naming InputSignal and no TS2416 on a class extending a DS field.",
89
- "searchHints": [
90
- "--surface-subtle",
91
- "@use 'styles/surface-motion'",
92
- "@use 'styles/overlay-motion'",
93
- ".heading",
94
- "sortMode",
95
- "[total]",
96
- "variant",
97
- "--field-h-floating",
98
- "--field-floating-label-fs",
99
- "--field-floating-pad-t",
100
- "InputSignal<",
101
- "ds-badge",
102
- "ds-progress",
103
- "ds-modal-card",
104
- "floating"
105
- ],
106
- "detect": [
107
- "--surface-subtle",
108
- "@use 'styles/surface-motion'",
109
- "@use 'styles/overlay-motion'",
110
- "--field-h-floating",
111
- "--field-floating-label-fs",
112
- "--field-floating-label-lh",
113
- "--field-floating-label-top",
114
- "--field-floating-pad-t",
115
- "InputSignal<",
116
- "ds-modal-card ::ng-deep .heading"
117
- ]
118
- },
119
74
  {
120
75
  "id": "sidenav-item-without-destination-is-a-button",
121
76
  "kind": "behavior",
@@ -141,9 +96,9 @@
141
96
  ],
142
97
  "informational": [
143
98
  "`--ds-field-message-icon-offset` and `--ds-time-picker-focus-shadow` are public, overridable, and listed in the token reference - the supported way to retune either. Nothing changed in the components - if you hand-rolled around either because it looked unsupported, the override is supported and is the way to do it. They belong with the twelve named under 0.10.3.",
144
- "If you applied 0.10.2 before its manifest was completed, two of its notes were reachable only from the CHANGELOG; this is one of them. components.md, the digest dist/ds carries for your own agent, had named --primary, --text-on-primary and --secondary as the active ds-sidenav-item defaults - the wash replaced them, so an override written against those three does not do what it looks like.",
99
+ "If you applied 0.10.2 before its manifest was completed, two of its notes were reachable only from the CHANGELOG; this is one of them. components.md, the digest this package carries for your own agent, had named --primary, --text-on-primary and --secondary as the active ds-sidenav-item defaults - the wash replaced them, so an override written against those three does not do what it looks like.",
145
100
  "The second note 0.10.2 kept only in its CHANGELOG: `data-focus=\"inset\"` (shipped in that release) draws the focus ring INSIDE the border box, for a subtree under an overflow:hidden ancestor that would otherwise clip it away entirely. It is the only focus style not pinned to :root - set it on the clipping element.",
146
- "ds-table columns take a new optional `link: (row) => string | readonly unknown[] | null`. Nothing changes on a column that does not set it; see the class-surface entry if you SUBCLASS TableComponent. Where you compensated for an invisible row click by repeating the destination as a 'View Details' item in the row overflow menu, that item can go: give the name column `link` instead and the destination becomes a real <a> - tabbable as a link, Ctrl/Cmd-clickable, and announced as a link rather than as a table row. If you also set `rowInteractive`, note the pair costs two tab stops per row; the link alone is usually the better trade on a long list. (delete list: row-menu-view-details-duplicate)",
101
+ "ds-table columns take a new optional `link: (row) => string | readonly unknown[] | null`. Nothing changes on a column that does not set it; see the exported-class-members-grew item if you SUBCLASS TableComponent. Where you compensated for an invisible row click by repeating the destination as a 'View Details' item in the row overflow menu, that item can go: give the name column `link` instead and the destination becomes a real <a> - tabbable as a link, Ctrl/Cmd-clickable, and announced as a link rather than as a table row. If you also set `rowInteractive`, note the pair costs two tab stops per row; the link alone is usually the better trade on a long list. (delete list: row-menu-view-details-duplicate)",
147
102
  "ds-card gains --ds-card-overflow, default visible. Opt-in on purpose: clipping a card also cuts the focus ring off any child at its edge, so where a clipped card holds focusable content pair it with data-focus=\"inset\".",
148
103
  "ds-button gains --ds-button-shadow and --ds-button-shadow-hover, both default none. Purely additive; -shadow-hover falls back to -shadow, and the focus/pressed hooks still win in their own states.",
149
104
  "ds-button gains disabledReason, hint, warning, error, messageIcon, reserveMessage and ariaDescribedBy; ds-icon-button gains ariaDescribedBy. All additive - a button that sets none of them is byte-identical in behaviour and layout. Two things worth knowing before you use them. (1) disabledReason CHANGES HOW THE BUTTON IS DISABLED: with a reason set the button carries aria-disabled=\"true\" instead of the native disabled attribute, so it stays focusable and the reason is announced as its accessible description; the click is swallowed in the handler, so (pressed) still never fires. If you have CSS keyed on `ds-button button[disabled]` or `:disabled`, add `[aria-disabled=\"true\"]` - the library's own disabled paint already covers both. (2) hint/warning/error are for the OTHER kind of refusal: a temporary one the user lifts by filling the form in. Do not disable the button for those - leave it live, judge validity in the submit handler, and let the message line explain. A message-bearing button becomes a column, and since the host shrinks to fit, a message longer than the label widens the pair, button included. (delete list: button-disabled-reason-tooltip)",