@wildo-ai/saas-frontend-lib 1.1.5 → 1.1.7

package/dist/esm/core/navigation/zone-collapse-migration.d.ts

@@ -0,0 +1,83 @@
+import { NavigationZoneContentModel, NavigationZoneName, ResponsiveCollapseMode } from '@wildo-ai/saas-models';
+import type { NavigationState } from './navigation.schemas';
+/**
+ * Moving a collapsed zone's content somewhere it can be SEEN, and home again — as pure state
+ * transforms the reducer applies in ONE update.
+ *
+ * ## Why this is a reducer transform and not a sequence of events
+ *
+ * The first implementation (2026-09-25, `c8c8a7dc`) emitted `NAVIGATION_PUSH` / `CLEAR_ZONE` /
+ * `POP` / `REPLACE` from a hook, one entry at a time. Each of those three defects followed from that
+ * shape, and none of them could have been patched inside it:
+ *
+ * - **It read stale state.** `getZoneState` answers from the last RENDER, so within one pass the
+ *   hook could not see the POP it had just emitted. When both panes collapsed and then widened, the
+ *   secondary's restore saw the companion's entry on primary's top, skipped, and marked itself
+ *   done — the secondary's record stayed full-width beside an empty pane.
+ * - **It lost what the entry was.** Every emit passes through a payload schema that STRIPS keys it
+ *   does not declare, and the migration re-described the entry field by field. `hostedPane`,
+ *   `persistent` and `ephemeral` did not make the round trip, so a hosted pane came home unflagged
+ *   under a URL still carrying its `?pane=`.
+ * - **It moved one entry.** A pane's history came back as its last record, and a TABBED pane's
+ *   last tab was moved rather than the one on screen.
+ *
+ * A transform over `NavigationState` moves the entry OBJECTS — nothing is re-described, so nothing
+ * can be dropped — and sees every zone at once, so two panes collapsing together are one decision.
+ *
+ * ## The invariant, which is what makes the caller a reconciler rather than an event handler
+ *
+ * **A collapsed zone holds nothing.** Content can reach one by any path — a click the resolver
+ * already retargeted, a URL restored before the content area was measured, a `?pane=` reload —
+ * and the rule does not care which: whatever sits in a collapsed zone is moved out. The inverse is
+ * **nothing is held on behalf of a zone that is showing**. Both transforms are idempotent (a second
+ * application changes nothing and returns the SAME object), so the caller may apply them on every
+ * render without looping and without remembering what it did last time.
+ */
+/** A zone's content model, as the layout declares it; `SINGLE` when undeclared. */
+export type CollapsibleZoneContentModel = NavigationZoneContentModel | undefined;
+/**
+ * Evacuate `zone` while it is collapsed under `mode`. Returns `state` itself when there is nothing
+ * to move, so a caller can compare by identity.
+ *
+ * - **SINGLE** — the whole stack moves, in order, so the pane's history survives: Back in primary
+ *   walks it exactly as Back in the pane would have. An earlier version moved only the top, on the
+ *   theory that history "in a pane that no longer exists" is not a place the reader can return to;
+ *   but the pane DOES come back, and the contract (`ResponsiveCollapseMode`) says its content is
+ *   preserved.
+ * - **TABBED** — every tab moves, with the tab on SCREEN last so it is the one primary shows. Tabs
+ *   become history while the pane cannot be drawn: that is the only shape one column can give them,
+ *   and it keeps every tab reachable rather than stranding the ones not in front.
+ *
+ * Each moved entry is stamped with `collapsedFromZone` — the one field that lets it go home — and its
+ * `zone` becomes where it now IS. The content area renders an entry under `entry.zone`, so an entry
+ * that kept `zone: secondary` while sitting in primary rendered a surface that believed it was in
+ * the pane: its Back called `goBack(secondary)` on an empty stack and did nothing (Wonder Todos,
+ * a `?pane=` record held in primary at 820px, 2026-09-28). Moving an object is not the same as
+ * re-describing it, but where it lives is not a property it keeps.
+ */
+export declare function evacuateCollapsedZone(state: NavigationState, zone: NavigationZoneName, mode: ResponsiveCollapseMode, contentModel: CollapsibleZoneContentModel): NavigationState;
+/**
+ * Return to `zone` everything held for it while it was collapsed. Returns `state` itself when there
+ * is nothing to return.
+ *
+ * Entries go home as the same objects, with `zone` set back and without their `collapsedFromZone`
+ * stamp, so `hostedPane`, `persistent`, `ephemeral`, `appearance` and anything added to the entry
+ * later all survive. A
+ * TABBED zone's active tab becomes the last returned entry — the one primary was showing, i.e. the
+ * one the reader was looking at.
+ */
+export declare function restoreCollapsedZone(state: NavigationState, zone: NavigationZoneName, contentModel: CollapsibleZoneContentModel): NavigationState;
+/** One collapsible zone's situation at this width, as the reconciler sees it. */
+export interface CollapsibleZoneSituation {
+    zone: NavigationZoneName;
+    /** `undefined` when the zone is shown; otherwise the declared way it collapses. */
+    mode: ResponsiveCollapseMode | undefined;
+    contentModel: CollapsibleZoneContentModel;
+}
+/**
+ * Apply the invariant to every collapsible zone at once: evacuate each collapsed zone, return what
+ * is held for each shown one. Identity-preserving — the SAME state object comes back when nothing
+ * had to move — so it is safe to run on every render.
+ */
+export declare function reconcileCollapsedZones(state: NavigationState, situations: CollapsibleZoneSituation[]): NavigationState;
+//# sourceMappingURL=zone-collapse-migration.d.ts.map

package/dist/esm/core/navigation/zone-collapse-migration.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"zone-collapse-migration.d.ts","sourceRoot":"","sources":["../../../../src/core/navigation/zone-collapse-migration.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,0BAA0B,EAAE,kBAAkB,EAAE,sBAAsB,EAAE,MAAM,uBAAuB,CAAC;AAG/G,OAAO,KAAK,EAAwB,eAAe,EAAuB,MAAM,sBAAsB,CAAC;AAGvG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAgCG;AAEH,mFAAmF;AACnF,MAAM,MAAM,2BAA2B,GAAG,0BAA0B,GAAG,SAAS,CAAC;AAEjF;;;;;;;;;;;;;;;;;;;GAmBG;AACH,wBAAgB,qBAAqB,CACnC,KAAK,EAAE,eAAe,EACtB,IAAI,EAAE,kBAAkB,EACxB,IAAI,EAAE,sBAAsB,EAC5B,YAAY,EAAE,2BAA2B,GACxC,eAAe,CAwBjB;AAoBD;;;;;;;;;GASG;AACH,wBAAgB,oBAAoB,CAClC,KAAK,EAAE,eAAe,EACtB,IAAI,EAAE,kBAAkB,EACxB,YAAY,EAAE,2BAA2B,GACxC,eAAe,CA8BjB;AAED,iFAAiF;AACjF,MAAM,WAAW,wBAAwB;IACvC,IAAI,EAAE,kBAAkB,CAAC;IACzB,mFAAmF;IACnF,IAAI,EAAE,sBAAsB,GAAG,SAAS,CAAC;IACzC,YAAY,EAAE,2BAA2B,CAAC;CAC3C;AAED;;;;GAIG;AACH,wBAAgB,uBAAuB,CAAC,KAAK,EAAE,eAAe,EAAE,UAAU,EAAE,wBAAwB,EAAE,GAAG,eAAe,CAOvH"}

package/dist/esm/core/navigation/zone-collapse-migration.js

@@ -0,0 +1,116 @@
+import { NavigationZoneContentModel, NavigationZoneName, ResponsiveCollapseMode } from '@wildo-ai/saas-models';
+import { NavigationZone } from './navigation.schemas.js';
+import { resolveVisibleEntryIndex } from './zone-visible-entry.js';
+/**
+ * Evacuate `zone` while it is collapsed under `mode`. Returns `state` itself when there is nothing
+ * to move, so a caller can compare by identity.
+ *
+ * - **SINGLE** — the whole stack moves, in order, so the pane's history survives: Back in primary
+ *   walks it exactly as Back in the pane would have. An earlier version moved only the top, on the
+ *   theory that history "in a pane that no longer exists" is not a place the reader can return to;
+ *   but the pane DOES come back, and the contract (`ResponsiveCollapseMode`) says its content is
+ *   preserved.
+ * - **TABBED** — every tab moves, with the tab on SCREEN last so it is the one primary shows. Tabs
+ *   become history while the pane cannot be drawn: that is the only shape one column can give them,
+ *   and it keeps every tab reachable rather than stranding the ones not in front.
+ *
+ * Each moved entry is stamped with `collapsedFromZone` — the one field that lets it go home — and its
+ * `zone` becomes where it now IS. The content area renders an entry under `entry.zone`, so an entry
+ * that kept `zone: secondary` while sitting in primary rendered a surface that believed it was in
+ * the pane: its Back called `goBack(secondary)` on an empty stack and did nothing (Wonder Todos,
+ * a `?pane=` record held in primary at 820px, 2026-09-28). Moving an object is not the same as
+ * re-describing it, but where it lives is not a property it keeps.
+ */
+export function evacuateCollapsedZone(state, zone, mode, contentModel) {
+    const zoneState = state.zones[zone];
+    if (!zoneState || zoneState.stack.length === 0)
+        return state;
+    const visibleIndex = resolveVisibleEntryIndex(zoneState.stack, contentModel, zoneState.activeTabId);
+    const ordered = contentModel === NavigationZoneContentModel.TABBED
+        ? [...zoneState.stack.filter((_, index) => index !== visibleIndex), zoneState.stack[visibleIndex]]
+        : zoneState.stack;
+    const heldIn = mode === ResponsiveCollapseMode.OVERLAY ? NavigationZone.OVERLAY : NavigationZoneName.PRIMARY;
+    const moving = ordered.map((entry) => ({ ...entry, zone: heldIn, collapsedFromZone: zone }));
+    const emptied = { ...zoneState, stack: [], activeTabId: undefined, isVisible: false };
+    if (mode === ResponsiveCollapseMode.OVERLAY) {
+        return { ...state, overlay: [...state.overlay, ...moving], zones: { ...state.zones, [zone]: emptied } };
+    }
+    const primary = state.zones[NavigationZoneName.PRIMARY];
+    return {
+        ...state,
+        zones: {
+            ...state.zones,
+            [zone]: emptied,
+            [NavigationZoneName.PRIMARY]: { ...primary, stack: [...primary.stack, ...moving], isVisible: true },
+        },
+    };
+}
+/**
+ * The entries of `stack` held on behalf of `zone` that may still go home: those inside the TRAILING
+ * run of stamped entries.
+ *
+ * An entry the reader pushed on top of the borrowed content — an ordinary, unstamped navigation —
+ * ends the run. Everything beneath it is then history they walked through, and pulling it out from
+ * under the page they are standing on would be a worse surprise than leaving it where it is.
+ *
+ * Several zones may share one run (both panes collapse at MOBILE together), so the run is filtered
+ * by zone rather than required to be homogeneous. That is what makes the order in which zones are
+ * restored irrelevant — the defect the event-driven version had.
+ */
+function returnableEntries(stack, zone) {
+    let runStart = stack.length;
+    while (runStart > 0 && stack[runStart - 1].collapsedFromZone !== undefined)
+        runStart -= 1;
+    return stack.slice(runStart).filter(entry => entry.collapsedFromZone === zone);
+}
+/**
+ * Return to `zone` everything held for it while it was collapsed. Returns `state` itself when there
+ * is nothing to return.
+ *
+ * Entries go home as the same objects, with `zone` set back and without their `collapsedFromZone`
+ * stamp, so `hostedPane`, `persistent`, `ephemeral`, `appearance` and anything added to the entry
+ * later all survive. A
+ * TABBED zone's active tab becomes the last returned entry — the one primary was showing, i.e. the
+ * one the reader was looking at.
+ */
+export function restoreCollapsedZone(state, zone, contentModel) {
+    const primary = state.zones[NavigationZoneName.PRIMARY];
+    const fromPrimary = returnableEntries(primary.stack, zone);
+    const fromOverlay = returnableEntries(state.overlay, zone);
+    if (fromPrimary.length === 0 && fromOverlay.length === 0)
+        return state;
+    const leaving = new Set([...fromPrimary, ...fromOverlay].map(entry => entry.id));
+    const returning = [...fromPrimary, ...fromOverlay].map((entry) => {
+        const { collapsedFromZone: _home, ...rest } = entry;
+        return { ...rest, zone };
+    });
+    const zoneState = state.zones[zone];
+    const stack = [...zoneState.stack, ...returning];
+    return {
+        ...state,
+        overlay: fromOverlay.length > 0 ? state.overlay.filter(entry => !leaving.has(entry.id)) : state.overlay,
+        zones: {
+            ...state.zones,
+            [NavigationZoneName.PRIMARY]: fromPrimary.length > 0
+                ? { ...primary, stack: primary.stack.filter(entry => !leaving.has(entry.id)), isVisible: true }
+                : primary,
+            [zone]: {
+                ...zoneState,
+                stack,
+                isVisible: true,
+                activeTabId: contentModel === NavigationZoneContentModel.TABBED ? stack[stack.length - 1].id : zoneState.activeTabId,
+            },
+        },
+    };
+}
+/**
+ * Apply the invariant to every collapsible zone at once: evacuate each collapsed zone, return what
+ * is held for each shown one. Identity-preserving — the SAME state object comes back when nothing
+ * had to move — so it is safe to run on every render.
+ */
+export function reconcileCollapsedZones(state, situations) {
+    return situations.reduce((current, { zone, mode, contentModel }) => (mode !== undefined
+        ? evacuateCollapsedZone(current, zone, mode, contentModel)
+        : restoreCollapsedZone(current, zone, contentModel)), state);
+}
+//# sourceMappingURL=zone-collapse-migration.js.map

