@clicktap/ui 2.4.3 → 2.4.4

package/components/Icon/UserIcon.js

@@ -1 +1 @@
-"use client";import{jsxs as o,jsx as e}from"react/jsx-runtime";import{cn as n}from"../../utils/cn.js";function c({className:t,size:r=16}){return o("svg",{width:r,height:r,viewBox:"0 0 24 24",fill:"none",xmlns:"http://www.w3.org/2000/svg",className:n("text-ffl-gray-500 flex-shrink-0",t),stroke:"currentColor",strokeWidth:"2",strokeLinecap:"round",strokeLinejoin:"round",children:[e("path",{d:"M19 21v-2a4 4 0 0 0-4-4H9a4 4 0 0 0-4 4v2"}),e("circle",{cx:"12",cy:"7",r:"4"})]})}export{c as UserIcon,c as default};
+"use client";import{jsxs as t,jsx as e}from"react/jsx-runtime";import{cn as n}from"../../utils/cn.js";function c({className:o,size:r=16}){return t("svg",{width:r,height:r,viewBox:"0 0 24 24",fill:"none",xmlns:"http://www.w3.org/2000/svg",className:n("flex-shrink-0",o),stroke:"currentColor",strokeWidth:"2",strokeLinecap:"round",strokeLinejoin:"round",children:[e("path",{d:"M19 21v-2a4 4 0 0 0-4-4H9a4 4 0 0 0-4 4v2"}),e("circle",{cx:"12",cy:"7",r:"4"})]})}export{c as UserIcon,c as default};

package/components/ModalOverlay/ModalOverlay.d.ts

@@ -13,7 +13,7 @@ import { ModalOverlayProps } from './ModalOverlay.types';
  * @clicktap/ui copies installed (ordinary pnpm version skew) the trigger wrote `visible` into one
  * copy while the overlay read the other's `unmounted` default — `animate="unmounted"` names no
  * variant, framer-motion holds `initial: "hidden"`, and every trigger-driven modal sat mounted at
- * `opacity: 0` with zero errors (CTAP-1210, noco). react-aria's context is the safe dependency:
+ * `opacity: 0` with zero errors (CTAP-1210, found by a consumer). react-aria's context is the safe dependency:
  * if react-aria-components itself is duplicated, everything breaks loudly.
  *
  * Exported for unit tests only.

package/docs/migrations/2026/06/ui-2026-06-17-select-standardization.md

@@ -2,7 +2,7 @@
 
 **Date:** 2026-06-17
 **Package:** `@clicktap/ui`
-**Affects:** Any app consuming `@clicktap/ui`'s `Select` / `DropdownSelect` (Crispi, FFL, and any fork that renders pickers, sort controls, country/region selects, or configurable-product options).
+**Affects:** Any app consuming `@clicktap/ui`'s `Select` / `DropdownSelect` (downstream projects and any fork that renders pickers, sort controls, country/region selects, or configurable-product options).
 **Classification:** FEATURE + BREAKING
 **Breaking:** Yes — (1) `DropdownSelect` removed, (2) the bare `<Select>` is now a **button picker**, not a combobox, (3) `DropdownSelect`'s `classNames.trigger` is now `classNames.input`, (4) the root is `w-full` by default, (5) `<Option>` is react-stately's `Item` — keyed by `key` (no `id`) and **cannot be wrapped**.
 **Formerly named:** `2026-06-17-select-standardization.md` — renamed 2026-08-10 (CTAP-1214) for global filename uniqueness; library guides carry their package slug so they can never collide with an app-level guide in a consumer's aggregated working set. **If you carry a `-applied` sibling under the old name, rename it to match — do NOT re-apply.**

package/docs/migrations/2026/07/ui-2026-07-31-ui-exports-bundler-resolution.md

@@ -1,7 +1,7 @@
 # `@clicktap/ui` resolves its deep subpaths under `moduleResolution: bundler` (CTAP-1060)
 
 **Date:** 2026-07-31
-**Revised:** 2026-08-08 — the test-runner half (CTAP-1195): every runtime subpath entry gains a `default` condition, so CJS resolvers (Jest) stop falling through to the `.d.ts`. See "Test runners (Jest)" below; reported by noco.
+**Revised:** 2026-08-08 — the test-runner half (CTAP-1195): every runtime subpath entry gains a `default` condition, so CJS resolvers (Jest) stop falling through to the `.d.ts`. See "Test runners (Jest)" below; reported by a consumer.
 **Package:** `@clicktap/ui`
 **Breaking:** No — additive to the `exports` map. Existing `moduleResolution: node` / `node10`
 consumers are unaffected (that resolver ignores `exports`); this only *adds* working resolution under
