@eifi1/ui-kit 0.54.0 → 0.55.0

package/src/components/user-avatar.tsx

@@ -1,116 +0,0 @@
-import type { ComponentPropsWithRef, ReactNode } from "react";
-import { cn } from "../lib/cn";
-import { personInitials } from "../lib/person-name";
-import type { PersonName } from "../lib/person-name";
-import { useKitLocale } from "../i18n/kit-labels";
-import { StatusDot } from "./status-dot";
-import type { StatusDotSize, StatusDotTone } from "./status-dot";
-
-/** Initials from a display name (first + last) or, failing that, an email —
- *  e.g. "Marcel Eifert" → "ME", "marcel@x.com" → "MA". App-agnostic.
- *
- *  "Failing that" means BLANK, not merely absent. This was `name ?? email ?? "?"`,
- *  and `??` falls through on null/undefined alone — so an empty or whitespace-only
- *  display name short-circuited the email it had in hand and landed on the guard
- *  below, returning "?" for a user whose address says "MA" perfectly well. Keksdose
- *  cannot reach it (its `display_name` has `min_length=1`), but this is exported as
- *  app-agnostic, and any consumer whose profile name is optional free text got a wall
- *  of "?" chips. The guard is what shows the empty case was foreseen; it just
- *  answered it at the wrong end. */
-export function avatarInitials(name?: string | null, email?: string | null): string {
-  const source = [name, email].map((s) => s?.trim()).find(Boolean) ?? "?";
-  const parts = source.split(/\s+/).filter(Boolean);
-  if (parts.length >= 2) return (parts[0][0] + parts[1][0]).toUpperCase();
-  return source.slice(0, 2).toUpperCase();
-}
-
-const AVATAR_SIZES = {
-  sm: "size-7 text-caption",
-  md: "size-8 text-xs",
-  lg: "size-12 text-base",
-} as const;
-
-const CHIP = "inline-flex shrink-0 items-center justify-center rounded-full bg-inverse font-semibold text-inverse";
-
-/** The dot grows with the avatar: 8px on `sm`, 10px on `md` (keksdose's), 12px on `lg`. */
-const BADGE_SIZES: Record<keyof typeof AVATAR_SIZES, StatusDotSize> = { sm: "sm", md: "md", lg: "lg" };
-
-/** A status dot in the avatar's top corner — an unread count, presence. */
-export interface UserAvatarBadge {
-  /** What the dot MEANS, for a screen reader ("3 unread"). Required: a coloured circle
-   *  says nothing to someone who cannot see it. */
-  label: ReactNode;
-  /** Default `danger`, the unread dot both apps draw by hand. */
-  tone?: StatusDotTone;
-}
-
-/** A `<span>`'s props, minus `children`: the content is the initials this computes
- *  from `person`/`name`/`email`, so there is nothing for a caller to put inside. */
-export interface UserAvatarProps extends Omit<ComponentPropsWithRef<"span">, "children"> {
-  name?: string | null;
-  email?: string | null;
-  /**
-   * The person's first and last name (0.29.0, docs/auth-harmonization.md §3.2) —
-   * preferred over `name` whenever either part is filled in. The initials follow the
-   * READER's language, the provider's `locale`: "AE" for Ada Example, "EA" in Hungarian
-   * (family name first), the family name's first character alone in Chinese. See
-   * {@link personInitials}.
-   *
-   * `name` stays the fallback for an API that still sends only `display_name`, and
-   * `email` after it: a person whose two parts are both blank falls through to them.
-   * A migrated user (the whole old display name in `first`, no `last`, §3.3) keeps the
-   * initials they had.
-   */
-  person?: PersonName | null;
-  size?: keyof typeof AVATAR_SIZES;
-  /**
-   * A status dot in the top-end corner (the top-right in LTR, top-left in RTL), ringed
-   * in the surface colour so it reads as its own mark (keksdose account-menu ~385,
-   * top-bar :152). Its `label` is read as text where the dot sits — inside a button
-   * named by its content it joins that name. In `TopBarActionMenu`'s `trigger` the
-   * button is named by the menu's `aria-label` followed by this label: "Account menu
-   * 3 unread". The initials stay hidden either way, so the person's name is NOT part
-   * of it — put it in `aria-label` ("Marcel Eifert, account menu") if it should be.
-   */
-  badge?: UserAvatarBadge | null;
-}
-
-/**
- * A round initials avatar — the common user chip shared across apps (feedback
- * #333). Purely presentational; wrap it in a button for the account menu trigger.
- */
-export function UserAvatar({ name, email, person, size = "md", badge, className, ...rest }: UserAvatarProps) {
-  const locale = useKitLocale();
-  const initials = (person ? personInitials(person, locale) : "") || avatarInitials(name, email);
-  if (badge) {
-    // A wrapper, because the chip itself is `aria-hidden` and the badge label must not
-    // be. `className` stays on the chip (a size override still sizes the circle); the
-    // other attributes go on the wrapper, which is what a caller addresses. `relative`
-    // also contains the sr-only text.
-    return (
-      <span {...rest} className="relative inline-flex shrink-0">
-        <span aria-hidden className={cn(CHIP, AVATAR_SIZES[size], className)}>
-          {initials}
-        </span>
-        <StatusDot ring tone={badge.tone ?? "danger"} size={BADGE_SIZES[size]} className="absolute -end-0.5 -top-0.5" />
-        <span className="sr-only">{badge.label}</span>
-      </span>
-    );
-  }
-  return (
-    <span
-      // `aria-hidden` sits BEFORE the spread, unlike the structural attributes on the
-      // other components here, because it is a DEFAULT rather than an invariant. The
-      // avatar is decorative next to the name it belongs to — which is where all three
-      // apps render it — so hiding it stops a screen reader saying "ME" after the word
-      // "Marcel Eifert". A caller who renders one ALONE (an assignee column, a
-      // presence dot) needs the opposite, and now has it: `aria-hidden={false}` plus an
-      // `aria-label` arrives through `...rest` and wins.
-      aria-hidden
-      {...rest}
-      className={cn(CHIP, AVATAR_SIZES[size], className)}
-    >
-      {initials}
-    </span>
-  );
-}