package/dist/esm/core/navigation/zone-collapse-migration.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"zone-collapse-migration.js","sourceRoot":"","sources":["../../../../src/core/navigation/zone-collapse-migration.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,0BAA0B,EAAE,kBAAkB,EAAE,sBAAsB,EAAE,MAAM,uBAAuB,CAAC;AAE/G,OAAO,EAAE,cAAc,EAAE,MAAM,sBAAsB,CAAC;AAEtD,OAAO,EAAE,wBAAwB,EAAE,MAAM,sBAAsB,CAAC;AAuChE;;;;;;;;;;;;;;;;;;;GAmBG;AACH,MAAM,UAAU,qBAAqB,CACnC,KAAsB,EACtB,IAAwB,EACxB,IAA4B,EAC5B,YAAyC;IAEzC,MAAM,SAAS,GAAG,KAAK,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC;IACpC,IAAI,CAAC,SAAS,IAAI,SAAS,CAAC,KAAK,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO,KAAK,CAAC;IAE7D,MAAM,YAAY,GAAG,wBAAwB,CAAC,SAAS,CAAC,KAAK,EAAE,YAAY,EAAE,SAAS,CAAC,WAAW,CAAC,CAAC;IACpG,MAAM,OAAO,GAAG,YAAY,KAAK,0BAA0B,CAAC,MAAM;QAChE,CAAC,CAAC,CAAC,GAAG,SAAS,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,KAAK,EAAE,EAAE,CAAC,KAAK,KAAK,YAAY,CAAC,EAAE,SAAS,CAAC,KAAK,CAAC,YAAY,CAAE,CAAC;QACnG,CAAC,CAAC,SAAS,CAAC,KAAK,CAAC;IACpB,MAAM,MAAM,GAAG,IAAI,KAAK,sBAAsB,CAAC,OAAO,CAAC,CAAC,CAAC,cAAc,CAAC,OAAO,CAAC,CAAC,CAAC,kBAAkB,CAAC,OAAO,CAAC;IAC7G,MAAM,MAAM,GAAG,OAAO,CAAC,GAAG,CAAC,CAAC,KAAK,EAAwB,EAAE,CAAC,CAAC,EAAE,GAAG,KAAK,EAAE,IAAI,EAAE,MAAM,EAAE,iBAAiB,EAAE,IAAI,EAAE,CAAC,CAAC,CAAC;IAEnH,MAAM,OAAO,GAAwB,EAAE,GAAG,SAAS,EAAE,KAAK,EAAE,EAAE,EAAE,WAAW,EAAE,SAAS,EAAE,SAAS,EAAE,KAAK,EAAE,CAAC;IAC3G,IAAI,IAAI,KAAK,sBAAsB,CAAC,OAAO,EAAE,CAAC;QAC5C,OAAO,EAAE,GAAG,KAAK,EAAE,OAAO,EAAE,CAAC,GAAG,KAAK,CAAC,OAAO,EAAE,GAAG,MAAM,CAAC,EAAE,KAAK,EAAE,EAAE,GAAG,KAAK,CAAC,KAAK,EAAE,CAAC,IAAI,CAAC,EAAE,OAAO,EAAE,EAAE,CAAC;IAC1G,CAAC;IACD,MAAM,OAAO,GAAG,KAAK,CAAC,KAAK,CAAC,kBAAkB,CAAC,OAAO,CAAC,CAAC;IACxD,OAAO;QACL,GAAG,KAAK;QACR,KAAK,EAAE;YACL,GAAG,KAAK,CAAC,KAAK;YACd,CAAC,IAAI,CAAC,EAAE,OAAO;YACf,CAAC,kBAAkB,CAAC,OAAO,CAAC,EAAE,EAAE,GAAG,OAAO,EAAE,KAAK,EAAE,CAAC,GAAG,OAAO,CAAC,KAAK,EAAE,GAAG,MAAM,CAAC,EAAE,SAAS,EAAE,IAAI,EAAE;SACpG;KACF,CAAC;AACJ,CAAC;AAED;;;;;;;;;;;GAWG;AACH,SAAS,iBAAiB,CAAC,KAA6B,EAAE,IAAwB;IAChF,IAAI,QAAQ,GAAG,KAAK,CAAC,MAAM,CAAC;IAC5B,OAAO,QAAQ,GAAG,CAAC,IAAI,KAAK,CAAC,QAAQ,GAAG,CAAC,CAAE,CAAC,iBAAiB,KAAK,SAAS;QAAE,QAAQ,IAAI,CAAC,CAAC;IAC3F,OAAO,KAAK,CAAC,KAAK,CAAC,QAAQ,CAAC,CAAC,MAAM,CAAC,KAAK,CAAC,EAAE,CAAC,KAAK,CAAC,iBAAiB,KAAK,IAAI,CAAC,CAAC;AACjF,CAAC;AAED;;;;;;;;;GASG;AACH,MAAM,UAAU,oBAAoB,CAClC,KAAsB,EACtB,IAAwB,EACxB,YAAyC;IAEzC,MAAM,OAAO,GAAG,KAAK,CAAC,KAAK,CAAC,kBAAkB,CAAC,OAAO,CAAC,CAAC;IACxD,MAAM,WAAW,GAAG,iBAAiB,CAAC,OAAO,CAAC,KAAK,EAAE,IAAI,CAAC,CAAC;IAC3D,MAAM,WAAW,GAAG,iBAAiB,CAAC,KAAK,CAAC,OAAO,EAAE,IAAI,CAAC,CAAC;IAC3D,IAAI,WAAW,CAAC,MAAM,KAAK,CAAC,IAAI,WAAW,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO,KAAK,CAAC;IAEvE,MAAM,OAAO,GAAG,IAAI,GAAG,CAAC,CAAC,GAAG,WAAW,EAAE,GAAG,WAAW,CAAC,CAAC,GAAG,CAAC,KAAK,CAAC,EAAE,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC,CAAC;IACjF,MAAM,SAAS,GAAG,CAAC,GAAG,WAAW,EAAE,GAAG,WAAW,CAAC,CAAC,GAAG,CAAC,CAAC,KAAK,EAAwB,EAAE;QACrF,MAAM,EAAE,iBAAiB,EAAE,KAAK,EAAE,GAAG,IAAI,EAAE,GAAG,KAAK,CAAC;QACpD,OAAO,EAAE,GAAG,IAAI,EAAE,IAAI,EAAE,CAAC;IAC3B,CAAC,CAAC,CAAC;IACH,MAAM,SAAS,GAAG,KAAK,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC;IACpC,MAAM,KAAK,GAAG,CAAC,GAAG,SAAS,CAAC,KAAK,EAAE,GAAG,SAAS,CAAC,CAAC;IAEjD,OAAO;QACL,GAAG,KAAK;QACR,OAAO,EAAE,WAAW,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,OAAO;QACvG,KAAK,EAAE;YACL,GAAG,KAAK,CAAC,KAAK;YACd,CAAC,kBAAkB,CAAC,OAAO,CAAC,EAAE,WAAW,CAAC,MAAM,GAAG,CAAC;gBAClD,CAAC,CAAC,EAAE,GAAG,OAAO,EAAE,KAAK,EAAE,OAAO,CAAC,KAAK,CAAC,MAAM,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC,EAAE,SAAS,EAAE,IAAI,EAAE;gBAC/F,CAAC,CAAC,OAAO;YACX,CAAC,IAAI,CAAC,EAAE;gBACN,GAAG,SAAS;gBACZ,KAAK;gBACL,SAAS,EAAE,IAAI;gBACf,WAAW,EAAE,YAAY,KAAK,0BAA0B,CAAC,MAAM,CAAC,CAAC,CAAC,KAAK,CAAC,KAAK,CAAC,MAAM,GAAG,CAAC,CAAE,CAAC,EAAE,CAAC,CAAC,CAAC,SAAS,CAAC,WAAW;aACtH;SACF;KACF,CAAC;AACJ,CAAC;AAUD;;;;GAIG;AACH,MAAM,UAAU,uBAAuB,CAAC,KAAsB,EAAE,UAAsC;IACpG,OAAO,UAAU,CAAC,MAAM,CACtB,CAAC,OAAO,EAAE,EAAE,IAAI,EAAE,IAAI,EAAE,YAAY,EAAE,EAAE,EAAE,CAAC,CAAC,IAAI,KAAK,SAAS;QAC5D,CAAC,CAAC,qBAAqB,CAAC,OAAO,EAAE,IAAI,EAAE,IAAI,EAAE,YAAY,CAAC;QAC1D,CAAC,CAAC,oBAAoB,CAAC,OAAO,EAAE,IAAI,EAAE,YAAY,CAAC,CAAC,EACtD,KAAK,CACN,CAAC;AACJ,CAAC","sourcesContent":["import { NavigationZoneContentModel, NavigationZoneName, ResponsiveCollapseMode } from '@wildo-ai/saas-models';\n\nimport { NavigationZone } from './navigation.schemas';\nimport type { NavigationStackEntry, NavigationState, NavigationZoneState } from './navigation.schemas';\nimport { resolveVisibleEntryIndex } from './zone-visible-entry';\n\n/**\n * Moving a collapsed zone's content somewhere it can be SEEN, and home again — as pure state\n * transforms the reducer applies in ONE update.\n *\n * ## Why this is a reducer transform and not a sequence of events\n *\n * The first implementation (2026-09-25, `c8c8a7dc`) emitted `NAVIGATION_PUSH` / `CLEAR_ZONE` /\n * `POP` / `REPLACE` from a hook, one entry at a time. Each of those three defects followed from that\n * shape, and none of them could have been patched inside it:\n *\n * - **It read stale state.** `getZoneState` answers from the last RENDER, so within one pass the\n *   hook could not see the POP it had just emitted. When both panes collapsed and then widened, the\n *   secondary's restore saw the companion's entry on primary's top, skipped, and marked itself\n *   done — the secondary's record stayed full-width beside an empty pane.\n * - **It lost what the entry was.** Every emit passes through a payload schema that STRIPS keys it\n *   does not declare, and the migration re-described the entry field by field. `hostedPane`,\n *   `persistent` and `ephemeral` did not make the round trip, so a hosted pane came home unflagged\n *   under a URL still carrying its `?pane=`.\n * - **It moved one entry.** A pane's history came back as its last record, and a TABBED pane's\n *   last tab was moved rather than the one on screen.\n *\n * A transform over `NavigationState` moves the entry OBJECTS — nothing is re-described, so nothing\n * can be dropped — and sees every zone at once, so two panes collapsing together are one decision.\n *\n * ## The invariant, which is what makes the caller a reconciler rather than an event handler\n *\n * **A collapsed zone holds nothing.** Content can reach one by any path — a click the resolver\n * already retargeted, a URL restored before the content area was measured, a `?pane=` reload —\n * and the rule does not care which: whatever sits in a collapsed zone is moved out. The inverse is\n * **nothing is held on behalf of a zone that is showing**. Both transforms are idempotent (a second\n * application changes nothing and returns the SAME object), so the caller may apply them on every\n * render without looping and without remembering what it did last time.\n */\n\n/** A zone's content model, as the layout declares it; `SINGLE` when undeclared. */\nexport type CollapsibleZoneContentModel = NavigationZoneContentModel | undefined;\n\n/**\n * Evacuate `zone` while it is collapsed under `mode`. Returns `state` itself when there is nothing\n * to move, so a caller can compare by identity.\n *\n * - **SINGLE** — the whole stack moves, in order, so the pane's history survives: Back in primary\n *   walks it exactly as Back in the pane would have. An earlier version moved only the top, on the\n *   theory that history \"in a pane that no longer exists\" is not a place the reader can return to;\n *   but the pane DOES come back, and the contract (`ResponsiveCollapseMode`) says its content is\n *   preserved.\n * - **TABBED** — every tab moves, with the tab on SCREEN last so it is the one primary shows. Tabs\n *   become history while the pane cannot be drawn: that is the only shape one column can give them,\n *   and it keeps every tab reachable rather than stranding the ones not in front.\n *\n * Each moved entry is stamped with `collapsedFromZone` — the one field that lets it go home — and its\n * `zone` becomes where it now IS. The content area renders an entry under `entry.zone`, so an entry\n * that kept `zone: secondary` while sitting in primary rendered a surface that believed it was in\n * the pane: its Back called `goBack(secondary)` on an empty stack and did nothing (Wonder Todos,\n * a `?pane=` record held in primary at 820px, 2026-09-28). Moving an object is not the same as\n * re-describing it, but where it lives is not a property it keeps.\n */\nexport function evacuateCollapsedZone(\n  state: NavigationState,\n  zone: NavigationZoneName,\n  mode: ResponsiveCollapseMode,\n  contentModel: CollapsibleZoneContentModel,\n): NavigationState {\n  const zoneState = state.zones[zone];\n  if (!zoneState || zoneState.stack.length === 0) return state;\n\n  const visibleIndex = resolveVisibleEntryIndex(zoneState.stack, contentModel, zoneState.activeTabId);\n  const ordered = contentModel === NavigationZoneContentModel.TABBED\n    ? [...zoneState.stack.filter((_, index) => index !== visibleIndex), zoneState.stack[visibleIndex]!]\n    : zoneState.stack;\n  const heldIn = mode === ResponsiveCollapseMode.OVERLAY ? NavigationZone.OVERLAY : NavigationZoneName.PRIMARY;\n  const moving = ordered.map((entry): NavigationStackEntry => ({ ...entry, zone: heldIn, collapsedFromZone: zone }));\n\n  const emptied: NavigationZoneState = { ...zoneState, stack: [], activeTabId: undefined, isVisible: false };\n  if (mode === ResponsiveCollapseMode.OVERLAY) {\n    return { ...state, overlay: [...state.overlay, ...moving], zones: { ...state.zones, [zone]: emptied } };\n  }\n  const primary = state.zones[NavigationZoneName.PRIMARY];\n  return {\n    ...state,\n    zones: {\n      ...state.zones,\n      [zone]: emptied,\n      [NavigationZoneName.PRIMARY]: { ...primary, stack: [...primary.stack, ...moving], isVisible: true },\n    },\n  };\n}\n\n/**\n * The entries of `stack` held on behalf of `zone` that may still go home: those inside the TRAILING\n * run of stamped entries.\n *\n * An entry the reader pushed on top of the borrowed content — an ordinary, unstamped navigation —\n * ends the run. Everything beneath it is then history they walked through, and pulling it out from\n * under the page they are standing on would be a worse surprise than leaving it where it is.\n *\n * Several zones may share one run (both panes collapse at MOBILE together), so the run is filtered\n * by zone rather than required to be homogeneous. That is what makes the order in which zones are\n * restored irrelevant — the defect the event-driven version had.\n */\nfunction returnableEntries(stack: NavigationStackEntry[], zone: NavigationZoneName): NavigationStackEntry[] {\n  let runStart = stack.length;\n  while (runStart > 0 && stack[runStart - 1]!.collapsedFromZone !== undefined) runStart -= 1;\n  return stack.slice(runStart).filter(entry => entry.collapsedFromZone === zone);\n}\n\n/**\n * Return to `zone` everything held for it while it was collapsed. Returns `state` itself when there\n * is nothing to return.\n *\n * Entries go home as the same objects, with `zone` set back and without their `collapsedFromZone`\n * stamp, so `hostedPane`, `persistent`, `ephemeral`, `appearance` and anything added to the entry\n * later all survive. A\n * TABBED zone's active tab becomes the last returned entry — the one primary was showing, i.e. the\n * one the reader was looking at.\n */\nexport function restoreCollapsedZone(\n  state: NavigationState,\n  zone: NavigationZoneName,\n  contentModel: CollapsibleZoneContentModel,\n): NavigationState {\n  const primary = state.zones[NavigationZoneName.PRIMARY];\n  const fromPrimary = returnableEntries(primary.stack, zone);\n  const fromOverlay = returnableEntries(state.overlay, zone);\n  if (fromPrimary.length === 0 && fromOverlay.length === 0) return state;\n\n  const leaving = new Set([...fromPrimary, ...fromOverlay].map(entry => entry.id));\n  const returning = [...fromPrimary, ...fromOverlay].map((entry): NavigationStackEntry => {\n    const { collapsedFromZone: _home, ...rest } = entry;\n    return { ...rest, zone };\n  });\n  const zoneState = state.zones[zone];\n  const stack = [...zoneState.stack, ...returning];\n\n  return {\n    ...state,\n    overlay: fromOverlay.length > 0 ? state.overlay.filter(entry => !leaving.has(entry.id)) : state.overlay,\n    zones: {\n      ...state.zones,\n      [NavigationZoneName.PRIMARY]: fromPrimary.length > 0\n        ? { ...primary, stack: primary.stack.filter(entry => !leaving.has(entry.id)), isVisible: true }\n        : primary,\n      [zone]: {\n        ...zoneState,\n        stack,\n        isVisible: true,\n        activeTabId: contentModel === NavigationZoneContentModel.TABBED ? stack[stack.length - 1]!.id : zoneState.activeTabId,\n      },\n    },\n  };\n}\n\n/** One collapsible zone's situation at this width, as the reconciler sees it. */\nexport interface CollapsibleZoneSituation {\n  zone: NavigationZoneName;\n  /** `undefined` when the zone is shown; otherwise the declared way it collapses. */\n  mode: ResponsiveCollapseMode | undefined;\n  contentModel: CollapsibleZoneContentModel;\n}\n\n/**\n * Apply the invariant to every collapsible zone at once: evacuate each collapsed zone, return what\n * is held for each shown one. Identity-preserving — the SAME state object comes back when nothing\n * had to move — so it is safe to run on every render.\n */\nexport function reconcileCollapsedZones(state: NavigationState, situations: CollapsibleZoneSituation[]): NavigationState {\n  return situations.reduce(\n    (current, { zone, mode, contentModel }) => (mode !== undefined\n      ? evacuateCollapsedZone(current, zone, mode, contentModel)\n      : restoreCollapsedZone(current, zone, contentModel)),\n    state,\n  );\n}\n"]}

