@poodle64/ui 2026.9.13 → 2026.9.15

package/dist/components/ui/app-shell/app-shell.svelte

@@ -110,8 +110,6 @@
 		identity,
 		settingsHref,
 		settingsLabel = 'Settings',
-		version,
-		versionHref,
 		onSearch,
 		searchLabel = 'Search…',
 		searchShortcut = '⌘K',
@@ -176,16 +174,14 @@
 		identity?: Snippet;
 		/** Where the Settings row at the rail's foot links. Absent renders no row.
 		 *  Settings sits at the foot because configuring the app is not navigating
-		 *  it, and the split reads without a label. */
+		 *  it, and the split reads without a label.
+		 *
+		 *  The app's version does NOT live beside it. A build string earns rail
+		 *  space only if it saves a trip, and it does not: Settings is on screen
+		 *  at every moment and its About section is one click from here, so the
+		 *  line was permanent furniture duplicating the thing directly above it. */
 		settingsHref?: string;
 		settingsLabel?: string;
-		/** The build this person is looking at, e.g. `2026.9.3 · b032a3a`. Rendered
-		 *  as one muted line under the Settings row: no icon, no hover, not a nav
-		 *  row. It earns its place by answering "what am I running" the moment
-		 *  someone reports a bug, and it links into Settings where the full
-		 *  About section lives. */
-		version?: string;
-		versionHref?: string;
 		/** Provide to render the search affordance. Usually opens a CommandPalette. */
 		onSearch?: () => void;
 		searchLabel?: string;
@@ -673,26 +669,19 @@
 				The version is not a row: no icon, no tile, no hover, one muted
 				line, so it reads as metadata and never competes for a click.
 			-->
