ui-style-kit-css 2.1.0 → 2.3.0

package/docs/BRIDGE-MIGRATION.md

@@ -0,0 +1,20 @@
+# Deprecated Interactive Surface Bridge Migration
+
+The canonical integration for new applications is `ui-style-kit-css/visual.css`, `ui-style-kit-css/interactive-surface-theme.css`, `interactive-surface-css/state-core.css`, and `layout-style-css` in that order.
+
+`interactive-surface-bridge` and `with-bridge` remain public v2 compatibility exports. They are deprecated because they include stateful bridge behavior that is no longer part of the canonical token-and-paint boundary. They are retained unchanged in v2 and will not be redirected to the token-only bridge.
+
+The shared semantic path is separate from migration: a third-party token producer may load before `interactive-surface-css/standalone-preset.css`, but it does not reproduce UI Style Kit's specialized variant and level mappings. Existing bridge consumers should follow the canonical imports above when migrating.
+
+## Retained deprecated imports
+
+Existing integrations may continue to use either exported stateful path while scheduling their migration:
+
+```js
+import "ui-style-kit-css/interactive-surface-bridge";
+import "ui-style-kit-css/interactive-surface-bridge.css";
+import "ui-style-kit-css/with-bridge";
+import "ui-style-kit-css/with-bridge.css";
+```
+
+Do not combine a deprecated bridge import with `interactive-surface-theme.css`; select the legacy stateful path during migration or the canonical token-only path for new integration work.

package/docs/ECOSYSTEM.md

@@ -2,15 +2,46 @@
 
 UI Style Kit CSS is the visual layer in the three-library CSS ecosystem. It can run alone, but it also has stable integration points for Interactive Surface CSS and Layout Style CSS.
 
+`ecosystem-compatibility.json` is the authoritative source for supported ranges, validated combinations, canonical imports, and deprecated bridge metadata. UI Style Kit owns this file temporarily until a dedicated ecosystem fixture repository is introduced.
+
+Its companion source records pin the exact published merge revisions used by integration and release verification. Update those immutable pins whenever a later companion release changes the validated contract.
+
+## Remote Validation Sequence
+
+The pinned Interactive Surface and Layout commits are published merge objects. Before a UI branch or pull request is expected to validate, verify each pinned SHA remains fetchable from its GitHub repository. The CI and publish workflows perform the same remote-object preflight, so they intentionally fail rather than silently substituting a mutable branch or stale registry artifact when either companion revision is unavailable.
+
 ## Aligned Versions
 
 | Library | Current aligned version | Owns |
 |---|---:|---|
-| `ui-style-kit-css@2.1.0` | staged source target | visual identity, color themes, UI paint, native HTML styling, content wrapping, and bridge tokens |
-| `interactive-surface-css@1.5.0` | published release | interaction-state primitives, surface behavior, state layers, and input affordances |
-| `layout-style-css@2.1.0` | staged source target | structural wrappers, grids, sections, app shells, and layout recipes |
+| `ui-style-kit-css@2.3.0` | current release target | visual identity, color themes, UI paint, native HTML styling, content wrapping, and bridge tokens |
+| `interactive-surface-css@1.6.0` | compatible state release | interaction-state primitives, surface behavior, state layers, and input affordances |
+| `layout-style-css@3.1.0` | compatible structural release | structural wrappers, grids, sections, app shells, and layout recipes |
+
+The current combination is `ui-style-kit-css@2.3.0`, `interactive-surface-css@1.6.0`, and `layout-style-css@3.1.0`. UI Style Kit `2.3.0` is the current release target; the companion versions are published releases. Layout Style `3.1.0` is the compatible structural release. The validated minimum remains `ui-style-kit-css@2.1.0`, `interactive-surface-css@1.5.0`, and `layout-style-css@3.0.0`.
+
+## Layout-to-visual pairing matrix
+
+Pairings are recommendations, never dependencies. `data-ly-layout`, `data-ui`, `data-theme`, and `data-mode` remain independently selectable; `layout-style-css/personalities.json` publishes the machine-readable source.
+
+| Layout personality | Visual guidance |
+| --- | --- |
+| Minimal SaaS, Bento, Maximalist, Bauhaus, Tactile, Neumorphism, Retrofuturism, Brutalism, Cyberpunk, Y2K, Retro Glass | Native UI Style Kit match with the same identifier |
+| F-pattern, Z-pattern, Split Screen, Mondrian | Any UI Style Kit visual preset; these are structure-only layouts |
+| Synthwave | Recommend `cyberpunk` or `retrofuturism`; Layout's rendered demo verifies each preset while keeping the synthwave layout selected |
 
