@eifi1/ui-kit 0.54.0 → 0.55.0

package/src/search/search-index.ts

@@ -1,283 +0,0 @@
-import type { ReactNode } from "react";
-import { foldForSearch } from "../lib/text-match";
-
-/**
- * The matcher behind {@link GlobalSearch} — pure, React-free, testable on its own.
- *
- * WHY IT EXISTS. `CommandPalette` is deliberately domain-free: it shows whatever a
- * `search(query)` provider returns. So every app wrote that provider, and every app wrote
- * the same one — `label.toLowerCase().includes(q)` over its pages and actions (kastlan's
- * command palette, keksdose's global search) plus a second copy with keywords for the
- * settings catalogue (keksdose's `matchSettingsEntries`). A substring test answers "does
- * this string contain that one", which is not what a search box is asked:
- *
- *  - "range date" finds nothing, because the words are in the other order;
- *  - "Uberweisung" misses "Überweisung", and "Tooltp" misses "Tooltip";
- *  - "del" matches "model" as happily as "delete", and every hit ranks the same, so the
- *    exact page name can sit under six unrelated rows.
- *
- * What it does instead, per entry:
- *
- *  - NORMALISES both sides: lower case, accents stripped (NFD minus combining marks),
- *    `ß` → `ss`, punctuation as a word break, and camelCase split so `DateRangePicker`
- *    is also the words date, range, picker.
- *  - Requires EVERY query word to match SOMEWHERE in the entry — title, keywords or
- *    description, in any order.
- *  - A word matches a word of the entry exactly, as its prefix, inside it (four letters or
- *    more, for compounds: "bereich" in "Datumsbereich"), or — for words of five letters
- *    or more — at edit distance one, transpositions included ("tooltp", "calender").
- *  - RANKS in tiers: exact title > title prefix > all words in the title > some word only
- *    in the keywords > some word only in the description. Within a tier, better word
- *    matches (exact over prefix over infix over typo) score higher, and `weight` is added
- *    last. The tiers are {@link SEARCH_TIER_POINTS} points apart, so a weight below that reorders within
- *    a tier and never across one.
- *  - Caps each group (`groupLimit`, default 8) after ranking, so one broad group cannot
- *    push every other group off the list.
- */
-
-/** One searchable thing: a page, an action, a record, a settings row. */
-export interface SearchEntry {
-  /** Unique across the entries handed to one index. */
-  id: string;
-  /** What the row says, and what ranks highest. */
-  title: string;
-  /** Other words or phrases that should find it — synonyms, a translated name, tags.
-   *  Matched like the title, ranked below it. */
-  keywords?: readonly string[];
-  /** Longer text, matched last and ranked lowest. Not shown in the row. */
-  description?: string;
-  /** Heading the row is grouped under in the palette. */
-  group?: string;
-  /** Secondary text on the row's trailing side (the page it lives on, an amount). */
-  hint?: string;
-  /** Leading icon. */
-  icon?: ReactNode;
-  /** Where it leads — the app's own path, handed to `GlobalSearch`'s `navigate`. */
-  href?: string;
-  /** Run instead of navigating. Wins over `href` for a plain click and ↵; `href` still
-   *  makes the row a real link for a middle-/⌘-click. */
-  onSelect?: () => void;
-  /** Added to the score. Below {@link SEARCH_TIER_POINTS} it reorders within a tier. */
-  weight?: number;
-  /** Masks the row for session replay (see `CommandItem.redact`). */
-  redact?: boolean;
-}
-
-export type SearchMatchField = "title" | "keywords" | "description";
-
-export interface SearchHit<E extends SearchEntry = SearchEntry> {
-  entry: E;
-  score: number;
-  /** The weakest field any query word had to be found in. */
-  field: SearchMatchField;
-}
-
-export interface SearchIndexOptions {
-  /** Hits kept per `group` after ranking. Default 8; `Infinity` for no cap. */
-  groupLimit?: number;
-  /** Hits kept in total. Default: no cap beyond `groupLimit`. */
-  limit?: number;
-  /** Shortest query word allowed an edit-distance-1 match. Default 5 — below that a
-   *  single typo is a different word ("cat" / "car"). */
-  typoMinLength?: number;
-  /** Shortest query word matched INSIDE an entry word. Default 4. */
-  infixMinLength?: number;
-}
-
-export interface SearchIndex<E extends SearchEntry = SearchEntry> {
-  /** Ranked hits for `query`; an empty query returns none. */
-  search: (query: string) => SearchHit<E>[];
-  readonly entries: readonly E[];
-}
-
-/** Points between two ranking tiers. */
-export const SEARCH_TIER_POINTS = 1000;
-
-const TIERS = {
-  exact: 5,
-  prefix: 4,
-  title: 3,
-  keywords: 2,
-  description: 1,
-} as const;
-
-/** How well one query word matched one entry word — higher is better. */
-const WORD_SCORE = { exact: 40, prefix: 30, infix: 15, typo: 10 } as const;
-/** How much the field a word matched in is worth, multiplied with the above. */
-const FIELD_FACTOR: Record<SearchMatchField, number> = { title: 3, keywords: 2, description: 1 };
-
-/**
- * Lower case, accents off, punctuation to spaces — the form both sides are compared in.
- * Exported so an app can normalise its own keys the same way. The fold is every kit
- * list's {@link foldForSearch} (DUP-5, refactor audit 2026-10); the index adds the
- * punctuation-to-space step its word split needs.
- */
-export function normalizeSearchText(text: string): string {
-  return foldForSearch(text)
-    .replace(/[^\p{L}\p{N}]+/gu, " ")
-    .trim();
-}
-
-/** The words of a text, camelCase split too: "DateRangePicker" → daterangepicker, date,
- *  range, picker. The joined word stays so "daterange" still prefixes it. */
-function words(text: string): string[] {
-  const out = new Set<string>();
-  // Split camelCase BEFORE lower-casing, or the boundaries are gone.
-  const spaced = text.replace(/(\p{Ll}|\p{N})(\p{Lu})/gu, "$1 $2").replace(/(\p{Lu})(\p{Lu}\p{Ll})/gu, "$1 $2");
-  for (const w of normalizeSearchText(text).split(" ")) if (w) out.add(w);
-  for (const w of normalizeSearchText(spaced).split(" ")) if (w) out.add(w);
-  return [...out];
-}
-
-/** Restricted Damerau–Levenshtein distance, early-exiting once it must exceed `max`. */
-function withinDistance(a: string, b: string, max: number): boolean {
-  if (Math.abs(a.length - b.length) > max) return false;
-  if (a === b) return true;
-  const n = a.length;
-  const m = b.length;
-  let prev2: number[] = [];
-  let prev = Array.from({ length: m + 1 }, (_, j) => j);
-  for (let i = 1; i <= n; i++) {
-    const cur = [i];
-    let rowMin = i;
-    for (let j = 1; j <= m; j++) {
-      const cost = a[i - 1] === b[j - 1] ? 0 : 1;
-      let v = Math.min(prev[j] + 1, cur[j - 1] + 1, prev[j - 1] + cost);
-      if (i > 1 && j > 1 && a[i - 1] === b[j - 2] && a[i - 2] === b[j - 1]) {
-        v = Math.min(v, prev2[j - 2] + 1);
-      }
-      cur.push(v);
-      if (v < rowMin) rowMin = v;
-    }
-    if (rowMin > max) return false;
-    prev2 = prev;
-    prev = cur;
-  }
-  return prev[m] <= max;
-}
-
-type WordKind = keyof typeof WORD_SCORE;
-
-function matchWord(
-  q: string,
-  word: string,
-  opts: Required<Pick<SearchIndexOptions, "typoMinLength" | "infixMinLength">>,
-): WordKind | null {
-  if (word === q) return "exact";
-  if (word.startsWith(q)) return "prefix";
-  if (q.length >= opts.infixMinLength && word.includes(q)) return "infix";
-  if (q.length >= opts.typoMinLength) {
-    // The whole word, or the word's start as long as the query (a typo in a prefix:
-    // "calender" is one edit from "calendar", the start of "calendars").
-    if (withinDistance(q, word, 1)) return "typo";
-    if (word.length > q.length && withinDistance(q, word.slice(0, q.length), 1)) return "typo";
-  }
-  return null;
-}
-
-interface Prepared<E> {
-  entry: E;
-  title: string;
-  titleCompact: string;
-  fields: Array<[SearchMatchField, string[]]>;
-}
-
-/**
- * Build an index over `entries`. Normalisation happens once here, so `search` is a scan
- * over prepared words — a few thousand entries per keystroke is nothing.
- */
-export function createSearchIndex<E extends SearchEntry>(
-  entries: readonly E[],
-  options: SearchIndexOptions = {},
-): SearchIndex<E> {
-  const { groupLimit = 8, limit = Infinity, typoMinLength = 5, infixMinLength = 4 } = options;
-  const wordOpts = { typoMinLength, infixMinLength };
-  const prepared: Prepared<E>[] = entries.map((entry) => {
-    const title = normalizeSearchText(entry.title);
-    return {
-      entry,
-      title,
-      titleCompact: title.replace(/ /g, ""),
-      fields: [
-        ["title", words(entry.title)],
-        ["keywords", (entry.keywords ?? []).flatMap(words)],
-        ["description", entry.description ? words(entry.description) : []],
-      ],
-    };
-  });
-
-  const search = (query: string): SearchHit<E>[] => {
-    const q = normalizeSearchText(query);
-    if (!q) return [];
-    const qWords = [...new Set(q.split(" "))];
-    const qCompact = q.replace(/ /g, "");
-    const hits: SearchHit<E>[] = [];
-
-    for (const p of prepared) {
-      let quality = 0;
-      let weakest: SearchMatchField = "title";
-      let ok = true;
-      for (const qw of qWords) {
-        let best = 0;
-        let bestField: SearchMatchField | null = null;
-        for (const [field, fieldWords] of p.fields) {
-          for (const w of fieldWords) {
-            const kind = matchWord(qw, w, wordOpts);
-            if (!kind) continue;
-            const s = WORD_SCORE[kind] * FIELD_FACTOR[field];
-            if (s > best) {
-              best = s;
-              bestField = field;
-            }
-          }
-        }
-        if (!bestField) {
-          ok = false;
-          break;
-        }
-        quality += best;
-        if (FIELD_FACTOR[bestField] < FIELD_FACTOR[weakest]) weakest = bestField;
-      }
-      if (!ok) continue;
-
-      let tier: number = TIERS[weakest];
-      if (p.title === q || p.titleCompact === qCompact) tier = TIERS.exact;
-      else if (
-        p.title.startsWith(q) ||
-        p.titleCompact.startsWith(qCompact) ||
-        // The whole title, mistyped once ("Tooltp") — as good as a prefix, not exact.
-        (qCompact.length >= typoMinLength && withinDistance(qCompact, p.titleCompact, 1))
-      ) {
-        tier = TIERS.prefix;
-      }
-      // Within a tier: how well the words matched (≤ 120 each, averaged so a long query
-      // cannot climb by word count), and how much of the title the query covers — so
-      // "Tooltip" beats "Popovers, menus & tooltips" for the same one-word match.
-      const coverage = Math.min(1, qCompact.length / Math.max(1, p.titleCompact.length)) * 40;
-      const score =
-        tier * SEARCH_TIER_POINTS +
-        Math.min(quality / qWords.length + coverage, SEARCH_TIER_POINTS / 2 - 1) +
-        (p.entry.weight ?? 0);
-      hits.push({ entry: p.entry, score, field: weakest });
-    }
-
-    hits.sort((a, b) => b.score - a.score || a.entry.title.localeCompare(b.entry.title));
-    return capByGroup(hits, groupLimit, limit);
-  };
-
-  return { search, entries };
-}
-
-function capByGroup<E extends SearchEntry>(hits: SearchHit<E>[], groupLimit: number, limit: number): SearchHit<E>[] {
-  const perGroup = new Map<string, number>();
-  const out: SearchHit<E>[] = [];
-  for (const hit of hits) {
-    if (out.length >= limit) break;
-    const g = hit.entry.group ?? "";
-    const n = perGroup.get(g) ?? 0;
-    if (n >= groupLimit) continue;
-    perGroup.set(g, n + 1);
-    out.push(hit);
-  }
-  return out;
-}