package/src/components/wizard-stepper.tsx

@@ -1,42 +0,0 @@
-import { cn } from "../lib/cn";
-
-/** Compact step indicator for the import wizards. Past steps are plain, the
- * current one is highlighted, future ones muted. */
-export function WizardStepper({
-  steps,
-  current,
-  "aria-label": ariaLabel,
-}: {
-  steps: { key: string; label: string }[];
-  current: string;
-  /** Names the list of steps ("Import steps"). */
-  "aria-label"?: string;
-}) {
-  const currentIndex = steps.findIndex((s) => s.key === current);
-  return (
-    // `flex-wrap`: the steps flow onto a second line rather than past the screen
-    // (0.32.1, the 360 px Extra-large sweep; docs/text-size-harmonization.md §4).
-    // "Upload — Map columns — Confirm" ran 22 px past a 360 px phone at Extra large.
-    // Where the steps fit, they stay one row.
-    <ol className="flex flex-wrap items-center gap-1 text-xs" aria-label={ariaLabel}>
-      {steps.map((step, i) => (
-        <li key={step.key} className="flex items-center gap-1">
-          {i > 0 && <span className="w-4 border-t border-subtle" />}
-          <span
-            aria-current={step.key === current ? "step" : undefined}
-            className={cn(
-              "rounded-full px-2 py-0.5",
-              i === currentIndex
-                ? "bg-inverse text-inverse font-medium"
-                : i < currentIndex
-                  ? "text-secondary"
-                  : "text-placeholder",
-            )}
-          >
-            {step.label}
-          </span>
-        </li>
-      ))}
-    </ol>
-  );
-}

package/src/components/write-lock-labels.ts

@@ -1,10 +0,0 @@
-// The English words of ./write-lock, in a module with no component code: the English
-// catalogue (src/i18n/defaults.ts) imports them without the component, so `en` loads as one
-// chunk like the other languages (0.34, KS U8). ./write-lock re-exports them.
-
-import type { WriteLockLabels } from "./write-lock";
-
-export const DEFAULT_WRITE_LOCK_LABELS: WriteLockLabels = {
-  reason: "You can view this but not change it.",
-  offline: "Needs a connection.",
-};

package/src/components/write-lock.tsx

