@poodle64/ui 2026.9.5 → 2026.9.6

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

@@ -30,7 +30,14 @@
 	 * instead (operator ruling, 07/09/2026, master-project#291's org-of-one
 	 * case). Wire it whenever the app has a members route, whether or not it
 	 * also renders a switcher.
+	 *
+	 * `links` is the escape valve for everything the fixed entries have no room
+	 * for — an Admin route, a support link — as a LIST, so every app's extra
+	 * destinations render as the same row. Without it an app puts its own
+	 * destination in AppShell's `actions` slot as an icon button (cadmus did,
+	 * twice), and two apps do it two ways in the same bar.
 	 */
+	import type { Component } from 'svelte';
 	import { toggleMode } from 'mode-watcher';
 	import * as DropdownMenu from '../dropdown-menu/index.js';
 	import * as Avatar from '../avatar/index.js';
@@ -43,7 +50,8 @@
 		onSignOut,
 		onAccountSettings,
 		onManageMembers,
-		onSwitchTheme
+		onSwitchTheme,
+		links = []
 	}: {
 		user: { username: string; display_name: string | null; email: string | null };
 		/** The active workspace's name. Omit while none is chosen yet — the block hides rather than rendering empty. */
@@ -70,6 +78,22 @@
 		onManageMembers?: () => void;
 		/** Override the theme action. Defaults to mode-watcher's toggleMode, matching AppShell. */
 		onSwitchTheme?: () => void;
+		/**
+		 * App destinations the fixed entries have no room for, rendered in their
+		 * own group.
+		 *
+		 * A list of items, never a snippet: a snippet lets each app invent its own
+		 * row shape, and two apps inventing two shapes in the same top bar is the
+		 * drift this package exists to end. Cadmus is the measured case — its
+		 * Admin entry had nowhere to go and became an icon button in AppShell's
+		 * `actions` slot, and a second one (a quiet support link) was about to
+		 * follow it there.
+		 *
+		 * No `href`: the callback shape matches every other action on this
+		 * component, and a consumer routes with its own `goto`. The icon is
+		 * optional — a label-only row stays aligned with any iconed row beside it.
+		 */
+		links?: { label: string; icon?: Component<{ class?: string }>; onSelect: () => void }[];
 	} = $props();
 
 	const shown = $derived(user.display_name ?? user.username);
@@ -110,6 +134,11 @@
 		user.display_name ? initialsOf(user.display_name) : handleInitials(user.username)
 	);
 
