haze-ui 1.25.0 → 1.26.0

package/dist/registry.json

@@ -14,7 +14,7 @@
       "files": [
         {
           "path": "components/haze/chat-message.tsx",
-          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). You also own the 'use client' boundary —\n// haze-ui ships no directives of its own.\n\nimport { ChatMessage } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/chat-message.css';\n\nexport { ChatMessage };\nexport type { ChatMessageProps, ChatMessageRole } from 'haze-ui';\n",
+          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). haze-ui dist modules ship their own\n// 'use client' directive, so imports resolve cleanly from RSC; the\n// wrapper inherits client semantics either way.\n\nimport { ChatMessage } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/chat-message.css';\n\nexport { ChatMessage };\nexport type { ChatMessageProps, ChatMessageRole } from 'haze-ui';\n",
           "type": "registry:component"
         }
       ]
@@ -30,7 +30,7 @@
       "files": [
         {
           "path": "components/haze/chat-container.tsx",
-          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). You also own the 'use client' boundary —\n// haze-ui ships no directives of its own.\n\nimport { ChatContainer } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/chat-container.css';\n\nexport { ChatContainer };\nexport type { ChatContainerProps } from 'haze-ui';\n",
+          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). haze-ui dist modules ship their own\n// 'use client' directive, so imports resolve cleanly from RSC; the\n// wrapper inherits client semantics either way.\n\nimport { ChatContainer } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/chat-container.css';\n\nexport { ChatContainer };\nexport type { ChatContainerProps } from 'haze-ui';\n",
           "type": "registry:component"
         }
       ]
@@ -46,7 +46,7 @@
       "files": [
         {
           "path": "components/haze/chat-input.tsx",
-          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). You also own the 'use client' boundary —\n// haze-ui ships no directives of its own.\n\nimport { ChatInput } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/chat-input.css';\n\nexport { ChatInput };\nexport type { ChatInputProps } from 'haze-ui';\n",
+          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). haze-ui dist modules ship their own\n// 'use client' directive, so imports resolve cleanly from RSC; the\n// wrapper inherits client semantics either way.\n\nimport { ChatInput } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/chat-input.css';\n\nexport { ChatInput };\nexport type { ChatInputProps } from 'haze-ui';\n",
           "type": "registry:component"
         }
       ]
@@ -62,7 +62,7 @@
       "files": [
         {
           "path": "components/haze/streaming-text.tsx",
-          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). You also own the 'use client' boundary —\n// haze-ui ships no directives of its own.\n\nimport { StreamingText } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/streaming-text.css';\n\nexport { StreamingText };\nexport type { StreamingTextProps } from 'haze-ui';\n",
+          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). haze-ui dist modules ship their own\n// 'use client' directive, so imports resolve cleanly from RSC; the\n// wrapper inherits client semantics either way.\n\nimport { StreamingText } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/streaming-text.css';\n\nexport { StreamingText };\nexport type { StreamingTextProps } from 'haze-ui';\n",
           "type": "registry:component"
         }
       ]
@@ -78,7 +78,7 @@
       "files": [
         {
           "path": "components/haze/markdown-renderer.tsx",
-          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). You also own the 'use client' boundary —\n// haze-ui ships no directives of its own.\n\nimport { MarkdownRenderer } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/markdown-renderer.css';\n\nexport { MarkdownRenderer };\nexport type { MarkdownRendererProps } from 'haze-ui';\n",
+          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). haze-ui dist modules ship their own\n// 'use client' directive, so imports resolve cleanly from RSC; the\n// wrapper inherits client semantics either way.\n\nimport { MarkdownRenderer } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/markdown-renderer.css';\n\nexport { MarkdownRenderer };\nexport type { MarkdownRendererProps } from 'haze-ui';\n",
           "type": "registry:component"
         }
       ]