package/dist/esm/core/navigation/zone-collapse.d.ts

@@ -0,0 +1,51 @@
+import { ViewportBreakpoint } from '@wildo-ai/zod-decorators';
+import type { NavigationLayout, ZoneConfig } from '@wildo-ai/saas-models';
+import { NavigationZoneName } from '@wildo-ai/saas-models';
+/**
+ * Is an adjacent zone COLLAPSED right now — too narrow a viewport, or too narrow a content area?
+ *
+ * ## Why this is one function and not three conditions
+ *
+ * Three places answer this question, and until 2026-09-25 only one of them answered it completely:
+ *
+ * | asker | what it decides | what it used to read |
+ * |---|---|---|
+ * | `navigationPolicyResolver.resolveCollapseMode` | where a CLICK's content lands | viewport + content-area fit — correct |
+ * | `NavigationContentAreas` | whether the pane is RENDERED | `isMobile` only |
+ * | `NavigationUtils.resolveResourceTargetZone` | where a URL's content lands | nothing — it took no viewport at all |
+ *
+ * Both gaps produced a silent wrong result:
+ *
+ * - **The renderer's**: at VERT_TABLET (768–1023px) a declared `responsiveCollapse` retargets every
+ *   click away from the pane while the pane keeps rendering — so a zone with `onEmpty: EMPTY_STATE`
+ *   showed its "select an item" placeholder permanently, next to a list whose clicks went elsewhere.
+ * - **The URL path's**: a depth ≥ 1 resource was routed to SECONDARY regardless of viewport, and the
+ *   mobile render branch draws PRIMARY and nothing else — so a bookmarked or refreshed nested record
+ *   on a phone showed its PARENT, silently. The click path was correct the whole time, which is what
+ *   made it invisible: the same content reached the right place when clicked and the wrong place when
+ *   linked to. Note the viewport WAS threaded into the adjacent depth-0 branch
+ *   (`prefersAdjacentZoneForDetail`) and not into this one — one invariant, two sites, one of them
+ *   done (`.claude/rules/invariant-call-site-enumeration.md`).
+ *
+ * @param contentAreaWidth  `undefined` until the first measurement, which answers "fits" — an
+ *                          unmeasured area is not a narrow one. See `contentAreaFitsSplit`.
+ */
+export declare function zoneIsCollapsedAtViewport(params: {
+    zoneConfig: ZoneConfig | undefined;
+    viewport: ViewportBreakpoint | undefined;
+    contentAreaWidth?: number;
+}): boolean;
+/**
+ * The adjacent zone a URL-restored resource may actually be placed in, or `undefined` when every
+ * adjacent zone is collapsed and the content belongs in PRIMARY.
+ *
+ * The URL path's counterpart to the resolver's collapse handling: same predicate, same inputs, so a
+ * deep link and a click cannot disagree about where a record lives at a given width.
+ */
+export declare function adjacentZoneUsableAtViewport(params: {
+    zone: NavigationZoneName;
+    layout: NavigationLayout | undefined;
+    viewport: ViewportBreakpoint | undefined;
+    contentAreaWidth?: number;
+}): boolean;
+//# sourceMappingURL=zone-collapse.d.ts.map

package/dist/esm/core/navigation/zone-collapse.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"zone-collapse.d.ts","sourceRoot":"","sources":["../../../../src/core/navigation/zone-collapse.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,kBAAkB,EAAE,MAAM,0BAA0B,CAAC;AAC9D,OAAO,KAAK,EAAE,gBAAgB,EAAE,UAAU,EAAE,MAAM,uBAAuB,CAAC;AAC1E,OAAO,EAAE,kBAAkB,EAAE,MAAM,uBAAuB,CAAC;AAI3D;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG;AACH,wBAAgB,yBAAyB,CAAC,MAAM,EAAE;IAChD,UAAU,EAAE,UAAU,GAAG,SAAS,CAAC;IACnC,QAAQ,EAAE,kBAAkB,GAAG,SAAS,CAAC;IACzC,gBAAgB,CAAC,EAAE,MAAM,CAAC;CAC3B,GAAG,OAAO,CAQV;AAED;;;;;;GAMG;AACH,wBAAgB,4BAA4B,CAAC,MAAM,EAAE;IACnD,IAAI,EAAE,kBAAkB,CAAC;IACzB,MAAM,EAAE,gBAAgB,GAAG,SAAS,CAAC;IACrC,QAAQ,EAAE,kBAAkB,GAAG,SAAS,CAAC;IACzC,gBAAgB,CAAC,EAAE,MAAM,CAAC;CAC3B,GAAG,OAAO,CAOV"}

package/dist/esm/core/navigation/zone-collapse.js

@@ -0,0 +1,59 @@
+import { ViewportBreakpoint } from '@wildo-ai/zod-decorators';
+import { NavigationZoneName } from '@wildo-ai/saas-models';
+import { contentAreaFitsSplit } from './split-fit.js';
+/**
+ * Is an adjacent zone COLLAPSED right now — too narrow a viewport, or too narrow a content area?
+ *
+ * ## Why this is one function and not three conditions
+ *
+ * Three places answer this question, and until 2026-09-25 only one of them answered it completely:
+ *
+ * | asker | what it decides | what it used to read |
+ * |---|---|---|
+ * | `navigationPolicyResolver.resolveCollapseMode` | where a CLICK's content lands | viewport + content-area fit — correct |
+ * | `NavigationContentAreas` | whether the pane is RENDERED | `isMobile` only |
+ * | `NavigationUtils.resolveResourceTargetZone` | where a URL's content lands | nothing — it took no viewport at all |
+ *
+ * Both gaps produced a silent wrong result:
+ *
+ * - **The renderer's**: at VERT_TABLET (768–1023px) a declared `responsiveCollapse` retargets every
+ *   click away from the pane while the pane keeps rendering — so a zone with `onEmpty: EMPTY_STATE`
+ *   showed its "select an item" placeholder permanently, next to a list whose clicks went elsewhere.
+ * - **The URL path's**: a depth ≥ 1 resource was routed to SECONDARY regardless of viewport, and the
+ *   mobile render branch draws PRIMARY and nothing else — so a bookmarked or refreshed nested record
+ *   on a phone showed its PARENT, silently. The click path was correct the whole time, which is what
+ *   made it invisible: the same content reached the right place when clicked and the wrong place when
+ *   linked to. Note the viewport WAS threaded into the adjacent depth-0 branch
+ *   (`prefersAdjacentZoneForDetail`) and not into this one — one invariant, two sites, one of them
+ *   done (`.claude/rules/invariant-call-site-enumeration.md`).
+ *
+ * @param contentAreaWidth  `undefined` until the first measurement, which answers "fits" — an
+ *                          unmeasured area is not a narrow one. See `contentAreaFitsSplit`.
+ */
+export function zoneIsCollapsedAtViewport(params) {
+    const narrowViewport = params.viewport === ViewportBreakpoint.MOBILE
+        || params.viewport === ViewportBreakpoint.VERT_TABLET;
+    if (narrowViewport)
+        return true;
+    return !contentAreaFitsSplit({
+        contentAreaWidth: params.contentAreaWidth,
+        paneMinWidthPx: params.zoneConfig?.minWidth,
+    });
+}
+/**
+ * The adjacent zone a URL-restored resource may actually be placed in, or `undefined` when every
+ * adjacent zone is collapsed and the content belongs in PRIMARY.
+ *
+ * The URL path's counterpart to the resolver's collapse handling: same predicate, same inputs, so a
+ * deep link and a click cannot disagree about where a record lives at a given width.
+ */
+export function adjacentZoneUsableAtViewport(params) {
+    if (params.zone === NavigationZoneName.PRIMARY)
+        return true;
+    return !zoneIsCollapsedAtViewport({
+        zoneConfig: params.layout?.zones?.[params.zone],
+        viewport: params.viewport,
+        contentAreaWidth: params.contentAreaWidth,
+    });
+}
+//# sourceMappingURL=zone-collapse.js.map

