@eifi1/ui-kit 0.34.0 → 0.35.0

package/src/components/dropdown.tsx

@@ -11,6 +11,7 @@ import { createPortal } from "react-dom";
 import { Search } from "lucide-react";
 import { anchoredInline, useAnchoredPanel } from "../hooks/use-anchored-panel";
 import { runOwnKeyDown, takeEscape, useDismissLayer, useOutsideClick } from "../hooks/use-dismiss";
+import type { DismissLayer } from "../hooks/use-dismiss";
 import { useOverlayHistory } from "../hooks/use-overlay-history";
 import { cn } from "../lib/cn";
 import { FIELD_TOUCH_TEXT } from "./field-base";
@@ -18,6 +19,12 @@ import { mergeRefs } from "./field-parts";
 import { FOCUS_RING } from "./focus-ring";
 import { useAnchorDir } from "./use-anchor-dir";
 
+/** Each list's Escape layer, filed under the refs {@link useDropdown} and
+ *  {@link useDropdownSearch} hand out (`panelRef`, `inputRef`), for the panel and the
+ *  search box those refs are passed to — see "The caller's own handler" on
+ *  {@link useDropdown} (round 0.35 R2). Weak: a list's refs go with its component. */
+const listLayers = new WeakMap<object, DismissLayer>();
+
 /**
  * Open state + close-on-outside-click for a custom dropdown — the two input-shaped
  * comboboxes, and an app's own panel. (MultiSelect, CurrencySelect, GroupedPicker and
@@ -88,6 +95,16 @@ import { useAnchorDir } from "./use-anchor-dir";
  * and stop it there — so a caller passes nothing new, AmountInput's currency chip
  * included.
  *
+ * ## The caller's own handler (round 0.35 R2)
+ *
+ * A caller's `onKeyDown` on {@link DropdownPanel} or {@link DropdownSearchHeader} hears
+ * Escape only while this list is the layer on top — the rule the dialogs got first. A
+ * tooltip over a row takes that press first, and the next one is the handler's, whose
+ * `preventDefault()` still keeps the list. The two find the list's layer through the
+ * refs this hook hands out — the panel through `panelRef`, the search box through
+ * {@link useDropdownSearch}'s `inputRef` — so a caller passes nothing new. One handed
+ * neither (an un-anchored panel may leave `panelRef` off) hears every key, as before.
+ *
  * `escapeLayer: false` is for a caller that registers its own layer: the editable
  * comboboxes, whose list can be "open" with nothing in it to show — an Escape there
  * belongs to the dialog.
@@ -129,7 +146,11 @@ export function useDropdown<T extends HTMLElement = HTMLDivElement>({
   }, []);
   useOutsideClick([wrapperRef, panelRef], close, open && !panelIsSheet);
   // See "Escape inside a dialog" above.
-  useDismissLayer(open && escapeLayer, closeToTrigger);
+  const layer = useDismissLayer(open && escapeLayer, closeToTrigger);
+  // Filed under `panelRef` for the panel's own handler — "The caller's own handler" above.
+  useEffect(() => {
+    listLayers.set(panelRef, layer);
+  }, [panelRef, layer]);
   // Same close path Escape and an outside click take, so a list dismissed by Back
   // cannot end up in a different state from one dismissed any other way.
   useOverlayHistory(open && backCloses, close);
@@ -145,6 +166,12 @@ export function useDropdownSearch<T extends HTMLElement = HTMLDivElement>() {
     useDropdown<T>();
   const [query, setQuery] = useState("");
   const inputRef = useRef<HTMLInputElement>(null);
+  // The list's layer again, under `inputRef` for the search box's handler (round 0.35
+  // R2). `useDropdown`'s effect, which runs first, has filed it under `panelRef`.
+  useEffect(() => {
+    const layer = listLayers.get(panelRef);
+    if (layer) listLayers.set(inputRef, layer);
+  }, [panelRef]);
   useEffect(() => {
     if (open) {
       // eslint-disable-next-line react-hooks/set-state-in-effect -- reset the query on open
@@ -237,7 +264,9 @@ export function DropdownSearchHeader({
         value={query}
         onChange={(e) => onQueryChange(e.target.value)}
         onKeyDown={(e) => {
-          runOwnKeyDown(e, onKeyDown);
+          // The caller's handler hears Escape only while the list is on top (round 0.35
+          // R2) — the layer filed under `inputRef`, when {@link useDropdownSearch} made it.
+          runOwnKeyDown(e, onKeyDown, listLayers.get(inputRef));
           // Focus is in this box while the list is up, so this is where Escape lands
           // first — see "Escape inside a dialog" on {@link useDropdown}.
           takeEscape(e);
@@ -271,30 +300,23 @@ export interface DropdownPanelProps extends ComponentPropsWithoutRef<"div"> {
   anchorRef?: RefObject<HTMLElement | null>;
   /** {@link useDropdown}'s `panelRef`, so an outside-click sees this as inside. Escape
    *  anywhere in the panel, on a row as in the search box, closes the list rather than
-   *  a dialog around it. */
+   *  a dialog around it. It is also how the panel finds the list's Escape layer, for
+   *  its `onKeyDown` (round 0.35 R2: see "The caller's own handler" there). */
   panelRef?: RefObject<HTMLDivElement | null>;
   /** Panel width in px, for the anchored form (the CSS `w-*` cannot be measured). */
   width?: number;
