pixelize-design-library 2.4.1-beta.1 → 2.4.1-beta.10

package/.cursor/modules/cards/MODULE.md

@@ -1,55 +0,0 @@
-# Cards
-
-## Purpose
-
-Card, PaymentCard, ProfileCard, ProductCard, ProductDetails.
-
-## Key paths
-
-- `src/Components/Card/`, `Card/PaymentCard/`, `ProfileCard/`, `ProductCard/`, `ProductDetails/`
-
-## Key rules
-
-- ProfileCard has Header/Body/Footer subcomponents
-
-## Dark mode
-
-PaymentCard, ProductCard, ProductPrice, ProductDtlPrice and ProductImageSlider read their colors
-from `useCustomTheme()` instead of hex literals, so they follow the active light/dark palette.
-
-- Surfaces use `colors.background[50]`, never `colors.white` — `white` is a foreground token and
-  stays white in dark. Covers the card body, the ProductPrice dropdown panel and its radio dot,
-  the unselected pack chip in ProductDtlPrice, and the play-button circle in ProductImageSlider.
-- PaymentCard's badge/button label no longer hardcodes `colors.white` — it's picked per
-  `buttonColor` via `onFilled()` (`Theme/tokens/builders/accentText`), which falls back to
-  `colors.black` when white would fail AA on that fill. Guarantees WCAG AA across the
-  active/upgrade/popular/default button colors instead of assuming white always works.
-- The product components keep Chakra literals for offer/pack chrome (`red.50`, `orange.50`,
-  `green.100`). Those are dark-aware already — the theme carries the palette as `colors`, and
-  `buildDarkPalette` reverses utility hue ramps so index roles survive (`red.50` = pale badge
-  background in light, deep in dark). They track the hue, not the brand accent.
-- ProductPrice's struck-through original price bumped `gray.400` → `gray.500` (still a raw
-  Chakra literal, not a theme token) for AA contrast against the card surface.
-- ProductTags' label swapped `colors.black` → `colors.text[900]` (mode-adaptive ink token) so it
-  stays legible in dark mode.
-- **Known gap:** ProductReview's rating chip (`bg="teal.50"` / `color="teal.900"`) and its star
-  fill (`RATING_STAR_FILL`, a pinned `#ECC94B` hex — see in-file comment) are still raw
-  Chakra/hex literals, not `useCustomTheme()` tokens. Pre-existing pattern, not worsened by this
-  pass, but won't track brand hue or dark mode — needs a mode-stable "rating gold" token added to
-  `pixelize-design-library` before this can move off literals.
-
-## WCAG contrast pass (Wave D, QA-driven)
-
-- **ProductPrice.tsx** — dropdown-arrow `red.400` (on `red.50` canvas) and discounted/final-price
-  `red.500` text (on `red.50`/`background[50]` depending on selection state) failed AA (2.6-3.7:1).
-  Fixed via `accentTextOnCanvas(theme.colors.red, <the actual local canvas>)` at each of the 3
-  call sites, matching the canvas each already renders on (including the existing `isSelected`
-  bg ternary). The dot-fill `bg="red.500"` (a filled swatch, not text) was left unchanged — it
-  clears the 3:1 non-text bar against `background[50]`.
-- **ProductDtlPrice.tsx** — price `Text` hardcoded `theme.colors.red[500]` (≈3.46:1 vs the page
-  canvas, fails) and the pack-swatch `color="orange.600"` (≈2.47-2.67:1 vs either bg state,
-  fails) both routed through `accentTextOnCanvas`. `borderColor`/`bg` on the swatch button are
-  decorative and were left alone.
-- **ProductImageSlider.tsx** — checked, not changed: all 6 `theme.colors.red[500]` Play-icon
-  usages sit on an opaque `background[50]` circular scrim (not the raw image), so the applicable
-  bar is 3:1 (graphical object, not text) — clears at ≈3.68:1 light / ≈6.48:1 dark.

package/.cursor/modules/charts/MODULE.md

