npm - @poodle64/ui - Versions diffs - 2026.8.10 → 2026.8.12 - Mend

@poodle64/ui 2026.8.10 → 2026.8.12

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 (57) hide show

package/README.md CHANGED Viewed

@@ -74,30 +74,35 @@ the one-owner-per-key note below). It becomes a candidate the day two apps want
 the same chart palette; until then a shared chart component would be a shared
 disagreement.
-**Composed components** (20). Primitives are not what makes an app look like an
+**Composed components** (24). Primitives are not what makes an app look like an
 app — the page chrome is. These are the cross-cutting surfaces every route
 composes from, so a household app gets its layout language from the package
 rather than rebuilding it:
-| Import                                          | What it is                                                                                                                                                                                                                                                                                                                                               |
-| ----------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `page-header`                                   | The only page-title pattern: optional `breadcrumbs` snippet, eyebrow, an optional title, one clamped subtitle, an `info` tooltip, an `actions` slot. Omit `title` for a header that is a breadcrumb bar.                                                                                                                                                 |
-| `panel`                                         | The generic titled card: optional icon, subtitle and trailing actions over a body that can opt out of padding.                                                                                                                                                                                                                                           |
-| `detail-panel`                                  | The entity-detail surface: header with icon/eyebrow/title/`StatusBadge`/close, scrollable body, footer of actions.                                                                                                                                                                                                                                       |
-| `context-column`                                | The persistent right-hand column: a standing `StatList` plus an optional detail that flows in on select.                                                                                                                                                                                                                                                 |
-| `app-dialog`                                    | The dialogue frame: titled header, scrollable body, footer action bar, five sizes (`xs`…`xl`), and an `onOpenChange` for the dismissals the caller did not drive.                                                                                                                                                                                        |
-| `dialog-section`                                | One section of a dialogue body; adjacent sections are divided automatically.                                                                                                                                                                                                                                                                             |
-| `stat-card`                                     | A single metric that earns its space (label, value, unit, sub, status dot, and `valueTone` to colour the figure itself).                                                                                                                                                                                                                                 |
-| `stat-list`                                     | A route's low-context integers as a label→value list. Zero-aware: `muted` keeps a healthy zero quiet.                                                                                                                                                                                                                                                    |
-| `arc-gauge`                                     | A radial capacity/percentage ring for a single 0–100 metric, in a footprint too compact for a `stat-card`.                                                                                                                                                                                                                                               |
-| `bar-row`                                       | A labelled horizontal bar with a trailing tabular value, for a ranked list (usage, rank, token burn).                                                                                                                                                                                                                                                    |
-| `scorecard`                                     | A compact 0/1/2 dot-row health strip for several independent checks read at a glance.                                                                                                                                                                                                                                                                    |
-| `sparkline`                                     | An inline multi-series area+line trend for a row or card with room for a trend but not a full chart.                                                                                                                                                                                                                                                     |
-| `status` / `status-badge`                       | The fixed five-state vocabulary (`success \| warning \| error \| info \| neutral`) and the one state chip, with `pulse` for a state still in motion and `class` for placement. `status-badge` alone also accepts `'primary'`, a brand-emphasis extension outside the shared vocabulary — `stat-card`, `stat-list` and `data-table-toolbar` never see it. |
-| `empty-state` / `error-state` / `loading-state` | The shared blank, error and loading surfaces. Never hand-roll one.                                                                                                                                                                                                                                                                                       |
-| `info-tip`                                      | One tooltip pattern: a small info trigger, or wrap an existing affordance as children.                                                                                                                                                                                                                                                                   |
-| `data-table-toolbar`                            | Search field plus filter-chip groups for a TanStack table. Owns no state; fires callbacks.                                                                                                                                                                                                                                                               |
-| `data-table-tanstack`                           | The TanStack-backed table: global search, column filters, master-detail row select, opt-in bulk selection, responsive column hiding, a first-class empty branch.                                                                                                                                                                                         |
+| Import                                          | What it is                                                                                                                                                                                                                                                                                                                                                  |
+| ----------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `page-header`                                   | The only page-title pattern: optional `breadcrumbs` snippet, eyebrow, an optional title, one clamped subtitle, an `info` tooltip, an `actions` slot. Omit `title` for a header that is a breadcrumb bar.                                                                                                                                                    |
+| `panel`                                         | The generic titled card: optional icon, subtitle and trailing actions over a body that can opt out of padding.                                                                                                                                                                                                                                              |
+| `detail-panel`                                  | The entity-detail surface: header with icon/eyebrow/title/`StatusBadge`/close, scrollable body, footer of actions.                                                                                                                                                                                                                                          |
+| `context-column`                                | The persistent right-hand column: a standing `StatList` plus an optional detail that flows in on select.                                                                                                                                                                                                                                                    |
+| `app-dialog`                                    | The dialogue frame: titled header, scrollable body, footer action bar, five sizes (`xs`…`xl`), and an `onOpenChange` for the dismissals the caller did not drive.                                                                                                                                                                                           |
+| `dialog-section`                                | One section of a dialogue body; adjacent sections are divided automatically.                                                                                                                                                                                                                                                                                |
+| `stat-card`                                     | A single metric that earns its space (label, value, unit, sub, status dot, and `valueTone` to colour the figure itself).                                                                                                                                                                                                                                    |
+| `stat-list`                                     | A route's low-context integers as a label→value list. Zero-aware: `muted` keeps a healthy zero quiet.                                                                                                                                                                                                                                                       |
+| `arc-gauge`                                     | A radial capacity/percentage ring for a single 0–100 metric, in a footprint too compact for a `stat-card`.                                                                                                                                                                                                                                                  |
+| `bar-row`                                       | A labelled horizontal bar with a trailing tabular value, for a ranked list (usage, rank, token burn).                                                                                                                                                                                                                                                       |
+| `scorecard`                                     | A compact 0/1/2 dot-row health strip for several independent checks read at a glance.                                                                                                                                                                                                                                                                       |
+| `sparkline`                                     | An inline multi-series area+line trend for a row or card with room for a trend but not a full chart.                                                                                                                                                                                                                                                        |
+| `status` / `status-badge`                       | The fixed five-state vocabulary (`success \| warning \| error \| info \| neutral`) and the one state chip, with `pulse` for a state still in motion and `class` for placement. `status-badge` alone also accepts `'primary'`, a brand-emphasis extension outside the shared vocabulary — `stat-card`, `stat-list` and `data-table-toolbar` never see it.    |
+| `empty-state` / `error-state` / `loading-state` | The shared blank, error and loading surfaces. Never hand-roll one.                                                                                                                                                                                                                                                                                          |
+| `info-tip`                                      | One tooltip pattern: a small info trigger, or wrap an existing affordance as children.                                                                                                                                                                                                                                                                      |
+| `data-table-toolbar`                            | Search field plus filter-chip groups for a TanStack table. Owns no state; fires callbacks.                                                                                                                                                                                                                                                                  |
+| `schema-form`                                   | The renderer for a config object the server described: a JSON Schema plus a JSON Forms UI Schema in, a form out. Anything it cannot dispatch renders flagged, never blank; see [Server-described forms](#server-described-forms) below.                                                                                                                     |
+| `data-table-tanstack`                           | The TanStack-backed table: global search, column filters, master-detail row select, opt-in bulk selection, responsive column hiding, a first-class empty branch.                                                                                                                                                                                            |
+| `library-browse`                                | The faceted catalogue index: search, facet rail, active filter chips, the document table and a pager, all over plain props (`LibraryDocument[]`, `LibraryFacet[]`). The page fetches, maps and routes; the component renders. Library data is fixed components because its shape is stable; configuration is `schema-form` because its shape changes (#30). |
+| `collection-detail`                             | One collection's surface: identity (`detail-panel`), an at-a-glance `stat-list`, and the documents it holds, with `actions` and `children` slots for the app-specific rest.                                                                                                                                                                                 |
+| `document-detail`                               | One document's surface: identity fields, locations, tags and collection memberships, each section present exactly when its data is. Membership links are the app's own via `collectionHref`.                                                                                                                                                                |
+| `search-results`                                | A ranked retrieval answer: title, the matched passage with accent-tinted highlights, source chip, mapped state and a mono relevance figure per hit; plus the before-any-search and matched-nothing empties.                                                                                                                                                 |
 **The application shell** (`app-shell`, `command-palette`). Page chrome is not
 what makes an app feel like an app either — the shell is. Five household
@@ -147,7 +152,6 @@ That is the whole minimum. Everything below is optional.
 | `identity`                                        | The signed-in surface. Rendered once, at the end of the top bar.                                                        |
 | `context`, `actions`                              | Leading and trailing top-bar slots: a store/tenant switcher, app-level action buttons.                                  |
 | `banner`                                          | Full-width region under the bar: reconnect notices, trial warnings.                                                     |
-| `sidebar`                                         | A secondary, route-scoped column between the nav and the page body.                                                     |
 | `onSearch`, `searchLabel`, `searchShortcut`       | Provide `onSearch` to render the search affordance at all.                                                              |
 | `themeToggle`, `onToggleTheme`                    | Defaults to `mode-watcher`. Set `themeToggle={false}` when the app puts theming inside its own user menu.               |
 | `measure`                                         | How wide the page body may get, from a named scale. Defaults to `full` (no cap).                                        |
@@ -176,10 +180,15 @@ it did before the field existed.
 It exists because the alternative was two left-hand columns: an app whose
 sections have inner navigation had nowhere to put it in the rail, so it put
-modules in `nav` and the current section's pages in `sidebar`. The other way out
-(modules along the top bar, rail for the current module) was rejected on mobile:
-it leaves two navigation surfaces that both need collapsing and both want the
-same hamburger. One nested tree collapses to one drawer.
+modules in `nav` and the current section's pages in a `sidebar` slot. The other
+way out (modules along the top bar, rail for the current module) was rejected on
+mobile: it leaves two navigation surfaces that both need collapsing and both want
+the same hamburger. One nested tree collapses to one drawer.
+Since **2026.8.11 it is the only way in**: the `sidebar` slot is gone. What it
+produced was the shell shape differing per app, and in one app per MODULE — two
+of its sections rendered their pages beside the rail and the rest rendered them
+inside it. Operator ruling, 21/08/2026: no app supports an additional sidebar.
 The behaviour, and why:
@@ -213,9 +222,11 @@ deep, so a section whose own navigation is itself grouped under sub-headings, or
 whose rows disclose a third level, does not lift into the rail whole. The rail is
 not the place to fix that. At 15.5rem a third level leaves roughly 128px for the
 label, which is about fifteen characters. A section that deep keeps its deepest
-level on its own page, where there is width for it, and the `sidebar` snippet
-stays the right home for a column that is not `NavItem`-shaped at all: a document
-tree, a table of contents, a filter panel.
+level on its own page, where there is width for it. A column that is not
+`NavItem`-shaped at all — a document tree, a table of contents, a filter panel —
+belongs in the page too, as a sibling of the article it serves, and not in the
+shell: it is part of that page's own reading surface, it wants that page's
+breakpoints, and no other route should be paying rail width for it.
 `NavItem` / `NavGroup` are exported so an app types its own config against them.
 They carry **no notion of who may see an item**: two surveyed apps gate
@@ -260,8 +271,8 @@ palette:
 }
 ```
-`AppNav` used outside the chrome (the `sidebar` slot's own column) keeps the
-page's ink, so inverting the rail does not drag a secondary nav with it.
+`AppNav` used outside the chrome (a navigation list inside a page) keeps the
+page's ink, so inverting the rail does not drag it along.
 ### The content measure
@@ -497,6 +508,145 @@ but the same class on the `<th>` collapses the heading over its neighbour:
 { accessorKey: 'filename', header: 'Document', meta: { class: 'w-full', cellClass: 'max-w-0' } }
 ```
+## Server-described forms
+`<SchemaForm>` renders a config object whose shape arrives at runtime. It is the
+estate's one mechanism for that, and this README is where its contract lives.
+Two standard documents go in. A **JSON Schema** says what the value is; a **JSON
+Forms UI Schema** says how it is laid out — a tree of layouts, Controls
+addressed by JSON Pointer `scope`, and declarative `rule: { effect, condition }`
+for conditional visibility. Both are published standards, which is the point:
+the renderer is replaceable without a server changing anything.
+```svelte
+<script lang="ts">
+	import SchemaForm from '@poodle64/ui/schema-form';
+	let { schema, uischema } = $props(); // fetched by the app, not by this package
+	let value = $state({});
+</script>
+<SchemaForm {schema} {uischema} {value} onChange={(next) => (value = next)} />
+```
+| Prop       | Purpose                                                                                                                                 |
+| ---------- | --------------------------------------------------------------------------------------------------------------------------------------- |
+| `schema`   | The JSON Schema. Scopes resolve against it, `$ref` included, and it drives validation.                                                  |
+| `uischema` | The JSON Forms UI Schema. Omit it and one is generated from the schema, the only mode in which no field can be missing from the layout. |
+| `value`    | The current value. The component is controlled and never mutates what it is given.                                                      |
+| `onChange` | `(next, { path, value })`. `next` is a fresh object with every untouched branch structurally intact.                                    |
+| `disabled` | Disables every control.                                                                                                                 |
+| `idPrefix` | Prefix for generated element ids, when two forms share a page.                                                                          |
+### It knows nothing about any app
+No HTTP client, no `fetch`, no endpoint string, no service name, no
+app-specific type. Consumers fetch the two documents and map the result
+themselves. That invariant is load-bearing: it is what lets the engine behind
+the schema be swapped later without touching a consumer, and what stopped three
+apps' renderers from being three different components.
+### An unrecognised control renders LOUDLY
+**This is the non-negotiable rule.** The three hand-rolled renderers this
+replaces failed silently: a `widget: "dropdown"` hint rendered no input at all,
+three whole top-level config groups never rendered because their names were
+absent from a hardcoded `GROUP_ORDER`, and nested hints were inert. Every one
+of those made a field VANISH, and a form with a field missing looks exactly like
+a form. They shipped that way for months.
+So nothing here renders as nothing. Eight failure shapes each produce a
+visibly-flagged block carrying `data-schema-form-unknown` and a
+`data-unknown-reason`, which names what could not be done, quotes the pointer so
+the fix is a copy-paste, shows the value that would otherwise have been lost,
+and keeps it editable wherever a text box cannot destroy structure:
+| `data-unknown-reason` | Raised when                                                                       |
+| --------------------- | --------------------------------------------------------------------------------- |
+| `unknown-widget`      | `options.format` / `options.widget` names a widget this package does not ship.    |
+| `unknown-element`     | A UI schema element `type` outside the vocabulary below.                          |
+| `unresolved-scope`    | A Control's `scope` resolves to nothing in the JSON Schema.                       |
+| `missing-scope`       | A Control carries no `scope` at all.                                              |
+| `no-options`          | A `select` or `radio` over a subschema that declares no `enum` or `oneOf`.        |
+| `object-control`      | A Control points at an object, which needs a layout rather than one control.      |
+| `unsupported-array`   | An array whose items are not primitives, so `tags` cannot represent it.           |
+| `not-in-layout`       | The JSON Schema describes a property no Control anywhere in the layout addresses. |
+A primitive value stays editable; an object or an array is shown read-only,
+because a text box over structured data is a data-loss affordance rather than a
+fallback. An unrecognised hint is never quietly swapped for the widget it
+probably meant — `dropdown` almost certainly meant `select`, and guessing would
+restore the field while hiding the fact that the two documents disagree.
+`not-in-layout` is reported once per unaddressed subtree, at the subtree, so a
+forgotten group is one loud entry rather than forty. There is no prop to silence
+any of this. The way to stop a field being flagged is to put a Control for it in
+the UI schema.
+`src/test/schema-form-loud-unknown.test.ts` pins all eight reasons, and
+`harness/drive.mjs` proves in a real engine that each flag has real size and a
+resolved, visible warning border. "Renders loudly" is a claim about paint, and
+a fallback styled into invisibility would satisfy every jsdom assertion while
+reproducing the original defect exactly.
+### The widget dispatch table
+An explicit hint wins; otherwise the widget is derived from the subschema.
+`options.format` is the JSON Forms spelling and `options.widget` is accepted
+alongside it, so a server migrating off a home-grown hint vocabulary does not
+have to change both documents at once. Any hint outside this table is
+`unknown-widget`.
+| Widget     | Chosen when                                     | Rendered by                       |
+| ---------- | ----------------------------------------------- | --------------------------------- |
+| `text`     | `string` (the default)                          | `input`                           |
+| `textarea` | `options.multi: true`, or the hint              | `textarea`                        |
+| `password` | `format: "password"`, or the hint               | `input[type=password]`            |
+| `date`     | `format: "date"`                                | `input[type=date]`                |
+| `time`     | `format: "time"`                                | `input[type=time]`                |
+| `datetime` | `format: "date-time"`                           | `input[type=datetime-local]`      |
+| `number`   | `number` / `integer`                            | `input[type=number]`              |
+| `slider`   | `options.slider: true` on a number, or the hint | composed here (native `range`)    |
+| `select`   | `enum`, or `oneOf: [{ const, title }]`          | `select`                          |
+| `radio`    | the hint, on the same closed value sets         | composed here (native `radio`)    |
+| `switch`   | `boolean` (the default)                         | `switch`                          |
+| `checkbox` | the hint, on a boolean                          | `checkbox`                        |
+| `tags`     | `array` of `string` / `number` / `integer`      | composed here (`badge` + `input`) |
+Three of those — `slider`, `radio` and `tags` — had no primitive in this package
+and are composed inside `schema-form/widgets/`. They are deliberately not
+top-level exports: their only caller is the renderer, and a widget promoted to
+the catalogue before a second consumer wants it is a shape nobody agreed to.
+### The layout vocabulary
+`VerticalLayout`, `HorizontalLayout`, `Group` (a `Panel`), `Categorization` /
+`Category` (a `Tabs` set), `Control` and `Label`. Anything else is
+`unknown-element`.
+`rule` is evaluated on every element, not only on Controls, so a rule on a Group
+takes the whole group with it — which is what an author writing one means.
+`SHOW` / `HIDE` decide whether the element renders at all; `ENABLE` / `DISABLE`
+and `options.readonly` disable the control instead.
+### The engine
+`@jsonforms/core` is used **headless**: JSON Pointer scope resolution, rule
+evaluation and the Ajv instance, nothing else. The renderers are this package's
+own and dispatch to this package's own widgets. There is no official Svelte
+renderer for JSON Forms and the community one carries no external validation, so
+neither is used.
+JSON Forms was chosen over RJSF and `@sjsf/form` on one deciding fact: the
+upstream config models carry 36 conditional-visibility rules, and JSON Forms'
+`rule` model maps onto them 1:1, while RJSF has no standard conditional-
+visibility directive. `@jsonforms/core@3.8.0` was verified working headless
+under Svelte 5 in this package before it was adopted, on 21/08/2026 — scope
+resolution through `$ref`, `SHOW`/`HIDE`/`DISABLE` evaluation, and
+`Generate.uiSchema` all exercised live. It is the package's only runtime
+dependency beyond what was already here.
 ## Consuming the package
 Published to public npm under the `@poodle64` scope, same as `@poodle64/design-tokens`

package/dist/components/ui/app-shell/app-nav.svelte CHANGED Viewed

@@ -3,19 +3,19 @@
 	 * The vertical navigation list.
 	 *
 	 * Rendered by AppShell in the rail/drawer (one element, two states — see
-	 * app-shell.svelte) and exported in its own right so an app with a SECOND,
-	 * route-scoped navigation column (a per-module sidebar) uses the same
-	 * affordance rather than hand-building a near-copy.
-	 * That was the concrete shape of the drift in the estate: one app's inner
-	 * sidebar had reimplemented the active indicator, the group separators and
-	 * the collapse behaviour independently of its own top bar.
+	 * app-shell.svelte), and exported in its own right for a navigation list that
+	 * belongs in a PAGE — so it is built from the same affordance rather than
+	 * hand-copied. That was the concrete shape of the drift in the estate: one
+	 * app's inner nav had reimplemented the active indicator, the group
+	 * separators and the collapse behaviour independently of its own top bar.
 	 *