@@ -1,253 +0,0 @@
-import { createContext, useContext, useMemo } from "react";
-import type { ReactNode } from "react";
-import { useKitLabels, type LabelOverride } from "../i18n/kit-labels";
-import { hasContent } from "../lib/presence";
-import { DEFAULT_WRITE_LOCK_LABELS } from "./write-lock-labels";
-
-/** The words {@link WriteLockProvider} renders on its own behalf. */
-export interface WriteLockLabels {
-  /** The tooltip of a locked commit when the provider gives no `reason`. */
-  reason: string;
-  /** 0.46 (kastlan K4): the reason of {@link useOfflineWriteLock} — "Needs a connection." */
-  offline: string;
-}
-
-// Defined in ./write-lock-labels, which holds no component code (0.34, KS U8).
-export { DEFAULT_WRITE_LOCK_LABELS };
-
-/**
- * What kind of lock a source is (docs/billing-harmonization.md §12.36, ui-kit 0.33).
- * `"demo"` (the read-only demo, `demo.writeLocked`), `"billing"` (a lapsed plan,
- * `billing.lockReason`) and, since 0.46, `"offline"` ({@link OFFLINE_LOCK}) are the kit's; an app names its own — Kurvenschmiede's
- * `"access"` (a curve shared to view) and `"customer"` (an account that owns nothing).
- * A control exempts itself from a kind with {@link CommitScope}; a source without a
- * kind is never exempted.
- */
-export type WriteLockKind = "demo" | "billing" | "offline" | (string & {});
-
-/** One locked source, as the provider holds it: its kind and its one sentence. */
-export interface WriteLockHold {
-  kind: WriteLockKind | undefined;
-  reason: ReactNode;
-}
-
-/**
- * A control's opt-in to the lock — the type of every `commit` prop in the kit.
- *
- * - `true`: every lock refuses the control (a save, an add, an invite).
- * - `{ except: [kinds] }`: every lock but those kinds. A billing lock leaves the
- *   reader able to remove access, revoke sessions, delete the account and change their
- *   own settings (§3.3, §12.13), so the kit's parts for those take
- *   {@link COMMIT_EXCEPT_BILLING} built in, and an app's own controls of that sort do
- *   too.
- * - `false` or left out: no lock reaches it.
- *
- * Under a demo lock and a billing lock together, a control exempt from billing is
- * still refused, with the demo's reason.
- */
-export type CommitScope = boolean | { readonly except: readonly WriteLockKind[] };
-
-/** Every lock but billing's: the scope of an action a lapsed plan still allows — removing
- *  access, the account's own settings, an operator's admin route (§12.13). One constant,
- *  so the call sites read alike. */
-export const COMMIT_EXCEPT_BILLING = { except: ["billing"] } as const;
-
-/**
- * 0.46 (kastlan K4, docs/local-first-harmonization.md D4): the kind of the lock "this
- * device has no connection". An action that only the server can do (numbers, money,
- * mail, people, settings) is locked with "Needs a connection." while offline; a control
- * that writes to the device's copy and syncs later takes {@link COMMIT_EXCEPT_OFFLINE}.
- * Feed it with {@link useOfflineWriteLock}.
- */
-export const OFFLINE_LOCK = "offline" as const;
-
-/** Every lock but the offline one: the scope of a control that works on the device's copy
- *  (it is still locked for a demo or a lapsed plan). */
-export const COMMIT_EXCEPT_OFFLINE = { except: [OFFLINE_LOCK] } as const;
-
-/**
- * What {@link useWriteLock} returns: whether commits are locked here as a control with
- * the scope asked for sees it, and why.
- */
-export interface WriteLock {
-  locked: boolean;
-  /** The one sentence a locked commit shows in its tooltip: the first hold in scope's.
-   *  Always set while `locked`; `undefined` when not. */
-  reason: ReactNode | undefined;
-  /** The first hold in scope's kind; `undefined` while unlocked, or for a source that
-   *  names none. */
-  kind: WriteLockKind | undefined;
-  /**
-   * EVERY locked source the provider holds, in the order the server refuses them
-   * (§12.3: the demo's 403 before billing's 402) — unfiltered by the scope, for code
-   * that must know what else locks (a toast that names the plan, a swipe plan). Empty
-   * while the provider is unlocked.
-   */
-  holds: readonly WriteLockHold[];
-}
-
-const NO_HOLDS: readonly WriteLockHold[] = [];
-
-const UNLOCKED: WriteLock = { locked: false, reason: undefined, kind: undefined, holds: NO_HOLDS };
-
-const WriteLockContext = createContext<WriteLock>(UNLOCKED);
-
-export interface WriteLockProviderProps {
-  /** Commits below are locked. `false` unlocks a subtree under an outer lock. */
-  locked: boolean;
-  /**
-   * The one sentence that says why — "Shared with you to read", "Read-only demo —
-   * saving is disabled", "A customer account cannot create curves". The app's policy,
-   * already translated. Left out: `labels.reason`.
-   */
-  reason?: ReactNode;
-  /** What kind of lock this is — `"demo"`, `"billing"` or the app's own (see
-   *  {@link WriteLockKind}), for a provider of one source. Left out, no control can be
-   *  exempt from it. */
-  kind?: WriteLockKind;
-  /**
-   * Every locked source, in refusal order — what `combineWriteLocks` answers, so
-   * `<WriteLockProvider {...combineWriteLocks([...])}>` carries them. Given while
-   * `locked`, it wins over `kind` and `reason`; a hold without a reason takes
-   * `labels.reason`.
-   */
-  holds?: readonly WriteLockHold[];
-  labels?: LabelOverride<WriteLockLabels>;
-  children?: ReactNode;
-}
-
-// `null`/`""`/`false` count as "no reason given" (`hasContent`): a lock whose tooltip is
-// empty would be a disabled button that cannot say why, the thing this replaces.
-
-/**
- * The read-only lock — **everything renders; only the commit is locked.**
- *
- * keksdose (features/budgets/write-lock.tsx, the read-only demo budget) and
- * Kurvenschmiede (features/sharing/write-lock.tsx, a curve shared to view, a customer
- * account that owns nothing) each built the same `SaveGuard`: the page, its tabs,
- * forms and dialogs render exactly as for an owner, because a viewer looking at half
- * a page is not looking at what they were sent; what changes is that the control
- * that SAVES is off and says why on hover or focus. Both wrapped each Save in a
- * Tooltip and forced a native `disabled` on it — out of the tab order, so the reason
- * never reached a keyboard — and both had to remember it at thirty call sites.
- *
- * Here the page mounts one provider and each commit control opts in with `commit`
- * ({@link Button}, {@link IconButton}, {@link FormActions}): under a lock it takes the
- * kit's `disabledReason` path with this reason — `aria-disabled` and focusable,
- * every activation swallowed, the reason in the kit Tooltip and its description.
- *
- * Who is locked is the app's: the provider takes a boolean, never a role. Fields stay
- * editable — nothing in them reaches the server until the commit is pressed, and a
- * form you cannot fill in is not a demo of the form (keksdose accounts-page). A
- * control that IS its own commit (a toggle that saves on change) reads
- * {@link useWriteLock} and disables itself. The lock is a courtesy, not a guard: the
- * server still refuses the write.
- *
- * **A lock says its source** (0.33, docs/billing-harmonization.md §12.36). A lapsed
- * plan locks creating and changing, but not removing access or the account's own
- * settings (§3.3, §12.13), and the kit's parts for those hard-coded `commit` — so
- * kastlan's app-wide lock locked a member's own sign-out everywhere. Each source now
- * has a kind, the provider holds every locked one in order (`holds`, from
- * `combineWriteLocks`), and a control's `commit` may name the kinds it is exempt from
- * ({@link CommitScope}). The kit's parts follow §3.3 and §12.13 by themselves.
- *
- * Nested providers: the nearest wins, so an inner `locked={false}` reopens a section
- * the caller may write (a viewer's own notes on a shared curve) — every source at
- * once — and an inner lock with its own reason (Kurvenschmiede's owner lock beside the
- * viewer lock) overrides the outer one's sentence and its holds.
- */
-export function WriteLockProvider({ locked, reason, kind, holds, labels, children }: WriteLockProviderProps) {
-  // The `writeLock` namespace: prop > `<UiKitProvider labels>` > English.
-  const fallback = useKitLabels("writeLock", DEFAULT_WRITE_LOCK_LABELS, labels).reason;
-  // `holds` wins while it has any; otherwise this provider is one source of its own.
-  const several = locked && holds !== undefined && holds.length > 0 ? holds : undefined;
-  const firstKind = several ? several[0].kind : kind;
-  const firstGiven = several ? several[0].reason : reason;
-  const firstReason = hasContent(firstGiven) ? firstGiven : fallback;
-  // Memoised on the first hold's kind and sentence — the strings an app passes — so a
-  // one-source lock keeps one context value across renders; a list of several is
-  // memoised on its own identity.
-  const many = several && several.length > 1 ? several : undefined;
-  const value = useMemo<WriteLock>(() => {
-    if (!locked) return UNLOCKED;
-    const all = many
-      ? many.map((hold) => ({ kind: hold.kind, reason: hasContent(hold.reason) ? hold.reason : fallback }))
-      : [{ kind: firstKind, reason: firstReason }];
-    return { locked: true, reason: firstReason, kind: firstKind, holds: all };
-  }, [locked, many, firstKind, firstReason, fallback]);
-  return <WriteLockContext.Provider value={value}>{children}</WriteLockContext.Provider>;
-}
-
-/**
- * Whether a hold refuses a control with this scope: `true` refuses with every hold,
- * `{ except }` with every hold whose kind it does not name. A hold with no kind is
- * never exempted — an app that forgot to name its source must not reopen by accident.
- */
-function inScope(hold: WriteLockHold, scope: CommitScope): boolean {
-  if (scope === true) return true;
-  if (scope === false) return false;
-  return hold.kind === undefined || !scope.except.includes(hold.kind);
-}
-
-/**
- * The lock as a control with `scope` sees it — {@link useWriteLock}'s answer, pure, for
- * a scope known only at call time: `useConfirm` reads the CALLER's lock when it is
- * called, and applies each `confirm({ commit })`'s own scope to it when it runs.
- *
- * `undefined` and `false` see no lock (a control without `commit`); `true` sees the
- * lock as it is; `{ except }` sees the first hold of another kind, with its reason
- * and kind. `holds` is passed on unfiltered.
- */
-export function writeLockFor(lock: WriteLock, scope: CommitScope | undefined): WriteLock {
-  if (!lock.locked || scope === true) return lock;
-  // A lock built by hand (a test's, an app's own context) may carry no holds: it is
-  // then the one source it describes.
-  const holds = lock.holds.length > 0 ? lock.holds : [{ kind: lock.kind, reason: lock.reason }];
-  const first = scope === undefined ? undefined : holds.find((hold) => inScope(hold, scope));
-  if (!first) return { ...UNLOCKED, holds: lock.holds };
-  // The first in scope is the provider's own first: the lock as it is, same object.
-  if (first === holds[0]) return lock;
-  return { locked: true, reason: first.reason, kind: first.kind, holds: lock.holds };
-}
-
-/**
- * The nearest {@link WriteLockProvider}'s lock, as a control with `scope` sees it —
- * unlocked with no provider. Left out, the scope is `true`: every lock.
- *
- * For code that must KNOW rather than a control that opts in: a toast that says why,
- * a swipe plan that leaves an action out, a hand-rolled toggle that disables itself.
- * `useWriteLock(COMMIT_EXCEPT_BILLING)` answers "would a lapsed plan's lock refuse me?"
- * as a removal sees it — what keksdose's `useWriteLockKind() !== "billing"` asked.
- */
-export function useWriteLock(scope: CommitScope = true): WriteLock {
-  return writeLockFor(useContext(WriteLockContext), scope);
-}
-
-/**
- * The `disabledReason` a control with `commit` should use: the lock's reason while
- * the lock refuses this scope — it wins over the control's own, since it is the answer
- * to the question the hover is asking — else the control's own. Internal to the kit's
- * commit controls.
- */
-export function useCommitReason(commit: CommitScope | undefined, own: ReactNode): ReactNode {
-  const lock = writeLockFor(useContext(WriteLockContext), commit);
-  return lock.locked ? lock.reason : own;
-}
-
-/**
- * 0.46 (kastlan K4): the offline lock as one source of `combineWriteLocks` —
- * `{ locked: offline, kind: "offline", reason: writeLock.offline }` ("Needs a
- * connection.", seven languages). `offline` is the app's own reading of the connection
- * (`!navigator.onLine`, or its better guess); the kit does not watch the network here.
- * List it after the demo's and billing's sources: the server refuses those first.
- *
- *     <WriteLockProvider {...combineWriteLocks([demo, billing, useOfflineWriteLock(!online)])}>
- *     <Button commit={COMMIT_EXCEPT_OFFLINE}>Save handover</Button>
- */
-export function useOfflineWriteLock(
-  offline: boolean,
-  labels?: LabelOverride<WriteLockLabels>,
-): { locked: boolean; kind: typeof OFFLINE_LOCK; reason: string } {
-  const words = useKitLabels("writeLock", DEFAULT_WRITE_LOCK_LABELS, labels);
-  return { locked: offline, kind: OFFLINE_LOCK, reason: words.offline };
-}