-  /** Which of the panel's edges lines up with the trigger's, room permitting.
-   *  `start`/`end` follow the trigger's reading direction — `end` is the right edge
-   *  in a left-to-right form and the left one in a right-to-left form — and are what
-   *  the kit's own pickers pass; `left`/`right` are physical and deprecated
-   *  ({@link PhysicalAlign}). Default `end`, which is the old `right` in a
-   *  left-to-right page. */
-  align?: "start" | "end" | PhysicalAlign;
+  /** Which of the panel's edges lines up with the trigger's, room permitting, by the
+   *  trigger's reading direction — `end` is the right edge in a left-to-right form and
+   *  the left one in a right-to-left form. Default `end`. The physical `left` / `right`
+   *  went in 0.35 (round 0.35 R1, refactor audit 2026-10, API-6e): `right` is `end` in a
+   *  left-to-right page, `left` is `start`. */
+  align?: "start" | "end";
   children: ReactNode;
   /** The panel, where the rest of the props go (0.34, API-2, refactor audit 2026-10) —
    *  merged with `panelRef`, so the outside-click still sees it. */
   ref?: Ref<HTMLDivElement>;
 }
 
-/**
- * @deprecated 0.34 — `"start"` / `"end"`, which follow the reading direction: `"right"`
- * is `"end"` in a left-to-right page, the default; removed in 0.35 (refactor audit
- * 2026-10, API-6e). The physical edges DropdownPanel's `align` still takes.
- */
-type PhysicalAlign = "left" | "right";
-
 /**
  * The floating popover surface for the searchable dropdowns: bordered/shadowed
  * panel, an optional `header` slot (search box, plus any actions), and a
@@ -344,7 +366,9 @@ export function DropdownPanel({
   // A row the keyboard reached by Tab holds focus too, and its Escape has to close the
   // list as the search box's does (BUG-1). The caller's handler first, as everywhere.
   const handleKeyDown = (e: ReactKeyboardEvent<HTMLDivElement>) => {
-    runOwnKeyDown(e, onKeyDown);
+    // It hears Escape only while the list is on top, a tooltip over a row taking the
+    // press first (round 0.35 R2) — the layer filed under `panelRef`, when handed one.
+    runOwnKeyDown(e, onKeyDown, panelRef && listLayers.get(panelRef));
     takeEscape(e);
   };
   const body = (

package/src/components/entity-combobox.tsx

@@ -73,7 +73,7 @@ export interface EntityComboboxProps<V extends string | number, C extends ComboC
    *  so it is the one control here that MUST be in the reader's language. */
   closeLabel?: string;
   /** The phone sheet's heading (and, as a string, its accessible name) for a picker
-   *  whose label is drawn by someone else — a form's `FormLabel`; `RhfCombobox`
+   *  whose label is drawn by someone else — a bound field's label; `RhfCombobox`
    *  hands its label over here (0.24). Default: `label`, then `placeholder`. */
   sheetTitle?: ReactNode;
   disabled?: boolean;

package/src/components/field-base.tsx

