@poodle64/ui 2026.9.10 → 2026.9.11

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 (4) hide show
  1. package/dist/styles.css +7 -1
  2. package/package.json +1 -1
  3. package/registry/component-map.json +1 -1
  4. package/registry/component-map.md +1 -1
package/dist/styles.css CHANGED
@@ -784,7 +784,13 @@
784
784
  margin-top: 0.125rem;
785
785
  margin-left: 1.1875rem;
786
786
  padding-left: 0.625rem;
787
- border-left: 1px solid var(--border);
787
+ /* Derived from the nav's OWN ink, not `--border`. The rail is chrome the
788
+ app may brand, and a page-surface border token cannot follow it there:
789
+ on a branded rail the grey lands at 1.54:1 and reads as a dead scratch
790
+ down the colour. At 50% of the chrome's ink the guide measures 3.10:1
791
+ on that same rail — over the 3:1 floor it owes as a real affordance,
792
+ and still a step quieter than the child labels it organises. */
793
+ border-left: 1px solid color-mix(in oklch, var(--ds-nav-ink) 50%, transparent);
788
794
  }
789
795
 
790
796
  /* `hidden` is an attribute the UA stylesheet honours at the weakest possible
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@poodle64/ui",
3
- "version": "2026.9.10",
3
+ "version": "2026.9.11",
4
4
  "description": "Household shared component layer: shadcn-svelte primitives (bits-ui) plus the composed page chrome every app builds its routes from, restyled by each app's @poodle64/design-tokens alias layer. One fix reaches every app.",
5
5
  "type": "module",
6
6
  "license": "MIT",
package/registry/component-map.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "meta": {
3
3
  "package": "@poodle64/ui",
4
- "version": "2026.9.10",
4
+ "version": "2026.9.11",
5
5
  "generatedBy": "scripts/generate-registry.mjs",
6
6
  "source": "scripts/situations.json + package source (DO NOT EDIT the outputs by hand)",
7
7
  "componentCount": 57,
package/registry/component-map.md CHANGED
@@ -1,7 +1,7 @@
1
1
  # @poodle64/ui — situation → component map
2
2
 
3
3
  <!-- GENERATED by scripts/generate-registry.mjs from scripts/situations.json + package source. DO NOT EDIT. -->
4
- Generated from `@poodle64/ui@2026.9.10`. 57 components, 15 situations.
4
+ Generated from `@poodle64/ui@2026.9.11`. 57 components, 15 situations.
5
5
 
6
6
  **Read this before writing a `<div>`.** Find the SITUATION you are in below, then compose the component named for it — do not hand-build it from raw `Card` or utility classes. Import is `import { Name } from '<import path>'`. Props marked `?` are optional. This map is the retrieval step the [`frontend-design` skill] makes mandatory; the [CHI 2026 study] measured composing-from-a-registry at 95% design-system compliance against 71% for writing the CSS from a prose style guide.
7
7