@@ -1,40 +0,0 @@
-# Charts
-
-## Purpose
-
-Apexcharts wrappers: Bar, Line, Pie, Polar.
-
-## Key paths
-
-- `src/Components/Apexcharts/ApexBarChart/`, `ApexLineChart/`, `ApexPieChart/`, `ApexPolarCharts/`
-- `src/Theme/tokens/builders/chartColorsFromTheme.ts` — shared chart color helpers (+ test)
-
-## Key rules
-
-- react-apexcharts; every color is a theme token, never a literal. Shared helpers:
-  `getDefaultSeriesColors` (primary / error / success / orange `500`), `mergeChartTitleStyle`
-  (title → `primary[500]`), `chartAxisLabelColor` (`gray[700]`). The rest read `palette` directly:
-  legend `text[900]` (Pie/Polar), Bar data labels `primary[500]`, Polar stroke `white`.
-- All four read `useTheme().colors` (cast to `CustomThemeProps["colors"]`) rather than styling via
-  Chakra props, because ApexCharts `options` need resolved hex **strings**.
-- The helper sits in the pure token layer: type-only imports, never Chakra/React (see CLAUDE.md).
-
-## Dark mode
-
-- Dark-aware for free — the theme swaps in the dark palette and these tokens re-resolve. No hex
-  literals remain under `Apexcharts/`.
-- Caller color props (`barColor`, `lineColors`, `chartColor`/`donutColors`, `chartColors`,
-  `titleStyle`, `legendStyle`) override the token defaults and are **not** dark-aware: a consumer
-  passing a hardcoded hex keeps it in both modes.
-- ApexPolarCharts `basic`/`monochrome` stroke slice borders with `colors.white` — foreground on a
-  filled slice, so it correctly stays white; not a missed `background[50]` surface.
-- All four now also set ApexCharts' own `options.theme.mode` (`"dark"`/`"light"`) from
-  `isDarkCanvas(palette.backgroundColor.main)` (`Theme/tokens/builders/accentText.ts`), so
-  ApexCharts' internal chrome (gridlines, built-in tooltip, etc.) follows the active canvas too,
-  not just the token-driven series/title/legend colors. No change to any chart's data/options
-  prop contract.
-- Removed `chartTooltipBackground`/`chartTooltipForeground` from `chartColorsFromTheme.ts` (they
-  always resolved to a hardcoded dark-styled tooltip — `gray[700]`/`white` — regardless of mode,
-  now unused repo-wide). `ApexLineChart`'s title-truncation `ToolTip` no longer overrides
-  `bg`/`color`; it defers to `ToolTip`'s own theme-aware default instead.
-- Known gap: titles/legends use `primary[500]` / `text[900]`, not the AA-safe `accentText` token.

package/.cursor/modules/common/MODULE.md

@@ -1,36 +0,0 @@
-# Common Helpers
-
-## Purpose
-
-Internal shared helpers under `Components/Common/` — not all exported from index.
-
-## Key paths
-
-- `src/Components/Common/` — ErrorComponent, FormLabel, etc.
-
-## Key rules
-
-- Internal use by other components; export only if needed publicly
-
-## Dark mode
-
-- **FormLabel** (`TextLabel`): both tooltips (`showTooltip` / `isInformation`) swapped
-  Chakra's own `Tooltip` for the library's `ToolTip` (`../ToolTip/ToolTip`), dropping the
-  hardcoded `bg={gray[600]}` / `color={white}` — `ToolTip` owns its own theme-aware
-  contrast (see `overlays` MODULE.md). No `TextLabel` prop changes.
-- **fieldStyles.ts** (`getFieldStateStyles`): idle border bumped `boxborder[500]` →
-  `boxborder[800]` — `[500]` failed WCAG 1.4.11 (>=3:1 non-text contrast) against
-  surfaces up to `muted`; `[800]` clears with margin. Focus/error ring colors and the
-  function signature are unchanged.
-- **ErrorMessage.tsx**, **ErrorComponent.tsx**, **FormLabel.tsx** (required-asterisk), **Label.tsx**:
-  error text color switched from a hardcoded `theme.colors.red[500]` / `semantic.error[500]` to
-  `accentTextOnCanvas(scale, canvas)` (`../../Theme/tokens/builders/accentText`) — `red[500]` alone
-  fails AA (~3.4:1) against the page canvas in every brand; see `theme` MODULE.md "Wave D" for why
-  this couldn't be a token retune. No prop/API changes.
-- **ErrorComponent.tsx's SVG mark ink (code-review catch):** the circle/rect/dot marks drawn on
-  top of the `errorFill` circle were hardcoded `theme.colors.white`. `errorFill` is tuned for
-  text-on-page-canvas contrast, not for "carries a white mark on top of itself" — those are
-  different constraints, and nothing guaranteed white would keep clearing AA there if the token
-  ever changed (it happened to today). Replaced with
-  `onFilled(errorFill, theme.colors.white, theme.colors.black)`, the same provably-always-safe
-  ink-on-a-filled-swatch helper used by FilterSidebar's checkmark and PaymentCard.