@@ -94,7 +94,7 @@
       "files": [
         {
           "path": "components/haze/tool-call-card.tsx",
-          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). You also own the 'use client' boundary —\n// haze-ui ships no directives of its own.\n\nimport { ToolCallCard } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/tool-call-card.css';\n\nexport { ToolCallCard };\nexport type { ToolCallCardProps, ToolCallStatus } from 'haze-ui';\n",
+          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). haze-ui dist modules ship their own\n// 'use client' directive, so imports resolve cleanly from RSC; the\n// wrapper inherits client semantics either way.\n\nimport { ToolCallCard } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/tool-call-card.css';\n\nexport { ToolCallCard };\nexport type { ToolCallCardProps, ToolCallStatus } from 'haze-ui';\n",
           "type": "registry:component"
         }
       ]
@@ -110,7 +110,7 @@
       "files": [
         {
           "path": "components/haze/thinking-indicator.tsx",
-          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). You also own the 'use client' boundary —\n// haze-ui ships no directives of its own.\n\nimport { ThinkingIndicator } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/thinking-indicator.css';\n\nexport { ThinkingIndicator };\nexport type { ThinkingIndicatorProps } from 'haze-ui';\n",
+          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). haze-ui dist modules ship their own\n// 'use client' directive, so imports resolve cleanly from RSC; the\n// wrapper inherits client semantics either way.\n\nimport { ThinkingIndicator } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/thinking-indicator.css';\n\nexport { ThinkingIndicator };\nexport type { ThinkingIndicatorProps } from 'haze-ui';\n",
           "type": "registry:component"
         }
       ]
@@ -126,7 +126,7 @@
       "files": [
         {
           "path": "components/haze/step-timeline.tsx",
-          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). You also own the 'use client' boundary —\n// haze-ui ships no directives of its own.\n\nimport { StepTimeline, StepTimelineItem } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/step-timeline.css';\n\nexport { StepTimeline, StepTimelineItem };\nexport type { StepTimelineProps, StepTimelineItemProps, StepStatus } from 'haze-ui';\n",
+          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). haze-ui dist modules ship their own\n// 'use client' directive, so imports resolve cleanly from RSC; the\n// wrapper inherits client semantics either way.\n\nimport { StepTimeline, StepTimelineItem } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/step-timeline.css';\n\nexport { StepTimeline, StepTimelineItem };\nexport type { StepTimelineProps, StepTimelineItemProps, StepStatus } from 'haze-ui';\n",
           "type": "registry:component"
         }
       ]
@@ -142,7 +142,7 @@
       "files": [
         {
           "path": "components/haze/approval-card.tsx",
-          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). You also own the 'use client' boundary —\n// haze-ui ships no directives of its own.\n\nimport { ApprovalCard } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/approval-card.css';\n\nexport { ApprovalCard };\nexport type { ApprovalCardProps } from 'haze-ui';\n",
+          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). haze-ui dist modules ship their own\n// 'use client' directive, so imports resolve cleanly from RSC; the\n// wrapper inherits client semantics either way.\n\nimport { ApprovalCard } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/approval-card.css';\n\nexport { ApprovalCard };\nexport type { ApprovalCardProps } from 'haze-ui';\n",
           "type": "registry:component"
         }
       ]
@@ -158,7 +158,7 @@
       "files": [
         {
           "path": "components/haze/token-counter.tsx",
-          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). You also own the 'use client' boundary —\n// haze-ui ships no directives of its own.\n\nimport { TokenCounter } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/token-counter.css';\n\nexport { TokenCounter };\nexport type { TokenCounterProps } from 'haze-ui';\n",
+          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). haze-ui dist modules ship their own\n// 'use client' directive, so imports resolve cleanly from RSC; the\n// wrapper inherits client semantics either way.\n\nimport { TokenCounter } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/token-counter.css';\n\nexport { TokenCounter };\nexport type { TokenCounterProps } from 'haze-ui';\n",
           "type": "registry:component"
         }
       ]