-UI Style Kit `2.1.0` and Layout Style `2.1.0` remain staged source targets until approved release steps complete. Interactive Surface `1.5.0` is the released companion state engine for this upgrade path.
+## Shared semantic theming
+
+UI Style Kit's complete, visual, and focused visual entrypoints produce the 12 package-neutral `--ui-*` control tokens under `[data-ui][data-theme][data-mode]`. A third-party theme may produce the same contract under its own scope; consumers do not need UI Style Kit-specific `--usk-*` values. Package-specific values remain first in consumer fallback chains, shared semantic values come second, and legacy values or literals remain last.
+
+A third-party producer can theme Interactive Surface's complete standalone entry point without a package-specific adapter:
+
+```js
+import "third-party-theme/tokens.css";
+import "interactive-surface-css/standalone-preset.css";
+```
+
+UI Style Kit can use the same portable path by loading `ui-style-kit-css/visual.css` before `interactive-surface-css/standalone-preset.css`. That composition provides the semantic control baseline. Use the canonical `interactive-surface-theme.css` plus `state-core.css` path when an application needs UI Style Kit's specialized variant, level, icon-role, and state-opacity mappings.
 
 ## Adoption Paths
 
@@ -57,3 +88,7 @@ import "layout-style-css";
 - Layout Style CSS owns structural wrappers, layout recipes, grids, app shells, and section composition.
 
 The canonical theme bridge does not make Interactive Surface a dependency of UI Style Kit. It only maps shared `--usk-*` roles to `--interactive-surface-*` tokens and provides paint; `state-core.css` continues to own interaction mechanics. The older `interactive-surface-bridge` and `with-bridge` exports are deprecated compatibility paths whose stateful behavior remains unchanged.
+
+## Canonical ownership order
+
+Load UI visual CSS first, UI interaction-theme paint second, Interactive Surface state core third, Layout CSS fourth, and application overrides last. Layout `3.1.0` no longer exports `integrations/ui-style-kit.css` or `legacy.css`; use its root or supported `foundation.css`, wrapper, primitive, recipe, utility, and personality entrypoints.

package/docs/PUBLISHING.md

@@ -1,38 +1,63 @@
 # Publishing Guide
 
+## 2.3.0 release workflow
+
+Prepare `ui-style-kit-css@2.3.0` on its release branch, open a pull request against `main`, and merge only after the complete gate is green. The aligned companion set is `layout-style-css@3.1.0` and `interactive-surface-css@1.6.0`.
+
+Do not push `v2.3.0` before the reviewed release commit is on `main`. A pushed version tag runs Release Version Alignment, which validates the tag/package/changelog contract and creates the GitHub Release; publishing that release triggers the protected npm workflow.
+
 ## Dry run
 
 ```bash
 npm run release:verify
 ```
 
