@lotics/ui 27.11.0 → 27.13.0

package/docs/catalog.md

@@ -382,7 +382,10 @@ source (`src/<module>.tsx`/`.ts`) is the API reference.
 - **`control_surface`** — `CONTROL_HEIGHT` (40), `CONTROL_RADIUS` (10), `CONTROL_TEXT_INSET`
   (9 — how far a control insets its OWN text: 1px border + 8px padding; anything that must line
   up with a control's WORDS rather than its box carries it, and `TASK_TEXT_INSET` IS it),
-  `FOCUS_RING`, `HOVER_BORDER`, `CONTROL_TRANSITION`, `chipSurfaceStyle` — the shared
+  `FOCUS_RING` (a 2px OUTSET ring, so a container that CLIPS — any `ScrollView` — has to
+  keep padding on an edge a focusable child sits against, or the ring shears off on the
+  one interaction it signals; the padding still comes off the 8-grid, the ring is only
+  the floor), `HOVER_BORDER`, `CONTROL_TRANSITION`, `chipSurfaceStyle` — the shared
   control-surface tokens.
 - **`fonts.css`** — the Inter sheet (400/500/600, served by absolute URL so it resolves on
   every origin an app runs from); the app entry imports it ONCE or every `Text` falls back
@@ -752,7 +755,10 @@ source (`src/<module>.tsx`/`.ts`) is the API reference.
   just text. **`InlineSelect` is single OR multi** — pass `multi` for a tag SET (`value: T[]`,
   commits the new set on popover-CLOSE; selected tags render as badges via `renderSelected`),
   mirroring `Select`'s `multi` axis; there is NO separate tag component. Both modes take
-  `allowCustom` (a create-a-tag/option row) + `searchable`, plus **`autoFocus`** to open the list
+  `allowCustom` (a create-a-tag/option row) + `searchable` + **`customOptionPlacement`** (default
+  `"bottom"`, right for a tag field; pass `"top"` for a find-or-create REFERENCE picker over a long
+  registry, so the create row stays visible while the keyboard highlight stays on the first MATCH —
+  Enter on a partial query then attaches instead of duplicating), plus **`autoFocus`** to open the list
   on mount — for the picker a `ReferenceField`'s `Change` just dropped the reader into, so the
   correction stays one gesture; leave it off for a field that is merely empty, since stealing the
   list open on load is a different act. **`InlineMemberSelect` takes `avatarOnly`**
@@ -1178,6 +1184,10 @@ source (`src/<module>.tsx`/`.ts`) is the API reference.
   stack (a Drawer drilling into a LINKED record swaps its header to a BACK `IconButton`
   while `canGoBack`). Key the router by record id so stepping between records resets the
   stack. Worked example: [`tpl_item_list`](../examples/tpl_item_list.tsx) drawer.
+  **`useScreenActive()` says whether the surrounding `Screen` is the one on top** —
+  because "stays mounted" means its effects keep running, so anything a screen claims
+  GLOBALLY (a keyboard shortcut) must stand down while it is buried, or the covered
+  screen answers input aimed at the one in front of it. `true` outside any `Screen`.
 - **`route_matching`** — pure `:param` route-pattern utilities — `routeMatches` /
   `parseRouteParams` / `findBestPattern` (exact beats parameterized) / `shouldRouteMatch`;
   the matching core under `ScreenRouter`/`Dialog`.

package/docs/composition.md

@@ -493,8 +493,8 @@ All view controls are 40px tall (`CONTROL_HEIGHT`), `sm` labels, in ONE wrapping
   "success"/green button. Decision UIs put positive/negative color on the STATUS (dot) and verdict
   (colored `Text`), not the buttons.
 - **Create buttons carry NO `+` icon** — "Add fee", not "+ Add fee". A create is `primary` and
-  sits BELOW the list it extends, never in the section heading — see the verb-placement law for
-  why, and for the one-verb-one-weight rule that keeps it primary in the `EmptyState` too. (The
+  rides its section's HEADING row at the right edge — see § The add-placement law for why, and
+  for the one-verb-one-weight rule that keeps it primary in the `EmptyState` too. (The
   icon-only `+` `IconButton` — a composer's attach — is a different thing and keeps its glyph.)
 
 ## The action-gating law — disabled + the reason as a co-located Callout
@@ -594,15 +594,13 @@ gate's SCOPE, once** — never prose beside the button, never revealed only on p
   |---|---|
   | a VALUE (copy it, open what it points at) | ON the value — `InlineButton` in the editor's `actions` |
   | a ROW (remove it, move it) | ON the row — an `ActionMenu`, or the row's own controls |
-  | the LIST (one more of them) | BELOW the list, left-aligned, `primary` |
+  | the LIST (one more of them) | its section's HEADING row, right edge, `primary` — see [the add-placement law](#the-add-placement-law--a-sections-add-rides-its-heading-row-right-edge) |
   | the RECORD (issue, print, hand off) | its own action row at the section's END |
   | the record's EXISTENCE | the `DangerZone`, last on the page |
 
-  The heading row is therefore identity + meta + view controls, and holds no content verb. An
-  **Add in the heading sits above the thing it extends**, at a different altitude from the rows
-  it affects, competing with the title for the one line that names the section — while the row it
-  creates appears at the BOTTOM, nowhere near the button that made it. Put it under the last row,
-  on the list's own left edge, and the button is where its result will be.
+  The ADD is the one verb this law does NOT place next to its effect, and the add-placement law
+  says why: a position that never moves beats a position that is adjacent, because "below the
+  last row" is a different place on every list and no place at all on an empty one.
   **An add is `primary`, in the `EmptyState` too.** It is the act its section offers, so it
   carries that section's weight; a lone `secondary` button reads as though the real action were
   somewhere else. The rule that matters is that ONE VERB KEEPS ONE WEIGHT — the same add must
@@ -685,7 +683,13 @@ gate's SCOPE, once** — never prose beside the button, never revealed only on p
   line** that carries the type + identifying fact as TEXT (`type, code, city`) — COMMA-joined, never
   a middot (see Microcopy), and free to wrap the row taller. A type/attribute is **NOT a status, so it is text, never a `Badge`** (see
   Badge discipline below). (The kit suppresses `renderOptionContent` on the `allowCustom` "Create …" row so it keeps its plain + look.)
-  Plus `allowCustom` + `customOptionPlacement:"top"` + `customOptionLabel={q => 'Create "…"'}`. In
+  Plus `allowCustom` + `customOptionPlacement:"top"` + `customOptionLabel={q => 'Create "…"'}` —
+  the same three on `InlineSelect` where the reference sits in an inline-editor grid rather than a
+  form. **The create row names the ENTITY, not the role** (`Create new customer "…"` on a carrier
+  row, when one registry serves all the party roles): a per-role noun claims a registry per role,
+  which is a data model the screen does not have. The role is named by the PLACEHOLDER, and derive
+  that placeholder from the same noun the row is labelled by — passing the two separately is how a
+  row ends up promising "Find or create" over a picker that can only find. In
   `onValueChange`, an existing pick attaches; the custom row opens a create **`Dialog` prefilled with
   the typed query** (mint the record + link it) — so a party absent from the registry is created
   WITHOUT leaving the record. `customOptionPlacement:"top"` keeps the create row visible while the

package/docs/templates.md

@@ -92,11 +92,11 @@ Laws for any screen where a record's data is edited and a primary action produce
 7. **Header = identity + provenance.** Id, the key identifier, created-at. No metrics or badges
    duplicating data a section already owns.
 8. **Action placement — a verb goes where its effect lands.** Value verbs on the value
-   (`InlineButton`), row verbs on the row, an ADD below the list it extends (primary, left —
-   where the new row will appear, and primary in the `EmptyState` too: one verb, one weight),
+   (`InlineButton`), row verbs on the row, an ADD on its section's HEADING row at the right edge
+   (primary — the one spot that does not move with the row count, and primary in the
+   `EmptyState` too: one verb, one weight),
    a committing act in its own row at the section's end,
-   deletion in the `DangerZone`. Section headings carry identity and view controls only; an Add
-   in the heading sits above what it extends and competes with the title. A committing act rides
+   deletion in the `DangerZone`. A committing act rides
    an empty-label `DetailRow` so it lands on the CONTROL column — never right-floated, which
    aligns to nothing (only overlay footers right-align).
 9. **Destructive placement.** Solid `danger`, bottom-left after the entity's fields, ONE

package/examples/tpl_record.tsx

@@ -779,14 +779,53 @@ function RouteStops({ stops, onChange }: { stops: Stop[]; onChange: (next: Stop[
   );
 }
 
+/** The reference picker's option row, for EVERY picker over the customer registry
+ *  — the Customer row and the three party rows. A glyph tile beside the name over
+ *  a COMMA-joined muted metadata line (the identifying facts as TEXT: a type or
+ *  attribute is not a status, so it is never a `Badge`).
+ *
+ *  It is shared rather than written per row precisely because four pickers over
+ *  ONE registry drifting into four looks is how this surface decayed the first
+ *  time: three of them rendered a wall of bare names while the fourth carried the
+ *  city and tax ID a reader needs to tell two similarly-named companies apart. */
+function customerOptionRow(o: PickerOption<string, Customer>) {
+  return (
+    <View style={{ flexDirection: "row", alignItems: "center", gap: 10 }}>
+      <View style={{ width: 28, height: 28, borderRadius: 7, backgroundColor: colors.zinc[100], alignItems: "center", justifyContent: "center" }}>
+        <Icon name="building-2" size={14} color={colors.zinc[600]} />
+      </View>
+      <View style={{ flex: 1, minWidth: 0 }}>
+        <Text size="sm" numberOfLines={1}>{o.label}</Text>
+        {o.data ? <Text size="xs" color="muted">{[o.data.city, o.data.taxId ? `Tax ID ${o.data.taxId}` : "No tax ID"].filter(Boolean).join(", ")}</Text> : null}
+      </View>
+    </View>
+  );
+}
+
+/** The create row names the ENTITY, never the role the field fills it for: one
+ *  registry holds all four, so "Create new customer" on the carrier row says the
+ *  true thing — a customer record, attached here as the carrier. A per-role noun
+ *  would imply four registries and four kinds of record, which is the data model
+ *  the screen deliberately does not have. The ROLE is named by the field's own
+ *  placeholder, where it belongs. */
+const createCustomerLabel = (query: string) => `Create new customer “${query}”`;
+const NO_CUSTOMER_MATCH = "No customer matches — type a name to create one";
+
+/** Which party row a pick or a create is destined for. */
+type PartyTarget = "customer" | "shipTo" | "notify" | "carrier";
+
 /** A party ROW — a reference when one is attached, the find-or-create picker when
  *  not. The two states share the row so the field never moves; the picker is the
  *  field's EMPTY state, not a different kind of surface. */
-function PartyRow({ role, rec, options, placeholder, onPick, onOpen, onUnset, onSaveFacts }: {
+function PartyRow({ role, noun, rec, options, onPick, onOpen, onUnset, onSaveFacts }: {
   role: string;
+  /** The ROLE this field fills, for its placeholder — "consignee", "carrier".
+   *  The placeholder is derived from it rather than passed alongside it: the two
+   *  were separate props once, and the row ended up promising "Find or create"
+   *  over a picker that could only find. */
+  noun: string;
   rec: Customer | null;
   options: PickerOption<string, Customer>[];
-  placeholder: string;
   onPick: (opt: PickerOption<string, Customer>) => void;
   onOpen: () => void;
   onUnset: () => void;
@@ -825,10 +864,14 @@ function PartyRow({ role, rec, options, placeholder, onPick, onOpen, onUnset, on
           options={options}
           autoFocus={changing}
           onValueChange={(o) => { setChanging(false); onPick(o); }}
+          renderOptionContent={customerOptionRow}
           reflectSelection={false}
+          allowCustom
+          customOptionPlacement="top"
+          customOptionLabel={createCustomerLabel}
         >
-          <ComboboxInput icon="search" placeholder={placeholder} accessibilityLabel={role} />
-          <ComboboxContent emptyText="No match" />
+          <ComboboxInput icon="search" placeholder={`Find or create a ${noun}`} accessibilityLabel={role} />
+          <ComboboxContent emptyText={NO_CUSTOMER_MATCH} />
         </Combobox>
       )}
     </DetailRow>
@@ -987,7 +1030,13 @@ export function TplRecord({ chrome = "page", code = "RC-2026-0418" }: { chrome?:
   // ── customer section — TWO states: attached (read-only card, Remove
   // detaches) or empty (the find-or-create search). The "create" branch opens
   // a focused Dialog; non-null draft = the dialog is open.
-  const [custDraft, setCustDraft] = useState<{ name: string; taxId: string; contact: string; city: string } | null>(null);
+  //
+  // `target` is the row that opened it. All four party rows attach a record from
+  // the SAME registry, so they share one dialog rather than each carrying a copy
+  // — and the draft names its destination as DATA instead of the dialog holding a
+  // callback, so what is in flight stays inspectable and the commit stays one
+  // function.
+  const [custDraft, setCustDraft] = useState<{ target: PartyTarget; name: string; taxId: string; contact: string; city: string } | null>(null);
   // The Fetch button's in-flight state (the registry lookup).
   const [fetching, setFetching] = useState(false);
 
@@ -1303,14 +1352,24 @@ export function TplRecord({ chrome = "page", code = "RC-2026-0418" }: { chrome?:
     data: c,
   }));
 
-  // Find-or-create resolution: an existing pick attaches; the custom row opens
-  // the create Dialog, prefilled with the query.
-  const onPickCustomer = (opt: PickerOption<string, Customer>) => {
+  // Where each party row's attach lands. One map, so a row added later cannot
+  // acquire a create path and quietly forget to wire its attach.
+  const attachParty: Record<PartyTarget, (id: string | null) => void> = {
+    customer: setCustomerId,
+    shipTo: setShipTo,
+    notify: setNotify,
+    carrier: setCarrier,
+  };
+
+  // Find-or-create resolution, shared by all four party rows: an existing pick
+  // attaches; the custom row opens the create Dialog, prefilled with the query
+  // and carrying the row that asked for it.
+  const onPickParty = (target: PartyTarget) => (opt: PickerOption<string, Customer>) => {
     if (customers.some((c) => c.id === opt.value)) {
-      setCustomerId(opt.value);
+      attachParty[target](opt.value);
       return;
     }
-    setCustDraft({ name: opt.value, taxId: "", contact: "", city: "" });
+    setCustDraft({ target, name: opt.value, taxId: "", contact: "", city: "" });
   };
 
   const taxIdError =
@@ -1331,7 +1390,7 @@ export function TplRecord({ chrome = "page", code = "RC-2026-0418" }: { chrome?:
       since: "",
     };
     setCustomers((prev) => [...prev, c]);
-    setCustomerId(c.id);
+    attachParty[custDraft.target](c.id);
     setCustDraft(null);
   };
 
@@ -1401,10 +1460,6 @@ export function TplRecord({ chrome = "page", code = "RC-2026-0418" }: { chrome?:
     Alert.alert("Receipt", `Printing receipt for ${formatMoney(grandTotal)}.`, [{ text: "OK" }]);
   };
 
-  // Where the record SITS — the one index the pipeline reads off, and the act
-  // that leaves that desk. A closed record is past the last desk, so no stage
-  // is current and no gate is offered.
-  const deskIndex = stage === "closed" ? DESKS.length : DESKS.findIndex((x) => x.key === stage);
   // `handoff` separates the two acts that LOOK alike, as a DISCRIMINATED union
   // so the difference is in the type and not just a runtime branch: handing off
   // has a receiving DESK (it asks whom, then stamps that desk), closing has no
@@ -1871,25 +1926,15 @@ export function TplRecord({ chrome = "page", code = "RC-2026-0418" }: { chrome?:
                          drops you into is already focused and open, and the
                          correction stays one gesture. */
                       autoFocus={changingCustomer}
-                      onValueChange={(o) => { setChangingCustomer(false); onPickCustomer(o); }}
-                      renderOptionContent={(o) => (
-                        <View style={{ flexDirection: "row", alignItems: "center", gap: 10 }}>
-                          <View style={{ width: 28, height: 28, borderRadius: 7, backgroundColor: colors.zinc[100], alignItems: "center", justifyContent: "center" }}>
-                            <Icon name="building-2" size={14} color={colors.zinc[600]} />
-                          </View>
-                          <View style={{ flex: 1, minWidth: 0 }}>
-                            <Text size="sm" numberOfLines={1}>{o.label}</Text>
-                            {o.data ? <Text size="xs" color="muted">{[o.data.city, o.data.taxId ? `Tax ID ${o.data.taxId}` : "No tax ID"].filter(Boolean).join(", ")}</Text> : null}
-                          </View>
-                        </View>
-                      )}
+                      onValueChange={(o) => { setChangingCustomer(false); onPickParty("customer")(o); }}
+                      renderOptionContent={customerOptionRow}
                       reflectSelection={false}
                       allowCustom
                       customOptionPlacement="top"
-                      customOptionLabel={(q) => `Create new customer “${q}”`}
+                      customOptionLabel={createCustomerLabel}
                     >
                       <ComboboxInput icon="search" placeholder="Search customers by name…" accessibilityLabel="Attach customer" />
-                      <ComboboxContent emptyText="No customer matches — type a name to create one" />
+                      <ComboboxContent emptyText={NO_CUSTOMER_MATCH} />
                     </Combobox>
                   )}
                 </DetailRow>
@@ -2208,14 +2253,12 @@ export function TplRecord({ chrome = "page", code = "RC-2026-0418" }: { chrome?:
               <SubsectionHeading><SubsectionHeadingTitle>Consignment &amp; terms</SubsectionHeadingTitle></SubsectionHeading>
               <DetailTable labelWidth={150} minHeight={40}>
                 <PartyRow
-                  role="Ship to" rec={shipToRec} options={customerOptions}
-                  placeholder="Find or create a consignee"
-                  onPick={(o) => setShipTo(o.value)} onOpen={() => {}} onUnset={() => setShipTo(null)} onSaveFacts={saveCustomerFacts}
+                  role="Ship to" noun="consignee" rec={shipToRec} options={customerOptions}
+                  onPick={onPickParty("shipTo")} onOpen={() => {}} onUnset={() => setShipTo(null)} onSaveFacts={saveCustomerFacts}
                 />
                 <PartyRow
-                  role="Notify" rec={notifyRec} options={customerOptions}
-                  placeholder="Find or create a notify party"
-                  onPick={(o) => setNotify(o.value)} onOpen={() => {}} onUnset={() => setNotify(null)} onSaveFacts={saveCustomerFacts}
+                  role="Notify" noun="notify party" rec={notifyRec} options={customerOptions}
+                  onPick={onPickParty("notify")} onOpen={() => {}} onUnset={() => setNotify(null)} onSaveFacts={saveCustomerFacts}
                 />
                 {/* A CHOICE IS ONE ROW, like every other field.
                     `RadioPicker` renders three full-width bordered choices with
@@ -2314,9 +2357,8 @@ export function TplRecord({ chrome = "page", code = "RC-2026-0418" }: { chrome?:
               ) : null}
               <DetailTable labelWidth={150} minHeight={40}>
                 <PartyRow
-                  role="Carrier" rec={carrierRec} options={customerOptions}
-                  placeholder="Find or create a carrier"
-                  onPick={(o) => setCarrier(o.value)} onOpen={() => {}} onUnset={() => setCarrier(null)} onSaveFacts={saveCustomerFacts}
+                  role="Carrier" noun="carrier" rec={carrierRec} options={customerOptions}
+                  onPick={onPickParty("carrier")} onOpen={() => {}} onUnset={() => setCarrier(null)} onSaveFacts={saveCustomerFacts}
                 />
                 <DetailRow label="Booking no.">
                   <InlineTextInput value={booking} onSave={persist(setBooking)} placeholder="Add booking number…" accessibilityLabel="Booking number" />

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lotics/ui",
-  "version": "27.11.0",
+  "version": "27.13.0",
   "type": "module",
   "exports": {
     "./vite": {

package/src/control_surface.ts

@@ -23,6 +23,13 @@ export const MIN_CONTROL_WIDTH = 160;
  *  (avatars, dots, switches, sliders, progress, icon buttons) stay full. */
 export const CONTROL_RADIUS = 10;
 
+/** How far {@link FOCUS_RING} extends BEYOND the control's border box. Module-local
+ *  on purpose: it is a FLOOR for anyone who clips (a container reserving less than
+ *  this on an edge a focusable child sits against shears that child's ring), never a
+ *  spacing value — padding comes off the 8-grid in `spacing.ts`, which clears this
+ *  several times over without coupling a layout number to a decoration one. */
+const FOCUS_RING_WIDTH = 2;
+
 /** THE focus ring — a 2px zinc-900 box-shadow flush against the box (offset 0),
  *  layout-neutral (never reflows). The kit no longer ships a global `:focus-visible`
  *  CSS rule, so every interactive control paints THIS inline when keyboard-focused
@@ -30,7 +37,7 @@ export const CONTROL_RADIUS = 10;
  *  trigger (Picker / Combobox / InlineSelect / InlineDatePicker) wears it on its open
  *  state so an open trigger reads identically to a keyboard-focused one — one token,
  *  one look. Apps building their own controls reuse it. */
-export const FOCUS_RING = `0 0 0 2px ${colors.zinc[900]}`;
+export const FOCUS_RING = `0 0 0 ${FOCUS_RING_WIDTH}px ${colors.zinc[900]}`;
 
 /**
  * How far a control surface insets its OWN text: 1px of border (transparent on an

package/src/dialog.tsx

@@ -313,6 +313,16 @@ const styles = StyleSheet.create({
     minHeight: 56,
   },
   scrollAreaContent: {
+    // A ScrollView clips, so the FIRST child sat flush against the boundary and lost
+    // the outer half of its focus ring — an input at the top of a dialog showed a
+    // sheared ring on the one interaction the ring exists to signal. 8 clears that
+    // several times over, but the ring is only the FLOOR here, not the reason: this
+    // is separation from the header, so it comes off the 8-grid like every other gap.
+    // `DialogHeader` already pays 8 below itself, making the visible gap a clean 16.
+    //
+    // Asymmetric with the bottom on purpose — 24 there is scroll RUNOUT, so the last
+    // row isn't jammed against the edge at the end of a scroll. Different job.
+    paddingTop: 8,
     paddingBottom: 24,
   },
   footer: {

package/src/inline_select.tsx

@@ -49,6 +49,12 @@ interface InlineSelectBaseProps<T extends string, D = unknown> {
   allowCustom?: boolean;
   /** Label for the create row (default: `Add "<query>"`). */
   customOptionLabel?: (query: string) => string | null;
+  /** Where the create row sits — default "bottom", which is right for a tag field
+   *  whose list is short and whose create row is the ordinary outcome. Pass "top"
+   *  for a find-or-create REFERENCE picker over a long registry: the create row
+   *  stays visible without scrolling while the keyboard highlight stays on the
+   *  first MATCH, so Enter on a partial query attaches rather than duplicating. */
+  customOptionPlacement?: "top" | "bottom";
 }
 
 /**
@@ -129,7 +135,7 @@ function InlineSelectShell(props: {
 }
 
 export function InlineSelect<T extends string, D = unknown>(props: InlineSelectProps<T, D>) {
-  const { options, renderOptionContent, renderSelected, placeholder, disabled, accessibilityLabel, searchable = false, allowCustom = false, customOptionLabel, variant, actions, autoFocus = false } = props;
+  const { options, renderOptionContent, renderSelected, placeholder, disabled, accessibilityLabel, searchable = false, allowCustom = false, customOptionLabel, customOptionPlacement, variant, actions, autoFocus = false } = props;
   const labels = useLoticsLocale().inline;
   const [open, setOpen] = useState(autoFocus);
   const [saving, setSaving] = useState(false);
@@ -192,6 +198,7 @@ export function InlineSelect<T extends string, D = unknown>(props: InlineSelectP
           onRequestClose={() => onOpenChange(false)}
           allowCustom={allowCustom}
           customOptionLabel={customOptionLabel}
+          customOptionPlacement={customOptionPlacement}
           onCustomCommit={(raw) => {
             const created = raw.trim() as T;
             if (created && !draft.includes(created)) setDraft([...draft, created]);
@@ -238,6 +245,7 @@ export function InlineSelect<T extends string, D = unknown>(props: InlineSelectP
         onRequestClose={() => setOpen(false)}
         allowCustom={allowCustom}
         customOptionLabel={customOptionLabel}
+        customOptionPlacement={customOptionPlacement}
         onCustomCommit={(raw) => {
           const created = raw.trim() as T;
           if (created) pick(created);

package/src/screen_router.tsx

@@ -159,6 +159,24 @@ export function useNavigationStack(
 // Screen
 // ============================================================================
 
+/**
+ * Whether the surrounding {@link Screen} is the one on top.
+ *
+ * A screen stacked BEHIND another stays mounted (`display: none`) so its scroll
+ * position survives, which means its effects keep running — including any
+ * keyboard shortcut it registered. Anything that claims a global key must read
+ * this and stand down while hidden, or the buried screen answers a keystroke the
+ * user aimed at the screen in front of it.
+ *
+ * Defaults to `true`, so a subtree outside any `Screen` behaves as if visible.
+ */
+const ScreenActiveContext = createContext(true);
+
+/** @see ScreenActiveContext */
+export function useScreenActive(): boolean {
+  return useContext(ScreenActiveContext);
+}
+
 export interface ScreenProps {
   /** Route pattern to match. Use empty string "" for the default/initial screen. */
   route: string;
@@ -208,9 +226,11 @@ export function Screen(props: ScreenProps) {
   const params = parseRouteParams(route, matchingStackPath);
 
   return (
-    <View style={isActive ? screenStyles.active : screenStyles.hidden}>
-      {typeof children === "function" ? children(params) : children}
-    </View>
+    <ScreenActiveContext.Provider value={isActive}>
+      <View style={isActive ? screenStyles.active : screenStyles.hidden}>
+        {typeof children === "function" ? children(params) : children}
+      </View>
+    </ScreenActiveContext.Provider>
   );
 }