@eifi1/ui-kit 0.54.0 → 0.56.0

package/src/lib/iban.ts

@@ -1,251 +0,0 @@
-/**
- * IBAN helpers — ISO 13616 — for kastlan (supplier and customer bank details, the
- * Swiss QR-bill) and keksdose (the accounts behind a household's transfers).
- *
- * Both apps validated an IBAN the same partial way: a regex for the shape, sometimes a
- * mod-97, never the per-country length — so a Swiss IBAN with a digit missing passed
- * as long as the shorter string happened to sum right, and "CH" followed by 22
- * characters (a German length) was accepted as Swiss. And kastlan's QR-bill needs a
- * second distinction neither had: a **QR-IBAN** (the institution id at positions 5–9 is
- * 30000–31999) is the only account a QR-bill with a QR reference can be paid to, and it
- * cannot receive an ordinary transfer — so a regular IBAN typed where a QR-IBAN is
- * needed, or the other way round, is a payment that bounces weeks later.
- *
- * Everything here works on the **electronic format** (no spaces, upper case), which is
- * what to store; {@link formatIban} is the paper format, which is what to show.
- *
- * Validation is the registry's two rules, nothing more: the length for the country and
- * the mod-97 check digits. It does not check each country's BBAN layout (which places
- * hold letters), nor whether the bank exists — a checksum catches a typo, not a closed
- * account.
- */
-
-/**
- * The IBAN length for each country in the SWIFT IBAN Registry (2025 edition) — the
- * whole string, country code and check digits included.
- *
- * A country that is not in the table does not issue IBANs, so {@link isValidIban}
- * refuses it ("XX" is a typo, not an exotic bank). Territories that use another
- * country's code (Åland under FI, Guernsey under GB, the French overseas departments
- * under FR) are covered by that code, as the registry lists them.
- */
-export const IBAN_LENGTHS: Readonly<Record<string, number>> = Object.freeze({
-  AD: 24,
-  AE: 23,
-  AL: 28,
-  AT: 20,
-  AZ: 28,
-  BA: 20,
-  BE: 16,
-  BG: 22,
-  BH: 22,
-  BI: 27,
-  BR: 29,
-  BY: 28,
-  CH: 21,
-  CR: 22,
-  CY: 28,
-  CZ: 24,
-  DE: 22,
-  DJ: 27,
-  DK: 18,
-  DO: 28,
-  EE: 20,
-  EG: 29,
-  ES: 24,
-  FI: 18,
-  FK: 18,
-  FO: 18,
-  FR: 27,
-  GB: 22,
-  GE: 22,
-  GI: 23,
-  GL: 18,
-  GR: 27,
-  GT: 28,
-  HN: 28,
-  HR: 21,
-  HU: 28,
-  IE: 22,
-  IL: 23,
-  IQ: 23,
-  IS: 26,
-  IT: 27,
-  JO: 30,
-  KW: 30,
-  KZ: 20,
-  LB: 28,
-  LC: 32,
-  LI: 21,
-  LT: 20,
-  LU: 20,
-  LV: 21,
-  LY: 25,
-  MC: 27,
-  MD: 24,
-  ME: 22,
-  MK: 19,
-  MN: 20,
-  MR: 27,
-  MT: 31,
-  MU: 30,
-  NI: 28,
-  NL: 18,
-  NO: 15,
-  OM: 23,
-  PK: 24,
-  PL: 28,
-  PS: 29,
-  PT: 25,
-  QA: 29,
-  RO: 24,
-  RS: 22,
-  RU: 33,
-  SA: 24,
-  SC: 31,
-  SD: 18,
-  SE: 24,
-  SI: 19,
-  SK: 24,
-  SM: 27,
-  SO: 23,
-  ST: 25,
-  SV: 28,
-  TL: 23,
-  TN: 24,
-  TR: 26,
-  UA: 29,
-  VA: 22,
-  VG: 24,
-  XK: 20,
-  YE: 30,
-});
-
-/**
- * Which kind of IBAN a field accepts. `"any"`: every valid IBAN. `"qr"`: only a
- * QR-IBAN (a QR-bill with a QR reference — kastlan's payment slips). `"plain"`: every
- * valid IBAN EXCEPT a QR-IBAN (an account for ordinary transfers, which a QR-IBAN
- * cannot receive).
- */
-export type IbanKind = "qr" | "plain" | "any";
-
-/**
- * Why a value is not the IBAN a field wants, most fundamental first:
- *
- *  - `"format"` — it does not start with a two-letter country code and two digits;
- *  - `"country"` — the first two letters are not a country in {@link IBAN_LENGTHS};
- *  - `"length"` — the wrong number of characters for that country;
- *  - `"checksum"` — the mod-97 check digits do not match (a typo, a swapped pair);
- *  - `"qrRequired"` — a valid IBAN, but not a QR-IBAN where `kind="qr"` needs one;
- *  - `"qrNotAllowed"` — a valid QR-IBAN where `kind="plain"` refuses one.
- */
-export type IbanProblem = "format" | "country" | "length" | "checksum" | "qrRequired" | "qrNotAllowed";
-
-/**
- * The electronic format: every character that is not a letter or a digit dropped, the
- * letters in upper case. Spaces, non-breaking spaces, hyphens and dots — what a paste
- * from an invoice, a PDF or an e-banking screen carries — all go.
- *
- * A leading `"IBAN"` (the paper format's label: "IBAN CH56 …") is dropped too, but only
- * in front of a country code and check digits, so typing the word does not make it
- * vanish under the caret.
- */
-export function compactIban(value: string): string {
-  const compact = value.replace(/[^0-9A-Za-z]/g, "").toUpperCase();
-  return /^IBAN[A-Z]{2}\d{2}/.test(compact) ? compact.slice(4) : compact;
-}
-
-/**
- * The paper format: {@link compactIban}, then groups of four separated by a single
- * space ("CH09 0000 0000 0000 0000 1"). The last group is whatever is left over.
- */
-export function formatIban(value: string): string {
-  return compactIban(value).replace(/(.{4})(?=.)/g, "$1 ");
-}
-
-/** The remainder of a long digit string modulo 97, a few digits at a time so it never
- *  leaves the safe-integer range — ISO 7064 MOD 97-10 without a BigInt. */
-function mod97(digits: string): number {
-  let rest = 0;
-  for (let i = 0; i < digits.length; i += 7) {
-    rest = Number(`${rest}${digits.slice(i, i + 7)}`) % 97;
-  }
-  return rest;
-}
-
-/** Letters to their two-digit numbers (A = 10 … Z = 35), digits as they are. */
-function expandLetters(value: string): string {
-  return value.replace(/[A-Z]/g, (c) => String(c.charCodeAt(0) - 55));
-}
-
-/**
- * The two check digits for a country code and a BBAN (the account part after them):
- * `98 − ((BBAN + country + "00") mod 97)`, letters expanded A = 10 … Z = 35.
- *
- * What an app needs to BUILD an IBAN — a test fixture, a demo, a migration that
- * assembles one from a clearing number and an account number — rather than to check
- * one. Both arguments are compacted first.
- */
-export function ibanCheckDigits(country: string, bban: string): string {
-  const rearranged = `${compactIban(bban)}${compactIban(country)}00`;
-  const check = 98 - mod97(expandLetters(rearranged));
-  return String(check).padStart(2, "0");
-}
-
-/**
- * The first thing wrong with `value` as an IBAN of `kind`, or `null` when it is one.
- * The value is compacted first, so the paper format is accepted. An empty value is
- * `"format"`: whether a field may be left empty is the form's rule, not the IBAN's.
- */
-export function ibanProblem(value: string, kind: IbanKind = "any"): IbanProblem | null {
-  const iban = compactIban(value);
-  if (!/^[A-Z]{2}\d{2}/.test(iban)) return "format";
-  const expected = IBAN_LENGTHS[iban.slice(0, 2)];
-  if (expected === undefined) return "country";
-  if (iban.length !== expected) return "length";
-  // 00, 01 and 99 are never computed (98 − r lies in 2…98), but 01 ≡ 98 mod 97 and
-  // would otherwise pass the remainder test below — ISO 7064 rules them out.
-  const check = iban.slice(2, 4);
-  if (check === "00" || check === "01" || check === "99") return "checksum";
-  if (mod97(expandLetters(`${iban.slice(4)}${iban.slice(0, 4)}`)) !== 1) return "checksum";
-  if (kind === "any") return null;
-  const qr = qrIid(iban);
-  if (kind === "qr" && !qr) return "qrRequired";
-  if (kind === "plain" && qr) return "qrNotAllowed";
-  return null;
-}
-
-/**
- * Whether `value` is a valid IBAN: a registry country, that country's length, and
- * matching mod-97 check digits. Spaces and lower case are fine (see
- * {@link compactIban}); what to store is the compact form.
- */
-export function isValidIban(value: string): boolean {
-  return ibanProblem(value) === null;
-}
-
-/** A CH/LI IBAN whose institution id (positions 5–9) is in the QR range. Structure
- *  only — the caller has checked or will check the rest. */
-function qrIid(iban: string): boolean {
-  const country = iban.slice(0, 2);
-  if (country !== "CH" && country !== "LI") return false;
-  const iid = iban.slice(4, 9);
-  if (!/^\d{5}$/.test(iid)) return false;
-  const n = Number(iid);
-  return n >= 30000 && n <= 31999;
-}
-
-/**
- * Whether `value` is a valid **QR-IBAN**: a valid Swiss or Liechtenstein IBAN whose
- * institution id — positions 5 to 9, the QR-IID — lies in 30000–31999 (SIX, Swiss
- * Implementation Guidelines for the QR-bill).
- *
- * The distinction is not cosmetic (kastlan): a QR-bill with a QR reference can only be
- * paid to a QR-IBAN, and a QR-IBAN can receive nothing else — so an app that prints
- * payment slips needs one, and an app that stores an account for ordinary transfers
- * must not take one.
- */
-export function isQrIban(value: string): boolean {
-  const iban = compactIban(value);
-  return ibanProblem(iban) === null && qrIid(iban);
-}