-`npm run release:verify` is the non-publishing release gate. It runs `npm run check`, `npm run test:e2e`, `npm run test:axe`, `npm run test:visual`, `npm run test:matrix`, `npm run check:ecosystem:packs`, `npm audit --audit-level=moderate`, and `npm run pack:dry-run`.
+`npm run release:verify` is the non-publishing release gate. It runs `npm run check`, `npm run test:e2e`, `npm run test:axe`, `npm run test:visual`, `npm run test:matrix`, the explicit UI-candidate release preflight, `npm audit --audit-level=moderate`, and `npm run pack:dry-run`.
+
+`npm run release:preflight` validates the shared manifests and compatibility contract, queries npm for every exact minimum/current version, resolves every export from the candidate tarball, checks maintained documentation against installed packages, and reuses the current/minimum clean-install browser matrix. Normal UI preflight remains strict and queries `ui-style-kit-css@2.3.0` alongside every other documented exact version. The release workflows pass `--candidate-package ui-style-kit-css`, which excludes only that exact current version while it is absent from npm and still requires every published minimum and companion version. The gate performs no publish, tag, release, or deployment mutation and is therefore safe to execute on pull requests.
+
+`npm run check` rebuilds dist CSS, runs stylelint, executes package and API contracts, validates all theme/mode contrast pairs, enforces the Browserslist compatibility contract through `check:compat`, verifies CSS ownership, and confirms package metadata. Browser gates cover regular demo flows, representative Axe scans, curated visual checks, and the sharded 3,600-combination matrix. `npm run check:ecosystem:packs` verifies standalone, pairwise, and all-three packed package compatibility for canonical visual/theme/state/layout imports and deprecated bridge imports in both supported matrices. `npm run pack:dry-run` shows the exact files that would publish.
+
+`npm run check:ecosystem:current` packs this repository and the sibling `../Layout-Style-CSS` and `../Interactive-Surface-CSS` checkouts. It extracts imports from the explicitly maintained current documentation in all three repositories and resolves every documented specifier from the installed tarballs. Deprecated UI bridge guides are validated as a separate supported-compatibility class; changelogs and Layout migration guides are reviewed historical material rather than current setup. Use `-- --ui-spec <specifier>`, `-- --layout-repo <path>`, `-- --layout-spec <specifier>`, `-- --interactive-spec <specifier>`, `-- --interactive-repo <path>`, `-- --layout-docs-repo <path>`, or `-- --interactive-docs-repo <path>` when validating different package or documentation sources.
+
+`npm run check:ecosystem:minimum` downloads and repacks the declared minimum published runtime versions: `ui-style-kit-css@2.1.0`, `interactive-surface-css@1.5.0`, and `layout-style-css@3.0.0`. Those tarballs predate the additive shared-manifest policy introduced on the coordinated branches, so the minimum matrix validates their exact installed versions and published CSS entry points; current packed heads retain the stricter manifest-schema and current-documentation checks. `npm run check:ecosystem:packs` runs current first and minimum second.
 
-`npm run check` rebuilds dist CSS, runs stylelint, executes package, class API, shared theme-color, and vendor-prefix unit checks, validates core text/link contrast pairs and filled component `on-*` contrast pairs, and confirms package metadata. Browser gates cover regular demo flows, representative Axe scans, curated visual smoke checks, and the sharded 990-combination matrix. `npm run check:ecosystem:packs` verifies standalone, pairwise, and all-three packed package compatibility for the canonical visual/theme/state/layout imports and the deprecated bridge imports. `npm run pack:dry-run` shows the exact files that would publish.
+The current matrix checks `ui-style-kit-css@2.3.0` as the active candidate only while its exact npm version is absent, `interactive-surface-css@1.6.0` as a published release, and `layout-style-css@3.1.0` as a published release. The minimum published matrix remains `ui-style-kit-css@2.1.0`, `interactive-surface-css@1.5.0`, and `layout-style-css@3.0.0`.
 
