@@ -0,0 +1,31 @@
+---
+'@object-ui/types': minor
+'@object-ui/components': minor
+'@object-ui/plugin-chatbot': minor
+'@object-ui/plugin-report': minor
+---
+
+Clause-②: yes
+Metadata-protocol: added
+
+Nine duration keys now carry their unit in their name (objectstack#25762). Each one said its unit only in its description, so `timeout: 300` read as either milliseconds or seconds. After objectui merges into objectstack, `@objectstack/spec`'s `check:duration-unit-keys` judges these schemas too, and the maintainer chose to rename the keys rather than exempt them. The renames follow objectstack's own (`…Ms` / `…Seconds`, the unit each description already stated). The value and its unit do not change, only the key name. This is breaking for a document that still writes an old name; it is marked `minor` under this repository's version policy.
+
+| Node / schema | FROM | TO | Unit |
+|---|---|---|---|
+| `carousel` (`CarouselSchema`) | `autoPlay` | `autoPlayMs` | milliseconds |
+| `chatbot`, `chatbot-enhanced`, `chatbot-floating` | `autoResponseDelay` | `autoResponseDelayMs` | milliseconds |
+| `ActionSchema` | `timeout` | `timeoutMs` | milliseconds |
+| `ActionSchema.retry` | `delay` | `delayMs` | milliseconds |
+| `toast` (`ToastSchema`) | `duration` | `durationMs` | milliseconds |
+| `tooltip` (`TooltipSchema`) | `delayDuration` | `delayDurationMs` | milliseconds |
+| `hover-card` (`HoverCardSchema`) | `openDelay` | `openDelayMs` | milliseconds |
+| `hover-card` (`HoverCardSchema`) | `closeDelay` | `closeDelayMs` | milliseconds |
+| `report` (`ReportComponentSchema`) | `refreshInterval` | `refreshIntervalSeconds` | seconds |
+
+What an author sees with an old name:
+
+- **zod (`@object-ui/types/zod`).** The old key is still declared, as a tombstone, so it is refused at its own path with code `invalid_type`. The message names the new key: "`timeout` is now `timeoutMs` … the value (milliseconds) is unchanged." Without the tombstone, `.passthrough()` would keep the value and nothing would read it.
+- **TypeScript.** The old member is `?: never` with `@deprecated`, so a typed literal that writes it fails to compile.
+- **Renderers.** `toast`, `tooltip`, `hover-card`, the three chatbot registrations and `ReportViewer` read the new key. Their registration `inputs` and `defaultProps` use the new name too. The `useObjectChat` hook option `autoResponseDelay` is a programmatic API, not a schema key, and keeps its name.
+
+objectui has no conversion registry: ADR-0087's D2 table lives in `@objectstack/spec`. The conversion is this table plus the refusal message. To migrate, rename each key as the table shows and keep the value.
@@ -667,7 +667,7 @@ A powerful action definition supporting API calls, confirmations, dialogs, chain
   "condition": "${data.items.length > 0}",
   "retry": {
     "maxAttempts": 3,
-    "delay": 1000
+    "delayMs": 1000
   }
 }
 ```
@@ -689,7 +689,7 @@ A powerful action definition supporting API calls, confirmations, dialogs, chain
 | `successMessage` / `errorMessage` | `string` | Toast messages on success/failure. |
 | `reload` | `boolean` | Reload data after action completes. |
 | `redirect` | `string` | URL to navigate to after action. |
-| `retry` | `object` | Retry config with `maxAttempts` and `delay`. |
+| `retry` | `object` | Retry config with `maxAttempts` and `delayMs` (milliseconds; renamed from `delay`, objectstack#25762). |
 
 **Related:** [DetailSchema](#detailschema), [ButtonSchema](#buttonschema)
 
 
@@ -10,7 +10,7 @@ The Toast component displays brief notifications to users that appear temporaril
 ## Basic Usage
 
 A `toast` node renders its own trigger button. Clicking the button raises the toast the
-node declares — the title, description, variant and duration are all read off the node
+node declares — the title, description, variant and `durationMs` are all read off the node
 itself, so the whole demo is one schema node with no handler to wire up.
 
 <SchemaExample id="components-feedback-toast/basic-toast" />
@@ -38,7 +38,7 @@ interface ToastSchema {
   variant?: 'default' | 'success' | 'warning' | 'error' | 'info';
 
   // Timing
-  duration?: number;              // Auto-dismiss time in ms
+  durationMs?: number;            // Auto-dismiss time in ms
 }
 ```
 
 
@@ -20,8 +20,8 @@ interface HoverCardSchema {
   content: SchemaNode | SchemaNode[];   // Card content
   side?: 'top' | 'right' | 'bottom' | 'left';
   align?: 'start' | 'center' | 'end';
-  openDelay?: number;                   // Delay before opening (ms)
-  closeDelay?: number;                  // Delay before closing (ms)
+  openDelayMs?: number;                 // Delay before opening (ms)
+  closeDelayMs?: number;                // Delay before closing (ms)
   className?: string;
 }
 ```
@@ -19,7 +19,7 @@ interface TooltipSchema {
   children?: SchemaNode | SchemaNode[]; // Rich content — the fallback half
   side?: 'top' | 'right' | 'bottom' | 'left';
   align?: 'start' | 'center' | 'end';
-  delayDuration?: number;               // Delay before showing (ms)
+  delayDurationMs?: number;             // Delay before showing (ms)
 }
 ```
 
 
