@godxjp/ui 21.0.0 → 23.0.0

package/docs/roadmap/parity-audit-data-entry.md

@@ -1,6 +1,12 @@
 # Ant Design parity — `data-entry` group
 
 > Audit pass, read-only, 2026-09-10. Method and ledger format: `antd-parity.md` §0 / §2.
+> **Cập nhật 11/09/2026 — `Select` (§2.1).** Chủ dự án yêu cầu Select bám sát Ant Design 6, nên
+> nhiều dòng `WONT-PORT` / `COVERED-ELSEWHERE` bên dưới ĐÃ BỊ ĐẢO và nay là `PRESENT`. Lý do cũ
+> không sai về kỹ thuật; nó chỉ không còn là quyết định hiện hành. Hai dòng KHÔNG đảo, và vì sao:
+> `variant: "underlined"` (docs/DESIGN-AUTHORITY.md nêu đích danh: SmartHR vẽ ô kín — đó là quyết
+> định của design authority, không phải của bản kiểm này) và `virtual` (vẫn thiếu — xem dòng của nó).
+>
 > Skipped by instruction: `TreeSelect`, `Segmented`, `TagInput` chip rendering, everything chat-shaped
 > (`ChatComposer`, `ChatSuggestion`). 45 catalog entries carry `group: "data-entry"`.
 
@@ -31,8 +37,9 @@ The five that matter, in order:
 3. **No option-list virtualization anywhere in `src/`** (`grep -rl 'virtual\|useVirtualizer\|react-window\|@tanstack/react-virtual' src/` → nothing).
    antd `Select virtual` is on by default; a 5 000-row `Select`/`Cascader` here renders 5 000 DOM
    nodes. Same root cause as the missing `List` in `list-masonry.md`. **P1.**
-4. **`Slider` never exposes a formatted value to assistive tech** — `tooltip.formatter` paints an
-   `aria-hidden` bubble and no `aria-valuetext`, so a ¥/%/件 slider announces a bare number. **P1 a11y.**
+4. ~~**`Slider` never exposes a formatted value to assistive tech.**~~ CLOSED — `tooltip.formatter`
+   is now also the thumb's `aria-valuetext` (`slider.tsx`, `slider-antd.test.tsx`), landed with the
+   move to react-aria-components.
 5. **`ColorPicker` is a native `<input type="color">` + hex box** and is the one control in the group
    with no `size`/`status`/`variant`/`allowClear`/`readOnly`, and no `presets`. It cannot express a
    brand palette, which is the ordinary enterprise use. **P1.**
@@ -41,9 +48,16 @@ The five that matter, in order:
 
 `Input` · `Textarea` · `PasswordInput` · `InputOTP` · `Switch` · `Checkbox` · `Radio` · `Field` ·
 `Form` / `FormField` / `FormErrors` / `FormRoot` / `FormFieldControl` / `FormFieldArray` /
-`useZodForm` · `Toggle` / `ToggleGroup` (they *are* the coverage for antd `CheckableTag`) ·
-`MonthPicker` / `MonthRangePicker` · `TimeRangePicker` · `UploadCropDialog` (antd has no
-counterpart — it documents `antd-img-crop` as a third-party add-on).
+`useZodForm` · `Toggle` / `ToggleGroup` (they _are_ the coverage for antd `CheckableTag`) ·
+`TimeRangePicker` · `UploadCropDialog` (antd has no counterpart — it documents `antd-img-crop` as a
+third-party add-on).
+
+`MonthPicker` / `MonthRangePicker` used to be listed here as "fully aligned". They were not: each
+was a hand copy of `DatePicker` / `DateRangePicker` carrying four contracts the original had right —
+a `disabled` picker that still opened, bounds that greyed a chevron and clamped nothing, an
+unhandled Enter, and a non-ISO `name`. Reading them against ANT found nothing, because their
+divergence was from the component beside them. They were merged into `DatePicker` in 22.0.0
+(`picker="month"` / `range picker="month"`).
 
 `Command` / `CommandPalette` / `BranchScopePicker` have **no Ant Design counterpart at all**
 (namethatui: "command palette / command menu"); there is nothing to diff. `AutoComplete` is
@@ -58,96 +72,107 @@ counterpart — it documents `antd-img-crop` as a third-party add-on).
 
 `src/props/components/data-entry.prop.ts:941-1142`, `src/components/data-entry/search-select.tsx`.
 