package/src/lib/ime.ts

@@ -1,24 +0,0 @@
-import type { KeyboardEvent as ReactKeyboardEvent } from "react";
-
-/**
- * Whether a key press belongs to an IME composition (Chinese, Japanese, Korean input):
- * `isComposing` while the composition is open, or `keyCode` 229, which is how Safari
- * reports the key that ENDED one — its keydown arrives after `compositionend`, with
- * `isComposing` already false (the note in `feedback-thread.tsx`). Takes a React event
- * or a native one.
- */
-export function isComposing(e: KeyboardEvent | ReactKeyboardEvent): boolean {
-  const native = "nativeEvent" in e ? e.nativeEvent : e;
-  return native.isComposing || native.keyCode === 229;
-}
-
-/**
- * An Enter that confirms an IME composition rather than the field (round 0.34 Wave 2,
- * BUG-9). It picks the IME's candidate, so a list must not also take the highlighted
- * option and a field must not submit: every Enter branch in the combobox family returns
- * early on it. Typing 北京 with a pinyin IME is "beijing", then Enter — and that Enter
- * chose option 1, or created a category through `onSubmit` (keksdose's budget cells).
- */
-export function isImeEnter(e: KeyboardEvent | ReactKeyboardEvent): boolean {
-  return e.key === "Enter" && isComposing(e);
-}