-	 * An item carrying `children` discloses them in place, beneath itself. That
-	 * is the same drift arriving from the other direction: an app whose sections
-	 * have their own navigation had nowhere to put it inside the rail, so it put
-	 * its modules here and its per-section pages in AppShell's `sidebar` snippet,
-	 * and shipped two left-hand columns. See `types.ts` on `children` for why the
-	 * nested rail won over modules-on-the-top-bar, and why the depth cap is one.
+	 * It is no longer how an app gets a second navigation COLUMN, because there
+	 * is no longer such a thing: AppShell's `sidebar` slot was removed in
+	 * 2026.8.11 (operator ruling, 21/08/2026 — no app supports an additional
+	 * sidebar). An item carrying `children` discloses them in place, beneath
+	 * itself, and that is where a section's own pages go at every width. See
+	 * `types.ts` on `children` for why the nested rail won over
+	 * modules-on-the-top-bar, and why the depth cap is one.
 	 */
 	import ChevronRight from '@lucide/svelte/icons/chevron-right';
 	import {

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

@@ -56,10 +56,20 @@
 	 * remembered. `collapsible` is on for the same reason.
 	 *
 	 * Everything else the surveyed apps differed on turned out to be a slot, not
-	 * a variant: the brand, the identity surface, a context switcher, a banner, a
-	 * secondary column. Those are snippets, so this package imports no app store,
-	 * no app route and no app brand — the coupling that made the best shell in
-	 * the estate unliftable in the first place.
+	 * a variant: the brand, the identity surface, a context switcher, a banner.
+	 * Those are snippets, so this package imports no app store, no app route and
+	 * no app brand — the coupling that made the best shell in the estate
+	 * unliftable in the first place.
+	 *
+	 * There is NO second navigation column, and there is no slot to make one.
+	 * `sidebar` was such a slot until 2026.8.11, and what it produced was two
+	 * apps rendering a module's own pages beside the rail while the other seven
+	 * rendered them inside it — the shell shape differing per app, and in one app
+	 * per MODULE, which is the thing this component exists to stop. Operator
+	 * ruling, 21/08/2026, on seeing one app's two modules disagree: no app
+	 * supports an additional sidebar; a section's own pages roll out beneath it
+	 * in the rail. That is `NavItem.children` (see types.ts), which the rail
+	 * already discloses at every width and folds into the one drawer on a phone.
 	 *
 	 * The minimum useful call is two props:
 	 *
@@ -96,7 +106,6 @@
 		context,
 		actions,
 		identity,
-		sidebar,
 		onSearch,
 		searchLabel = 'Search…',
 		searchShortcut = '⌘K',
@@ -154,8 +163,6 @@
 		actions?: Snippet;
 		/** The signed-in user surface. Rendered once, at the end of the top bar. */
 		identity?: Snippet;
-		/** A secondary, route-scoped column between the nav and the page body. */
-		sidebar?: Snippet;
 		/** Provide to render the search affordance. Usually opens a CommandPalette. */
 		onSearch?: () => void;
 		searchLabel?: string;
@@ -590,11 +597,6 @@
 		{#if banner}{@render banner()}{/if}
 		<div class="flex min-h-0 min-w-0 flex-1">
-			{#if sidebar}
-				<div class="border-border hidden min-h-0 flex-none border-r md:flex">
-					{@render sidebar()}
-				</div>
-			{/if}
 			<!--
 				The scrolling content region, and the element a consumer's
 				"no horizontal overflow" test must measure.

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

@@ -55,10 +55,20 @@
      * remembered. `collapsible` is on for the same reason.
      *
      * Everything else the surveyed apps differed on turned out to be a slot, not
-     * a variant: the brand, the identity surface, a context switcher, a banner, a
-     * secondary column. Those are snippets, so this package imports no app store,
-     * no app route and no app brand — the coupling that made the best shell in
-     * the estate unliftable in the first place.
+     * a variant: the brand, the identity surface, a context switcher, a banner.
+     * Those are snippets, so this package imports no app store, no app route and
+     * no app brand — the coupling that made the best shell in the estate
+     * unliftable in the first place.
+     *
+     * There is NO second navigation column, and there is no slot to make one.
+     * `sidebar` was such a slot until 2026.8.11, and what it produced was two
+     * apps rendering a module's own pages beside the rail while the other seven
+     * rendered them inside it — the shell shape differing per app, and in one app
+     * per MODULE, which is the thing this component exists to stop. Operator
+     * ruling, 21/08/2026, on seeing one app's two modules disagree: no app
+     * supports an additional sidebar; a section's own pages roll out beneath it
+     * in the rail. That is `NavItem.children` (see types.ts), which the rail
+     * already discloses at every width and folds into the one drawer on a phone.
      *
      * The minimum useful call is two props:
      *
@@ -116,8 +126,6 @@ type $$ComponentProps = {
     actions?: Snippet;
     /** The signed-in user surface. Rendered once, at the end of the top bar. */
     identity?: Snippet;
-    /** A secondary, route-scoped column between the nav and the page body. */
-    sidebar?: Snippet;
     /** Provide to render the search affordance. Usually opens a CommandPalette. */
     onSearch?: () => void;
     searchLabel?: string;

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

@@ -57,10 +57,12 @@ export interface NavItem {
      *
      * Without this, an app whose sections have their own inner navigation has
      * nowhere to put it inside the rail. The observed workaround was modules in
-     * `nav` and the current module's pages in the `sidebar` snippet — two
+     * `nav` and the current module's pages in AppShell's `sidebar` snippet — two
      * left-hand columns on a desktop, and, the reason this shape won over moving
      * modules to a top bar, two surfaces on a phone that both want the same
-     * hamburger. One nested tree collapses to one drawer.
+     * hamburger. One nested tree collapses to one drawer. That slot is gone as
+     * of 2026.8.11 and this is the only way in, so a section's navigation is in
+     * the same place in every app and on every route.
      *
      * Named `children`, not `items`, for a mechanical reason as well as a
      * readable one: `isNavGroup` narrows on `'items' in entry`, so an item
@@ -105,11 +107,26 @@ export declare function toGroups(nav: NavSource | undefined): NavGroup[];
 export declare function navChildren(item: NavItem): readonly NavChildItem[];
 /**
  * Every item in source order, ignoring grouping — a parent immediately followed
- * by its own children. Used by the command palette.
+ * by its own children, each destination appearing ONCE. Used by the command
+ * palette.
  *
  * Children are included because they are destinations like any other, and the
  * palette is the fastest route to a page three levels into a section. An item
  * with no children flattens exactly as it always did.
+ *
+ * The de-duplication is not tidiness. A section that discloses its own pages
+ * names its landing page twice by nature — the parent row goes there, and the
+ * section's first child row is that same page under its own name ("Property",
+ * then "Dashboard"). Both rows are wanted in the rail, where they render in
+ * different `{#each}` blocks; flattened they collide, and every consumer keys
+ * this list by `href`, so Svelte throws `each_key_duplicate` and the throw
+ * takes the palette's whole content with it. Measured in a consumer: ⌘K opened
+ * an empty sheet on every module route until the app hand-filtered its own nav
+ * before passing it. An app should not have to know that.
+ *
+ * First occurrence wins, so the surviving entry is the parent's — the row
+ * carrying the section's own name, which is what someone typing into a palette
+ * is looking for.
  */
 export declare function toItems(nav: NavSource | undefined): NavItem[];
 /**

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

@@ -35,19 +35,43 @@ export function navChildren(item) {
 }
 /**
  * Every item in source order, ignoring grouping — a parent immediately followed
- * by its own children. Used by the command palette.
+ * by its own children, each destination appearing ONCE. Used by the command
+ * palette.
  *
  * Children are included because they are destinations like any other, and the
  * palette is the fastest route to a page three levels into a section. An item
  * with no children flattens exactly as it always did.
+ *
+ * The de-duplication is not tidiness. A section that discloses its own pages
+ * names its landing page twice by nature — the parent row goes there, and the
+ * section's first child row is that same page under its own name ("Property",
+ * then "Dashboard"). Both rows are wanted in the rail, where they render in
+ * different `{#each}` blocks; flattened they collide, and every consumer keys
+ * this list by `href`, so Svelte throws `each_key_duplicate` and the throw
+ * takes the palette's whole content with it. Measured in a consumer: ⌘K opened
+ * an empty sheet on every module route until the app hand-filtered its own nav
+ * before passing it. An app should not have to know that.
+ *
+ * First occurrence wins, so the surviving entry is the parent's — the row
+ * carrying the section's own name, which is what someone typing into a palette
+ * is looking for.
  */
 export function toItems(nav) {
     if (!nav)
         return [];
-    return nav.flatMap((entry) => {
-        const items = isNavGroup(entry) ? entry.items : [entry];
-        return items.flatMap((item) => [item, ...navChildren(item)]);
-    });
+    const seen = new Set();
+    const items = [];
+    for (const entry of nav) {
+        for (const item of isNavGroup(entry) ? entry.items : [entry]) {
+            for (const candidate of [item, ...navChildren(item)]) {
+                if (seen.has(candidate.href))
+                    continue;
+                seen.add(candidate.href);
+                items.push(candidate);
+            }
+        }
+    }
+    return items;
 }
 /** Prefix-match `path` against `prefix`, without running past a path segment. */
 function matchesPrefix(path, prefix) {