package/.cursor/modules/contact-auth/MODULE.md

@@ -1,19 +0,0 @@
-# Contact & Email
-
-## Purpose
-
-ContactForm, VerifyEmailOtp (EmailCards).
-
-## Key paths
-
-- `src/Components/ContactForm/`, `EmailCards/VerifyEmailOtp/`
-
-## Key rules
-
-- OTP flow UI only — API wiring in consumer apps
-
-## Dark mode
-
-- **VerifyEmailOtp**: `PinInputField` idle border bumped `boxborder[300]` → `boxborder[800]` —
-  `[300]` failed WCAG 1.4.11 (>=3:1 non-text contrast) against surfaces up to `muted`; `[800]`
-  clears with margin. Already theme-token-driven before this change; no prop/signature changes.

package/.cursor/modules/data-display/MODULE.md

@@ -1,42 +0,0 @@
-# Data Display
-
-## Purpose
-
-Tag, Timeline, Reorder, Divider, Trail.
-
-## Key paths
-
-- `src/Components/Tag/` — `Tag.tsx`, `TagProps.ts`, `Tag.styles.tsx` (registered in `Theme/componentStyles.ts`)
-- `Timeline/`, `Reorder/`, `Divider/`, `Trail/`
-- Demo: `src/Pages/tag.tsx`
-
-## Key rules
-
-- Timeline: each event card renders its manual notes from `event.notes` (`TimelineNote[]` — `log_note_id`, `title`, `note`, `attachments[]`, `created_by`, `created_at`). Adding a note is event-scoped via the per-card "Add note" button → `onAddNote(note, title, files, event, index)`; the consumer persists it against `event.logs_id` and re-supplies it back in `event.notes`. Attachments show as links opening `attachment.url`.
-- Timeline notes support edit + delete: hovering a note shows edit/delete icons → `onEditNote(logNoteId, note, title, files, event, index)` (inline `NoteTextArea`) and `onDeleteNote(logNoteId, event, index)` (consumer owns any confirm dialog). Loading props: `addNoteLoading`/`editNoteLoading` keep the editor open with a Save spinner until the request resolves (then auto-close); `deletingNoteId` shows a spinner on the note being deleted. With no loading props wired, the add editor closes immediately on submit (back-compat).
-- Trail includes editable cell demos
-- Tag styling lives in `Tag.styles.tsx` (Chakra component theme), not hardcoded in `Tag.tsx`
-- Tag sizes: `xs | sm | md | lg`; variants: `solid | outline | subtle`
-- Tag colors are token-driven from the active theme via `colorScheme` (brand `primary/secondary/tertiary` + global scales); palette resolution falls back to `gray` so a missing scale never throws
-- Tag `solid` variant label color is now `onFilled(fill, white, black)` (per state: base/hover/active), not a hardcoded `white` — picks whichever of white/black clears WCAG AA against that swatch, so it stays readable on light brand fills too
-
-## WCAG / dark-mode pass (this session)
-
-- **Tag.styles.tsx** — `solid` variant's foreground swapped from hardcoded `theme.colors?.white` to
-  `onFilled(fill, white, black)`, computed per bg (base `500`, hover `600`, active `700`); verified
-  against WCAG AA.
-- **Trail/EditableCell.tsx** — `priority` menu's `MenuButton` had a real hover-contrast fix: `bg`
-  `teal.500`/`color white` → `bg="teal.50"` / `color="teal.900"` (+ hover/active states). **Known
-  gap:** this uses raw Chakra `teal.*` literals, not `useCustomTheme()` tokens, so it won't track
-  brand hue or dark mode — needs a follow-up token pass.
-  - **Known gap (not fixed this pass):** the same `MenuList`/`MenuItem` still has no `bg=`/
-    `sx={{ "--menu-bg": ... }}` override, so Chakra's `--menu-bg` CSS var still resolves to its
-    hardcoded light-mode white regardless of this app's active dark mode — same root-cause bug
-    already fixed this session in `ButtonGroupIcon` (buttons module) and `NavigationBar`
-    (layout-navigation module). Deliberately deferred, not overlooked.
-
-## Dark mode
-
-- Timeline takes every color from `useCustomTheme()`, so it follows whichever palette the theme carries. Dark works by swapping the palette — there is no `_dark`/`semanticTokens` layer, so a hardcoded value would stay light forever.
-- White surfaces use `colors.background[50]`, **not** `colors.white` — `white` is a *foreground* token (label on a filled button) and stays white in dark. Covers Timeline's event card, date chip, and the node ring that punches each node out of the spine. (Timeline's inline `NoteTextArea` is owned by `inputs-basic`.)
-- Timeline's remaining `?? "#fff"` fallbacks are defensive only — every brand palette defines `background[50]` (dark included, derived by `buildDarkPalette`).