package/src/lib/intl-cache.ts

@@ -1,27 +0,0 @@
-/**
- * One `Intl.DateTimeFormat` per locale and option set, for every date the kit prints.
- *
- * Constructing the formatter is the expensive part: keksdose measured 392 ms per click on
- * a 270-row register when each cell built its own (dev#632), and kept its own renderer of
- * the date-format preference because the kit's built one per call (refactor audit
- * 2026-10-30, DUP-2). `lib/format` and `lib/date-format` both format through this one, and
- * since 0.54 `lib/dates`' `formatIsoDate` (keksdose audit follow-up, 2026-11-01).
- *
- * @internal Not part of the barrel — `lib/format` is re-exported whole, so the cache
- * lives apart from it. It imports nothing, which `@eifi1/ui-kit/dates` (no package at
- * all) relies on.
- */
-
-const dateFormatters = new Map<string, Intl.DateTimeFormat>();
-
-/** The cached formatter for `locale` and `options`. Throws as `Intl.DateTimeFormat` does
- *  for a tag it refuses — and caches nothing then. */
-export function dateFormatter(locale: string | undefined, options: Intl.DateTimeFormatOptions): Intl.DateTimeFormat {
-  const key = `${locale ?? ""}|${JSON.stringify(options)}`;
-  let f = dateFormatters.get(key);
-  if (!f) {
-    f = new Intl.DateTimeFormat(locale, options);
-    dateFormatters.set(key, f);
-  }
-  return f;
-}

package/src/lib/iso-day.ts