package/src/currencies.ts

@@ -1,90 +0,0 @@
-// `@eifi1/ui-kit/currencies` — the currencies the kit's pickers offer, as plain data
-// (0.35, keksdose's 0.34 report).
-//
-// This module imports NOTHING: no React, no stylesheet, no other kit module. That is the
-// entry's whole promise, because an app's BUILD reads it in Node — keksdose's Vite plugin
-// builds its flag-icons subset from these country codes while Vite loads its config. Until
-// 0.35 that plugin parsed the `country` literals out of dist/components/currency-select.js;
-// 0.34 moved the list into the picker's option list and 91 of its test files failed at
-// load. A file inside dist/ is not something the kit promises; an entry is.
-// packaging-contract.test.ts pins the purity, scripts/verify-package.mjs the load in Node.
-//
-// CurrencySelect, AmountInput's currency chip and NumberInput's code detection read this
-// same array (components/currency-option-list re-exports it, and currency-select as it
-// always has), so the list the pickers show and the flags an app ships cannot drift.
-//
-// A currency that was REPLACED stays in the array, marked `retired`: the pickers stop
-// offering it, and whatever reads a value an app already holds — the trigger's flag and
-// code, `getCurrency`, the flag subset, NumberInput's code detection — keeps knowing it
-// (keksdose audit follow-up, 2026-11-01: the lev, after Bulgaria's euro).
-
-export interface CurrencyOption {
-  code: string;
-  name: string;
-  symbol: string;
-  /** ISO 3166-1 alpha-2 country code (lowercase) used by flag-icons. */
-  country: string;
-  /**
-   * The day ("YYYY-MM-DD") the currency was replaced as its country's money — set only on
-   * one that was. The pickers leave it out of their default list. A field that already
-   * holds it still shows it (the trigger's flag and code, and its row in the list,
-   * checked), and an explicit `options` list that names it still offers it: that list is
-   * the caller's.
-   *
-   * Marked rather than deleted, because an app may hold amounts in it from before. Gone
-   * from the array, `getCurrency` would answer `undefined` for a stored value, the field
-   * would show its placeholder over a real amount, and an app's flag subset
-   * (`CURRENCY_COUNTRIES`) would ship that value's flag as an empty box.
-   */
-  retired?: string;
-}
-
-export const CURRENCIES: CurrencyOption[] = [
-  { code: "EUR", name: "Euro", symbol: "€", country: "eu" },
-  { code: "USD", name: "US Dollar", symbol: "$", country: "us" },
-  { code: "GBP", name: "British Pound", symbol: "£", country: "gb" },
-  { code: "CHF", name: "Swiss Franc", symbol: "CHF", country: "ch" },
-  { code: "JPY", name: "Japanese Yen", symbol: "¥", country: "jp" },
-  { code: "CAD", name: "Canadian Dollar", symbol: "CA$", country: "ca" },
-  { code: "AUD", name: "Australian Dollar", symbol: "A$", country: "au" },
-  { code: "NZD", name: "New Zealand Dollar", symbol: "NZ$", country: "nz" },
-  { code: "SEK", name: "Swedish Krona", symbol: "kr", country: "se" },
-  { code: "NOK", name: "Norwegian Krone", symbol: "kr", country: "no" },
-  { code: "DKK", name: "Danish Krone", symbol: "kr", country: "dk" },
-  { code: "PLN", name: "Polish Zloty", symbol: "zł", country: "pl" },
-  { code: "CZK", name: "Czech Koruna", symbol: "Kč", country: "cz" },
-  { code: "HUF", name: "Hungarian Forint", symbol: "Ft", country: "hu" },
-  { code: "RON", name: "Romanian Leu", symbol: "lei", country: "ro" },
-  // Bulgaria adopted the euro on 2026-01-01 (keksdose audit follow-up, 2026-11-01).
-  { code: "BGN", name: "Bulgarian Lev", symbol: "лв", country: "bg", retired: "2026-01-01" },
-  { code: "TRY", name: "Turkish Lira", symbol: "₺", country: "tr" },
-  { code: "RUB", name: "Russian Ruble", symbol: "₽", country: "ru" },
-  { code: "CNY", name: "Chinese Yuan", symbol: "¥", country: "cn" },
-  { code: "HKD", name: "Hong Kong Dollar", symbol: "HK$", country: "hk" },
-  { code: "SGD", name: "Singapore Dollar", symbol: "S$", country: "sg" },
-  { code: "INR", name: "Indian Rupee", symbol: "₹", country: "in" },
-  { code: "BRL", name: "Brazilian Real", symbol: "R$", country: "br" },
-  { code: "MXN", name: "Mexican Peso", symbol: "MX$", country: "mx" },
-  { code: "ZAR", name: "South African Rand", symbol: "R", country: "za" },
-  { code: "ILS", name: "Israeli Shekel", symbol: "₪", country: "il" },
-  { code: "AED", name: "UAE Dirham", symbol: "د.إ", country: "ae" },
-];
-
-/**
- * Each currency code → the flag the kit paints for it: the lowercase ISO 3166-1 alpha-2
- * code flag-icons names it by (`fi-ch`, `flags/4x3/ch.svg`). `CHF` → `"ch"`, `EUR` →
- * `"eu"` (flag-icons has the EU's flag under that code).
- *
- * Derived from {@link CURRENCIES}, so a currency the pickers gain is a flag here too — and
- * a `retired` one keeps its flag, for the values an app still holds in it. An app that
- * ships only the flags it renders builds its subset from these values:
- *
- * ```ts
- * // vite.config.ts — plain Node, no DOM
- * import { CURRENCY_COUNTRIES } from "@eifi1/ui-kit/currencies";
- * const flags = new Set(Object.values(CURRENCY_COUNTRIES));
- * ```
- */
-export const CURRENCY_COUNTRIES: Record<string, string> = Object.fromEntries(
-  CURRENCIES.map((c) => [c.code, c.country]),
-);