-			{#if settingsHref || version}
-				<div class="ds-shell-rail-foot mt-auto" class:sr-only={railCollapsed && !mobileNavOpen}>
-					{#if settingsHref}
-						<a
-							href={settingsHref}
-							class="ds-nav-item"
-							aria-current={currentPath?.startsWith(settingsHref) ? 'page' : undefined}
-							onclick={() => (mobileNavOpen = false)}
-						>
-							<Settings class="ds-nav-icon size-[1.125rem] flex-none" aria-hidden="true" />
-							<span class="truncate">{settingsLabel}</span>
-						</a>
-					{/if}
-					{#if version}
-						{#if versionHref}
-							<a href={versionHref} class="ds-shell-version">{version}</a>
-						{:else}
-							<p class="ds-shell-version">{version}</p>
-						{/if}
-					{/if}
+			{#if settingsHref}
+				<div class="ds-shell-rail-foot mt-auto">
+					<a
+						href={settingsHref}
+						class="ds-nav-item"
+						aria-current={currentPath?.startsWith(settingsHref) ? 'page' : undefined}
+						onclick={() => (mobileNavOpen = false)}
+					>
+						<Settings class="ds-nav-icon size-[1.125rem] flex-none" aria-hidden="true" />
+						<span class={railCollapsed && !mobileNavOpen ? 'sr-only' : 'truncate'}>
+							{settingsLabel}
+						</span>
+					</a>
 				</div>
 			{/if}
 			{#if collapsible && !railCollapsed && !mobileNavOpen}

package/dist/components/ui/app-shell/app-shell.svelte.d.ts

@@ -133,16 +133,14 @@ type $$ComponentProps = {
     identity?: Snippet;
     /** Where the Settings row at the rail's foot links. Absent renders no row.
      *  Settings sits at the foot because configuring the app is not navigating
-     *  it, and the split reads without a label. */
+     *  it, and the split reads without a label.
+     *
+     *  The app's version does NOT live beside it. A build string earns rail
+     *  space only if it saves a trip, and it does not: Settings is on screen
+     *  at every moment and its About section is one click from here, so the
+     *  line was permanent furniture duplicating the thing directly above it. */
     settingsHref?: string;
     settingsLabel?: string;
-    /** The build this person is looking at, e.g. `2026.9.3 · b032a3a`. Rendered
-     *  as one muted line under the Settings row: no icon, no hover, not a nav
-     *  row. It earns its place by answering "what am I running" the moment
-     *  someone reports a bug, and it links into Settings where the full
-     *  About section lives. */
-    version?: string;
-    versionHref?: string;
     /** Provide to render the search affordance. Usually opens a CommandPalette. */
     onSearch?: () => void;
     searchLabel?: string;

package/dist/styles.css

@@ -777,6 +777,13 @@
 	   lands its label at 2.5rem, exactly under the parent's. The border is a real
 	   affordance at fifteen rows, not decoration: it is what makes the run
 	   scannable as one section. */
+	/* The disclosed rows carry no guide rule. Indentation and the children's own
+	   icons already read as one group, and a line down the side is a second
+	   signal for a grouping that was never ambiguous. The indent is still
+	   measured against the parent's geometry rather than picked: `.ds-nav-item`
+	   pads 0.625rem and the icon is 1.125rem, so 1.1875rem plus 0.625rem here
+	   plus the child's own 0.625rem lands its label at 2.5rem, exactly under the
+	   parent's. */
 	.ds-nav-children {
 		display: flex;
 		flex-direction: column;
@@ -784,13 +791,6 @@
 		margin-top: 0.125rem;
 		margin-left: 1.1875rem;
 		padding-left: 0.625rem;
-		/* Derived from the nav's OWN ink, not `--border`. The rail is chrome the
-		   app may brand, and a page-surface border token cannot follow it there:
-		   on a branded rail the grey lands at 1.54:1 and reads as a dead scratch
-		   down the colour. At 50% of the chrome's ink the guide measures 3.10:1
-		   on that same rail — over the 3:1 floor it owes as a real affordance,
-		   and still a step quieter than the child labels it organises. */
-		border-left: 1px solid color-mix(in oklch, var(--ds-nav-ink) 50%, transparent);
 	}
 
 	/* The rail's foot: where you configure the app, and which build you are on.
@@ -803,7 +803,7 @@
 	.ds-shell-rail-foot {
 		display: flex;
 		flex-direction: column;
-		padding-block: 0.375rem 0.75rem;
+		padding-block: 0.375rem 0.5rem;
 		padding-inline: 0.75rem;
 		border-top: 1px solid color-mix(in oklch, var(--ds-nav-ink) 22%, transparent);
 	}
@@ -811,24 +811,6 @@
 	/* Metadata, not a row. No icon, no tile, no hover: it answers "what am I
 	   running" when someone reports a bug and otherwise stays out of the way.
 	   `tabular-nums` so a version does not re-flow as the digits change. */
-	/* Below Settings, on the rail's bottom edge, so the rail OPENS with the app's
-	   name and CLOSES with its build — identity at both ends, the action between
-	   them. Above Settings would put metadata before the thing people click.
-	   `padding-inline` matches `.ds-nav-item`'s own, so it starts on the same
-	   vertical as the icons rather than the labels: it is a line of metadata,
-	   not a row missing its icon. */
-	.ds-shell-version {
-		margin: 0;
-		padding: 0.25rem 0.625rem 0;
-		color: var(--ds-nav-ink-muted);
-		font-size: var(--ds-text-2xs);
-		font-variant-numeric: tabular-nums;
-		text-decoration: none;
-	}
-
-	a.ds-shell-version:hover {
-		color: var(--ds-nav-ink);
-	}
 
 	/* `hidden` is an attribute the UA stylesheet honours at the weakest possible
 	   specificity, so the `display: flex` above beats it and a closed group would

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@poodle64/ui",
-	"version": "2026.9.13",
+	"version": "2026.9.15",
 	"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.",
 	"type": "module",
 	"license": "MIT",

package/registry/component-map.json

@@ -1,7 +1,7 @@
 {
 	"meta": {
 		"package": "@poodle64/ui",
-		"version": "2026.9.13",
+		"version": "2026.9.15",
 		"generatedBy": "scripts/generate-registry.mjs",
 		"source": "scripts/situations.json + package source (DO NOT EDIT the outputs by hand)",
 		"componentCount": 57,

package/registry/component-map.md

@@ -1,7 +1,7 @@
 # @poodle64/ui — situation → component map
 
 <!-- GENERATED by scripts/generate-registry.mjs from scripts/situations.json + package source. DO NOT EDIT. -->
-Generated from `@poodle64/ui@2026.9.13`. 57 components, 15 situations.
+Generated from `@poodle64/ui@2026.9.15`. 57 components, 15 situations.
 
 **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.