@@ -1,13 +0,0 @@
-/**
- * The bare ISO calendar day, `"YYYY-MM-DD"` — no time, no zone: the day it names in every
- * zone. `toDate` and `formatDate` (lib/format), the kit's day ladder (`useDayFormatter`,
- * lib/day-format) and the preference's renderers (lib/date-format) each kept a copy of this
- * pattern (0.52 code review, lib/day-format.ts). Were one to learn a new shape (say
- * `YYYY-MM-DDT00:00`) alone, the ladder would ask the provider for a different day than the
- * kit prints. One rule.
- *
- * @internal Not part of the barrel: `lib/format` is re-exported whole, so it lives apart.
- */
-export function isBareIsoDay(value: unknown): value is string {
-  return typeof value === "string" && /^\d{4}-\d{2}-\d{2}$/.test(value);
-}

package/src/lib/lazy-with-fallback.ts

@@ -1,82 +0,0 @@
-import { createContext, createElement, lazy, useCallback, useContext, useLayoutEffect, useState } from "react";
-import type { ComponentType, LazyExoticComponent } from "react";
-
-/** What a {@link lazyWithFallback} fallback is given besides the component's own props. */
-export interface LazyFallbackProps {
-  /** What the import rejected with. Already on `console.error`. */
-  error: unknown;
-  /** Fetch the module again and draw it here if it comes (back online, the deploy's
-   *  new chunk). Call it on the person's next attempt, never at once: offline, a retry
-   *  on mount would fetch in a loop. */
-  retry: () => void;
-}
-
-interface Attempt<P> {
-  Component: LazyExoticComponent<ComponentType<P>>;
-  /** Its import failed and its fallback was drawn: the next mount, or `retry`, takes a
-   *  fresh attempt. Marked when the fallback COMMITS, not when the import rejects: a
-   *  first mount that suspended is thrown away and rendered anew, and an attempt marked
-   *  at the rejection would hand that re-render a fresh import — which fails, and so on. */
-  spent: boolean;
-}
-
-const RetryContext = createContext<() => void>(() => {});
-
-/**
- * `React.lazy` for a module the kit loads late (refactor audit 2026-10, MOD-1: the tour
- * overlay, the search palette, the feedback dialog), where an import that fails — a tab
- * left open across a deploy, a local-first app offline — draws `Fallback` instead of
- * throwing.
- *
- * `React.lazy` keeps what its import settled to, so one failed fetch threw on every render
- * for as long as the component stayed mounted, to the nearest error boundary. All three
- * sit above the routes — in the provider every app mounts, in the top bar — where that
- * boundary is the whole app's: a white page because somebody pressed ⌘K or "Take the
- * tour" (0.52 code review, tour.tsx: the tour's own fix, written by hand with a module-level
- * `let`, made shared here).
- *
- * A failure is logged and the next mount (or the fallback's `retry`) fetches again; a
- * re-render of a mounted fallback does not. `load` resolves to the component itself,
- * through a LITERAL relative dynamic import of its module (as feedback-submit's), so an
- * app's bundler can split it off. Render the result under a `Suspense`, as a lazy
- * component. (No import call is spelled out here: the build's fix-esm-extensions step
- * reads specifiers in the .d.ts comments too, and would try to resolve an example.)
- */
-export function lazyWithFallback<P extends object>(
-  load: () => Promise<ComponentType<P>>,
-  Fallback: ComponentType<P & LazyFallbackProps>,
-): ComponentType<P> {
-  const attempt = (): Attempt<P> => {
-    const made: Attempt<P> = {
-      spent: false,
-      Component: lazy<ComponentType<P>>(() =>
-        load().then(
-          (Loaded) => ({ default: Loaded }),
-          (error: unknown) => {
-            console.error(error);
-            function Failed(props: P) {
-              const retry = useContext(RetryContext);
-              useLayoutEffect(() => {
-                made.spent = true;
-              }, []);
-              return createElement(Fallback, { ...props, error, retry });
-            }
-            return { default: Failed };
-          },
-        ),
-      ),
-    };
-    return made;
-  };
-  let latest = attempt();
-  /** The attempt a new mount takes: the latest, or a fresh one once that has failed. */
-  const take = () => (latest.spent ? (latest = attempt()) : latest);
-
-  function LazyWithFallback(props: P) {
-    // Fixed per mount, so a re-render of a mounted fallback fetches nothing.
-    const [current, setCurrent] = useState(take);
-    const retry = useCallback(() => setCurrent(take), []);
-    return createElement(RetryContext.Provider, { value: retry }, createElement(current.Component, props));
-  }
-  return LazyWithFallback;
-}

