@godxjp/ui 31.31.8 → 32.0.1

package/docs/react-router/prefetch-link.tsx

@@ -1,262 +0,0 @@
-import * as React from "react";
-import { QueryClient, QueryClientProvider, useQuery, useQueryClient } from "@tanstack/react-query";
-
-import {
-  Badge,
-  Card,
-  CardContent,
-  CardDescription,
-  CardHeader,
-  CardTitle,
-  Descriptions,
-  EmptyState,
-  Table,
-  TableBody,
-  TableCell,
-  TableHead,
-  TableHeader,
-  TableRow,
-} from "@godxjp/ui/data-display";
-import { Flex, PageContainer } from "@godxjp/ui/layout";
-import { PrefetchLink } from "@godxjp/ui/react-router";
-
-/**
- * PrefetchLink · a React Router Link that fires queryClient.prefetchQuery on
- * hover/focus so the detail page renders instantly on click. Requires a
- * QueryClientProvider (and a Router) in context. The queryKey/queryFn must match
- * the destination page's useQuery. The `prefetchOn` prop selects the trigger:
- * "both" (default) | "hover" | "focus" | "none". Composed from real @godxjp/ui +
- * @tanstack/react-query + react-router-dom.
- */
-const queryClient = new QueryClient();
-
-type Invoice = { id: string; partner: string; status: "active" | "pending" | "draft" };
-const invoices: Invoice[] = [
-  { id: "INV-0312", partner: "株式会社ベトヤ", status: "active" },
-  { id: "INV-0311", partner: "ハノイ物流", status: "pending" },
-  { id: "INV-0310", partner: "GMO決済", status: "draft" },
-];
-
-const invoiceById = (id: string) => invoices.find((inv) => inv.id === id)!;
-
-/** Destination-page query: a deliberate delay so prefetch (vs cold fetch) is observable. */
-async function fetchInvoice(id: string): Promise<Invoice> {
-  await new Promise((resolve) => setTimeout(resolve, 1200));
-  return invoiceById(id);
-}
-
-const invoiceQueryKey = (id: string) => ["invoice", id] as const;
-
-/** List rows · hover/focus a 請求書番号 to prime ["invoice", id]. */
-function InvoiceList() {
-  return (
-    <Table>
-      <TableHeader>
-        <TableRow>
-          <TableHead>請求書番号</TableHead>
-          <TableHead>取引先</TableHead>
-          <TableHead>状態</TableHead>
-        </TableRow>
-      </TableHeader>
-      <TableBody>
-        {invoices.map((inv) => (
-          <TableRow key={inv.id}>
-            <TableCell>
-              <PrefetchLink
-                to={`/invoices/${inv.id}`}
-                queryKey={invoiceQueryKey(inv.id)}
-                queryFn={() => fetchInvoice(inv.id)}
-                staleTime={60_000}
-                className="text-primary font-medium hover:underline"
-              >
-                {inv.id}
-              </PrefetchLink>
-            </TableCell>
-            <TableCell>{inv.partner}</TableCell>
-            <TableCell>
-              <Badge status={inv.status} />
-            </TableCell>
-          </TableRow>
-        ))}
-      </TableBody>
-    </Table>
-  );
-}
-
-/**
- * Every prefetchOn union value, labelled. "none" never prefetches; "hover" and
- * "focus" prime only on that trigger; "both" (the default) primes on either.
- */
-const triggerCases: { value: "hover" | "focus" | "both" | "none"; id: string; copy: string }[] = [
-  { value: "both", id: "INV-0312", copy: "既定。ホバーまたはフォーカスで先読み" },
-  { value: "hover", id: "INV-0311", copy: "ホバー時のみ先読み" },
-  { value: "focus", id: "INV-0310", copy: "キーボードのフォーカス時のみ先読み" },
-  { value: "none", id: "INV-0312", copy: "先読みを無効化（通常の Link）" },
-];
-
-function TriggerMatrix() {
-  return (
-    <Table>
-      <TableHeader>
-        <TableRow>
-          <TableHead>prefetchOn</TableHead>
-          <TableHead>リンク</TableHead>
-          <TableHead>挙動</TableHead>
-        </TableRow>
-      </TableHeader>
-      <TableBody>
-        {triggerCases.map((c) => (
-          <TableRow key={c.value}>
-            <TableCell>
-              <Badge variant="outline">{c.value}</Badge>
-            </TableCell>
-            <TableCell>
-              <PrefetchLink
-                to={`/invoices/${c.id}`}
-                prefetchOn={c.value}
-                queryKey={invoiceQueryKey(c.id)}
-                queryFn={() => fetchInvoice(c.id)}
-                className="text-primary font-medium hover:underline"
-              >
-                {c.id}
-              </PrefetchLink>
-            </TableCell>
-            <TableCell>{c.copy}</TableCell>
-          </TableRow>
-        ))}
-      </TableBody>
-    </Table>
-  );
-}
-
-/**
- * Observable proof · reads the QueryClient cache directly and lists every
- * ["invoice", id] entry the links above have primed. Updates as you hover/focus.
- */
-function CacheObserver() {
-  const client = useQueryClient();
-  const [, forceRender] = React.useReducer((n: number) => n + 1, 0);
-
-  React.useEffect(() => client.getQueryCache().subscribe(forceRender), [client]);
-
-  const cached = client
-    .getQueryCache()
-    .getAll()
-    .filter((q) => Array.isArray(q.queryKey) && q.queryKey[0] === "invoice");
-
-  if (cached.length === 0) {
-    return (
-      <EmptyState
-        title="まだ先読みされていません"
-        description="上のリンクにホバーまたはフォーカスしてください。"
-      />
-    );
-  }
-
-  return (
-    <Descriptions columns={1}>
-      {cached.map((q) => (
-        <Descriptions.Item
-          key={JSON.stringify(q.queryKey)}
-          label={<Badge variant="outline">{JSON.stringify(q.queryKey)}</Badge>}
-          mono
-        >
-          {q.state.status === "success" ? "キャッシュ済み (cached)" : "先読み中… (fetching)"}
-        </Descriptions.Item>
-      ))}
-    </Descriptions>
-  );
-}
-
-/**
- * Destination block · the SAME queryKey/queryFn contract as the list link.
- * Because the link already primed ["invoice", "INV-0312"], this useQuery resolves
- * from cache (no skeleton) instead of paying the 1.2s fetch.
- */
-function DestinationDetail() {
-  const query = useQuery({
-    queryKey: invoiceQueryKey("INV-0312"),
-    queryFn: () => fetchInvoice("INV-0312"),
-    staleTime: 60_000,
-  });
-
-  if (query.isPending) {
-    return <EmptyState title="読み込み中…" description="先読みが間に合えば即時表示されます。" />;
-  }
-
-  const inv = query.data!;
-  return (
-    <Descriptions columns={1}>
-      <Descriptions.Item label="請求書番号" mono>
-        {inv.id}
-      </Descriptions.Item>
-      <Descriptions.Item label="取引先">{inv.partner}</Descriptions.Item>
-      <Descriptions.Item label="状態">
-        <Badge status={inv.status} />
-      </Descriptions.Item>
-    </Descriptions>
-  );
-}
-
-export default function Demo() {
-  return (
-    <QueryClientProvider client={queryClient}>
-      {/* The preview/isolate harness already provides a Router; PrefetchLink reads it from context. */}
-      <PageContainer
-        title="PrefetchLink"
-        subtitle="Router Link that prefetches the destination query on hover/focus"
-      >
-        <Flex direction="col" gap="lg">
-          <Card>
-            <CardHeader>
-              <CardTitle level={2}>請求書 一覧</CardTitle>
-              <CardDescription>
-                請求書番号にホバーまたはフォーカスすると、その明細クエリが先読みされ次の画面が即時表示されます。
-              </CardDescription>
-            </CardHeader>
-            <CardContent flush>
-              <InvoiceList />
-            </CardContent>
-          </Card>
-
-          <Card>
-            <CardHeader>
-              <CardTitle level={2}>prefetchOn · トリガーの種類</CardTitle>
-              <CardDescription>
-                既定は both。hover / focus / none で先読みのきっかけを切り替えます。
-              </CardDescription>
-            </CardHeader>
-            <CardContent flush>
-              <TriggerMatrix />
-            </CardContent>
-          </Card>
-
-          <Card>
-            <CardHeader>
-              <CardTitle level={2}>先読みキャッシュ（観測）</CardTitle>
-              <CardDescription>
-                QueryClient のキャッシュから ["invoice", id] を直接読み出して表示します。
-              </CardDescription>
-            </CardHeader>
-            <CardContent>
-              <CacheObserver />
-            </CardContent>
-          </Card>
-
-          <Card>
-            <CardHeader>
-              <CardTitle level={2}>遷移先の明細（契約）</CardTitle>
-              <CardDescription>
-                リンクと同じ queryKey/queryFn を使う
-                useQuery。先読み済みならキャッシュから即時解決します。
-              </CardDescription>
-            </CardHeader>
-            <CardContent>
-              <DestinationDetail />
-            </CardContent>
-          </Card>
-        </Flex>
-      </PageContainer>
-    </QueryClientProvider>
-  );
-}

