@jsenv/navi 0.29.387 → 0.29.389

package/dist/dev/jsenv_navi.js

@@ -554,12 +554,17 @@ effect(() => {
  * The active language is read from `languagesSignal` (see lang_signal.js —
  * combines the browser's own `navigator.languages`, an optional
  * `setPreferredLanguage()` user override, and an optional
- * `setSupportedLanguages()` app-wide allow-list), live on every lookup.
+ * `setSupportedLanguages()` app-wide allow-list), live on every lookup. Each
+ * key is looked up in those languages in order, then in English, which
+ * translates every key: a language shipped for part of the keys only (German
+ * has the `time.*` words) never shows a raw key.
  *
  * Built-in key namespaces, all overridable — the registrations below are the
  * exhaustive list, read them to find the exact key to override:
  *   - `"button.*"`     — Clear, Reset, Send, Open, Close, Cancel, Confirm…
- *   - `"time.*"`       — what a clock writes between hours and minutes, and how the two ends of a span are named; the wording the formatters use is registered by @jsenv/humanize
+ *   - `"confirm.*"`    — the question a confirmation asks by default
+ *   - `"time.*"`       — what a clock writes between hours and minutes, and the labels of its hour and minute parts; the wording the formatters use is registered by @jsenv/humanize
+ *   - `"time_range.*"` — how the two ends of a span are named ("From", "to")
  *   - `"spin.*"`       — the ends of a steppable range
  *   - `"list.*"`       — empty/no-match/failed-rows messages
  *   - `"badge_list.*"` — the "+[count] more" overflow badge
@@ -1472,19 +1477,25 @@ const isNetworkPolicyError = (error) => {
  * is already saying it in words the person understands.
  *
  * navi's own report leaves it alone (action_error_report.js). What is left is
- * the screen displaying it: it does so by throwing the error to a boundary, and
- * `preact/debug` re-emits on `window` every error a boundary caught — on
- * purpose, for React devtools compatibility. Uncancelled, that lands as an
- * uncaught error in the console, over a page calmly explaining why nothing was
- * asked. Cancelling the event is what says it is handled: the browser drops
+ * the error reaching `window` on its own — a run called by hand whose failure
+ * nobody catches, a render throw no boundary took — where it lands as an
+ * uncaught error in the console, about a request the app itself declared would
+ * not leave. Cancelling the event is what says it is handled: the browser drops
  * the console line, and the jsenv supervisor skips prevented events too.
  *
  * Both shapes a failure travels in are covered, since which one it is depends
  * on whether the resource callback happened to be async — the throw reaching
  * `window`, and the rejection nobody caught.
  *
- * Scoped to the policy's own error and to nothing else — every other error a
- * boundary caught, and every other rejection let go, stays exactly as loud as
+ * A boundary displaying it raises no event at all. In dev, `preact/debug` hands
+ * every error a boundary caught to `console.error`, after the boundary took it
+ * and before it rendered anything; it reads no option and no flag, so that line
+ * stays. Muting it from here is not done: wrapping `console.error` rewrites a
+ * global, and wrapping `options._catchError` reaches into preact's private
+ * hooks, both to hide one class of error.
+ *
+ * Scoped to the policy's own error and to nothing else — every other error
+ * thrown at window, and every other rejection let go, stays exactly as loud as
  * it is.
  */
 let networkPolicyErrorSilenced = false;
@@ -1572,11 +1583,10 @@ const errorIsDisplayed = (error) => {
  *
  * Whatever the reader does with it is already covered without any deadline: it
  * displays it (and marks it), or it throws it, and a thrown error either finds a
- * boundary that displays it or reaches window on its own — `preact/debug`
- * re-throws every error a boundary caught, and an unbounded one aborts the
- * render loudly. Reporting it here as well would be a second voice saying the
- * same thing, always the wrong one, since this module cannot see which of those
- * happened.
+ * boundary that displays it or reaches window on its own — preact re-throws
+ * what no boundary handled. Reporting it here as well would be a second voice
+ * saying the same thing, always the wrong one, since this module cannot see
+ * which of those happened.
  */
 const errorTakenByRenderSet = new WeakSet();
 const markErrorAsTakenByRender = (error) => {
@@ -1651,8 +1661,8 @@ const markErrorAsStoppingRender = (error) => {
  * An error the network policy produced is never reported: the app declared the
  * state that produced it, the request never left, and there is nothing for a
  * developer to fix. It is data a screen shows, and it stays data whether or not
- * one does (see network_policy.js, which also keeps it out of the browser
- * console).
+ * one does (see network_policy.js, which also cancels it when it reaches
+ * window).
  */
 const errorIsAccountedFor = (error) => {
   return (
@@ -1666,7 +1676,7 @@ const errorIsAccountedFor = (error) => {
 /**
  * Rethrown rather than logged: an error nobody took is an unhandled error, and
  * the runtime already knows what to do with those (window "error" event, jsenv
- * overlay in dev). Same trick preact/debug uses for the same reason.
+ * overlay in dev). Same answer preact gives an error no boundary handled.
  */
 const errorReportedSet = new WeakSet();
 const reportErrorIfNobodyDisplaysIt = (error, { action } = {}) => {
@@ -2187,7 +2197,7 @@ const compareTwoJsValues = (
         }
         return true;
       }
-      // Ordered array comparison (original behavior)
+      // Ordered array comparison
       let i = 0;
       while (i < a.length) {
         const aValue = a[i];
@@ -3370,6 +3380,8 @@ const actionWeakMap = new WeakMap();
  *   long is this still true?" belongs to the question: a court list is good for
  *   the session, a count of people watching grows on its own and is worth a few
  *   minutes, a payment status is worth nothing at all.
+ * @param {{ verb?: "GET" | "POST" | "PUT" | "PATCH" | "DELETE" }} [rootOptions.meta] -
+ *   `verb` puts the action under the network policy (docs/network_policy.md).
  */
 const createAction = (callback, rootOptions = {}) => {
   const existing = actionWeakMap.get(callback);
@@ -4484,7 +4496,7 @@ const runUnwatched = (startRun) => {
 /**
  * Reactively runs an action whenever the params derived from signals change.
  *
- * @param {object} action - The action to run.
+ * @param {object | Function} action - The action to run, or a function made into one.
  * @param {Function} deriveActionParamsFromSignals - A function that reads signals and returns
  *   the params to pass to the action. It is re-evaluated automatically whenever a signal it
  *   read changes. Return `false`/`null`/`undefined` to skip running the action.
@@ -4507,6 +4519,8 @@ const runUnwatched = (startRun) => {
  *   ```
  *   The action will not fire while the user is actively changing filters; it fires once
  *   they pause for half a second.
+ * @returns {object} the instance bound to the derived params: the one to read
+ *   (`useAsyncData`), since the answer lands there and never on `action` itself.
  */
 // The run is not awaited here, and a rejection nobody waits for is an unhandled
 // one — in dev, an error overlay thrown over a page that is already saying what
@@ -5021,11 +5035,12 @@ const isNumberInput = (type, naviInputType) => {
  */
 /**
  * A bound signal that carries a default of its own says the same thing on every
- * control: the control starts there and stays uncontrolled, which is what makes
- * a form read the value shown as a SUGGESTION rather than as something it
- * already holds. Uncontrolled here is about what the control HOLDS, not about
- * whether it follows the signal — the binding stays two-way either way (see
- * stateFromSignal in control_hooks.jsx). Written once and used by everything
+ * control: the control starts there, uncontrolled, and a reset goes back to it.
+ * Uncontrolled here is about where the control starts, not about whether it
+ * follows the signal — the binding stays two-way either way (see
+ * stateFromSignal in control_hooks.jsx) — nor about what a form counts as
+ * held: that is the signal's content (isUIStateHeld in held_ui_state.js), and a
+ * stateSignal holds its default. Written once and used by everything
  * that takes a `signal`, so one signal cannot mean two different things
  * depending on which control it was handed to.
  */
@@ -5085,8 +5100,7 @@ const resolveInputProps = (props, { controlType = "input" } = {}) => {
         // If no explicit defaultChecked, derive it from the signal's default
         // value so that resetUIState restores to the original default.
         // Only a stateSignal carries a default of its own; a plain signal has
-        // no `options` at all, and asking it for one used to throw on mount —
-        // the same optional read every other branch here already does.
+        // no `options` at all, hence the optional read.
         const defaultVal = signalOptions?.getDefaultValue(false);
         if (defaultVal === undefined) ; else if (props.type === "radio") {
           if (defaultVal === true) {
@@ -9169,8 +9183,8 @@ const isLanguageSupported = (lang, supportedLanguages) => {
  * supported), falls back to `supportedLanguagesSignal` itself so callers
  * still get *something* usable rather than an empty array.
  *
- * Consumers that accept either a single lang or an ordered array (this
- * package's own `matchBestLang`/`createI18n`, and native `Intl.NumberFormat`/
+ * Consumers that accept either a single lang or an ordered array
+ * (@jsenv/humanize's `createI18n` and formatters, and native `Intl.NumberFormat`/
  * `Intl.DateTimeFormat`) can pass this straight through: anything not
  * covered by the first entry falls through to the next, rather than
  * jumping straight to an unrelated default like "en".
@@ -10153,15 +10167,15 @@ const readOnlyMessage = (field) => {
  * - Action dispatch + validity: `control_action.js` / `dispatchRequestAction`
  * - Validity checking: `control_validation.js`
  *
- * Each UI state controller gets its own `controlInteraction` instance (created by
- * `createControlInteraction`) just like it gets a `controlValidity` instance.
+ * Each UI state controller gets its own instance, `controller.rules.interaction`
+ * (created by `createControlInteraction`), beside `controller.rules.validation`.
  *
  * Flow:
  *   user interaction
  *   → dispatchRequestInteraction
  *   → "navi_request_interaction" event
  *   → onRequestInteraction
- *       → check disabled / read-only / busy (via controller.controlInteraction)
+ *       → check disabled / read-only / busy (via controller.rules.interaction)
  *         against the interaction's `intent` ("write" by default, "read" for one
  *         that only shows what is already there — see READONLY_CONSTRAINT)
  *       → if blocked  → prevented()
@@ -11004,7 +11018,8 @@ const interactionsDisputeThePress = (interactions) => {
  * control (a Button) is its own; a Box inside one, or wrapping exactly one,
  * reaches it; a Box with no control anywhere near it — or laying out several,
  * which belongs to none of them — still answers with a callback of the caller's,
- * and only "request_action" has nothing to ask.
+ * and only the two requests ("request_action", "request_ui_action") have
+ * nothing to ask.
  *
  * Set up once per element rather than on every render, which is what lets a
  * detector be a plain `setup`/teardown pair. So the interactions themselves are
@@ -11173,7 +11188,7 @@ const useInteractionsEffect = (ref, interactionsRef) => {
           cancelable: true,
         });
         // The event the interaction was read from stays reachable from it:
-        // `findEvent(actionEvent, "pointerdown")` still finds the press a swipe
+        // `findEvent(actionEvent, "pointerdown")` still finds the press a hold
         // was made of.
         chainEvent(interactionEvent, originalEvent);
         if (!element.dispatchEvent(interactionEvent)) {
@@ -11939,7 +11954,7 @@ const swipeTypeOf = (axis, pulled) => {
  *     …
  *   }}}
  *
- * `toId` is an element and never null: a copy over nothing is a release that meant
+ * `toId` names an element and is never null: a copy over nothing is a release that meant
  * nothing, and the interaction does not happen at all — unless the element
  * declares `leave` (see below), which gives that release a meaning of its own.
  *
@@ -12634,8 +12649,9 @@ defineInteractionDetector({
   name: "surface",
   claims: (type) =>
     type === PAN || type === ZOOM || type === GRAB || type === RELEASE,
-  // A press on the surface may be a tap, a hold or the beginning of a pan, and
-  // nothing may read it as the first until the pointer has said which.
+  // A press on the surface may be a tap, a hold or the first finger of a pan or
+  // a pinch, and nothing may read it as the first until the pointer has said
+  // which.
   disputesPress: true,
   setup: (element, trigger, { types, readConfig }) => {
     const canPan = types.includes(PAN);
@@ -15757,21 +15773,33 @@ const getActionResultProperties = (action) => {
   return actionResultPropertiesMap.get(action);
 };
 
-// PUT/PATCH results update the UI through the store, and DELETE resets the GET
-// instead of rerunning it, so a GET rerun would only ever cost a request.
-// A POST is the one case the client cannot decide alone: whether a new item
-// belongs to a list depends on filters/pagination the backend owns.
 // Rationale in full, plus when to override: docs/list_refresh.md
 const defaultRerunOn = {
+  // PUT/PATCH results update the UI through the store, and DELETE resets the
+  // GET rather than rerunning it, so a GET rerun would only ever cost a request.
   GET: false,
+  // A POST is the one case the client cannot decide alone: whether a new item
+  // belongs to a list depends on filters/pagination the backend owns.
   GET_MANY: ["POST"],
+  // DELETE is in there, unlike for GET_MANY: an action holds ids and the store
+  // drops the deleted one out of every list holding it, while a list reading
+  // by slices holds places — the row that left takes the ones after it one
+  // rank up, and only the collection knows who fills the last one.
+  GET_RANGE: ["POST", "DELETE"],
+};
+// A key a `rerunOn` leaves out keeps the value it would have had without it:
+// the default for a resource, the value of the resource it is declared on for
+// a withParams() scope or a relation.
+const resolveRerunOn = (rerunOn, inheritedRerunOn = defaultRerunOn) => {
+  if (!rerunOn) {
+    return inheritedRerunOn;
+  }
+  return {
+    GET: rerunOn.GET ?? inheritedRerunOn.GET,
+    GET_MANY: rerunOn.GET_MANY ?? inheritedRerunOn.GET_MANY,
+    GET_RANGE: rerunOn.GET_RANGE ?? inheritedRerunOn.GET_RANGE,
+  };
 };
-// What makes a range reader stale (rerunOn.GET_RANGE overrides it). DELETE is
-// in there, unlike for GET_MANY: an action holds ids and the store drops the
-// deleted one out of every list holding it, while a list reading by slices
-// holds places — the row that left takes the ones after it one rank up, and
-// only the collection knows who fills the last one.
-const defaultInvalidateRangeOn = ["POST", "DELETE"];
 
 // This handles ALL resource lifecycle logic (rerun/reset) across all resources
 const createResourceLifecycleManager = () => {
@@ -15781,7 +15809,7 @@ const createResourceLifecycleManager = () => {
 
   const registerResource = (resourceScope, config) => {
     const {
-      rerunOn = defaultRerunOn,
+      rerunOn,
       paramScope = null,
       dependencies = [],
       uniqueKeys = [],
@@ -16064,8 +16092,7 @@ const createResourceLifecycleManager = () => {
       if (!isSameResource && !isDependent) {
         continue;
       }
-      const invalidateOn = config.rerunOn.GET_RANGE ?? defaultInvalidateRangeOn;
-      if (!shouldRerunAfter(invalidateOn, triggerVerb)) {
+      if (!shouldRerunAfter(config.rerunOn.GET_RANGE, triggerVerb)) {
         continue;
       }
       for (const rangeReader of config.rangeReaderSet) {
@@ -16403,7 +16430,7 @@ const debug$3 = (...args) => {
  * @param {string} name - resource name, used in action names and error messages
  * @param {Object} restCallbacks - `{ idKey, uniqueKeys, rerunOn, dependencies, GET, GET_MANY, GET_RANGE, POST, POST_MANY, PUT, PUT_MANY, PATCH, PATCH_MANY, DELETE, DELETE_MANY }`
  * @param {string} [restCallbacks.idKey] - primary key property, defaults to `"id"`
- * @param {string[]} [restCallbacks.uniqueKeys] - alternate keys the store can find an item by (e.g. `"username"`); a callback may return a different `id` to rename the item's primary key
+ * @param {string[]} [restCallbacks.uniqueKeys] - alternate keys the store can find an item by (e.g. `"username"`)
  * @see docs/resource.md — relationships, callback return contracts, decision table
  *
  * @example
@@ -16566,7 +16593,7 @@ const resource = (
     addItemSetup,
     createRestAction: createRestActionForRoot,
     paramScope: getParamScope(undefined),
-    rerunOn,
+    rerunOn: resolveRerunOn(rerunOn),
     dependencies,
   });
 };
@@ -16630,7 +16657,7 @@ const createResource = (
    * identical parameters, preventing cross-contamination between different parameter sets.
    *
    * @param {Object} params - Parameters to bind to all actions of this resource (required)
-   * @param {Object} options - Additional options for the parameterized resource
+   * @param {{ rerunOn?: Object, dependencies?: Object[] }} [options] - reruns of that scope; a `rerunOn` key left out keeps the resource's value, and `dependencies` left out are the resource's
    * @returns {Object} A new resource instance with parameter-bound actions and isolated lifecycle
    * @see docs/resource.md — what a scope isolates, and `dependencies`
    *
@@ -16648,7 +16675,7 @@ const createResource = (
    * const ROLE_WITH_OWNERSHIP = role.withParams({ owners: true }, {
    *   dependencies: [role, database, tables],
    * });
-   * // ROLE_WITH_OWNERSHIP.GET_MANY will autorerun when any table/database/role is POST/DELETE
+   * // ROLE_WITH_OWNERSHIP.GET_MANY reruns after any write (POST/PUT/PATCH/DELETE) on a role, a database or a table
    */
   const withParams = (
     paramsToInject,
@@ -16676,7 +16703,7 @@ const createResource = (
       addItemSetup,
       createRestAction: createRestActionWithParams,
       paramScope: resolvedParamScope,
-      rerunOn: withParamsRerunOn ?? rerunOn,
+      rerunOn: resolveRerunOn(withParamsRerunOn, rerunOn),
       dependencies: withParamsDeps ?? dependencies,
     });
   };
@@ -16694,13 +16721,15 @@ const createResource = (
    * Callback return contracts:
    * - GET / PUT → the parent object with the relationship nested inside:
    *   `async ({ id }) => ({ id, session: { id: 10, token: "abc" } })`; `null` for no relationship
-   * - DELETE → the parent id (or `{ id }`); the property is set to `null`
+   * - DELETE → the parent id, or `{ id }`; the property is set to `null`
    *
    * The backend may also embed the child inline in a parent GET/POST response — the
    * setter on the property upserts the nested object into the child store.
    *
-   * Returns the child relationship resource, itself chainable:
-   * `USER_SESSION.one("device", DEVICE)` adds a reactive `.device` property to each session.
+   * Returns the relationship resource, itself chainable. Its items are the child
+   * resource's own, shared by every parent: `USER_SESSION.one("device", DEVICE)`
+   * adds a reactive `.device` property to every session, as
+   * `SESSION.one("device", DEVICE)` would.
    *
    * @param {string} propertyName - property holding the child on each parent item
    * @param {Object} childResource - the independent resource created by `resource()`
@@ -16783,11 +16812,11 @@ const createResource = (
     const createRestActionForOne = (verb, callback, { onActionComplete }) => {
       const applyResultToValue =
         verb === "DELETE"
-          ? (itemId) => {
-              const item = store.select(itemId);
+          ? (itemIdOrItemProps) => {
+              const item = store.select(itemIdOrItemProps);
               const childItemId = item[propertyName][childIdKey];
               store.upsert({
-                [idKey]: itemId,
+                [idKey]: item[idKey],
                 [propertyName]: null,
               });
               return childItemId;
@@ -16815,7 +16844,7 @@ const createResource = (
             if (!isProps(result) && !primitiveCanBeId(result)) {
               throwInvalidResult(
                 action.name,
-                `an object (that will be used to drop "${name}" resource)`,
+                `the "${name}" id, or { ${idKey} } (the item whose "${propertyName}" becomes null)`,
                 result,
               );
             }
@@ -16840,11 +16869,11 @@ const createResource = (
         PUT,
         DELETE,
       },
-      store,
-      addItemSetup,
+      store: childStore,
+      addItemSetup: childResource.addItemSetup,
       createRestAction: createRestActionForOne,
       paramScope,
-      rerunOn: oneRerunOn ?? rerunOn,
+      rerunOn: resolveRerunOn(oneRerunOn, rerunOn),
       dependencies: oneDependencies ?? dependencies,
     });
   };
@@ -16867,6 +16896,9 @@ const createResource = (
    * - DELETE → `[parentId, childId]`
    * - DELETE_MANY → `[parentId, [childId, childId, …]]`
    *
+   * Returns the relationship resource, itself chainable; its items are the child
+   * resource's own, as for `.one()`.
+   *
    * @param {string} propertyName - property holding the child array on each parent item
    * @param {Object} childResource - the independent resource created by `resource()`
    * @param {Object} [restCallbacks] - `{ rerunOn, dependencies, GET, GET_MANY, POST, POST_MANY, PUT, PUT_MANY, PATCH, PATCH_MANY, DELETE, DELETE_MANY }`
@@ -17102,11 +17134,11 @@ const createResource = (
         DELETE,
         DELETE_MANY,
       },
-      store,
-      addItemSetup,
+      store: childStore,
+      addItemSetup: childResource.addItemSetup,
       createRestAction: createRestActionForMany,
       paramScope,
-      rerunOn: manyRerunOn ?? rerunOn,
+      rerunOn: resolveRerunOn(manyRerunOn, rerunOn),
       dependencies: manyDependencies ?? dependencies,
     });
   };
@@ -17235,7 +17267,7 @@ const createResource = (
       addItemSetup: childAddItemSetup,
       createRestAction: createRestActionForScopedOne,
       paramScope,
-      rerunOn: scopedOneRerunOn ?? rerunOn,
+      rerunOn: resolveRerunOn(scopedOneRerunOn, rerunOn),
       dependencies: scopedOneDependencies ?? dependencies,
     });
   };
@@ -17470,7 +17502,7 @@ const createResource = (
       addItemSetup: childAddItemSetup,
       createRestAction: createRestActionForScopedMany,
       paramScope,
-      rerunOn: scopedManyRerunOn ?? rerunOn,
+      rerunOn: resolveRerunOn(scopedManyRerunOn, rerunOn),
       dependencies: scopedManyDependencies ?? dependencies,
     });
     // When a scoped child collection is mutated (POST etc.), the parent GET must
@@ -17861,7 +17893,7 @@ Received an object with keys: ${keys.join(", ")}.`,
  * });
  *
  * syncResourceToSignals(USER, { username: usernameSignal });
- * // Now when a user item's username is updated via USER.PUT,
+ * // When a user item's username is updated via USER.PUT,
  * // usernameSignal.value is set to the new username,
  * // which in turn triggers the route Signal->URL sync and updates the browser URL.
  */
@@ -17874,6 +17906,17 @@ const syncResourceToSignals = (resource, propertyToSignalMap) => {
   syncStoreToSignals(resource.store, propertyToSignalMap);
 };
 
+/**
+ * The same, for a `scopedOne`/`scopedMany` resource: its items live in one store
+ * per owner, so the store to watch is the one of the owner `ownerSignal` names
+ * (by id or by any unique key), and it is switched when the signal changes.
+ * Nothing is synced while `ownerSignal` holds `null`/`undefined` or names an
+ * owner nothing has been loaded for yet.
+ *
+ * @param {Object} resource - a resource made by `.scopedOne()` / `.scopedMany()`
+ * @param {import("@preact/signals").Signal} ownerSignal - the owner whose children are watched
+ * @param {Object} propertyToSignalMap - `{ [propertyName]: signal }`, as for `syncResourceToSignals`
+ */
 const syncOwnedResourceToSignals = (
   resource,
   ownerSignal,
@@ -17921,7 +17964,7 @@ const generateSignalId = () => {
  * 1. Initially takes value from the default signal
  * 2. When explicitly set (programmatically or via localStorage), the explicit value takes precedence
  * 3. When default signal changes, it only updates if no explicit value was ever set
- * 4. Calling reset() or setting to undefined makes the signal use the dynamic default again
+ * 4. Setting it to undefined makes the signal use the dynamic default again
  * 5. If dynamic default is undefined and options.default is provided, uses the static fallback
  *
  * This is useful for:
@@ -17935,7 +17978,9 @@ const generateSignalId = () => {
  * @param {string|number} [options.id] - Custom ID for the signal. If not provided, an auto-generated ID will be used. Used for localStorage key and route pattern detection.
  * @param {any} [options.default] - Static fallback value used when defaultValue is a signal and that signal's value is undefined
  * @param {boolean} [options.persists=false] - Whether to persist the signal value in localStorage using the signal ID as key
- * @param {"string" | "number" | "boolean" | "object"} [options.type="string"] - Type for localStorage serialization/deserialization
+ * @param {string} [options.type] - Type the value is coerced to, and read back as from localStorage and the url:
+ *   any @jsenv/validity type (`"string"`, `"number"`, `"boolean"`, `"array"`, `"object"`, `"integer"`, `"date"`,
+ *   `"time"`…). Without it the value is not coerced.
  * @param {"string" | "number" | "boolean"} [options.itemType] - For array type: type of the array items.
  *   Used when reading the value back from a url search param, where everything is a string:
  *   `?level=3,4` becomes `[3, 4]` instead of `["3", "4"]`. Without it items stay strings.
@@ -19105,14 +19150,12 @@ const LoadingFallback = ({
  * Two things it gets right that a hand-written boundary rarely does, both
  * explained in docs/error_handling.md:
  *
- * - It marks the error as displayed ONLY when it actually displays it.
- *   `preact/debug` rethrows every error a boundary caught in a `setTimeout`, on
- *   purpose (React devtools compatibility), so a handled error still reaches
- *   window and the jsenv overlay covers the app unless `__handled_by__` is set.
- *   Setting it before knowing whether anything is rendered turns a boundary into
- *   a bug swallower: a TypeError in a component becomes a blank page AND a
- *   silent one. Without a `fallback` there is nothing to display, so the error is
- *   left alone and continues up.
+ * - It marks the error as displayed ONLY when it actually displays it. The
+ *   jsenv overlay skips an error carrying `__handled_by__`, so a mark set before
+ *   knowing whether anything is rendered mutes an error that then continues up:
+ *   a TypeError in a component becomes a blank page AND a silent one. Without a
+ *   `fallback` there is nothing to display, so the error is left alone and
+ *   continues up.
  *
  * - It resets on navigation, not only on rerun. Rerunning the failed action is
  *   one way out; going somewhere else is the common one. Without a reset on the
@@ -20178,9 +20221,9 @@ const isSizeSpacingKey = (key) => {
 // "vvw"/"vvh" are navi's own: the *visual* viewport, which — unlike vw/dvw —
 // shrinks when the mobile virtual keyboard opens (see layout/responsive.js), so
 // they are what a popup meant to stay clear of the keyboard should use.
-// "appw"/"apph" are the same thing narrowed to the app's own screen: identical
-// to vvw/vvh until the app declares --navi-app-max-width, and a share of that
-// width afterwards. A gap meant to read as "a small margin" must use these —
+// "appw"/"apph" are the same thing narrowed to the app's own screen: the
+// visual viewport minus the app's bands (--navi-app-inset-*), so identical to
+// vvw/vvh until the app declares bands. A gap meant to read as "a small margin" must use these —
 // 3vvw on a 1500px window is a 45px gap around a 600px app.
 // Functions rather than the signals themselves: appw/apph are not a signal to
 // read but a value to compute (a signal, then a CSS var read back). Reading the
@@ -22222,9 +22265,48 @@ const PSEUDO_STATE_CHILD_PROP_SET = new Set(["tabIndex", "tabindex"]);
  *   separator?: import("ignore:preact").ComponentChildren | ((index: number) => import("ignore:preact").ComponentChildren),
  *   selfInteractions?: string,
  *   interactions?: { [type: string]: "request_action" | "request_ui_action" | "refuse" | ((event: Event) => void) | false | null | undefined },
+ *   alignX?: string,
+ *   alignY?: string,
+ *   spacing?: string | number,
+ *   overflow?: string,
+ *   header?: boolean,
+ *   footer?: boolean,
+ *   body?: boolean,
+ *   sticky?: boolean,
  *   children?: import("ignore:preact").ComponentChildren,
  *   [key: string]: any,
  * }>}
+ * @param {"x"|"y"|boolean} [flex] A flex container: `"x"` (or `true`) side by
+ *   side, `"y"` stacked. Named by axis because `flex-direction: column` stacks
+ *   items vertically, the opposite of what "column" suggests.
+ * @param {boolean} [inline] The inline form of the box's display
+ *   (`inline-flex`, `inline-grid`…). An inline box given a `width`/`height`
+ *   becomes an inline flex row, since an inline box ignores both.
+ * @param {string} [alignX] Horizontal alignment of the content whatever the
+ *   flex direction: `justify-content` or `align-items` is picked from it
+ *   (`text-align` outside flex and grid).
+ * @param {string} [alignY] Vertical alignment, the same way.
+ * @param {string|number} [spacing] The gap between children in a flex or grid
+ *   box (`spacingX`/`spacingY` per axis) — there is no `gap` prop. Spacing
+ *   props (`spacing`, `margin*`, `padding*`) take the scale `"xxs"`…`"xxl"`
+ *   (`--navi-xxs`…), `"-s"` for a negative, or any CSS value.
+ * @param {object|string} [style] CSS properties, plus pseudo keys holding
+ *   their own: `style={{ color: "blue", ":hover": { color: "red" } }}`
+ *   (`":-navi-pressed"`, `"::before"`…). A pseudo class used there is tracked
+ *   on the element; nothing re-renders when it changes.
+ * @param {string} [overflow] `"auto"`/`"scroll"` (`overflowX`/`overflowY`
+ *   too) makes the box a scrolling area, which is what gives `header`/`body`/
+ *   `footer` their meaning; such a box is also `isolation: isolate` and gets a
+ *   `scroll-padding` (see docs/scroll.md).
+ * @param {boolean} [header] A part that stays put at the top of the scrolling
+ *   box it is a direct child of — nothing at all without that box's overflow.
+ *   Rendered as `<header>` unless `as` says otherwise.
+ * @param {boolean} [footer] The same at the bottom, rendered as `<footer>`.
+ * @param {boolean} [body] The only part of its scrolling box that scrolls,
+ *   `header`/`footer` sitting outside it. It shrinks, it never grows.
+ * @param {boolean} [sticky] `position: sticky` in the sticky z-index band
+ *   (`--navi-z-index-sticky`), stuck or not; an explicit `zIndex`, `"auto"`
+ *   included, wins (see docs/z_index.md). `top`/`bottom`/… take `true` for 0.
  * @param {string} [background] Any CSS background, plus two keywords for the
  *   planes an app paints: `"surface"` is the paper content sits on,
  *   `"chrome"` the frame around a screen — a top bar, a side menu, a toolbar.
@@ -23968,21 +24050,16 @@ const createUITransitionController = (
 /**
  * UITransition
  *
- * A Preact component that enables smooth animated transitions between its children when the content changes.
- * It observes content keys and phases to create different types of transitions.
+ * A Preact component that animates the change between its children: the
+ * outgoing content fades out while the incoming one fades in, and the box
+ * resizes from the one to the other (the mechanics are in ui_transition.js).
  *
- * Features:
- * - Content transitions: Between different content keys (e.g., user profiles, search results)
- * - Phase transitions: Between loading/content/error states for the same content key
- * - Automatic size animation to accommodate content changes
- * - Configurable transition types: "slide-left", "cross-fade"
- * - Independent duration control for content and phase transitions
- *
- * Usage:
- * - Wrap dynamic content in <UITransition> to animate between states
- * - Set a unique `data-content-id` on your rendered content to identify each content variant
- * - Use `data-content-phase` to mark loading/error states for phase transitions
- * - Configure transition types and durations for both content and phase changes
+ * Two kinds of change are told apart, from attributes on the rendered content:
+ * - a content transition, when the content key changes — `data-content-key` on
+ *   the rendered element (a user id, a search), or `useUITransitionContentId`
+ *   called from a component inside (what `<Route>` does with its url pattern);
+ * - a phase transition, when `data-content-phase` (a loading or error state)
+ *   changes for the same content key.
  *
  * Example:
  *
@@ -23991,9 +24068,6 @@ const createUITransitionController = (
  *       ? <Spinner data-content-key={userId} data-content-phase />
  *       : <UserProfile user={user} data-content-key={userId} />}
  *   </UITransition>
- *
- * When `data-content-id` changes, UITransition animates content transitions.
- * When `data-content-phase` changes for the same key, it animates phase transitions.
  */
 
 const UITransitionContentIdContext = createContext();
@@ -24115,16 +24189,12 @@ const UITransition = ({
 };
 
 /**
- * The goal of this hook is to allow a component to set a "content key"
- * Meaning all content within the component is identified by that key
- *
- * When the key changes, UITransition will be able to detect that and consider the content
- * as changed even if the component is still the same
- *
- * This is used by <Route> to set the content key to the route path
- * When the route becomes inactive it will call useUITransitionContentId(undefined)
- * And if a sibling route becones active it will call useUITransitionContentId with its own path
+ * Names the content a component renders, for the <UITransition> around it:
+ * everything rendered inside is identified by that key, and the key changing
+ * is read as a content change even though the component is the same.
  *
+ * <Route> calls it with the url pattern of the branch it renders; the branch
+ * unmounting removes its part, and a sibling branch mounting adds its own.
  */
 const useUITransitionContentId = value => {
   const contentId = useContext(UITransitionContentIdContext);
@@ -24149,8 +24219,8 @@ const useUITransitionContentId = value => {
 };
 
 /**
- * Custom route pattern matching system
- * Replaces URLPattern with a simpler, more predictable approach
+ * Custom route pattern matching system.
+ * Not built on URLPattern: matching here is simpler and more predictable.
  */
 
 
@@ -27482,7 +27552,7 @@ const useRouteStatus = (route) => {
 const assertRoute = (route) => {
   if (!route.isRoute) {
     throw new Error(
-      "The route prop must be a route object created with createRoute",
+      "The route prop must be a route object created with route()",
     );
   }
   if (!setupRoutesCalled) {
@@ -30157,8 +30227,8 @@ const TRANSITION_FURNITURE_CSS = /* css */ `.navi_fixed_bar[data-navi-transition
 }
 `;
 
-// Called from the render of whatever holds the pages, never at module scope:
-// a page that never travels between routes must not carry this sheet, and a
+// Called as a movement starts over a marked area, never at module scope: a
+// page that never travels between routes must not carry this sheet, and a
 // build that sees no caller drops the css with the function.
 const installTransitionFurnitureCss = () => {
   import.meta.css = [TRANSITION_FURNITURE_CSS, "@jsenv/navi/src/nav/transition_furniture.js"];
@@ -30621,9 +30691,10 @@ const TRANSITION_WINDOW_CSS = /* css */ `@property --navi-transition-cover-top {
 }
 `;
 
-// Called from the render of whatever needs the window, never at module scope:
-// a page that never travels between routes must not carry this sheet, and a
-// build that sees no caller drops the css with the function.
+// Called by whatever needs the window — a render, or a movement starting —
+// never at module scope: a page that never travels between routes must not
+// carry this sheet, and a build that sees no caller drops the css with the
+// function.
 const installTransitionWindowCss = () => {
   import.meta.css = [TRANSITION_WINDOW_CSS, "@jsenv/navi/src/nav/transition_window.js"];
 };
@@ -31436,9 +31507,6 @@ const RouteTransitionArea = ({
   children,
   ...rest
 }) => {
-  import.meta.css = [css$12, "@jsenv/navi/src/nav/route_transition.jsx"];
-  installTransitionWindowCss();
-  installTransitionFurnitureCss();
   const props = {
     ...rest,
     [TRANSITION_AREA_ATTRIBUTE]: ""
@@ -31453,8 +31521,9 @@ const RouteTransitionArea = ({
  * Declare how a pair of routes moves against each other — or how one route is
  * entered, from wherever its door happens to be.
  *
- * @param {object|null} from - a route, or `{ route, params }` when the page is
- *   a param of a route rather than a route of its own. `null` says the page is
+ * @param {object|null} from - a route (or the `routeFallback()` page), or
+ *   `{ route, params }` when the page is a param of a route rather than a route
+ *   of its own. `null` says the page is
  *   reached FROM ANYWHERE: its door is in the furniture (a gear in the top
  *   bar, a "+" in the tab bar) rather than on a screen, so there is no pair to
  *   write it on. Arriving at `to` from any page then plays forward and leaving
@@ -31502,13 +31571,10 @@ const RouteTransitionArea = ({
  *   Whatever is written here is what EVERY crossing of the pair plays. One
  *   crossing can ask for something else — `<Link routeTransition>`, or
  *   navTo(url, { routeTransition }) — which overrides this field by field, for
- *   that
- *   navigation alone.
+ *   that navigation alone.
  * @returns {() => void} remove this relation.
  */
 const defineRouteTransition = (from, to, transition) => {
-  import.meta.css = [css$12, "@jsenv/navi/src/nav/route_transition.jsx"];
-  installTransitionWindowCss();
   if (!to) {
     throw new TypeError(`defineRouteTransition needs a destination: "to" is ${to}. The page reached from anywhere is written defineRouteTransition(null, THAT_PAGE, ...) — there is no relation the other way round, a page LEFT for anywhere being the back half of that one.`);
   }
@@ -31548,8 +31614,6 @@ const defineRouteTransition = (from, to, transition) => {
  * @returns {() => void} remove this default.
  */
 const defineRouteDefaultTransition = transition => {
-  import.meta.css = [css$12, "@jsenv/navi/src/nav/route_transition.jsx"];
-  installTransitionWindowCss();
   const value = normalizeTransition(transition);
   defaultTransition = value;
   return () => {
@@ -31586,9 +31650,8 @@ const normalizeTransition = transition => {
  *
  * Two mouths, one meaning: the element being pressed wears it (a `<Link
  * routeTransition>`, or the attribute by hand on any anchor), or navTo() is
- * handed
- * it. Both arrive here through the announcement the navigation makes before it
- * writes anything (see before_routing.js).
+ * handed it. Both arrive here through the announcement the navigation makes
+ * before it writes anything (see before_routing.js).
  *
  * A request answers FIELD BY FIELD: what it does not say, the relation — or
  * the default — still answers for. So `{ direction: "back" }` keeps the pair's
@@ -32132,6 +32195,10 @@ const beginTransition = ({
   // Said before the picture is taken: whoever names something for a movement
   // between two pages decides on it now (see transition_destination.js).
   holdTransitionDestination(transition, url);
+  // Adopted by what starts a movement rather than by what declares one: a link
+  // or a navTo() asks for a movement in an app that declared none, and an app
+  // that never moves never carries the sheet.
+  import.meta.css = [css$12, "@jsenv/navi/src/nav/route_transition.jsx"];
   documentElement.setAttribute(TRANSITION_ATTRIBUTE, direction);
   if (type) {
     documentElement.setAttribute(TRANSITION_TYPE_ATTRIBUTE, type);
@@ -32153,6 +32220,10 @@ const beginTransition = ({
   // left (see transition_window.js).
   let areaStateBefore = null;
   if (areaElement) {
+    // The area is the application's element as often as <RouteTransitionArea>,
+    // so what a movement on it plays with is adopted here, where it is found.
+    installTransitionWindowCss();
+    installTransitionFurnitureCss();
     documentElement.setAttribute(TRANSITION_TARGET_ATTRIBUTE, "area");
     // Said before the picture is taken, like every name (see
     // transition_furniture.js): what the bars are wearing when the transition
@@ -32835,10 +32906,10 @@ const css$11 = /* css */`.navi_route_travel {
  * The pages are cut at the edge of this box while they travel, and at the app's
  * safe area the box runs under, which is written on the transition's own
  * pseudo-elements — no overflow of the document reaches pictures drawn in the
- * top layer. It needs nothing of the browser beyond view
- * transitions themselves: a browser without them (Firefox) navigates without the
- * movement, and the gesture applies its change on release instead of dragging a
- * picture that does not exist.
+ * top layer. It needs nothing of the browser beyond view transitions
+ * themselves: a browser without them navigates without the movement, and the
+ * gesture applies its change on release instead of dragging a picture that does
+ * not exist.
  *
  * While a travel plays, the rest of the page is taken as a picture too — this
  * box asks for `view-transition-name: root` back for that time, so an
@@ -34429,9 +34500,6 @@ const onNaviCommand = (e, { debugCommand = () => {} } = {}) => {
     `targeting`,
     commandTarget,
   );
-  // Timed once, for the wheel-in-dialog "Définir feels frozen on mobile" case;
-  // the line is gone now that the answer is known — a command that runs in 1ms
-  // said nothing, and it said it on every single interaction.
   return implementation();
 };
 
@@ -35076,8 +35144,8 @@ registerNaviCommand("--navi-open", (source, event, { anchor, value } = {}) => {
     target,
     implementation: () => {
       // The popup reads `anchor` first and falls back to the source (see
-      // onnavi_request_open in popover.jsx), so saying nothing keeps the old
-      // behaviour: the element asking is the element opened against.
+      // onnavi_request_open in popover.jsx): without an `anchor`, the element
+      // asking is the element opened against.
       return dispatchCustomEvent(target, "navi_request_open", {
         event,
         source: resolveCommandProxySource(source),
@@ -37548,8 +37616,8 @@ const usePopupContentMount = (
  * are no-ops.
  *
  * Behavior:
- *   - No <dialog>/<details>/[popover] ancestor → runs like a normal
- *     useLayoutEffect with the provided deps.
+ *   - No <dialog>/<details>/[popover]/[aria-expanded] ancestor → runs like a
+ *     normal useLayoutEffect with the provided deps.
  *   - Inside a closed/hidden ancestor → skips the initial run; instead runs
  *     the callback once the ancestor opens — see @jsenv/dom's own
  *     observeAncestorOpenState for exactly how that's detected, and why it
@@ -37563,8 +37631,9 @@ const usePopupContentMount = (
  *     reveals nothing about them, so it does not re-run them either. See
  *     isDisplayedDespiteClosedAncestor in @jsenv/dom.
  *
- * The callback's second argument is always a `navi_displayed` CustomEvent,
- * with `detail: { ancestor, ancestorType, becauseAncestorOpened }`:
+ * The callback is called with the element (`ref.current`), and a
+ * `navi_displayed` CustomEvent as its second argument, with
+ * `detail: { ancestor, ancestorType, becauseAncestorOpened }`:
  *   - No <dialog>/<details>/[popover]/[aria-expanded] ancestor at all →
  *     `{ ancestor: document, ancestorType: "document" }`.
  *   - Otherwise → `{ ancestor: <the matched element>, ancestorType: "dialog"
@@ -37729,6 +37798,8 @@ const createDisplayedEvent = (ancestor, becauseAncestorOpened) => {
 // see also https://github.com/preactjs/preact/issues/1255
 
 
+const NO_ELEMENT_REF = { current: null };
+
 /**
  * Programmatic autofocus that runs after Preact layout effects are flushed.
  *
@@ -37781,13 +37852,12 @@ const createDisplayedEvent = (ancestor, becauseAncestorOpened) => {
  *   the browser's built-in scroll-into-view that accompanies focus.
  * @param {boolean} [options.focusVisible]
  *   Passed as `focusVisible` to `element.focus()`.
- * @param {boolean} [options.autoFocusSelect]
+ * @param {boolean} [options.autoSelect]
  *   When true, also calls `element.select()` after focusing (useful for text inputs).
- * @returns {Function} triggerAutofocus — can be called manually with a synthetic
- *   event to re-run the focus logic outside of the layout-effect lifecycle.
+ * @returns {object} The attributes to spread on the element: `navi-autofocus`
+ *   (and `navi-autofocus-select`), with `autoFocus` set to undefined so the
+ *   native attribute never lands on the node.
  */
-const NO_ELEMENT_REF = { current: null };
-
 const useAutoFocus = (
   focusableElementRef,
   autoFocus,
@@ -37982,9 +38052,10 @@ document.body.addEventListener(
  * and nothing about it stops someone from starting a run on every row before
  * any of them comes back: a dozen requests in flight, a dozen rows waiting, and
  * a server asked to do a dozen things at once because a list happened to be
- * long. The guard is what makes the surface say "not yet" instead — the rows
- * that are not running go read-only and say what they are waiting for, and the
- * next press is possible again the moment one of the runs comes back.
+ * long. The guard is what makes the surface say "not yet" instead — the
+ * controls that would start another run go read-only and say what they are
+ * waiting for, and the next press is possible again the moment one of the runs
+ * comes back.
  *
  * It counts runs, not values — which is what separates it from
  * `maxLengthGuard`, the one that says how many things a selection may HOLD.
@@ -38329,14 +38400,13 @@ const createControlGuard = (controller) => {
 };
 
 /**
- * Orchestrates the three rule managers for a UI state controller.
- *
- * Instead of holding `controller.controlInteraction` + `controller.controlValidity`
- * independently, a controller now has a single `controller.rules` object:
+ * Orchestrates the rule managers of a UI state controller, held together in
+ * one `controller.rules` object:
  *
  *   controller.rules.callout     — shared callout display manager
  *   controller.rules.interaction — interactivity gate (disabled/readonly/busy)
  *   controller.rules.validation  — value validity gate (required/pattern/etc.)
+ *   controller.rules.guard       — keystroke guard (charGuard/maxLengthGuard)
  *
  * The callout manager is created first so both interaction and validation
  * can use the same callout slot and the same lifecycle hooks.
@@ -40487,9 +40557,8 @@ const EMPTY_OBJECT = {};
  *   child changes → we update picker input → navi_ui_state_change fires →
  *   we see updatingRef=true → skip → no loop.
  *
- * This removes the need for `command="--navi-update"` on controls placed
- * inside the picker popup. It also means `commands.js` no longer has to
- * manually re-dispatch to inner controls.
+ * So a control placed inside the picker popup needs no
+ * `command="--navi-update"` to reach the picker input.
  */
 const useUIFacadeStateController = (props, realUIStateController) => {
   const firstChildControllerRef = useRef(null);
@@ -40981,9 +41050,10 @@ const uiStateHoldsNothing = (uiState) => {
  *    use `onInput` internally and route through `dispatchRequestAction` so the behavior
  *    is consistent regardless of input type.
  *
- * 2. Any field (text, checkbox, radio, picker…) can opt into debounce simply by passing
- *    a debounced action. The request-action event chain handles the timing centrally
- *    rather than each component having to manage its own debounce logic.
+ * 2. Any field (text, checkbox, radio, picker…) can opt into debounce with
+ *    `actionDebounce` (ms). The input effect every field installs (input_effect.js)
+ *    handles the timing centrally rather than each component having to manage its
+ *    own debounce logic.
  */
 const NO_ACTION_YET = Symbol("no_action_yet");
 
@@ -41059,7 +41129,7 @@ const ControlgroupChildrenWrapper = ({
 });
 
 /**
- * Core hook for interactive field components (InputText, InputCheckbox, etc.).
+ * Core hook for interactive field components (InputTextual, InputCheckbox, etc.).
  *
  * Sets up the full field lifecycle:
  * - Creates a UI state controller that manages state divergence between props and user interactions
@@ -41070,7 +41140,7 @@ const ControlgroupChildrenWrapper = ({
  * - Handles constraint validation and message props
  *
  * All state changes route through DOM events on the field element so that
- * external subscribers (e.g. useUIState, Selectable) receive every update.
+ * external subscribers (e.g. useControlUIState, Selectable) receive every update.
  *
  * @returns {[controlRootProps, controlHostProps, { uiStateController }]}
  */
@@ -42163,10 +42233,10 @@ const useReadOnlyUncontrolled = (props, controlInfo) => {
 };
 
 /**
- * Core hook for field group components (SelectableList, CheckboxList, etc.).
+ * Core hook for field group components (List selectable, CheckboxGroup, etc.).
  * - Creates a UI group state controller that aggregates child states into one group state
  * - Binds the group's action to the aggregated state signal
- * - Provides context to children: ParentUIStateController, FieldName, Disabled, ReadOnly,
+ * - Provides context to children: ParentUIStateController, ControlName, Disabled, ReadOnly,
  *   Required, Loading, Action, ActionRequester
  * - Overrides `onnavi_reset_ui_state` to cascade resets to all monitored children
  *   by dispatching `navi_reset_ui_state` DOM events on each child's DOM element
@@ -44701,10 +44771,10 @@ const LoadingRectangleSvg = ({
 }) => {
   // The stroke is centered on the path, so half of it falls outside: drawing
   // at half the stroke width puts its outer edge exactly on the box, whatever
-  // the box. It used to be a share of the smaller dimension (3%, floored at
-  // 2px), which held the line further and further inside as the box grew — a
-  // caller placing the outline with `inset` got the distance it asked for on a
-  // field and something several pixels inward on a card. Nothing needs the
+  // the box. Not a share of the smaller dimension (3%, floored at 2px): that
+  // holds the line further and further inside as the box grows — a caller
+  // placing the outline with `inset` gets the distance it asked for on a field
+  // and something several pixels inward on a card. Nothing needs the
   // extra room: the svg is `overflow: visible` and whoever positions the
   // wrapper already reserves the half stroke.
   const margin = strokeWidth / 2;
@@ -45357,16 +45427,6 @@ const css$Z = /* css */`@layer navi {
       border-radius: .2em;
     }
 
-    &[data-capitalize] {
-      text-transform: capitalize;
-
-      & .navi_text_sizer {
-        & .navi_text {
-          display: inline-block;
-        }
-      }
-    }
-
     &[data-shrinkwrap] {
       display: inline-block;
     }
@@ -45389,12 +45449,6 @@ time.navi_text {
 }
 
 .navi_text {
-  &[data-capitalize] {
-    &:first-letter, & .navi_text_sizer_placeholder:first-letter, & .navi_text_sizer_overlay:first-letter {
-      text-transform: uppercase;
-    }
-  }
-
   & .navi_text_sizer, & .navi_text_sizer_placeholder, & .navi_text_sizer_overlay {
     display: inherit;
     width: inherit;
@@ -45776,7 +45830,7 @@ const shouldInjectSpacingBetween = (left, right) => {
  *   boldStable?: boolean,
  *   shrinkWrap?: boolean,
  *   capitalize?: boolean,
- *   selectRange?: string | [number, number],
+ *   selectRange?: string | [number, number] | [string, string],
  *   childrenOutsideFlow?: import("ignore:preact").ComponentChildren,
  *   [key: string]: any,
  * }>}
@@ -45842,11 +45896,14 @@ const shouldInjectSpacingBetween = (left, right) => {
  *   text block from being wider than its content when inside a flex/grid container.
  *
  * @param {boolean} [capitalize]
- *   Uppercases the first letter of the text content via CSS.
+ *   Uppercases the first letter of the text, and only that one: "lundi 11 mai"
+ *   reads "Lundi 11 mai". Applied to the string the text starts with; a text
+ *   starting with an element keeps its first letter as written.
  *
- * @param {string|[number,number]} [selectRange]
- *   Selects a portion of the text on mount. Pass a substring to search for, or
- *   a `[start, end]` character-offset tuple.
+ * @param {string|[number,number]|[string,string]} [selectRange]
+ *   Selects a portion of the text on mount. Pass a substring to search for, a
+ *   `[start, end]` character-offset tuple, or a `[startText, endText]` pair of
+ *   substrings selecting from the first to the end of the second.
  *
  * @param {import("ignore:preact").ComponentChildren} [childrenOutsideFlow]
  *   Rendered after children but outside the text spacing/flow logic. Used
@@ -45961,11 +46018,13 @@ const TextUI = props => {
     shrinkWrap,
     ...rest
   } = props;
+  if (capitalize) {
+    children = capitalizeFirstLetter(children);
+  }
   const defaultSpace = preventSpaceUnderlines ? FAKE_SPACE : REGULAR_SPACE;
   const resolvedSpacing = spacing ?? defaultSpace;
   const boxProps = {
     "as": "span",
-    "data-capitalize": capitalize ? "" : undefined,
     "data-shrinkwrap": shrinkWrap ? "" : undefined,
     ...rest,
     ref,
@@ -46266,6 +46325,28 @@ const Icon = ({
   });
 };
 
+// On the string rather than with ::first-letter, which needs a block container:
+// an inline text made one is an atomic box, and the ellipsis of the line
+// holding it (a Picker's value) can then no longer cut it. The string is also
+// what every copy of the children (sizer, bold background) renders, so they
+// all read the same. Leading spaces and punctuation are skipped, and a text
+// starting with a digit is left as it is, as ::first-letter would.
+const capitalizeFirstLetter = children => {
+  if (typeof children === "string") {
+    return children.replace(FIRST_LOWERCASE_LETTER_REGEXP, (match, lead, letter) => `${lead}${letter.toLocaleUpperCase()}`);
+  }
+  if (Array.isArray(children) && children.length > 0) {
+    const first = children[0];
+    const firstCapitalized = capitalizeFirstLetter(first);
+    if (firstCapitalized === first) {
+      return children;
+    }
+    return [firstCapitalized, ...children.slice(1)];
+  }
+  return children;
+};
+const FIRST_LOWERCASE_LETTER_REGEXP = /^([\s\p{P}]*)(\p{Ll})/u;
+
 /**
  * Where a link leads, asked for when the pointer or the focus arrives on it:
  * the moment the user signals a destination, before the press. Only what the
@@ -46716,7 +46797,7 @@ Object.assign(PSEUDO_CLASSES, {
  * @param {object} props
  * @param {string} [props.href] - Destination. Also the default `value`, and
  *   (when `hrefFallback`) the default visible text.
- * @param {import("../route.js").Route} [props.route] - Renders via `route`
+ * @param {object} [props.route] - Renders via `route`
  *   instead of a raw `href`: the URL is built from the route (see
  *   `routeParams`) and "current" is derived from whether the route matches.
  * @param {object} [props.routeParams] - Params passed to `route.buildUrl`.
@@ -46740,14 +46821,14 @@ Object.assign(PSEUDO_CLASSES, {
  *   (`navi_value`); defaults to `href`.
  * @param {boolean} [props.current] - Forces the "current" state on (otherwise
  *   derived from the href/route).
- * @param {import("../route.js").Route|import("../route.js").Route[]} [props.currentExcept] -
+ * @param {object|object[]} [props.currentExcept] -
  *   Route(s) inside this link's own that are NOT it: while one of them matches,
  *   the link is not current even though its route still is. A bar entry
  *   standing for a whole section, and one place under that section the entry
  *   does not stand for — settings reached from everywhere and shown over
  *   whatever the reader was on. Nothing about the routing changes: the url is
  *   in the section, only the link stops claiming "you are here".
- * @param {import("../route.js").Route|import("../route.js").Route[]} [props.currentAlso] -
+ * @param {object|object[]} [props.currentAlso] -
  *   Route(s) other than this link's own that are it: the link is current while
  *   one of them matches. The other side of `currentExcept` — an entry standing
  *   for more than the one page it opens. `currentExcept` wins over it.
@@ -47660,6 +47741,7 @@ const positionOfCurrentIndicator = (currentIndicator, vertical) => {
  *   currentIndicator?: boolean|"top"|"bottom"|"left"|"right",
  *   currentIndicatorSlides?: boolean,
  *   slideContainer?: string,
+ *   panelPosition?: "before"|"after",
  * }>}
  * @param {boolean|"top"|"bottom"|"left"|"right"} [props.currentIndicator] - the
  *   bar that says which tab one is on, said once here rather than on every
@@ -47685,6 +47767,9 @@ const positionOfCurrentIndicator = (currentIndicator, vertical) => {
  *   container says which one is on screen, and pressing a tab travels there.
  *   Tabs that are places in the same screen rather than pages of their own —
  *   nothing is written to the URL and nothing is a link.
+ * @param {"before"|"after"} [props.panelPosition] - turns the row into folder
+ *   tabs: the current tab and the panel it opens share one surface, and this
+ *   says which side of the row the panel sits on.
  */
 const Nav = ({
   children,
@@ -48807,6 +48892,8 @@ const TABS_ALIGN_TO_JUSTIFY_CONTENT = {
  *   onChange?: (value: any) => void,
  *   tabsPosition?: "top"|"bottom"|"left"|"right",
  *   tabsAlign?: "start"|"center"|"end"|"stretch",
+ *   scrollablePage?: boolean,
+ *   maxLines?: number|false,
  *   borderWidth?: string|number,
  *   borderRadius?: string|number,
  *   tabBorderRadius?: string|number,
@@ -48986,7 +49073,7 @@ const Binder = ({
  *   position among its siblings.
  * @param {import("ignore:preact").ComponentChildren} [props.label] - What the tab
  *   shows.
- * @param {import("../route.js").Route} [props.route] - Makes the tab a `Link`
+ * @param {object} [props.route] - Makes the tab a `Link`
  *   to that route, and the binder follows the url: the open item is the one
  *   whose route matches, no `value`/`onChange` needed.
  * @param {string} [props.href] - Same, for a plain url.
@@ -49425,6 +49512,9 @@ const FixedBarStyleCSSVars = {
  *   `border={false}` for none.
  * @param {string|number} [props.maxWidth] - Keeps the bar lined up with a
  *   content column narrower than the window (it stays centered).
+ * @param {string|number} [props.padding=0] - Along the bar only: left/right on
+ *   a top or bottom bar, top/bottom on a side one. Across it, the size is
+ *   `height`/`width`.
  */
 const FixedBar = ({
   children,
@@ -50293,9 +50383,10 @@ const useExpandableContext = partName => {
  *   height too. `"idle"` builds it in a browser idle moment after load.
  *   `"while-opened"` throws the content away once the collapse
  *   settles — after the closing animation, so it still plays on real
- *   content — and rebuilds it from scratch on every expansion. Whatever the
- *   value, intent on the UI part (pointer entering it, focus landing in it)
- *   builds the content ahead of the click.
+ *   content — and rebuilds it from scratch on every expansion. Under the
+ *   other three, intent on the UI part (pointer entering it, focus landing in
+ *   it) builds the content ahead of the click; `"while-opened"` content is
+ *   never warmed, it is built at the open.
  */
 const Expandable = props => {
   import.meta.css = [css$R, "@jsenv/navi/src/control/expandable/expandable.jsx"];
@@ -51072,7 +51163,8 @@ const DARK_CONTRAST_LIGHTNESS_THRESHOLD = 0.65;
  * @param {string} accentColor - The accent color value. When it changes, attributes are recomputed.
  * @param {object} [options]
  * @param {string} [options.elementSelector] - CSS selector to find the element whose computed color is read.
- *   Defaults to the root element itself. Useful when the color is applied to a probe/child element.
+ *   Defaults to the root's own `data-visual-selector` attribute, else the root element itself.
+ *   Useful when the color is applied to a probe/child element.
  * @param {string} [options.colorProperty="backgroundColor"] - Computed style property to read (e.g. "color", "borderColor").
  */
 const useAccentColorAttributes = (
@@ -53117,16 +53209,18 @@ const css$L = /* css */`@layer navi {
 /**
  * Field — a semantic wrapper that connects a label to a form control.
  *
- * It generates a stable `fieldId` (or accepts an explicit `id`) that is
+ * It generates a stable `fieldId` (or accepts an explicit one) that is
  * automatically forwarded to the `Label` inside the field as `htmlFor` and to
- * any interactive control (Picker, Input, …) as its `id`, so clicking the
- * label focuses the control without requiring manual wiring.
+ * the labelable control inside it (Input, Select, Picker, Button) as its `id`,
+ * so clicking the label focuses the control without requiring manual wiring.
  *
  * It also tracks the readOnly / disabled / interactive state reported by its
  * child control and reflects it on the `Label` (dimmed color, cursor change).
  *
  * Props:
- *   id        — optional explicit id used as the field id instead of the auto-generated one
+ *   fieldId   — optional explicit field id instead of the auto-generated one (an `id`
+ *               is the wrapper's own DOM id)
+ *   as="label" — the field IS the label, wrapping its control: no id needed
  *   flex="y"  — vertical layout; automatically sets alignX="start" and data-vertical
  *   children  — any JSX; should contain a `Label` and a form control
  *   ...rest   — forwarded to the wrapping element (className, style, flex, spacing, …)
@@ -53333,6 +53427,7 @@ const InputUnitSlot = ({
 };
 const InputSlot = ({
   side,
+  children,
   ...props
 }) => {
   const ctx = useContext(InputTextualContext);
@@ -53362,7 +53457,11 @@ const InputSlot = ({
         e.preventDefault();
       }
     },
-    ...props
+    ...props,
+    children: jsx(ControlIdContext.Provider, {
+      value: undefined,
+      children: children
+    })
   });
 };
 
@@ -54827,9 +54926,9 @@ const InputWithListResolver = props => {
 };
 
 /**
- * InputWithList — connects an input to a SelectableList via its id.
+ * InputWithList — connects an input to a selectable List via its id.
  *
- * Usage: <Input navi-list="my-list-id" /> next to <SelectableList id="my-list-id" />
+ * Usage: <Input navi-list="my-list-id" /> next to <List selectable id="my-list-id">
  *
  * Behavior:
  *   - ArrowDown / ArrowUp move the list's "current item" without moving focus
@@ -55197,11 +55296,14 @@ const useAutoSelectReadOnly = (props) => {
  *
  * - charGuard — restricts which characters can be typed, pasted, or set externally.
  *   Accepts a preset name or a raw regex character class:
- *   "numeric"      → digits only, sets inputMode="numeric" + pattern auto
+ *   true / "auto"  → picked from the field: inputMode numeric/decimal, type tel/email
+ *   "numeric"      → digits only, sets inputMode="numeric"
+ *   "decimal"      → digits, minus, dot, comma, sets inputMode="decimal"
  *   "alpha"        → letters only
  *   "alphanumeric" → letters and digits
  *   "uppercase"    → uppercase letters only
  *   "tel"          → phone chars (digits, +, -, parens, space), sets inputMode="tel"
+ *   "email"        → what an email address is made of
  *   "card"         → credit card (digits and spaces), sets inputMode="numeric"
  *   "hex"          → hexadecimal digits
  *   "pin"          → numeric PIN, sets inputMode="numeric"
@@ -56272,18 +56374,13 @@ const commitSubtree = (controller, e) => {
 };
 
 /**
- *
- * Here we want the same behaviour as web standards:
- *
- * 1. When submitting the form URL does not change
- * 2. When form submission id done user is redirected (by default the current one)
- *    (we can configure this using target)
- *    So for example user might be reidrect to a page with the resource he just created
- *    I could create an example where we would put a link on the page to let user see what he created
- *    but by default user stays on the form allowing to create multiple resources at once
- *    And an other where he is redirected to the resource he created
- * 3. If form submission fails ideally we should display this somewhere on the UI
- *    right now it's just logged to the console I need to see how we can achieve this
+ * <Form>: the <form> element as a navi control group. Its named fields
+ * aggregate into one object; a submit checks their constraints, runs `action`
+ * with that object when it changed (docs/form_changed.md), and `command` — or
+ * the surface the form sits in — says what follows. The URL does not change on
+ * a submit, and a failing action is drawn as an error callout on the button
+ * that sent it (docs/error_handling.md). A form inside another form renders no
+ * <form> element (FormNested).
  */
 
 const Form = props => {
@@ -56923,9 +57020,9 @@ const offsetToPx = (offset, box) => {
 
 // A press landing while the track is already travelling: what is playing is
 // sent home in a fifth of the time it has left, and the press it could not take
-// yet is taken as soon as it lands. A press has to be FELT — nudging the pace
-// of a travel already in flight (what this used to do) reads as "nothing
-// happened", because the thing was moving before the click too. Getting there
+// yet is taken as soon as it lands. A press has to be FELT — merely nudging the
+// pace of a travel already in flight reads as "nothing happened", because the
+// thing was moving before the click too. Getting there
 // almost at once and setting off again is the click being answered.
 // Played out fast rather than cut short: ending it on the spot would jump.
 // Compounds, so two presses during one travel bring it home twice as sharply,
@@ -59523,13 +59620,12 @@ const SlideNavButton = ({
   autoFocus: "last-resort",
   icon: true,
   variant: "discrete"
-  // Takes the focus like any other button, on purpose. It used to refuse it
+  // Takes the focus like any other button, on purpose. Do not refuse it
   // (mousedown.preventDefault) to keep the keyboard where the user had put
-  // it — but pressing a way out with nothing focused then left the keyboard
-  // on nothing at all: the travel below only hands the focus to the slide
-  // arriving when it was leaving a slide, so a click from document.body
-  // arrived on document.body, and the next Tab started from the top of the
-  // page rather than from what is on screen.
+  // it: the travel below only hands the focus to the slide arriving when it
+  // was leaving a slide, so a press with nothing focused would arrive on
+  // document.body, and the next Tab would start from the top of the page
+  // rather than from what is on screen.
   //
   // Letting it focus is both the plain behaviour of a button and what makes
   // the rest fall into place: the press lands on the chevron, the slide left
@@ -59546,12 +59642,6 @@ const SlideNavButton = ({
   })
 });
 
-/**
- * The way out of a slide, and the way into the next one. Nothing but the
- * command plus the chevron that matches the travel: a row goes left/right, a
- * column up/down — so the button points where the slide actually goes without
- * the caller having to keep the two in sync.
- */
 /**
  * A way out pointing where it goes. It says a direction, not a slide: what is
  * over there is the map's business, and moving a screen changes nothing here.
@@ -61193,7 +61283,6 @@ const createSwipeToClose = (side, { grip } = {}) => {
       panelEl.style.transform = "";
       panelEl.style.clipPath = "";
       panelEl.style.transitionProperty = "";
-      panelEl.style.userSelect = "";
     };
     // The resting value is written first and the animation only covers the way
     // to it: both end on the same number, so nothing is seen changing when the
@@ -61237,10 +61326,6 @@ const createSwipeToClose = (side, { grip } = {}) => {
           return false;
         }
         panelEl.style.transitionProperty = "none";
-        panelEl.style.userSelect = "none";
-        // What the first pixels of the gesture may have started selecting is
-        // not a selection, it is the beginning of this travel.
-        window.getSelection().removeAllRanges();
         // The way out is the only way there is anything: pulling the other way
         // leans against a wall and comes back.
         return {
@@ -61946,7 +62031,7 @@ const css$E = /* css */`
          --navi-app-width rather than 3vvw): the gap must read as a small
          margin around the dialog, and 3% of a 1500px window is a 45px gap
          around a 600px app. Identical to 3vvw until the app declares
-         --navi-app-max-width. */
+         bands (--navi-app-max-width, or --navi-app-inset-* written by it). */
       --x-dialog-container-spacing: calc(0.03 * var(--navi-app-width));
 
       /* --navi-app-width, not --navi-vvw: a top-layer dialog is calibrated on
@@ -62663,7 +62748,7 @@ const css$E = /* css */`
  *   within its container (the viewport for `layer="top"`, the positioned
  *   ancestor for `layer="local"`) — Dialog is never anchored to a real
  *   element for positioning purposes. Same grammar as `Popover`'s own
- *   `positionArea` (see `popup_shared.js`'s `parsePositionArea`): a single
+ *   `positionArea` (see `parsePositionArea` in @jsenv/dom): a single
  *   compass token — `top`/`top-start`/`top-end`/`top-left`/`top-right`,
  *   `right`/`right-start`/`right-end`, `bottom`/`bottom-start`/
  *   `bottom-end`/`bottom-left`/`bottom-right`, `left`/`left-start`/
@@ -62682,12 +62767,12 @@ const css$E = /* css */`
  *   between the dialog and the edges of its container, whatever its
  *   `positionArea`: it both caps the dialog's own size (via
  *   `--x-dialog-container-spacing`, written from this prop) and offsets a docked
- *   one from the edge it docks to. Accepts a spacing token ("s", "m"…), a
- *   number of pixels, or a viewport length — "appw"/"apph" being the app's own
- *   screen (the visual viewport, or the narrower one the app declared with
- *   --navi-app-max-width) and "vvw"/"vvh" the visual viewport itself, which
- *   shrinks when the mobile keyboard opens. Pass 0 for a dialog
- *   meant to sit flush (a side panel).
+ *   one from the edge it docks to. Accepts a number of pixels, a viewport
+ *   length — "appw"/"apph" being the app's own screen (the visual viewport
+ *   minus the app's bands, see docs/safe_area.md) and
+ *   "vvw"/"vvh" the visual viewport itself, which shrinks when the mobile
+ *   keyboard opens — or a container length ("3cqw", the `layer="local"`
+ *   default). Pass 0 for a dialog meant to sit flush (a side panel).
  * @param {boolean} [props.backdrop=true] - Whether anything is laid between
  *   the dialog and the page at all — asked before any question of what an
  *   outside press does or how the backdrop is painted. `false` leaves the page
@@ -62700,10 +62785,12 @@ const css$E = /* css */`
  *   needs. What it gives up is what only a modal gets natively: the hardware
  *   back button no longer dismisses it. See docs/popup_backdrop.md.
  * @param {"close"|"cancel"|"capture"|"ignore"} [props.pressOutside="close"]
- *   - `"close"` closes the dialog on an outside press. `"capture"`/`"ignore"`
- *   both just absorb the press without closing (visually dimmed backdrop vs.
- *   not) — a dialog with a backdrop is modal one way or another, so there's
- *   always at least a press-absorbing backdrop regardless of this prop.
+ *   - `"close"` closes the dialog on an outside press, `"cancel"` closes it
+ *   as a cancel (what it holds reverts, as on Escape). `"capture"`/`"ignore"`
+ *   both just absorb the press without closing (`"capture"` paints the
+ *   blurred glass, `"ignore"` leaves the wall's paint alone) — a wall absorbs
+ *   the press whatever this prop says, natively for a modal and through the
+ *   sibling element for a local one.
  *   "Outside" is the dialog's own border box; a see-through dialog whose box is
  *   bigger than what it paints marks the difference with
  *   `data-navi-popup-outside` (see docs/popup_backdrop.md).
@@ -62778,11 +62865,10 @@ const css$E = /* css */`
  * @param {string} [props.animationDuration] - Maps to
  *   `--popup-animation-duration`.
  * @param {Element|{current: Element}|string} [props.anchor] - Never used for
- *   positioning (see this file's top comment), and ignored entirely unless
- *   `sizeFromAnchor` or `animation="lifting"` asks for it — the first sizes
- *   the dialog via the `--anchor-width`/`--anchor-height` CSS vars, the second
- *   makes the dialog come out of the anchor's own box. Used when the open
- *   itself names none — an anchor carried by the opening event
+ *   positioning (see this file's top comment); read by `sizeFromAnchor` (the
+ *   `--anchor-width`/`--anchor-height` CSS vars), by `animation="lifting"`
+ *   (the box the dialog comes out of) and by `mount`'s warm-on-intent. Used
+ *   when the open itself names none — an anchor carried by the opening event
  *   (`e.detail.anchor`) is about that one opening and comes first; left out,
  *   whatever triggered the open (`e.detail.source`). A string is resolved via
  *   `document.getElementById` when the dialog opens — see popover.jsx's own
@@ -62844,6 +62930,9 @@ const css$E = /* css */`
  *     focusable of its own.
  *   - `"restore"` — the dialog stays out of the opening focus chain unless it
  *     held focus when it closed.
+ *   - `false` — the dialog element itself is never where the focus lands; the
+ *     opening still hands the focus to what the dialog holds. Unlike
+ *     `Popover`'s `false`, it does not leave the keyboard where it was.
  *   Wherever the keyboard is a virtual one (a touch device), the surface is
  *   already what one arrives on: a popup is read before it is reached there, so
  *   the focus only leaves it for something that asked by name (`autoFocus` on
@@ -63089,8 +63178,8 @@ const useDialogProps = props => {
     // `backdrop` — see this file's top comment.
     layer = "top",
     dockedOnSmallTouchScreen,
-    // Same grammar as Popover's own positionArea — see this file's top
-    // comment and popup_shared.js's parsePositionArea.
+    // Same grammar as Popover's own positionArea — see parsePositionArea in
+    // @jsenv/dom.
     positionArea: positionAreaProp,
     // A dialog docked against an edge must keep the same gap its own size cap
     // already guarantees a centered one — so this drives both (see
@@ -63130,8 +63219,8 @@ const useDialogProps = props => {
     sizing = "auto",
     animation,
     lift = "box",
-    // Inert unless sizeFromAnchor below (see this file's top comment) —
-    // Dialog's own positioning is never relative to it.
+    // Never positioned against (see this file's top comment): read by
+    // sizeFromAnchor, by a lift, and by the warm-on-intent of `mount`.
     anchor,
     // Where a lift comes back to, when that is no longer the box it came out
     // of. Read at the close, not kept from the opening — see
@@ -63141,8 +63230,8 @@ const useDialogProps = props => {
     // See this prop's own JSDoc above for why a dialog does not follow its
     // trigger's box by default.
     sizeFromAnchor = false,
-    // Same meaning as Popover's own prop, applied to the only thing an anchor
-    // can do here: sizing under sizeFromAnchor.
+    // Same meaning as Popover's own prop, applied to what an anchor does here:
+    // sizing under sizeFromAnchor, and a lift.
     anchorCustomEventDetail = "override",
     // Makes the dialog itself a valid focus target so
     // autoFocus="last-resort" below has somewhere to land when it contains
@@ -63201,8 +63290,8 @@ const useDialogProps = props => {
   // narrower one) — and the positioned ancestor for a local one, where
   // reading 3% of the screen gives an absurd gap inside a small box.
   isTopLayer ? "3appw" : "3cqw");
-  // "expand || expandX", the shorthand semantics Popup used to apply before
-  // handing them over — the docked default only applies when neither was said
+  // `expand` is the shorthand for both axes; the docked default only applies
+  // when neither was said.
   const expandXUnset = expand === undefined && expandXProp === undefined;
   const expandX = expandXUnset ? isDocked && DOCKED.expandX : Boolean(expand) || Boolean(expandXProp);
   const scrollCapture = scrollCaptureProp ?? (isDocked ? DOCKED.scrollCapture : false);
@@ -63941,8 +64030,8 @@ const useDialogProps = props => {
     // ("[navi-control='dialog'], [navi-control='popover']" — see openEffect
     // above), and --navi-open/--navi-close resolve their target this way.
     "navi-control": "dialog",
-    // The protocol every command target answers. It came with the control
-    // group before; a dialog is layout and still has to answer --navi-open,
+    // The protocol every command target answers: a dialog is layout, not a
+    // control, and still has to answer --navi-open,
     // --navi-close and --navi-toggle, which are dispatched here and do not
     // bubble.
     "onnavi_command": e => {
@@ -63964,14 +64053,12 @@ const useDialogProps = props => {
     "popover": isTopLayerPopover ? "manual" : undefined,
     "baseClassName": "navi_dialog",
     "pseudoClasses": DIALOG_PSEUDO_CLASSES,
-    // Distinguishes the two renderers for the CSS above (position: fixed
-    // vs. absolute) — positioning itself is entirely JS-driven now (see
-    // openEffect's own positionDialog above), no data-position-area
-    // attribute needed at all.
     // A popup scrolls, and asking Box for that overflow is also what lets what
     // it contains claim header/footer/body (see box.jsx) — a popup is always a
     // scrolling area, so it says so once, here.
     "overflow": "auto",
+    // Tells the two renderers apart for the CSS above (position: fixed vs.
+    // absolute); the placement itself is JS-driven (positionDialog).
     "data-layer": layer,
     // The sheet shape is live in CSS, not just a set of resolved defaults:
     // it is what withdraws the caller's --dialog-max-width (see the stylesheet
@@ -64475,8 +64562,8 @@ const css$D = /* css */`
  *   whole viewport. A real `anchor` works with either.
  * @param {string} [props.positionArea="bottom"] - Where to place the popover
  *   relative to its `anchor` (or its container, if there is none). Same
- *   grammar as `Dialog`'s own `positionArea` (see `popup_shared.js`'s
- *   `parsePositionArea`): a single compass token — `top`/`top-start`/
+ *   grammar as `Dialog`'s own `positionArea` (see `parsePositionArea` in
+ *   @jsenv/dom): a single compass token — `top`/`top-start`/
  *   `top-end`/`top-left`/`top-right`, `right`/`right-start`/`right-end`,
  *   `bottom`/`bottom-start`/`bottom-end`/`bottom-left`/`bottom-right`,
  *   `left`/`left-start`/`left-end`, or `center`. A bare token means no
@@ -64505,8 +64592,9 @@ const css$D = /* css */`
  *   See docs/popup_backdrop.md.
  * @param {"close"|"cancel"|"capture"|"ignore"} [props.pressOutside="ignore"]
  *   - `"ignore"` (default): no backdrop at all, outside presses pass straight
- *   through. `"close"` closes the popover on an outside press. `"capture"`
- *   absorbs the press (dims the backdrop) without closing. Note this
+ *   through. `"close"` closes the popover on an outside press, `"cancel"`
+ *   closes it as a cancel (what it holds reverts, as on Escape). `"capture"`
+ *   absorbs the press (blurred glass) without closing. Note this
  *   default differs from `Dialog`'s own (`"close"`) — a popover is
  *   typically a lightweight, non-modal affordance. "Outside" is the popover's
  *   own border box; a see-through popover whose box is bigger than what it
@@ -64540,9 +64628,11 @@ const css$D = /* css */`
  *   popover so the page/container behind it can't scroll while it's open.
  * @param {boolean} [props.focusCapture] - Traps Tab navigation inside the
  *   popover (see `focus_trap.js`).
- * @param {boolean|"auto"|"fading"|"scaling"|"sliding"|`slide-from-${string}`} [props.animation]
- *   - `true`/`"auto"` resolves to a concrete `"slide-from-*"` direction
- *   based on `positionArea`. Any other explicit value is used as-is.
+ * @param {boolean|"auto"|"fading"|"scaling"|"sliding"|`slide-from-${string}`|"expanding"|`expand-${string}`} [props.animation]
+ *   - `true`/`"auto"` resolves to `"scaling"` for a real anchor or a centered
+ *   `positionArea`, and to a concrete `"slide-from-*"` direction otherwise.
+ *   `"expanding"`/`"expand-*"` grow out of a real anchor (see popup_css.js).
+ *   Any other explicit value is used as-is.
  * @param {string} [props.animationDuration] - Maps to
  *   `--popup-animation-duration`.
  * @param {Element|{current: Element}|string} [props.anchor] - The element the
@@ -64654,7 +64744,7 @@ const css$D = /* css */`
  * @param {object} [props.openController] - Advanced: an externally-owned
  *   open controller (see `open_controller.js`) for a caller that wants to
  *   drive open/close itself instead of `open`/`defaultOpen`/`onClose` (used
- *   by `picker_custom.jsx`/`side_panel.jsx`).
+ *   by `picker_custom.jsx`).
  * @param {"always"|"idle"|"from-first-open"|"while-opened"} [props.mount] - When
  *   `children` are built and thrown away (see popup_content_mount.js).
  *   `"from-first-open"` (the default) builds them on the first open and keeps
@@ -64966,12 +65056,10 @@ const usePopoverProps = props => {
       unfreezeSize(popoverEl);
     }
   }, [sizing]);
-  // The custom renderer's own starting-hidden state is a stylesheet default
-  // now (&:not([popover]) { display: none } on .navi_popover/
-  // .navi_popover_backdrop above) rather than set here imperatively — a
-  // plain div has no native default the way [popover]/<dialog> do, so
-  // leaving this to a layout effect meant an actual (if narrow) window
-  // where the browser could paint it visible before this ever ran.
+  // The custom renderer starts hidden from the stylesheet ([navi-hidden] on
+  // .navi_popover/.navi_popover_backdrop above), never from a layout effect:
+  // a plain div has no native hidden default the way [popover]/<dialog> do,
+  // and an effect leaves a window where the browser paints it visible first.
   // aria-expanded starts "false" the same way, but via a static literal
   // JSX prop on contentProps/backdropProps below instead of a layout
   // effect — see that prop's own comment for why a *constant* value there
@@ -64990,8 +65078,8 @@ const usePopoverProps = props => {
   openController.getElement = () => ref.current;
   openController.openEffect = e => {
     const popoverEl = ref.current;
-    // backdropEl is null when pressOutside is "ignore" —
-    // the backdrop isn't rendered at all in that case.
+    // backdropEl is null when there is no wall (pressOutside "ignore", or
+    // backdrop={false}): the backdrop isn't rendered at all then.
     const backdropEl = backdropRef.current;
     if (!popoverEl) {
       {
@@ -65052,10 +65140,8 @@ const usePopoverProps = props => {
     // needed here.
     const positionedAncestor = getPositionedParent(popoverEl);
     // Drives the via-attribute renderer's own position: fixed/absolute
-    // switch (see this file's top comment) — set here, well before any
-    // positioning/measurement runs, so there's no ordering subtlety to get
-    // wrong (unlike the CSS this replaced, which keyed off the resolved
-    // animation instead, known too late relative to the first measurement).
+    // switch (see this file's top comment) — set here, before any
+    // positioning/measurement runs, so the first measurement already sees it.
     // True only for a real anchor that itself scrolls with the document —
     // that's the one case `absolute` (scrolling in lockstep with it) is
     // correct; not just "has an anchor at all", since an anchor that's
@@ -65105,10 +65191,9 @@ const usePopoverProps = props => {
       disarmBackdropHideRef.current?.();
       disarmBackdropHideRef.current = null;
       // transitionProperty stays "none" here for both — reset later, in the
-      // final commit step alongside popoverEl's own (not resumed early the
-      // way it briefly was), so a `silent` open (see above) can keep both
-      // elements' transitions suppressed right up until after their
-      // aria-expanded flip, the same way it does for popoverEl.
+      // final commit step alongside popoverEl's own, so a `silent` open (see
+      // above) can keep both elements' transitions suppressed right up until
+      // after their aria-expanded flip, the same way it does for popoverEl.
       backdropEl.style.transitionProperty = "none";
       if (isTopLayer) {
         // Hidden first if a previous close's deferred hidePopover() (see
@@ -65534,16 +65619,10 @@ const usePopoverProps = props => {
       // current unconditionally on every call, and treats their mere
       // *presence* as "already positioned this session — stay on this
       // side unless it no longer fits" (its own anti-oscillation guard for
-      // repositioning mid-open, e.g. on scroll/resize). Popover's own CSS
-      // doesn't read these anymore (slide direction is resolved in JS now,
-      // see resolveDirectionValue), which is why the clearing that used to
-      // live here was removed — but that removal missed this second,
-      // still-live purpose: without clearing them on close, a later reopen
-      // sees a stale, "already positioned" value left over from a
-      // *previous* open (e.g. the container-aligned collapse from an
-      // anchorless silent open) and wrongly stays sticky to it instead of
-      // resolving fresh from the current positionArea/anchor — a real,
-      // reproduced bug, not just a leftover no-op.
+      // repositioning mid-open, e.g. on scroll/resize). Cleared on close so a
+      // later reopen resolves fresh from the current positionArea/anchor
+      // instead of staying sticky to a side left over from a previous open
+      // (e.g. the container-aligned collapse from an anchorless silent open).
       popoverEl.removeAttribute("data-position-y-current");
       popoverEl.removeAttribute("data-position-x-current");
       cleanup();
@@ -65673,8 +65752,8 @@ const usePopoverProps = props => {
     // ("[navi-control='dialog'], [navi-control='popover']"), and
     // --navi-open/--navi-close resolve their target this way.
     "navi-control": "popover",
-    // The protocol every command target answers. It came with the control
-    // group before; a popover is layout and still has to answer --navi-open,
+    // The protocol every command target answers: a popover is layout, not a
+    // control, and still has to answer --navi-open,
     // --navi-close and --navi-toggle, which are dispatched here and do not
     // bubble.
     "onnavi_command": e => {
@@ -65714,7 +65793,7 @@ const usePopoverProps = props => {
     // already arrive here as plain props via ...rest (wired by
     // UncontrolledPopover above, forwarded through ControlledPopover's own
     // {...props} spread) — nothing extra to add here. A controlled caller
-    // (picker_custom.jsx/side_panel.jsx) wires its own equivalent handling
+    // (picker_custom.jsx) wires its own equivalent handling
     // directly against its own openController instead.
   });
   return [hasBackdrop ? backdropProps : null, contentProps];
@@ -65746,9 +65825,6 @@ const POPUP_STYLE_CSS_VARS = {
   maxHeight: "--popover-max-height"
 };
 
-// parsePositionArea/POSITION_AREA_X/Y_VALUES moved to popup_shared.js — same
-// grammar Dialog's own layer="local"/"top" now shares.
-
 /**
  * Shared by both renderers: parses `positionArea` and resolves
  * `animation="auto"`/`true`. `animationAnchor` is the real anchor element
@@ -65776,15 +65852,6 @@ const resolvePositionAreaAndAnimationKind = ({
     resolvedAnimationKind
   };
 };
-
-// resolveDirectionValue/resolveAutoAnimationKind moved to popup_shared.js —
-// same logic Dialog's own auto-animation resolution now shares, since it
-// never has a real anchor either (always the "anchor === undefined" path).
-
-// suppressPointerEventsDuringTransition/armPointerDownOutsideClose moved to
-// popup_shared.js — same helpers Dialog's own custom renderer needs, no
-// Popover-specific knowledge in either.
-
 Popover.Close = PopupClose;
 
 installImportMetaCssBuild(import.meta);
@@ -65823,11 +65890,12 @@ const css$C = /* css */`@layer navi {
  * @param {"top"|"local"} [props.layer] - Forwarded as-is to whichever of
  *   `Dialog`/`Popover` renders — see either component's own doc.
  * @param {Element|{current: Element}} [props.anchor] - Forwarded as-is —
- *   positioning for `Popover`, and for `Dialog` sizing only, and only when
- *   `sizeFromAnchor` is also passed (see each component's own doc).
+ *   positioning for `Popover`; for `Dialog`, the box it sizes from under
+ *   `sizeFromAnchor` and lifts out of under `animation="lifting"`. In both,
+ *   intent on the anchor warms the content (see `mount`).
  * @param {"override"|"ignore"} [props.anchorCustomEventDetail] - Forwarded
  *   as-is to both — what it governs differs (positioning for `Popover`,
- *   `sizeFromAnchor` sizing for `Dialog`), but "ignore whatever anchor the
+ *   sizing and lifting for `Dialog`), but "ignore whatever anchor the
  *   triggering event carried" has to mean the same thing in either mode.
  * @param {string} [props.marginWithAnchor] - **Popover-only**, destructured
  *   out so it can't leak onto the real `<dialog>` element as a stray DOM
@@ -65845,6 +65913,8 @@ const css$C = /* css */`@layer navi {
  *   `maxWidth` below.
  * @param {boolean} [props.sizeFromAnchor] - **Dialog-only**, same guard.
  * @param {"box"|"scene"} [props.lift] - **Dialog-only**, same guard.
+ * @param {Element|{current: Element}|string} [props.liftAnchor] -
+ *   **Dialog-only**, same guard.
  * @param {string} [props.positionArea] - Forwarded as-is — `Dialog` and
  *   `Popover` have different own defaults (`"center"` vs. `"bottom"`),
  *   deliberately not homogenized here (each reads best for its own typical
@@ -65857,8 +65927,9 @@ const css$C = /* css */`@layer navi {
  *   the screen-size check happens to pick, which defeats the point of
  *   having one shared API in the first place. Note this only says what a
  *   press outside *does*; whether it reaches the page at all is `backdrop`
- *   below, and `"ignore"`/`"capture"` describe a wall either way — the popup
- *   absorbs the press without closing, dimmed or not.
+ *   below. `"capture"` is a wall that absorbs the press without closing, in
+ *   either mode. `"ignore"` is not the same in both: a `Dialog` keeps its
+ *   wall, a `Popover` lays none and the press reaches the page.
  * @param {boolean} [props.backdrop] - Whether anything is laid between the
  *   popup and the page at all: `false` lets a press outside both dismiss the
  *   popup and reach whatever it landed on, in one gesture. Forwarded as-is and
@@ -65877,8 +65948,13 @@ const css$C = /* css */`@layer navi {
  *   identically): the wash the backdrop paints over what is behind.
  * @param {string} [props.backdropFilter] - Forwarded as-is: what that wash
  *   does to the picture underneath, `"blur(4px)"` and the like.
- * @param {boolean|"auto"|"fading"|"scaling"|"sliding"|"expanding"|`slide-from-${string}`|`expand-${string}`} [props.animation]
- *   - Forwarded as-is.
+ * @param {boolean|"auto"|"fading"|"scaling"|"sliding"|`slide-from-${string}`|"expanding"|`expand-${string}`|"lifting"|{open: boolean|"auto"|"fading"|"scaling"|"sliding"|`slide-from-${string}`, close: "lifting"}} [props.animation]
+ *   - Forwarded to whichever renders — see either component's own doc.
+ *   `"expanding"`/`"expand-*"` are `Popover`'s own; `"lifting"` and
+ *   `{ open, close: "lifting" }` are `Dialog`'s. A popover has no lift, so in
+ *   popover mode `"lifting"` plays no movement (what a dialog does with no
+ *   anchor to lift out of) and the object form opens with its `open`, which
+ *   the close plays backwards like every other kind.
  * @param {string} [props.animationDuration] - Forwarded as-is.
  * @param {string} [props.maxWidth] - Forwarded as-is to both; also read
  *   here directly to help decide the automatic `mode` (a fixed length under
@@ -65898,11 +65974,15 @@ const css$C = /* css */`@layer navi {
  *   `--x-popover-max-width`) instead of its content width — same meaning
  *   whichever mode the screen-size resolution picks.
  * @param {boolean} [props.expandY] - Same, vertically (`data-expand-y`).
- * @param {boolean} [props.scrollCapture] - Forwarded as-is.
+ * @param {boolean|"dialog"|"popover"} [props.scrollCapture] - Forwarded to
+ *   both; a mode name traps scroll only when that mode is the one rendered.
  * @param {boolean} [props.open] - Forwarded as-is (controlled).
- * @param {import("@preact/signals").Signal<boolean>} [props.signal] -
+ * @param {import("@preact/signals").Signal<any>} [props.signal] -
  *   Forwarded as-is: one binding to both drive the popup's open state and
  *   know where it is (see `Dialog`/`Popover`'s own `signal`).
+ * @param {any} [props.value] - Forwarded as-is: what `signal` holds while
+ *   THIS popup is open, for several sharing one signal (see
+ *   `Dialog`/`Popover`'s own `value`).
  * @param {boolean} [props.defaultOpen] - Forwarded as-is (uncontrolled,
  *   mount-only).
  * @param {(event: Event) => void} [props.onClose] - Forwarded as-is.
@@ -65917,6 +65997,8 @@ const css$C = /* css */`@layer navi {
  *   them afterwards. `"always"` builds them right away, for content something
  *   depends on while the popup is still closed: a value read off it, fields a
  *   surrounding form collects on submit, a size measured from outside.
+ *   `"idle"` builds them in a browser idle moment after load — `"always"`
+ *   minus the cost on the critical render.
  *   `"while-opened"` throws them away once the popup has finished closing, for
  *   content whose fresh state is its initial state: an uncontrolled field
  *   seeded from a `defaultValue` that changed while the popup was closed.
@@ -65938,6 +66020,8 @@ const Popup = props => {
     // mode the automatic screen-size resolution happens to pick.
     pressOutside = "close",
     backdrop,
+    // A popover is handed only the values it understands (toPopoverAnimation).
+    animation,
     // Popover-only (see this component's own doc) — destructured out so
     // they're never part of ...rest, and therefore never forwarded to
     // Dialog below, where they'd otherwise leak onto the real <dialog>
@@ -65952,6 +66036,7 @@ const Popup = props => {
     dockedOnSmallTouchScreen,
     sizeFromAnchor,
     lift,
+    liftAnchor,
     ...rest
   } = props;
   const [mode] = useResolvedPopupMode(modeProp, maxWidth, {
@@ -65971,6 +66056,8 @@ const Popup = props => {
       dockedOnSmallTouchScreen: dockedOnSmallTouchScreen,
       sizeFromAnchor: sizeFromAnchor,
       lift: lift,
+      liftAnchor: liftAnchor,
+      animation: animation,
       maxWidth: maxWidth,
       pressOutside: pressOutside,
       backdrop: backdrop,
@@ -65984,6 +66071,7 @@ const Popup = props => {
   }
   return jsx(Popover, {
     ...rest,
+    animation: toPopoverAnimation(animation),
     maxWidth: maxWidth,
     pressOutside: pressOutside,
     backdrop: backdrop,
@@ -66001,6 +66089,18 @@ const Popup = props => {
 };
 Popup.Close = PopupClose;
 
+// What Dialog's own animation values mean to a popover, which has no lift
+// (see the `animation` doc above).
+const toPopoverAnimation = animation => {
+  if (animation === "lifting") {
+    return undefined;
+  }
+  if (animation !== null && typeof animation === "object") {
+    return animation.open;
+  }
+  return animation;
+};
+
 installImportMetaCssBuild(import.meta);
 const css$B = /* css */`.navi_picker_callout_dock > [data-picker-content] {
   display: none;
@@ -66515,7 +66615,7 @@ const PickerCustom = props => {
       // Not on pickerProps (the trigger): commands.js's own
       // resolveClosestExpandable() does `el.closest("[aria-expanded]")` to
       // find where to dispatch navi_request_open/navi_request_close — and
-      // the popup itself now carries its own aria-expanded (see
+      // the popup itself carries its own aria-expanded (see
       // popover.jsx/dialog.jsx), which is *closer* than the picker's own
       // aria-expanded for anything dispatched from inside the popup's own
       // content (e.g. a `command="--navi-close"` button rendered as
@@ -66795,12 +66895,8 @@ const PickerContentInsidePopup = props => {
     mode,
     pointerLock,
     scrollCapture,
-    // No default here (matches Popover's own default of inactive) — the
-    // old, differently-named `focusTrap = true` prop never actually reached
-    // Popover's real `focusCapture` prop (see this file's history), so
-    // focus-trapping has never really been active for popover-mode pickers;
-    // defaulting the now-correctly-named prop to `true` would be a real,
-    // unintended behavior change riding along with the rename.
+    // No default here: Popover's own `focusCapture` is inactive by default,
+    // and a popover-mode picker traps the focus only when asked to.
     focusCapture,
     // Popup documents its own `layer` as forwarded as-is to Dialog/Popover,
     // but popupProps is built explicitly here, so it only travels if named.
@@ -67329,9 +67425,14 @@ const PickerNaviMinute = props => {
     step,
     value
   } = props;
+
+  // resolveInputProps has already run (PickerFirstResolver), so the type
+  // handed on is one the picker renders as is — the text field a navi numeric
+  // type resolves to, told what its value is.
   return jsx(Next, {
     ...props,
-    type: "minute",
+    type: "text",
+    "navi-input-type": "minute",
     children: jsxs(Box, {
       flex: "y",
       spacing: "s",
@@ -67437,6 +67538,8 @@ document.addEventListener(
   { capture: true, passive: true },
 );
 
+const FRAME_TIMEOUT_MS = 100;
+
 /**
  * Calls back once the browser has painted what is committed now.
  *
@@ -67448,10 +67551,9 @@ document.addEventListener(
  * has to survive. A frame not coming at all (a background tab) still answers,
  * late, through the timeout.
  *
+ * @param {() => void} callback
  * @returns {() => void} cancel
  */
-const FRAME_TIMEOUT_MS = 100;
-
 const afterPaint = (callback) => {
   let called = false;
   let timeoutId;
@@ -68998,7 +69100,7 @@ const SELECTABLE_INPUT_PSEUDO_CLASSES = [":hover", ":active", ":focus", ":focus-
 const SelectableInputProxy = props => {
   const selectableRealInputProps = useContext(SelectableRealInputContext);
   if (!selectableRealInputProps) {
-    throw new Error("Selectable.Input must be used within a Selectable component");
+    throw new Error("SelectableInput must be used within a row of a selectable List");
   }
 
   // Reset FieldToInterfaceContext to ensure we don't read id or report our
@@ -69036,7 +69138,7 @@ const SelectableInput = SelectableInputProxy;
  *     background-color: var(--search-match-background-color);
  *   }
  *
- * The `highlight` prop can be:
+ * The `highlight` argument of `useSearchHighlight` (a row's `matchInfo.matchRanges`) can be:
  *   - an array of [start, end] pairs — applied to all text nodes under the root element
  *   - an object { [domSelector]: [[start, end], …] } — applied to each sub-element
  *     matched by the selector (the format produced by createSearch)
@@ -72584,8 +72686,8 @@ const LIST_ITEM_STYLE_CSS_VARS = {
  *
  *   All three are about the row as a thing the LIST holds, never about the
  *   selection: a selectable row taken while its list sends says so on its own
- *   ("la sélection est en cours d'enregistrement"), and needs no `loading` for
- *   that.
+ *   ("le choix est en cours d'enregistrement", "la sélection…" in a `multiple`
+ *   list), and needs no `loading` for that.
  * @param {boolean} [props.readOnly]
  *   The row cannot be acted on: dimmed and click-through-proof, buttons inside
  *   it included.
@@ -73680,9 +73782,12 @@ const useItemStore = ({
  * (accessible via aria-labelledby) and a <ul role="group"> for the items.
  *
  * Props:
- *   label      — group label content
- *   labelProps — props forwarded to the label <span>
- *   ...rest    — forwarded to the outer <li role="presentation">
+ *   label            — group label content
+ *   labelProps       — props forwarded to the label <span>
+ *   hiddenWhileEmpty — the group leaves the flow (`display: none`) while it
+ *                      holds no real row — a search that emptied it, rows not
+ *                      arrived yet
+ *   ...rest          — forwarded to the outer <li role="presentation">
  */
 const ListItemGroup = ({
   label,
@@ -73794,7 +73899,7 @@ const ListResolved = /*#__PURE__*/createComponentResolver([ListFirstResolver, Li
  *   uiAction?: (value: any) => void,
  *   popover?: boolean,
  *   role?: string,
- *   renderBudget?: number | string,
+ *   renderBudget?: number | string | {initial?: number, after: number},
  *   renderBudgetSkipCheck?: boolean,
  *   virtualItemSize?: number,
  *   onListVisibleItemsChange?: (visibleItems: any[]) => void,
@@ -73823,6 +73928,7 @@ const ListResolved = /*#__PURE__*/createComponentResolver([ListFirstResolver, Li
  *   alignX?: string,
  *   alignY?: string,
  *   flexWrap?: boolean,
+ *   overflow?: string,
  *   expandX?: boolean,
  *   expandY?: boolean,
  *   expand?: boolean,
@@ -74009,10 +74115,10 @@ const ListResolved = /*#__PURE__*/createComponentResolver([ListFirstResolver, Li
  * @param {number} [props.parallelGuard=4]
  *   How many runs the rows may have in flight at once, for a list whose rows
  *   carry their own `action` (a button per row). While that many are out, every
- *   row that is not running goes read-only and says how many it is waiting on;
- *   the next press is possible again as soon as one comes back. `Infinity`
- *   lifts it. Counts runs, not values — `maxLengthGuard` above is the one that
- *   says how many things the selection may hold.
+ *   control that would start another run goes read-only and says how many it is
+ *   waiting on; the next press is possible again as soon as one comes back.
+ *   `Infinity` lifts it. Counts runs, not values — `maxLengthGuard` above is
+ *   the one that says how many things the selection may hold.
  * @param {boolean} [props.standalone]
  *   This list answers for itself: it does not register with the control group
  *   or picker around it, so its selection stays out of that value and nothing
@@ -76481,7 +76587,7 @@ const PickerFirstResolver = props => {
  * `focusOnOpen` below.
  *
  * @type {import("ignore:preact").FunctionComponent<{
- *   type?: "date" | "month" | "week" | "time" | "datetime" | "duration" | "color" | "file" | "text" | "object" | "array" | "confirm" | "navi_time" | "navi_number" | "navi_percentage",
+ *   type?: "date" | "month" | "week" | "time" | "datetime" | "duration" | "color" | "file" | "text" | "object" | "array" | "confirm" | "navi_time" | "navi_minute" | "navi_number" | "navi_percentage",
  *   value?: any,
  *   defaultValue?: any,
  *   name?: string,
@@ -76547,7 +76653,7 @@ const PickerFirstResolver = props => {
  *   popupTestId?: string,
  *   confirmTestId?: string,
  *   cancelTestId?: string,
- *   mount?: "always" | "from-first-open" | "while-opened",
+ *   mount?: "always" | "idle" | "from-first-open" | "while-opened",
  *   dialogExpand?: boolean,
  *   dialogExpandX?: boolean,
  *   dialogExpandY?: boolean,
@@ -76984,8 +77090,8 @@ const PickerFirstResolver = props => {
  *   itself names the trigger (see docs/testid.md); this one is for a test that
  *   needs the popup's own box — its surface, its position, its backdrop — and
  *   not only what it holds, which a testid inside the children already names.
- *   A `mode="callout"` picker has no popup of its own — the callout is the
- *   control's, shared with its constraint messages — so it is not named.
+ *   Under `mode="callout"` it names the callout element — the control's own,
+ *   shared with its constraint messages — while the children are shown in it.
  * @param {string} [confirmTestId] `type="confirm"`, default body: the
  *   `data-testid` of the yes button; `cancelTestId` that of the no button.
  *   Both are elements navi builds, which a test may not name by class (see
@@ -77373,7 +77479,7 @@ const TRAVELS_NONE = [];
  *   fallbackValue?: any,
  *   valueAtStep: (value: any, count: number) => any,
  *   compareValues?: (a: any, b: any) => number,
- *   renderValue?: (value: any) => import("ignore:preact").ComponentChildren,
+ *   renderValue?: (value: any, context: { maxLines?: number }) => import("ignore:preact").ComponentChildren,
  *   controlProps?: object,
  *   duration?: number,
  *   vertical?: boolean,
@@ -78848,7 +78954,8 @@ const css$q = /* css */`.navi_input_duration {
  * @param {boolean} [props.required]
  * @param {boolean} [props.loading]
  * @param {Function} [props.uiAction] - Called on every change with the ISO 8601 value
- * @param {Function} [props.action] - Called on form submission
+ * @param {Function} [props.action] - Runs with the ISO 8601 value when it changes,
+ *   like any control's `action` (busy state, error callout)
  * @param {preact.ComponentChild} [props.unitHour] - Custom label for the hour sub-field
  * @param {"auto"|"left"|"center"|"right"} [props.textAlign="auto"] - Text alignment of sub-inputs.
  *   "auto" aligns each field toward its neighbouring separator (first→right, last→left, middle/solo→center).
@@ -79859,11 +79966,12 @@ const splitPopupProps = props => {
  *   multi-word, one word at start (all match)  0.75
  *   phrase / word at word boundary           0.625
  *   phrase / words mid-word                  0.5
+ *   acronym (2+ chars, each the first letter of a word, in order)  0.4, 0.45 at start
  *   + case-exact bonus                       +0.125
  *   multi-word partial: score × (matched/total)
  *
  * matchRanges: [start, end] pairs (exclusive end) for CSS Highlight API.
- * Intended to be passed to useSearch as the matchFn parameter.
+ * Intended to be passed to useSearchText as the matchFn parameter.
  */
 const applySearch = (searchText, value) => {
   if (!searchText) {
@@ -80073,7 +80181,7 @@ const mergeRanges = (ranges) => {
 };
 
 /**
- * createSearch — builds a matchFn compatible with useSearch that searches
+ * createSearch — builds a matchFn compatible with useSearchText that searches
  * across multiple named fields of an item, each with its own DOM selector
  * and optional priority weight.
  *
@@ -80091,7 +80199,7 @@ const mergeRanges = (ranges) => {
  *   },
  * });
  *
- * const [orderedItems, getItemMatchInfo] = useSearch(search, items, searchPerson);
+ * const [orderedItems, getItemMatchInfo] = useSearchText(search, items, searchPerson);
  * // getItemMatchInfo(item).matchRanges is { ".name": [[start,end],…], ".address": [[start,end],…] }
  * // Pass the whole thing: <ListItem matchInfo={getItemMatchInfo(item)} />
  * // — ListItem handles the per-selector object format for matchRanges.
@@ -80158,7 +80266,7 @@ const useSearchText = (searchText, items, matchFn = applySearch) => {
     );
   }
   if (items === undefined) {
-    throw new TypeError("useSearch: items is undefined");
+    throw new TypeError("useSearchText: items is undefined");
   }
   const { orderedItems, matchInfoMap } = useMemo(() => {
     const { scoreEntries, nonMatched, matchInfoMap } = buildMatchInfo(
@@ -80283,17 +80391,19 @@ const buildMatchInfo = (searchText, items, matchFn) => {
  *   - orderedKeys: number[] of visible item keys sorted by explicit order
  *   - keyToOrderedIndex: Map key → orderedKeys index, gives O(1) indexOf equivalent
  *   - keyToExplicitOrder: Map key → explicitly passed index, used to maintain sort order
- *   - allItemsSignal: signal(array), all items including hidden, ordered by explicit index
- *   - visibleItemsSignal: signal(array), non-hidden items only
+ *   - itemsSignal: signal(array), all items including hidden, ordered by explicit index
+ *   - visibleItemsSignal: signal(array), items neither hidden nor filtered
  *   - countSignal: signal(number), count of all items including hidden
  *   - visibleCountSignal: signal(number), updated in microtask batch, only when count changes
- *   - propSignals: Map propName → signal(array), updated in microtask batch with element equality
+ *   - noMatchCountSignal: signal(number), items registered with `match: false`
  *   - onChangeRef: holds the latest onChange callback, called once per microtask batch
  *
- *   useTrackItem(id, data, index): registers the item with an explicitly provided index
- *   that determines its position among siblings. The caller (e.g. items.map) knows the
- *   correct order and passes it directly — no render-sequence deduction needed.
- *   Returns the visible rank (position among non-hidden items), or -1 when hidden.
+ *   useTrackItem(data): registers the item under `data.id`, at the position
+ *   `data.index` gives it among its siblings. The caller (e.g. items.map) knows
+ *   the correct order and passes it directly — no render-sequence deduction
+ *   needed. `data.role === "presentation"` keeps it out entirely.
+ *   Returns the visible rank (position among visible items), or -1 when hidden
+ *   or filtered.
  *   Signals and onChange are deferred to a microtask so multiple items updating
  *   in one commit cause only one notification.
  *
@@ -81061,7 +81171,7 @@ const WheelGroupContext = createContext(null);
  *   [key: string]: any,
  * }>}
  * @param {number} [props.visibleCount=3] - Odd number of rows visible in the viewport (the center one is the selection).
- * @param {number|string} [props.itemHeight] - Main-axis size of a row when vertical (number = px). Defaults to the CSS var (2.4em).
+ * @param {number|string} [props.itemHeight] - Main-axis size of a row when vertical (number = px). Defaults to the CSS var (1.8em).
  * @param {number|string} [props.itemWidth] - Main-axis size of a cell when horizontal (number = px). Defaults to the CSS var (3.5ch).
  * @param {number|string} [props.size] - Font size of the wheel: a size token ("s", "m", "l", "xl", …), a number (px), or a CSS length. Scales the digits and, since the row size is em-based, the row height too — a simple way to make the whole wheel bigger. An explicit itemHeight/itemWidth still overrides the row size.
  * @param {boolean} [props.bounded] - Give the wheel fixed ends instead of wrapping: it stops at the first/last value. By default the wheel loops endlessly (past the last value the first reappears, and vice-versa).
@@ -82557,7 +82667,7 @@ Wheel.Item = WheelItem;
  * @param {boolean} [props.horizontal] - Stack the (horizontal) wheels vertically instead of in a row.
  * @param {boolean} [props.glass] - Frost every wheel's neighbouring rows (see Wheel's glass prop) with one prop for the whole group.
  * @param {boolean} [props.frameBorder] - Line every wheel's center-window edges with a faint frame (off by default; independent of glass).
- * @param {boolean} [props.zoom] - Enlarge the centered value of every wheel (see Wheel's zoom prop) with one prop for the whole group.
+ * @param {boolean|number} [props.zoom] - Enlarge the centered value of every wheel (see Wheel's zoom prop) with one prop for the whole group.
  */
 const WheelGroup = props => {
   import.meta.css = [css$m, "@jsenv/navi/src/control/wheel/wheel.jsx"];
@@ -83342,8 +83452,8 @@ const stringifyTableSelectionValue = (type, value) => {
 
 /**
  * Check if a specific cell is selected
- * @param {Array} selection - The selection set or array
- * @param {{rowIndex: number, columnIndex: number}} cellPosition - Cell coordinates
+ * @param {string[]} selection - The table's `selection` array
+ * @param {{columnId: string, rowId: string}} cell - The cell's column and row ids
  * @returns {boolean} True if the cell is selected
  */
 const isCellSelected = (selection, { columnId, rowId }) => {
@@ -83356,8 +83466,8 @@ const isCellSelected = (selection, { columnId, rowId }) => {
 
 /**
  * Check if a specific row is selected
- * @param {Array} selection - The selection set or array
- * @param {number} rowIndex - Row index
+ * @param {string[]} selection - The table's `selection` array
+ * @param {string} rowId - The row's id (the `id` of its `<Tr>`)
  * @returns {boolean} True if the row is selected
  */
 const isRowSelected = (selection, rowId) => {
@@ -83367,8 +83477,8 @@ const isRowSelected = (selection, rowId) => {
 
 /**
  * Check if a specific column is selected
- * @param {Array} selection - The selection set or array
- * @param {number} columnIndex - Column index
+ * @param {string[]} selection - The table's `selection` array
+ * @param {string} columnId - The column's id (the `id` of its `<Col>`)
  * @returns {boolean} True if the column is selected
  */
 const isColumnSelected = (selection, columnId) => {
@@ -83903,7 +84013,7 @@ const initDragTableColumnViaPointer = (pointerdownEvent, {
 /**
  * Creates a MutationObserver that syncs attribute changes from original table to clone
  * @param {HTMLElement} table - The original table element
- * @param {HTMLElement} cloneTable - The cloned table element
+ * @param {HTMLElement} tableClone - The cloned table element
  * @returns {MutationObserver} The observer instance with disconnect method
  */
 const createTableAttributeSync = (table, tableClone) => {
@@ -85868,9 +85978,10 @@ const TableUI = /*#__PURE__*/forwardRef((props, ref) => {
  * KEY PRINCIPLES:
  * - Use inset box-shadow to ensure borders appear above table cell backgrounds
  * - Use ::before pseudo-elements with position: absolute for flexible positioning
- * - Each cell draws its own borders independently (no border-collapse by default)
+ * - Each cell draws its own borders; `borderCollapse` (on by default) keeps only
+ *   the right and bottom ones, plus top on the first row and left on the first column
  * - Selection borders override table borders using higher CSS specificity
- * - Sticky borders use thicker box-shadows in accent color (yellow)
+ * - Sticky borders use thicker box-shadows in an accent color
  *
  * TECHNICAL IMPLEMENTATION:
  * - All borders use inset box-shadow with specific directional mapping:
@@ -85878,9 +85989,8 @@ const TableUI = /*#__PURE__*/forwardRef((props, ref) => {
  *   * Right: inset -1px 0 0 0
  *   * Bottom: inset 0 -1px 0 0
  *   * Left: inset 1px 0 0 0
- * - Selection borders (blue) override table borders (red) in same pseudo-element
+ * - Selection borders override table borders in the same pseudo-element
  * - Sticky borders replace regular borders with thicker colored variants
- * - Border-collapse mode available as optional feature for future use
  *
  * Note how border disappear for sticky elements when using border-collapse (https://bugzilla.mozilla.org/show_bug.cgi?id=1727594)
  *
@@ -87014,11 +87124,18 @@ const BadgeCountOverflow = () => jsx("span", {
 });
 const MAX_CHAR_AS_CIRCLE = 3;
 const MAX_FOR_CIRCLE = 99;
+
+/**
+ * @param {boolean} [circle] Drawn round rather than as a pill. A circle holds
+ *   three characters at most, so `max` defaults to 99 with it ("99+"); a `max`
+ *   above 99, or `"none"`, lets a bigger count turn the circle into a pill as
+ *   it grows.
+ * @param {number|"none"} [max] The count above which `max` and a "+" are
+ *   written in its place. 99 under `circle`, no cap otherwise.
+ */
 const BadgeCount = ({
   children,
   maxElement = jsx(BadgeCountOverflow, {}),
-  // When you use max="none" (or max > 99) it might be a good idea to force ellipse
-  // so that visually the interface do not suddently switch from circle to ellipse depending on the count
   circle,
   max = circle ? MAX_FOR_CIRCLE : Infinity,
   integer,
@@ -88201,12 +88318,13 @@ const css$7 = /* css */`.navi_text_box {
  * - Displays optional icon(s) before and/or after the text
  * - Shrinks its width to fit the longest rendered text line (no trailing blank space)
  * - Wraps long text by default (overflow-wrap: anywhere)
- * - Shows ellipsis for a single overflowing unwrappable line
+ * - Shows an ellipsis instead under `singleLine`
  *
  * Props:
  *   iconBefore — element shown to the left of the text
  *   iconAfter  — element shown to the right of the text (stays on the same line)
- *   maxHeight  — CSS max-height string; when set, content that cannot wrap gets ellipsis
+ *   singleLine — keeps the text on one line, cut with an ellipsis (no width shrinking)
+ *   maxHeight  — CSS max-height string; content past it is clipped
  *   children   — the text content
  */
 const TextBox = ({
@@ -88385,6 +88503,41 @@ const css$4 = /* css */`.svg_mask_content * {
   stroke-opacity: 1 !important;
 }
 `;
+
+/**
+ * SVGMaskOverlay
+ *
+ * Creates composite SVGs by combining independent SVG elements with masking.
+ *
+ * This component solves the challenge of combining independently created SVGs into
+ * a single visual composition. Each SVG can have its own coordinate system, viewBox,
+ * and styling, allowing for maximum reusability of individual icons or graphics.
+ *
+ * When overlaying SVGs, each subsequent overlay "cuts out" its portion from the base SVG,
+ * creating a seamless integration where SVGs appear to interact with each other visually.
+ *
+ * Key benefits:
+ * - Maintains each SVG's independence - use them individually elsewhere
+ * - Handles different viewBox dimensions automatically
+ * - Works with any SVG components regardless of internal implementation
+ * - Supports unlimited overlay elements
+ * - Creates proper masking between elements for visual integration
+ *
+ * Usage example combining two independent icon components:
+ * ```jsx
+ * <SVGMaskOverlay viewBox="0 0 24 24">
+ *   <DatabaseSvg />
+ *   <svg x="12" y="12" width="16" height="16" overflow="visible">
+ *     <PlusSvg />
+ *   </svg>
+ * </SVGMaskOverlay>
+ * ```
+ *
+ * @param {Object} props - Component properties
+ * @param {string} props.viewBox - The main viewBox for the composition (required as soon as there is an overlay)
+ * @param {import("ignore:preact").ComponentChildren} props.children - SVG elements (first is base, rest are overlays)
+ * @returns {import("ignore:preact").VNode} A composed SVG with all elements properly masked
+ */
 const SVGMaskOverlay = ({
   viewBox,
   children
@@ -88397,7 +88550,7 @@ const SVGMaskOverlay = ({
     return children[0];
   }
   if (!viewBox) {
-    console.error("SVGComposition requires an explicit viewBox");
+    console.error("SVGMaskOverlay requires an explicit viewBox");
     return null;
   }
 
@@ -88457,6 +88610,8 @@ const css$3 = /* css */`@layer navi {
 }
 
 .navi_card_layout {
+  box-sizing: border-box;
+  min-height: 100%;
   padding-top: var(--layout-margin-top, var(--layout-margin-y, var(--layout-margin)));
   padding-right: var(--layout-margin-right, var(--layout-margin-x, var(--layout-margin)));
   padding-bottom: var(--layout-margin-bottom, var(--layout-margin-y, var(--layout-margin)));
@@ -88498,6 +88653,11 @@ const CardLayoutStyleCSSVars = {
   minHeight: "--layout-min-height"
 };
 /**
+ * The card is centered in the area both ways and is as wide as its content,
+ * `minWidth` at least. Down the area, the layout takes at least the height of
+ * what holds it, so how tall that area is is up to the page around it, as for
+ * `ViewportLayout`.
+ *
  * @type {import("ignore:preact").FunctionComponent<{
  *   alignX?: string,
  *   alignY?: string,
@@ -88527,6 +88687,11 @@ const CardLayout = ({
 }) => {
   import.meta.css = [css$3, "@jsenv/navi/src/layout/card_layout.jsx"];
   return jsx(Box, {
+    flex: true
+    // The card's place in the area; alignX/alignY below are its content's.
+    ,
+    alignX: "center",
+    alignY: "center",
     baseClassName: "navi_card_layout",
     styleCSSVars: CardLayoutStyleCSSVars,
     visualSelector: ".navi_card",
@@ -89338,7 +89503,8 @@ const css = /* css */`.navi_side_panel {
  *   interaction only makes sense paired with not letting focus silently
  *   leave the panel first. A box of the page whose press must not close the
  *   panel (a card that fills it) names the panel:
- *   `data-navi-popup-inside={id}` — see docs/popup_backdrop.md.
+ *   `data-navi-popup-inside={id}`, read when the panel has no wall
+ *   (`backdrop={false}`) — see docs/popup_backdrop.md.
  * @param {boolean} [props.closeByDrag=true] - Pushing the panel back
  *   towards the edge it is docked to closes it: the panel follows the
  *   pointer and finishes leaving (or comes back to rest) when it is
@@ -89353,8 +89519,8 @@ const css = /* css */`.navi_side_panel {
  *   doc).
  * @param {import("ignore:preact").ComponentChildren} props.children - No built-in
  *   close button — add one wherever it makes sense for the layout (e.g. a
- *   plain `<Button command="--navi-close">`), use `SidePanel.Head`'s own
- *   `closeButton` prop, or rely on `closeByPressOutside`/Escape instead.
+ *   plain `<Button command="--navi-close">` in `SidePanel.Head`), or rely on
+ *   `closeByPressOutside`/Escape instead.
  *   A form sent inside the panel closes it, as in any popup: a panel one
  *   keeps editing in says `command="--navi-void"` on that form (see
  *   docs/form_changed.md).
@@ -89445,9 +89611,7 @@ const toCssLength = (value, propertyName) => value === undefined || value === nu
  * Stuck to the top of the panel's own scrollable area (`position: sticky`)
  * regardless of `side` — only the panel's content in between scrolls. No
  * built-in padding or close button — add a `<Button command="--navi-close">`
- * (optionally with the `"navi_side_panel_head_close_button"` className, a
- * float-right utility this file's own CSS still provides) wherever it makes
- * sense for the layout.
+ * wherever it makes sense for the layout.
  *
  * @param {object} props
  * @param {string} [props.className] - Merged with the shared