@appinternalleads/ui 0.2.0

package/dist/esm/tokens/tokens.d.ts

@@ -0,0 +1,884 @@
+import { type BackgroundImageValue } from 'react-native';
+/**
+ * Design tokens — **WARM PAPER**, ported from the design project's
+ * `tokens/colors.css` and `tokens/materials.css` (August 2026).
+ *
+ * This replaced a pine-green-on-glass system. If you are reading a comment that mentions
+ * substrates, specular rims, blur, five user accents or a dark scope, it predates the
+ * shift and is wrong.
+ *
+ * **The one rule: the page is paper and objects sit ON it.** Depth is a soft drop shadow
+ * plus a hairline — never a fill that differs from the page, never transparency, never
+ * blur. Three consequences, and they are the whole material system:
+ *
+ * 1. **All surfaces are the same white.** A card tinted away from the page reads as a
+ *    highlight, and once everything is highlighted nothing is. Separation is shadow.
+ * 2. **A field is a hole, not an object.** Inputs never lift. Focus darkens the hairline;
+ *    there is no colour ring anywhere.
+ * 3. **Nothing is translucent, so nothing needs a fallback.** The reduced-transparency
+ *    path is gone because it is now the only path — a simplification, not a loss.
+ *
+ * Two things did NOT survive the shift, and both are real feature losses:
+ * **dark mode** (warm neutrals do not invert — the result is muddy khaki, not a dark
+ * theme) and **the five user accents**. Both are recorded as open gaps upstream.
+ */
+/**
+ * Kept as a type so call sites compile, but there is exactly one mode. A dark theme here
+ * needs its own ramp, not a transform of this one; until it exists, a dark system setting
+ * is answered by staying light.
+ */
+export type Mode = 'light';
+export type Surface = 'ios' | 'android';
+/**
+ * **Which palette an app is painted in.**
+ *
+ * `paper` is the warm-paper system every screen was built against. `solarium` is the reskin
+ * specified by `design_handoff_ambi` — the Canvas OS system from the `solarium` repo, whose
+ * values are transcribed here from its `globals.css` `:root` block.
+ *
+ * A THEME rather than a replacement, and that is forced by the constraint
+ * `design/AMBI-SURFACES.md` states in its own words: *Ambi does not own its design system —
+ * `@comppack/ds` is shared with Key and Build. A change to a token is a change to all three.*
+ * Overwriting the palette would silently reskin the keyboard app and app 3, neither of which
+ * asked for it. Selecting it per app is the only way to reskin one.
+ *
+ * `paper` stays the default, so an app that says nothing keeps exactly what it has.
+ */
+export type Theme = 'paper' | 'solarium';
+/** The four shortcut kinds. Kind colour is allowed ONLY inside the leading chip. */
+export type Kind = 'text' | 'action' | 'flow' | 'media';
+/**
+ * Status always carries a word. The dot beside it is redundant by design.
+ *
+ * **`needsUser`, added for the KeyShort revamp (D3, 11 Sep 2026).** Everything else here is a
+ * report — what a run did. This one is a request — what a run is waiting on the user for — and
+ * reads as a fourth semantic rather than a shade of `error`, because nothing failed. CLAUDE.md's
+ * old "one red, no warning tone" rule is now "one red, one warning": `error` stays the only red,
+ * `needsUser` is the warning.
+ */
+export type Status = 'executed' | 'running' | 'queued' | 'error' | 'needsUser';
+export type KindPair = {
+    bg: string;
+    fg: string;
+};
+/** A tinted chip: a ground and the ink that reads on it. */
+export type TonePair = {
+    bg: string;
+    fg: string;
+};
+export type Colors = {
+    /**
+     * Terracotta. Alias of the accent — they are the same colour now. It survives so
+     * components written against the pine system keep working; read nothing more into it.
+     */
+    brandPrimary: string;
+    brandOnPrimary: string;
+    brandSubtle: string;
+    /** The primary button, the active tab, step badges. One hue, one job. */
+    accentFill: string;
+    accentOnFill: string;
+    /**
+     * Accent TEXT is always this, never `accentFill`. The fill measures 4.71:1 on pure
+     * white but 4.19:1 on the page and 3.92:1 on its own tint — safe only as a background.
+     */
+    accentInk: string;
+    /** Behind an active glyph, a binding chip, a selected state. */
+    accentTint: string;
+    accentPressed: string;
+    /**
+     * **`--alert-soft` — the ground of a terminal failure. C7, decided 2026-09-18.**
+     *
+     * The pair that finally gives "Failed" a token of its own. Until C7 every failure fell back to
+     * apricot (`status.needsUser`), whose meaning is "needs attention, nothing is broken" — an overload
+     * that blurred the one distinction this system otherwise keeps. `alertSoft` is a GROUND;
+     * `alertInk` is its INK and the only legal text colour on it. Global, not output-scoped:
+     * this is the one place the values are defined. Measured (see `tests/alertTokens.test.tsx`):
+     * ink on soft 6.44:1, on card 7.85:1, on page 7.5:1.
+     */
+    alertSoft: string;
+    /** `--alert-ink`. Text, glyph or 1px border for a failure — never a fill. */
+    alertInk: string;
+    textPrimary: string;
+    textSecondary: string;
+    /**
+     * **The one deliberate contrast exemption in the system, and it is a knowing one.**
+     *
+     * 2.63:1 on the page, 2.96:1 on white — under the 3.0 floor for even large or incidental
+     * text. The Dashboard handoff states that failure in its own accessibility section, adopts
+     * the value anyway, and scopes it: *"permitted only for 13pt+ day headers, counters and
+     * timestamps"*. It asks for the discrepancy to be flagged to design, not overruled here.
+     *
+     * So: eyebrows, timestamps, roll-ups, hints, day labels. **Never anything a user must read
+     * to act** — those take `textSecondary` at 4.89:1.
+     *
+     * This was briefly `#8A8279` on a miscount of mine. Counting hexes across the whole design
+     * bundle put `#8A8279` ahead 143 to 71, but 127 of those came from `CANVAS2099.dc.html` —
+     * the *composite* document, which re-renders every frame from the shared token sheet. It
+     * double-counts the same screens. The per-screen frames are unambiguous: the Dashboard file
+     * uses `#9C958C` 32 times and `#8A8279` zero times.
+     */
+    textTertiary: string;
+    /**
+     * A glyph that is present but unavailable — the run row's caret, a disabled chevron.
+     *
+     * 1.57:1 on the page, so it is **never** legible text and must never carry a word. The
+     * Dashboard handoff names it for exactly one job: *"disabled glyphs (the row caret)"*.
+     */
+    textDisabled: string;
+    textOnAccent: string;
+    /** The flat stop the page gradient ends on. Anything that must match the page uses it. */
+    surfacePage: string;
+    /** Rows, cards, sheets. */
+    surface1: string;
+    /** Tab bar, nav bar. */
+    surface2: string;
+    /** Dialogs. */
+    surface3: string;
+    /**
+     * The host tray, read-only value boxes, chip grounds, **and skeleton fills**.
+     *
+     * A skeleton painted in this reads as loading only when it sits **inside a white shell** —
+     * on the page it is within 3% of the ground and disappears. That is a structural rule, not
+     * a colour one: a loading row keeps its card and skeletonises the contents.
+     */
+    surfaceSunken: string;
+    /**
+     * §17's `band` — the **unknown-state** tone, and the keyboard's bar.
+     *
+     * One step darker than `surfaceSunken`, which is what separates *we do not know* from the
+     * settled quiet of skipped and cancelled. It exists because §12 needs a tone that is neither
+     * success green nor error red: a step that timed out after its request had left may well have
+     * landed, and a red pill would say "nothing happened".
+     */
+    band: string;
+    hairline: string;
+    hairlineStrong: string;
+    /**
+     * **`--control-border` — the outline of a control you operate, not of a surface you read.**
+     *
+     * Checkbox and radio rims, a switch's off track, a dropzone's dashes, a pending step node.
+     * `hairline`/`hairlineStrong` are 1.1–1.3:1 by design — they separate surfaces, and a control
+     * drawn in them fails WCAG 1.4.11's 3:1 for "the visual information required to identify" it.
+     * This is the slot that clears it. Added by `design_handoff_solarium_blocks_case_studies`
+     * (2026-09-23); see `docs/HANDOFF-SOLARIUM-BLOCKS.md` §2. Measured in
+     * `tests/solariumTokens.test.ts`. Never text — it is a rim, and it only just clears 3:1.
+     */
+    controlBorder: string;
+    /**
+     * The automation rail. `bound` marks the segment above a step that reads from an
+     * earlier one — terracotta, because a binding is the thing the user authored.
+     */
+    rail: {
+        default: string;
+        bound: string;
+    };
+    /** "Add a step" and other additive outlines. */
+    dashed: string;
+    kind: Record<Kind, KindPair>;
+    /** A connector slug, an API constant, a run id — any string the machine owns. */
+    reference: TonePair;
+    /** A skill or named ability, as distinct from a connector. */
+    capability: TonePair;
+    status: Record<Status, string>;
+    /** The ground each status word sits on when it is rendered as a chip. */
+    statusBg: Record<Status, string>;
+};
+/**
+ * **The Solarium tokens the `Colors` shape has nowhere to put — and nothing else.**
+ *
+ * Solarium names eight hue families of up to four rungs each. `Colors` is one shape shared by
+ * paper and Solarium, and its slots are named by JOB (`accentTint`, `kind.action`,
+ * `statusBg.executed`) rather than by hue, so most of those rungs already live somewhere
+ * above under a different name. This holds only the leftovers.
+ *
+ * **Every hex defined here is defined nowhere else in this file.** That is the rule the
+ * object exists to enforce, and it is not pedantry: the moment `--sky-soft` is also spelled
+ * `solariumHues.skySoft`, a reskin that moves `kind.media` leaves the alias behind and two
+ * things that were meant to be one colour quietly drift apart. So when the rung you want is
+ * missing here, it is missing because it is already reachable — the map is:
+ *
+ * | Solarium | already in `Colors` as |
+ * |---|---|
+ * | `--coral` / `-deep` / `-soft` / `-tint` / `--on-coral` | `accentFill` / `accentInk` / `brandSubtle` / `accentTint` / `accentOnFill` |
+ * | `--butter-soft` / `--butter-deep` | `kind.action.bg` / `.fg`, and `statusBg.running` / `status.running` |
+ * | `--sky-soft` / `--sky-deep` | `kind.media` and `reference` |
+ * | `--lilac-soft` / `--lilac-deep` | `kind.flow` and `capability` |
+ * | `--neutral` / `-deep` / `-soft` | `textTertiary` / `textSecondary` / `band` (and `hairline`) |
+ * | `--mint` / `--mint-deep` | `statusBg.executed` / `status.executed` |
+ * | `--clay-deep` / `--clay-soft` | `status.error` / `statusBg.error` — see the note there |
+ * | `--apricot` / `--apricot-deep` | `statusBg.needsUser` / `status.needsUser` — added by D3, same reasoning as clay |
+ * | `--control-border` | `controlBorder` — Building Blocks handoff, 2026-09-23, in both palettes |
+ * | `--alert-soft` / `--alert-ink` | `alertSoft` / `alertInk` — C7, decided 2026-09-18: the terminal-failure pair, in both palettes |
+ * | `--ground` / `--card` / `--well` / `--ink` / `--muted` / `--line` / `--line-soft` | `surfacePage` / `surface1` / `surfaceSunken` / `textPrimary` / `textSecondary` / `hairlineStrong` / `hairline` |
+ *
+ * Which leaves four things: the mid rung of clay, butter, sky and lilac — the four families
+ * that reached `Colors` only as a soft/deep pair, because a hue's mid tone is a stroke or a
+ * bar and no `Colors` slot is a stroke. And `--on-butter`, which is not `--butter-deep`.
+ *
+ * **Apricot entire used to be the fifth thing here** — Solarium named it and this palette had
+ * never carried it under any name — until D3 (11 Sep 2026) promoted it into `Colors.status` as
+ * `needsUser`. It is removed below for the reason `clayDeep`/`claySoft` were never added here in
+ * the first place: once a hue's pair reads through a status word, keeping a second, hue-named
+ * copy is exactly the drift this comment's second paragraph warns about.
+ *
+ * **A separate export rather than a field on `Colors`, for the reason `solariumRadii` is
+ * one:** paper has no clay and no apricot, and widening the shared shape would force it to
+ * invent two families it does not have. The name is the guard — a paper app that reaches for
+ * `solariumHues` can see in the identifier that it is reaching outside its own system.
+ */
+export declare const solariumHues: {
+    /**
+     * **Failure, and only failure.** `clayDeep` and `claySoft` are NOT repeated here — they are
+     * `status.error` and `statusBg.error`, which is where a failed run should be reading its
+     * colour from anyway. This is the mid rung: the 1px rule down a failure bubble, the alert
+     * glyph's stroke, a full-height bar in a trend strip. Never text — 2.60:1 on white.
+     */
+    readonly clay: "#D98E73";
+    /** The mid rung of the gate hue — the padlock's stroke, not its ground. 1.83:1 on white. */
+    readonly butter: "#E9B949";
+    /**
+     * `--on-butter`, and deliberately not `--butter-deep` (`#7D5F14`, which is `kind.action.fg`).
+     * Solarium names both because they do different jobs: the deep rung is a LABEL on the soft
+     * tint, this is ink on `--butter` itself. Substituting one for the other is not a nuance —
+     * on that ground the deep rung measures 3.27:1 and this one 5.91:1, so the wrong pick puts
+     * the gate's own words under the legibility floor.
+     */
+    readonly onButter: "#4D3B0B";
+    /** Mid rungs. Their soft and deep rungs are `kind.media`/`reference` and `kind.flow`/`capability`. */
+    readonly sky: "#6E9FC4";
+    readonly lilac: "#9C8FD0";
+};
+/**
+ * **The keyboard focus ring — Solarium 0.2.0, mandatory (onboarding PRD §1.7).**
+ *
+ * A 1px accent edge plus a 3px accent-soft halo: the handoff's `border-color: --coral` +
+ * `box-shadow: 0 0 0 3px --coral-soft`, drawn entirely as box-shadow so it needs no border on the
+ * element and cannot shift layout. Built from the palette, so paper gets its own accent and nothing
+ * here is a new hex. It REPLACES the old "no colour focus ring anywhere" rule (2026-09-24,
+ * `docs/DECISIONS.md` §2): that rule is what the ThresholdFlow audit failed on.
+ *
+ * Shown on `:focus-visible` for controls (keyboard focus — `core/focusVisible` decides) and on any
+ * focus for text fields (`:focus-within` in the handoff), where the caret is not enough.
+ */
+export declare function focusRingFor(colors: Colors): string;
+/** The example in the colour field's invalid-hex message. Lives here because it is a hex. */
+export declare const HEX_EXAMPLE = "#1F6FEB";
+/** There is one palette. The signature keeps its shape so call sites do not churn. */
+export declare function paletteFor(_mode: Mode, surface: Surface, theme?: Theme): Colors;
+/**
+ * Each level is a hairline plus a two-part shadow: a tight contact shadow that keeps the
+ * edge crisp, and a wide soft one that does the lifting. Both are needed — one alone
+ * either looks stuck down or looks like it is floating away.
+ *
+ * **There is no fourth level.** If something seems to need one it needs different spacing.
+ *
+ * **Never add a light-coloured outer shadow.** That single move is what reads as
+ * neumorphism, and it is the specific thing this system has now replaced twice over.
+ */
+export type Lift = 1 | 2 | 3;
+export declare function liftFor(surface: Surface, level?: Lift, theme?: Theme): string;
+/**
+ * The lift for a card sitting **inside** another card's sunken tray, rather than on the page.
+ *
+ * Tighter than level 1 — `-14px`/`.28` against its `-16px`/`.30`. The difference is small and
+ * it is the whole point: a widget frame using the page-level shadow reads as floating above
+ * the tray instead of resting in it, which undoes the separation the tray exists to draw.
+ *
+ * Android collapses to the same hairline as level 1, because M3 groups with dividers rather
+ * than stacking shadows and a second inset shadow there reads as a seam.
+ */
+export declare function liftInner(surface: Surface): string;
+/**
+ * The ONE coloured shadow in the system, and it exists because the primary button is the
+ * one coloured object that floats.
+ */
+export declare const liftAccent = "0 6px 16px -8px rgba(193, 80, 46, 0.80)";
+/** Theme-aware `liftAccent` — paper's `#C1502E` vs Solarium's `#C1552C`; see `authFocusRingFor`. */
+export declare function liftAccentFor(theme?: Theme): string;
+/**
+ * A field is a hole in the paper, not an object on it, so it **never lifts**.
+ * Focus darkens the hairline from 9% to 28% — there is no colour focus ring anywhere.
+ */
+export declare const fieldEdge: {
+    readonly default: "0 0 0 1px rgba(42,39,36,0.09), 0 1px 2px rgba(42,39,36,0.04)";
+    readonly focus: "0 0 0 1px rgba(42,39,36,0.28), 0 1px 2px rgba(42,39,36,0.05)";
+    readonly error: "0 0 0 1px #A33224";
+};
+/**
+ * **Home's command field, which keys its ring off CONTENT rather than focus.**
+ *
+ * Not a second opinion about `fieldEdge` — a different state machine. Every other field in
+ * the product darkens on focus and returns when focus leaves; Home's dock darkens when the
+ * field **has something in it, or is in Build mode**, and stays dark whether or not the
+ * caret is there. That is deliberate: the dock is the subject of the tab, so its ring says
+ * *this field is carrying something* rather than *you are typing here*.
+ *
+ * There is no focus ring at all, which is why both steps are so close together. The field is
+ * not competing with the results above it, and an accent ring on a screen whose only accent
+ * is the mode chip and the mic would put the eye in the wrong place.
+ */
+export declare const commandEdge: {
+    readonly rest: "0 0 0 1px rgba(42,39,36,0.07), 0 1px 2px rgba(42,39,36,0.04)";
+    readonly filled: "0 0 0 1px rgba(42,39,36,0.14), 0 1px 2px rgba(42,39,36,0.04)";
+};
+/**
+ * A sign-in door — a white button that carries a provider mark and floats slightly.
+ *
+ * Heavier at the edge than `lift1` (14% against 7%) because a door is pressed rather than read:
+ * it has to look like an object with a boundary, not a card holding content. The soft half is
+ * tighter too (`-14px`/`.28` against `-16px`/`.30`), which keeps three stacked doors from reading
+ * as one drifting mass.
+ */
+export declare const doorEdge: {
+    readonly primary: "0 0 0 1px rgba(42,39,36,0.14), 0 1px 2px rgba(42,39,36,0.04), 0 8px 20px -14px rgba(42,39,36,0.28)";
+    readonly secondary: "0 0 0 1px rgba(42,39,36,0.12)";
+};
+/**
+ * **The one accent focus ring in the product, and it is a knowing exception.**
+ *
+ * This file states plainly that a field is a hole and that "focus darkens the hairline; there is
+ * no colour ring anywhere". The sign-in handoff (August 2026) specifies one anyway, twice, and the
+ * second use is why it is adopted rather than overruled: on the code field the ring sits on the
+ * **next empty box** and *is* the caret — there is no text cursor to see, so the ring has to carry
+ * position, and a darker hairline reads as a heavier border rather than as "you are here".
+ *
+ * Scoped to sign-in. Every other field in the product keeps `fieldEdge`, and this must not spread
+ * — flag it to design rather than quietly generalising it.
+ */
+export declare const authFocusRing = "0 0 0 1.5px rgba(193, 80, 46, 0.45)";
+export declare const authFieldRing = "0 0 0 1px rgba(42, 39, 36, 0.12)";
+/**
+ * **Theme-aware versions of `authFocusRing`/`authFieldRing`/`doorEdge`, for an app on Solarium.**
+ *
+ * The three constants above are evaluated at import time against paper's exact hex
+ * (`accentFill` `#C1502E`, `textPrimary` `#2A2724`) and cannot themselves become theme-aware —
+ * the same reason `lift1`/`lift2` are exposed through `useDs()` rather than imported directly
+ * (see `DsProvider.tsx`'s own note). Solarium's values are three digits apart (`accentFill`
+ * `#C1552C`, `textPrimary` `#2C2E2A`), which the sign-in and onboarding screens never picked up
+ * because nothing routed them there — the auth focus ring and every door's edge rendered a few
+ * RGB units off from where Solarium's own accent and ink actually sit.
+ *
+ * Kept as separate functions rather than changing the constants' type: `canvas-app` imports
+ * `authFieldRing`/`authFocusRing`/`doorEdge` directly as plain strings (`parity.test.ts`), so
+ * turning them into functions would be a breaking change to a consumer outside this repo.
+ */
+export declare function authFocusRingFor(theme?: Theme): string;
+export declare function authFieldRingFor(theme?: Theme): string;
+export declare function doorEdgeFor(theme?: Theme): {
+    primary: string;
+    secondary: string;
+};
+/**
+ * **A button that is drawn rather than filled** — an outline on the page colour, with no lift.
+ *
+ * The secondary half of a pair whose primary is sunken or accent-filled: Home's `Dismiss`
+ * beside `Copy`, and the save bar's `✕` beside `Save`. Heavier than a card's hairline at 12%
+ * against 7–9%, because it has to read as an edge you can press rather than as the boundary of
+ * a surface.
+ */
+export declare const outlineEdge = "0 0 0 1px rgba(42,39,36,0.12)";
+/** Theme-aware `outlineEdge` — same reason and same shape as `authFieldRingFor`. */
+export declare function outlineEdgeFor(theme?: Theme): string;
+/**
+ * Compatibility alias. The pine system called the card treatment `edge` and most
+ * components still ask for it; it resolves to lift-1.
+ */
+export declare function edgeFor(_mode: Mode, surface: Surface, theme?: Theme): string;
+/** Search-field focus. Kept for call sites; the edge IS the focus indicator. */
+export declare function focusEdgeFor(_mode: Mode): string;
+/**
+ * Three stops — cool green-grey at the top drifting warm toward the bottom, the way a
+ * sheet lit from one side reads.
+ *
+ * This is the ONE thing carried over from the glass system, and its justification changed
+ * completely: there it existed so blur had something to refract, here it is simply the
+ * warmth of the paper. **Keep it subtle** — if you can name it as a gradient at arm's
+ * length it is too strong. Full-bleed, never scrolls independently, never interactive.
+ */
+export declare function substrateFor(_mode?: Mode, theme?: Theme): readonly BackgroundImageValue[];
+/**
+ * The keyboard composites opaquely for its frame budget, which cost the glass system a
+ * whole baked-material pipeline. On paper that is simply what the surfaces already are —
+ * the extension renders what every other surface renders.
+ */
+export declare const keyboard: {
+    readonly surface: "#FFFFFF";
+    readonly surfaceAlt: "#E7E2D9";
+    readonly bar: "#F6F1E9";
+    readonly bed: "#E4DED4";
+    readonly edge: "0 1px 1.5px rgba(42, 39, 36, 0.16)";
+};
+/**
+ * The ladder pre-resolved for this platform. There is one palette and the platform is
+ * fixed at runtime, so a module constant is honest here — and it lets a module-scope
+ * `StyleSheet.create` block carry a lift without threading anything through.
+ */
+/**
+ * ⚠ **Theme-blind, and nothing in this app should import them any more.**
+ *
+ * They are evaluated at import time — before an app has had the chance to say which theme it
+ * wants — so they are always `paper`'s elevation, whatever the provider was told. The
+ * theme-aware reads are `useDs().lift1`, `.lift2` and — for level 3 — `.edge3`.
+ *
+ * ⚠ **This block used to claim every call site in the repo had already moved, and that was
+ * false for `lift3`.** `HomeSheet` and `ConfirmCard` still imported the constant, so the home
+ * sheet, the build panel's sheet and the canvas confirm card all drew PAPER's level 3 inside an
+ * app mounted `theme="solarium"` (App.tsx). Not a near-miss: paper level 3 opens with a
+ * `0 0 0 1px` hairline ring and closes on a tight `0 24px 48px -20px …0.45`, where solarium has
+ * no ring at all and a wide, soft `0 28px 64px …0.15`. Both now read `edge3`.
+ *
+ * There is deliberately no `useDs().lift3`. Level 3 has lived on the context as `edge3` since
+ * before this ladder was named, `RunSheet` already reads it, and a fourth synonym for one value
+ * in a file that already carries `edge`≈`lift1` and `edge2`≈`lift2` would make the confusion
+ * that caused this bug worse rather than better.
+ *
+ * Kept exported only because the two sibling apps' copies of this package still import them and
+ * are still on paper, where the values are correct. Delete them when those repos are synced.
+ */
+export declare const lift1: string;
+export declare const lift2: string;
+export declare const lift3: string;
+/**
+ * The one true drop shadow inside a platform-owned control: the iOS switch thumb. The
+ * redesign does not reach inside it.
+ */
+export declare const switchThumb: {
+    offsetX: number;
+    offsetY: number;
+    blurRadius: number;
+    color: string;
+    inset: boolean;
+}[];
+export declare const radii: {
+    readonly key: 10;
+    readonly chip: 8;
+    readonly control: 14;
+    readonly card: 20;
+    readonly sheet: 28;
+    readonly pill: 999;
+    readonly cardAndroid: 16;
+    readonly controlAndroid: 999;
+    readonly field: 8;
+    readonly pillSm: 10;
+    readonly search: 11;
+    readonly row: 12;
+    readonly button: 13;
+    readonly sheetIos: 14;
+    readonly iconTile: 18;
+    readonly dialogMd: 28;
+    readonly screen: 35;
+    readonly bezel: 44;
+};
+/**
+ * Solarium's radii, by the names this system already uses.
+ *
+ * Sheets take `26px` — the handoff calls that out as an iOS/Android platform value rather
+ * than a Solarium token, so it is quoted here with that provenance rather than folded into
+ * the ladder as if the design system had chosen it.
+ *
+ * **Chat bubbles are not on this ladder, and no rung should be added for them.** The
+ * chat-duplex handoff states it directly: bubbles use literal asymmetric radii, not tokens —
+ * agent `18 18 18 6`, yours `18 18 6 18`, the voice surface a uniform `26`. The asymmetry is
+ * the point (the squared corner is the tail, and which corner it is says who spoke), so the
+ * value a bubble needs is a four-corner shape rather than a number, and `card: 18` already
+ * supplies the three round corners. A `bubbleAgent` / `bubbleUser` pair here would be four
+ * numbers pretending to be one rung, and the next reader would try to use it for a card.
+ * They belong in the bubble component's own `StyleSheet` as
+ * `borderTopLeftRadius` / `…TopRight` / `…BottomRight` / `…BottomLeft`.
+ */
+export declare const solariumRadii: {
+    readonly chip: 9;
+    readonly control: 14;
+    readonly card: 18;
+    readonly sheet: 26;
+    readonly pill: 999;
+    readonly cardAndroid: 18;
+    readonly controlAndroid: 999;
+    /** `--r-sentence`: the command field and every search field. */
+    readonly sentence: 22;
+    /** `--r-major`: full-card empty states. */
+    readonly major: 20;
+    /** `--r-inset`: rows inside a list. */
+    readonly row: 14;
+    /** `--r-tile`: the 34-40px icon tiles. */
+    readonly iconTile: 9;
+    /** `--r-key` */
+    readonly key: 7;
+    /** `--r-nav` */
+    readonly nav: 12;
+    readonly field: 8;
+    readonly pillSm: 10;
+    readonly search: 11;
+    readonly button: 13;
+    readonly sheetIos: 14;
+    readonly dialogMd: 28;
+    readonly screen: 35;
+    readonly bezel: 44;
+};
+/**
+ * **The Building Blocks radius ladder — a third set, and deliberately not merged into either.**
+ *
+ * `design_handoff_solarium_blocks_case_studies` (2026-09-23) specifies major 16 · mid 12 · inset 8
+ * · tile 6 · key 4, with the rule *nest inner = outer − gap*. `solariumRadii` above came from the
+ * Ambi handoff and disagrees on every shared name (`major` 20, `row` 14, `iconTile` 9, `key` 7).
+ * Rewriting `solariumRadii` would reshape every Ambi screen; so the blocks read this ladder and
+ * nothing else does. Which ladder is right is open — `docs/HANDOFF-SOLARIUM-BLOCKS.md` §6.
+ */
+export declare const blockRadii: {
+    /** `--r-major`: cards, toasts, dialogs. */
+    readonly major: 16;
+    /** `--r-mid`: selectable cards, callouts, menus. */
+    readonly mid: 12;
+    /** `--r-inset`: fields, buttons, wells, menu items. */
+    readonly inset: 8;
+    /** `--r-tile`: leading tiles, segments. */
+    readonly tile: 6;
+    /** `--r-key`: a checkbox. */
+    readonly key: 4;
+};
+/**
+ * **Which rung each part of a widget's interior sits on.**
+ *
+ * Not a second system — every value here *is* a `radii` or `type` rung above. It exists
+ * because the widget layer kept answering "what radius is an error box?" per file, and
+ * arrived at seven different radii (6, 7, 8, 9, 10, 12, 999) and eight font sizes across
+ * eleven widgets. The answer is not a new number; it is *which existing rung*, written down
+ * once so the twelfth widget does not invent a ninth.
+ *
+ * Read it as a lookup, not a scale: a widget asks what KIND of part it is drawing and gets
+ * the rung. Anything not listed here does not belong inside a widget body.
+ */
+export declare const widgetPart: {
+    /** A pill: type pill, produced pill, delta pill, state pill. */
+    readonly pill: 8;
+    /** An inset block that holds a value: a well, an error box, a stats tile, a diff original. */
+    readonly block: 10;
+    /** A pressable control inside a body: Reconnect, Re-run, the presentation toggle. */
+    readonly control: 12;
+    /** A skeleton bar. Small enough that a softer corner reads as a different object. */
+    readonly skeleton: 4;
+    /** Anything circular — a numeral badge, a deck action. */
+    readonly round: 999;
+};
+/**
+ * **The strip along the bottom edge that docked overlays occupy.**
+ *
+ * A scrollable screen whose LAST element is something the user must press has to reserve this,
+ * or that control ends up underneath a toast. It is a real defect rather than a cosmetic one:
+ * an overlay sitting on top of a button swallows the tap, and from the user's side the button
+ * simply does not work.
+ *
+ * It has to clear two different things, which is why it is larger than any one of them. Ours is
+ * `ConflictToast`, docked at `insets.bottom + space.s14 * 2` because it is mounted once at the
+ * app root and cannot know whether the screen under it has a tab bar — so it clears the tallest
+ * case always. React Native's own LogBox notification is the other, and it sits lower; it is a
+ * development overlay, but "the Continue button does not respond while you are testing" is a
+ * cost paid on every device run.
+ *
+ * **Reserved on top of the safe-area inset, never instead of it** — the inset is the gesture
+ * handle's, and Android reports ~11dp for one it draws far taller.
+ */
+/**
+ * **The ground behind a modal, and it was never a token before this.**
+ *
+ * The app carries THREE scrim values across two files, all inline: `Confirm.tsx` uses
+ * `rgba(0, 0, 0, 0.42)`, while `Sheet.tsx` uses `rgba(8, 8, 10, 0.5)` and `rgba(8, 8, 10, 0.62)`
+ * for its destructive variant. Two different hues and three different opacities for one job —
+ * exactly the drift this file exists to stop, and it went unnoticed because a scrim is drawn
+ * once per overlay and never side by side with another.
+ *
+ * `Sheet`'s pair is adopted here because `Sheet` is the general-purpose overlay and the
+ * destructive step is a real distinction the other value cannot express. **`Confirm.tsx`'s
+ * `rgba(0, 0, 0, 0.42)` is left unreconciled on purpose** — collapsing it silently would be a
+ * visual change to a shipped screen made in passing, which is not a token decision to take
+ * inside an unrelated task. Flag it, port `Confirm` onto this, then delete the third value.
+ */
+export declare const scrim: {
+    readonly default: "rgba(8, 8, 10, 0.5)";
+    /** One step darker, for a sheet whose primary action destroys something. */
+    readonly destructive: "rgba(8, 8, 10, 0.62)";
+};
+/**
+ * **The Building Blocks modal scrim (O4)** — `rgba(44,46,42,.28)`, lighter than `scrim.default`
+ * because the handoff's dialog sits on a porcelain page rather than over a photo-dark app. Only the
+ * blocks' `Modal`/`Layer` read it; every existing sheet keeps `scrim`.
+ */
+export declare const blockScrim = "rgba(44, 46, 42, 0.28)";
+export declare const overlayLane = 80;
+/** 4pt base throughout — nothing is spaced by eye. */
+export declare const space: {
+    readonly s1: 4;
+    readonly s2: 8;
+    readonly s3: 12;
+    readonly s4: 16;
+    readonly s5: 20;
+    readonly s6: 24;
+    readonly s8: 32;
+    readonly s10: 40;
+    readonly s14: 56;
+    readonly gutterRow: 13;
+    readonly gutterText: 16;
+    readonly gapRow: 8;
+    readonly gapChip: 7;
+    readonly gapSection: 20;
+    readonly hitIos: 44;
+    readonly hitMd: 48;
+};
+export declare const layout: {
+    readonly gutter: 20;
+    readonly gutterAndroid: 16;
+    readonly rowPadding: 16;
+    readonly rowGap: 12;
+    readonly sectionGap: 20;
+    /** Accessibility floor. Never override, on either platform. */
+    readonly touchTargetMin: 44;
+    readonly kindChipSize: 28;
+    readonly kindChipSizeAndroid: 40;
+    readonly ctaHeight: 56;
+    /**
+     * The tab bar's own content height, BEFORE the safe-area inset — voice-and-tabs §1.
+     *
+     * §1 quotes 88 "including the home indicator", which makes it a derivation rather than a
+     * constant: 10 of top padding, a 27pt pill, a 6pt gap and the label come to 54, and the
+     * device adds the rest. On a 34pt phone that is the specified 88; on one with no indicator
+     * it is 54, instead of 88 with 34pt of dead strip under the labels.
+     *
+     * It replaces the `tabBarHeight` / `tabBarHeightAndroid` pair, which existed because the bar
+     * was a floating pill on iOS and flush on Android. It is flush on both now, so one number.
+     */
+    readonly tabBarContent: 54;
+};
+/** Platform-resolved layout constants, so screens do not branch by hand. */
+export declare const isAndroid: boolean;
+export declare const gutter: 20 | 16;
+export declare const cardRadius: 20 | 16;
+export declare const kindChipSize: 28 | 40;
+export declare const tabBarHeight: 54;
+/**
+ * Sizes, weights and tracking only — the FAMILY is resolved from the provider, because
+ * typeface is a user preference. Never hard-code a family at a call site.
+ */
+export declare const type: {
+    readonly display: {
+        readonly fontSize: 34;
+        readonly lineHeight: 38;
+        readonly fontWeight: "700";
+        readonly letterSpacing: number;
+    };
+    readonly title: {
+        readonly fontSize: 22;
+        readonly lineHeight: 28;
+        readonly fontWeight: "600";
+        readonly letterSpacing: number;
+    };
+    readonly heading: {
+        readonly fontSize: 17;
+        readonly lineHeight: 24;
+        readonly fontWeight: "600";
+        readonly letterSpacing: number;
+    };
+    readonly body: {
+        readonly fontSize: 16;
+        readonly lineHeight: 24;
+        readonly fontWeight: "400";
+        readonly letterSpacing: 0;
+    };
+    readonly label: {
+        readonly fontSize: 14;
+        readonly lineHeight: 20;
+        readonly fontWeight: "500";
+        readonly letterSpacing: 0;
+    };
+    readonly caption: {
+        readonly fontSize: 13;
+        readonly lineHeight: 18;
+        readonly fontWeight: "400";
+        readonly letterSpacing: number;
+    };
+    readonly monoTrigger: {
+        readonly fontSize: 17;
+        readonly lineHeight: 24;
+        readonly fontWeight: "500";
+        readonly letterSpacing: 0;
+    };
+    readonly monoMeta: {
+        readonly fontSize: 13;
+        readonly lineHeight: 18;
+        readonly fontWeight: "400";
+        readonly letterSpacing: 0;
+    };
+    /**
+     * The 32px screen H1 a KeyShort top-level screen carries below its drawer row — "Home",
+     * "Your keyboard", "Library". Added by A7 (`tasks/KEYSHORT-REVAMP.md`, 11 Sep 2026) rather
+     * than S4, which found the gap first but deliberately left it unnamed until a real call site
+     * existed to name it from (`KeyShortScreensA/B/C/D.dc.html`: `font-size:32px;line-height:1.1;
+     * letter-spacing:-.01em`). `display` (34) is close but is the mono mark on Shortcut detail's
+     * `/remind`, a different job at a different size — do not reach for it here.
+     */
+    readonly screenTitle: {
+        readonly fontSize: 32;
+        readonly lineHeight: 35;
+        readonly fontWeight: "400";
+        readonly letterSpacing: number;
+    };
+    /** Structural group labels — `RECENT RUNS`, `TRIGGER`, `STEPS`. */
+    readonly eyebrow: {
+        readonly fontSize: 12;
+        readonly lineHeight: 16;
+        readonly fontWeight: "500";
+        readonly letterSpacing: number;
+    };
+    /**
+     * The same job at the KeyShort handoff's size — `font-size:10px; letter-spacing:.12em` on
+     * every structural label it draws (`SET UP`, `TYPEFACE`, `ACTIONS`). Selected per app by
+     * `DsProvider`'s `headings="screen"`, never by a call site: the eyebrow is one decision for
+     * the whole app, not a size each screen picks. See D4 in the KeyShort task board.
+     */
+    readonly eyebrowDense: {
+        readonly fontSize: 10;
+        readonly lineHeight: 14;
+        readonly fontWeight: "500";
+        readonly letterSpacing: number;
+    };
+    /**
+     * The Settings handoff's grouped row (`design_handoff_padki_settings`, Component Spec · Row): a
+     * 15px title and a 12px subtitle, both regular. Neither `body` (16) nor `caption` (13) is either
+     * one, and v2 is pixel-exact. The value beside them is `caption`, which already is 13. Used by
+     * `GroupedRow` (SET-3, 13 Sep 2026).
+     */
+    readonly rowTitleDense: {
+        readonly fontSize: 15;
+        readonly lineHeight: 20;
+        readonly fontWeight: "400";
+        readonly letterSpacing: 0;
+    };
+    readonly rowSubtitle: {
+        readonly fontSize: 12;
+        readonly lineHeight: 16;
+        readonly fontWeight: "400";
+        readonly letterSpacing: 0;
+    };
+    /**
+     * `SubScreenHeader`'s two rungs (Settings handoff, 13 Sep 2026). `appBarTitle` is the Android top
+     * app bar's title — 18/600, the handoff's `← Settings` row; `mdAppBar` (22) is the legacy M3 size
+     * and not this. `screenSubtitle` is the 14px line under a screen title on both platforms.
+     */
+    readonly appBarTitle: {
+        readonly fontSize: 18;
+        readonly lineHeight: 24;
+        readonly fontWeight: "600";
+        readonly letterSpacing: 0;
+    };
+    readonly screenSubtitle: {
+        readonly fontSize: 14;
+        readonly lineHeight: 20;
+        readonly fontWeight: "400";
+        readonly letterSpacing: 0;
+    };
+    readonly iosLargeTitle: {
+        readonly fontSize: 34;
+        readonly lineHeight: 38;
+        readonly fontWeight: "700";
+        readonly letterSpacing: -0.7;
+    };
+    readonly mdAppBar: {
+        readonly fontSize: 22;
+        readonly lineHeight: 28;
+        readonly fontWeight: "600";
+    };
+    readonly overlayTitle: {
+        readonly fontSize: 19;
+        readonly lineHeight: 24;
+        readonly fontWeight: "600";
+    };
+    readonly rowTitle: {
+        readonly fontSize: 16;
+        readonly lineHeight: 24;
+        readonly fontWeight: "400";
+    };
+    readonly rowTrigger: {
+        readonly fontSize: 17;
+        readonly lineHeight: 24;
+        readonly fontWeight: "500";
+    };
+    readonly rowMeta: {
+        readonly fontSize: 13;
+        readonly lineHeight: 18;
+        readonly fontWeight: "400";
+    };
+    readonly sectionLabel: {
+        readonly fontSize: 13;
+        readonly lineHeight: 18;
+        readonly fontWeight: "600";
+    };
+    readonly monoLabel: {
+        readonly fontSize: 12;
+        readonly lineHeight: 16;
+        readonly fontWeight: "400";
+        readonly letterSpacing: 1.08;
+    };
+    readonly monoCount: {
+        readonly fontSize: 12;
+        readonly lineHeight: 16;
+        readonly fontWeight: "400";
+    };
+    readonly monoId: {
+        readonly fontSize: 11;
+        readonly lineHeight: 15;
+        readonly fontWeight: "400";
+    };
+    readonly statusBar: {
+        readonly fontSize: 12;
+        readonly lineHeight: 16;
+        readonly fontWeight: "400";
+    };
+};
+/**
+ * v2 is pixel-exact, so this is the identity. It survives only because the components
+ * moved in from `neu/` still wrap their literals in it; it goes as they are re-spaced.
+ */
+export declare const scale: (n: number) => number;
+/**
+ * No binaries are committed, so both families fall back to the system faces. React
+ * Native and iOS need .otf or .ttf — woff2 is web-only and will not load.
+ */
+/**
+ * The families the shortcuts handoff specifies — **Switzer** and **JetBrains Mono**,
+ * replacing Geist and Geist Mono.
+ *
+ * Naming them here would be worse than useless: no binaries are bundled, and React Native
+ * takes a single family name rather than a stack, so an unresolvable name silently falls
+ * back with no way to tell it did. The names are recorded and the system faces stand in
+ * until the binaries land — and they must be .otf or .ttf, not the woff2 the handoff's
+ * fonts.css imports, which will not load on iOS or Android.
+ */
+export declare const FONT_FAMILIES: {
+    readonly sans: "Switzer";
+    readonly mono: "JetBrains Mono";
+};
+export declare const FONTS: {
+    readonly sans: string;
+    readonly mono: string;
+};
+/**
+ * One signature moment: trigger fire. Everything else is restrained — press is scale
+ * only, never a colour change and never an opacity dip; a tab change is a crossfade,
+ * never a slide, because the four tabs are peers rather than a sequence.
+ */
+export declare const motion: {
+    readonly easeSweep: readonly [0.22, 1, 0.36, 1];
+    readonly easeStandard: readonly [0.4, 0, 0.2, 1];
+    readonly durationSweep: 420;
+    readonly durationPress: 120;
+    readonly durationTab: 180;
+    readonly durationReducedPulse: 200;
+    readonly pressScale: 0.98;
+    readonly instant: 140;
+    readonly fast: 160;
+    readonly quick: 180;
+    readonly base: 200;
+    readonly spin: 900;
+};
+/** The active segment of a Solarium segmented control (onboarding batch 2): white on the well, this lift. */
+export declare const segmentLift = "0 1px 2px rgba(44, 46, 42, .08)";
+//# sourceMappingURL=tokens.d.ts.map