package/src/search/use-command-key.ts

@@ -1,23 +0,0 @@
-import { useHotkey, type UseHotkeyOptions } from "../hooks/use-hotkey";
-
-/**
- * Registers a global ⌘K / Ctrl-K shortcut that calls `onOpen`.
- *
- * Its own module since 0.34 (MOD-1, refactor audit 2026-10): `GlobalSearch` listens for
- * the shortcut from the moment the top bar mounts but loads the palette only when it is
- * first opened, and a hook imported from command-palette.tsx would have brought the
- * palette along with it. Still exported from command-palette.tsx, where it always was.
- *
- * `useHotkey("Mod+K")` since 0.52 (refactor audit 2026-10-30, DUP-12): Cmd+K on a Mac,
- * Ctrl+K elsewhere, with no other modifier, once per press. Hand-rolled, it took Ctrl+K
- * on a Mac as well — a text field's kill-line there — and Ctrl+Shift+K, Cmd+Alt+K and
- * every repeat of a held key. It still fires from inside a text field: the palette is
- * where a search starts, whatever has focus.
- *
- * `enabled: false` lets Mod+K go (0.52 code review, global-search.tsx): `GlobalSearch
- * shortcut={false}` passed a no-op, and the listener still cancelled every Mod+K — the
- * browser's own Ctrl+K and any other handler on the page that checks `defaultPrevented`.
- */
-export function useCommandKey(onOpen: () => void, options: Pick<UseHotkeyOptions, "enabled"> = {}): void {
-  useHotkey("Mod+K", () => onOpen(), { allowInInputs: true, enabled: options.enabled });
-}

