ui-style-kit-css 2.7.2 → 2.7.3

package/dist/visual/paper-editorial.css

@@ -1,5 +1,5 @@
 /*!
- * UI Style Kit CSS v2.7.2
+ * UI Style Kit CSS v2.7.3
  * CSS theme and UI style preset library.
  * License: MIT
  */

package/dist/visual/retro-glass.css

@@ -1,5 +1,5 @@
 /*!
- * UI Style Kit CSS v2.7.2
+ * UI Style Kit CSS v2.7.3
  * CSS theme and UI style preset library.
  * License: MIT
  */

package/dist/visual/retrofuturism.css

@@ -1,5 +1,5 @@
 /*!
- * UI Style Kit CSS v2.7.2
+ * UI Style Kit CSS v2.7.3
  * CSS theme and UI style preset library.
  * License: MIT
  */

package/dist/visual/tactile.css

@@ -1,5 +1,5 @@
 /*!
- * UI Style Kit CSS v2.7.2
+ * UI Style Kit CSS v2.7.3
  * CSS theme and UI style preset library.
  * License: MIT
  */

package/dist/visual/technical-blueprint.css

@@ -1,5 +1,5 @@
 /*!
- * UI Style Kit CSS v2.7.2
+ * UI Style Kit CSS v2.7.3
  * CSS theme and UI style preset library.
  * License: MIT
  */

package/dist/visual/y2k.css

@@ -1,5 +1,5 @@
 /*!
- * UI Style Kit CSS v2.7.2
+ * UI Style Kit CSS v2.7.3
  * CSS theme and UI style preset library.
  * License: MIT
  */

package/docs/ECOSYSTEM.md

@@ -14,11 +14,11 @@ Before a UI branch or pull request is expected to validate, verify the reviewed
 
 | Library | Current aligned version | Owns |
 |---|---:|---|
-| `ui-style-kit-css@2.7.2` | current UI version | visual identity, color themes, UI paint, native HTML styling, content wrapping, and bridge tokens |
+| `ui-style-kit-css@2.7.3` | current UI version | visual identity, color themes, UI paint, native HTML styling, content wrapping, and bridge tokens |
 | `interactive-surface-css@1.7.3` | compatible state release | interaction-state primitives, surface behavior, state layers, and input affordances |
 | `layout-style-css@3.2.3` | compatible structural release | structural wrappers, grids, sections, app shells, and layout recipes |
 
-The current combination is `ui-style-kit-css@2.7.2`, `interactive-surface-css@1.7.3`, and `layout-style-css@3.2.3`. UI Style Kit `2.7.2` is the current UI version. The companion versions are reviewed releases. Layout Style `3.2.3` 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`.
+The current combination is `ui-style-kit-css@2.7.3`, `interactive-surface-css@1.7.3`, and `layout-style-css@3.2.3`. UI Style Kit `2.7.3` is the current UI version. The companion versions are reviewed releases. Layout Style `3.2.3` 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
 

package/docs/PUBLISHING.md

@@ -1,14 +1,16 @@
 # Publishing Guide
 
-## 2.7.2 focused patch route
+## 2.7.3 focused patch route
 
-The owner authorized selected affected checks and prohibited CI/full suites for this repair. Follow [the 2.7.2 publication boundary](RELEASE-2.7.2.md) and the reviewed manual publish-select-patch.yml workflow. It requires signed exact source, the merged exact-head STE-Adam review, generated-asset reproduction, package admission and anonymous byte readback. It uses the existing npm publisher credential; no new secret or application deployment is included. Do not dispatch either legacy publisher for this patch. The 2.7.1 procedure below is historical and does not describe current 2.7.2 evidence.
+The owner authorized selected affected checks and prohibited CI/full suites for this repair. Follow [the 2.7.3 publication boundary](RELEASE-2.7.3.md) and the reviewed manual publish-select-patch.yml workflow. It requires signed exact source, the merged exact-head STE-Adam review, generated-asset reproduction, package admission and anonymous byte readback. It uses the existing npm publisher credential; no new secret or application deployment is included. Do not dispatch either legacy publisher for this patch. The 2.7.3 procedure below is historical and does not describe current 2.7.3 evidence.
 
-## 2.7.1 release workflow
+If run 42890785010 reports upload success but its immediate registry readback returns 404, use the same manual workflow with complete_only=true, source 56b1e3d50c4c1b17d2f28733cb590e0a742e2941 and approval PR 61. The continuation skips install/build/pack/publication, requires the original prepublication SHA-512 and producer SHA-1 plus exact public byte length, and completes only readback and release records. Preserve the original failed run; do not claim it passed or rerun its successful publication.
 
-This guide prepares version `2.7.1`. [Release preparation notes](RELEASE-2.7.1.md)
+## 2.7.3 release workflow
+
+This guide prepares version `2.7.3`. [Release preparation notes](RELEASE-2.7.3.md)
 record the current local scope and gates; existing visual-QA documents are historical
-evidence, not proof that subsequent edits passed browser validation. The 2.7.1
+evidence, not proof that subsequent edits passed browser validation. The 2.7.3
 changelog entry must carry the approved publication date before tagging.
 
 Update the tracked `wiki/` sources with the README and docs. Publishing those pages
@@ -17,9 +19,9 @@ documentation generator is configured in this package; reusable JavaScript helpe
 use JSDoc-compatible comments, and the checked-in build owns generated CSS, manifests,
 icons, README size measurements, and demo asset hashes.
 
-Prepare `ui-style-kit-css@2.7.1` on its release branch, open a pull request against `main`, and merge only after the fast automated gate is green and any requested manual demo review is complete. The aligned companion releases are `layout-style-css@3.2.3` and `interactive-surface-css@1.7.3`.
+Prepare `ui-style-kit-css@2.7.3` on its release branch, open a pull request against `main`, and merge only after the fast automated gate is green and any requested manual demo review is complete. The aligned companion releases are `layout-style-css@3.2.3` and `interactive-surface-css@1.7.3`.
 
-Do not push `v2.7.1` 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.
+Do not push `v2.7.3` 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.
 
 Release Version Alignment owns the fast automated release gate: lint, build, unit checks, the tagged Chromium release-smoke Playwright suite, and packed ecosystem preflight with `--skip-clean-install`. The visual-baseline suite, full UI matrix, and clean-install ecosystem matrix are manual escalation tools, not default push or publish blockers. The protected npm workflow intentionally does not rerun browser gates; it revalidates the immutable tag, package contracts, browser-free compatibility checks, companion commit reachability, the explicit release preflight with `--skip-clean-install`, npm token presence, npm owner authorization, and registry state before publishing.
 
@@ -80,7 +82,7 @@ npm run check:ecosystem:packs -- --layout-repo ../Layout-Style-CSS --interactive
 npm publish
 ```
 