+	// Spacers only where the group actually has an icon to align to: a group of
+	// label-only rows sits flush with the fixed entries below it, exactly as it
+	// would if this prop had never existed.
+	const linksHaveIcons = $derived(links.some((l) => l.icon));
+
 	function switchTheme() {
 		if (onSwitchTheme) onSwitchTheme();
 		else toggleMode();
@@ -177,6 +206,26 @@
 				<DropdownMenu.Item onSelect={onManageMembers}>Members</DropdownMenu.Item>
 			{/if}
 		{/if}
+		{#if links.length}
+			<DropdownMenu.Separator />
+			<DropdownMenu.Group>
+				<!-- Keyed by position, not by label: nothing in the type makes a label
+				     unique, and two apps' configs colliding on one would be a
+				     duplicate-key crash rather than a duplicated row. This list is
+				     app configuration, not data that reorders. -->
+				{#each links as link, i (i)}
+					{@const Icon = link.icon}
+					<DropdownMenu.Item onSelect={link.onSelect}>
+						{#if Icon}
+							<Icon class="size-4" />
+						{:else if linksHaveIcons}
+							<span class="size-4 flex-none" aria-hidden="true"></span>
+						{/if}
+						{link.label}
+					</DropdownMenu.Item>
+				{/each}
+			</DropdownMenu.Group>
+		{/if}
 		<DropdownMenu.Separator />
 		<DropdownMenu.Item onSelect={switchTheme}>Switch theme</DropdownMenu.Item>
 		<DropdownMenu.Item onSelect={onAccountSettings}>Account settings</DropdownMenu.Item>

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

@@ -1,3 +1,42 @@
+/**
+     * The signed-in user surface for AppShell's `identity` slot.
+     *
+     * Graduated from the shell lab (`packages/console/src/routes/lab/+page.svelte`,
+     * the `identity === 'avatar'` shape) — operator ruling 04/09/2026: avatar
+     * only at rest, no name, no chevron, and no prop reintroduces a variant.
+     * Opening it answers who is signed in, which workspace they act in, and the
+     * ways out — identity first, because a menu that opens on a list of actions
+     * makes you infer who you are from the avatar you just clicked.
+     *
+     * Prop names match the stamped template's auth store
+     * (`frontend/src/lib/auth.svelte.ts` — `User`, `Membership`) exactly, so a
+     * consumer wires this straight from `auth.user`, `auth.entitlements`,
+     * `auth.activeWorkspace` and `auth.activeRole` with no reshaping. A guessed
+     * shape needs rewriting the day it meets the real store, which is the whole
+     * reason this one didn't. `display_name` and `email` are both nullable
+     * there, and `activeWorkspace` is genuinely null until a caller with several
+     * memberships chooses one — this component is built against that, not a
+     * happy path.
+     *
+     * Sign-out and settings are the consuming app's concerns, never behaviour
+     * baked in here: `onSignOut` and `onAccountSettings` are callbacks. Theme
+     * follows AppShell's own `onToggleTheme` pattern — override it, or accept
+     * mode-watcher's `toggleMode` by default.
+     *
+     * `onManageMembers` exists for the caller a workspace switcher has nothing
+     * to show: `WorkspaceMenu` (the factory template) renders nothing in the
+     * bar for a single-member workspace, and this is where Members lands
+     * instead (operator ruling, 07/09/2026, master-project#291's org-of-one
+     * case). Wire it whenever the app has a members route, whether or not it
+     * also renders a switcher.
+     *
+     * `links` is the escape valve for everything the fixed entries have no room
+     * for — an Admin route, a support link — as a LIST, so every app's extra
+     * destinations render as the same row. Without it an app puts its own
+     * destination in AppShell's `actions` slot as an icon button (cadmus did,
+     * twice), and two apps do it two ways in the same bar.
+     */
+import type { Component } from 'svelte';
 type $$ComponentProps = {
     user: {
         username: string;
@@ -28,7 +67,29 @@ type $$ComponentProps = {
     onManageMembers?: () => void;
     /** Override the theme action. Defaults to mode-watcher's toggleMode, matching AppShell. */
     onSwitchTheme?: () => void;
+    /**
+     * App destinations the fixed entries have no room for, rendered in their
+     * own group.
+     *
+     * A list of items, never a snippet: a snippet lets each app invent its own
+     * row shape, and two apps inventing two shapes in the same top bar is the
+     * drift this package exists to end. Cadmus is the measured case — its
+     * Admin entry had nowhere to go and became an icon button in AppShell's
+     * `actions` slot, and a second one (a quiet support link) was about to
+     * follow it there.
+     *
+     * No `href`: the callback shape matches every other action on this
+     * component, and a consumer routes with its own `goto`. The icon is
+     * optional — a label-only row stays aligned with any iconed row beside it.
+     */
+    links?: {
+        label: string;
+        icon?: Component<{
+            class?: string;
+        }>;
+        onSelect: () => void;
+    }[];
 };
-declare const AppIdentity: import("svelte").Component<$$ComponentProps, {}, "">;
+declare const AppIdentity: Component<$$ComponentProps, {}, "">;
 type AppIdentity = ReturnType<typeof AppIdentity>;
 export default AppIdentity;

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@poodle64/ui",
-	"version": "2026.9.5",
+	"version": "2026.9.6",
 	"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.5",
+		"version": "2026.9.6",
 		"generatedBy": "scripts/generate-registry.mjs",
 		"source": "scripts/situations.json + package source (DO NOT EDIT the outputs by hand)",
 		"componentCount": 56,

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.5`. 56 components, 15 situations.
+Generated from `@poodle64/ui@2026.9.6`. 56 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.