@@ -457,17 +457,6 @@ export interface PasswordRevealLabels {
 // Defined in ./ui-labels, which holds no component code (0.34, KS U8).
 export { DEFAULT_PASSWORD_REVEAL_LABELS };
 
-/** @deprecated 0.34 — `useKitLabels("passwordReveal", DEFAULT_PASSWORD_REVEAL_LABELS, labels)`,
- *  which the provider reaches too, or Input's own `passwordLabels`; removed in 0.35
- *  (refactor audit 2026-10, API-6a). A merge from before the provider, which no kit
- *  component calls. */
-export function resolvePasswordRevealLabels(
-  partial?: Partial<PasswordRevealLabels>,
-): PasswordRevealLabels {
-  if (!partial) return DEFAULT_PASSWORD_REVEAL_LABELS;
-  return { ...DEFAULT_PASSWORD_REVEAL_LABELS, ...partial };
-}
-
 /**
  * What the character counter of {@link Input} and {@link Textarea} (`showCount`) says.
  * The visible "12/80" is digits and a slash and is not translated; these are the words

package/src/components/field-parts.tsx

@@ -1,5 +1,5 @@
 import { createContext, isValidElement, useContext, useId } from "react";
-import type { ComponentPropsWithoutRef, ComponentPropsWithRef, ReactNode, Ref, RefCallback } from "react";
+import type { ComponentPropsWithoutRef, ComponentPropsWithRef, ReactNode } from "react";
 import { HelpCircle } from "lucide-react";
 import { cn } from "../lib/cn";
 import { hasContent } from "../lib/presence";
@@ -41,23 +41,9 @@ export function mergeDescribedBy(...ids: Array<string | false | null | undefined
   return list.length ? list.join(" ") : undefined;
 }
 
-/** Point a ref — a callback or an object — at `node`. `undefined` and `null` are no ref. */
-export function assignRef<T>(ref: Ref<T> | undefined, node: T | null): void {
-  if (typeof ref === "function") ref(node);
-  else if (ref) (ref as { current: T | null }).current = node;
-}
-
-/**
- * One callback ref feeding several — the caller's forwarded `ref` and a field's own
- * (DUP-11: AmountInput, FormActions, ScrollArea and SearchField each wrote this by hand).
- * Wrap it in `useCallback` (or `useMemo`) over the same refs where a new callback every
- * render would detach and re-attach the node.
- */
-export function mergeRefs<T>(...refs: Array<Ref<T> | undefined>): RefCallback<T> {
-  return (node) => {
-    for (const ref of refs) assignRef(ref, node);
-  };
-}
+// The ref plumbing lives in ../lib/refs since round 0.35 (Tooltip needs it, and this module
+// renders a Tooltip); the fields keep importing it from here.
+export { assignRef, mergeRefs } from "../lib/refs";
 
 /* ── the static label ─────────────────────────────────────────────────────── */
 
@@ -312,7 +298,7 @@ export function useFieldError(
   invalid: boolean | undefined,
   describedBy: string | undefined,
   /** The caller's own `aria-invalid`. A form library sets THIS (see `@eifi1/ui-kit/rhf`
-   *  `FormControl`), not our `invalid` prop — and a field that announces invalid should
+   *  `RhfField`), not our `invalid` prop — and a field that announces invalid should
    *  look it too. */
   ariaInvalid?: unknown,
 ): { isInvalid: boolean; describedBy: string | undefined; errorEl: ReactNode } {

package/src/components/field-strip.tsx

@@ -1,13 +1,7 @@
 import { useId } from "react";
-import type { ComponentPropsWithoutRef, ReactNode } from "react";
+import type { ComponentPropsWithRef, ReactNode } from "react";
 import { LabelStrip, useFieldMessages } from "./field-parts";
 
-/**
- * How far down the content starts, under the 11px label — see {@link FieldStripProps.pad}.
- * Since 0.34 both are the one 20px strip.
- */
-export type FieldStripPad = "clear" | "field";
-
 /** What a {@link FieldStrip} hands render-prop children. */
 export interface FieldStripIds {
   /** The label's id — for content that names ITSELF by the label (`aria-labelledby`)
@@ -19,7 +13,12 @@ export interface FieldStripIds {
   describedBy: string | undefined;
 }
 
-export interface FieldStripProps extends Omit<ComponentPropsWithoutRef<"div">, "children"> {
+/**
+ * A `div`'s props, `ref` included since 0.35 (round 0.35 R4, as Card and EmptyState took
+ * it in 0.34, API-2): the ref is the root — the group, or the plain box under
+ * `group={false}` — which a caller scrolls into view or measures.
+ */
+export interface FieldStripProps extends Omit<ComponentPropsWithRef<"div">, "children"> {
   /** The 11px static label, on the line a labelled field's label sits on. */
   label: ReactNode;
   /**
@@ -37,21 +36,6 @@ export interface FieldStripProps extends Omit<ComponentPropsWithoutRef<"div">, "
    * turns its map into a picture and drops its buttons, which no flag here could guess.
    */
   disabled?: boolean;
-  /**
-   * @deprecated 0.34 — drop it; removed in 0.35. Both values are the same 20px strip
-   * since 0.34, and the prop does nothing; it stays so a caller that passes it still
-   * compiles.
-   *
-   * It chose between `"clear"` (20px) and `"field"` (16px: the strip plus a 26px
-   * bordered control made a labelled Input's 42px). The label row — the label and its
-   * "?" — ends 18px down, so over a 16px strip it crossed the content's top border by
-   * 2px (keksdose dev#593; the arithmetic is on `LABEL_STRIP_PAD` in field-parts.tsx).
-   * For a row of 42px fields, make the content 22px tall: 20 + 22 = 42, the shape
-   * ToggleGroup's `labelPlacement="strip"` has since 0.34.
-   *
-   * A `className` still merges after the strip's padding.
-   */
-  pad?: FieldStripPad;
   /**
    * The wrapper is a `role="group"` named by the label (default), so a screen reader
    * entering the map or the first button hears "Location, group" — what the visible
@@ -104,8 +88,6 @@ export function FieldStrip({
   hint,
   error,
   disabled = false,
-  // Taken off so it never reaches the DOM; see `pad` (deprecated, one strip since 0.34).
-  pad: _pad,
   group = true,
   className,
   children,
@@ -118,6 +100,8 @@ export function FieldStrip({
   // every kit field reads them in.
   const groupDescribedBy = [rest["aria-describedby"], messages.describedBy].filter(Boolean).join(" ") || undefined;
   return (
+    // `rest` carries the caller's `ref` too (a plain prop in React 19): LabelStrip spreads
+    // its own rest onto the wrapper `<div>`, so the ref lands on the root.
     <LabelStrip
       {...rest}
       {...(group

package/src/components/field-sync.tsx

@@ -38,13 +38,6 @@ export interface FieldSyncLabels {
 // Defined in ./field-sync-labels, which holds no component code (0.34, KS U8).
 export { DEFAULT_FIELD_SYNC_LABELS };
 
-/** @deprecated 0.34 — `useKitLabels("fieldSync", DEFAULT_FIELD_SYNC_LABELS, labels)`, which
- *  the provider reaches too, or the field's own `labels`; removed in 0.35 (refactor audit
- *  2026-10, API-6a). A merge from before the provider, which no kit component calls. */
-export function resolveFieldSyncLabels(labels?: Partial<FieldSyncLabels>): FieldSyncLabels {
-  return labels ? { ...DEFAULT_FIELD_SYNC_LABELS, ...labels } : DEFAULT_FIELD_SYNC_LABELS;
-}
-
 export interface UseFieldSyncOptions<T> {
   /** What the database currently holds. Changing it re-seeds a CLEAN field. */
   value: T;

package/src/components/field.tsx

@@ -29,10 +29,10 @@
  *
  * Deliberately knows neither the wizard nor react-hook-form: `error` is a plain
  * value. Pass `wizard.fieldErrors.iban`, a step-local error, or
- * `fieldState.error?.message` from a `FormField` render — the markup is the same
- * whichever of them gates the step, so a step can move between them without its
- * fields changing. (Inside a react-hook-form form, `FormItem` + `FormLabel` from
- * `@eifi1/ui-kit/rhf` do the same job with the ids taken from the form.)
+ * `fieldState.error?.message` from a react-hook-form `Controller` — the markup is the
+ * same whichever of them gates the step, so a step can move between them without its
+ * fields changing. (Inside a react-hook-form form, `RhfField` from `@eifi1/ui-kit/rhf`
+ * does the same job with the ids taken from the form.)
  *
  * The error is NOT `role="alert"`, for the reason the kit's `error` prop gives (see
  * `useFieldError` in components/field-parts.tsx): it is read when focus reaches the control.

package/src/components/full-bleed-dialog.tsx

@@ -174,14 +174,15 @@ export function FullBleedDialog({
   // to whichever of them is topmost — one press dismissing the sheet AND the edit
   // behind it was Keksdose live #309 (*"Mouse Back does not only close the select but
   // also the whole edit or create dialog"*) on a different key.
-  useDismissLayer(open, requestClose);
+  const layer = useDismissLayer(open, requestClose);
   const handleKeyDown = (e: KeyboardEvent<HTMLDivElement>) => {
     // The caller's handler first (keksdose's transaction-search keeps its list keys on
     // the dialog); a `preventDefault()` IN THAT HANDLER claims Escape. Only there: a
     // descendant's does not count. A SearchField in the header prevents Escape to stop
     // Chromium clearing a type=search input, and in 0.8.0 that silently stopped Escape
-    // from closing the dialog (keksdose). The one rule `Modal` now shares.
-    runOwnKeyDown(e, onKeyDown);
+    // from closing the dialog (keksdose). The one rule `Modal` now shares — as is this
+    // one: the handler sees Escape only while this dialog is the layer on top (0.35).
+    runOwnKeyDown(e, onKeyDown, layer);
     takeEscape(e);
   };
 

package/src/components/hover-menu.tsx

@@ -20,12 +20,13 @@ export interface HoverMenuProps extends Omit<ComponentPropsWithoutRef<"div">, "c
   trigger: (state: { open: boolean; toggle: () => void; close: () => void }) => ReactNode;
   children: (close: () => void) => ReactNode;
   /**
-   * Which edge of the trigger the panel lines up with. `start`/`end` follow the
-   * reading direction (`end` is the right edge in LTR, the left in RTL); `left`/`right`
-   * are physical and deprecated ({@link PhysicalAlign}). Default `end` — the same
-   * right-aligned panel as before in LTR, mirrored in RTL.
+   * Which edge of the trigger the panel lines up with, by the reading direction: `end`
+   * is the right edge in LTR and the left in RTL. Default `end` — the same right-aligned
+   * panel as before in LTR, mirrored in RTL. The physical `left` / `right` went in 0.35
+   * (round 0.35 R1, refactor audit 2026-10, API-6e): `right` is `end` in a left-to-right
+   * page, `left` is `start`.
    */
-  align?: "start" | "end" | PhysicalAlign;
+  align?: "start" | "end";
   panelClassName?: string;
   /** Extra classes for the WRAPPER (the panel has {@link panelClassName}). */
   className?: string;
@@ -34,14 +35,6 @@ export interface HoverMenuProps extends Omit<ComponentPropsWithoutRef<"div">, "c
   ref?: Ref<HTMLDivElement>;
 }
 
-/**
- * @deprecated 0.34 — `"start"` / `"end"`, which follow the reading direction: `"right"`
- * is `"end"` in a left-to-right page, the default; removed in 0.35 (refactor audit
- * 2026-10, API-6e). The physical edges HoverMenu's `align` — and TopBarActionMenu's and
- * FeedbackMenu's, which hand it on — still take.
- */
-type PhysicalAlign = "left" | "right";
-
 // Hovering waits briefly before opening so sweeping the cursor across a row of
 // triggers doesn't flash menus; closing waits so the cursor can travel from
 // trigger to panel. Click/keyboard toggling is instant (no "opening" phase).
@@ -50,7 +43,7 @@ const CLOSE_DELAY_MS = 120;
 
 type Phase = "closed" | "opening" | "open" | "closing";
 
-const ALIGN_CLASS = { start: "start-0", end: "end-0", left: "left-0", right: "right-0" } as const;
+const ALIGN_CLASS = { start: "start-0", end: "end-0" } as const;
 
 /** Explicit menu-item roles a caller may already have written. */
 const ITEM_ROLES = '[role="menuitem"],[role="menuitemcheckbox"],[role="menuitemradio"]';
@@ -188,7 +181,7 @@ export function HoverMenu({
   // DUP-1). Focus goes back to the trigger only when it was inside the menu: a panel
   // opened by hover while the user is typing elsewhere must not yank the caret over
   // here on the way out.
-  useDismissLayer(open, () => {
+  const layer = useDismissLayer(open, () => {
     const hadFocus = wrapperRef.current?.contains(document.activeElement) ?? false;
     close();
     if (hadFocus) triggerEl()?.focus();
@@ -298,7 +291,10 @@ export function HoverMenu({
       onMouseEnter={handleMouseEnter}
       onMouseLeave={handleMouseLeave}
       onKeyDown={(e) => {
-        runOwnKeyDown(e, rest.onKeyDown);
+        // The caller's handler sees Escape only while this menu is the layer on top: a
+        // tooltip on one of its rows takes that press first (round 0.35 R2, the rule
+        // the dialogs got first). Every other key, and a closed menu's, as before.
+        runOwnKeyDown(e, rest.onKeyDown, layer);
         // Focus on the trigger or in the menu: the key stops here, so a panel around
         // the menu does not close with it.
         if (open) takeEscape(e);

package/src/components/inline-entity-combobox.tsx

@@ -83,7 +83,7 @@ export interface InlineEntityComboboxProps<V extends string | number, C extends
   emptyLabel?: string;
   closeLabel?: string;
   /** The phone sheet's heading (and, as a string, its accessible name) for a field
-   *  whose label is drawn by someone else — a form's `FormLabel`;
+   *  whose label is drawn by someone else — a bound field's label;
    *  `RhfInlineEntityCombobox` hands its label over here (0.24). Default: `label`.
    *  See {@link Combobox}'s `sheetTitle`. */
   sheetTitle?: ReactNode;

package/src/components/modal.tsx

@@ -1,4 +1,4 @@
-import { createContext, useEffect, useRef, useState } from "react";
+import { createContext, useEffect, useMemo, useRef, useState } from "react";
 import { createPortal } from "react-dom";
 import type {
   ComponentPropsWithoutRef,
@@ -6,8 +6,10 @@ import type {
   MouseEvent as ReactMouseEvent,
   PointerEvent as ReactPointerEvent,
   ReactNode,
+  Ref,
 } from "react";
 import { cn } from "../lib/cn";
+import { mergeRefs } from "./field-parts";
 import { useFocusTrap } from "../hooks/use-focus-trap";
 import { useBodyScrollLock } from "../hooks/use-body-scroll-lock";
 import { useOverlayHistory } from "../hooks/use-overlay-history";
@@ -228,6 +230,14 @@ export interface ModalProps extends Omit<ComponentPropsWithoutRef<"div">, "role"
    * `onClose` still runs, after the param is cleared. Requires a react-router Router.
    */
   urlParam?: DialogParam;
+  /**
+   * The PANEL — the `role="dialog"` element the rest of the props go on, not the
+   * backdrop around it (0.35, round 0.35 R4, the follow-up to API-2; as on
+   * `FullBleedDialog`). Merged with the panel's own ref, which the focus
+   * trap holds. Set while the panel is in the document: `null` while a dialog with
+   * `open={false}` is closed, and after a `urlParam` dialog's param is cleared.
+   */
+  ref?: Ref<HTMLDivElement>;
 }
 
 /**
@@ -286,12 +296,16 @@ function ModalPanel({
   role = "dialog",
   urlParam: _urlParam,
   ownHistoryEntry = true,
+  ref,
   ...rest
 }: ModalProps & {
   /** False when the URL already holds an entry for this dialog — see `urlParam`. */
   ownHistoryEntry?: boolean;
 }) {
   const panelRef = useRef<HTMLDivElement>(null);
+  // The caller's `ref` beside the trap's (round 0.35 R4): memoised, so the panel is not
+  // detached and re-attached on every render.
+  const setPanel = useMemo(() => mergeRefs(panelRef, ref), [ref]);
   const drag = useDragOffset(Boolean(draggable));
   // Without `open`, mounted means open — the constant `true` every hook below used to
   // be given. With it, `open` itself.
@@ -357,9 +371,11 @@ function ModalPanel({
   // One layer on the Escape stack while open (Wave 2, DUP-1): a list, a popover or a
   // tooltip opened inside takes the key before the dialog does, wherever focus is —
   // and the dialog gets it even when focus is not in the panel.
-  useDismissLayer(active, requestClose);
+  const layer = useDismissLayer(active, requestClose);
   const handleKeyDown = (e: KeyboardEvent<HTMLDivElement>) => {
-    runOwnKeyDown(e, onKeyDown);
+    // The caller's handler sees Escape only while this dialog is the layer on top: a
+    // tooltip or a list open over it takes that press first (0.35, KS's gear wizard).
+    runOwnKeyDown(e, onKeyDown, layer);
     // To whatever is on top — this dialog, unless something opened over it — and
     // stopped here. Tab containment lives in useFocusTrap, which listens on the panel.
     takeEscape(e);
@@ -399,7 +415,7 @@ function ModalPanel({
         // losing any of the three is silent, and the symptom (a dialog a screen reader
         // walks straight out of) shows up nowhere near the call site that caused it.
         {...rest}
-        ref={panelRef}
+        ref={setPanel}
         // Normalised at runtime too: an untyped caller's `role="presentation"` must not
         // take the dialog role away (props-passthrough pins that).
         role={role === "alertdialog" ? "alertdialog" : "dialog"}

package/src/components/multi-select.tsx

@@ -50,32 +50,21 @@ export interface MultiSelectProps<V extends string | number = string | number>
   options: MultiSelectOption<V>[];
   /** The chosen values — the select family's `value` (API-4). */
   value?: V[];
-  /** @deprecated 0.34 — use `value`; removed in 0.35 (refactor audit 2026-10, API-4). */
-  values?: V[];
   onChange: (next: V[]) => void;
-  /** @deprecated 0.34 — use `labels.all`; removed in 0.35 (API-4). Displayed when no
-   *  value is selected (i.e. "all"); wins over `placeholder`, as `labels.all` does. */
-  allLabel?: string;
   /** Singular/plural countable label, used when 1+ items are selected. Default:
    *  `labels.selectedCount`, else `multiSelect.selectedCount` from the provider — the
    *  bare count in English. */
   itemLabel?: (count: number) => string;
-  /** Shown when nothing is picked, unless `labels.all` (or `allLabel`) says otherwise —
-   *  it has always doubled as the "nothing picked" text. */
+  /** Shown when nothing is picked, unless `labels.all` says otherwise — it has always
+   *  doubled as the "nothing picked" text. */
   placeholder?: string;
   /** Embedded top-boundary label, matching the native Input/Select fields. */
   label?: ReactNode;
-  /** @deprecated 0.34 — use `labels.search`; removed in 0.35 (API-4). */
-  searchLabel?: string;
-  /** @deprecated 0.34 — use `labels.selectAll`; removed in 0.35 (API-4). */
-  selectAllLabel?: string;
-  /** @deprecated 0.34 — use `labels.clear`; removed in 0.35 (API-4). */
-  clearLabel?: string;
   /**
    * Per-instance overrides of the provider's `multiSelect` namespace, over English — the
-   * kit's `labels` shape, where this took four string props (API-4). `all` is the trigger
-   * when nothing is picked: `labels.all`, then `allLabel`, then `placeholder`, then the
-   * provider's.
+   * kit's `labels` shape, where this took four string props until 0.35 (API-4: `allLabel`,
+   * `searchLabel`, `selectAllLabel`, `clearLabel`). `all` is the trigger when nothing is
+   * picked: `labels.all`, then `placeholder`, then the provider's.
    */
   labels?: LabelOverride<MultiSelectLabels>;
   /**
@@ -141,15 +130,10 @@ export function MultiSelect<V extends string | number = string | number>(props:
   const {
     options,
     value: valueProp,
-    values,
     onChange,
-    allLabel,
     itemLabel,
     placeholder,
     label,
-    searchLabel,
-    selectAllLabel,
-    clearLabel,
     labels: labelsProp,
     className,
     panelClassName,
@@ -172,7 +156,7 @@ export function MultiSelect<V extends string | number = string | number>(props:
     "aria-required": ariaRequired,
     ...rest
   } = props;
-  const value = useMemo<V[]>(() => valueProp ?? values ?? [], [valueProp, values]);
+  const value = useMemo<V[]>(() => valueProp ?? [], [valueProp]);
   // The rows as the family's options — the hint is the sublabel, searched like the label.
   const comboOptions = useMemo(
     () => options.map((o): ComboOption<V> => ({ value: o.value, label: o.label, sublabel: o.hint, disabled: o.disabled })),
@@ -190,14 +174,13 @@ export function MultiSelect<V extends string | number = string | number>(props:
     },
     [ref, triggerRef],
   );
-  // `labels` > the deprecated string props > the provider's `multiSelect` > English. `all`
-  // is resolved apart below: between the instance's and the provider's sits `placeholder`,
-  // which has always doubled as the "nothing picked" text, and a caller who set it must
-  // keep seeing it.
+  // `labels` > the provider's `multiSelect` > English. `all` is resolved apart below:
+  // between the instance's and the provider's sits `placeholder`, which has always
+  // doubled as the "nothing picked" text, and a caller who set it must keep seeing it.
   const text = useKitLabels("multiSelect", DEFAULT_MULTI_SELECT_LABELS, {
-    search: labelsProp?.search ?? searchLabel,
-    selectAll: labelsProp?.selectAll ?? selectAllLabel,
-    clear: labelsProp?.clear ?? clearLabel,
+    search: labelsProp?.search,
+    selectAll: labelsProp?.selectAll,
+    clear: labelsProp?.clear,
     selectedCount: labelsProp?.selectedCount ?? itemLabel,
   });
   const common = useKitLabels("common", DEFAULT_COMMON_LABELS);
@@ -226,7 +209,7 @@ export function MultiSelect<V extends string | number = string | number>(props:
   const allChecked = options.length > 0 && options.every((o) => valueSet.has(o.value));
   const selectedSummary =
     value.length === 0 || allChecked
-      ? (labelsProp?.all ?? allLabel ?? placeholder ?? text.all)
+      ? (labelsProp?.all ?? placeholder ?? text.all)
       : text.selectedCount(value.length);
 
   const toggle = (o: ComboOption<V>) => {

package/src/components/number-input.tsx

@@ -9,7 +9,8 @@ import {
   FLOATING_INPUT_CLASS,
   FloatingField,
 } from "./field-base";
-import { CURRENCIES } from "./currency-select";
+// The data alone (0.35): not the picker, which this field does not render.
+import { CURRENCIES } from "../currencies";
 import { FieldCaption, LockedReason, mergeRefs, type DisabledReasonDisplay } from "./field-parts";
 import { useEndWidth, useNumericField } from "./numeric-field";
 import type { CommitScope } from "./write-lock";
@@ -35,9 +36,6 @@ export interface NumberInputProps {
   /** Names the field when it has no visible `label` (a table cell, a phone's display
    *  shape). */
   "aria-label"?: string;
-  /** @deprecated 0.34 — use `aria-label`; removed in 0.35 (refactor audit 2026-10, API-1).
-   *  Names the field only when `aria-label` is absent. */
-  ariaLabel?: string;
   /** Names for the calculator this field renders — its trigger, and the controls
    *  inside the popover — and for the numpad sheet it opens on a phone. Overrides
    *  for THIS field only: both resolve the `calculator` namespace of
@@ -319,8 +317,7 @@ export function NumberInput(props: NumberInputProps) {
     onChange,
     onCommit,
     label,
-    "aria-label": ariaLabelAttr,
-    ariaLabel: ariaLabelProp,
+    "aria-label": ariaLabel,
     labels,
     placeholder,
     autoFocus,
@@ -334,8 +331,6 @@ export function NumberInput(props: NumberInputProps) {
     max,
     disabledReasonDisplay,
   } = props;
-  // The DOM spelling wins; `ariaLabel` is the fallback for call sites not moved yet.
-  const ariaLabel = ariaLabelAttr ?? ariaLabelProp;
   const generatedId = useId();
   const fieldId = id ?? generatedId;
   // The engine AmountInput shares (DUP-10): the lock (focusable, `readOnly`, nothing

package/src/components/popover.tsx

@@ -159,7 +159,7 @@ export function Popover({
   // A layer on the Escape stack while open (Wave 2, DUP-1): a list opened inside closes
   // first, and the dialog this popover sits in only after it — the calculator on an
   // amount field in a Modal is exactly that.
-  useDismissLayer(open, close);
+  const layer = useDismissLayer(open, close);
 
   useFocusTrap(panelRef, {
     active: open && pos !== null,
@@ -178,8 +178,10 @@ export function Popover({
   const handleKeyDown = (e: KeyboardEvent<HTMLDivElement>) => {
     // A caller's own handler first (0.32.2: RowActions stops Enter / Space at the panel);
     // it used to be dropped, overwritten by this one. A `preventDefault()` on Escape
-    // there keeps the popover open — the owner's claim, as on the dialogs.
-    runOwnKeyDown(e, onKeyDownProp);
+    // there keeps the popover open — the owner's claim, as on the dialogs. And as there,
+    // the handler sees Escape only while this popover is the layer on top: a tooltip or a
+    // menu open over it takes that press first (round 0.35 R2, the dialogs' rule).
+    runOwnKeyDown(e, onKeyDownProp, layer);
     // Focus is in here, the normal case: the key is handed to the top layer and STOPPED,
     // so it does not travel on up the React tree to a dialog around the popover.
     takeEscape(e);

package/src/components/series-chart.tsx

@@ -25,7 +25,7 @@
 // "area"` (and `stack`), and the abscissa may be a row of PERIODS (`x.type:
 // "category"`) or real dates (`x.type: "time"`) instead of a number the app had to
 // invent. What each of those does to the zoom is decided in one place,
-// `defaultZoomAxes` in `chart-zoom.tsx`.
+// `defaultZoomAxes` in `chart-zoom-core.tsx`.
 //
 // **An axis budget (0.15.1).** Every visible axis reserves its band, and four of them
 // leave a phone nothing to plot. A chart draws at most `maxVisibleAxes`, and — on its

package/src/components/server-wake.tsx

@@ -69,12 +69,6 @@ export interface ServerWakeNoticeProps {
    *  label says "the app". */
   appName?: string;
   labels?: LabelOverride<ServerWakeLabels>;
-  /**
-   * @deprecated 0.34 — drop it; removed in 0.35. The notice sits at the TOP of the
-   * screen since 0.34, so there is no bottom nav to clear and this does nothing. It was
-   * the height kept clear at the bottom (AppShell's `--app-nav-h`).
-   */
-  navOffset?: string | number;
   /** Extra classes on the fixed anchor — a different width (`max-w-*`), or another
    *  `top-*` for an app that wants it under its top bar rather than over it. Merged, so
    *  a class given here replaces the kit's of the same kind. */