-`prepublishOnly` runs `npm run release:verify`, so a direct `npm publish` still has the default fast release gate. For GitHub releases, push or dispatch the matching package tag, such as `v2.7.1`, 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. Dispatch the protected npm workflow from the current `main` workflow file when recovering publication for a release that has already passed Release Version Alignment.
+`prepublishOnly` runs `npm run release:verify`, so a direct `npm publish` still has the default fast release gate. For GitHub releases, push or dispatch the matching package tag, such as `v2.7.3`, 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. Dispatch the protected npm workflow from the current `main` workflow file when recovering publication for a release that has already passed Release Version Alignment.
 
 The repository `NPM_TOKEN` secret must authenticate to npm as a user that appears in `npm owner ls ui-style-kit-css`. If the token belongs to another npm account or lacks package publish rights, npm may report a misleading registry `E404` at publish time.
 
@@ -92,4 +94,4 @@ npm run release:minor
 npm run release:major
 ```
 
-Use patch for compatible fixes, minor for new themes, presets, component capabilities, or browser-support contracts, and major for incompatible public API changes. Version `2.7.1` is a patch release because it repairs interaction paint and contrast while retaining the preset and semantic component APIs. Future feature versioning continues to follow this policy.
+Use patch for compatible fixes, minor for new themes, presets, component capabilities, or browser-support contracts, and major for incompatible public API changes. Version `2.7.3` is a patch release because it repairs interaction paint and contrast while retaining the preset and semantic component APIs. Future feature versioning continues to follow this policy.

package/docs/RELEASE-2.7.3.md

@@ -0,0 +1,9 @@
+# UI Style Kit CSS 2.7.3
+
+The optional `component-composition.css` entrypoint preserves the existing message foreground in native paragraphs and lists within `.usk-alert__body`. STE-USK-React already imports this composition entrypoint. Palette values, raw preset declarations, unrelated prose and control behavior are unchanged.
+
+The focused browser regression exercises both semantic alert namespaces with the composition entrypoint, the default visual bundle, its minified form and the focused Bento bundle, across manifest palettes and all three modes. SYS's original intake warning measured 4.15:1. Actual published-package consumer qualification remains separate.
+
+The first native-stylesheet placement was rejected by the existing raw-preset and alias-isolation guards. The correction is confined to component composition; the raw-preset and alias-isolation guards stay in place. Declaration constants now bind the byte-identical published 2.7.2 visual/default bundles; the preceding 2.7.1 constants were stale. Current-version documentation, metadata and assertions are aligned with 2.7.3 while immutable companion revisions and historical release notes remain intact.
+
+The existing release verification and publication controls still apply. Source checks do not establish npm publication or SYS deployment.

package/manifest.json

@@ -5,7 +5,7 @@
     "breakingChange": "increment-schemaVersion-before-removing-or-renaming-fields"
   },
   "name": "ui-style-kit-css",
-  "version": "2.7.2",
+  "version": "2.7.3",
   "cascadeLayers": [
     "ui-style-kit.theme_colors",
     "ui-style-kit.native_elements",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ui-style-kit-css",
-  "version": "2.7.2",
+  "version": "2.7.3",
   "description": "CSS theme and UI style preset library for accessible websites, dashboards, admin interfaces, and client-facing pages.",
   "style": "dist/ui-style-kit.css",
   "main": "dist/ui-style-kit.css",

package/styles/component-composition.css

@@ -890,3 +890,10 @@
   }
 }
 }
+
+/** Native prose and lists retain their owning semantic message body foreground. */
+@layer ui-style-kit.clean_defaults {
+[data-ui][data-mode] .usk-alert__body :where(p, ul, ol, menu) {
+  color: inherit;
+}
+}