@poodle64/ui 2026.9.15 → 2026.9.16

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

@@ -90,7 +90,7 @@
 	import PanelLeftClose from '@lucide/svelte/icons/panel-left-close';
 	import PanelLeftOpen from '@lucide/svelte/icons/panel-left-open';
 	import AppNav from './app-nav.svelte';
-	import { activeNavLabel, toItems, type NavSource } from './types.js';
+	import { activeNavLabel, matchesPrefix, toItems, type NavSource } from './types.js';
 	import { provideShellControls, type ShellControlsSlot } from './controls.js';
 	import { cn } from '../../../utils.js';
 
@@ -233,9 +233,19 @@
 
 	const hasNav = $derived(toItems(nav).length > 0);
 
+	// The foot's Settings row owns its subtree, matched exactly as a nav `href`
+	// is, so the row's own current state and the bar's label cannot disagree.
+	const atSettings = $derived(
+		!!settingsHref && !!currentPath && matchesPrefix(currentPath, settingsHref)
+	);
+
 	// Where the user is, in words: the rail is icons when collapsed and a closed
-	// drawer on a phone, so the bar names the section.
-	const location = $derived(activeNavLabel(nav, currentPath));
+	// drawer on a phone, so the bar names the section. Settings is a section like
+	// any other and is named the same way — by the foot row's own label, since
+	// the shell knows nothing of the pages inside it.
+	const location = $derived(
+		activeNavLabel(nav, currentPath) ?? (atSettings ? settingsLabel : undefined)
+	);
 
 	// The page's scope controls, registered by `<ShellControls>` from the route.
 	const controls: ShellControlsSlot = $state({ content: null });
@@ -674,7 +684,7 @@
 					<a
 						href={settingsHref}
 						class="ds-nav-item"
-						aria-current={currentPath?.startsWith(settingsHref) ? 'page' : undefined}
+						aria-current={atSettings ? 'page' : undefined}
 						onclick={() => (mobileNavOpen = false)}
 					>
 						<Settings class="ds-nav-icon size-[1.125rem] flex-none" aria-hidden="true" />

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

@@ -129,6 +129,8 @@ export declare function navChildren(item: NavItem): readonly NavChildItem[];
  * is looking for.
  */
 export declare function toItems(nav: NavSource | undefined): NavItem[];
+/** Prefix-match `path` against `prefix`, without running past a path segment. */
+export declare function matchesPrefix(path: string, prefix: string): boolean;
 /**
  * Whether `item` is the current page.
  *

package/dist/components/ui/app-shell/types.js

@@ -74,7 +74,7 @@ export function toItems(nav) {
     return items;
 }
 /** Prefix-match `path` against `prefix`, without running past a path segment. */
-function matchesPrefix(path, prefix) {
+export function matchesPrefix(path, prefix) {
     return path === prefix || path.startsWith(prefix + '/');
 }
 /**

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@poodle64/ui",
-	"version": "2026.9.15",
+	"version": "2026.9.16",
 	"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.15",
+		"version": "2026.9.16",
 		"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.15`. 57 components, 15 situations.
+Generated from `@poodle64/ui@2026.9.16`. 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.