-By default, `npm run check:ecosystem:packs` packs this repository, packs the sibling `../Layout-Style-CSS` checkout, and packs the published `interactive-surface-css@1.5.0` artifact. Use `-- --layout-repo <path>` or `-- --interactive-spec <specifier>` when validating a different local Layout Style checkout or a different Interactive Surface package source.
+Both matrices install fresh tarball consumers for UI only, Interaction only, Layout only, every pair, and all three. Chromium then checks selected theme paint, native and prefixed components, interaction focus/disabled/loading/selected/persistent states, Layout wrappers/primitives/recipes/personalities, console cleanliness, and an empty external-request log. Three text-free baselines under `tests/snapshots/clean-install/` cover the highest-risk integrated combinations.
 
-`npm run build` uses exactly pinned CSS Tree parsing and Lightning CSS formatting/minification. Generated minified bundles retain the release banner while preserving grammar-sensitive selector and `calc()` whitespace.
+Snapshot verification decodes PNG pixels, requires exact dimensions, ignores pixelmatch-classified antialias noise, uses a `0.1` color threshold, and permits at most `0.25%` differing pixels. The committed fixtures render at 720-721 by 261 pixels and therefore allow 469-470 changed pixels while rejecting the tested 42% meaningful change. A mismatch retains both `SCENARIO-actual.png` and `SCENARIO-diff.png` in the reported safe temporary directory. CI only validates committed baselines and never passes the generation flag. To intentionally refresh them locally, run the current checker with `--update-snapshots`, inspect all three images, and rerun without that flag.
+
+The PR integration and npm-publish workflows read the companion repository and immutable revision pins from `ecosystem-compatibility.json`, then pack those coordinated reviewed artifacts. Advance those pins whenever a later release changes a companion contract. The current values pin the published Interactive Surface CSS merge at `b50a60d8ffd804d8227b1a16903c394556b88511` and the published Layout Style CSS merge at `afcb1fdf70d4635e35739e621ee1598400fed103`.
+
+Use this exact bootstrap and merge sequence:
+
+1. Verify the published Interactive Surface CSS and Layout Style CSS merge commits remain remotely reachable.
+2. Update and review the final UI companion pins against those immutable merge commits.
+3. Push the final UI branch, rerun its explicit UI-candidate ecosystem preflight, and merge UI with a merge commit.
+4. Do not squash or rebase away reviewed release commits that remain part of the pinned verification history.
+
+The workflows enforce immutable remote-object reachability and do not fall back to mutable branches or registry packages. The stable bootstrap ref lets companion workflows load the reviewed preflight implementation before the final UI commit references their heads.
+
+`npm run build` synchronizes manifest-driven component and overflow inventories and uses exactly pinned CSS Tree parsing and Lightning CSS formatting/minification. Every transform resolves the package Browserslist policy through `browserslistToTargets`. Generated minified bundles retain the release banner while preserving grammar-sensitive selector and `calc()` whitespace.
 
 The npm artifact is library-focused: `dist/`, `styles/`, docs, and metadata. Demo pages, favicon source assets, and social preview images remain checked in for GitHub Pages but are excluded from the tarball to keep package installs small.
 
 ## Publish
 
-No package, tag, or registry release occurs without explicit approval.
+No package, tag, or registry release occurs without explicit approval. Release tags must use the `v<package-version>` form and point to the reviewed commit on `main`.
 
-For this ecosystem upgrade, use the approval-gated rollout order below:
+Run the coordinated checked-out ecosystem proof from this repository:
 
-1. Release `ui-style-kit-css@2.0.4` as the correctness hotfix from the merged hotfix content on `origin/main`. The 2.0.4 hotfix release line must pass `npm run release:verify` before any tag or publish step.
-2. Confirm the already published `interactive-surface-css@1.5.0` companion state engine remains available from npm.
-3. Release `ui-style-kit-css@2.1.0` after the hotfix is live.
-4. Release `layout-style-css@2.1.0` after UI Style Kit 2.1 is live and Layout replaces its temporary GitHub UI fixture with the registry package.
-5. Run the final all-three packed compatibility suite against the published packages.
+```bash
+npm run check:ecosystem:packs -- --layout-repo ../Layout-Style-CSS --interactive-repo ../Interactive-Surface-CSS --layout-docs-repo ../Layout-Style-CSS --interactive-docs-repo ../Interactive-Surface-CSS
+```
 
 ```bash
 npm publish
 ```
 