package/src/lib/logger.ts

@@ -1,69 +0,0 @@
-import type { StateCreator, StoreMutatorIdentifier } from "zustand";
-
-import { readStored } from "./safe-storage";
-
-/**
- * zustand logging middleware.
- *
- * Logs every state transition (a store "action") to the DevTools console as a
- * single grouped line showing the prev/next state. Enabled in dev (Vite
- * `import.meta.env.DEV`) by default; override at runtime with
- * `localStorage.setItem("store_log", "0")` to silence or `"1"` to force-on in a
- * production build.
- */
-type Logger = <
-  T,
-  Mps extends [StoreMutatorIdentifier, unknown][] = [],
-  Mcs extends [StoreMutatorIdentifier, unknown][] = [],
->(
-  f: StateCreator<T, Mps, Mcs>,
-  name?: string,
-) => StateCreator<T, Mps, Mcs>;
-
-type LoggerImpl = <T>(f: StateCreator<T, [], []>, name?: string) => StateCreator<T, [], []>;
-
-/**
- * Read ONCE, at module scope, not on every `set`.
- *
- * This used to run inside the wrapped `set`, which means a synchronous
- * `localStorage.getItem` on every state transition of every logged store — in
- * production builds too, because the override has to stay readable there by design.
- * The stores this middleware wraps include ones that transition per pointer event.
- *
- * The override cannot change without someone opening devtools and reloading, so
- * once per session is the same behaviour at a fraction of the cost. {@link setStoreLog}
- * keeps the ability to flip it live from a console, which is the only thing the
- * per-call read was actually buying.
- */
-let storeLog: boolean = (() => {
-  const override = readStored("store_log");
-  if (override === "0") return false;
-  if (override === "1") return true;
-  // NOT under vitest. `DEV` distinguishes a dev build from a production one; a test
-  // run is neither, and vitest sets `DEV=true` — so every transition of every logged
-  // store printed a prev/next object into the suite output. Measured on the consumer's
-  // suite: 822 blocks, several thousand lines, in a log whose whole job is to make one
-  // real `console.error` findable. `store_log=1` still forces it on.
-  // Optional-chained because `import.meta.env` is a Vite injection: it is
-  // undefined under plain Node ESM, and this package is published publicly,
-  // so a non-Vite consumer must be able to import it without throwing.
-  return Boolean(import.meta.env?.DEV) && !import.meta.env?.VITEST;
-})();
-
-/** Turn store logging on or off for the rest of the session (devtools escape hatch). */
-export function setStoreLog(enabled: boolean): void {
-  storeLog = enabled;
-}
-
-const loggerImpl: LoggerImpl = (f, name) => (set, get, store) => {
-  const loggedSet = ((...args: unknown[]) => {
-    const prev = get();
-    (set as (...a: unknown[]) => void)(...args);
-    if (storeLog) {
-      console.debug(`%c[store${name ? `:${name}` : ""}]`, "color:#0d9488", { prev, next: get() });
-    }
-  }) as typeof set;
-  return f(loggedSet, get, store);
-};
-
-export const logger = loggerImpl as unknown as Logger;

package/src/lib/minus.ts

