ui-style-kit-css 2.7.3 → 2.7.4

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.
@@ -1,5 +1,5 @@
1
1
  /*!
2
- * UI Style Kit CSS v2.7.3
2
+ * UI Style Kit CSS v2.7.4
3
3
  * CSS theme and UI style preset library.
4
4
  * License: MIT
5
5
  */
@@ -219,7 +219,8 @@
219
219
  --usk-success-text-rgb: 255 255 255;
220
220
  --usk-warning-text-rgb: 255 255 255;
221
221
  --usk-danger-text-rgb: 255 255 255;
222
- --usk-focus-rgb: 156 186 82;
222
+ /** Dark green focus ink remains distinct on every light neutral surface. */
223
+ --usk-focus-rgb: 47 97 43;
223
224
  }
224
225
 
225
226
  :where([data-ui][data-theme="forest-moss"][data-mode="dark"]) {
@@ -1,5 +1,5 @@
1
1
  /*!
2
- * UI Style Kit CSS v2.7.3
2
+ * UI Style Kit CSS v2.7.4
3
3
  * CSS theme and UI style preset library.
4
4
  * License: MIT
5
5
  */
@@ -219,7 +219,8 @@
219
219
  --usk-success-text-rgb: 255 255 255;
220
220
  --usk-warning-text-rgb: 255 255 255;
221
221
  --usk-danger-text-rgb: 255 255 255;
222
- --usk-focus-rgb: 156 186 82;
222
+ /** Dark green focus ink remains distinct on every light neutral surface. */
223
+ --usk-focus-rgb: 47 97 43;
223
224
  }
224
225
 
225
226
  :where([data-ui][data-theme="forest-moss"][data-mode="dark"]) {
@@ -1,5 +1,5 @@
1
1
  /*!
2
- * UI Style Kit CSS v2.7.3
2
+ * UI Style Kit CSS v2.7.4
3
3
  * CSS theme and UI style preset library.
4
4
  * License: MIT
5
5
  */
@@ -219,7 +219,8 @@
219
219
  --usk-success-text-rgb: 255 255 255;
220
220
  --usk-warning-text-rgb: 255 255 255;
221
221
  --usk-danger-text-rgb: 255 255 255;
222
- --usk-focus-rgb: 156 186 82;
222
+ /** Dark green focus ink remains distinct on every light neutral surface. */
223
+ --usk-focus-rgb: 47 97 43;
223
224
  }
224
225
 
225
226
  :where([data-ui][data-theme="forest-moss"][data-mode="dark"]) {
@@ -1,5 +1,5 @@
1
1
  /*!
2
- * UI Style Kit CSS v2.7.3
2
+ * UI Style Kit CSS v2.7.4
3
3
  * CSS theme and UI style preset library.
4
4
  * License: MIT
5
5
  */
@@ -219,7 +219,8 @@
219
219
  --usk-success-text-rgb: 255 255 255;
220
220
  --usk-warning-text-rgb: 255 255 255;
221
221
  --usk-danger-text-rgb: 255 255 255;
222
- --usk-focus-rgb: 156 186 82;
222
+ /** Dark green focus ink remains distinct on every light neutral surface. */
223
+ --usk-focus-rgb: 47 97 43;
223
224
  }
224
225
 
225
226
  :where([data-ui][data-theme="forest-moss"][data-mode="dark"]) {
@@ -1,5 +1,5 @@
1
1
  /*!
2
- * UI Style Kit CSS v2.7.3
2
+ * UI Style Kit CSS v2.7.4
3
3
  * CSS theme and UI style preset library.
4
4
  * License: MIT
5
5
  */
@@ -219,7 +219,8 @@
219
219
  --usk-success-text-rgb: 255 255 255;
220
220
  --usk-warning-text-rgb: 255 255 255;
221
221
  --usk-danger-text-rgb: 255 255 255;
222
- --usk-focus-rgb: 156 186 82;
222
+ /** Dark green focus ink remains distinct on every light neutral surface. */
223
+ --usk-focus-rgb: 47 97 43;
223
224
  }
224
225
 