@@ -50,7 +50,7 @@ emits only `.d.ts` for it).
 The original map declared only `types` + `import` conditions. That covers bundlers — but **Node CJS
 resolution** (what Jest uses without ESM flags) matches neither, so it fell through to the `.d.ts`
 and died on `export interface`. Any consumer whose Jest suite touches `useCooldown` (i.e. anyone
-adopting the CTAP-1114 `useResendCode` pattern *with* its tests) hit this; noco worked around it with
+adopting the CTAP-1114 `useResendCode` pattern *with* its tests) hit this; one consumer worked around it with
 a `moduleNameMapper` straight to the `.js` files.
 
 Since this revision every runtime subpath entry carries a **`default` condition (last)** pointing at

package/docs/migrations/2026/08/ui-2026-08-07-ui-peer-contract-form-graphql-optional-peers.md

@@ -12,7 +12,7 @@
 CTAP-1158 validated every publishable lib manifest against its real imports. For `@clicktap/ui`
 that audit changed the peer contract and corrected a wrong dependency pin, but no guide shipped
 with it — consumers would meet the changes as unexplained manifest churn on the next release
-(reported by family-rpg, 2026-08-07). This is that guide.
+(reported by a consumer, 2026-08-07). This is that guide.
 
 ## What changed
 

package/docs/migrations/2026/08/ui-2026-08-11-password-reveal-toggle.md

@@ -2,7 +2,7 @@
 
 **Date:** 2026-08-11
 **Revised:** 2026-08-11 — consumer action now says to rename a component named for the press-and-hold