-| Ant Design prop / behaviour | Status | Evidence | Verdict |
-| --- | --- | --- | --- |
-| `virtual` — virtualized option list (default ON in antd) | `MISSING` | `grep -rl "virtual\|useVirtualizer\|react-window\|@tanstack/react-virtual" src/` → no files | Add `virtual?: boolean` + a windowed list. Shared work with `List` (`list-masonry.md`) — do it once. |
-| `fieldNames` — map `{label,value,options}` onto foreign row shapes | `MISSING` | `grep -n fieldNames src/props/components/data-entry.prop.ts` → only `:1281` (Cascader), `:1362` (TreeSelect) | Add `fieldNames?: TreeFieldNamesProp`-shaped sibling. The spelling already exists on two neighbours; a Select that cannot eat `{id,name}` is the odd one out. |
-| `labelInValue` — report `{value,label}` instead of a bare value | `COVERED-ELSEWHERE` | `onValueChange?: (value, option?)` — `:1091`, `:1110` | The option already rides the callback. No second dialect. |
-| `optionFilterProp` / `optionLabelProp` | `COVERED-ELSEWHERE` | `filterOption` `:1012`, `labelRender` `:954`, `optionRender` `:1031` | Function form is strictly more expressive than a prop-name string. |
-| `maxTagTextLength` — truncate each chip's text | `WONT-PORT` | trigger is a `<button>` with collapsed labels, `:1096-1104` | A character-count truncation is a text contract; use `maxTagCount` + `maxTagPlaceholder`, or CSS. |
-| `listHeight` — popup max height in px | `WONT-PORT` | `search-select.tsx:534` uses `collisionPadding` + available height | Pixel height is a design knob → token (`--select-popup-*`), cardinal rule #44. |
-| `placement` (`bottomLeft`…) | `COVERED-ELSEWHERE` | Radix `PopoverContent` collision flip, `search-select.tsx:529-534` | Auto-placement beats a manual physical spelling (ground rule #4). |
-| `suffixIcon` / `removeIcon` / `loadingIcon` | `WONT-PORT` | `allowClear` object form already carries `clearIcon` — `src/props/vocabulary/shared.prop.ts:105` | Icon-per-slot props are a token/`allowClear` job, not four more props. |
-| `getPopupContainer` / `styles` / `classNames` / `popupClassName` | `WONT-PORT` | ground rule #4 | Inline-style twins and portal escape hatches. |
-| `tagRender` in `mode="multiple"` | `WONT-PORT` | `:1096-1104` states the reason verbatim (button-in-button) | Documented refusal; `TagInput` owns `tagRender` where chips are legal. |
-| `onPopupScroll` | `COVERED-ELSEWHERE` | built-in infinite scroll + `renderLoadMore` `:1062` | |
-| `defaultActiveFirstOption` | `MISSING` | `grep -n defaultActiveFirstOption src/` → nothing | P2. Add as `defaultActiveFirstOption?: boolean`; a search box that pre-highlights row 1 makes Enter a one-key pick. |
-| `onInputKeyDown` | `MISSING` | grep → nothing | P2. Real for "Enter creates a new record" flows. |
-| `maxTagCount: "responsive"` | `WONT-PORT` | `src/props/vocabulary/shared.prop.ts:109-113` documents the refusal | Container queries instead. Already recorded. |
-| `variant: "underlined"` | `WONT-PORT` | `src/props/vocabulary/interaction.prop.ts:126-130` documents the refusal | SmartHR draws full boxes. Already recorded. |
-| `onSelect` / `onDeselect` / `maxTagPlaceholder` **exist but are undocumented** | `MISSING` (catalog) | props at `:1093`, `:1112-1114`, `:1124`; `sed -n '5560,5990p' mcp/src/data/components.ts \| grep -n "onSelect\|onDeselect\|maxTagPlaceholder"` → **no match** | Catalog drift: three shipped props the MCP never tells a consumer about. Add three catalog rows (`godxjp-ui-mcp-catalog-sync`). |
+| Ant Design prop / behaviour                                                    | Status              | Evidence                                                                                                                                                      | Verdict                                                                                                                                                                                                                                                            |
+| ------------------------------------------------------------------------------ | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `virtual` — virtualized option list (default ON in antd)                       | `MISSING`           | `grep -rl "virtual\|useVirtualizer\|react-window\|@tanstack/react-virtual" src/` → no files                                                                   | Add `virtual?: boolean` + a windowed list. Shared work with `List` (`list-masonry.md`) — do it once.                                                                                                                                                               |
+| `fieldNames` — map `{label,value,options}` onto foreign row shapes             | `PRESENT`           | `SelectFieldNamesProp`; `src/lib/select-options.ts` normalises rows, groups and foreign keys into one list for both branches                                  | Done. Rows in a foreign shape need a cast at the call site, exactly as Cascader's and TreeSelect's do.                                                                                                                                                             |
+| `labelInValue` — report `{value,label}` instead of a bare value                | `PRESENT`           | `SelectLabeledValueProp`; the adapter in `select.tsx` translates it in and out                                                                                | Done. The earlier "no second dialect" ruling is REVERSED: the option riding the callback does not help the async EDIT form, which holds `{value,label}` and no option list yet. Labels that arrive on the value join the option list so the trigger can show them. |
+| `optionFilterProp`                                                             | `PRESENT`           | `SearchSelectBaseProp.optionFilterProp` + `showSearch.optionFilterProp`                                                                                       | Done. The function form is still more expressive, but naming one field is the two-word answer to the common case. `optionLabelProp` stays COVERED-ELSEWHERE (`labelRender`).                                                                                       |
+| `maxTagTextLength` — truncate each chip's text                                 | `PRESENT`           | `chipLabel()` in `search-select.tsx`; test `select-antd-tags.test.tsx`                                                                                        | Done. Cuts what the TRIGGER shows; the value keeps its whole label.                                                                                                                                                                                                |
+| `listHeight` — popup max height in px                                          | `PRESENT`           | writes `--select-content-max-height` / `--search-select-list-max-height` inline                                                                               | Done, and it does NOT break rule #44: the height stays a token, and `listHeight` overrides that token for one instance — the same shape `popupMatchSelectWidth`'s number already had.                                                                              |
+| `placement` (`bottomLeft`…)                                                    | `PRESENT`           | `SelectPlacementProp` — `bottomStart` / `bottomEnd` / `topStart` / `topEnd`                                                                                   | Done, spelled LOGICALLY (the DESIGN-AUTHORITY override antd's physical names get everywhere else). Auto-placement with collision flipping is still the default.                                                                                                    |
+| `suffixIcon` / `prefix`                                                        | `PRESENT`           | both branches; `suffixIcon={null}` removes the indicator (antd's own replacement for `showArrow`)                                                             | Done. `removeIcon` / `loadingIcon` stay WONT-PORT: `allowClear`'s object form already carries an icon, and the spinner is a token.                                                                                                                                 |
+| `getPopupContainer` / `styles` / `classNames` / `popupClassName`               | `WONT-PORT`         | ground rule #4                                                                                                                                                | Inline-style twins and portal escape hatches.                                                                                                                                                                                                                      |
+| `tagRender` in `mode="multiple"`                                               | `WONT-PORT`         | `:1096-1104` states the reason verbatim (button-in-button)                                                                                                    | Documented refusal; `TagInput` owns `tagRender` where chips are legal.                                                                                                                                                                                             |
+| `onPopupScroll`                                                                | `PRESENT`           | fires BESIDE the built-in infinite scroll, never instead of it                                                                                                | Done. The built-in pagination and `renderLoadMore` remain the reason most call sites need neither.                                                                                                                                                                 |
+| `defaultActiveFirstOption`                                                     | `MISSING`           | `grep -n defaultActiveFirstOption src/` → nothing                                                                                                             | P2. Add as `defaultActiveFirstOption?: boolean`; a search box that pre-highlights row 1 makes Enter a one-key pick.                                                                                                                                                |
+| `onInputKeyDown`                                                               | `MISSING`           | grep → nothing                                                                                                                                                | P2. Real for "Enter creates a new record" flows.                                                                                                                                                                                                                   |
+| `maxTagCount: "responsive"`                                                    | `WONT-PORT`         | `src/props/vocabulary/shared.prop.ts:109-113` documents the refusal                                                                                           | Container queries instead. Already recorded.                                                                                                                                                                                                                       |
+| `variant: "underlined"`                                                        | `WONT-PORT`         | `src/props/vocabulary/interaction.prop.ts:126-130` documents the refusal                                                                                      | SmartHR draws full boxes. Already recorded.                                                                                                                                                                                                                        |
+| `onSelect` / `onDeselect` / `maxTagPlaceholder` **exist but are undocumented** | `MISSING` (catalog) | props at `:1093`, `:1112-1114`, `:1124`; `sed -n '5560,5990p' mcp/src/data/components.ts \| grep -n "onSelect\|onDeselect\|maxTagPlaceholder"` → **no match** | Catalog drift: three shipped props the MCP never tells a consumer about. Add three catalog rows (`godxjp-ui-mcp-catalog-sync`).                                                                                                                                    |
 
 ### 2.2 `Cascader` — `CascaderProp` `src/props/components/data-entry.prop.ts:1253-1330`
 
-| Ant Design prop / behaviour | Status | Evidence | Verdict |
-| --- | --- | --- | --- |
-| `showSearch` **object form** — `{filter, sort, limit, render, matchInputWidth}` | `MISSING` | `showSearch?: boolean` only, `:1263`; search runs `filterTreeOptions(options, search)` uncapped, `cascader.tsx:389-393` | Add `filterOption` + `filterSort` + a result cap, spelled as Select already spells them (`:1012`, `:1017`) — **not** a nested antd-shaped `showSearch` object. antd's own `limit` default is 50; here a 5 000-leaf tree renders every match. |
-| `expandIcon` | `WONT-PORT` | no grep hit | Token (`--cascader-expand-*`), rule #44. |
-| `Cascader.Panel` — the picker without its trigger | `MISSING` | grep `CascaderPanel` → nothing | P2. Real for a "browse the catalogue" page. Extend `Cascader`, do not add a component. |
-| `maxTagTextLength` | `WONT-PORT` | same reasoning as Select | |
-| `suffixIcon` / `removeIcon` / `prefix` / `loadingIcon` / `popupRender` / `getPopupContainer` / `styles` | `WONT-PORT` | ground rule #4 | |
-| `placement` | `COVERED-ELSEWHERE` | Radix `PopoverContent align="start"`, `cascader.tsx:555` | |
-| `tagRender` | `WONT-PORT` | button-in-button, same as Select | |
-| `virtual` | `MISSING` | no virtualization in `src/` | Same P1 row as Select. |
+| Ant Design prop / behaviour                                                                             | Status              | Evidence                                                                                                                | Verdict                                                                                                                                                                                                                                      |
+| ------------------------------------------------------------------------------------------------------- | ------------------- | ----------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `showSearch` **object form** — `{filter, sort, limit, render, matchInputWidth}`                         | `MISSING`           | `showSearch?: boolean` only, `:1263`; search runs `filterTreeOptions(options, search)` uncapped, `cascader.tsx:389-393` | Add `filterOption` + `filterSort` + a result cap, spelled as Select already spells them (`:1012`, `:1017`) — **not** a nested antd-shaped `showSearch` object. antd's own `limit` default is 50; here a 5 000-leaf tree renders every match. |
+| `expandIcon`                                                                                            | `WONT-PORT`         | no grep hit                                                                                                             | Token (`--cascader-expand-*`), rule #44.                                                                                                                                                                                                     |
+| `Cascader.Panel` — the picker without its trigger                                                       | `MISSING`           | grep `CascaderPanel` → nothing                                                                                          | P2. Real for a "browse the catalogue" page. Extend `Cascader`, do not add a component.                                                                                                                                                       |
+| `maxTagTextLength`                                                                                      | `WONT-PORT`         | same reasoning as Select                                                                                                |                                                                                                                                                                                                                                              |
+| `suffixIcon` / `removeIcon` / `prefix` / `loadingIcon` / `popupRender` / `getPopupContainer` / `styles` | `WONT-PORT`         | ground rule #4                                                                                                          |                                                                                                                                                                                                                                              |
+| `placement`                                                                                             | `COVERED-ELSEWHERE` | Radix `PopoverContent align="start"`, `cascader.tsx:555`                                                                |                                                                                                                                                                                                                                              |
+| `tagRender`                                                                                             | `WONT-PORT`         | button-in-button, same as Select                                                                                        |                                                                                                                                                                                                                                              |
+| `virtual`                                                                                               | `MISSING`           | no virtualization in `src/`                                                                                             | Same P1 row as Select.                                                                                                                                                                                                                       |
 
 ### 2.3 `NumberInput` — `NumberInputProp` `:228-282` · `src/components/data-entry/number-input.tsx`
 
-| Ant Design prop / behaviour | Status | Evidence | Verdict |
-| --- | --- | --- | --- |
-| **locale round-trip** (antd `decimalSeparator` exists precisely for this) | `MISSING` — **defect** | Formats with `new Intl.NumberFormat(locale, …)` `number-input.tsx:100`; parses with `raw.normalize("NFKC").replace(/,/g, "")` `:41`; `handleBlur` re-parses the displayed draft `:220`. Measured: `Intl.NumberFormat("vi",{useGrouping:false}).format(1.5)` → `"1,5"`; `Number("1,5".normalize("NFKC").replace(/,/g,""))` → **`15`**. | **P0.** Derive the locale's decimal + group separators from `Intl.NumberFormat(locale).formatToParts()` and normalise against *those*, instead of hardcoding `,` = thousands. Keep the NFKC 全角 fold — it is correct and load-bearing for `ja`. A regression test per shipped locale (`en`, `ja`, `vi`) is the acceptance. |
-| `stringMode` — string in/out for values past `Number.MAX_SAFE_INTEGER` or exact decimals | `MISSING` | grep `stringMode` → nothing; value type is `number \| null` `:180-182` | P1. Money and 13-digit ids are the ordinary enterprise case; `roundTo` `:45-49` mitigates FP drift but cannot fix range. Add as an opt-in that widens the triad to `string`. |
-| `onStep` — fired on stepper / arrow / wheel with the direction | `MISSING` | grep `onStep` → nothing | P2. Add `onStep?: (value, info: { offset, type: "up" \| "down" }) => void`. |
-| `addonBefore` / `addonAfter` | `WONT-PORT` | deprecated in antd itself (use `Space.Compact`) | `prefix`/`suffix` present `:215-217`. |
-| `onPressEnter` | `COVERED-ELSEWHERE` | commit-on-Enter is already the behaviour, `:237` | |
-| `decimalSeparator` as an explicit prop | `WONT-PORT` | should follow the locale, not a prop | Fixing the round-trip above removes the need. |
-
-### 2.4 `Slider` — `SliderProp` `:547-568` · `src/components/data-entry/slider.tsx`
-
-| Ant Design prop / behaviour | Status | Evidence | Verdict |
-| --- | --- | --- | --- |
-| **`aria-valuetext` mirroring `tooltip.formatter`** (rc-slider `ariaValueTextFormatterForHandle`) | `MISSING` — **a11y** | `tooltipContent` returns the bare number `slider.tsx:33,35`; the bubble is `aria-hidden` `:152`; the `Thumb` `:138-157` sets no `aria-valuetext` | **P1.** A `¥50,000` / `3 件` slider announces "50000". Feed the resolved `tooltip.formatter` (or `Intl.NumberFormat`) into `aria-valuetext`. |
-| default tooltip / mark text is not `Intl`-formatted | `MISSING` — i18n | `tooltipContent` `:33` returns `value` verbatim; no `Intl.NumberFormat` in the file | P2 (same fix as the row above). |
-| `onChangeComplete` | `RENAMED` | Radix `onValueCommit`, inherited via `React.ComponentPropsWithoutRef<typeof SliderPrimitive.Root>` `:547` | No work. Record both names in the catalog. |
-| `vertical` | `RENAMED` | Radix `orientation="vertical"`, `slider.tsx:55,88,112` | No work. |
-| `reverse` | `PRESENT` (aliased) | `inverted ?? reverse`, `slider.tsx:115` | |
-| `keyboard: false` | `WONT-PORT` | — | Removing keyboard operation from a `role="slider"` fails WCAG 2.1.1. |
-| `range: { draggableTrack }` — drag the whole span | `MISSING` | grep `draggableTrack` → nothing; Radix has no equivalent | P2. |
-| `tooltip.placement` / `getPopupContainer` / `autoAdjustOverflow` | `WONT-PORT` | ground rule #4 | Token + collision-aware positioning. |
+| Ant Design prop / behaviour                                                              | Status                 | Evidence                                                                                                                                                                                                                                                                                                                              | Verdict                                                                                                                                                                                                                                                                                                                     |
+| ---------------------------------------------------------------------------------------- | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **locale round-trip** (antd `decimalSeparator` exists precisely for this)                | `MISSING` — **defect** | Formats with `new Intl.NumberFormat(locale, …)` `number-input.tsx:100`; parses with `raw.normalize("NFKC").replace(/,/g, "")` `:41`; `handleBlur` re-parses the displayed draft `:220`. Measured: `Intl.NumberFormat("vi",{useGrouping:false}).format(1.5)` → `"1,5"`; `Number("1,5".normalize("NFKC").replace(/,/g,""))` → **`15`**. | **P0.** Derive the locale's decimal + group separators from `Intl.NumberFormat(locale).formatToParts()` and normalise against _those_, instead of hardcoding `,` = thousands. Keep the NFKC 全角 fold — it is correct and load-bearing for `ja`. A regression test per shipped locale (`en`, `ja`, `vi`) is the acceptance. |
+| `stringMode` — string in/out for values past `Number.MAX_SAFE_INTEGER` or exact decimals | `MISSING`              | grep `stringMode` → nothing; value type is `number \| null` `:180-182`                                                                                                                                                                                                                                                                | P1. Money and 13-digit ids are the ordinary enterprise case; `roundTo` `:45-49` mitigates FP drift but cannot fix range. Add as an opt-in that widens the triad to `string`.                                                                                                                                                |
+| `onStep` — fired on stepper / arrow / wheel with the direction                           | `MISSING`              | grep `onStep` → nothing                                                                                                                                                                                                                                                                                                               | P2. Add `onStep?: (value, info: { offset, type: "up" \| "down" }) => void`.                                                                                                                                                                                                                                                 |
+| `addonBefore` / `addonAfter`                                                             | `WONT-PORT`            | deprecated in antd itself (use `Space.Compact`)                                                                                                                                                                                                                                                                                       | `prefix`/`suffix` present `:215-217`.                                                                                                                                                                                                                                                                                       |
+| `onPressEnter`                                                                           | `COVERED-ELSEWHERE`    | commit-on-Enter is already the behaviour, `:237`                                                                                                                                                                                                                                                                                      |                                                                                                                                                                                                                                                                                                                             |
+| `decimalSeparator` as an explicit prop                                                   | `WONT-PORT`            | should follow the locale, not a prop                                                                                                                                                                                                                                                                                                  | Fixing the round-trip above removes the need.                                                                                                                                                                                                                                                                               |
+
+### 2.4 `Slider` — `SliderProp` · `src/components/data-entry/slider.tsx`
+
+CLOSED. `Slider` moved to `react-aria-components` and took the antd 6 API with it, so every row
+this table used to hold is now either `PRESENT` or a recorded non-port:
+
+| Ant Design prop / behaviour                                              | Status                                                                                                    |
+| ------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------- |
+| `aria-valuetext` mirroring `tooltip.formatter`                           | `PRESENT` — a string/number `formatter` result is written onto the thumb's input                          |
+| `value`/`defaultValue`/`onChange`/`onChangeComplete` as antd spells them | `PRESENT` — the Radix-era `number[]` + `onValueChange`/`onValueCommit` spelling still compiles            |
+| `step={null}`, `marks` object form, `dots`, `included`, `vertical`       | `PRESENT`                                                                                                 |
+| `range: { editable, minCount, maxCount, draggableTrack }`                | `PRESENT`                                                                                                 |
+| `disabled` as `boolean[]`                                                | `PRESENT`                                                                                                 |
+| `tooltip.placement` / `autoAdjustOverflow`                               | `PRESENT` — logical sides, flip measured against the thumb's rect                                         |
+| `tooltip.getPopupContainer`                                              | `WONT-PORT` — the bubble lives inside the thumb; nothing is portalled, so there is no container to choose |
+| `keyboard: false`                                                        | `WONT-PORT` — removing keyboard operation from a `role="slider"` fails WCAG 2.1.1                         |
+| `classNames` / `styles` semantic slots                                   | `WONT-PORT` — docs/WHAT-BELONGS-HERE.md, "lỗ kiểu dáng tự do"                                             |
+| default tooltip text is not `Intl`-formatted                             | `MISSING` — P2, unchanged: pass `tooltip.formatter` for ¥/%/件                                            |
 
 ### 2.5 `ColorPicker` — `ColorPickerProp` `:893-908` · `src/components/data-entry/color-picker.tsx` (114 lines)
 
-| Ant Design prop / behaviour | Status | Evidence | Verdict |
-| --- | --- | --- | --- |
-| `presets` — named swatch groups | `MISSING` | whole file read; only `<input type="color">` `color-picker.tsx:84-93` + a hex `Input` `:96-108` | **P1.** A tenant/brand palette is the ordinary case; today the consumer hand-rolls a swatch row of `Button`s beside it. |
-| `size` / `status` / `variant` | `MISSING` | prop type `:893-908` has none of the three; every other control in the group carries all three | **P1 (consistency).** A `ColorPicker` cannot line up with the `Input` next to it in a form row, and cannot paint a validation error. |
-| `allowClear` + `onClear` | `MISSING` | `AllowClearProp` not imported into `ColorPickerProp` `:893` | P2. The value can legitimately be `""` `:46` but nothing clears it back. |
-| `readOnly` | `MISSING` | `disabled` only `:902` | P2. `Select`/`Cascader`/`TagInput`/`Transfer` all state a `readOnly` contract; this one does not. |
-| `format` / `defaultFormat` / `onFormatChange` (rgb/hex/hsb) | `MISSING` | `HEX_PATTERN` `:14` is the only accepted shape | P2. |
-| `disabledAlpha` / alpha channel | `WONT-PORT` | `<input type="color">` has no alpha | Would require replacing the native panel. Not worth it unless `presets` forces a custom panel anyway — decide the two together. |
-| `mode: "gradient"` | `WONT-PORT` | — | A gradient editor is a different control. |
-| `showText` | `MISSING` | `showHexInput` `:38` shows an *editable* hex box, not a read-only label | P2 — `showHexInput` is the house spelling and covers the intent; record as `RENAMED` if the read-only variant is not wanted. |
-| `panelRender` / `trigger` / `arrow` / `placement` / `destroyOnHidden` | `WONT-PORT` | native panel; ground rule #4 | |
-
-### 2.6 `DatePicker` / `DateRangePicker` — `:653-716`, `:770-804` (+ `PickerChromeProp` `:635-647`)
+| Ant Design prop / behaviour                                           | Status      | Evidence                                                                                        | Verdict                                                                                                                              |
+| --------------------------------------------------------------------- | ----------- | ----------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
+| `presets` — named swatch groups                                       | `MISSING`   | whole file read; only `<input type="color">` `color-picker.tsx:84-93` + a hex `Input` `:96-108` | **P1.** A tenant/brand palette is the ordinary case; today the consumer hand-rolls a swatch row of `Button`s beside it.              |
+| `size` / `status` / `variant`                                         | `MISSING`   | prop type `:893-908` has none of the three; every other control in the group carries all three  | **P1 (consistency).** A `ColorPicker` cannot line up with the `Input` next to it in a form row, and cannot paint a validation error. |
+| `allowClear` + `onClear`                                              | `MISSING`   | `AllowClearProp` not imported into `ColorPickerProp` `:893`                                     | P2. The value can legitimately be `""` `:46` but nothing clears it back.                                                             |
+| `readOnly`                                                            | `MISSING`   | `disabled` only `:902`                                                                          | P2. `Select`/`Cascader`/`TagInput`/`Transfer` all state a `readOnly` contract; this one does not.                                    |
+| `format` / `defaultFormat` / `onFormatChange` (rgb/hex/hsb)           | `MISSING`   | `HEX_PATTERN` `:14` is the only accepted shape                                                  | P2.                                                                                                                                  |
+| `disabledAlpha` / alpha channel                                       | `WONT-PORT` | `<input type="color">` has no alpha                                                             | Would require replacing the native panel. Not worth it unless `presets` forces a custom panel anyway — decide the two together.      |
+| `mode: "gradient"`                                                    | `WONT-PORT` | —                                                                                               | A gradient editor is a different control.                                                                                            |
+| `showText`                                                            | `MISSING`   | `showHexInput` `:38` shows an _editable_ hex box, not a read-only label                         | P2 — `showHexInput` is the house spelling and covers the intent; record as `RENAMED` if the read-only variant is not wanted.         |
+| `panelRender` / `trigger` / `arrow` / `placement` / `destroyOnHidden` | `WONT-PORT` | native panel; ground rule #4                                                                    |                                                                                                                                      |
+
+### 2.6 `DatePicker` (one control: `picker` × `range`/`multiple`) — `data-entry.prop.ts` `DatePickerBaseProp` / `DatePickerProp` (+ `PickerChromeProp`)
+
+As of 22.0.0 this is ONE component. antd ships one `DatePicker` with `picker` plus a
+`DatePicker.RangePicker`; this library had drifted to four (`DatePicker`, `DateRangePicker`,
+`MonthPicker`, `MonthRangePicker`), three of them hand copies of the first. `picker` is the
+granularity axis and `range` the cardinality axis, so the eight combinations are one implementation.
 
 Present and correct: `format` (string | `Intl.DateTimeFormatOptions` incl. Japanese era | fn),
-`parseFormat`, `minDate`/`maxDate`, `showWeek`, `needConfirm`, `picker`, `order`, `showTime`,
-`presets`, `disabledDate`, `cellRender`, `allowClear`, `allowEmpty`, `showNow`/`showToday`,
-`inputReadOnly`, `preserveInvalidOnBlur`, `renderExtraFooter`, `placement` (logical `bottom-start`…),
-`open`/`defaultOpen`/`onOpenChange`, `multiple`, ISO native submission.
-
-| Ant Design prop / behaviour | Status | Evidence | Verdict |
-| --- | --- | --- | --- |
-| `mode` + `onPanelChange` — controlled panel level (date→month→year) | `MISSING` | `grep -rn "onPanelChange" src/` → nothing; `picker` `:663` selects the *value granularity*, not the panel level | P2. Distinct from `picker`; needed only for a picker that drives an external month/year state. |
-| `defaultPickerValue` / `pickerValue` / `onPickerValueChange` — which month the panel opens on | `MISSING` | grep → nothing | **P1.** "Open on the fiscal-year start", "open on the month of the row being edited" has no expression today; the panel always opens on the value or today. |
-| `onOk` — the confirm click | `MISSING` | grep `onOk` in `src/components/data-entry/` → nothing, although `needConfirm` `:662` renders the button | P2. `onValueChange` already fires on confirm; `onOk` is a convenience. |
-| `separator` (RangePicker) | `MISSING` | hardcoded `<ArrowRight … />`, `date-range-picker.tsx:264` | P2. RTL is handled (logical icon flip), so this is cosmetic — a token would do. |
-| `disabled: [boolean, boolean]` — lock one end of a range | `MISSING` | `disabled?: DisabledProp` (scalar) `:787` | **P1.** "The start date is fixed by the contract, only the end is editable" is a real screen and has no expression. |
-| `onCalendarChange` — fires on each end of the range | `MISSING` | grep → nothing | P2. Needed to compute a live duration while the range is half-picked. |
-| `panelRender` / `prevIcon` / `nextIcon` / `superPrevIcon` / `superNextIcon` / `suffixIcon` / `components` | `WONT-PORT` | grep → nothing; ground rule #4 | Tokens, not props. |
-| `getPopupContainer` / `styles` / `classNames` / `popupClassName` | `WONT-PORT` | ground rule #4 | |
-| `maxTagCount` for `multiple` | `MISSING` | `multiple` `:710-715` has no collapse knob, unlike `Select`/`Cascader`/`TreeSelect` which all take `MaxTagCountProp` | P2 — reuse `MaxTagCountProp` (`shared.prop.ts:113`), do not invent a spelling. |
-| `dateRender` | `RENAMED` | `cellRender` `:682` (antd renamed it too) | No work. |
+`parseFormat`, `minDate`/`maxDate`, `showWeek`, `needConfirm`, `picker`, `range`, `order`,
+`showTime`, `presets`, `disabledDate`, `cellRender`, `allowClear`, `allowEmpty`,
+`showNow`/`showToday`, `inputReadOnly`, `preserveInvalidOnBlur`, `renderExtraFooter`, `placement`
+(logical `bottom-start`…), `open`/`defaultOpen`/`onOpenChange`, `multiple`, ISO native submission
+at the granularity `picker` selects.
+
+| Ant Design prop / behaviour                                                                               | Status      | Evidence                                                                                                          | Verdict                                                                                                                                                     |
+| --------------------------------------------------------------------------------------------------------- | ----------- | ----------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `mode` + `onPanelChange` — controlled panel level (date→month→year)                                       | `MISSING`   | `grep -rn "onPanelChange" src/` → nothing; `picker` selects the _value granularity_, not the panel level          | P2. Distinct from `picker`; needed only for a picker that drives an external month/year state.                                                              |
+| `defaultPickerValue` / `pickerValue` / `onPickerValueChange` — which month the panel opens on             | `MISSING`   | grep → nothing                                                                                                    | **P1.** "Open on the fiscal-year start", "open on the month of the row being edited" has no expression today; the panel always opens on the value or today. |
+| `onOk` — the confirm click                                                                                | `MISSING`   | grep `onOk` in `src/components/data-entry/` → nothing, although `needConfirm` renders the button                  | P2. `onValueChange` already fires on confirm; `onOk` is a convenience.                                                                                      |
+| `separator` (RangePicker)                                                                                 | `MISSING`   | hardcoded `<ArrowRight … />` in the range shell of `date-picker.tsx`                                              | P2. RTL is handled (logical icon flip), so this is cosmetic — a token would do.                                                                             |
+| `disabled: [boolean, boolean]` — lock one end of a range                                                  | `MISSING`   | `disabled?: DisabledProp` (scalar) on `DatePickerBaseProp`                                                        | **P1.** "The start date is fixed by the contract, only the end is editable" is a real screen and has no expression.                                         |
+| `onCalendarChange` — fires on each end of the range                                                       | `MISSING`   | grep → nothing                                                                                                    | P2. Needed to compute a live duration while the range is half-picked.                                                                                       |
+| `panelRender` / `prevIcon` / `nextIcon` / `superPrevIcon` / `superNextIcon` / `suffixIcon` / `components` | `WONT-PORT` | grep → nothing; ground rule #4                                                                                    | Tokens, not props.                                                                                                                                          |
+| `getPopupContainer` / `styles` / `classNames` / `popupClassName`                                          | `WONT-PORT` | ground rule #4                                                                                                    |                                                                                                                                                             |
+| `maxTagCount` for `multiple`                                                                              | `MISSING`   | the `multiple` arm has no collapse knob, unlike `Select`/`Cascader`/`TreeSelect` which all take `MaxTagCountProp` | P2 — reuse `MaxTagCountProp` (`shared.prop.ts:113`), do not invent a spelling.                                                                              |
+| `dateRender`                                                                                              | `RENAMED`   | `cellRender` (antd renamed it too)                                                                                | No work.                                                                                                                                                    |
 
 ### 2.7 `TimePicker` — `TimePickerProp` `:822-877`
 
@@ -155,23 +180,23 @@ Present: `hourStep`/`minuteStep`/`secondStep`, `showSeconds`, `use12Hours`, `for
 `hideDisabledOptions`, `showNow`, `needConfirm`, `changeOnScroll`, `inputReadOnly`, `allowClear`,
 `renderExtraFooter`, canonical 24-h storage.
 
-| Ant Design prop / behaviour | Status | Evidence | Verdict |
-| --- | --- | --- | --- |
-| `cellRender` | `MISSING` | `grep -n cellRender src/components/data-entry/time-picker.tsx` → nothing | P2. Marking "already booked" times is the same need `Calendar cellRender` already serves. |
-| `onSelect` — fires per column pick, before commit | `MISSING` | grep → nothing | P2. |
-| `needConfirm` default | `PRESENT` — **deliberate divergence** | `:864-871` states it: antd defaults `true`, this library `false`, with the reason | No work; already documented. Keep. |
-| `suffixIcon` / `popupClassName` / `getPopupContainer` | `WONT-PORT` | ground rule #4 | |
+| Ant Design prop / behaviour                           | Status                                | Evidence                                                                          | Verdict                                                                                   |
+| ----------------------------------------------------- | ------------------------------------- | --------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
+| `cellRender`                                          | `MISSING`                             | `grep -n cellRender src/components/data-entry/time-picker.tsx` → nothing          | P2. Marking "already booked" times is the same need `Calendar cellRender` already serves. |
+| `onSelect` — fires per column pick, before commit     | `MISSING`                             | grep → nothing                                                                    | P2.                                                                                       |
+| `needConfirm` default                                 | `PRESENT` — **deliberate divergence** | `:864-871` states it: antd defaults `true`, this library `false`, with the reason | No work; already documented. Keep.                                                        |
+| `suffixIcon` / `popupClassName` / `getPopupContainer` | `WONT-PORT`                           | ground rule #4                                                                    |                                                                                           |
 
 ### 2.8 `Calendar` — `CalendarProp` `:585-619`
 
-| Ant Design prop / behaviour | Status | Evidence | Verdict |
-| --- | --- | --- | --- |
-| `mode: "month" \| "year"` + `onPanelChange` — the 12-month year board | `MISSING` | `grep -rn "onPanelChange\|fullCellRender" src/` → nothing; `CalendarProp` is `DayPickerProps` + footer + `width`/`bordered`/`cellRender` | P2. `MonthPicker` covers *picking* a month; it does not cover a year board a consumer can decorate. |
-| `headerRender` | `COVERED-ELSEWHERE` | `CalendarProp extends DayPickerProps` `:585` → react-day-picker `captionLayout="dropdown" \| "dropdown-months" \| "dropdown-years"` + `startMonth`/`endMonth` (used at `calendar.tsx:60-61`) | Add a `related`/usage note; no code. |
-| `validRange` | `COVERED-ELSEWHERE` | DayPicker `startMonth`/`endMonth` + `disabled`, `calendar.tsx:60-61` | |
-| `fullscreen` | `RENAMED` | `width="full"` + `bordered` `:604,616`, with the measured rationale for the split | No work. |
-| `fullCellRender` — replace the whole cell | `WONT-PORT` | `CalendarCellRenderProp` `:571-583` states the refusal: `cellRender` **wraps** `originNode` so selection state, `aria-selected`, disabled handling and the roving tabindex survive | Correct call. Record it in the catalog so nobody re-adds it. |
-| `showWeek` | `COVERED-ELSEWHERE` | DayPicker `showWeekNumber` | |
+| Ant Design prop / behaviour                                           | Status              | Evidence                                                                                                                                                                                     | Verdict                                                                                                             |
+| --------------------------------------------------------------------- | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
+| `mode: "month" \| "year"` + `onPanelChange` — the 12-month year board | `MISSING`           | `grep -rn "onPanelChange\|fullCellRender" src/` → nothing; `CalendarProp` is `DayPickerProps` + footer + `width`/`bordered`/`cellRender`                                                     | P2. `<DatePicker picker="month">` covers _picking_ a month; it does not cover a year board a consumer can decorate. |
+| `headerRender`                                                        | `COVERED-ELSEWHERE` | `CalendarProp extends DayPickerProps` `:585` → react-day-picker `captionLayout="dropdown" \| "dropdown-months" \| "dropdown-years"` + `startMonth`/`endMonth` (used at `calendar.tsx:60-61`) | Add a `related`/usage note; no code.                                                                                |
+| `validRange`                                                          | `COVERED-ELSEWHERE` | DayPicker `startMonth`/`endMonth` + `disabled`, `calendar.tsx:60-61`                                                                                                                         |                                                                                                                     |
+| `fullscreen`                                                          | `RENAMED`           | `width="full"` + `bordered` `:604,616`, with the measured rationale for the split                                                                                                            | No work.                                                                                                            |
+| `fullCellRender` — replace the whole cell                             | `WONT-PORT`         | `CalendarCellRenderProp` `:571-583` states the refusal: `cellRender` **wraps** `originNode` so selection state, `aria-selected`, disabled handling and the roving tabindex survive           | Correct call. Record it in the catalog so nobody re-adds it.                                                        |
+| `showWeek`                                                            | `COVERED-ELSEWHERE` | DayPicker `showWeekNumber`                                                                                                                                                                   |                                                                                                                     |
 
 ### 2.9 `Upload` — `UploadProp` `:1152-1234`
 
@@ -180,17 +205,17 @@ Present and unusually complete: `action`/`method`/`headers`/`data`/`withCredenti
 `maxCount`/`maxSizeBytes`, `itemRender`, `previewFile`, `onPreview`/`onDownload`/`onRemove`/`onDrop`,
 per-item progress + cancel (`upload.tsx:234-289`, `upload-request.ts:16-54`).
 
-| Ant Design prop / behaviour | Status | Evidence | Verdict |
-| --- | --- | --- | --- |
-| `customRequest` | `RENAMED` | `onUpload(file, item, context)` `:1206-1210` with an abort signal + `onProgress` `upload-types.ts:87,106` — strictly richer than antd's | No work; record both names. |
-| `listType` | `RENAMED` | `variant` `:1148-1149` (`dropzone`/`button`/`picture-card`/`picture`/`avatar`/`avatar-crop`) | No work. |
-| `fileList` / `defaultFileList` / `onChange` | `RENAMED` | the controlled triad `:1154-1156` | No work. |
-| `showUploadList` **object form** — `{showPreviewIcon, showRemoveIcon, showDownloadIcon, extra}` | `MISSING` | `showUploadList?: boolean` `:1196`, consumed as a boolean at `upload.tsx:461,644` | **P1.** "Files can be previewed but not removed" is a permissions case; today the only escape is `itemRender`, which hands the consumer the whole row and its a11y with it. Widen to `boolean \| { … }`. |
-| `iconRender` — per-status file icon | `MISSING` | `grep -n iconRender src/components/data-entry/upload.tsx` → nothing (only `PasswordInput` has one) | P2 — or `WONT-PORT` in favour of tokens; decide with the row above. |
-| `isImageUrl` — decide whether a thumbnail is an `<img>` | `MISSING` | grep → nothing; `createUploadItem` infers from `file.type` `upload-types.ts:43` | P2. Bites a `value` restored from the server with a `url` but no `mimeType`. |
-| `progress` — antd's Progress config | `WONT-PORT` | renders this library's own `Progress` `upload.tsx:866,979` | Token, rule #44. |
-| `capture` — mobile camera | `MISSING` | grep `capture` → nothing on the `<input type="file">` | P2. |
-| `styles` / `classNames` | `WONT-PORT` | ground rule #4 | |
+| Ant Design prop / behaviour                                                                     | Status      | Evidence                                                                                                                                | Verdict                                                                                                                                                                                                  |
+| ----------------------------------------------------------------------------------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `customRequest`                                                                                 | `RENAMED`   | `onUpload(file, item, context)` `:1206-1210` with an abort signal + `onProgress` `upload-types.ts:87,106` — strictly richer than antd's | No work; record both names.                                                                                                                                                                              |
+| `listType`                                                                                      | `RENAMED`   | `variant` `:1148-1149` (`dropzone`/`button`/`picture-card`/`picture`/`avatar`/`avatar-crop`)                                            | No work.                                                                                                                                                                                                 |
+| `fileList` / `defaultFileList` / `onChange`                                                     | `RENAMED`   | the controlled triad `:1154-1156`                                                                                                       | No work.                                                                                                                                                                                                 |
+| `showUploadList` **object form** — `{showPreviewIcon, showRemoveIcon, showDownloadIcon, extra}` | `MISSING`   | `showUploadList?: boolean` `:1196`, consumed as a boolean at `upload.tsx:461,644`                                                       | **P1.** "Files can be previewed but not removed" is a permissions case; today the only escape is `itemRender`, which hands the consumer the whole row and its a11y with it. Widen to `boolean \| { … }`. |
+| `iconRender` — per-status file icon                                                             | `MISSING`   | `grep -n iconRender src/components/data-entry/upload.tsx` → nothing (only `PasswordInput` has one)                                      | P2 — or `WONT-PORT` in favour of tokens; decide with the row above.                                                                                                                                      |
+| `isImageUrl` — decide whether a thumbnail is an `<img>`                                         | `MISSING`   | grep → nothing; `createUploadItem` infers from `file.type` `upload-types.ts:43`                                                         | P2. Bites a `value` restored from the server with a `url` but no `mimeType`.                                                                                                                             |
+| `progress` — antd's Progress config                                                             | `WONT-PORT` | renders this library's own `Progress` `upload.tsx:866,979`                                                                              | Token, rule #44.                                                                                                                                                                                         |
+| `capture` — mobile camera                                                                       | `MISSING`   | grep `capture` → nothing on the `<input type="file">`                                                                                   | P2.                                                                                                                                                                                                      |
+| `styles` / `classNames`                                                                         | `WONT-PORT` | ground rule #4                                                                                                                          |                                                                                                                                                                                                          |
 
 ### 2.10 `Transfer` — `TransferProp` `:1413-1459`
 
@@ -198,40 +223,40 @@ Present: `dataSource`, `targetKeys`/`defaultTargetKeys` + the `value`/`defaultVa
 `showSearch`, `render`, `filterOption`, `showSelectAll`, `oneWay`, `pagination`, `selectedKeys` +
 `onSelectChange`, `readOnly`, `name`.
 
-| Ant Design prop / behaviour | Status | Evidence | Verdict |
-| --- | --- | --- | --- |
-| `status` | `MISSING` | no `status` in `:1413-1459`; every other data-entry control takes `ControlStatusProp` (`interaction.prop.ts:117`) | **P1.** A required Transfer inside a `FormField` cannot paint its own validation error. |
-| `rowKey` | `MISSING` | `TransferItemProp` requires a literal `key` `:1405-1410` | P2. The house spelling is `getRowId` (`GetRowIdProp`, `PROPS-VOCABULARY.md` · Data collections) — reuse it, do not add `rowKey`. |
-| `footer` | `MISSING` | grep → nothing | P2. |
-| `operations` / `actions` — relabel the ⇄ buttons | `MISSING` | grep → nothing | P2. The buttons are localized via `t()`; a per-instance override ("承認する" / "取り消す") has no expression. |
-| `selectAllLabels` | `MISSING` | grep → nothing | P2. |
-| `onSearch` | `MISSING` | `showSearch` `:1434` is a boolean; no query callback | P2 — spell it `onSearchChange` (`OnSearchChangeProp`), as Select and Cascader already do. |
-| `onScroll` | `MISSING` | grep → nothing | P2. `pagination` `:1420` covers the large-list case instead. |
-| `locale` object | `COVERED-ELSEWHERE` | `t()` + the `i18n/messages/*` bundles | |
-| `listStyle` / `styles` / `classNames` | `WONT-PORT` | ground rule #4 | |
+| Ant Design prop / behaviour                      | Status              | Evidence                                                                                                          | Verdict                                                                                                                          |
+| ------------------------------------------------ | ------------------- | ----------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| `status`                                         | `MISSING`           | no `status` in `:1413-1459`; every other data-entry control takes `ControlStatusProp` (`interaction.prop.ts:117`) | **P1.** A required Transfer inside a `FormField` cannot paint its own validation error.                                          |
+| `rowKey`                                         | `MISSING`           | `TransferItemProp` requires a literal `key` `:1405-1410`                                                          | P2. The house spelling is `getRowId` (`GetRowIdProp`, `PROPS-VOCABULARY.md` · Data collections) — reuse it, do not add `rowKey`. |
+| `footer`                                         | `MISSING`           | grep → nothing                                                                                                    | P2.                                                                                                                              |
+| `operations` / `actions` — relabel the ⇄ buttons | `MISSING`           | grep → nothing                                                                                                    | P2. The buttons are localized via `t()`; a per-instance override ("承認する" / "取り消す") has no expression.                    |
+| `selectAllLabels`                                | `MISSING`           | grep → nothing                                                                                                    | P2.                                                                                                                              |
+| `onSearch`                                       | `MISSING`           | `showSearch` `:1434` is a boolean; no query callback                                                              | P2 — spell it `onSearchChange` (`OnSearchChangeProp`), as Select and Cascader already do.                                        |
+| `onScroll`                                       | `MISSING`           | grep → nothing                                                                                                    | P2. `pagination` `:1420` covers the large-list case instead.                                                                     |
+| `locale` object                                  | `COVERED-ELSEWHERE` | `t()` + the `i18n/messages/*` bundles                                                                             |                                                                                                                                  |
+| `listStyle` / `styles` / `classNames`            | `WONT-PORT`         | ground rule #4                                                                                                    |                                                                                                                                  |
 
 ### 2.11 `SearchInput` — `SearchInputProp` `:418-437` · `src/components/data-entry/search-input.tsx`
 
 This maps to antd `Input.Search`.
 
-| Ant Design prop / behaviour | Status | Evidence | Verdict |
-| --- | --- | --- | --- |
-| **`onSearch` on Enter** — commit the query immediately instead of waiting out the debounce | `MISSING` — UX | no `onKeyDown` anywhere in the file (read in full, 125 lines); `onSearch` fires only from the debounced effect `search-input.tsx:59-63` | **P1.** Pressing Enter in a search box is the universal "search now" gesture; here it does nothing and the user waits `debounce` ms. The IME guard `:43-46` is correct and must be preserved — Enter that *confirms a conversion* must not submit. |
-| `enterButton` — a visible 検索 button | `MISSING` | grep → nothing | P2. Common on JP admin screens; today the consumer puts a `Button` beside it and re-wires the query. |
-| `loading` | `MISSING` | grep → nothing; `PendingProp` exists in the vocabulary | P2. Reuse `loading?: PendingProp` as `Select` `:998` does. |
-| `size` | `MISSING` | `SearchInputProp` `:418-437` has `status` and `variant` but no `size`, while the `Input` it wraps does (`:110`) | P2 (consistency) — a `SearchInput` cannot match an `sm` toolbar row. |
-| `allowClear` | `PRESENT` (always on) | hardcoded clear button `search-input.tsx:110-121` | Fine; note it is not switchable. |
-| `searchIcon` | `WONT-PORT` | ground rule #4 | Token. |
+| Ant Design prop / behaviour                                                                | Status                | Evidence                                                                                                                                | Verdict                                                                                                                                                                                                                                            |
+| ------------------------------------------------------------------------------------------ | --------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`onSearch` on Enter** — commit the query immediately instead of waiting out the debounce | `MISSING` — UX        | no `onKeyDown` anywhere in the file (read in full, 125 lines); `onSearch` fires only from the debounced effect `search-input.tsx:59-63` | **P1.** Pressing Enter in a search box is the universal "search now" gesture; here it does nothing and the user waits `debounce` ms. The IME guard `:43-46` is correct and must be preserved — Enter that _confirms a conversion_ must not submit. |
+| `enterButton` — a visible 検索 button                                                      | `MISSING`             | grep → nothing                                                                                                                          | P2. Common on JP admin screens; today the consumer puts a `Button` beside it and re-wires the query.                                                                                                                                               |
+| `loading`                                                                                  | `MISSING`             | grep → nothing; `PendingProp` exists in the vocabulary                                                                                  | P2. Reuse `loading?: PendingProp` as `Select` `:998` does.                                                                                                                                                                                         |
+| `size`                                                                                     | `MISSING`             | `SearchInputProp` `:418-437` has `status` and `variant` but no `size`, while the `Input` it wraps does (`:110`)                         | P2 (consistency) — a `SearchInput` cannot match an `sm` toolbar row.                                                                                                                                                                               |
+| `allowClear`                                                                               | `PRESENT` (always on) | hardcoded clear button `search-input.tsx:110-121`                                                                                       | Fine; note it is not switchable.                                                                                                                                                                                                                   |
+| `searchIcon`                                                                               | `WONT-PORT`           | ground rule #4                                                                                                                          | Token.                                                                                                                                                                                                                                             |
 
 ### 2.12 `CheckboxGroup` / `RadioGroup` — `:457-470`, `:472-494`
 
-| Ant Design prop / behaviour | Status | Evidence | Verdict |
-| --- | --- | --- | --- |
-| `options` as bare `string \| number` | `MISSING` | `ChoiceOptionProp` requires `{label, value}` `:449-455` | P2. Identical to the `Segmented` row already logged in `antd-parity.md` §3.2 — fix all three together, one shared widening. |
-| `Radio.Group block` — stretch to the parent width (antd 5.21) | `MISSING` | `grep -n "block" src/props/components/data-entry.prop.ts` → no `block` on `RadioGroupProp` `:472-494` | P2. `Segmented` already has `block`; a `optionType="button"` group `:440` wants the same. Reuse the spelling. |
-| `optionType` / `buttonStyle` | `PRESENT` | `:440`, `:442` | |
-| option `title` (hover hint) | `COVERED-ELSEWHERE` | wrap in `Tooltip` — same ruling as `Segmented` in §3.2 | |
-| `size` on `Radio.Group` | `MISSING` | no `size` on `RadioGroupProp` `:472-494` | P2 — only meaningful with `optionType="button"`. Reuse `SizeProp`. |
+| Ant Design prop / behaviour                                   | Status              | Evidence                                                                                              | Verdict                                                                                                                     |
+| ------------------------------------------------------------- | ------------------- | ----------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
+| `options` as bare `string \| number`                          | `MISSING`           | `ChoiceOptionProp` requires `{label, value}` `:449-455`                                               | P2. Identical to the `Segmented` row already logged in `antd-parity.md` §3.2 — fix all three together, one shared widening. |
+| `Radio.Group block` — stretch to the parent width (antd 5.21) | `MISSING`           | `grep -n "block" src/props/components/data-entry.prop.ts` → no `block` on `RadioGroupProp` `:472-494` | P2. `Segmented` already has `block`; a `optionType="button"` group `:440` wants the same. Reuse the spelling.               |
+| `optionType` / `buttonStyle`                                  | `PRESENT`           | `:440`, `:442`                                                                                        |                                                                                                                             |
+| option `title` (hover hint)                                   | `COVERED-ELSEWHERE` | wrap in `Tooltip` — same ruling as `Segmented` in §3.2                                                |                                                                                                                             |
+| `size` on `Radio.Group`                                       | `MISSING`           | no `size` on `RadioGroupProp` `:472-494`                                                              | P2 — only meaningful with `optionType="button"`. Reuse `SizeProp`.                                                          |
 
 ### 2.13 `Rating` (antd `Rate`) — `src/components/ui/rating.tsx:7-42`
 
@@ -239,19 +264,19 @@ Present: `count` (+ the legacy `max`), `allowHalf`, `allowClear`, `character` (n
 `tooltips` folded into the accessible name `:32-36`, `readOnly`, `disabled`, `name`. a11y is correct:
 `role="radiogroup"` + `role="radio"` + roving tabindex `:131-155`.
 
-| Ant Design prop / behaviour | Status | Evidence | Verdict |
-| --- | --- | --- | --- |
-| `onHoverChange` | `MISSING` | `hover` state is internal, `rating.tsx:70` | P2. |
-| `keyboard: false` | `WONT-PORT` | — | Disabling arrow keys on a `radiogroup` fails WCAG 2.1.1. |
+| Ant Design prop / behaviour                                | Status                                 | Evidence                                                                                        | Verdict                                                                                                                                                                                                                             |
+| ---------------------------------------------------------- | -------------------------------------- | ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `onHoverChange`                                            | `MISSING`                              | `hover` state is internal, `rating.tsx:70`                                                      | P2.                                                                                                                                                                                                                                 |
+| `keyboard: false`                                          | `WONT-PORT`                            | —                                                                                               | Disabling arrow keys on a `radiogroup` fails WCAG 2.1.1.                                                                                                                                                                            |
 | `RatingProps` is not registered in `src/props/components/` | `MISSING` (house standard, not parity) | `grep -rn "RatingProp" src/props/` → no hit; the type lives in `src/components/ui/rating.tsx:7` | Same for `TagInputProps`, `ToggleProp`, `ToggleGroupItemProp`, `PasswordInputProps`, `UploadCropDialog`. Out of Ant-parity scope, but `STANDARDS-vocabulary-tokens.md` rules 1–2 want them in the registry. Flagged, not scheduled. |
 
 ### 2.14 `PasswordStrength` — `src/components/data-entry/password-strength.tsx` (no antd counterpart)
 
-| Behaviour | Status | Evidence | Verdict |
-| --- | --- | --- | --- |
-| Every visible string is hardcoded English | `MISSING` — **i18n** | `DEFAULT_LABELS = { weak: "Weak", fair: "Fair", strong: "Strong" }` `:4-8`; `labelForRule` returns `"8+ characters"`, `"Contains uppercase letter"`, … `:119-133`; `` aria-label={`Password strength ${score}/4`} `` `:75`; `"Passed: "` / `"Failed: "` `:106`; the live region `{scoreLabel(…)} password strength` `:113`. The file never imports `useTranslation` (`grep -L useTranslation` over `src/components/data-entry/*.tsx` — this is the only non-shim file with real copy that misses it). | **P0.** Route every string through `t()` + the `en`/`ja`/`vi` bundles. `labels` `:21` overrides only 3 of the ~10 strings, so a consumer cannot even work around it. |
-| `role="img"` on the meter | `MISSING` — a11y | `:74-76` | P1. It is a value indicator, not an image: `role="meter"` (or `progressbar`) with `aria-valuenow`/`aria-valuemin`/`aria-valuemax`/`aria-valuetext`. Screen-reader users get a static label today and never hear the value change except via the separate live region `:112-114`. |
-| Rule set is closed | `MISSING` | `PasswordRule` is a fixed 5-member union `:3,10`; thresholds hardcoded `:35-39` | P2. A tenant policy of "12+ characters" has no expression. |
+| Behaviour                                 | Status               | Evidence                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Verdict                                                                                                                                                                                                                                                                          |
+| ----------------------------------------- | -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Every visible string is hardcoded English | `MISSING` — **i18n** | `DEFAULT_LABELS = { weak: "Weak", fair: "Fair", strong: "Strong" }` `:4-8`; `labelForRule` returns `"8+ characters"`, `"Contains uppercase letter"`, … `:119-133`; ``aria-label={`Password strength ${score}/4`}`` `:75`; `"Passed: "` / `"Failed: "` `:106`; the live region `{scoreLabel(…)} password strength` `:113`. The file never imports `useTranslation` (`grep -L useTranslation` over `src/components/data-entry/*.tsx` — this is the only non-shim file with real copy that misses it). | **P0.** Route every string through `t()` + the `en`/`ja`/`vi` bundles. `labels` `:21` overrides only 3 of the ~10 strings, so a consumer cannot even work around it.                                                                                                             |
+| `role="img"` on the meter                 | `MISSING` — a11y     | `:74-76`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | P1. It is a value indicator, not an image: `role="meter"` (or `progressbar`) with `aria-valuenow`/`aria-valuemin`/`aria-valuemax`/`aria-valuetext`. Screen-reader users get a static label today and never hear the value change except via the separate live region `:112-114`. |
+| Rule set is closed                        | `MISSING`            | `PasswordRule` is a fixed 5-member union `:3,10`; thresholds hardcoded `:35-39`                                                                                                                                                                                                                                                                                                                                                                                                                     | P2. A tenant policy of "12+ characters" has no expression.                                                                                                                                                                                                                       |
 
 ---
 
@@ -259,38 +284,37 @@ Present: `count` (+ the legacy `max`), `allowHalf`, `allowClear`, `character` (n
 
 ### P0 — breaks a real screen
 
-| # | Component | Gap | Cite |
-| --- | --- | --- | --- |
-| 1 | `NumberInput` | Locale round-trip corrupts the value: formatted with `Intl` for the active locale, parsed with a hardcoded `,`-is-a-thousands-separator rule. `vi` (shipped) turns `1.5` into `15` on blur. | `number-input.tsx:41,100,220` |
-| 2 | `PasswordStrength` | Entirely hardcoded English — labels, checklist, `aria-label`, live region. No `t()` in the file. | `password-strength.tsx:4-8,75,106,113,119-133` |
+| #   | Component          | Gap                                                                                                                                                                                         | Cite                                           |
+| --- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
+| 1   | `NumberInput`      | Locale round-trip corrupts the value: formatted with `Intl` for the active locale, parsed with a hardcoded `,`-is-a-thousands-separator rule. `vi` (shipped) turns `1.5` into `15` on blur. | `number-input.tsx:41,100,220`                  |
+| 2   | `PasswordStrength` | Entirely hardcoded English — labels, checklist, `aria-label`, live region. No `t()` in the file.                                                                                            | `password-strength.tsx:4-8,75,106,113,119-133` |
 
 ### P1 — a workaround exists, but it is hand-rolled and a11y-risky
 
-| # | Component | Gap | Cite |
-| --- | --- | --- | --- |
-| 3 | `Slider` | No `aria-valuetext`; `tooltip.formatter` paints an `aria-hidden` bubble only. Formatted sliders announce a bare number. | `slider.tsx:33,138-157` |
-| 4 | `Select` / `Cascader` | No list virtualization anywhere in `src/` (antd `virtual` is on by default). | `grep -rl "virtual\|useVirtualizer\|react-window\|@tanstack/react-virtual" src/` → ∅ |
-| 5 | `ColorPicker` | No `presets`, and the only control in the group with no `size`/`status`/`variant`. | `data-entry.prop.ts:893-908` |
-| 6 | `PasswordStrength` | `role="img"` on a value meter instead of `role="meter"` + `aria-valuenow`. | `password-strength.tsx:74-76` |
-| 7 | `SearchInput` | Enter does not commit the query — `onSearch` fires only after the debounce; no `onKeyDown` in the file. | `search-input.tsx:59-63` (whole file read) |
-| 8 | `Upload` | `showUploadList` is boolean-only; "preview but do not remove" forces `itemRender`, which hands the consumer the row's a11y. | `data-entry.prop.ts:1196`, `upload.tsx:461,644` |
-| 9 | `DateRangePicker` | `disabled` is scalar; one end of a range cannot be locked (antd `disabled: [boolean, boolean]`). | `data-entry.prop.ts:787` |
-| 10 | `DatePicker` / `DateRangePicker` | No `defaultPickerValue`/`pickerValue` — the panel cannot be opened on a chosen month. | grep → ∅ |
-| 11 | `Transfer` | No `status`; cannot paint a validation error inside a `FormField`. | `data-entry.prop.ts:1413-1459` |
-| 12 | `Cascader` | Search is uncapped and uncustomizable (no `filterOption`/`filterSort`/result limit; antd's `limit` default is 50). | `cascader.tsx:389-393`, `data-entry.prop.ts:1263` |
-| 13 | `Select` | `fieldNames` absent although `Cascader` and `TreeSelect` both have it — a foreign row shape must be pre-mapped. | `data-entry.prop.ts:1281,1362` vs `:941-1080` |
-| 14 | `NumberInput` | No `stringMode`; money and >2^53 ids lose precision. | grep → ∅ |
-| 15 | `Select` (catalog) | `onSelect` / `onDeselect` / `maxTagPlaceholder` ship but are absent from the MCP entry — consumers cannot discover them. | props `:1093,1112-1114,1124`; catalog `mcp/src/data/components.ts:5572-5987` |
+| #   | Component             | Gap                                                                                                                         | Cite                                                                                 |
+| --- | --------------------- | --------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
+| 4   | `Select` / `Cascader` | No list virtualization anywhere in `src/` (antd `virtual` is on by default).                                                | `grep -rl "virtual\|useVirtualizer\|react-window\|@tanstack/react-virtual" src/` → ∅ |
+| 5   | `ColorPicker`         | No `presets`, and the only control in the group with no `size`/`status`/`variant`.                                          | `data-entry.prop.ts:893-908`                                                         |
+| 6   | `PasswordStrength`    | `role="img"` on a value meter instead of `role="meter"` + `aria-valuenow`.                                                  | `password-strength.tsx:74-76`                                                        |
+| 7   | `SearchInput`         | Enter does not commit the query — `onSearch` fires only after the debounce; no `onKeyDown` in the file.                     | `search-input.tsx:59-63` (whole file read)                                           |
+| 8   | `Upload`              | `showUploadList` is boolean-only; "preview but do not remove" forces `itemRender`, which hands the consumer the row's a11y. | `data-entry.prop.ts:1196`, `upload.tsx:461,644`                                      |
+| 9   | `DatePicker range`    | `disabled` is scalar; one end of a range cannot be locked (antd `disabled: [boolean, boolean]`).                            | `DatePickerBaseProp.disabled`                                                        |
+| 10  | `DatePicker`          | No `defaultPickerValue`/`pickerValue` — the panel cannot be opened on a chosen month.                                       | grep → ∅                                                                             |
+| 11  | `Transfer`            | No `status`; cannot paint a validation error inside a `FormField`.                                                          | `data-entry.prop.ts:1413-1459`                                                       |
+| 12  | `Cascader`            | Search is uncapped and uncustomizable (no `filterOption`/`filterSort`/result limit; antd's `limit` default is 50).          | `cascader.tsx:389-393`, `data-entry.prop.ts:1263`                                    |
+| 13  | `Select`              | `fieldNames` absent although `Cascader` and `TreeSelect` both have it — a foreign row shape must be pre-mapped.             | `data-entry.prop.ts:1281,1362` vs `:941-1080`                                        |
+| 14  | `NumberInput`         | No `stringMode`; money and >2^53 ids lose precision.                                                                        | grep → ∅                                                                             |
+| 15  | `Select` (catalog)    | `onSelect` / `onDeselect` / `maxTagPlaceholder` ship but are absent from the MCP entry — consumers cannot discover them.    | props `:1093,1112-1114,1124`; catalog `mcp/src/data/components.ts:5572-5987`         |
 
 ### P2 — nice to have
 
 `Select`: `defaultActiveFirstOption`, `onInputKeyDown`. ·
 `Cascader`: `Cascader.Panel`. ·
 `NumberInput`: `onStep`. ·
-`Slider`: `Intl`-formatted default tooltip, `draggableTrack`. ·
+`Slider`: `Intl`-formatted default tooltip (`draggableTrack` has landed). ·
 `ColorPicker`: `allowClear`+`onClear`, `readOnly`, `format`/`defaultFormat`/`onFormatChange`. ·
-`DatePicker`: `mode`+`onPanelChange`, `onOk`, `maxTagCount` for `multiple`. ·
-`DateRangePicker`: `separator` (token), `onCalendarChange`. ·
+`DatePicker`: `mode`+`onPanelChange`, `onOk`, `maxTagCount` for `multiple`, `format` as an
+array of accepted inputs, and — with `range` — `separator` (token) and `onCalendarChange`. ·
 `TimePicker`: `cellRender`, `onSelect`. ·
 `Calendar`: `mode`/`onPanelChange` (year board). ·
 `Upload`: `iconRender`, `isImageUrl`, `capture`. ·
@@ -309,13 +333,13 @@ Present: `count` (+ the legacy `max`), `allowHalf`, `allowClear`, `character` (n
 component that already exists. Three candidates were considered and rejected before reaching a C1–C7
 ledger:
 
-| Candidate | Why it is not a new component |
-| --- | --- |
-| `ColorSwatchPicker` (for `presets`) | Fails **C3** — it is a `presets` prop on the existing `ColorPicker`, or a row of `Toggle`s in the app. Adding a second colour control would be the duplication ground rule #3 forbids. |
-| `CascaderPanel` (for antd `Cascader.Panel`) | Fails **C3/C4** — it is `Cascader` rendered without its trigger, i.e. one prop (or a `<Cascader.Panel>` sub-part on the same component), not a second component with a second API. |
-| `SearchButton` / `Input.Search` twin (for `enterButton`) | Fails **C1/C3** — `SearchInput` exists; `enterButton` is a prop on it. |
+| Candidate                                                | Why it is not a new component                                                                                                                                                          |
+| -------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `ColorSwatchPicker` (for `presets`)                      | Fails **C3** — it is a `presets` prop on the existing `ColorPicker`, or a row of `Toggle`s in the app. Adding a second colour control would be the duplication ground rule #3 forbids. |
+| `CascaderPanel` (for antd `Cascader.Panel`)              | Fails **C3/C4** — it is `Cascader` rendered without its trigger, i.e. one prop (or a `<Cascader.Panel>` sub-part on the same component), not a second component with a second API.     |
+| `SearchButton` / `Input.Search` twin (for `enterButton`) | Fails **C1/C3** — `SearchInput` exists; `enterButton` is a prop on it.                                                                                                                 |
 
-The one place where a *new* thing is arguably justified is the **virtualized list engine** behind
+The one place where a _new_ thing is arguably justified is the **virtualized list engine** behind
 `Select virtual` / `Cascader virtual`. That is not a data-entry component: it is the same engine
 `list-masonry.md` needs for `List`. It should be specced once, there, and consumed here — not
 invented twice.