225
226
  :where([data-ui][data-theme="forest-moss"][data-mode="dark"]) {
@@ -1,5 +1,5 @@
1
1
  /*!
2
- * UI Style Kit CSS v2.7.3
2
+ * UI Style Kit CSS v2.7.4
3
3
  * CSS theme and UI style preset library.
4
4
  * License: MIT
5
5
  */
@@ -219,7 +219,8 @@
219
219
  --usk-success-text-rgb: 255 255 255;
220
220
  --usk-warning-text-rgb: 255 255 255;
221
221
  --usk-danger-text-rgb: 255 255 255;
222
- --usk-focus-rgb: 156 186 82;
222
+ /** Dark green focus ink remains distinct on every light neutral surface. */
223
+ --usk-focus-rgb: 47 97 43;
223
224
  }
224
225
 
225
226
  :where([data-ui][data-theme="forest-moss"][data-mode="dark"]) {
package/docs/ECOSYSTEM.md CHANGED
@@ -14,11 +14,11 @@ Before a UI branch or pull request is expected to validate, verify the reviewed
14
14
 
15
15
  | Library | Current aligned version | Owns |
16
16
  |---|---:|---|
17
- | `ui-style-kit-css@2.7.3` | current UI version | visual identity, color themes, UI paint, native HTML styling, content wrapping, and bridge tokens |
17
+ | `ui-style-kit-css@2.7.4` | current UI version | visual identity, color themes, UI paint, native HTML styling, content wrapping, and bridge tokens |
18
18
  | `interactive-surface-css@1.7.3` | compatible state release | interaction-state primitives, surface behavior, state layers, and input affordances |
19
19
  | `layout-style-css@3.2.3` | compatible structural release | structural wrappers, grids, sections, app shells, and layout recipes |
20
20
 
21
- 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`.
21
+ The current combination is `ui-style-kit-css@2.7.4`, `interactive-surface-css@1.7.3`, and `layout-style-css@3.2.3`. UI Style Kit `2.7.4` 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`.
22
22
 
23
23
  ## Layout-to-visual pairing matrix
24
24
 
@@ -1,16 +1,14 @@
1
- # Publishing Guide
1
+ # Publishing
2
2
 
3
- ## 2.7.3 focused patch route
3
+ ## 2.7.4 accessibility patch
4
4
 
5
- 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.
5
+ Use the existing reviewed source, signed tag and protected npm release workflow for this patch. The historical `publish-select-patch.yml` controller is restricted to 2.7.2 and must not be dispatched for 2.7.4. Complete local release verification, align generated artifacts and inspect the exact source before opening the release PR. Review, package-owner credentials, immutable identities and anonymous public-byte readback remain required. SYS may consume only the resulting published artifact. See [the 2.7.4 release notes](RELEASE-2.7.4.md).
6
6
 
7
- 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.
7
+ ## 2.7.4 release workflow
8
8
 
9
- ## 2.7.3 release workflow
10
-
11
- This guide prepares version `2.7.3`. [Release preparation notes](RELEASE-2.7.3.md)
9
+ This guide prepares version `2.7.4`. [Release preparation notes](RELEASE-2.7.4.md)
12
10
  record the current local scope and gates; existing visual-QA documents are historical
13
- evidence, not proof that subsequent edits passed browser validation. The 2.7.3
11
+ evidence, not proof that subsequent edits passed browser validation. The 2.7.4
14
12
  changelog entry must carry the approved publication date before tagging.
15
13
 
16
14
  Update the tracked `wiki/` sources with the README and docs. Publishing those pages
@@ -19,9 +17,9 @@ documentation generator is configured in this package; reusable JavaScript helpe
19
17
  use JSDoc-compatible comments, and the checked-in build owns generated CSS, manifests,
20
18
  icons, README size measurements, and demo asset hashes.
21
19
 
22
- 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`.
20
+ Prepare `ui-style-kit-css@2.7.4` 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`.
23
21
 
24
- 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.
22
+ Do not push `v2.7.4` 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.
25
23
 
26
24
  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.
27
25
 
@@ -82,7 +80,7 @@ npm run check:ecosystem:packs -- --layout-repo ../Layout-Style-CSS --interactive
82
80
  npm publish
83
81
  ```
84
82
 
85
- `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.
83
+ `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.4`, 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.
86
84
 
87
85
  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.
88
86
 
@@ -94,4 +92,4 @@ npm run release:minor
94
92
  npm run release:major
95
93
  ```
96
94
 
97
- 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.
95
+ 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.4` 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.
@@ -0,0 +1,5 @@
1
+ # UI Style Kit CSS 2.7.4
2
+
3
+ This accessibility patch corrects three shared defects reproduced by SYS browser acceptance. Navigable semantic breadcrumbs have 44px minimum targets and own their compound spacing; current-page labels retain their semantics and ordinary lists retain native spacing. Forest Moss light-mode focus uses the palette's existing dark green link ink, correcting the observed 1.78-2.20 contrast ratios on neutral surfaces. Nested native `small` metadata inherits its semantic alert body foreground through the optional component-composition entrypoint.
4
+
5
+ The focused geometry regression covers every manifest preset and both semantic namespaces. Separate focused keyboard-focus and alert-metadata regressions fail before their respective corrections and pass afterward. Alert metadata also covers the default visual bundle, its minified distribution and the focused Minimal SaaS/Bento exports across palettes and modes. Normal release verification remains required. Published artifact, SYS consumer and deployment acceptance are separate delivery gates.
package/manifest.json CHANGED
@@ -5,7 +5,7 @@
5
5
  "breakingChange": "increment-schemaVersion-before-removing-or-renaming-fields"
6
6
  },