package/.cursor/modules/feedback/MODULE.md

@@ -1,32 +0,0 @@
-# Feedback
-
-## Purpose
-
-Loading, Skeletons, ProgressBar, Notification, FeedbackForm.
-
-## Key paths
-
-- `src/Components/Loading/`, `Skeletons/`, `ProgressBar/`, `Notification/`, `FeedbackForm/`
-- `src/services/feedback.ts`
-
-## Key rules
-
-- FeedbackForm may POST to account API in consumer apps — keep props generic
-
-## Dark mode
-
-- **Notification**: default `bgColor` switched `theme.colors.white` → `theme.colors.background[50]`
-  — `white` is a foreground token (label ink, stays white in dark) and was being used as the card
-  surface; `background[50]` is the correct dark-mode-aware white-surface token. Real bug fix (was
-  forcing a white card in dark mode), not a plain refactor. Consumers passing `colors.bgColor`
-  explicitly are unaffected.
-- **`warningColor`/`errorColor`/`successColor` object-vs-string bug (QA-adjacent, real correctness
-  bug, not WCAG):** `NotificationProps` types these as hex strings, but the defaults were an
-  un-indexed whole `ColorScale` object (`theme.colors.semantic.warning` instead of
-  `theme.colors.semantic.warning[500]`) — Chakra silently can't render an object as a `bg=` color,
-  so the default (no-override) case was broken. Fixed by indexing `[500]` on all three defaults.
-- **Time-elapsed icon/label AA gap:** the "time ago" `Icon`/`Text` defaulted to `orange.400`/
-  `orange.500`, which fail AA (~1.9–2.2:1) against `bgColor` in every brand — same class of bug as
-  the `error`/`red[500]` gap (theme module). Fixed by routing both through
-  `accentTextOnCanvas(theme.colors.orange, bgColor)` (`Theme/tokens/builders/accentText`) instead
-  of a fixed rung.

package/.cursor/modules/form/MODULE.md

@@ -1,13 +0,0 @@
-# Form
-
-## Purpose
-
-FormWrapper — shared form layout wrapper for entity forms in CRM apps.
-
-## Key paths
-
-- `src/Components/Form/FormWrapper`
-
-## Key rules
-
-- Used with smart forms in crm-frontend; keep generic props

package/.cursor/modules/inputs-basic/MODULE.md

