@8wave/ai-elements 0.110.0-beta.4 → 0.111.0-beta.3

package/dist-vue/packages/components/src/table/PkTableSortable.d.ts

@@ -75,6 +75,14 @@ declare const __VLS_export: <TableRow extends Record<string | number | symbol, a
             type: BooleanConstructor;
             default: boolean;
         };
+        rowHover: {
+            type: BooleanConstructor;
+            default: boolean;
+        };
+        rowClass: {
+            type: PropType<(row: TableRow, index: number) => string | string[] | Record<string, boolean> | undefined>;
+            default: undefined;
+        };
     }> & {
         "onUpdate:limit"?: ((...args: any[]) => any) | undefined;
         "onUpdate:page"?: ((...args: any[]) => any) | undefined;

package/dist-vue/packages/models/src/schema/Chat.d.ts

@@ -247,6 +247,27 @@ export declare const ChatRequestSchema: z.ZodObject<{
     smoothStream: z.ZodOptional<z.ZodBoolean>;
 }, z.core.$strip>;
 export type ChatRequest = z.infer<typeof ChatRequestSchema>;
+/**
+ * What the chat route validates on the way in.
+ *
+ * Deliberately not `ChatRequestSchema`: a turn resumed after a client tool or
+ * a tool approval posts the assistant message back, whose parts are tool
+ * calls, and the part union above accepts text and files only. Pinning the
+ * body to it would answer 400 to a legitimate resume. So this validates the
+ * envelope the turn cannot run without and lets the rest through untouched
+ * (`loose`), which is also why the overrides the client sends still reach the
+ * service.
+ *
+ * The id is minted by the client and read back as a row key: without it the
+ * lookup ran with `undefined` and the route answered 500 instead of 400
+ * (found 2026-09-21).
+ */
+export declare const ChatRequestEnvelopeSchema: z.ZodObject<{
+    id: z.ZodString;
+    messages: z.ZodArray<z.ZodObject<{
+        role: z.ZodString;
+    }, z.core.$loose>>;
+}, z.core.$loose>;
 export declare enum BlockedReasonCode {
     SevereAbuse = "severe_abuse",
     HighRiskScore = "high_risk_score",