package/docs/roadmap/ai-chat-components.md

@@ -1,206 +0,0 @@
-# AI / chatbot components — normalized spec
-
-> **Reference:** Ant Design X (<https://x.ant.design/components/overview>) for *capabilities*.
-> **Naming:** when a component's identity is unclear, look it up at
-> <https://namethatui.com/?platform=web> before inventing a name.
-> **Contract:** `.claude/skills/godxjp-ui-component/SKILL.md` is the hard gate — MCP-first, real
-> primitives only, `t()` + `Intl`, WAI-ARIA APG + WCAG 2.2 AA, logical CSS, controlled
-> vocabulary, semantic tokens, MCP catalog entry, real-screen docs page.
-
-The library has **zero** chat/AI components today (verified against `mcp/src/data/components.ts` —
-127 entries, none of them conversational). This document decides which of Ant Design X's surface
-becomes a framework component and which is a composition, so no agent has to re-litigate it.
-
-## 1. Scope decision — GATE 0 applied to every Ant Design X component
-
-`docs/COMPOSITION-VS-COMPONENT.md` C1–C7. **Any FAIL ⇒ composition, never `src/components/`.**
-
-| Ant Design X | godx name | Group | C1 | C2 | C3 | C4 | C5 | C6 | C7 | Verdict |
-| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
-| `Bubble` | **`ChatBubble`** | `data-display` | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | **Framework component** |
-| `Bubble.List` | **`ChatBubbleList`** | `data-display` | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | **Framework component** |
-| `Sender` | **`ChatComposer`** | `data-entry` | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | **Framework component** |
-| `Suggestion` | **`ChatSuggestion`** | `data-entry` | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | **Framework component** |
-| `Conversations` | **`ConversationList`** | `navigation` | ✅ | ✅ | ⚠️ | ✅ | ✅ | ✅ | ✅ | **Verify C3 first** — see §6 |
-| `ThoughtChain` / `Think` | **`ThoughtChain`** | `data-display` | ✅ | ⚠️ | ⚠️ | ✅ | ✅ | ✅ | ⚠️ | **Verify C2/C3 first** — see §6 |
-| `Prompts` | — | — | ✅ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | **Composition** — `ResponsiveGrid` + `Card` + `Button` |
-| `Welcome` | — | — | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | **Composition** — static block, `EmptyState`-shaped |
-| `Actions` | — | — | ✅ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | **Composition** — `Button` + `DropdownMenu` |
-| `Attachments` / `FileCard` | — | — | ✅ | ✅ | ❌ | — | — | — | — | **Extend `Upload`** — duplicating it is an instant reject |
-| `CodeHighlighter` | — | — | — | — | ❌ | — | — | — | — | **Use `CodeBlock`** |
-| `Sources` | — | — | ✅ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | **Composition** — `ListRow` + `Badge` |
-| `XProvider` | — | — | — | — | ❌ | — | — | — | — | **Use `AppProvider`** |
-| `Mermaid` | — | — | ❌ | — | — | — | — | — | ❌ | **Out of scope** |
-| `Folder/File Tree` | — | — | — | — | ❌ | — | — | — | — | **Covered by `Tree`** — see `docs/roadmap/tree-components.md` |
-
-**v1 build set: `ChatBubble`, `ChatBubbleList`, `ChatComposer`, `ChatSuggestion`** (4 components,
-all 7/7 PASS). `ConversationList` and `ThoughtChain` are conditional — §6.
-Everything else ships as a `docs/` showcase composition, not library code.
-
----
-
-## 2. `ChatBubble` — one message in a conversation
-
-**Group:** `data-display` · **File:** `src/components/data-display/chat-bubble.tsx`
-
-| Ant Design X | **godx `ChatBubble`** |
-| --- | --- |
-| `content` | `children` (a `ReactNode`; do not take an HTML string) |
-| `placement: 'start' \| 'end'` | `placement: 'start' \| 'end'` (logical — flips under RTL) |
-| `variant: 'filled' \| 'borderless' \| 'outlined' \| 'shadow'` | `variant: 'filled' \| 'borderless' \| 'outlined'` (drop `shadow`; the design system is 1px-border, no drop shadows) |
-| `avatar` | `avatar` (a real `Avatar` node, never a styled div) |
-| `header` / `footer` | `header` / `footer` |
-| `loading` | `loading` (renders `Skeleton`, `aria-busy="true"`) |
-| `typing` | `typing: boolean \| { step?: number; interval?: number }` |
-| `messageRender` | *dropped* — the caller passes rendered `children` |
-| `shape` | *dropped* — corner radius is a token |
-| — | `size: 'xs' \| 'sm' \| 'lg'` (`md` default) |
-| — | `tone` for status-tinted bubbles (error/warning), never colour-only |
-
-**Semantics.** The bubble is an `<article>` inside the list's feed. Give it an accessible name from
-its `header` (the author). The typing animation MUST respect `prefers-reduced-motion: reduce` —
-render the full text immediately, no animation. Streaming text goes in an `aria-live="polite"`
-region owned by `ChatBubbleList`, **not** per-bubble (a live region per bubble floods a screen
-reader). Decorative avatars `aria-hidden`.
-
-**Tokens** (`src/tokens/components/chat-bubble.css`): `--chat-bubble-background`,
-`--chat-bubble-foreground`, `--chat-bubble-border-color`, `--chat-bubble-radius`,
-`--chat-bubble-gap`, `--chat-bubble-max-inline-size`, `--chat-bubble-avatar-size`.
-Role-mirror knobs default to `initial` (`docs/TOKENS.md`).
-
-**i18n:** `chat.bubble.typing`, `chat.bubble.loading`, `chat.bubble.you`, `chat.bubble.assistant`.
-Timestamps via `Intl.DateTimeFormat`; "2 minutes ago" via `Intl.RelativeTimeFormat`; counted nouns
-via `Intl.PluralRules` — never a template string.
-
----
-
-## 3. `ChatBubbleList` — the message feed
-
-**Group:** `data-display` · **File:** same module as `ChatBubble`
-
-| Ant Design X `Bubble.List` | **godx `ChatBubbleList`** |
-| --- | --- |
-| `items` | `items: ChatMessageProp[]` |
-| `roles` | `roles: Record<string, Partial<ChatBubbleProp>>` — per-role defaults (`user`, `assistant`, `system`) |
-| `autoScroll` | `autoScroll` (default `true`) |
-
-**The behavior that earns C2/C3** — none of it is composable from `ScrollArea` + `map`:
-
-1. **Stick-to-bottom.** Auto-scroll while the user is at the bottom; the moment they scroll up,
-   **stop** and surface a "jump to latest" affordance. Silently yanking a reader back to the bottom
-   mid-read is the classic chat-UI defect.
-2. **Streaming without layout thrash** — appended text must not re-scroll the whole feed.
-3. **One `aria-live="polite"` region** for the whole feed, announcing only the newest message.
-4. `role="log"` on the scroll container, `aria-label` via `t()`.
-5. Keyboard: the feed is focusable and scrollable with `PageUp`/`PageDown`/`Home`/`End`; bubbles
-   are not a roving-tabindex widget (interactive controls inside them keep normal tab order).
-
----
-
-## 4. `ChatComposer` — the message input (Ant's `Sender`)
-
-**Group:** `data-entry` · **File:** `src/components/data-entry/chat-composer.tsx`
-
-Named for what the industry calls it (Slack/Discord "composer"); `Sender` describes the person,
-not the control.
-
-| Ant Design X `Sender` | **godx `ChatComposer`** |
-| --- | --- |
-| `value` / `onChange` | `value` / `defaultValue` / `onValueChange` (**controlled triad — mandatory**) |
-| `onSubmit` | `onSubmit(value: string)` |
-| `loading` + `onCancel` | `loading` + `onCancel` |
-| `submitType: 'enter' \| 'shiftEnter'` | `submitType: 'enter' \| 'shiftEnter'` |
-| `placeholder` | `placeholder` (through `t()` at the call site) |
-| `disabled` / `readOnly` | `disabled` / `readOnly` |
-| `header` (`Sender.Header`) | `header` slot |
-| `prefix` / `footer` / `actions` | `prefix` / `footer` / `actions` slots |
-| `allowSpeech` | **out of scope v1** — Web Speech API is not cross-browser; file a follow-up |
-| `autoSize` | always auto-sizing; not a prop |
-| — | `size: 'xs' \| 'sm' \| 'lg'` · `maxLength` · `status` |
-
-**Rules.**
-- Built on the real `Textarea` primitive and real `Button`s — **no raw `<textarea>`/`<button>`**.
-- Auto-grow between a min and max height expressed in `--control-height` tiers, then scroll
-  inside. **No literal `height` and no `calc(var(--control-height) ± …)`** (`check:control-sizing`).
-- `submitType="enter"`: `Enter` submits, `Shift+Enter` newline. `submitType="shiftEnter"`: the
-  inverse. IME composition must never submit — guard on `compositionstart`/`compositionend`
-  (this is the bug that breaks Japanese and Vietnamese input; it is not optional).
-- Empty or whitespace-only input does not submit; the submit button is `disabled` with an
-  accessible name, not merely greyed out.
-- While `loading`, the submit button becomes a cancel button — **one trailing action at a time**,
-  the same discipline as the picker trailing-action rule.
-- The textarea is the semantic focus target; forward the `FormField` label/helper/error contract
-  onto it via `pickFieldA11y` / `useFieldIdentity` — do not reinvent it (`src/lib/field-a11y.ts`).
-
----
-
-## 5. `ChatSuggestion` — trigger-character autocomplete over the composer
-
-**Group:** `data-entry` · **File:** `src/components/data-entry/chat-suggestion.tsx`
-
-| Ant Design X `Suggestion` | **godx `ChatSuggestion`** |
-| --- | --- |
-| `items` | `items: SuggestionItemProp[]` (supports one level of `children`) |
-| `onSelect` | `onValueChange(value: string)` |
-| `block` | *dropped* — width follows the anchor |
-| render-prop `children({ onTrigger, onKeyDown })` | same shape — it wraps `ChatComposer` |
-| — | `triggerCharacter` (default `'/'`) · `open` / `defaultOpen` / `onOpenChange` |
-
-**Rules.** Compose the existing `Command` (cmdk) inside a `Popover` anchored to the composer — do
-**not** hand-roll a listbox; `Command` already ships correct ARIA. What this component owns is the
-part `Command` does not: detecting the trigger character in a textarea, tracking the query as the
-caret moves, and closing on `Escape`/blur/word-break. `Escape` returns focus to the textarea and
-leaves the typed text intact.
-
----
-
-## 6. Conditional components — prove C3 before writing code
-
-Do **not** start these until the ledger is recorded in the PR description.
-
-**`ConversationList`** (Ant's `Conversations`). `NavList` already renders selectable rows with
-`aria-current="page"`, an icon column and a badge; `ListRow` covers short entity lists. Before
-building, answer in writing: what does a conversation list own that `NavList` does not?
-The honest candidates are date **grouping** (Today / Yesterday / Last 7 days — via
-`Intl.RelativeTimeFormat` + `Intl.DateTimeFormat`, never hand-rolled buckets), a **per-item
-overflow menu**, and **inline rename**. If those land as `NavList` props instead, that is the
-better outcome — extend `NavList` and close this out.
-
-**`ThoughtChain`** (Ant's `ThoughtChain` / `Think`). `Timeline` already has a 3-state per-item
-`status` (`done`/`current`/`pending`), an icon rail and ordinal/status variants; `Collapsible`
-owns disclosure. `ThoughtChain` = `Timeline` + per-item collapsible body + a streaming/pending
-state. Strongly prefer adding a `collapsible` affordance to `Timeline` over a new component.
-Whichever way it goes, the reasoning body must be collapsible, and the running step must be
-announced once via `aria-live="polite"` — not on every token.
-
----
-
-## 7. Per-component definition of done
-
-Every component in the build set ships **all** of:
-
-1. `src/components/<group>/<name>.tsx` — real primitives only, logical CSS, `t()` for every string
-   and `aria-label`, `ref` forwarded, `...props` spread, `className` + `id` accepted.
-2. `XProp` + `XProp as XProps` in `src/props/components/<group>.prop.ts`, **registered in
-   `src/props/registry.ts`**.
-3. `src/tokens/components/<name>.css` + an `@import` in `src/tokens/base.css`; names pass
-   `check:token-tiers`; control boxes come from the `--control-height` tier.
-4. Keys in `src/i18n/messages/en.json`, `vi.json`, `ja.json` — all three, no exceptions.
-5. Tests in `src/components/<group>/__tests__/`: a behavior test using `@testing-library/user-event`
-6. An `mcp/src/data/components.ts` entry (props / usage / useCases / related / example / rules) —
-   `check:mcp-sync` and `check:mcp-orphans` must pass.
-7. A real-screen docs page under `docs/<group>/` (AppShell + PageContainer + real primitives), not
-   a bare `Card` snippet.
-8. Export from the group's `index.ts`.
-
-Gates, then **only** the touched group's tests:
-
-```
-pnpm typecheck && pnpm lint && pnpm run audit \
-  && pnpm check:prop-vocabulary && pnpm check:mcp-sync && pnpm check:mcp-orphans \
-  && pnpm check:token-tiers && pnpm check:control-sizing && pnpm check:example-imports
-pnpm vitest run src/components/<group>/__tests__ --maxWorkers=2
-```
-
-`pnpm test` and a bare `pnpm vitest run` are **forbidden** — 506 files / 3700+ tests, and several
-agents on one machine takes the load past 90. The full suite is CI's job on the PR.

package/docs/roadmap/antd-parity.md

@@ -1,155 +0,0 @@
-# Ant Design parity — the audit programme
-
-> The complaint is systemic: _"hầu hết các component thiếu tính năng so với Ant Design."_
-> This document is the **method**, so that 127 catalog entries can be audited by different agents
-> and still produce comparable, reviewable results. Per-component specs live in sibling files.
-
-## 0. Ground rules (a parity gap is not a licence to copy Ant Design)
-
-1. **Capabilities are the target; prop names are not.** Map every antd prop onto
-   `docs/PROPS-VOCABULARY.md` — controlled triad `value`/`defaultValue`/`onValueChange`,
-   overlays `open`/`defaultOpen`/`onOpenChange`, `size ∈ xs|sm|md|lg` (never `"default"`),
-   `tone` for status, positive booleans. Where the library already has a spelling
-   (`getRowId`, `gap`, `columns: {base,sm,md,lg}`, `count`/`overflowCount`/`showZero`), **reuse it**.
-   A third dialect of the same idea is the defect this repo keeps paying to fix.
-2. **GATE 0 still applies.** A missing antd component is not automatically a framework component.
-   Run the C1–C7 test in `docs/COMPOSITION-VS-COMPONENT.md` and publish the ledger. Ant ships
-   things that are compositions here (`Badge.Ribbon`, `Welcome`, `Prompts`).
-3. **Do not duplicate what exists.** Ant's `CheckableTag` is this library's `Toggle`. Ant's
-   searchable select is `Select showSearch`. Check the MCP catalog before proposing anything.
-4. **Do not port antd's mistakes.** Skip `styles={{…}}` inline-style twins (this system themes with
-   tokens), pixel `offset` pairs, and physical `left/right` spellings.
-5. **A gap is only real once measured.** Cite the file and line, or the absence of a grep hit.
-   "Looks less capable than antd" is not a finding.
-
-## 1. Spacing, geometry and token names — the rules already exist, so use them
-
-This library is instrumented with ~60 checkers. Anything you write — **a spec document included** —
-is machine-checkable, so check it before you hand it to anyone.
-
-**Spacing is not free-form.** `docs/SPACING.md` is binding:
-
-- Macro layout uses a **φ modular scale (≈1.618)**, _not_ the 8pt grid. `xs`/`sm` = 4px grid,
-  `md` = φ⁰, `lg` = φ¹, `xl` = φ². Applying Material's 8pt grid here is wrong, not "standard".
-- Tailwind `p-*` / `m-*` / `gap-*` are rejected by `no-utility-spacing`; hand-rolled `flex`/`grid`
-  by `no-utility-layout`. Rows are `<Flex>`, stacks `<Flex direction="col" gap>`, grids
-  `<ResponsiveGrid>`, page sections spaced by `<PageContainer>` itself.
-- **Card padding has a single owner**: `src/styles/card-layout.css`. Anything else that must sit on
-  the same rhythm uses `ui-card-inset-x` / `ui-card-inset-y` / `ui-card-inset` — and those three do
-  **not** share one value. Never invent a per-component inline-padding token where the Card already
-  owns the inset.
-
-**Component token names must match this exact shape** — `check:token-tiers` enforces it:
-
-```
---{component}-{part}-{property}
-```
-
-where `{property}` is one of: `space color background foreground border radius height width padding
-gap size font line letter shadow glow tint gradient alpha align inset offset translate max overflow
-display`.
-
-`surface`, `bg`, `fg`, `spacing` are **not** accepted words. Control boxes come from the
-`--control-height` tier — never a literal height, never `calc(var(--control-height) ± …)`
-(`check:control-sizing`), never a Tailwind scale literal (`check:no-hardcoded-geometry` —
-even `min-w-0` fails).
-
-**Before handing over any doc or spec, run at minimum:**
-
-```
-pnpm check:doc-prop-existence   # a prop named in an example must exist on that component —
-                                # including a prop you only meant as an Ant Design illustration
-pnpm check:token-tiers && pnpm check:no-hardcoded-geometry && pnpm run audit
-```
-
-This section exists because it was violated: a comparison table in
-`badge-tag-chip-count.md` wrote an antd `Badge` + `count` example to illustrate _Ant's_ API and
-`check:doc-prop-existence` correctly read it as a claim about _ours_; and three specs named tokens
-`--…-surface` / `--…-bg`, which the shape above forbids. Both were caught by gates that already
-existed and simply had not been run.
-
-## 2. The ledger format — every audit produces exactly this table
-
-One row per antd capability. No prose findings.
-
-| Ant Design prop / behaviour | Status                                                                | Evidence                                     | Verdict                                                    |
-| --------------------------- | --------------------------------------------------------------------- | -------------------------------------------- | ---------------------------------------------------------- |
-| `<prop>` — one-line meaning | `PRESENT` / `RENAMED` / `COVERED-ELSEWHERE` / `MISSING` / `WONT-PORT` | `src/…:line`, or the grep that found nothing | for `MISSING`: the godx prop name to add, or "composition" |
-
-- `RENAMED` — present under the house spelling. Record both names; no work.
-- `COVERED-ELSEWHERE` — another primitive owns it. Name it. No work, but add a `related` cross-link
-  in the catalog **on both sides** (a one-sided claim is the mistake commit `8365bf05` fixed).
-- `WONT-PORT` — a deliberate refusal. State the reason in the catalog entry so nobody re-adds it.
-
-Close every audit with a **priority call**: `P0` (breaks a real screen), `P1` (a workaround exists
-but it is hand-rolled and a11y-risky), `P2` (nice to have).
-
-## 3. Findings so far
-
-### 3.1 Already specced — see the sibling documents
-
-| Area                               | Verdict                                                                                                      | Spec                      |
-| ---------------------------------- | ------------------------------------------------------------------------------------------------------------ | ------------------------- |
-| `Tree` / `TreeList` / `TreeSelect` | `TreeSelect` fine; `TreeList` is not a tree; **`Tree` missing entirely**                                     | `tree-components.md`      |
-| Badge / Tag / Chip / Pill / Count  | Count marker missing entirely; removable chip trapped inside `TagInput`; selectable chip already is `Toggle` | `badge-tag-chip-count.md` |
-| `List` (Ant `Listy`) / `Masonry`   | Both missing entirely — no virtualization and no column packing anywhere in `src/`                           | `list-masonry.md`         |
-| AI / chat surface                  | Nothing exists; 4 components + 6 compositions decided                                                        | `ai-chat-components.md`   |
-
-### 3.2 `Tabs`, `Steps`, `Segmented` — audited 2026-09-10
-
-These three are **already deliberately Ant-aligned** — the prop types cite antd by name. The
-remaining gaps are narrow, and none of them is P0.
-
-**`Tabs`** (`src/props/components/navigation.prop.ts:301`, `src/components/navigation/tabs.tsx`).
-Present: `items` (incl. `closable`/`closeIcon`/`icon`), `value`/`defaultValue`/`onValueChange`,
-`variant` (`line`/`card`/`editable-card`), `tabPlacement`, `centered`, `extra`
-(= antd `tabBarExtraContent`), `destroyOnHidden`, `onEdit`, `addIcon`, `hideAdd`. Overflow already
-scrolls and keeps the active tab visible (`src/components/navigation/tabs-scroll.ts`).
-
-| Gap                                                                                          | Priority | Verdict                                                                                       |
-| -------------------------------------------------------------------------------------------- | -------- | --------------------------------------------------------------------------------------------- |
-| `moreIcon` + an overflow **"more" dropdown** when the strip cannot scroll (narrow viewports) | **P1**   | Add. Scrolling alone hides tabs from a touch user with no affordance.                         |
-| `indicator: { size, align }`                                                                 | P2       | Add as tokens (`--tabs-indicator-*`), not props — it is a design knob (cardinal rule #44).    |
-| `tabBarGutter`                                                                               | P2       | Token, not a prop.                                                                            |
-| `animated`                                                                                   | P2       | `WONT-PORT` as a prop — motion is a system decision and must follow `prefers-reduced-motion`. |
-| `renderTabBar`                                                                               | P2       | `WONT-PORT` — an escape hatch that lets a consumer bypass the a11y contract.                  |
-| `size` lacks `xs`                                                                            | P2       | Add `xs` for the full `xs\|sm\|md\|lg` tier.                                                  |
-
-**`Steps`** (`src/props/components/navigation.prop.ts:201-240`).
-Present: `items` (`title`/`subtitle`/`description`/`icon`/`status`/`disabled`),
-`value`/`defaultValue`/`onValueChange`, `orientation`, `status`, `type`
-(`default`/`dot`/`inline`/`navigation` — `dot` **is** antd's deprecated `progressDot`), `percent`,
-`titlePlacement`, `separator`.
-
-| Gap                                                          | Priority | Verdict                                                                |
-| ------------------------------------------------------------ | -------- | ---------------------------------------------------------------------- |
-| `initial` — start the visible numbering at N                 | P2       | Add. Trivial, and real for resumed wizards.                            |
-| `responsive` — auto-switch to vertical on a narrow container | **P1**   | Add. Today a horizontal 5-step bar on a phone is the caller's problem. |
-| `size` is `md\|sm` only                                      | P2       | Extend to `xs\|sm\|md\|lg`.                                            |
-
-**`Segmented`** (`src/components/ui/segmented.tsx`). Built on react-aria-components' `RadioGroup`
-(Radix's, when this was audited) — the correct APG choice either way, and the comment explaining why
-it is not a `ToggleGroup` should be preserved verbatim.
-Present: `options` (`value`/`label`/`icon`/`disabled`), `value`/`defaultValue`/`onValueChange`,
-`block`, `vertical`, `size`, `disabled`, `name`.
-
-| Gap                                         | Priority | Verdict                                                                                                       |
-| ------------------------------------------- | -------- | ------------------------------------------------------------------------------------------------------------- |
-| `shape: 'default' \| 'round'`               | P2       | Add as `shape` — the existing `ShapeProp` vocabulary already has `pill`; reuse it rather than antd's `round`. |
-| Option as a bare `string \| number`         | P2       | Add. Ant accepts it; it removes ceremony for the common case.                                                 |
-| Per-option `title` (a tooltip / hover hint) | P2       | `COVERED-ELSEWHERE` — wrap the option in `Tooltip`. Do not add a second tooltip API.                          |
-| `size` lacks `xs`                           | P2       | Add.                                                                                                          |
-
-**None of these three is the source of the "doesn't look like Ant Design" impression** — that is
-`TreeList`, the missing count badge, and the missing `List`/`Masonry`/`Tree`.
-
-## 4. How to run an audit (per component group)
-
-1. Read the group's catalog entries in `mcp/src/data/components.ts` and the prop types in
-   `src/props/components/<group>.prop.ts`.
-2. Fetch the matching Ant Design docs page for each. Where a component's _identity_ is unclear,
-   settle it at <https://namethatui.com/?platform=web> before writing anything.
-3. Produce the §2 ledger per component. Cite file:line.
-4. Publish a GATE-0 C1–C7 ledger for anything proposed as a **new** component.
-5. Do **not** write source in an audit pass. An audit is read-only; fixes are a separate wave with
-   their own spec, so the diff stays reviewable and two agents never edit one file at once.