@@ -1,42 +0,0 @@
-# Basic Inputs
-
-## Purpose
-
-TextInput, PhoneNumberInput, InputTextArea, NoteTextArea, NumberInput, PinInput, PinInputs.
-
-## Key paths
-
-- `src/Components/Input/`, `InputTextArea/`, `NoteTextArea/`, `NumberInput/`, `PinInput/`, `PinInputs/`
-
-## Key rules
-
-- InputSwitch in `Input/Switch/`
-
-## Dark mode
-
-- No hex literals remain — every field follows the active palette, but by three paths, not one:
-  `useCustomTheme()` (TextInput, PhoneNumberInput, NoteTextArea, PinInput, InputSwitch), Chakra
-  `useTheme()` (Input/Input, PinInputs), and `componentStyles` `({ theme })` fns (InputTextArea,
-  NumberInput — no theme hook at all). The `?? "gray.300"` fallbacks in `*.styles.ts` are token
-  refs, not literals: `createBrandTheme` sets `colors: palette`, so they resolve against the
-  swapped palette.
-- `NoteTextArea` was the only migration here: its 4 white surfaces moved `colors.white` →
-  `colors.background[50]`. `colors.white` is a **foreground** token (a label on a filled button)
-  and stays white in dark; a white *surface* needs `background[50]` (identical `#ffffff` in light).
-- `InputSwitch` layers `useColorModeValue` over the palette swap — it picks a different *rung*
-  (`primary[500]`→`[300]`, `gray[300]`→`[600]`) of the already-dark palette, not a second palette.
-
-## Border contrast bump ([500]/[700] → [800])
-
-- Follow-up fix: `boxborder` at `[500]`/`[700]` only cleared canvas-level surfaces (main/base)
-  and failed WCAG 1.4.11 (control boundary, >=3.0) against `muted`, the lightest named surface
-  (2.41-2.72). All seven fields — `Input/Input.tsx`, `TextInput.styles.ts`,
-  `InputTextArea.style.tsx`, `NumberInput.styles.ts`, `PinInput.tsx`, `PinInputs.tsx`,
-  `NoteTextArea.tsx` — now use `boxborder?.[800]` for the resting/default border, clearing all
-  12 named surfaces (3.44-3.90) in both modes.
-- `Input/Input.tsx` also swapped its label/accent color from `colors.secondary?.[500]` to
-  `accentTextOnCanvas(colors.secondary, colors.backgroundColor?.main)` — relies on the shared
-  `accentText.ts` guard (Theme module) for safety when rendered without a full Pixelize theme;
-  no separate fix was needed in this file.
-- `Input/Input.tsx` is **not** exported from `src/index.ts` (internal, used only by
-  `src/Pages/TInput.tsx`) — low external impact.

package/.cursor/modules/inputs-date-file/MODULE.md