package/src/data-table.ts

@@ -1,42 +0,0 @@
-// `@eifi1/ui-kit/data-table` — the table suite.
-//
-// A re-slicing of the main barrel, not a new API. This entry point imports
-// `react-router` (a peer dependency), but since 0.49 (KIT-3) a Router is needed only for
-// a table with `urlSync`: without it DataTable keeps its view in local state alone.
-export * from "./components/data-table-labels";
-export * from "./components/data-table-sort";
-export * from "./components/data-table-filters";
-export * from "./components/data-table-pagination";
-export { FilterPopover } from "./components/data-table-filter-popover";
-// `SortState` comes from data-table-sort above; re-exporting the module wholesale
-// would collide with it, which is why the main barrel names these explicitly too.
-export { DataTable, DEFAULT_DATA_TABLE_SORT_LABELS } from "./components/data-table";
-export type {
-  DataTableSortLabels,
-  DataTableColumn,
-  // The barrel had these two and this entry did not (refactor audit 2026-10, MOD-5):
-  // the types of a column's `cellProps` and `headProps`.
-  DataTableCellProps,
-  DataTableHeadProps,
-  DataTableProps,
-  ServerPagination,
-  FilterState,
-  MobileSwipeActions,
-  DataTableDensity,
-  DataTableChrome,
-  DataTableRowAction,
-  DataTableDesktopSwipeActions,
-} from "./components/data-table";
-// 0.48 (keksdose dev #605): a `groupBy` level (also `mobileGroupBy`'s) and the `loadMore` footer.
-export type { DataTableGroupBy, DataTableLoadMore } from "./components/data-table-groups";
-// 0.48.2 (keksdose dev #632): `virtualize`'s options.
-export type { DataTableVirtualize } from "./components/data-table-virtual";
-export * from "./components/data-table-cells";
-export { useTableUrlState } from "./components/use-table-state";
-export type {
-  TableUrlState,
-  TableUrlSync,
-  TableUrlStateProps,
-  UseTableUrlStateOptions,
-  UseTableUrlStateReturn,
-} from "./components/use-table-state";