@@ -174,7 +174,7 @@
       "files": [
         {
           "path": "components/haze/model-picker.tsx",
-          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). You also own the 'use client' boundary —\n// haze-ui ships no directives of its own.\n\nimport { ModelPicker } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/model-picker.css';\n\nexport { ModelPicker };\nexport type { ModelPickerProps, ModelOption } from 'haze-ui';\n",
+          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). haze-ui dist modules ship their own\n// 'use client' directive, so imports resolve cleanly from RSC; the\n// wrapper inherits client semantics either way.\n\nimport { ModelPicker } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/model-picker.css';\n\nexport { ModelPicker };\nexport type { ModelPickerProps, ModelOption } from 'haze-ui';\n",
           "type": "registry:component"
         }
       ]
@@ -190,7 +190,7 @@
       "files": [
         {
           "path": "components/haze/conversation-list.tsx",
-          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). You also own the 'use client' boundary —\n// haze-ui ships no directives of its own.\n\nimport { ConversationList, ConversationItem } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/conversation-list.css';\n\nexport { ConversationList, ConversationItem };\nexport type { ConversationListProps, ConversationItemProps } from 'haze-ui';\n",
+          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). haze-ui dist modules ship their own\n// 'use client' directive, so imports resolve cleanly from RSC; the\n// wrapper inherits client semantics either way.\n\nimport { ConversationList, ConversationItem } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/conversation-list.css';\n\nexport { ConversationList, ConversationItem };\nexport type { ConversationListProps, ConversationItemProps } from 'haze-ui';\n",
           "type": "registry:component"
         }
       ]
@@ -206,7 +206,7 @@
       "files": [
         {
           "path": "components/haze/diff-viewer.tsx",
-          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). You also own the 'use client' boundary —\n// haze-ui ships no directives of its own.\n\nimport { DiffViewer } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/diff-viewer.css';\n\nexport { DiffViewer };\nexport type { DiffViewerProps, DiffLine } from 'haze-ui';\n",
+          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). haze-ui dist modules ship their own\n// 'use client' directive, so imports resolve cleanly from RSC; the\n// wrapper inherits client semantics either way.\n\nimport { DiffViewer } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/diff-viewer.css';\n\nexport { DiffViewer };\nexport type { DiffViewerProps, DiffLine } from 'haze-ui';\n",
           "type": "registry:component"
         }
       ]
@@ -222,7 +222,7 @@
       "files": [
         {
           "path": "components/haze/log-viewer.tsx",
-          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). You also own the 'use client' boundary —\n// haze-ui ships no directives of its own.\n\nimport { LogViewer } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/log-viewer.css';\n\nexport { LogViewer };\nexport type { LogViewerProps, LogEntry, LogLevel } from 'haze-ui';\n",
+          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). haze-ui dist modules ship their own\n// 'use client' directive, so imports resolve cleanly from RSC; the\n// wrapper inherits client semantics either way.\n\nimport { LogViewer } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/log-viewer.css';\n\nexport { LogViewer };\nexport type { LogViewerProps, LogEntry, LogLevel } from 'haze-ui';\n",
           "type": "registry:component"
         }
       ]
@@ -238,7 +238,7 @@
       "files": [
         {
           "path": "components/haze/async-section.tsx",
-          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). You also own the 'use client' boundary —\n// haze-ui ships no directives of its own.\n\nimport { AsyncSection } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/async-section.css';\n\nexport { AsyncSection };\nexport type { AsyncSectionProps } from 'haze-ui';\n",
+          "content": "// haze-ui agent component wrapper — generated by scripts/generate-registry.mjs.\n//\n// This file deliberately contains no component source: haze-ui is compiled\n// CSS-in-JS (linaria) styled against --haze-* design tokens, so vendoring\n// the source would neither build nor style. It re-exports the published\n// component and imports its stylesheet instead — treat this file as your\n// customization layer (wrap, restyle, compose) while haze-ui stays an npm\n// dependency and keeps updating underneath.\n//\n// Theming (once per app): apply the token classes to a root element, e.g.\n//   import { lightTheme, spacing, typography } from 'haze-ui';\n//   <div className={`${lightTheme} ${spacing} ${typography}`}>…</div>\n// (darkTheme is a drop-in swap). haze-ui dist modules ship their own\n// 'use client' directive, so imports resolve cleanly from RSC; the\n// wrapper inherits client semantics either way.\n\nimport { AsyncSection } from 'haze-ui';\n\nimport 'haze-ui/css/tokens.css';\nimport 'haze-ui/css/async-section.css';\n\nexport { AsyncSection };\nexport type { AsyncSectionProps } from 'haze-ui';\n",
           "type": "registry:component"
         }
       ]