@@ -64,8 +64,8 @@ const ajaxAction: ActionSchema = {
 - `method` - HTTP method (GET, POST, PUT, DELETE, PATCH)
 - `data` - Request body/payload
 - `headers` - Custom HTTP headers
-- `timeout` - Request timeout in milliseconds
-- `retry` - Retry configuration
+- `timeoutMs` - Request timeout in milliseconds (renamed from `timeout`)
+- `retry` - Retry configuration (`maxAttempts`, `delayMs`)
 
 ### Confirm Actions
 
@@ -389,11 +389,11 @@ const retryAction: ActionSchema = {
   api: '/api/submit',
   method: 'POST',
 
-  timeout: 30000,  // 30 seconds
+  timeoutMs: 30000,  // 30 seconds
 
   retry: {
     maxAttempts: 3,
-    delay: 1000  // 1 second between retries
+    delayMs: 1000  // 1 second between retries
   }
 };
 ```
@@ -467,10 +467,10 @@ const complexAction: ActionSchema = {
   },
 
   // Retry
-  timeout: 60000,
+  timeoutMs: 60000,
   retry: {
     maxAttempts: 3,
-    delay: 2000
+    delayMs: 2000
   },
 
   // Post-action behavior
 
@@ -399,7 +399,7 @@ const comprehensiveReport: ReportComponentSchema = {
   showExportButtons: true,
   showPrintButton: true,
   showScheduleButton: true,
-  refreshInterval: 300  // Auto-refresh every 5 minutes
+  refreshIntervalSeconds: 300  // Auto-refresh every 5 minutes
 };
 ```
 
 
@@ -98,7 +98,7 @@ const schema: ChatbotSchema = {
   maxHeight?: string,
   autoResponse?: boolean,
   autoResponseText?: string,
-  autoResponseDelay?: number,
+  autoResponseDelayMs?: number,
   onSend?: (content: string, messages: ObjectChatMessage[]) => void,
   className?: string,
   // AI / service-ai integration fields
@@ -179,7 +179,7 @@ to apply. They are documented in their own table after this one, under
 | `maxHeight` | string | `'500px'` | **`chatbot` and `chatbot-enhanced` only** (declared on `ChatbotSchema` and `ChatbotEnhancedSchema`; `ChatbotFloatingSchema` does not declare it). Maximum height of the chat message container, as a CSS length. `chatbot-floating` does not read it: its panel is sized by `floatingConfig.panelHeight` (a **number** of pixels, default `520`), and the panel pins its inner chat to `maxHeight: '100%'` so it fills that panel - a `maxHeight` authored on a floating node would be overridden even if it were forwarded. Size a floating chatbot with `floatingConfig.panelHeight` instead |
 | `autoResponse` | boolean | `false` | Enable auto-response (demo mode, ignored when `api` is set) |
 | `autoResponseText` | string | - | Text for auto-response |
-| `autoResponseDelay` | number | `1000` | Delay before auto-response (ms) |
+| `autoResponseDelayMs` | number | `1000` | Delay before auto-response, in milliseconds (renamed from `autoResponseDelay`, which is now refused with a message naming this key) |
 | `onSend` | function | - | Callback when message is sent |
 | `className` | string | `''` | Additional Tailwind CSS classes |
 | `api` | string | - | Backend SSE endpoint (e.g., `/api/v1/ai/chat`). Enables AI streaming mode |
@@ -329,7 +329,7 @@ const schema: ChatbotSchema = {
   messages: [], // seed with your own ChatMessage values
   autoResponse: true,
   autoResponseText: 'Thanks!',
-  autoResponseDelay: 1000,
+  autoResponseDelayMs: 1000,
 };
 ```
 
@@ -554,7 +554,7 @@ const salesBot: ChatbotSchema = {
   userAvatarFallback: 'You',
   autoResponse: true,
   autoResponseText: 'Great choice! Let me show you some options...',
-  autoResponseDelay: 1200,
+  autoResponseDelayMs: 1200,
   maxHeight: '500px',
   className: 'border-2 border-primary rounded-xl'
 };
 
@@ -3,5 +3,5 @@
   "variant": "success",
   "title": "Saved Successfully",
   "description": "Your changes have been saved.",
-  "duration": 3000
+  "durationMs": 3000
 }
@@ -11,6 +11,6 @@
   "showTimestamp": false,
   "autoResponse": true,
   "autoResponseText": "Thank you for your message! This is an automated response.",
-  "autoResponseDelay": 1000,
+  "autoResponseDelayMs": 1000,
   "maxHeight": "400px"
 }
Original file line number	Diff line number	Diff line change
`@@ -19,7 +19,7 @@ interface TooltipSchema {`
`19`	`19`	`children?: SchemaNode \| SchemaNode[]; // Rich content — the fallback half`
`20`	`20`	`side?: 'top' \| 'right' \| 'bottom' \| 'left';`
`21`	`21`	`align?: 'start' \| 'center' \| 'end';`
`22`		`- delayDuration?: number; // Delay before showing (ms)`
	`22`	`+ delayDurationMs?: number; // Delay before showing (ms)`
`23`	`23`	`}`
`24`	`24`	```
`25`	`25`
Original file line number	Diff line number	Diff line change
`@@ -3,5 +3,5 @@`
`3`	`3`	`"variant": "success",`
`4`	`4`	`"title": "Saved Successfully",`
`5`	`5`	`"description": "Your changes have been saved.",`
`6`		`- "duration": 3000`
	`6`	`+ "durationMs": 3000`
`7`	`7`	`}`
Original file line number	Diff line number	Diff line change
`@@ -11,6 +11,6 @@`
`11`	`11`	`"showTimestamp": false,`
`12`	`12`	`"autoResponse": true,`
`13`	`13`	`"autoResponseText": "Thank you for your message! This is an automated response.",`
`14`		`- "autoResponseDelay": 1000,`
	`14`	`+ "autoResponseDelayMs": 1000,`
`15`	`15`	`"maxHeight": "400px"`
`16`	`16`	`}`