package/src/search.ts

@@ -1,14 +0,0 @@
-// `@eifi1/ui-kit/search` — the command palette / global search.
-// A re-slicing of the main barrel, not a new API.
-export * from "./search/command-palette";
-// Named, not `*`: 0.53 took `SEARCH_TIER_POINTS` and `normalizeSearchText` off the surface
-// (deprecated in 0.52, refactor audit 2026-10-30, API-4); the index keeps them.
-export {
-  createSearchIndex,
-  type SearchEntry,
-  type SearchMatchField,
-  type SearchHit,
-  type SearchIndexOptions,
-  type SearchIndex,
-} from "./search/search-index";
-export * from "./search/global-search";

package/src/settings/device-reset-setting-labels.ts

@@ -1,20 +0,0 @@
-// The English words of ./device-reset-setting, 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). ./device-reset-setting
-// re-exports them.
-
-import type { DeviceResetLabels } from "./device-reset-setting";
-
-/** docs/settings-harmonization.md §11.3, word for word. */
-export const DEFAULT_DEVICE_RESET_LABELS: DeviceResetLabels = {
-  title: "Reset this device",
-  description:
-    "Puts this device's appearance, and the way its tables and panels were left, back to the defaults. Your account, your data and your sign-in are not touched.",
-  action: "Reset this device's settings",
-  confirmTitle: "Reset this device's settings?",
-  confirmBody:
-    "Theme, colours, text size, contrast and language go back to their defaults here, and tables and panels open as they first did. Where your account has a language, a text size or a contrast, this device follows it again. Your account and your other devices stay as they are.",
-  confirmAction: "Reset",
-  done: "This device's settings are back to their defaults.",
-  keywords: "reset defaults device restore appearance tables layout",
-};