-gesture (family-rpg's `HoldToRevealButton`), not only to swap its handlers.
+gesture (for example a `HoldToRevealButton`), not only to swap its handlers.
 **Package:** `@clicktap/ui`
 **Affects:** `@clicktap/ui` — `Input` with `type="password"`.
 **Classification:** IMPROVEMENT (UX / accessibility)
@@ -69,7 +69,7 @@ Shipped in `@clicktap/ui` **0.43.6**.
   and add `aria-pressed` + the state-dependent `aria-label` while you are in there. The reference
   frontend also updated its one bespoke reveal (`UpdateEmailForm`) to match.
   - **Rename the component if its name describes the gesture.** If you named it for press-and-hold
-    when you applied CTAP-1128 — family-rpg had `HoldToRevealButton` (2026-08-11) — the name now
+    when you applied CTAP-1128 — one consumer had `HoldToRevealButton` (2026-08-11) — the name now
     documents behaviour the code no longer implements, in the one place nobody re-reads. Rename it
     (`PasswordRevealButton`, `ShowPasswordToggle`) in the same change as the handler swap, and grep
     for the old name in tests and stories.

package/docs/migrations/2026/08/ui-2026-08-11-peer-ranges-capped.md

@@ -57,7 +57,7 @@ rather than as an error.
 ### When the duplicate is transitive — nothing of yours to pin
 
 The paragraph above assumes the second copy comes from a declaration you own. Often it does not:
-crispi resolves `react-stately` 3.49.0 cleanly across every workspace member and still carries a
+one consumer resolves `react-stately` 3.49.0 cleanly across every workspace member and still carries a
 second copy at 3.46.0, arriving via `@adobe/react-spectrum` → `react-aria-components`. No manifest of
 theirs names it, so there is no pin to correct.
 

package/docs/migrations/2026/08/ui-2026-08-24-accordion-author-key-space.md

@@ -4,7 +4,7 @@
 **Package:** `@clicktap/ui`
 **Affects:** every controlled or default-expanded `Accordion` — checkout payment method selection, checkout's `defaultExpandedKeys={['cart']}`, totals/discount panel, PDP mobile overview, filter groups.
 **Classification:** BUGFIX
-**Breaking:** No — unless you shipped a workaround that pre-prefixes keys (see crispi note).
+**Breaking:** No — unless you shipped a workaround that pre-prefixes keys (see the shim note below).
 **Ticket:** CTAP-1404
 
 ## The defect (2.0.x regression from the CTAP-1383 react-aria rewrite)
@@ -17,11 +17,11 @@ were only `String()`ed, so:
 1. `selectedKeys` / `defaultSelectedKeys` / `defaultExpandedKeys` never matched
    any item — nothing opened, nothing highlighted. The checkout payment step's
    method selection "not working" was this.
-2. `onSelectionChange` handed the PREFIXED id back out — crispi's checkout
+2. `onSelectionChange` handed the PREFIXED id back out — a consumer's checkout
    dispatched `".$CYBERSOURCE"` as a payment method code to the backend.
 
 The heroui accordion this replaced handled keys correctly. Diagnosed by the
-crispi session against the installed 2.0.6 bundle.
+consumer's session against the installed 2.0.6 bundle.
 
 ## The fix
 
@@ -36,13 +36,13 @@ round-trips with no output translation. `"all"` and unkeyed children (positional
 
 1. Take the release; no call-site changes needed — controlled accordions start
    working as written.
-2. **Delete compensating shims.** crispi: `libs/crispi-ui/.../Accordion.tsx`
-   wrapper (crispi-monorepo `7a44704f0`) must be REMOVED when taking this
+2. **Delete compensating shims.** A consumer-side `.../Accordion.tsx`
+   wrapper that pre-prefixes keys must be REMOVED when taking this
    release — it translates keys into the prefixed space, which no longer
    exists, so keeping it reintroduces the bug in the other direction. Check the
    shim's own escape handling is not needed elsewhere (this fix also covers
    escaped keys, which a bare `.$`-strip shim does not).
-3. If any code path stored or transmitted a prefixed id (`.$…`) — crispi saw
+3. If any code path stored or transmitted a prefixed id (`.$…`) — one consumer saw
    them reach the backend as payment codes — check persisted data for the
    `.$` prefix.
 

package/docs/migrations/2026/09/ui-2026-09-16-modal-overlay-detached-motion-element.md

@@ -28,7 +28,7 @@ observed:
    keyframe resolvers synchronously on the detached element.
 
 🚨 Thrown inside framer-motion's frame loop, so nothing reaches server logs and no React error
-boundary catches it. noco hit it in the warranty admin: a controlled drawer (route 1) containing a
+boundary catches it. A consumer hit it in its warranty admin: a controlled drawer (route 1) containing a
 never-opened trigger-driven Page Builder overlay threw **13 errors on every close**, and in
 production that broke the frame loop — the close animation and the success toast were both lost.
 Every other trigger-driven overlay in that app (delete confirms, edit modals) carried the same
@@ -49,8 +49,8 @@ already gets from `AnimatePresence` is now the same on both paths:
 
 ## Consumer impact
 
-- **Nothing to change.** Take the release. If you gated the overlay yourself in a wrapper (noco
-  tried it in `@noco/ui`), **remove that gate**: mounting only once already open, with the hook
+- **Nothing to change.** Take the release. If you gated the overlay yourself in a wrapper (one
+  consumer tried it in its own UI library), **remove that gate**: mounting only once already open, with the hook
   initialized to `visible`, gives framer-motion no transition to play and leaves the backdrop stuck
   at `opacity: 0`. The fix has to live where the animation state is derived.
 - ⚠️ Do not read the mount as a signal. Nothing should depend on a closed trigger-driven overlay

package/docs/migrations/2026/09/ui-2026-09-18-pin-input-autofill-and-controlled-value.md

@@ -5,11 +5,11 @@
 **Affects:** `src/components/PinInput/PinInput.tsx`, `PinInput.types.ts`. Every consumer of `<PinInput>` (signup, forgot-password and email/password-change verification on the storefront).
 **Classification:** BUGFIX (three) + IMPROVEMENT (`value`/`name` honored)
 **Breaking:** No API change. **Behavioral:** passing `value` now controls the boxes (it was silently ignored); `maxLength` is no longer rendered; `autoComplete="one-time-code"` is on the first box only.
-**Ticket:** CTAP-1749 (from NOCOE-2944)
+**Ticket:** CTAP-1749
 
 ## What was wrong
 
-Four things, all in this component (a consumer wrapper such as noco's `libs/noco-ui` only restyles it):
+Four things, all in this component (a consumer wrapper in a consumer's UI library only restyles it):
 
 1. **Android autofill and Gboard's clipboard chip lost five of six digits.** The paste handler split
    digits across the boxes correctly, but autofill and the keyboard chip insert text as an *input*

package/docs/migrations/2026/10/ui-2026-10-02-user-icon-drops-project-color-class.md

@@ -0,0 +1,25 @@
+# `UserIcon` no longer carries a project's color class
+
+**Date:** 2026-10-02
+**Package:** `@clicktap/ui`
+**Affects:** `components/Icon/UserIcon`
+**Classification:** IMPROVEMENT
+**Breaking:** No for any app that does not define the removed color token. One that does loses that color on the icon until it passes the class itself.
+**Ticket:** CTAP-2094
+
+## What changed
+
+`UserIcon` hard-coded a `text-*-gray-500` class for a color token one consuming project defines in its
+own theme. The platform defines no such token, so the class did nothing here, and it named a project in
+the shared library. The icon now carries only `flex-shrink-0` and inherits its color like the other
+icons, so a consumer sets the color it wants through `className`.
+
+## Migrate
+
+If your theme defined that token (or any color you relied on for this icon), pass it:
+
+```tsx
+<UserIcon className="text-brand-gray-500" />
+```
+
+Nothing else.

package/docs/migrations/index.json

@@ -1,4 +1,14 @@
 [
+  {
+    "path": "2026/10/ui-2026-10-02-user-icon-drops-project-color-class.md",
+    "module": "libs/frontend-modules/ui",
+    "package": "@clicktap/ui",
+    "date": "2026-10-02",
+    "title": "`UserIcon` no longer carries a project's color class",
+    "classification": "IMPROVEMENT",
+    "breaking": "No for any app that does not define the removed color token. One that does loses that color on the icon until it passes the class itself.",
+    "affects": "`components/Icon/UserIcon`"
+  },
   {
     "path": "2026/09/ui-2026-09-30-modal-fade-no-final-frame-blink.md",
     "module": "libs/frontend-modules/ui",
@@ -156,7 +166,7 @@
     "date": "2026-08-24",
     "title": "Accordion controlled selection matches authored keys again",
     "classification": "BUGFIX",
-    "breaking": "No — unless you shipped a workaround that pre-prefixes keys (see crispi note).",
+    "breaking": "No — unless you shipped a workaround that pre-prefixes keys (see the shim note below).",
     "affects": "every controlled or default-expanded `Accordion` — checkout payment method selection, checkout's `defaultExpandedKeys={['cart']}`, totals/discount panel, PDP mobile overview, filter groups."
   },
   {
@@ -393,7 +403,7 @@
     "breaking": "No — additive to the `exports` map. Existing `moduleResolution: node` / `node10`",
     "affects": "",
     "revised": "2026-08-08",
-    "revised_note": "2026-08-08 — the test-runner half (CTAP-1195): every runtime subpath entry gains a `default` condition, so CJS resolvers (Jest) stop falling through to the `.d.ts`. See \"Test runners (Jest)\" below; reported by noco."
+    "revised_note": "2026-08-08 — the test-runner half (CTAP-1195): every runtime subpath entry gains a `default` condition, so CJS resolvers (Jest) stop falling through to the `.d.ts`. See \"Test runners (Jest)\" below; reported by a consumer."
   },
   {
     "path": "2026/06/ui-2026-06-18-select-hiddenselect-setvalue-crash.md",
@@ -413,7 +423,7 @@
     "title": "Select standardization — one `<Select searchable>`, `DropdownSelect` removed",
     "classification": "FEATURE + BREAKING",
     "breaking": "Yes — (1) `DropdownSelect` removed, (2) the bare `<Select>` is now a **button picker**, not a combobox, (3) `DropdownSelect`'s `classNames.trigger` is now `classNames.input`, (4) the root is `w-full` by default, (5) `<Option>` is react-stately's `Item` — keyed by `key` (no `id`) and **cannot be wrapped**.",
-    "affects": "Any app consuming `@clicktap/ui`'s `Select` / `DropdownSelect` (Crispi, FFL, and any fork that renders pickers, sort controls, country/region selects, or configurable-product options)."
+    "affects": "Any app consuming `@clicktap/ui`'s `Select` / `DropdownSelect` (downstream projects and any fork that renders pickers, sort controls, country/region selects, or configurable-product options)."
   },
   {
     "path": "2026/05/ui-2026-05-29-password-check-requirements-variant.md",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clicktap/ui",
-  "version": "2.4.3",
+  "version": "2.4.4",
   "private": false,
   "author": "Clicktap",
   "description": "A library of React UI components and low-level hooks.",