@crossworks/client-types 0.232.335 → 0.232.337

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@crossworks/client-types",
-  "version": "0.232.335",
+  "version": "0.232.337",
   "type": "module",
   "main": "./src/index.ts",
   "types": "./src/index.ts",

package/src/dto/client.ts

@@ -224,3 +224,44 @@ export type ClientSigninSenderPreview = {
 /** Why an admin's sender choice was refused (the 4xx `reason`). */
 export type ClientSenderRefusedReason =
   'account-not-found' | 'account-cannot-send' | 'no-sent-folder' | 'folders-unreadable';
+
+// ── Client chat (client logins C4) ───────────────────────────────────────
+
+/** One message of a client's own chat thread. */
+export type ClientChatMessage = {
+  id: string;
+  direction: 'inbound' | 'outbound';
+  text: string;
+  status: 'pending' | 'complete' | 'failed';
+  failed: boolean;
+  createdAt: string;
+};
+
+/** GET /api/client/chat[?before=ISO]: the client's own thread with the
+ *  client-responder, newest page first (50 a page). `agent` null = the chat
+ *  is not open (no enabled client-level client-responder): the dock says so
+ *  and offers no input. Poll it (every few seconds while a reply is pending):
+ *  there is no live stream for clients. */
+export type ClientChatThread = {
+  agent: { name: string } | null;
+  messages: ClientChatMessage[];
+};
+
+/** POST /api/client/chat { text } -> 202: the turn is queued; the reply
+ *  lands in the thread. A retry with the same Idempotency-Key is the same
+ *  turn. */
+export type ClientChatQueued = { turnId: string };
+
+/** Why a client chat send was refused (the 4xx `reason`): 409 `chat-closed`
+ *  (no client-level agent), 409 `idempotency-key-reused`, 429 `rate-limited`
+ *  (6 a minute), 429 `daily_cap` or `token_budget` (the member caps, per
+ *  client login per UTC day). */
+export type ClientChatRefusedReason =
+  'chat-closed' | 'idempotency-key-reused' | 'rate-limited' | 'daily_cap' | 'token_budget';
+
+/** GET /api/team-admin/clients/usage: each client login's chat use today
+ *  (UTC) against the caps every client login has (the member caps). */
+export type ClientChatUsage = {
+  limits: { dailyTurns: number; dailyTokens: number };
+  rows: { loginId: string; turnsToday: number; tokensToday: number }[];
+};

package/src/dto/rows.ts

@@ -560,6 +560,10 @@ export type TeamRequest = {
   contactName: string | null;
   /** When the owner last posted a resolution to the member for this request. */
   notifiedAt: string | null;
+  /** True for a request a CLIENT login filed through the client-responder
+   *  (client logins C4, 0.232.336 on): the reply still goes into that
+   *  login's thread. Absent on older brains = a member's request. */
+  fromClient?: boolean;
 };
 
 /** The newest thing waiting in one "needs you" queue: its title and who it

package/src/index.ts

@@ -118,6 +118,11 @@ export type {
 } from './dto/logins';
 export type {
   ClientAdminRefusedReason,
+  ClientChatMessage,
+  ClientChatQueued,
+  ClientChatRefusedReason,
+  ClientChatThread,
+  ClientChatUsage,
   ClientLinkSignIn,
   ClientCodeAvailability,
   ClientCodeRequested,