@@ -1,56 +0,0 @@
-# Date & Files
-
-## Purpose
-
-ThemeDatePicker (Single/Range/Time variants), FileUpload, FileUploader, Editor (jodit-react).
-
-## Key paths
-
-- `src/Components/DatePicker/` — `ThemeDatePicker.tsx` (public entry), `SingleDatePicker.tsx`, `RangeDatePicker.tsx`, `TimePicker.tsx`, `TimeOnlyPicker.tsx`, `CalendarPanel.tsx`
-- `src/Components/FileUpload/`, `FileUploader/`, `Editor/`
-
-## Key rules
-
-- DatePicker themed for brand tokens — `CalendarPanel` reads every color from `useCustomTheme()` (no hex literals), so it follows the active light/dark palette automatically.
-- The month/year `<select>` uses `colors.background[50]`, not `colors.white`: it is a white *surface* and must darken in dark mode. The one remaining `colors.white` (day label on the filled `primary[500]` circle — selected / range start / range end) is a *foreground* and correctly stays white. Don't "fix" it.
-- **Calendar/time popover surface bug (user-reported, blocking):** `SingleDatePicker.tsx`, `RangeDatePicker.tsx`, `TimeOnlyPicker.tsx`, and the legacy `DatePicker.tsx` (still reachable — consumed directly by `Table/filters/LeftFilterPane.tsx`, not just via the unused commented-out playground import) each rendered a `PopoverContent` with no explicit `bg=` — the same Chakra-hardcoded-`colors.white`-behind-`_dark` bug as `Modal`/`AlertDialog`/`Drawer` (overlays module). Because `CalendarPanel`'s day/weekday text (`text[700]`/`gray[400]`/`gray[500]`) is computed against the *intended* dark canvas, the panel rendered on Chakra's un-migrated white default while its text was tuned for a dark background — producing exactly the washed-out, near-invisible day numbers reported. Fixed with `bg={theme.colors.background[50]}` on all four `PopoverContent`s (`TimeOnlyPicker.tsx` didn't previously call `useCustomTheme()` at all — added the hook). Verified live via Playwright across all four variants (date-only, date+time, range, time-only).
-- **FileUploader (QA-caught)** — its file-count and "Click here" text hardcoded `color="blue.500"`/
-  `"blue.400"`, which fail AA against the component's canvas (same class as the Notification
-  orange gap). Fixed via `accentTextOnCanvas(colors.blue, colors.backgroundColor?.main ?? "#ffffff")`
-  (`Theme/tokens/builders/accentText`), reused for both spots. Rest of the component (drag/drop
-  chrome, file-row chips) is still Chakra scale literals (`gray.*`), not migrated to
-  `useCustomTheme()` — out of scope for this pass since those are already dark-aware Chakra
-  literals (see table/account-management MODULE.md for why plain `gray.*` literals already track
-  the swapped palette).
-- Editor is now theme-aware: it reads `theme.colors.backgroundColor?.main` (with a `"#ffffff"` fallback added after a code-review-caught crash risk) via `isDarkCanvas()` to switch Jodit's own internal `dark`/`default` editor theme — it does not restyle Jodit itself, just picks which built-in Jodit theme renders. FileUpload does use theme (`useCustomTheme()`: `gray`, `red`, `blue`, `background`, `secondary.opacity`) but was not migrated — **known gap**: `FileUpload.tsx:153` paints the uploaded-file row `bg={colors?.white}`, a *surface* on the foreground token, so it stays white in dark mode; should be `background[50]`.
-- **Editor dark-mode "not black" bug (user-reported, fixed):** toggling Jodit's `config.theme` between `"dark"`/`"default"` only switches which of Jodit's OWN CSS selectors apply (`.jodit_theme_dark`, 180+ occurrences in `jodit.css`) — those selectors are still driven by Jodit's own hardcoded CSS custom properties (`--jd-dark-background-color: #575757`, a mid-gray, not black; `--jd-color-border-selected: #1e88e5`, generic blue), never fed this library's palette. Fixed in `Editor.tsx` by wrapping `<JoditEditor>` in a `<Box sx={...}>` carrying `getJoditThemeVars(theme.colors, isDark)` (`joditThemeVars.ts`) — inline CSS custom properties, scoped to this instance only (no `:root` leak onto other Jodit instances). Mapping: canvas/toolbar → `backgroundColor.main`/`.secondary`, ink → `text[900]`, icons → `text[700]`, hover/select-bg → `backgroundColor.muted`, border → `boxborder[500]`, accent → `primary[500]` — reusing the SAME role-stable tokens in both modes (`background[50]`/`text[900]` etc. already flip lightness internally per `buildDarkPalette.ts`, so no per-mode branching on VALUES, only on the `--jd-color-*` vs `--jd-dark-*` variable NAMES Jodit's default vs dark theme actually reads). Verified via Playwright: before showed `rgb(87,87,87)` (`#575757`, Jodit's default) on the canvas/toolbar in dark mode; after shows the brand's real near-black surface. Regression tests: `joditThemeVars.test.ts` (contrast + non-default-value assertions, lavender + rosewood).
-- **Editor popup/dialog portal gap (user-reported follow-up on the fix above, fixed):** the "Known gap" this section used to note — Jodit appends dialogs and toolbar-dropdown popups (search & replace, image/link properties, font-size list, paragraph format, …) directly to `document.body` (`Dialog.destination` / `getPopupViewRoot` in jodit core), outside the CSS-variable wrapper's DOM subtree, so they kept rendering in Jodit's default (light, unthemed) styling even in dark mode — was reported again as "hovering [in the] editor is not following WCAG standards." Traced via `node_modules/jodit/es2021/jodit.css`: the main toolbar's own `:hover` rule (`.jodit_theme_dark .jodit-toolbar-button:hover`) already clears AA/AA-non-text comfortably once `--jd-dark-background-color`/`--jd-dark-icon-color` are mapped (verified numerically — computed contrast ~10:1+ across all 8 brands, not touched), so the actual gap was specifically the portalled popups never inheriting `themeVars` at all. Fixed by wiring Jodit's own `config.popupRoot` (a supported, documented option — `node_modules/jodit/esm/config.d.ts`: `popupRoot: Nullable<HTMLElement>`) to the wrapper `<Box>`'s own DOM node via a callback ref (`useState<HTMLElement | null>` + `ref={setPopupRoot}` on the `Box`), so `Dialog.destination` resolves to the themed wrapper instead of `document.body` and every popup/dialog now inherits the same CSS custom properties as the toolbar/canvas. Regression test: `Editor.test.tsx` (mocks `jodit-react` to assert `config.popupRoot` is a real DOM node, not `null`/`document.body`). One TS gotcha hit while wiring this: adding a literal `popupRoot` key alongside `...config` (typed `DeepPartial<Config>`, Jodit's huge recursive config type) triggered `TS2589: Type instantiation is excessively deep` — worked around by spreading `config` as `Record<string, unknown>` before the final `as EditorProps["config"]` assertion, since the plain literal-plus-spread pattern is otherwise unaffected (see comment in `Editor.tsx`).
-- **Editor dialog inputs/search-panel/button-hover still unthemed (QA follow-up round, fixed):** the
-  `popupRoot` fix above got popups into the themed DOM subtree, but 3 more Jodit CSS variables were
-  still unmapped: `--jd-color-panel` (search & replace box background — only set in the light
-  branch, so dark mode fell to Jodit's own `#f9f9f9`, a near-white panel), `--jd-color-white` /
-  `--jd-color-gray` (`.jodit-ui-input__input` / `.jodit-ui-select__input` background — Jodit's own
-  raw white default, unmapped in either mode; `-gray` is what the `_theme_dark`-suffixed variant
-  reads instead of `-white`, and dialogs don't reliably get that modifier class). Traced each via
-  `node_modules/jodit/es2021/jodit.css` line-by-line before touching anything. Also found (via a
-  throwaway jest contrast computation, not assumed): the toolbar/dialog-button hover fill and the
-  `.jodit-select`/`.jodit-input` background both already mapped to `--jd-dark-background-ligher:
-  colors.backgroundColor.muted` — computed at ~1.3:1 against the canvas, a near-miss that had
-  actually shipped (both values sit within ~11 lightness points of each other down near L7-18, where
-  WCAG contrast collapses non-linearly) — this was the QA-reported "Insert button illegible on
-  hover." Fixed in `joditThemeVars.ts`: `--jd-color-panel` moved into `shared` (role-stable, same
-  `backgroundColor.secondary` expression already correct for light); `--jd-color-white:
-  background[50]` added to `shared`; `--jd-color-gray: background[50]` added to the dark branch;
-  `--jd-dark-background-ligher` changed to `background[900]` (this palette's dark-mode "bright
-  highlight" rung, ~9.7-10.7:1 against the canvas across brands — verified before applying, not
-  guessed). Confirmed via `node_modules/jodit/es2021/jodit.css` that `.jodit_theme_dark` /
-  `.jodit-dialog_theme_dark` already hardcode `--jd-color-border: #6b6b6b` themselves (a Jodit-owned
-  override we can't/don't need to touch), so this fix only had to cover panel/input backgrounds and
-  the hover fill. Regression tests added to `joditThemeVars.test.ts`.
-- Masked-input blur must not discard a valid value. `isMaskComplete()` only recognises numeric/`a` tokens, so text month formats (e.g. `MMM d, yyyy`) never look "complete" — `handleInputBlur`/`handleInputFocus` therefore keep any value that `parseValidatedValue()` can parse to a valid date, and only `requestClose(null)` (clear) on empty/unparseable input. The Clear button and emptied-mask paths remain the explicit ways to clear. Regression: `SingleDatePicker.blur.test.tsx`.
-
-## Migration notes
-
-- DatePicker public export moved: `DatePicker/DatePicker` → `DatePicker/ThemeDatePicker` (exported as `DatePicker` from `src/index.ts`)
-- Split into Single/Range/Time picker variants under the same folder
-- Picker tests build their Chakra theme from `Theme/tokens/brands/lavender/palette.light` (was `Theme/Default/palette`)

package/.cursor/modules/inputs-select/MODULE.md

@@ -1,27 +0,0 @@
-# Select & Search
-
-## Purpose
-
-Select, SearchSelect, SelectSearch, MultiSelect, Dropdown, Search.
-
-## Key paths
-
-- `src/Components/Select/`, `SearchSelect/`, `SelectSearch/`, `MultiSelect/`, `Dropdown/`, `Search/`
-
-## Key rules
-
-- SearchSelect has performance tests; virtualize for large lists
-- Dropdown and SearchSelect main options menu are portaled to `<body>` (`position: fixed`) and clamp to the viewport — right-align/flip above when near edges
-- `insideSelect` prefix: mutually exclusive with main dropdown; menu uses `position: fixed`, flips above/below based on viewport space, and re-anchors on scroll/resize; supports `placeholder` when no value
-
-## Dark mode
-
-SearchSelect and SelectSearch source every color from `useCustomTheme()` or a palette-backed Chakra scale literal — no hex in source — so they follow the active light/dark palette.
-
-- Menu/panel surfaces use `colors.background[50]`, never `colors.white` — `white` is a foreground token (label on a filled button) and stays white in dark. The portaled menus are no exception: a portal escapes the DOM, not the theme
-- Chakra scale literals (`gray.300`) are palette-backed — the Chakra theme's `colors` *is* the palette — but the literal `bg="white"` hits the same foreground-token trap as `colors.white`
-- Lucide icons default to `currentColor` (a bare `<ChevronDown />` inherits the wrapper's `color`), but an explicit `color` prop is a raw CSS string — a scale name like `"gray.500"` won't resolve there; pass a token value
-- Known gap: SearchSelect's "Remove All" X passes `colors.black`, which is untouched in dark, on a `gray[50]` control (L10 in dark) — near-invisible; needs a text token
-- Control borders (`MultiSelect`, `Select.styles`, `SelectSearch`) bumped `boxborder` step [500]/[700] to **[800]**: WCAG 1.4.11 needs a 3:1 contrast ratio against any named surface up to `muted` (lightest) — [500]/[700] failed there, [800] clears all with margin (see inline comments at each call site)
-- Known behavior change: SearchSelect's inside-select placeholder text dropped the `theme.colors.placeholder?.[500] ?? theme.colors.gray[500]` fallback for a flat `theme.colors.gray[500]` — still a valid token, but only the lavender brand defines a distinct `placeholder` scale (other brands inherit it via spread), so lavender's placeholder text loses its tint and now renders plain gray
-- SearchSelect's "Remove All" tooltip dropped its explicit `bg`/`color` overrides, now rendering with ToolTip's own default styling instead of a forced `gray[600]`/`white`

package/.cursor/modules/inputs-toggle/MODULE.md

@@ -1,18 +0,0 @@
-# Toggles
-
-## Purpose
-
-Checkbox, RadioButton, Switch, Slider, Toggle/TableToggle.
-
-## Key paths
-
-- `src/Components/Checkbox/`, `RadioButton/`, `Switch/`, `Slider/`, `Toggle/`
-
-## Key rules
-
-- RadioButtonGroup for grouped radios
-
-## Dark-mode / contrast fixes
-
-- `Checkbox`: label tooltip now uses the shared `ToolTip` component instead of raw Chakra `Tooltip` with hardcoded `gray[600]`/`white` — `ToolTip` resolves a dark-mode-aware surface itself.
-- `Toggle/TableToggle`: selected-tab label color changed from `theme.colors.black` (mode-invariant) to `theme.colors.text[900]` (mode-adaptive). Real bug fix: `black` was rendered on `background[50]`, which is near-black in dark mode — black-on-near-black was invisible; `text[900]` flips to near-white in dark mode.

package/.cursor/modules/kanban/MODULE.md

@@ -1,22 +0,0 @@
-# Kanban
-
-## Purpose
-
-KanbanBoard with drag-and-drop columns and KanbanActions.
-
-## Key paths
-
-- `src/Components/KanbanBoard/`, `KanbanActions/`
-- Tests: `KanbanBoard.test.tsx`, `AccountCard.test.tsx`
-
-## Key rules
-
-- Uses @hello-pangea/dnd; MeasuredItem for layout
-
-## Dark mode
-
-- **KanbanBoard.test.tsx** mocked theme extended with a full `secondary` ramp (`600`-`900`) and
-  `backgroundColor.main`, for parity with other components' test mocks in this refactor pass.
-  **Known gap:** neither field is actually read by `KanbanBoard.tsx` or its subcomponents today —
-  this is inert test-fixture parity, not new dark-mode test coverage. KanbanBoard itself was not
-  touched in this pass.