@godxjp/chat 32.0.0 → 32.0.1

package/dist/thought-chain.d.ts

@@ -0,0 +1,45 @@
+import * as React from 'react';
+import { ThoughtChainProp, ThoughtChainItemProp } from '@godxjp/ui/props/components';
+export { ThoughtChainItemProp, ThoughtChainItemProp as ThoughtChainItemProps, ThoughtChainItemsProp, ThoughtChainLineProp, ThoughtChainProp, ThoughtChainProp as ThoughtChainProps, ThoughtChainStatusProp, ThoughtChainVariantProp } from '@godxjp/ui/props/components';
+
+/**
+ * ThoughtChain — the assistant's reasoning, step by step (Ant Design X `ThoughtChain`).
+ *
+ * ## The shape, and why it is an `<ol>`
+ *
+ * Ant renders the whole chain as nested `<div>`s and paints the step number itself
+ * (`index + 1` in `es/thought-chain/Node.js`). The order of the steps IS the content here — step 3
+ * only makes sense after step 2 — so the chain is an ordered list and a screen reader gets "list,
+ * 4 items" plus each step's position for free. The visible ordinal stays, because the same number
+ * has to be on screen for a sighted reader following a long chain.
+ *
+ * ## The disclosure is a real button
+ *
+ * A `collapsible` step's title in Ant is a `<div onClick>` with a rotating chevron — no role, no
+ * `tabIndex`, no `aria-expanded`. Here it is a `<button aria-expanded aria-controls>` over the
+ * body it opens: the WAI-ARIA APG Disclosure pattern, so the step can be opened from the keyboard
+ * and its state is announced rather than inferred from a rotation.
+ *
+ * Everything a caller passes keeps Ant's spelling: `items` (with `icon`, `title`, `description`,
+ * `content`, `footer`, `status`, `collapsible`, `blink`, `destroyOnHidden`), the
+ * `defaultExpandedKeys` / `expandedKeys` / `onExpand` triad, and `line`. `styles` / `classNames` /
+ * `prefixCls` / `rootClassName` are not ported — the standing style-hole decision
+ * (docs/WHAT-BELONGS-HERE.md, docs/DESIGN-AUTHORITY.md); the chain is retuned through
+ * `src/tokens/components/thought-chain.css`.
+ */
+declare const ThoughtChain: React.ForwardRefExoticComponent<ThoughtChainProp & React.RefAttributes<HTMLOListElement>>;
+/**
+ * ThoughtChainItem — one step OUTSIDE a chain (Ant Design X `ThoughtChain.Item`).
+ *
+ * A named export rather than `ThoughtChain.Item`, for the same reason `ActionsItem` is: every
+ * compound in this library is separate named exports (`CardHeader`, `TabsList`), and attaching
+ * statics to one component would be the only instance of it here.
+ *
+ * ONE DEVIATION: Ant renders the chip as a `<div>` and hangs `onClick` on it, so a clickable step
+ * is invisible to the keyboard and to assistive technology. Here an item WITH `onClick` renders a
+ * real `<button>` and one without renders a plain `<div>` — the element follows whether the thing
+ * is actually a control.
+ */
+declare const ThoughtChainItem: React.ForwardRefExoticComponent<ThoughtChainItemProp & React.RefAttributes<HTMLElement>>;
+
+export { ThoughtChain, ThoughtChainItem };

package/dist/thought-chain.js

@@ -0,0 +1,9 @@
+"use client";
+import {
+  ThoughtChain,
+  ThoughtChainItem
+} from "./chunk-52TWSF6W.js";
+export {
+  ThoughtChain,
+  ThoughtChainItem
+};

package/dist/welcome.d.ts

@@ -0,0 +1,29 @@
+import * as React from 'react';
+import { WelcomeProp } from '@godxjp/ui/props/components';
+export { WelcomeProp, WelcomeProp as WelcomeProps, WelcomeVariantProp } from '@godxjp/ui/props/components';
+
+/**
+ * Welcome — the greeting block at the head of an empty conversation (Ant Design X `Welcome`).
+ *
+ * ## Why this is a component and not four lines of composition
+ *
+ * It is close to the line, and the honest answer is that the SHAPE is the value: an assistant's
+ * first screen is the same object in every product — glyph, greeting, one line under it, one
+ * trailing action — and Ant X named it, so every consumer that builds a chat now expects the name.
+ * What it owns beyond a `Flex` is the `extra` slot's placement (on the TITLE row, not below the
+ * description, which is where a hand-roll puts it) and the `icon`-as-URL rule below.
+ *
+ * ## Two deliberate differences from Ant X, both in the same direction
+ *
+ * - **The image icon is decorative.** Ant renders `alt="icon"` — a screen reader then reads the
+ *   word "icon" beside a title the glyph is only decorating. Here it is `alt=""`, which is what an
+ *   image that duplicates adjacent text is supposed to be.
+ * - **The heading level is Ant's.** Ant hardcodes `Typography.Title level={4}`, so this renders an
+ *   `<h4>`. Hardcoding a level is a document-structure decision a component should not normally
+ *   make, but the alternative — inventing a `level` prop Ant does not have — is a second spelling
+ *   of an axis the issue asked to port verbatim. Wrap it in your own heading hierarchy if the page
+ *   needs a different rung.
+ */
+declare const Welcome: React.ForwardRefExoticComponent<WelcomeProp & React.RefAttributes<HTMLDivElement>>;
+
+export { Welcome };

package/dist/welcome.js

@@ -0,0 +1,7 @@
+"use client";
+import {
+  Welcome
+} from "./chunk-NUCO7NAP.js";
+export {
+  Welcome
+};

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@godxjp/chat",
-  "version": "32.0.0",
+  "version": "32.0.1",
   "description": "Conversational UI for GoDX apps on @godxjp/ui: message bubbles and lists, the composer with slash / mention suggestions, the conversation list, thought chains, the welcome block, attachments and the message action bar — IME-safe, ja / en / vi.",
   "type": "module",
   "main": "./dist/index.js",
@@ -32,7 +32,7 @@
     "lucide-react": "^1.37.0"
   },
   "peerDependencies": {
-    "@godxjp/ui": "~32.0.0",
+    "@godxjp/ui": "~32.0.1",
     "react": ">=19.0.0",
     "react-dom": ">=19.0.0"
   },