package/dist/esm/core/navigation/zone-collapse.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"zone-collapse.js","sourceRoot":"","sources":["../../../../src/core/navigation/zone-collapse.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,kBAAkB,EAAE,MAAM,0BAA0B,CAAC;AAE9D,OAAO,EAAE,kBAAkB,EAAE,MAAM,uBAAuB,CAAC;AAE3D,OAAO,EAAE,oBAAoB,EAAE,MAAM,aAAa,CAAC;AAEnD;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG;AACH,MAAM,UAAU,yBAAyB,CAAC,MAIzC;IACC,MAAM,cAAc,GAAG,MAAM,CAAC,QAAQ,KAAK,kBAAkB,CAAC,MAAM;WAC/D,MAAM,CAAC,QAAQ,KAAK,kBAAkB,CAAC,WAAW,CAAC;IACxD,IAAI,cAAc;QAAE,OAAO,IAAI,CAAC;IAChC,OAAO,CAAC,oBAAoB,CAAC;QAC3B,gBAAgB,EAAE,MAAM,CAAC,gBAAgB;QACzC,cAAc,EAAE,MAAM,CAAC,UAAU,EAAE,QAAQ;KAC5C,CAAC,CAAC;AACL,CAAC;AAED;;;;;;GAMG;AACH,MAAM,UAAU,4BAA4B,CAAC,MAK5C;IACC,IAAI,MAAM,CAAC,IAAI,KAAK,kBAAkB,CAAC,OAAO;QAAE,OAAO,IAAI,CAAC;IAC5D,OAAO,CAAC,yBAAyB,CAAC;QAChC,UAAU,EAAE,MAAM,CAAC,MAAM,EAAE,KAAK,EAAE,CAAC,MAAM,CAAC,IAAI,CAAC;QAC/C,QAAQ,EAAE,MAAM,CAAC,QAAQ;QACzB,gBAAgB,EAAE,MAAM,CAAC,gBAAgB;KAC1C,CAAC,CAAC;AACL,CAAC","sourcesContent":["import { ViewportBreakpoint } from '@wildo-ai/zod-decorators';\nimport type { NavigationLayout, ZoneConfig } from '@wildo-ai/saas-models';\nimport { NavigationZoneName } from '@wildo-ai/saas-models';\n\nimport { contentAreaFitsSplit } from './split-fit';\n\n/**\n * Is an adjacent zone COLLAPSED right now — too narrow a viewport, or too narrow a content area?\n *\n * ## Why this is one function and not three conditions\n *\n * Three places answer this question, and until 2026-09-25 only one of them answered it completely:\n *\n * | asker | what it decides | what it used to read |\n * |---|---|---|\n * | `navigationPolicyResolver.resolveCollapseMode` | where a CLICK's content lands | viewport + content-area fit — correct |\n * | `NavigationContentAreas` | whether the pane is RENDERED | `isMobile` only |\n * | `NavigationUtils.resolveResourceTargetZone` | where a URL's content lands | nothing — it took no viewport at all |\n *\n * Both gaps produced a silent wrong result:\n *\n * - **The renderer's**: at VERT_TABLET (768–1023px) a declared `responsiveCollapse` retargets every\n *   click away from the pane while the pane keeps rendering — so a zone with `onEmpty: EMPTY_STATE`\n *   showed its \"select an item\" placeholder permanently, next to a list whose clicks went elsewhere.\n * - **The URL path's**: a depth ≥ 1 resource was routed to SECONDARY regardless of viewport, and the\n *   mobile render branch draws PRIMARY and nothing else — so a bookmarked or refreshed nested record\n *   on a phone showed its PARENT, silently. The click path was correct the whole time, which is what\n *   made it invisible: the same content reached the right place when clicked and the wrong place when\n *   linked to. Note the viewport WAS threaded into the adjacent depth-0 branch\n *   (`prefersAdjacentZoneForDetail`) and not into this one — one invariant, two sites, one of them\n *   done (`.claude/rules/invariant-call-site-enumeration.md`).\n *\n * @param contentAreaWidth  `undefined` until the first measurement, which answers \"fits\" — an\n *                          unmeasured area is not a narrow one. See `contentAreaFitsSplit`.\n */\nexport function zoneIsCollapsedAtViewport(params: {\n  zoneConfig: ZoneConfig | undefined;\n  viewport: ViewportBreakpoint | undefined;\n  contentAreaWidth?: number;\n}): boolean {\n  const narrowViewport = params.viewport === ViewportBreakpoint.MOBILE\n    || params.viewport === ViewportBreakpoint.VERT_TABLET;\n  if (narrowViewport) return true;\n  return !contentAreaFitsSplit({\n    contentAreaWidth: params.contentAreaWidth,\n    paneMinWidthPx: params.zoneConfig?.minWidth,\n  });\n}\n\n/**\n * The adjacent zone a URL-restored resource may actually be placed in, or `undefined` when every\n * adjacent zone is collapsed and the content belongs in PRIMARY.\n *\n * The URL path's counterpart to the resolver's collapse handling: same predicate, same inputs, so a\n * deep link and a click cannot disagree about where a record lives at a given width.\n */\nexport function adjacentZoneUsableAtViewport(params: {\n  zone: NavigationZoneName;\n  layout: NavigationLayout | undefined;\n  viewport: ViewportBreakpoint | undefined;\n  contentAreaWidth?: number;\n}): boolean {\n  if (params.zone === NavigationZoneName.PRIMARY) return true;\n  return !zoneIsCollapsedAtViewport({\n    zoneConfig: params.layout?.zones?.[params.zone],\n    viewport: params.viewport,\n    contentAreaWidth: params.contentAreaWidth,\n  });\n}\n"]}