@@ -1,50 +0,0 @@
-/**
- * The one minus sign (0.49, KIT-1). `Intl.NumberFormat` writes a negative with the
- * HYPHEN-MINUS (U+002D) in nearly every locale — en, de-CH, fr, it, es, hu, zh — and
- * with the typographic MINUS SIGN (U+2212) in a few (sv, fi). The kit prints U+2212
- * everywhere, as `SignedAmount` always has: it is as wide as "+" and the tabular
- * digits, so a column of signed figures lines up, and it does not break a line the way
- * a hyphen may.
- *
- * `"ascii"` is the other way round, for text a machine reads back — a CSV, the
- * clipboard: every minus becomes U+002D, whatever the locale wrote, so `Number()` and a
- * spreadsheet parse it.
- */
-export type MinusStyle = "typographic" | "ascii";
-
-/** U+2212 MINUS SIGN. */
-export const TYPOGRAPHIC_MINUS = "\u2212";
-
-/** The parts `formatToParts` writes a minus in (the exponent's, under `notation:
- *  "scientific"`, too). */
-const MINUS_PARTS: ReadonlySet<string> = new Set(["minusSign", "exponentMinusSign"]);
-
-/**
- * `formatter.format(value)` with every minus sign in `minus` style. Only the parts
- * `Intl` marks as a minus are touched — a hyphen inside a currency's name
- * ("Bosnia-Herzegovina convertible marks") stays — and only when the text holds the
- * other sign at all, so a positive figure costs no `formatToParts`.
- *
- * Public since 0.50 (the KIT-1 follow-up): an app that keeps its OWN `Intl.NumberFormat`
- * wrapper (a currency with app-specific digits, a quantity) calls it in place of
- * `formatter.format(value)`, so its negatives match the kit's "−". Where the wrapper only
- * re-states `formatMoney` / `formatNumber`, route it through those instead.
- *
- * @example
- *   const eur = new Intl.NumberFormat("en", { style: "currency", currency: "EUR" });
- *   formatWithMinus(eur, -150);          // "−€150.00"
- *   formatWithMinus(eur, -150, "ascii"); // "-€150.00", for a CSV
- */
-export function formatWithMinus(
-  formatter: Intl.NumberFormat,
-  value: number,
-  minus: MinusStyle = "typographic",
-): string {
-  const text = formatter.format(value);
-  const [wanted, other] = minus === "ascii" ? ["-", TYPOGRAPHIC_MINUS] : [TYPOGRAPHIC_MINUS, "-"];
-  if (!text.includes(other)) return text;
-  return formatter
-    .formatToParts(value)
-    .map((part) => (MINUS_PARTS.has(part.type) ? wanted : part.value))
-    .join("");
-}

package/src/lib/path-pattern.ts

@@ -1,55 +0,0 @@
-/**
- * Whether a pathname is one a `PathPattern` names — the rule `useLastVisitedPage`'s
- * `exclude` reads (landing/routing.tsx) and the feedback guard's one-shot routes
- * (refactor audit 2026-10-30, FLW-7), here without the router: `landing/routing` imports
- * react-router, which `/feedback` must not drag in. The one copy: routing kept a private
- * one, and the two had drifted within the round (0.52 code review, this file).
- *
- * A string is that path and everything under it (`/join` is `/join` and `/join/abc`, not
- * `/joined`; `/` is only `/`); a RegExp is tested on the pathname (a `g` flag dropped, so
- * `lastIndex` never carries over between calls).
- *
- * Case-INSENSITIVE, as React Router matches a route unless it sets `caseSensitive` (0.52
- * code review, feedback/feedback-page-link.ts): the FLW-7 guard compared case-sensitively,
- * and `/Join?token=` went out as a link the router still rendered as `/join`. A RegExp
- * gets the `i` flag for the same reason. Matching more than a case-sensitive route would
- * only turns a link into text, or leaves a page unrecorded as a resume target: both
- * callers' safe side.
- *
- * @internal Package-private — not re-exported from the barrel.
- */
-export function matchesPathPattern(pathname: string, pattern: string | RegExp): boolean {
-  if (typeof pattern !== "string") {
-    return new RegExp(pattern.source, `${pattern.flags.replace(/[gi]/g, "")}i`).test(pathname);
-  }
-  const path = pathname.toLowerCase();
-  if (pattern === "/") return path === "/";
-  const base = (pattern.endsWith("/") ? pattern.slice(0, -1) : pattern).toLowerCase();
-  return path === base || path.startsWith(`${base}/`);
-}
-
-/**
- * The pathname of `href` (a path with its query and hash) as React Router matches it:
- * each segment percent-decoded, an encoded `/` kept as `%2F` so it never splits a segment
- * (react-router 8, `decodePath` in `matchRoutesImpl`). The 0.52 code review
- * (feedback/feedback-page-link.ts) found `/j%6Fin?token=` passing the FLW-7 guard as a
- * link that the router decoded to `/join`.
- *
- * A malformed escape leaves its own segment as written, where the router gives up on the
- * whole path: the rest still decodes, so the answer is never less than the router's.
- *
- * @internal Package-private — not re-exported from the barrel.
- */
-export function routerPathname(href: string): string {
-  return href
-    .replace(/[?#].*$/, "")
-    .split("/")
-    .map((segment) => {
-      try {
-        return decodeURIComponent(segment).replace(/\//g, "%2F");
-      } catch {
-        return segment;
-      }
-    })
-    .join("/");
-}