-`prepublishOnly` runs `npm run release:verify`, so a direct `npm publish` still has the full release gate. For GitHub releases, create or dispatch a release for the matching package tag, such as `v2.1.0`. The release workflows verify that `package.json`, `package-lock.json`, `CHANGELOG.md`, and generated dist banners are aligned before publishing.
+`prepublishOnly` runs `npm run release:verify`, so a direct `npm publish` still has the full release gate. For GitHub releases, push or dispatch the matching package tag, such as `v2.3.0`, only after the release PR is merged. The release workflows verify that `package.json`, `package-lock.json`, `CHANGELOG.md`, generated dist banners, and ecosystem pins are aligned before publishing.
 
 ## Versioning
 
@@ -42,4 +67,4 @@ npm run release:minor
 npm run release:major
 ```
 
-Use patch for fixes, minor for new themes/styles, and major for breaking public API changes. The 2.x release line is major because color-scheme authoring moved from per-UI `--<prefix>-*-rgb` blocks to shared `--usk-*-rgb` roles in `styles/theme-colors.css`.
+Use patch for compatible fixes, minor for new themes, presets, component capabilities, or browser-support contracts, and major for incompatible public API changes. The nine additional presets, ten additional schemes, universal component vocabulary, and compatibility contract make `2.3.0` a minor release.

package/docs/STYLE-GUIDE.md

@@ -2,22 +2,62 @@
 
 | UI style | Best for |
 |---|---|
-| Minimal SaaS | Dashboards, admin tools, SaaS apps, documentation, internal systems |
-| Bento UI | Landing pages, portfolio sections, feature pages, product showcases |
-| Maximalist / Playful | Creators, entertainment brands, events, bold client sites |
-| Bauhaus / Swiss Modern | Agencies, artists, editorial pages, design-forward brands |
-| Tactile / Skeuomorphic | Premium sites, distinctive client interfaces, control-panel metaphors |
-| Neumorphism | Soft dashboards, experimental UI, visual demos |
-| Retrofuturism | Futuristic product pages, portfolios, technology showcases |
-| Brutalism | Bold landing pages, anti-template websites, creative brands |
-| Cyberpunk | Security, gaming, encryption, developer demos, nightlife/tech branding |
-| Y2K | Nostalgic, playful, music/fashion/event sites |
-| Retro Glass | Futuristic premium apps, glass dashboards, hero sections |
-
-All styles share the same 10 color schemes through `styles/theme-colors.css`, so changing `data-theme` affects the active color scheme independently from the selected UI treatment.
+| Minimal SaaS | Dashboards, admin tools, SaaS apps |
+| Bento UI | Landing pages, feature sections, showcases |
+| Maximalist / Playful | Creators, entertainment, bold client sites |
+| Bauhaus / Swiss Modern | Agencies, editorial layouts, design-forward brands |
+| Skeuomorphic / Tactile | Premium tactile interfaces, control panels |
+| Neumorphism | Soft dashboards, experimental UI |
+| Retrofuturism | Futuristic portfolios and product pages |
+| Brutalism | Bold creative websites |
+| Cyberpunk | Security, gaming, encryption, tech demos |
+| Y2K | Nostalgic, playful, fashion/music/event sites |
+| Retro Glass | Futuristic glass dashboards and hero sections |
+| Editorial Luxe | Luxury brands, architecture, hospitality, premium editorial sites |
+| Organic Modern | Wellness, sustainability, hospitality, natural product brands |
+| Industrial Utility | Operations software, manufacturing, logistics, fleet and equipment systems |
+| Technical Blueprint | Engineering, architecture, technical documentation, scientific tools |
+| Art Deco | Luxury, hospitality, heritage brands, events and distinctive showcases |
+| Clay | Friendly SaaS, collaborative tools, education and approachable product sites |
+| Data Terminal | Operator consoles, telemetry, infrastructure, monitoring and developer tools |
+| Paper Editorial | News, magazines, journals, cultural sites and story-led publishing |
+| Neo-Noir | Cinematic portfolios, nightlife, premium creative studios and dramatic product sites |
+
+All styles share the same 20 color schemes through `styles/theme-colors.css`, so changing `data-theme` affects the active color scheme independently from the selected UI treatment.
 
 Use `data-mode="contrast"` for high-contrast variants and pair it with semantic HTML for best accessibility outcomes.
 
+## Preset identity and component roles
+
+UI presets own geometry, material, spacing, depth, and typographic character. Color schemes own semantic color roles. A preset should therefore remain recognizable when its `data-theme` changes, while every component continues to consume the active theme tokens instead of fixed artwork colors.
+
+| UI style | Repeated component identity |
+|---|---|
+| Minimal SaaS | Restrained single-corner folds and low-elevation outlines |
+| Bento UI | Stepped tile edges and compact block composition |
+| Maximalist / Playful | Skewed silhouettes, layered fills and pronounced shadows |
+| Bauhaus / Swiss Modern | Asymmetric primary geometry and hard-edged composition |
+| Skeuomorphic / Tactile | Chamfered physical keys, bevels and pressed depth |
+| Neumorphism | Softly clipped surfaces with raised and inset shadows |
+| Retrofuturism | Elongated console geometry and metallic rims |
+| Brutalism | Blunt cuts, thick borders and offset shadows |
+| Cyberpunk | Multi-notch technical polygons and luminous edges |
+| Y2K | Glossy capsule geometry and playful depth |
+| Retro Glass | Frosted angular tabs with inner highlights |
+| Editorial Luxe | Slim bookplates, hairlines and restrained framing |
+| Organic Modern | Asymmetric pebble and leaf contours with soft depth |
+| Industrial Utility | Octagonal hazard-control geometry and dense framing |
+| Technical Blueprint | Drafting-corner outlines and technical markings |
+| Art Deco | Symmetric chevrons and double-rule framing |
+| Clay | Inflated clipped pills and chunky soft shadows |
+| Data Terminal | Terminal brackets and luminous operator outlines |
+| Paper Editorial | Ticket or tab notches with inked offset edges |
+| Neo-Noir | Cinematic slants and high-contrast edge lighting |
+
+For filled service actions, compose `<prefix>-button`, `<prefix>-button-primary`, and `<prefix>-button-cut`. For framed callout actions, compose `<prefix>-button` and `<prefix>-button-outline-heavy`. These modifiers are independent; the library does not expose a `button-cta` class. Carry the same preset identity into service cards, media scrims, feature strips, callout bars, native actions, and dialogs rather than treating each specimen as isolated artwork.
+
+Preset-specific grids must size from their own container. Bento feature tiles, for example, use intrinsic columns and only introduce a feature span when their container can support it, preventing metric labels from collapsing into vertical text.
+
 ## Visual regression baseline
 
 The repository includes optional Playwright visual smoke checks:

package/docs/TOKENS.md

@@ -8,6 +8,46 @@ shared scheme channels -> prefixed aliases -> UI rules
 
 `styles/theme-colors.css` defines the active scheme and mode once as `--usk-*` RGB channels. Each UI style maps those shared channels to its public prefix, then component rules consume prefixed functional variables. `styles/native-elements.css` owns native HTML fallback selectors and consumes `--usk-native-*` tokens that each preset maps back to its own public variables.
 
+## Shared semantic token handshake
+
+The existing `[data-ui][data-theme][data-mode]` native-token root publishes 12 fully typed `--ui-*` values. UI Style Kit is the primary producer, but the names are intentionally package-neutral so a third-party theme can produce the same contract. Consumer libraries treat these values as optional fallbacks: a package-specific override wins first, then the shared semantic value, then the consumer's legacy token and literal default.
+
+| Shared token | CSS type | UI Style Kit source |
+|---|---|---|
+| `--ui-color-bg` | `<color>` | `rgb(var(--usk-bg-rgb))` |
+| `--ui-color-surface` | `<color>` | `var(--usk-native-surface-strong)` |
+| `--ui-color-text` | `<color>` | `var(--usk-native-text)` |
+| `--ui-color-muted` | `<color>` | `var(--usk-native-text-muted)` |
+| `--ui-color-primary` | `<color>` | `var(--usk-native-primary)` |
+| `--ui-color-on-primary` | `<color>` | `var(--usk-native-on-primary)` |
+| `--ui-color-border` | `<color>` | `var(--usk-native-border)` |
+| `--ui-radius-control` | `<length>` | `var(--usk-native-radius)` |
+| `--ui-shadow-control` | `<shadow-list>` | `var(--usk-native-shadow)` |
+| `--ui-focus-color` | `<color>` | `var(--usk-native-focus)` |
+| `--ui-motion-duration` | `<time>` | `var(--usk-motion-duration)` |
+| `--ui-motion-easing` | `<easing-function>` | `var(--usk-motion-easing)` |
+
+The two motion sources are scalar values (`140ms` and `cubic-bezier(0.2, 0, 0.2, 1)`), not values derived from a transition shorthand. That keeps them valid wherever a consumer needs one duration or one easing function.
+
+A third-party theme can provide the same handshake without importing UI Style Kit:
+
+```css
+[data-theme="partner"] {
+  --ui-color-surface: rgb(250 252 255);
+  --ui-color-text: rgb(18 28 45);
+  --ui-color-primary: rgb(20 92 180);
+  --ui-color-on-primary: white;
+  --ui-color-border: rgb(150 165 185);
+  --ui-radius-control: 0.75rem;
+  --ui-shadow-control: 0 8px 24px rgb(20 40 70 / 0.16);
+  --ui-focus-color: rgb(20 92 180);
+  --ui-motion-duration: 140ms;
+  --ui-motion-easing: cubic-bezier(0.2, 0, 0.2, 1);
+}
+```
+
+UI Style Kit entrypoints publish all 12 values. Standalone consumer packages must remain complete when none of them are present.
+
 ## Prefixes
 
 | UI style | Prefix |
@@ -23,6 +63,15 @@ shared scheme channels -> prefixed aliases -> UI rules
 | Cyberpunk | `cyber` |
 | Y2K | `y2k` |
 | Retro Glass | `rg` |
+| Editorial Luxe | `luxe` |
+| Organic Modern | `organic` |
+| Industrial Utility | `utility` |
+| Technical Blueprint | `blueprint` |
+| Art Deco | `deco` |
+| Clay | `clay` |
+| Data Terminal | `terminal` |
+| Paper Editorial | `paper` |
+| Neo-Noir | `noir` |
 
 ## Stable functional tokens
 
@@ -203,7 +252,7 @@ Loading indicators use theme variables by default:
 --<prefix>-spinner-accent
 ```
 
-The class utilities are `<prefix>-spinner`, `<prefix>-loading-spinner`, `<prefix>-spinner-sm`, and `<prefix>-spinner-lg`. Native buttons and prefixed buttons also render an inline spinner when `aria-busy="true"` is present.
+The class utilities are `<prefix>-spinner`, `<prefix>-loading-spinner`, `<prefix>-spinner-sm`, and `<prefix>-spinner-lg`. Each preset owns its loader silhouette, cadence, and depth while consuming only these active theme roles. Native buttons and prefixed buttons render the matching preset-owned indicator when `aria-busy="true"` is present.
 
 ## Interactive Surface bridge tokens