package/dist/esm/core/navigation/zone-content-geometry.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"zone-content-geometry.d.ts","sourceRoot":"","sources":["../../../../../src/core/navigation/zone-content-geometry.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AAEH,OAAO,KAAK,EAAE,kBAAkB,EAAE,MAAM,qCAAqC,CAAC;AAC9E,OAAO,KAAK,EAAE,wBAAwB,EAAE,MAAM,qCAAqC,CAAC;AAGpF,OAAO,KAAK,EAAE,+BAA+B,EAAE,yBAAyB,EAAE,MAAM,8BAA8B,CAAC;AAE/G,mEAAmE;AACnE,MAAM,WAAW,mBAAmB;IAClC,kGAAkG;IAClG,QAAQ,EAAE,kBAAkB,CAAC;IAC7B,uFAAuF;IACvF,WAAW,EAAE,OAAO,CAAC;CACtB;AAED,iGAAiG;AACjG,eAAO,MAAM,6BAA6B,EAAE,mBAAiE,CAAC;AAE9G;;;;;;GAMG;AACH,wBAAgB,iCAAiC,CAAC,MAAM,EAAE;IACxD,cAAc,EAAE,yBAAyB,GAAG,SAAS,CAAC;IACtD,cAAc,EAAE,SAAS,+BAA+B,EAAE,GAAG,SAAS,CAAC;CACxE,GAAG,mBAAmB,CAMtB;AAED;;;;;;;;;;;;;GAaG;AACH,wBAAgB,kCAAkC,CAAC,MAAM,EAAE;IACzD,WAAW,EAAE,yBAAyB,GAAG,SAAS,CAAC;IACnD,cAAc,EAAE,SAAS,+BAA+B,EAAE,GAAG,SAAS,CAAC;CACxE,GAAG,mBAAmB,CAStB;AAED;;;;;GAKG;AACH,wBAAgB,mCAAmC,CACjD,QAAQ,EAAE,mBAAmB,EAC7B,IAAI,EAAE,wBAAwB,GAC7B,wBAAwB,CAI1B;AAED;;;;;;;;;;;GAWG;AACH,wBAAgB,sCAAsC,CAAC,QAAQ,EAAE,mBAAmB,GAAG,MAAM,GAAG,SAAS,CAExG"}
+{"version":3,"file":"zone-content-geometry.d.ts","sourceRoot":"","sources":["../../../../src/core/navigation/zone-content-geometry.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AAEH,OAAO,KAAK,EAAE,kBAAkB,EAAE,MAAM,qCAAqC,CAAC;AAC9E,OAAO,KAAK,EAAE,wBAAwB,EAAE,MAAM,qCAAqC,CAAC;AAGpF,OAAO,KAAK,EAAE,+BAA+B,EAAE,yBAAyB,EAAE,MAAM,8BAA8B,CAAC;AAE/G,mEAAmE;AACnE,MAAM,WAAW,mBAAmB;IAClC,kGAAkG;IAClG,QAAQ,EAAE,kBAAkB,CAAC;IAC7B,uFAAuF;IACvF,WAAW,EAAE,OAAO,CAAC;CACtB;AAED,iGAAiG;AACjG,eAAO,MAAM,6BAA6B,EAAE,mBAAiE,CAAC;AAE9G;;;;;;GAMG;AACH,wBAAgB,iCAAiC,CAAC,MAAM,EAAE;IACxD,cAAc,EAAE,yBAAyB,GAAG,SAAS,CAAC;IACtD,cAAc,EAAE,SAAS,+BAA+B,EAAE,GAAG,SAAS,CAAC;CACxE,GAAG,mBAAmB,CAMtB;AAED;;;;;;;;;;;;;GAaG;AACH,wBAAgB,kCAAkC,CAAC,MAAM,EAAE;IACzD,WAAW,EAAE,yBAAyB,GAAG,SAAS,CAAC;IACnD,cAAc,EAAE,SAAS,+BAA+B,EAAE,GAAG,SAAS,CAAC;CACxE,GAAG,mBAAmB,CAStB;AAED;;;;;GAKG;AACH,wBAAgB,mCAAmC,CACjD,QAAQ,EAAE,mBAAmB,EAC7B,IAAI,EAAE,wBAAwB,GAC7B,wBAAwB,CAI1B;AAED;;;;;;;;;;;GAWG;AACH,wBAAgB,sCAAsC,CAAC,QAAQ,EAAE,mBAAmB,GAAG,MAAM,GAAG,SAAS,CAExG"}

package/dist/esm/core/navigation/zone-content-geometry.js.map

@@ -1 +1 @@
-{"version":3,"file":"zone-content-geometry.js","sourceRoot":"","sources":["../../../../../src/core/navigation/zone-content-geometry.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AAKH,OAAO,EAAE,0CAA0C,EAAE,MAAM,8BAA8B,CAAC;AAW1F,iGAAiG;AACjG,MAAM,CAAC,MAAM,6BAA6B,GAAwB,EAAE,QAAQ,EAAE,SAAS,EAAE,WAAW,EAAE,KAAK,EAAE,CAAC;AAE9G;;;;;;GAMG;AACH,MAAM,UAAU,iCAAiC,CAAC,MAGjD;IACC,MAAM,QAAQ,GAAG,0CAA0C,CAAC,MAAM,CAAC,CAAC;IACpE,OAAO;QACL,QAAQ,EAAE,QAAQ,EAAE,mBAAmB,IAAI,6BAA6B,CAAC,QAAQ;QACjF,WAAW,EAAE,QAAQ,EAAE,sBAAsB,IAAI,6BAA6B,CAAC,WAAW;KAC3F,CAAC;AACJ,CAAC;AAED;;;;;;;;;;;;;GAaG;AACH,MAAM,UAAU,kCAAkC,CAAC,MAGlD;IACC,MAAM,QAAQ,GAAG,0CAA0C,CAAC;QAC1D,cAAc,EAAE,MAAM,CAAC,WAAW;QAClC,cAAc,EAAE,MAAM,CAAC,cAAc;KACtC,CAAC,CAAC;IACH,OAAO;QACL,QAAQ,EAAE,QAAQ,EAAE,mBAAmB,IAAI,6BAA6B,CAAC,QAAQ;QACjF,WAAW,EAAE,KAAK;KACnB,CAAC;AACJ,CAAC;AAED;;;;;GAKG;AACH,MAAM,UAAU,mCAAmC,CACjD,QAA6B,EAC7B,IAA8B;IAE9B,OAAO,QAAQ,CAAC,QAAQ,KAAK,6BAA6B,CAAC,QAAQ;QACjE,CAAC,CAAC,IAAI;QACN,CAAC,CAAC,EAAE,GAAG,IAAI,EAAE,QAAQ,EAAE,EAAE,kBAAkB,EAAE,QAAQ,CAAC,QAAQ,EAAE,EAAE,CAAC;AACvE,CAAC;AAED;;;;;;;;;;;GAWG;AACH,MAAM,UAAU,sCAAsC,CAAC,QAA6B;IAClF,OAAO,QAAQ,CAAC,WAAW,CAAC,CAAC,CAAC,8BAA8B,CAAC,CAAC,CAAC,SAAS,CAAC;AAC3E,CAAC","sourcesContent":["/**\n * Zone content geometry (#176) — how much of a zone a destination's content occupies.\n *\n * ## Two axes, deliberately not one enum\n *\n * This replaced `ZoneContentFill`, a three-member enum — `NONE` / `WIDTH` / `BOTH` — that fused a\n * WIDTH decision and a HEIGHT decision into one value. Three points on a 2×2 grid: `NONE`→`WIDTH`\n * moved the width, `WIDTH`→`BOTH` moved the height, and the fourth cell (a capped width with a\n * definite height) was unrepresentable. Its width half also restated `ResponsiveMaxWidth`, the\n * vocabulary a Surface, a `DisplayLayout` and a `FormLayout` already use — so the same question had\n * two answers with different spellings depending on which level you asked.\n *\n * Splitting them costs one extra field and buys the missing cell, one vocabulary for width across\n * every level, and a height flag that reads as what it is. `design-philosophy.md` says not to merge\n * semantically distinct concepts for convenience; this is that rule applied to something that had\n * already shipped.\n *\n * ## What the boundary is for\n *\n * The boundary caps and centres a zone's content, and its defaults are RIGHT for almost everything a\n * zone hosts: a form, a list or a settings page stretched across a wide monitor is unreadable. What\n * did not exist before #176 was a way to say \"this one is a canvas\" — so the one surface that needed\n * it hand-rolled `h-[70vh]`, sizing against the WINDOW rather than its container and ignoring whatever\n * chrome sat above it.\n *\n * The defaults are preserved rather than inverted: every surface authored before this existed keeps\n * `'content'` and a natural height, and opting out is per-destination and explicit. The alternative\n * door — the application-wide `--content-max-width` variable — is the one that already existed and is\n * the reason the issue was filed: uncapping a graph that way uncaps every form in the application.\n */\n\nimport type { ResponsiveMaxWidth } from '@wildo-ai/presets-components-models';\nimport type { DeepPartialSurfacePolicy } from '@wildo-ai/presets-components-models';\n\nimport { resolvePrimaryDestinationLayoutDeclaration } from './primary-destination-layout';\nimport type { PrimaryDestinationCompositeView, PrimaryDestinationContent } from './primary-destination-layout';\n\n/** The two independent answers a zone's content boundary needs. */\nexport interface ZoneContentGeometry {\n  /** The width cap, in the framework's shared vocabulary. `'content'` is the historical default. */\n  maxWidth: ResponsiveMaxWidth;\n  /** Whether the boundary becomes a definite-height flex column the content can fill. */\n  fillsHeight: boolean;\n}\n\n/** What a destination that declares nothing receives — and what every pre-#176 surface keeps. */\nexport const DEFAULT_ZONE_CONTENT_GEOMETRY: ZoneContentGeometry = { maxWidth: 'content', fillsHeight: false };\n\n/**\n * Read the geometry off whatever occupies PRIMARY, defaulting to {@link DEFAULT_ZONE_CONTENT_GEOMETRY}.\n *\n * Defaults HERE rather than at the declaration sites so there is one answer to \"what does a destination\n * that declares nothing get\", and it is the same answer for a composite view, a resource operation, a\n * content kind that cannot declare, and an empty primary stack.\n */\nexport function resolvePrimaryZoneContentGeometry(params: {\n  primaryContent: PrimaryDestinationContent | undefined;\n  compositeViews: readonly PrimaryDestinationCompositeView[] | undefined;\n}): ZoneContentGeometry {\n  const declared = resolvePrimaryDestinationLayoutDeclaration(params);\n  return {\n    maxWidth: declared?.zoneContentMaxWidth ?? DEFAULT_ZONE_CONTENT_GEOMETRY.maxWidth,\n    fillsHeight: declared?.zoneContentFillsHeight ?? DEFAULT_ZONE_CONTENT_GEOMETRY.fillsHeight,\n  };\n}\n\n/**\n * The geometry for an ADJACENT zone's content.\n *\n * Adjacent zones had no content boundary at all before #176: a detail pane's width was decided by\n * whatever component happened to be rendered in it, so the workbench's artifact detail capped itself\n * and centred — an application solving, locally and invisibly, a question the engine had not answered.\n * The answer is the one primary already gets: cap at the page-content width and fill anything narrower.\n * A detail pane is usually narrower than that cap, so in practice the content fills the pane, which is\n * what \"full width, up to a maximum\" describes without the pane having to know its own size.\n *\n * `fillsHeight` is forced FALSE here, whatever the destination declared. Filling the height requires a\n * definite-height ancestor chain and an adjacent zone SCROLLS — it is the one place where a filling\n * child and a scrolling parent contradict each other. A canvas belongs in primary.\n */\nexport function resolveAdjacentZoneContentGeometry(params: {\n  zoneContent: PrimaryDestinationContent | undefined;\n  compositeViews: readonly PrimaryDestinationCompositeView[] | undefined;\n}): ZoneContentGeometry {\n  const declared = resolvePrimaryDestinationLayoutDeclaration({\n    primaryContent: params.zoneContent,\n    compositeViews: params.compositeViews,\n  });\n  return {\n    maxWidth: declared?.zoneContentMaxWidth ?? DEFAULT_ZONE_CONTENT_GEOMETRY.maxWidth,\n    fillsHeight: false,\n  };\n}\n\n/**\n * The boundary's surface policy for a given geometry.\n *\n * The width rides the policy because that is the framework's declared channel for it — the same field\n * a Surface anywhere else sets, so the boundary announces its tier in the DOM like every other cap.\n */\nexport function zoneContentGeometryToPolicyOverride(\n  geometry: ZoneContentGeometry,\n  base: DeepPartialSurfacePolicy,\n): DeepPartialSurfacePolicy {\n  return geometry.maxWidth === DEFAULT_ZONE_CONTENT_GEOMETRY.maxWidth\n    ? base\n    : { ...base, geometry: { responsiveMaxWidth: geometry.maxWidth } };\n}\n\n/**\n * Extra classes the boundary element needs so filling content can actually fill.\n *\n * This is the half a surface policy cannot express. Filling the HEIGHT is not a property of the\n * boundary's own box — it is a property of the CHAIN: the boundary must become a definite-height flex\n * column so that the view's root, as its flex item, has something for `flex-1 min-h-0` to resolve\n * against. `h-full` alone is not enough (an auto-height parent gives a percentage height nothing to\n * measure), which is precisely why the previous state forced viewport fractions.\n *\n * `min-h-0` is what lets the column shrink rather than overflow its zone; without it a tall child\n * pushes the boundary past the content area and the zone's own scroll never engages.\n */\nexport function zoneContentGeometryToBoundaryClassName(geometry: ZoneContentGeometry): string | undefined {\n  return geometry.fillsHeight ? 'flex h-full min-h-0 flex-col' : undefined;\n}\n"]}
+{"version":3,"file":"zone-content-geometry.js","sourceRoot":"","sources":["../../../../src/core/navigation/zone-content-geometry.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AAKH,OAAO,EAAE,0CAA0C,EAAE,MAAM,8BAA8B,CAAC;AAW1F,iGAAiG;AACjG,MAAM,CAAC,MAAM,6BAA6B,GAAwB,EAAE,QAAQ,EAAE,SAAS,EAAE,WAAW,EAAE,KAAK,EAAE,CAAC;AAE9G;;;;;;GAMG;AACH,MAAM,UAAU,iCAAiC,CAAC,MAGjD;IACC,MAAM,QAAQ,GAAG,0CAA0C,CAAC,MAAM,CAAC,CAAC;IACpE,OAAO;QACL,QAAQ,EAAE,QAAQ,EAAE,mBAAmB,IAAI,6BAA6B,CAAC,QAAQ;QACjF,WAAW,EAAE,QAAQ,EAAE,sBAAsB,IAAI,6BAA6B,CAAC,WAAW;KAC3F,CAAC;AACJ,CAAC;AAED;;;;;;;;;;;;;GAaG;AACH,MAAM,UAAU,kCAAkC,CAAC,MAGlD;IACC,MAAM,QAAQ,GAAG,0CAA0C,CAAC;QAC1D,cAAc,EAAE,MAAM,CAAC,WAAW;QAClC,cAAc,EAAE,MAAM,CAAC,cAAc;KACtC,CAAC,CAAC;IACH,OAAO;QACL,QAAQ,EAAE,QAAQ,EAAE,mBAAmB,IAAI,6BAA6B,CAAC,QAAQ;QACjF,WAAW,EAAE,KAAK;KACnB,CAAC;AACJ,CAAC;AAED;;;;;GAKG;AACH,MAAM,UAAU,mCAAmC,CACjD,QAA6B,EAC7B,IAA8B;IAE9B,OAAO,QAAQ,CAAC,QAAQ,KAAK,6BAA6B,CAAC,QAAQ;QACjE,CAAC,CAAC,IAAI;QACN,CAAC,CAAC,EAAE,GAAG,IAAI,EAAE,QAAQ,EAAE,EAAE,kBAAkB,EAAE,QAAQ,CAAC,QAAQ,EAAE,EAAE,CAAC;AACvE,CAAC;AAED;;;;;;;;;;;GAWG;AACH,MAAM,UAAU,sCAAsC,CAAC,QAA6B;IAClF,OAAO,QAAQ,CAAC,WAAW,CAAC,CAAC,CAAC,8BAA8B,CAAC,CAAC,CAAC,SAAS,CAAC;AAC3E,CAAC","sourcesContent":["/**\n * Zone content geometry (#176) — how much of a zone a destination's content occupies.\n *\n * ## Two axes, deliberately not one enum\n *\n * This replaced `ZoneContentFill`, a three-member enum — `NONE` / `WIDTH` / `BOTH` — that fused a\n * WIDTH decision and a HEIGHT decision into one value. Three points on a 2×2 grid: `NONE`→`WIDTH`\n * moved the width, `WIDTH`→`BOTH` moved the height, and the fourth cell (a capped width with a\n * definite height) was unrepresentable. Its width half also restated `ResponsiveMaxWidth`, the\n * vocabulary a Surface, a `DisplayLayout` and a `FormLayout` already use — so the same question had\n * two answers with different spellings depending on which level you asked.\n *\n * Splitting them costs one extra field and buys the missing cell, one vocabulary for width across\n * every level, and a height flag that reads as what it is. `design-philosophy.md` says not to merge\n * semantically distinct concepts for convenience; this is that rule applied to something that had\n * already shipped.\n *\n * ## What the boundary is for\n *\n * The boundary caps and centres a zone's content, and its defaults are RIGHT for almost everything a\n * zone hosts: a form, a list or a settings page stretched across a wide monitor is unreadable. What\n * did not exist before #176 was a way to say \"this one is a canvas\" — so the one surface that needed\n * it hand-rolled `h-[70vh]`, sizing against the WINDOW rather than its container and ignoring whatever\n * chrome sat above it.\n *\n * The defaults are preserved rather than inverted: every surface authored before this existed keeps\n * `'content'` and a natural height, and opting out is per-destination and explicit. The alternative\n * door — the application-wide `--content-max-width` variable — is the one that already existed and is\n * the reason the issue was filed: uncapping a graph that way uncaps every form in the application.\n */\n\nimport type { ResponsiveMaxWidth } from '@wildo-ai/presets-components-models';\nimport type { DeepPartialSurfacePolicy } from '@wildo-ai/presets-components-models';\n\nimport { resolvePrimaryDestinationLayoutDeclaration } from './primary-destination-layout';\nimport type { PrimaryDestinationCompositeView, PrimaryDestinationContent } from './primary-destination-layout';\n\n/** The two independent answers a zone's content boundary needs. */\nexport interface ZoneContentGeometry {\n  /** The width cap, in the framework's shared vocabulary. `'content'` is the historical default. */\n  maxWidth: ResponsiveMaxWidth;\n  /** Whether the boundary becomes a definite-height flex column the content can fill. */\n  fillsHeight: boolean;\n}\n\n/** What a destination that declares nothing receives — and what every pre-#176 surface keeps. */\nexport const DEFAULT_ZONE_CONTENT_GEOMETRY: ZoneContentGeometry = { maxWidth: 'content', fillsHeight: false };\n\n/**\n * Read the geometry off whatever occupies PRIMARY, defaulting to {@link DEFAULT_ZONE_CONTENT_GEOMETRY}.\n *\n * Defaults HERE rather than at the declaration sites so there is one answer to \"what does a destination\n * that declares nothing get\", and it is the same answer for a composite view, a resource operation, a\n * content kind that cannot declare, and an empty primary stack.\n */\nexport function resolvePrimaryZoneContentGeometry(params: {\n  primaryContent: PrimaryDestinationContent | undefined;\n  compositeViews: readonly PrimaryDestinationCompositeView[] | undefined;\n}): ZoneContentGeometry {\n  const declared = resolvePrimaryDestinationLayoutDeclaration(params);\n  return {\n    maxWidth: declared?.zoneContentMaxWidth ?? DEFAULT_ZONE_CONTENT_GEOMETRY.maxWidth,\n    fillsHeight: declared?.zoneContentFillsHeight ?? DEFAULT_ZONE_CONTENT_GEOMETRY.fillsHeight,\n  };\n}\n\n/**\n * The geometry for an ADJACENT zone's content.\n *\n * Adjacent zones had no content boundary at all before #176: a detail pane's width was decided by\n * whatever component happened to be rendered in it, so the workbench's artifact detail capped itself\n * and centred — an application solving, locally and invisibly, a question the engine had not answered.\n * The answer is the one primary already gets: cap at the page-content width and fill anything narrower.\n * A detail pane is usually narrower than that cap, so in practice the content fills the pane, which is\n * what \"full width, up to a maximum\" describes without the pane having to know its own size.\n *\n * `fillsHeight` is forced FALSE here, whatever the destination declared. Filling the height requires a\n * definite-height ancestor chain and an adjacent zone SCROLLS — it is the one place where a filling\n * child and a scrolling parent contradict each other. A canvas belongs in primary.\n */\nexport function resolveAdjacentZoneContentGeometry(params: {\n  zoneContent: PrimaryDestinationContent | undefined;\n  compositeViews: readonly PrimaryDestinationCompositeView[] | undefined;\n}): ZoneContentGeometry {\n  const declared = resolvePrimaryDestinationLayoutDeclaration({\n    primaryContent: params.zoneContent,\n    compositeViews: params.compositeViews,\n  });\n  return {\n    maxWidth: declared?.zoneContentMaxWidth ?? DEFAULT_ZONE_CONTENT_GEOMETRY.maxWidth,\n    fillsHeight: false,\n  };\n}\n\n/**\n * The boundary's surface policy for a given geometry.\n *\n * The width rides the policy because that is the framework's declared channel for it — the same field\n * a Surface anywhere else sets, so the boundary announces its tier in the DOM like every other cap.\n */\nexport function zoneContentGeometryToPolicyOverride(\n  geometry: ZoneContentGeometry,\n  base: DeepPartialSurfacePolicy,\n): DeepPartialSurfacePolicy {\n  return geometry.maxWidth === DEFAULT_ZONE_CONTENT_GEOMETRY.maxWidth\n    ? base\n    : { ...base, geometry: { responsiveMaxWidth: geometry.maxWidth } };\n}\n\n/**\n * Extra classes the boundary element needs so filling content can actually fill.\n *\n * This is the half a surface policy cannot express. Filling the HEIGHT is not a property of the\n * boundary's own box — it is a property of the CHAIN: the boundary must become a definite-height flex\n * column so that the view's root, as its flex item, has something for `flex-1 min-h-0` to resolve\n * against. `h-full` alone is not enough (an auto-height parent gives a percentage height nothing to\n * measure), which is precisely why the previous state forced viewport fractions.\n *\n * `min-h-0` is what lets the column shrink rather than overflow its zone; without it a tall child\n * pushes the boundary past the content area and the zone's own scroll never engages.\n */\nexport function zoneContentGeometryToBoundaryClassName(geometry: ZoneContentGeometry): string | undefined {\n  return geometry.fillsHeight ? 'flex h-full min-h-0 flex-col' : undefined;\n}\n"]}

package/dist/esm/core/navigation/zone-emphasis.d.ts

@@ -23,6 +23,9 @@ export declare function resolveEmphasizedZone(input: {
     isMobile: boolean;
     secondaryShown: boolean;
     companionShown: boolean;
+    /** Does the zone actually HOLD something? See the emptiness rule below. */
+    secondaryHasContent: boolean;
+    companionHasContent: boolean;
 }): NavigationZoneName.SECONDARY | NavigationZoneName.COMPANION | null;
 /**
  * Whether a keyboard Escape should restore the split.

package/dist/esm/core/navigation/zone-emphasis.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"zone-emphasis.d.ts","sourceRoot":"","sources":["../../../../../src/core/navigation/zone-emphasis.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,kBAAkB,EAAE,MAAM,uBAAuB,CAAC;AAE3D;;;;;;;;;;;;;;;;;;GAkBG;AACH,wBAAgB,qBAAqB,CAAC,KAAK,EAAE;IAC3C,SAAS,EAAE,kBAAkB,GAAG,IAAI,CAAC;IACrC,QAAQ,EAAE,OAAO,CAAC;IAClB,cAAc,EAAE,OAAO,CAAC;IACxB,cAAc,EAAE,OAAO,CAAC;CACzB,GAAG,kBAAkB,CAAC,SAAS,GAAG,kBAAkB,CAAC,SAAS,GAAG,IAAI,CAKrE;AAED;;;;;;;;GAQG;AACH,wBAAgB,sBAAsB,CAAC,KAAK,EAAE;IAC5C,GAAG,EAAE,MAAM,CAAC;IACZ,UAAU,EAAE,OAAO,CAAC;IACpB,WAAW,EAAE,OAAO,CAAC;IACrB,MAAM,EAAE,WAAW,GAAG,IAAI,CAAC;CAC5B,GAAG,OAAO,CAOV"}
+{"version":3,"file":"zone-emphasis.d.ts","sourceRoot":"","sources":["../../../../src/core/navigation/zone-emphasis.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,kBAAkB,EAAE,MAAM,uBAAuB,CAAC;AAE3D;;;;;;;;;;;;;;;;;;GAkBG;AAqBH,wBAAgB,qBAAqB,CAAC,KAAK,EAAE;IAC3C,SAAS,EAAE,kBAAkB,GAAG,IAAI,CAAC;IACrC,QAAQ,EAAE,OAAO,CAAC;IAClB,cAAc,EAAE,OAAO,CAAC;IACxB,cAAc,EAAE,OAAO,CAAC;IACxB,2EAA2E;IAC3E,mBAAmB,EAAE,OAAO,CAAC;IAC7B,mBAAmB,EAAE,OAAO,CAAC;CAC9B,GAAG,kBAAkB,CAAC,SAAS,GAAG,kBAAkB,CAAC,SAAS,GAAG,IAAI,CASrE;AAED;;;;;;;;GAQG;AACH,wBAAgB,sBAAsB,CAAC,KAAK,EAAE;IAC5C,GAAG,EAAE,MAAM,CAAC;IACZ,UAAU,EAAE,OAAO,CAAC;IACpB,WAAW,EAAE,OAAO,CAAC;IACrB,MAAM,EAAE,WAAW,GAAG,IAAI,CAAC;CAC5B,GAAG,OAAO,CAOV"}

package/dist/esm/core/navigation/zone-emphasis.js

@@ -18,13 +18,35 @@ import { NavigationZoneName } from '@wildo-ai/saas-models';
  * to a responsive collapse and got it back should find it expanded again; clearing the request on
  * every non-honouring render would make emphasis flicker off under them.
  */
+/*
+ * ─── AN EMPTY ZONE IS NEVER EMPHASIZED, and that closes two ways of hiding the whole page ────────
+ *
+ * Emphasis hides every other structural zone, PRIMARY included (`primaryHidden = emphasized !== null`).
+ * Until 2026-09-25 it was released only when the requested zone was not SHOWN — and a zone whose
+ * `onEmpty` resolves to `EMPTY_STATE` is shown WHILE EMPTY, by construction.
+ *
+ * 1. **The pane empties while emphasized.** Navigate primary, let the dependency cleanup clear the
+ *    pane, or pop its last entry: the zone keeps its width, keeps being shown, keeps being
+ *    emphasized — and the entire content area becomes the pane's empty-state placeholder with the
+ *    page behind it `display: none`. An `EMPTY_STATE` zone is deliberately NOT dismissable
+ *    (`zoneIsDismissable`), so the only ways out were Escape and the emphasis toggle.
+ * 2. **The reader navigates the app.** Nothing cleared emphasis on navigation, so a sidebar click
+ *    mounted the new destination in a hidden PRIMARY. This rule covers that case too rather than
+ *    needing its own: an app-level navigation is a clean break, the clean break clears the adjacent
+ *    zones, and a cleared zone now releases emphasis.
+ *
+ * "Shown" and "holds something" are different questions, and emphasis needs both. Asking only the
+ * first is what made an empty pane able to take the whole window.
+ */
 export function resolveEmphasizedZone(input) {
     if (input.requested === null || input.isMobile)
         return null;
-    if (input.requested === NavigationZoneName.SECONDARY)
-        return input.secondaryShown ? NavigationZoneName.SECONDARY : null;
-    if (input.requested === NavigationZoneName.COMPANION)
-        return input.companionShown ? NavigationZoneName.COMPANION : null;
+    if (input.requested === NavigationZoneName.SECONDARY) {
+        return input.secondaryShown && input.secondaryHasContent ? NavigationZoneName.SECONDARY : null;
+    }
+    if (input.requested === NavigationZoneName.COMPANION) {
+        return input.companionShown && input.companionHasContent ? NavigationZoneName.COMPANION : null;
+    }
     return null;
 }
 /**

package/dist/esm/core/navigation/zone-emphasis.js.map

@@ -1 +1 @@
-{"version":3,"file":"zone-emphasis.js","sourceRoot":"","sources":["../../../../../src/core/navigation/zone-emphasis.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,kBAAkB,EAAE,MAAM,uBAAuB,CAAC;AAE3D;;;;;;;;;;;;;;;;;;GAkBG;AACH,MAAM,UAAU,qBAAqB,CAAC,KAKrC;IACC,IAAI,KAAK,CAAC,SAAS,KAAK,IAAI,IAAI,KAAK,CAAC,QAAQ;QAAE,OAAO,IAAI,CAAC;IAC5D,IAAI,KAAK,CAAC,SAAS,KAAK,kBAAkB,CAAC,SAAS;QAAE,OAAO,KAAK,CAAC,cAAc,CAAC,CAAC,CAAC,kBAAkB,CAAC,SAAS,CAAC,CAAC,CAAC,IAAI,CAAC;IACxH,IAAI,KAAK,CAAC,SAAS,KAAK,kBAAkB,CAAC,SAAS;QAAE,OAAO,KAAK,CAAC,cAAc,CAAC,CAAC,CAAC,kBAAkB,CAAC,SAAS,CAAC,CAAC,CAAC,IAAI,CAAC;IACxH,OAAO,IAAI,CAAC;AACd,CAAC;AAED;;;;;;;;GAQG;AACH,MAAM,UAAU,sBAAsB,CAAC,KAKtC;IACC,IAAI,KAAK,CAAC,GAAG,KAAK,QAAQ,IAAI,CAAC,KAAK,CAAC,UAAU,IAAI,KAAK,CAAC,WAAW;QAAE,OAAO,KAAK,CAAC;IACnF,MAAM,OAAO,GAAG,KAAK,CAAC,MAAM,YAAY,WAAW,CAAC,CAAC,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC,CAAC,IAAI,CAAC;IAC1E,IAAI,OAAO,KAAK,IAAI;QAAE,OAAO,IAAI,CAAC;IAClC,IAAI,OAAO,CAAC,iBAAiB;QAAE,OAAO,KAAK,CAAC;IAC5C,MAAM,GAAG,GAAG,OAAO,CAAC,OAAO,CAAC;IAC5B,OAAO,GAAG,KAAK,OAAO,IAAI,GAAG,KAAK,UAAU,IAAI,GAAG,KAAK,QAAQ,CAAC;AACnE,CAAC","sourcesContent":["import { NavigationZoneName } from '@wildo-ai/saas-models';\n\n/**\n * The zone that actually takes the whole content area this render, given what the reader asked for\n * and what the layout can currently show.\n *\n * Pure, so the rule is pinned without a provider stack. The reader's request\n * (`NavigationContextType.emphasizedZone`) is a wish; this is the decision, and it yields the area\n * back in every case where honouring the wish would hide the page:\n *\n * - on MOBILE there is one zone already, so emphasis means nothing;\n * - a zone with NOTHING IN IT cannot be emphasized — an empty full-width pane over a hidden list is\n *   the blank screen the request was never about;\n * - PRIMARY is never emphasized: it has the whole area whenever nothing is beside it, and hiding the\n *   adjacent zones to \"emphasize\" primary would be the same as closing them, which is a navigation\n *   act with its own verbs.\n *\n * The request itself is left standing when it is not honoured. A reader who expanded a pane, lost it\n * to a responsive collapse and got it back should find it expanded again; clearing the request on\n * every non-honouring render would make emphasis flicker off under them.\n */\nexport function resolveEmphasizedZone(input: {\n  requested: NavigationZoneName | null;\n  isMobile: boolean;\n  secondaryShown: boolean;\n  companionShown: boolean;\n}): NavigationZoneName.SECONDARY | NavigationZoneName.COMPANION | null {\n  if (input.requested === null || input.isMobile) return null;\n  if (input.requested === NavigationZoneName.SECONDARY) return input.secondaryShown ? NavigationZoneName.SECONDARY : null;\n  if (input.requested === NavigationZoneName.COMPANION) return input.companionShown ? NavigationZoneName.COMPANION : null;\n  return null;\n}\n\n/**\n * Whether a keyboard Escape should restore the split.\n *\n * Escape is the universal \"leave this mode\" key and it is also what every text control, menu and\n * dialog listens for. Emphasis yields to all of them: a key pressed inside an editable control is\n * that control's, and a key pressed while an overlay is open belongs to the overlay (the overlay\n * layer sits above the content areas and has its own dismissal). What is left — Escape on the page\n * itself while a pane is emphasized — restores the split.\n */\nexport function escapeRestoresEmphasis(input: {\n  key: string;\n  emphasized: boolean;\n  overlayOpen: boolean;\n  target: EventTarget | null;\n}): boolean {\n  if (input.key !== 'Escape' || !input.emphasized || input.overlayOpen) return false;\n  const element = input.target instanceof HTMLElement ? input.target : null;\n  if (element === null) return true;\n  if (element.isContentEditable) return false;\n  const tag = element.tagName;\n  return tag !== 'INPUT' && tag !== 'TEXTAREA' && tag !== 'SELECT';\n}\n"]}
+{"version":3,"file":"zone-emphasis.js","sourceRoot":"","sources":["../../../../src/core/navigation/zone-emphasis.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,kBAAkB,EAAE,MAAM,uBAAuB,CAAC;AAE3D;;;;;;;;;;;;;;;;;;GAkBG;AACH;;;;;;;;;;;;;;;;;;;GAmBG;AACH,MAAM,UAAU,qBAAqB,CAAC,KAQrC;IACC,IAAI,KAAK,CAAC,SAAS,KAAK,IAAI,IAAI,KAAK,CAAC,QAAQ;QAAE,OAAO,IAAI,CAAC;IAC5D,IAAI,KAAK,CAAC,SAAS,KAAK,kBAAkB,CAAC,SAAS,EAAE,CAAC;QACrD,OAAO,KAAK,CAAC,cAAc,IAAI,KAAK,CAAC,mBAAmB,CAAC,CAAC,CAAC,kBAAkB,CAAC,SAAS,CAAC,CAAC,CAAC,IAAI,CAAC;IACjG,CAAC;IACD,IAAI,KAAK,CAAC,SAAS,KAAK,kBAAkB,CAAC,SAAS,EAAE,CAAC;QACrD,OAAO,KAAK,CAAC,cAAc,IAAI,KAAK,CAAC,mBAAmB,CAAC,CAAC,CAAC,kBAAkB,CAAC,SAAS,CAAC,CAAC,CAAC,IAAI,CAAC;IACjG,CAAC;IACD,OAAO,IAAI,CAAC;AACd,CAAC;AAED;;;;;;;;GAQG;AACH,MAAM,UAAU,sBAAsB,CAAC,KAKtC;IACC,IAAI,KAAK,CAAC,GAAG,KAAK,QAAQ,IAAI,CAAC,KAAK,CAAC,UAAU,IAAI,KAAK,CAAC,WAAW;QAAE,OAAO,KAAK,CAAC;IACnF,MAAM,OAAO,GAAG,KAAK,CAAC,MAAM,YAAY,WAAW,CAAC,CAAC,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC,CAAC,IAAI,CAAC;IAC1E,IAAI,OAAO,KAAK,IAAI;QAAE,OAAO,IAAI,CAAC;IAClC,IAAI,OAAO,CAAC,iBAAiB;QAAE,OAAO,KAAK,CAAC;IAC5C,MAAM,GAAG,GAAG,OAAO,CAAC,OAAO,CAAC;IAC5B,OAAO,GAAG,KAAK,OAAO,IAAI,GAAG,KAAK,UAAU,IAAI,GAAG,KAAK,QAAQ,CAAC;AACnE,CAAC","sourcesContent":["import { NavigationZoneName } from '@wildo-ai/saas-models';\n\n/**\n * The zone that actually takes the whole content area this render, given what the reader asked for\n * and what the layout can currently show.\n *\n * Pure, so the rule is pinned without a provider stack. The reader's request\n * (`NavigationContextType.emphasizedZone`) is a wish; this is the decision, and it yields the area\n * back in every case where honouring the wish would hide the page:\n *\n * - on MOBILE there is one zone already, so emphasis means nothing;\n * - a zone with NOTHING IN IT cannot be emphasized — an empty full-width pane over a hidden list is\n *   the blank screen the request was never about;\n * - PRIMARY is never emphasized: it has the whole area whenever nothing is beside it, and hiding the\n *   adjacent zones to \"emphasize\" primary would be the same as closing them, which is a navigation\n *   act with its own verbs.\n *\n * The request itself is left standing when it is not honoured. A reader who expanded a pane, lost it\n * to a responsive collapse and got it back should find it expanded again; clearing the request on\n * every non-honouring render would make emphasis flicker off under them.\n */\n/*\n * ─── AN EMPTY ZONE IS NEVER EMPHASIZED, and that closes two ways of hiding the whole page ────────\n *\n * Emphasis hides every other structural zone, PRIMARY included (`primaryHidden = emphasized !== null`).\n * Until 2026-09-25 it was released only when the requested zone was not SHOWN — and a zone whose\n * `onEmpty` resolves to `EMPTY_STATE` is shown WHILE EMPTY, by construction.\n *\n * 1. **The pane empties while emphasized.** Navigate primary, let the dependency cleanup clear the\n *    pane, or pop its last entry: the zone keeps its width, keeps being shown, keeps being\n *    emphasized — and the entire content area becomes the pane's empty-state placeholder with the\n *    page behind it `display: none`. An `EMPTY_STATE` zone is deliberately NOT dismissable\n *    (`zoneIsDismissable`), so the only ways out were Escape and the emphasis toggle.\n * 2. **The reader navigates the app.** Nothing cleared emphasis on navigation, so a sidebar click\n *    mounted the new destination in a hidden PRIMARY. This rule covers that case too rather than\n *    needing its own: an app-level navigation is a clean break, the clean break clears the adjacent\n *    zones, and a cleared zone now releases emphasis.\n *\n * \"Shown\" and \"holds something\" are different questions, and emphasis needs both. Asking only the\n * first is what made an empty pane able to take the whole window.\n */\nexport function resolveEmphasizedZone(input: {\n  requested: NavigationZoneName | null;\n  isMobile: boolean;\n  secondaryShown: boolean;\n  companionShown: boolean;\n  /** Does the zone actually HOLD something? See the emptiness rule below. */\n  secondaryHasContent: boolean;\n  companionHasContent: boolean;\n}): NavigationZoneName.SECONDARY | NavigationZoneName.COMPANION | null {\n  if (input.requested === null || input.isMobile) return null;\n  if (input.requested === NavigationZoneName.SECONDARY) {\n    return input.secondaryShown && input.secondaryHasContent ? NavigationZoneName.SECONDARY : null;\n  }\n  if (input.requested === NavigationZoneName.COMPANION) {\n    return input.companionShown && input.companionHasContent ? NavigationZoneName.COMPANION : null;\n  }\n  return null;\n}\n\n/**\n * Whether a keyboard Escape should restore the split.\n *\n * Escape is the universal \"leave this mode\" key and it is also what every text control, menu and\n * dialog listens for. Emphasis yields to all of them: a key pressed inside an editable control is\n * that control's, and a key pressed while an overlay is open belongs to the overlay (the overlay\n * layer sits above the content areas and has its own dismissal). What is left — Escape on the page\n * itself while a pane is emphasized — restores the split.\n */\nexport function escapeRestoresEmphasis(input: {\n  key: string;\n  emphasized: boolean;\n  overlayOpen: boolean;\n  target: EventTarget | null;\n}): boolean {\n  if (input.key !== 'Escape' || !input.emphasized || input.overlayOpen) return false;\n  const element = input.target instanceof HTMLElement ? input.target : null;\n  if (element === null) return true;\n  if (element.isContentEditable) return false;\n  const tag = element.tagName;\n  return tag !== 'INPUT' && tag !== 'TEXTAREA' && tag !== 'SELECT';\n}\n"]}

package/dist/esm/core/navigation/zone-empty-behavior.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"zone-empty-behavior.d.ts","sourceRoot":"","sources":["../../../../../src/core/navigation/zone-empty-behavior.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AAEH,OAAO,EAAE,kBAAkB,EAAE,iBAAiB,EAAE,MAAM,uBAAuB,CAAC;AAC9E,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,uBAAuB,CAAC;AAG9D,OAAO,KAAK,EAAE,+BAA+B,EAAE,yBAAyB,EAAE,MAAM,8BAA8B,CAAC;AAE/G;;;;;;;GAOG;AACH,MAAM,WAAW,uBAAuB;IACtC,mGAAmG;IACnG,IAAI,EAAE,kBAAkB,CAAC;IACzB,4FAA4F;IAC5F,KAAK,EAAE,gBAAgB,CAAC,OAAO,CAAC,GAAG,SAAS,CAAC;IAC7C;;;OAGG;IACH,mBAAmB,EAAE,iBAAiB,GAAG,SAAS,CAAC;CACpD;AAED;;;;;;GAMG;AACH,wBAAgB,wBAAwB,CAAC,EACvC,IAAI,EACJ,KAAK,EACL,mBAAmB,GACpB,EAAE,uBAAuB,GAAG,iBAAiB,CAO7C;AAED;;;;;;;GAOG;AACH,wBAAgB,0BAA0B,CAAC,QAAQ,EAAE,iBAAiB,GAAG,OAAO,CAE/E;AAED;;;;;;;;;;;;;;;;;GAiBG;AACH,wBAAgB,iBAAiB,CAAC,MAAM,EAAE;IAAE,UAAU,EAAE,OAAO,CAAC;IAAC,QAAQ,EAAE,iBAAiB,CAAA;CAAE,GAAG,OAAO,CAEvG;AAED;;;;;;GAMG;AACH,wBAAgB,4CAA4C,CAAC,MAAM,EAAE;IACnE,cAAc,EAAE,yBAAyB,GAAG,SAAS,CAAC;IACtD,cAAc,EAAE,SAAS,+BAA+B,EAAE,GAAG,SAAS,CAAC;CACxE,GAAG,iBAAiB,GAAG,SAAS,CAEhC"}
+{"version":3,"file":"zone-empty-behavior.d.ts","sourceRoot":"","sources":["../../../../src/core/navigation/zone-empty-behavior.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AAEH,OAAO,EAAE,kBAAkB,EAAE,iBAAiB,EAAE,MAAM,uBAAuB,CAAC;AAC9E,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,uBAAuB,CAAC;AAG9D,OAAO,KAAK,EAAE,+BAA+B,EAAE,yBAAyB,EAAE,MAAM,8BAA8B,CAAC;AAE/G;;;;;;;GAOG;AACH,MAAM,WAAW,uBAAuB;IACtC,mGAAmG;IACnG,IAAI,EAAE,kBAAkB,CAAC;IACzB,4FAA4F;IAC5F,KAAK,EAAE,gBAAgB,CAAC,OAAO,CAAC,GAAG,SAAS,CAAC;IAC7C;;;OAGG;IACH,mBAAmB,EAAE,iBAAiB,GAAG,SAAS,CAAC;CACpD;AAED;;;;;;GAMG;AACH,wBAAgB,wBAAwB,CAAC,EACvC,IAAI,EACJ,KAAK,EACL,mBAAmB,GACpB,EAAE,uBAAuB,GAAG,iBAAiB,CAO7C;AAED;;;;;;;GAOG;AACH,wBAAgB,0BAA0B,CAAC,QAAQ,EAAE,iBAAiB,GAAG,OAAO,CAE/E;AAED;;;;;;;;;;;;;;;;;GAiBG;AACH,wBAAgB,iBAAiB,CAAC,MAAM,EAAE;IAAE,UAAU,EAAE,OAAO,CAAC;IAAC,QAAQ,EAAE,iBAAiB,CAAA;CAAE,GAAG,OAAO,CAEvG;AAED;;;;;;GAMG;AACH,wBAAgB,4CAA4C,CAAC,MAAM,EAAE;IACnE,cAAc,EAAE,yBAAyB,GAAG,SAAS,CAAC;IACtD,cAAc,EAAE,SAAS,+BAA+B,EAAE,GAAG,SAAS,CAAC;CACxE,GAAG,iBAAiB,GAAG,SAAS,CAEhC"}

package/dist/esm/core/navigation/zone-empty-behavior.js.map

@@ -1 +1 @@
-{"version":3,"file":"zone-empty-behavior.js","sourceRoot":"","sources":["../../../../../src/core/navigation/zone-empty-behavior.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AAEH,OAAO,EAAE,kBAAkB,EAAE,iBAAiB,EAAE,MAAM,uBAAuB,CAAC;AAG9E,OAAO,EAAE,0CAA0C,EAAE,MAAM,8BAA8B,CAAC;AAuB1F;;;;;;GAMG;AACH,MAAM,UAAU,wBAAwB,CAAC,EACvC,IAAI,EACJ,KAAK,EACL,mBAAmB,GACK;IACxB,IAAI,IAAI,KAAK,kBAAkB,CAAC,OAAO,EAAE,CAAC;QACxC,OAAO,iBAAiB,CAAC,QAAQ,CAAC;IACpC,CAAC;IACD,OAAO,mBAAmB;WACrB,KAAK,EAAE,CAAC,IAAI,CAAC,EAAE,OAAO;WACtB,iBAAiB,CAAC,QAAQ,CAAC;AAClC,CAAC;AAED;;;;;;;GAOG;AACH,MAAM,UAAU,0BAA0B,CAAC,QAA2B;IACpE,OAAO,QAAQ,KAAK,iBAAiB,CAAC,WAAW,CAAC;AACpD,CAAC;AAED;;;;;;;;;;;;;;;;;GAiBG;AACH,MAAM,UAAU,iBAAiB,CAAC,MAA4D;IAC5F,OAAO,MAAM,CAAC,UAAU,IAAI,CAAC,0BAA0B,CAAC,MAAM,CAAC,QAAQ,CAAC,CAAC;AAC3E,CAAC;AAED;;;;;;GAMG;AACH,MAAM,UAAU,4CAA4C,CAAC,MAG5D;IACC,OAAO,0CAA0C,CAAC,MAAM,CAAC,EAAE,mBAAmB,CAAC;AACjF,CAAC","sourcesContent":["/**\n * Zone empty-behavior resolution — what an ADJACENT zone does once its last content is dismissed.\n *\n * ## Why this is a resolver rather than a field read\n *\n * `ZoneConfig.onEmpty` is declared per ZONE, so one value covers every destination that splits into\n * that zone — and destinations legitimately disagree. A LIST wants the detail pane to stay put so the\n * layout does not reflow while a reviewer steps through rows; a CANVAS wants its width back the moment\n * nothing is selected. They share one secondary zone, so a single zone-level value is wrong for one of\n * them whichever way it is set.\n *\n * The override therefore lives on the DESTINATION — the thing occupying primary — because the question\n * \"what should happen to my detail pane when it empties\" is a property of the surface being returned\n * TO, not of the content that just left.\n *\n * ## Precedence, and why COLLAPSE is the floor\n *\n *   destination override → zone config → `ZoneEmptyBehavior.COLLAPSE`\n *\n * COLLAPSE is the schema default and, until this resolver existed, the UNCONDITIONAL behavior: nothing\n * read `onEmpty` at all, so every zone collapsed regardless of what its layout declared (issue #191).\n * Keeping COLLAPSE as the floor is what makes this change invisible to every layout that authored\n * nothing — and to every layout that authored COLLAPSE and was silently getting it by accident.\n */\n\nimport { NavigationZoneName, ZoneEmptyBehavior } from '@wildo-ai/saas-models';\nimport type { NavigationLayout } from '@wildo-ai/saas-models';\n\nimport { resolvePrimaryDestinationLayoutDeclaration } from './primary-destination-layout';\nimport type { PrimaryDestinationCompositeView, PrimaryDestinationContent } from './primary-destination-layout';\n\n/**\n * The destination-level override, already resolved from whatever is in primary.\n *\n * Passed in rather than looked up here so this stays a pure function of its arguments: resolving a\n * composite view's or a resource operation's frontend config needs the registry and the app config,\n * and threading those through would make the precedence rule — the part worth testing — untestable\n * without mounting half the runtime.\n */\nexport interface ZoneEmptyBehaviorInputs {\n  /** The zone whose empty behavior is being resolved. PRIMARY never empties; see the guard below. */\n  zone: NavigationZoneName;\n  /** The resolved layout's zone declarations, or `undefined` when no layout is configured. */\n  zones: NavigationLayout['zones'] | undefined;\n  /**\n   * `adjacentZoneOnEmpty` declared by whatever currently occupies PRIMARY, or `undefined` when the\n   * destination declares nothing (the common case).\n   */\n  destinationOverride: ZoneEmptyBehavior | undefined;\n}\n\n/**\n * Resolve what `zone` does when its stack empties.\n *\n * PRIMARY always answers COLLAPSE, which is not a behavior so much as a refusal: primary never empties\n * (it falls back to the router's own children), so no caller should be asking. Answering the floor\n * rather than throwing keeps a mis-call from taking the shell down over a layout question.\n */\nexport function resolveZoneEmptyBehavior({\n  zone,\n  zones,\n  destinationOverride,\n}: ZoneEmptyBehaviorInputs): ZoneEmptyBehavior {\n  if (zone === NavigationZoneName.PRIMARY) {\n    return ZoneEmptyBehavior.COLLAPSE;\n  }\n  return destinationOverride\n    ?? zones?.[zone]?.onEmpty\n    ?? ZoneEmptyBehavior.COLLAPSE;\n}\n\n/**\n * Should `zone` occupy space right now?\n *\n * Two reasons a zone is shown, and they are different questions: it HAS content, or it has none and\n * its resolved behavior is `EMPTY_STATE` (a reserved pane carrying a placeholder). Kept beside the\n * resolver so the two can never drift — a caller that resolved the behavior and then wrote its own\n * visibility expression is how one of them ends up reading the field and the other not.\n */\nexport function zoneOccupiesSpaceWhenEmpty(behavior: ZoneEmptyBehavior): boolean {\n  return behavior === ZoneEmptyBehavior.EMPTY_STATE;\n}\n\n/**\n * May this zone be DISMISSED — is a close control worth offering on it?\n *\n * Two conditions, and both are about whether the gesture would DO anything:\n *\n * - **It holds something.** Closing an empty pane is a no-op by definition.\n * - **Closing gives the width back**, i.e. the resolved behavior is not `EMPTY_STATE`. A zone that\n *   stays on screen when empty has declared that it stays; \"closing\" it would swap a record for a\n *   placeholder and return no room, so the control would appear to do nothing. That is a worse\n *   affordance than no control at all.\n *\n * Kept beside {@link zoneOccupiesSpaceWhenEmpty} — it is that predicate's inverse plus the content\n * test — so the two cannot drift: the control can never appear on a pane that would stay put, nor be\n * withheld from one that would go.\n *\n * Deliberately NOT conditioned on emphasis: closing an emphasized pane is the fastest way back to\n * the list beneath it, and hiding the control there strands the reader on the expand toggle.\n */\nexport function zoneIsDismissable(params: { hasContent: boolean; behavior: ZoneEmptyBehavior }): boolean {\n  return params.hasContent && !zoneOccupiesSpaceWhenEmpty(params.behavior);\n}\n\n/**\n * Read `adjacentZoneOnEmpty` off whatever occupies PRIMARY.\n *\n * A thin projection over {@link resolvePrimaryDestinationLayoutDeclaration}, which owns the\n * content-kind switch shared with `zoneContentFill`. Kept as a named function rather than inlined at\n * the call site so the pins below exercise the same path the runtime takes.\n */\nexport function resolvePrimaryDestinationAdjacentZoneOnEmpty(params: {\n  primaryContent: PrimaryDestinationContent | undefined;\n  compositeViews: readonly PrimaryDestinationCompositeView[] | undefined;\n}): ZoneEmptyBehavior | undefined {\n  return resolvePrimaryDestinationLayoutDeclaration(params)?.adjacentZoneOnEmpty;\n}\n"]}
+{"version":3,"file":"zone-empty-behavior.js","sourceRoot":"","sources":["../../../../src/core/navigation/zone-empty-behavior.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AAEH,OAAO,EAAE,kBAAkB,EAAE,iBAAiB,EAAE,MAAM,uBAAuB,CAAC;AAG9E,OAAO,EAAE,0CAA0C,EAAE,MAAM,8BAA8B,CAAC;AAuB1F;;;;;;GAMG;AACH,MAAM,UAAU,wBAAwB,CAAC,EACvC,IAAI,EACJ,KAAK,EACL,mBAAmB,GACK;IACxB,IAAI,IAAI,KAAK,kBAAkB,CAAC,OAAO,EAAE,CAAC;QACxC,OAAO,iBAAiB,CAAC,QAAQ,CAAC;IACpC,CAAC;IACD,OAAO,mBAAmB;WACrB,KAAK,EAAE,CAAC,IAAI,CAAC,EAAE,OAAO;WACtB,iBAAiB,CAAC,QAAQ,CAAC;AAClC,CAAC;AAED;;;;;;;GAOG;AACH,MAAM,UAAU,0BAA0B,CAAC,QAA2B;IACpE,OAAO,QAAQ,KAAK,iBAAiB,CAAC,WAAW,CAAC;AACpD,CAAC;AAED;;;;;;;;;;;;;;;;;GAiBG;AACH,MAAM,UAAU,iBAAiB,CAAC,MAA4D;IAC5F,OAAO,MAAM,CAAC,UAAU,IAAI,CAAC,0BAA0B,CAAC,MAAM,CAAC,QAAQ,CAAC,CAAC;AAC3E,CAAC;AAED;;;;;;GAMG;AACH,MAAM,UAAU,4CAA4C,CAAC,MAG5D;IACC,OAAO,0CAA0C,CAAC,MAAM,CAAC,EAAE,mBAAmB,CAAC;AACjF,CAAC","sourcesContent":["/**\n * Zone empty-behavior resolution — what an ADJACENT zone does once its last content is dismissed.\n *\n * ## Why this is a resolver rather than a field read\n *\n * `ZoneConfig.onEmpty` is declared per ZONE, so one value covers every destination that splits into\n * that zone — and destinations legitimately disagree. A LIST wants the detail pane to stay put so the\n * layout does not reflow while a reviewer steps through rows; a CANVAS wants its width back the moment\n * nothing is selected. They share one secondary zone, so a single zone-level value is wrong for one of\n * them whichever way it is set.\n *\n * The override therefore lives on the DESTINATION — the thing occupying primary — because the question\n * \"what should happen to my detail pane when it empties\" is a property of the surface being returned\n * TO, not of the content that just left.\n *\n * ## Precedence, and why COLLAPSE is the floor\n *\n *   destination override → zone config → `ZoneEmptyBehavior.COLLAPSE`\n *\n * COLLAPSE is the schema default and, until this resolver existed, the UNCONDITIONAL behavior: nothing\n * read `onEmpty` at all, so every zone collapsed regardless of what its layout declared (issue #191).\n * Keeping COLLAPSE as the floor is what makes this change invisible to every layout that authored\n * nothing — and to every layout that authored COLLAPSE and was silently getting it by accident.\n */\n\nimport { NavigationZoneName, ZoneEmptyBehavior } from '@wildo-ai/saas-models';\nimport type { NavigationLayout } from '@wildo-ai/saas-models';\n\nimport { resolvePrimaryDestinationLayoutDeclaration } from './primary-destination-layout';\nimport type { PrimaryDestinationCompositeView, PrimaryDestinationContent } from './primary-destination-layout';\n\n/**\n * The destination-level override, already resolved from whatever is in primary.\n *\n * Passed in rather than looked up here so this stays a pure function of its arguments: resolving a\n * composite view's or a resource operation's frontend config needs the registry and the app config,\n * and threading those through would make the precedence rule — the part worth testing — untestable\n * without mounting half the runtime.\n */\nexport interface ZoneEmptyBehaviorInputs {\n  /** The zone whose empty behavior is being resolved. PRIMARY never empties; see the guard below. */\n  zone: NavigationZoneName;\n  /** The resolved layout's zone declarations, or `undefined` when no layout is configured. */\n  zones: NavigationLayout['zones'] | undefined;\n  /**\n   * `adjacentZoneOnEmpty` declared by whatever currently occupies PRIMARY, or `undefined` when the\n   * destination declares nothing (the common case).\n   */\n  destinationOverride: ZoneEmptyBehavior | undefined;\n}\n\n/**\n * Resolve what `zone` does when its stack empties.\n *\n * PRIMARY always answers COLLAPSE, which is not a behavior so much as a refusal: primary never empties\n * (it falls back to the router's own children), so no caller should be asking. Answering the floor\n * rather than throwing keeps a mis-call from taking the shell down over a layout question.\n */\nexport function resolveZoneEmptyBehavior({\n  zone,\n  zones,\n  destinationOverride,\n}: ZoneEmptyBehaviorInputs): ZoneEmptyBehavior {\n  if (zone === NavigationZoneName.PRIMARY) {\n    return ZoneEmptyBehavior.COLLAPSE;\n  }\n  return destinationOverride\n    ?? zones?.[zone]?.onEmpty\n    ?? ZoneEmptyBehavior.COLLAPSE;\n}\n\n/**\n * Should `zone` occupy space right now?\n *\n * Two reasons a zone is shown, and they are different questions: it HAS content, or it has none and\n * its resolved behavior is `EMPTY_STATE` (a reserved pane carrying a placeholder). Kept beside the\n * resolver so the two can never drift — a caller that resolved the behavior and then wrote its own\n * visibility expression is how one of them ends up reading the field and the other not.\n */\nexport function zoneOccupiesSpaceWhenEmpty(behavior: ZoneEmptyBehavior): boolean {\n  return behavior === ZoneEmptyBehavior.EMPTY_STATE;\n}\n\n/**\n * May this zone be DISMISSED — is a close control worth offering on it?\n *\n * Two conditions, and both are about whether the gesture would DO anything:\n *\n * - **It holds something.** Closing an empty pane is a no-op by definition.\n * - **Closing gives the width back**, i.e. the resolved behavior is not `EMPTY_STATE`. A zone that\n *   stays on screen when empty has declared that it stays; \"closing\" it would swap a record for a\n *   placeholder and return no room, so the control would appear to do nothing. That is a worse\n *   affordance than no control at all.\n *\n * Kept beside {@link zoneOccupiesSpaceWhenEmpty} — it is that predicate's inverse plus the content\n * test — so the two cannot drift: the control can never appear on a pane that would stay put, nor be\n * withheld from one that would go.\n *\n * Deliberately NOT conditioned on emphasis: closing an emphasized pane is the fastest way back to\n * the list beneath it, and hiding the control there strands the reader on the expand toggle.\n */\nexport function zoneIsDismissable(params: { hasContent: boolean; behavior: ZoneEmptyBehavior }): boolean {\n  return params.hasContent && !zoneOccupiesSpaceWhenEmpty(params.behavior);\n}\n\n/**\n * Read `adjacentZoneOnEmpty` off whatever occupies PRIMARY.\n *\n * A thin projection over {@link resolvePrimaryDestinationLayoutDeclaration}, which owns the\n * content-kind switch shared with `zoneContentFill`. Kept as a named function rather than inlined at\n * the call site so the pins below exercise the same path the runtime takes.\n */\nexport function resolvePrimaryDestinationAdjacentZoneOnEmpty(params: {\n  primaryContent: PrimaryDestinationContent | undefined;\n  compositeViews: readonly PrimaryDestinationCompositeView[] | undefined;\n}): ZoneEmptyBehavior | undefined {\n  return resolvePrimaryDestinationLayoutDeclaration(params)?.adjacentZoneOnEmpty;\n}\n"]}

package/dist/esm/core/navigation/zone-visible-entry.d.ts

@@ -23,4 +23,26 @@ import type { NavigationStackEntry } from './navigation.schemas';
  * @returns The index to render, or `-1` for an empty stack.
  */
 export declare function resolveVisibleEntryIndex(stack: NavigationStackEntry[], contentModel: NavigationZoneContentModel | undefined, activeTabId: string | undefined): number;
+/**
+ * Which entry a zone MUTATION acts on — the reducer's counterpart to {@link resolveVisibleEntryIndex}.
+ *
+ * ## Why it does not take the content model
+ *
+ * `resolveVisibleEntryIndex` is the renderer's answer and reads `contentModel` off the LAYOUT. The
+ * reducer has no layout, so it reads the one thing that is only ever written for a TABBED zone:
+ * `NavigationZoneState.activeTabId`. Absent, the acted-on entry is the top of the stack, which is
+ * the SINGLE contract exactly.
+ *
+ * ## Why it is a function and not two inline copies
+ *
+ * It was two, briefly, on 2026-09-25 — one in `replaceEntry` and one in `popEntry` — added in the
+ * change that deleted `useIsStackEntryActive` for being a third answer to the same question. Two
+ * copies with a rule of their own is the thing that change existed to remove, so they became this.
+ *
+ * A stale `activeTabId` matching no entry falls back to the top rather than dropping the write: a
+ * tab closed from under an id must not make the zone unwritable.
+ */
+export declare function zoneMutationTargetIndex(stack: readonly {
+    id: string;
+}[], activeTabId: string | undefined): number;
 //# sourceMappingURL=zone-visible-entry.d.ts.map

package/dist/esm/core/navigation/zone-visible-entry.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"zone-visible-entry.d.ts","sourceRoot":"","sources":["../../../../../src/core/navigation/zone-visible-entry.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AAEH,OAAO,EAAE,0BAA0B,EAAE,MAAM,uBAAuB,CAAC;AAEnE,OAAO,KAAK,EAAE,oBAAoB,EAAE,MAAM,sBAAsB,CAAC;AAEjE;;;;;;GAMG;AACH,wBAAgB,wBAAwB,CACtC,KAAK,EAAE,oBAAoB,EAAE,EAC7B,YAAY,EAAE,0BAA0B,GAAG,SAAS,EACpD,WAAW,EAAE,MAAM,GAAG,SAAS,GAC9B,MAAM,CAuDR"}
+{"version":3,"file":"zone-visible-entry.d.ts","sourceRoot":"","sources":["../../../../src/core/navigation/zone-visible-entry.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AAEH,OAAO,EAAE,0BAA0B,EAAE,MAAM,uBAAuB,CAAC;AAEnE,OAAO,KAAK,EAAE,oBAAoB,EAAE,MAAM,sBAAsB,CAAC;AAEjE;;;;;;GAMG;AACH,wBAAgB,wBAAwB,CACtC,KAAK,EAAE,oBAAoB,EAAE,EAC7B,YAAY,EAAE,0BAA0B,GAAG,SAAS,EACpD,WAAW,EAAE,MAAM,GAAG,SAAS,GAC9B,MAAM,CAuDR;AAED;;;;;;;;;;;;;;;;;;GAkBG;AACH,wBAAgB,uBAAuB,CACrC,KAAK,EAAE,SAAS;IAAE,EAAE,EAAE,MAAM,CAAA;CAAE,EAAE,EAChC,WAAW,EAAE,MAAM,GAAG,SAAS,GAC9B,MAAM,CAIR"}

package/dist/esm/core/navigation/zone-visible-entry.js

@@ -73,4 +73,29 @@ export function resolveVisibleEntryIndex(stack, contentModel, activeTabId) {
     const activeIndex = stack.findIndex(entry => entry.id === activeTabId);
     return activeIndex >= 0 ? activeIndex : topIndex;
 }
+/**
+ * Which entry a zone MUTATION acts on — the reducer's counterpart to {@link resolveVisibleEntryIndex}.
+ *
+ * ## Why it does not take the content model
+ *
+ * `resolveVisibleEntryIndex` is the renderer's answer and reads `contentModel` off the LAYOUT. The
+ * reducer has no layout, so it reads the one thing that is only ever written for a TABBED zone:
+ * `NavigationZoneState.activeTabId`. Absent, the acted-on entry is the top of the stack, which is
+ * the SINGLE contract exactly.
+ *
+ * ## Why it is a function and not two inline copies
+ *
+ * It was two, briefly, on 2026-09-25 — one in `replaceEntry` and one in `popEntry` — added in the
+ * change that deleted `useIsStackEntryActive` for being a third answer to the same question. Two
+ * copies with a rule of their own is the thing that change existed to remove, so they became this.
+ *
+ * A stale `activeTabId` matching no entry falls back to the top rather than dropping the write: a
+ * tab closed from under an id must not make the zone unwritable.
+ */
+export function zoneMutationTargetIndex(stack, activeTabId) {
+    if (stack.length === 0)
+        return -1;
+    const activeIndex = activeTabId !== undefined ? stack.findIndex(entry => entry.id === activeTabId) : -1;
+    return activeIndex >= 0 ? activeIndex : stack.length - 1;
+}
 //# sourceMappingURL=zone-visible-entry.js.map