package/dist/tokens/colors.js

@@ -1,4 +1,5 @@
 
+"use client";
 /* empty css                 */
 //#region src/lib/tokens/colors.ts
 var e = "haze-colors__lightTheme", t = "haze-colors__darkTheme";

package/dist/tokens/index.js

@@ -1,3 +1,4 @@
+"use client";
 import { darkTheme as e, lightTheme as t } from "./colors.js";
 import { spacing as n } from "./spacing.js";
 import { typography as r } from "./typography.js";

package/dist/tokens/motion.js

@@ -1,4 +1,5 @@
 
+"use client";
 /* empty css                 */
 //#region src/lib/tokens/motion.ts
 var e = "haze-motion__motion";

package/dist/tokens/oklch.js

@@ -1,3 +1,4 @@
+"use client";
 function e(e) {
 	return e <= .04045 ? e / 12.92 : ((e + .055) / 1.055) ** 2.4;
 }

package/dist/tokens/palette.js

@@ -1,3 +1,4 @@
+"use client";
 import { clampChroma as e, formatOklch as t, parseHex as n, parseOklch as r } from "./oklch.js";
 //#region src/lib/tokens/palette.ts
 var i = {

package/dist/tokens/registry.js

@@ -1,3 +1,4 @@
+"use client";
 import { formatOklch as e } from "./oklch.js";
 import { SEMANTIC_COLOR_TOKENS as t } from "./palette.js";
 //#region src/lib/tokens/registry.ts

package/dist/tokens/spacing.js

@@ -1,4 +1,5 @@
 
+"use client";
 /* empty css                  */
 //#region src/lib/tokens/spacing.ts
 var e = "haze-spacing__spacing";

package/dist/tokens/typography.js

@@ -1,4 +1,5 @@
 
+"use client";
 /* empty css                     */
 //#region src/lib/tokens/typography.ts
 var e = "haze-typography__typography";

package/dist/types/components/Calendar/date.d.ts

@@ -0,0 +1,79 @@
+/**
+ * Pure calendar-date math for the Calendar grid, extracted from Calendar.tsx.
+ *
+ * Semantics — naive local civil time:
+ *
+ * - Every `(year, month, day)` triple denotes a civil calendar date realized
+ *   as a *local* Date at midnight via `new Date(year, month, day)`. The UTC
+ *   constructor (`new Date(Date.UTC(…))`) is deliberately never used, and
+ *   `new Date('YYYY-MM-DD')` — which parses as UTC midnight and therefore
+ *   shifts a day in zones behind UTC — is never a source of truth here.
+ * - DST transitions move wall-clock hours (typically 02:00/03:00), never
+ *   midnight, so constructing a local midnight and reading back
+ *   `getFullYear`/`getMonth`/`getDate` round-trips exactly even on
+ *   spring-forward and fall-back days.
+ * - Months are 0-based (`Date#getMonth` semantics: 0 = January, 11 =
+ *   December). All functions are pure: they only read the local zone to
+ *   query weekdays of civil dates they constructed themselves, and never
+ *   normalize dates through out-of-range days (the classic
+ *   `new Date(y, m + 1, 31)` rollover hazard).
+ */
+/** One cell of the Calendar grid; `outside` marks days of adjacent months. */
+export type CalendarCell = {
+    day: number;
+    month: number;
+    year: number;
+    outside: boolean;
+};
+/**
+ * Number of days in a month, via day 0 of the following month
+ * (`new Date(year, month + 1, 0).getDate()`). Out-of-range months
+ * normalize through the Date constructor, so `month` may be `-1` or `12`
+ * and still yields the true length of the adjacent month.
+ */
+export declare function getDaysInMonth(year: number, month: number): number;
+/**
+ * Shift a `(year, month)` view by `delta` months with year carry, e.g.
+ * `(2026, 11) + 1 → { year: 2027, month: 0 }`. Pure integer arithmetic on
+ * the month index — no Date is constructed, so navigating from a long month
+ * into a short one (Jan 31 → February) can never roll a phantom day 29–31
+ * over into the next month the way `new Date(y, m + 1, 31)` would.
+ */
+export declare function addMonths(year: number, month: number, delta: number): {
+    year: number;
+    month: number;
+};
+/**
+ * Number of leading cells (previous-month days) before day 1 of the month,
+ * for a grid whose first column is `weekStart` (`Date#getDay` semantics:
+ * 0 = Sunday, 1 = Monday). The weekday of day 1 is read from the
+ * local-midnight Date of that civil date; DST never moves midnight, so the
+ * offset is stable across transitions.
+ */
+export declare function getLeadingDays(year: number, month: number, weekStart: number): number;
+/**
+ * Flat list of grid cells for one month view: `getLeadingDays` previous-month
+ * days, then every day of the month itself, then just enough next-month days
+ * to complete the final week row. When the month already fills its rows
+ * exactly (e.g. a Sunday-first February with 28 days), no padding row is
+ * added. The result length is always a multiple of 7.
+ */
+export declare function buildMonthCells(year: number, month: number, weekStart: number): CalendarCell[];
+/**
+ * Format a civil date as the `"YYYY-MM-DD"` string Calendar uses as its
+ * value. Value semantics: the string denotes the **local** civil date — it
+ * is a plain calendar date, not a UTC timestamp (parsing it with
+ * `new Date('YYYY-MM-DD')` yields UTC midnight and shifts a day in zones
+ * behind UTC). Pure string math; no Date construction.
+ */
+export declare function formatDate(year: number, month: number, day: number): string;
+/**
+ * Parse a `"YYYY-MM-DD"` value string into a local-midnight Date — the
+ * inverse of {@link formatDate} and the only safe way to turn a value into
+ * a Date (`new Date('YYYY-MM-DD')` parses as UTC midnight and shifts a
+ * day in zones behind UTC, e.g. `'2026-03-01'` lands on local Feb 28 in
+ * America/New_York). Returns `null` for anything that is not a real
+ * calendar date (`'2026-02-30'`, `'2026-13-01'`, malformed input),
+ * leaving the caller free to fall back to today.
+ */
+export declare function parseCivilDate(value: string): Date | null;

package/dist/types/components/Combobox/ComboboxOption.d.ts

@@ -3,9 +3,21 @@ type ComboboxOptionProps = {
     value: string;
     highlighted?: boolean;
     selected?: boolean;
+    /**
+     * DOM id of this option — what the combobox input points at via
+     * aria-activedescendant while the row holds the keyboard highlight.
+     */
+    id?: string;
+    /**
+     * Size of the whole option set, per aria-setsize. Must count every
+     * option, not just the rows a windowed (virtualized) list mounted.
+     */
+    setSize?: number;
+    /** 1-based position of this option in the set, per aria-posinset. */
+    posInSet?: number;
     onSelect?: (value: string) => void;
     className?: string;
     children: ReactNode;
 };
-export default function ComboboxOption({ value, highlighted, selected, onSelect, className, children, }: ComboboxOptionProps): import("react").JSX.Element;
+export default function ComboboxOption({ value, highlighted, selected, id, setSize, posInSet, onSelect, className, children, }: ComboboxOptionProps): import("react").JSX.Element;
 export type { ComboboxOptionProps };

package/dist/types/components/DataTable/DataTable.d.ts

@@ -6,6 +6,15 @@ type DataTableColumnMeta = {
     /** Column-level sorting switch — overrides the table-level `sortable` default. */
     sortable?: boolean;
 };
+/** Windowing configuration for the table body, reusing `VirtualList`. */
+type DataTableVirtualized = boolean | {
+    /** Fixed row height in px — must match the rendered row (custom cell
+     * padding or multi-line content need this form). */
+    rowHeight: number;
+    /** Extra rows kept mounted above/below the visible window.
+     * Defaults to `VirtualList`'s `5`. */
+    overscan?: number;
+};
 /** The feature set stitched into every DataTable instance — TanStack v9's
  * tree-shaking contract: only the row models and registries the component
  * actually drives are registered. `columnMeta` is a type-only slot that
@@ -47,6 +56,38 @@ type DataTableProps<TData extends RowData> = {
     loading?: boolean;
     /** Keep the header visible while the table body scrolls. */
     stickyHeader?: boolean;
+    /**
+     * Window the table body so only rows near the viewport stay mounted,
+     * reusing the library's `VirtualList`. `true` uses the default row
+     * height; an object pins it explicitly (plus an optional `overscan`,
+     * default 5).
+     *
+     * The default height is `34px` — the natural single-line row of the
+     * default cell styles: 2 × `--haze-space-2` padding (16px) + a 14px
+     * (`--haze-text-sm`) line box + the 1px row border.
+     *
+     * Limitations and tradeoffs (evaluated against keeping `<tr>`s in one
+     * shared table): `VirtualList` positions rows through absolutely
+     * positioned `div` wrappers, and `position: absolute` blockifies
+     * `display: table-row` — so rows cannot stay in the header's table.
+     * Instead each row renders as a complete sibling `<table><tbody><tr>`
+     * inside the wrapper. Rows remain legal, axe-clean table structures
+     * with row/cell roles, and `table-layout: fixed` on header and rows
+     * distributes columns equally in both, keeping them aligned without a
+     * column-width measurement pass. Consequences:
+     * - Fixed row height only — dynamic or wrapping row heights are not
+     *   supported; content taller than `rowHeight` overlaps the next row.
+     * - Columns distribute equally instead of auto-sizing to content;
+     *   per-column widths are not supported in this mode.
+     * - The header sits outside the scroll window (always visible) — the
+     *   `stickyHeader` behavior is implied.
+     * - The root must be height-bounded by the consumer (e.g. a
+     *   `className` setting `height`/`max-height`, or a sized flex
+     *   parent); unbounded, the viewport degenerates to a single row.
+     * - Sorting, selection, pagination and `getRowId` semantics are
+     *   unchanged — the window always shows the post-sort, post-page slice.
+     */
+    virtualized?: DataTableVirtualized;
     /** Stable row identity; also keys the `rowSelection` state. Defaults to
      * the row's index. */
     getRowId?: (row: TData, index: number) => string;
@@ -57,5 +98,5 @@ type DataTableProps<TData extends RowData> = {
     empty?: ReactNode;
     className?: string;
 } & Omit<ComponentPropsWithoutRef<'table'>, 'children'>;
-export default function DataTable<TData extends RowData>({ columns, data, sortable, selectable, rowSelection: rowSelectionControl, sorting: sortingControl, pageSize, page: pageControl, loading, stickyHeader, getRowId, onRowClick, empty, className, ...rest }: DataTableProps<TData>): import("react").JSX.Element;
-export type { DataTableProps, DataTableColumnDef, DataTableColumnMeta };
+export default function DataTable<TData extends RowData>({ columns, data, sortable, selectable, rowSelection: rowSelectionControl, sorting: sortingControl, pageSize, page: pageControl, loading, stickyHeader, virtualized, getRowId, onRowClick, empty, className, ...rest }: DataTableProps<TData>): import("react").JSX.Element;
+export type { DataTableProps, DataTableColumnDef, DataTableColumnMeta, DataTableVirtualized, };

package/dist/types/components/DataTable/index.d.ts

@@ -1,2 +1,2 @@
 export { default as DataTable } from './DataTable';
-export type { DataTableProps, DataTableColumnDef, DataTableColumnMeta, } from './DataTable';
+export type { DataTableProps, DataTableColumnDef, DataTableColumnMeta, DataTableVirtualized, } from './DataTable';

package/dist/types/components/LocaleProvider/LocaleContext.d.ts

@@ -9,7 +9,7 @@ type HazeStringsOverrides = {
  * defaults → outermost → innermost per section key.
  */
 type LocaleContextValue = {
-    /** Reserved for Intl-based formatting in a future release. */
+    /** BCP 47 tag; `useStrings` resolves it to a built-in string pack. */
     locale?: string;
     strings?: HazeStringsOverrides;
     parent?: LocaleContextValue;

package/dist/types/components/LocaleProvider/LocaleProvider.d.ts

@@ -2,8 +2,11 @@ import type { ReactNode } from 'react';
 import type { HazeStringsOverrides } from './LocaleContext';
 type LocaleProviderProps = {
     /**
-     * BCP 47 language tag. Currently stored and inherited only — no
-     * library string is formatted through Intl yet.
+     * BCP 47 language tag selecting the built-in string pack: Chinese
+     * variants ('zh', 'zh-CN', 'zh_TW', …) serve the bundled zh-CN
+     * copy, any other value falls back to English. Unset inherits the
+     * tag from the enclosing provider; `strings` still layers on top
+     * of the selected pack.
      */
     locale?: string;
     strings?: HazeStringsOverrides;

package/dist/types/components/LocaleProvider/index.d.ts

@@ -2,5 +2,6 @@ export { default } from './LocaleProvider';
 export type { LocaleProviderProps } from './LocaleProvider';
 export { useStrings } from './useStrings';
 export type { HazeStringsOverrides } from './LocaleContext';
-export { defaultStrings } from './locale';
+export { defaultStrings, enUS } from './locale';
 export type { HazeStrings } from './locale';
+export { zhCN } from './zh-cn';

package/dist/types/components/LocaleProvider/locale.d.ts

@@ -97,6 +97,10 @@ declare const defaultStrings: {
         all: string;
         noLogs: string;
     };
+    mentions: {
+        label: string;
+        noMatch: string;
+    };
     modelPicker: {
         label: string;
     };
@@ -173,4 +177,6 @@ export type HazeStrings = typeof defaultStrings;
  * can never blank out a label.
  */
 declare function formatString(template: string, params: Record<string, string | number>): string;
-export { defaultStrings, formatString };
+/** English copy — the default pack, aliased for symmetry with `zhCN`. */
+declare const enUS: HazeStrings;
+export { defaultStrings, enUS, formatString };

package/dist/types/components/LocaleProvider/useStrings.d.ts

@@ -1,9 +1,10 @@
 import type { HazeStrings } from './locale';
 /**
- * Resolved copy for one component: the section of `defaultStrings`
- * layered with every enclosing provider's override, key by key, so the
- * innermost provider wins conflicts and silent keys keep outer (or
- * default) values. Falls back to the defaults when no provider is
+ * Resolved copy for one component: the section of the built-in pack
+ * selected by the provider chain's effective `locale`, layered with
+ * every enclosing provider's override, key by key, so the innermost
+ * provider wins conflicts and silent keys keep outer (or pack)
+ * values. Falls back to the English defaults when no provider is
  * mounted.
  */
 export declare function useStrings<K extends keyof HazeStrings>(componentKey: K): Readonly<HazeStrings[K]>;

package/dist/types/components/LocaleProvider/zh-cn.d.ts

@@ -0,0 +1,13 @@
+import type { HazeStrings } from './locale';
+/**
+ * Simplified Chinese (zh-CN) copy for every user-visible literal in
+ * the library. `LocaleProvider` selects this pack automatically for
+ * Chinese BCP 47 tags ('zh', 'zh-CN', 'zh_TW', …).
+ *
+ * Keys mirror `defaultStrings` 1:1 — the `HazeStrings` annotation
+ * fails the build when either pack drifts out of sync. `{name}`
+ * placeholders must survive translation verbatim; they are expanded
+ * by `formatString` at runtime.
+ */
+declare const zhCN: HazeStrings;
+export { zhCN };

package/dist/types/components/Mentions/Mentions.d.ts

@@ -0,0 +1,17 @@
+import type { ComponentPropsWithoutRef } from 'react';
+import type { ControlOrValue } from 'react-use-control';
+import type { MentionsOption } from './MentionsCore';
+type MentionsProps = {
+    value?: ControlOrValue<string>;
+    onChange?: (value: string) => void;
+    options: MentionsOption[];
+    /**
+     * Single character that opens the suggestion panel while typing.
+     * Defaults to '@'.
+     */
+    trigger?: string;
+    placeholder?: string;
+    className?: string;
+} & Omit<ComponentPropsWithoutRef<'textarea'>, 'value' | 'onChange' | 'placeholder' | 'className' | 'style'>;
+export default function Mentions({ value: valueControl, onChange, ...rest }: MentionsProps): import("react").JSX.Element;
+export type { MentionsProps };

package/dist/types/components/Mentions/MentionsCore.d.ts

@@ -0,0 +1,21 @@
+import type { ComponentPropsWithoutRef } from 'react';
+export type MentionsOption = {
+    /** Text inserted after the trigger character when picked. */
+    value: string;
+    /** Display text; falls back to `value` when omitted. */
+    label?: string;
+};
+type MentionsCoreProps = {
+    value: string;
+    onChange: (value: string) => void;
+    options: MentionsOption[];
+    /**
+     * Single character that opens the suggestion panel while typing.
+     * Defaults to '@'.
+     */
+    trigger?: string;
+    placeholder?: string;
+    className?: string;
+} & Omit<ComponentPropsWithoutRef<'textarea'>, 'value' | 'onChange' | 'placeholder' | 'className' | 'style'>;
+export default function MentionsCore({ value, onChange, options, trigger, placeholder, className, 'aria-label': ariaLabel, ...rest }: MentionsCoreProps): import("react").JSX.Element;
+export type { MentionsCoreProps };

package/dist/types/components/Mentions/index.d.ts

@@ -0,0 +1,4 @@
+export { default as Mentions } from './Mentions';
+export type { MentionsProps } from './Mentions';
+export { default as MentionsCore } from './MentionsCore';
+export type { MentionsCoreProps, MentionsOption } from './MentionsCore';

package/dist/types/hooks/index.d.ts

@@ -1 +1,7 @@
+export { useClipboard } from './useClipboard';
+export type { UseClipboardResult } from './useClipboard';
+export { useDebouncedCallback } from './useDebouncedCallback';
+export { useDebouncedValue } from './useDebouncedValue';
+export { useMediaQuery } from './useMediaQuery';
+export { usePrefersReducedMotion } from './usePrefersReducedMotion';
 export { useTitle } from './useTitle';

package/dist/types/hooks/useClipboard.d.ts

@@ -0,0 +1,31 @@
+type UseClipboardResult = {
+    /** 最近一次成功复制后的反馈窗口内为 `true`，`resetMs` 后回落 `false`。 */
+    copied: boolean;
+    /**
+     * 复制文本到剪贴板，成功返回 `true`。优先异步剪贴板 API，失败退化
+     * `document.execCommand('copy')`；两条路径都失败返回 `false` 且
+     * `copied` 不置位。
+     */
+    copy: (text: string) => Promise<boolean>;
+};
+/**
+ * 复制文本到剪贴板并跟踪「已复制」反馈状态。
+ *
+ * ```tsx
+ * const { copied, copy } = useClipboard();
+ * <Button onClick={() => copy(shareLink)}>{copied ? '已复制' : '复制链接'}</Button>
+ * ```
+ *
+ * - 优先 `navigator.clipboard.writeText`；不可用（undefined 时访问属性
+ *   即抛 TypeError）或被权限拒绝时，退化到隐藏 textarea +
+ *   `document.execCommand('copy')`。两条路径都失败返回 `false`。
+ * - 复制成功后 `copied` 置 `true`，`resetMs`（默认 2000）后自动回落；
+ *   窗口内再次成功复制会重置计时。
+ * - SSR：`navigator` / `document` 只在 `copy` 事件回调里触碰，服务端
+ *   渲染安全（`copied` 初始 `false`，无 hydration 差异）；reset 计时器
+ *   随卸载清理。
+ *
+ * @param resetMs `copied` 从 `true` 回落的延迟（毫秒），默认 2000。
+ */
+export declare function useClipboard(resetMs?: number): UseClipboardResult;
+export type { UseClipboardResult };