package/src/settings/device-reset-setting.tsx

@@ -1,116 +0,0 @@
-import type { ReactNode } from "react";
-
-import { useKitLabels, type LabelOverride } from "../i18n/kit-labels";
-import { resetDeviceSettings } from "../lib/device-settings";
-import { Button } from "../components/button";
-import { useConfirm } from "../components/confirm-dialog";
-import { toast } from "../components/toast";
-import { SettingsSection, type SettingsSectionProps } from "./settings-section";
-import { DEFAULT_DEVICE_RESET_LABELS } from "./device-reset-setting-labels";
-
-/* ── Labels ──────────────────────────────────────────────────────────────── */
-
-/** Every string {@link DeviceResetSetting} renders — the `deviceReset` namespace of
- *  `<UiKitProvider labels>`, overridable per instance through `labels`
- *  (docs/settings-harmonization.md §11.3). The confirm's Cancel is `confirmDialog.cancel`. */
-export interface DeviceResetLabels {
-  /** The card's title, and the app's catalogue entry's. */
-  title: string;
-  /** The line under it: what goes back, and that the account is not touched. */
-  description: string;
-  /** The button that asks first. */
-  action: string;
-  /** The question it asks. */
-  confirmTitle: string;
-  /** What goes, what follows the account again, and what stays. */
-  confirmBody: string;
-  /** The button that answers it. */
-  confirmAction: string;
-  /** The toast once it is done. */
-  done: string;
-  /** For the app's catalogue entry (`keywords`); the card never reads it. */
-  keywords: string;
-}
-
-// Defined in ./device-reset-setting-labels, which holds no component code.
-export { DEFAULT_DEVICE_RESET_LABELS };
-
-/* ── The card ────────────────────────────────────────────────────────────── */
-
-/** The card's DOM id: its catalogue entry's `anchor`, the `?focus=` target. */
-export const DEVICE_RESET_ANCHOR = "settings-device-reset";
-
-// `onReset` is the card's own: the DOM's form-reset handler never fires on a div.
-export interface DeviceResetSettingProps extends Omit<
-  SettingsSectionProps,
-  "anchor" | "title" | "description" | "children" | "onReset"
-> {
-  /** The app's sentence after the kit's description: what of its own goes back, and what
-   *  stays (keksdose: the date format, the feature set and the gestures go; presentation
-   *  mode and the home position stay). */
-  description?: ReactNode;
-  labels?: LabelOverride<DeviceResetLabels>;
-  /** Runs after the reset and before the toast, with the keys reset or removed. */
-  onReset?: (keys: string[]) => void;
-}
-
-/**
- * "Reset this device's settings" (docs/settings-harmonization.md §11): the LAST card of
- * the appearance group. It puts this device's appearance — theme, palette, language, text
- * size, contrast and the app's own appearance choices — and its views — table views, the
- * sidebar, folded groups, saved filters — back to what a new device gets, through
- * {@link resetDeviceSettings}. The account, the sign-in, the session and anything waiting
- * to be sent are never touched: they never join the registry.
- *
- * - **A confirm, not an undo** (§11.2 decision 9): `useConfirm` in the neutral tone,
- *   then a toast. An app mounts a `ConfirmProvider` and a `Toaster` already.
- * - **Not a commit**: nothing is written to the account, so a demo or a lapsed plan's
- *   write lock does not disable it (decision 3).
- * - **Live, no reload** (decision 10): each registered store resets through its own
- *   setter; the card stays where it is.
- *
- * The app adds the catalogue entry, `{ id, group: "appearance", anchor: DEVICE_RESET_ANCHOR,
- * title, keywords }` (the id in its catalogue's own style, e.g. `device_reset` or
- * `deviceReset`; `title` and `keywords` from these labels), last in its appearance group:
- * inside a `SettingsLayout`, `SettingsSection` throws in development without it.
- */
-export function DeviceResetSetting({ description, labels: labelsProp, onReset, ...rest }: DeviceResetSettingProps) {
-  const labels = useKitLabels("deviceReset", DEFAULT_DEVICE_RESET_LABELS, labelsProp);
-  const confirm = useConfirm();
-
-  const reset = async () => {
-    const ok = await confirm({
-      title: labels.confirmTitle,
-      body: labels.confirmBody,
-      confirmLabel: labels.confirmAction,
-      tone: "neutral",
-    });
-    if (!ok) return;
-    const keys = resetDeviceSettings();
-    onReset?.(keys);
-    toast.success(labels.done);
-  };
-
-  return (
-    <SettingsSection
-      {...rest}
-      anchor={DEVICE_RESET_ANCHOR}
-      title={labels.title}
-      description={
-        description != null ? (
-          <>
-            {labels.description} {description}
-          </>
-        ) : (
-          labels.description
-        )
-      }
-    >
-      <div>
-        <Button variant="secondary" onClick={() => void reset()}>
-          {labels.action}
-        </Button>
-      </div>
-    </SettingsSection>
-  );
-}