7
7
  "name": "ui-style-kit-css",
8
- "version": "2.7.3",
8
+ "version": "2.7.4",
9
9
  "cascadeLayers": [
10
10
  "ui-style-kit.theme_colors",
11
11
  "ui-style-kit.native_elements",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "ui-style-kit-css",
3
- "version": "2.7.3",
3
+ "version": "2.7.4",
4
4
  "description": "CSS theme and UI style preset library for accessible websites, dashboards, admin interfaces, and client-facing pages.",
5
5
  "style": "dist/ui-style-kit.css",
6
6
  "main": "dist/ui-style-kit.css",
@@ -6,6 +6,22 @@
6
6
  ========================================================= */
7
7
 
8
8
  @layer ui-style-kit.clean_defaults {
9
+ /** Breadcrumb compounds own their spacing instead of accumulating native element insets. */
10
+ [data-ui][data-mode] :is(.usk-breadcrumb, .ui-breadcrumb, .usk-breadcrumb-list, .ui-breadcrumb-list, .usk-breadcrumb-item, .ui-breadcrumb-item) {
11
+ margin: 0;
12
+ padding: 0;
13
+ }
14
+
15
+ /** Navigable breadcrumb links expose touch targets without enlarging the current-page label. */
16
+ [data-ui][data-mode] :is(.usk-breadcrumb-link, .ui-breadcrumb-link):any-link {
17
+ display: inline-flex;
18
+ align-items: center;
19
+ box-sizing: border-box;
20
+ min-inline-size: 44px;
21
+ min-block-size: 44px;
22
+ margin: 0;
23
+ }
24
+
9
25
  /** Long chip content shrinks and wraps before it can displace the separate remove action. */
10
26
  [data-ui][data-mode] .usk-chip > .usk-chip__label {
11
27
  min-inline-size: 0;
@@ -891,9 +907,9 @@
891
907
  }
892
908
  }
893
909
 
894
- /** Native prose and lists retain their owning semantic message body foreground. */
910
+ /** Native prose, lists and small metadata retain their owning semantic message foreground. */
895
911
  @layer ui-style-kit.clean_defaults {
896
- [data-ui][data-mode] .usk-alert__body :where(p, ul, ol, menu) {
912
+ [data-ui][data-mode] .usk-alert__body :where(p, ul, ol, menu, small) {
897
913
  color: inherit;
898
914
  }
899
915
  }
@@ -210,7 +210,8 @@
210
210
  --usk-success-text-rgb: 255 255 255;
211
211
  --usk-warning-text-rgb: 255 255 255;
212
212
  --usk-danger-text-rgb: 255 255 255;
213
- --usk-focus-rgb: 156 186 82;
213
+ /** Dark green focus ink remains distinct on every light neutral surface. */
214
+ --usk-focus-rgb: 47 97 43;
214
215
  }
215
216
 
216
217
  :where([data-ui][data-theme="forest-moss"][data-mode="dark"]) {