package/src/settings/settings-card-classes.ts

@@ -1,11 +0,0 @@
-/**
- * The settings cards' type scale, PasskeysSetting's: a small title and a muted line.
- * Every kit setting card draws it — the account cards, `SettingsSection` and the
- * `SettingsCardTitle` they share — so it lives with the card look, in settings/. It was in
- * account/account-parts.ts, which made settings/ import account/ and account/ import
- * settings/ (MOD-8, refactor audit 2026-10); account-parts re-exports it.
- *
- * @internal Not part of the barrel.
- */
-export const CARD_TITLE_CLASS = "text-sm font-medium";
-export const CARD_DESCRIPTION_CLASS = "text-xs text-muted";

package/src/settings/settings-catalogue.ts

@@ -1,150 +0,0 @@
-import type { ReactNode } from "react";
-import type { SearchEntry } from "../search/search-index";
-
-/**
- * The settings catalogue (docs/settings-harmonization.md §4.1), lifted from keksdose's
- * `settings-index.ts`: the groups a settings page is split into, and one entry per
- * SETTING — not per card — so a search for "quiet hours" finds the field inside the
- * notifications card. One list feeds the sidebar, the phone list, the in-page search and
- * ⌘K ({@link settingsSearchEntries}); keksdose's page and its palette drifted when they
- * had one each.
- *
- * The kit resolves no words: `title`, `help` and `keywords` arrive translated (an app's
- * own, or the core groups' from `DEFAULT_SETTINGS_LABELS.groups`).
- */
-
-/** One group of the page: a sidebar row on a desktop, a list row on a phone (§3.2, §3.3). */
-export interface SettingsGroup<G extends string = string> {
-  /** The path segment, `/settings/<id>`: lowercase, a–z and "-". */
-  id: G;
-  /** The row's icon — a lucide icon at the row's size is sized by the row. */
-  icon: ReactNode;
-  /** The group's name: the sidebar row, the heading over its cards, the phone list. */
-  title: string;
-  /** One line under the heading and in the phone list, where it is cut to one line. */
-  help: string;
-  /**
-   * 0.48 (keksdose live #450): a count or a mark drawn on the group's ROW — at the end of
-   * its desktop sidebar row and before the chevron of its phone list row — never on the
-   * heading over its cards. The admin area's waiting work: `<AdminWaitingBadge count={n} />`
-   * (nothing for 0), so the account menu's badge leads to the section that holds it. It
-   * sits inside the row's link and is read with its name, so say what the number is (the
-   * waiting pill does: "3, 3 waiting"). While the page is searched the sidebar shows the
-   * hit count in its place. Default: none.
-   */
-  badge?: ReactNode;
-  /**
-   * `false` hides the group: no row, no hits, and its path acts as an unknown one — it
-   * lands on the default group (desktop) or the list (phone), never on a 404 (§3.1).
-   * kastlan's `/admin/billing` while billing is off. Default: visible.
-   */
-  visible?: boolean;
-  /**
-   * 0.43: the group shows with no visible entry — a page of its own rather than of setting
-   * cards (the admin area's Overview, whose tiles are no settings; `adminSections` sets
-   * it). `visible: false` still hides it. Default: a group shows only with an entry once
-   * `entries` are given (§4.1).
-   */
-  standalone?: boolean;
-}
-
-/** One setting, and the card that holds it (§4.1). */
-export interface SettingsEntry<G extends string = string> {
-  /** Unique within the catalogue. */
-  id: string;
-  /** The group whose page shows the card. */
-  group: G;
-  /** The card's DOM id, unique on the page — the `?focus=` target. Several entries may
-   *  share one: a card that holds four settings has four entries. */
-  anchor: string;
-  /** What a search hit says. */
-  title: string;
-  /** Localized, space-separated words people type that the title does not contain
-   *  ("dark night" for the theme, "2fa totp" for two-factor). Never shown. */
-  keywords?: string;
-  /**
-   * `false` drops the entry from the page's search and ⌘K. A group whose entries are
-   * ALL hidden is hidden with them (§4.1): a demo session marks every card it is refused
-   * (passkeys, 2FA, export, deletion …) and so never sees a page of cards that each
-   * answer 403. Default: visible.
-   */
-  visible?: boolean;
-}
-
-/**
- * The groups that show, in their order: not `visible: false`, and — when `entries` is
- * given — holding at least one visible entry (§4.1: Kurvenschmiede's notifications group
- * stays hidden until it has a card) or `standalone` (0.43). Without `entries` only the
- * groups' own flag counts.
- */
-export function visibleSettingsGroups<G extends string>(
-  groups: readonly SettingsGroup<G>[],
-  entries?: readonly SettingsEntry<G>[],
-): SettingsGroup<G>[] {
-  if (!entries) return groups.filter((g) => g.visible !== false);
-  const filled = new Set<G>();
-  for (const e of entries) if (e.visible !== false) filled.add(e.group);
-  return groups.filter((g) => g.visible !== false && (g.standalone === true || filled.has(g.id)));
-}
-
-/** The visible entries of the visible groups — what search may find. */
-export function visibleSettingsEntries<G extends string>(
-  groups: readonly SettingsGroup<G>[],
-  entries: readonly SettingsEntry<G>[],
-): SettingsEntry<G>[] {
-  const shown = new Set(visibleSettingsGroups(groups, entries).map((g) => g.id));
-  return entries.filter((e) => e.visible !== false && shown.has(e.group));
-}
-
-/** `basePath` without a trailing slash: "/settings/" and "/settings" are one page. */
-export function normalizeSettingsBase(basePath: string): string {
-  const trimmed = basePath.replace(/\/+$/, "");
-  return trimmed.startsWith("/") || trimmed === "" ? trimmed : `/${trimmed}`;
-}
-
-/** `/settings/<group>`, and `?focus=<anchor>` when a card is named (§3.4). */
-export function settingsHref(basePath: string, group: string, anchor?: string): string {
-  const path = `${normalizeSettingsBase(basePath)}/${group}`;
-  return anchor ? `${path}?focus=${encodeURIComponent(anchor)}` : path;
-}
-
-/** "dark  night" → ["dark", "night"]. */
-export function settingsKeywords(keywords: string | undefined): string[] {
-  return keywords ? keywords.split(/\s+/).filter(Boolean) : [];
-}
-
-export interface SettingsSearchEntriesOptions {
-  /** `/settings` or `/admin` — the hits link to `<basePath>/<group>?focus=<anchor>`. */
-  basePath: string;
-}
-
-/**
- * The catalogue as {@link GlobalSearch} entries (§3.4): each visible setting, under its
- * group's name as the palette's section, linking to `/settings/<group>?focus=<anchor>` —
- * the same link the page's own search hit is, so ⌘K, a tour and a mail all land the
- * same way (§3.5). The group's name is a keyword too, as on the page: "security" lists
- * the security group's settings.
- *
- * Ids are prefixed with the base path ("settings:theme", "admin:users") so a palette
- * that also holds pages and actions keeps them unique.
- */
-export function settingsSearchEntries<G extends string>(
-  groups: readonly SettingsGroup<G>[],
-  entries: readonly SettingsEntry<G>[],
-  options: SettingsSearchEntriesOptions,
-): SearchEntry[] {
-  const base = normalizeSettingsBase(options.basePath);
-  const prefix = base.replace(/^\//, "").replace(/\//g, ":") || "settings";
-  const byId = new Map(visibleSettingsGroups(groups, entries).map((g) => [g.id, g]));
-  return visibleSettingsEntries(groups, entries).map((e) => {
-    const group = byId.get(e.group)!;
-    return {
-      id: `${prefix}:${e.id}`,
-      title: e.title,
-      keywords: [group.title, ...settingsKeywords(e.keywords)],
-      group: group.title,
-      icon: group.icon,
-      href: settingsHref(base, e.group, e.anchor),
-    };
-  });
-}

package/src/settings/settings-context.ts

@@ -1,33 +0,0 @@
-import { createContext, useContext } from "react";
-import type { SettingsHeadingTag } from "./settings-heading";
-
-/**
- * What {@link SettingsLayout} hands the cards it renders (docs/settings-harmonization.md
- * §3.1, §3.7). Router-free on purpose, so `SettingsSection` and an app's cards can read
- * it without importing the layout.
- */
-export interface SettingsLayoutContextValue {
-  /** `/settings` or `/admin`, without a trailing slash. */
-  basePath: string;
-  /** The group on screen; `null` on a phone's list. */
-  group: string | null;
-  /** The path segment after the group — the surface a card owns (keksdose's swipe card). */
-  sub: string | null;
-  /**
-   * Select the card's sub-surface: `/settings/<group>/<sub>`, or the group alone with
-   * `null`. A replace, keeping the query and the history marker: switching a tab inside a
-   * card is not a place to go back to. The card never builds the path itself (§3.1).
-   */
-  selectSub: (sub: string | null) => void;
-  /** The level the cards' titles are at: `h3` on a desktop, `h2` on a phone. */
-  headingLevel: SettingsHeadingTag;
-  /** Whether the catalogue has an entry with this anchor — `SettingsSection`'s check. */
-  hasAnchor: (anchor: string) => boolean;
-}
-
-export const SettingsLayoutContext = createContext<SettingsLayoutContextValue | null>(null);
-
-/** The {@link SettingsLayout} around this card, or `null` outside one. */
-export function useSettingsLayout(): SettingsLayoutContextValue | null {
-  return useContext(SettingsLayoutContext);
-}