@lightworkai.official/debug-capture 0.18.0 → 0.19.0

package/README.md

@@ -199,6 +199,9 @@ knowing before you ship:
 - **`callFrame`** — the call itself happens in your app, in the support host's
   own call UI (0.16, see below). Default `true`; `false` keeps 0.15's card that
   opens the portal to answer.
+- **`chat`** — แชทกับทีม, a chat bubble at the bottom of your app (0.19, see
+  below). Off unless set; `true`, or `{ position: "left", offset: { x, y } }`.
+  Needs `identity`.
 
 ## The other half: letting people track what they reported
 
@@ -244,11 +247,16 @@ export const GET = supportTokenHandler({
   // The one thing we cannot do for you: only you can read your session.
   user: async () => {
     const session = await getServerSession(authOptions);
-    return session?.user?.email ? { id: session.user.id, email: session.user.email } : null;
+    return session?.user ? { id: session.user.id, email: session.user.email } : null;
   },
 });
 ```
 
+Someone you know but hold no email for — signed in with a national ID, say — is
+vouched for by your own `id` alone (0.18): leave `email` out or null. The
+support desk keeps one account for them by that id, and moves it to their email
+the day you have one. Return null only when nobody is signed in.
+
 It returns a standard `Response`, so it works anywhere the Fetch API does — Bun,
 Deno, Hono, Next. The secret comes from `SUPPORT_REPORTER_SECRET` unless you
 pass one. `createSupportToken()` is the same thing without the routing, if your
@@ -437,6 +445,34 @@ While the person shares their screen, the call itself folds to a single bar,
 so it covers very little of your page; that comes from the support host and
 needs no update here.
 
+### A chat with the support team, no report needed (0.19)
+
+People do not only report problems — they ask: how to do something, for a
+permission, whether what they see is a problem at all. Until now the only door
+was the report button, so questions arrived as reports (or by LINE, outside the
+desk). `chat: true` puts a round chat button at the bottom right of your app:
+
+```ts
+configureDebugCapture({ /* … */, identity: async () => /* your support token */, chat: true });
+```
+
+Pressed, a panel opens above it — the support host's own page, framed, signed
+in with the token your `identity` already provides (handed over by
+`postMessage`, never in the address). It has two tabs: **แชท**, the person's
+one ongoing chat with the desk, and **เรื่องของฉัน**, what they filed, each
+opening its thread in the panel. The desk answers from สนทนา › แชท and can open
+a ticket from the chat (the chat keeps every line and shows the ticket's card).
+**แจ้งปัญหาพร้อมภาพหน้าจอ** in the panel folds it and opens this library's
+report over your page — its screen, its logs — linked to the chat.
+
+The button carries a badge of what waits for the person (the desk's new lines
+and their tickets' replies), kept current by the same socket the call ring
+uses — with calls off for the desk too. The call's card and frame sit above
+the button. It is not shown when nobody is signed in (`identity` returns
+null). Your own button instead of ours: `openSupportChat()` /
+`closeSupportChat()`; on a page with no bundler, `data-chat` and
+`data-identity-url` on the script tag, and `window.lwOpenSupportChat()`.
+
 
 ## Installing
 

package/dist/config.d.ts

@@ -105,6 +105,16 @@ export interface DebugCaptureConfig {
     } | null;
     /** Anything else worth recording — feature flags, build id, tenant. */
     extra?: () => Record<string, unknown>;
+    /**
+     * แชทกับทีม — a chat bubble at the bottom right: the person asks the support desk anything, no report needed, and
+     * follows what they filed (เรื่องของฉัน) in the same panel. The desk answers from สนทนา › แชท and can open a เรื่อง
+     * from it; แจ้งปัญหาพร้อมภาพหน้าจอ in the panel opens this library's report, linked to the chat.
+     *
+     * Off unless set. Needs `identity` — a chat is a person's, and is read back: with no signed-in person the bubble is
+     * not shown. `true` puts it at the bottom right; `{ position: "left" }` at the bottom left; `offset` moves it in from
+     * the corner (px) for a host that already has something there.
+     */
+    chat?: boolean | ChatOptions;
     capture?: CaptureOptions;
     redact?: RedactOptions;
     /**
@@ -198,6 +208,22 @@ export interface ToastNotice {
         onClick: () => void;
     };
 }
+/** Where แชทกับทีม's bubble sits (`chat`). */
+export interface ChatOptions {
+    /** Which bottom corner — the right unless said. */
+    position?: "right" | "left";
+    /** In from that corner, in px — for a host that already has something there. */
+    offset?: {
+        x?: number;
+        y?: number;
+    };
+}
+/** The bubble's place, from `chat`: null when it is off. */
+export declare function chatPlace(chat: DebugCaptureConfig["chat"]): {
+    side: "right" | "left";
+    x: number;
+    y: number;
+} | null;
 export interface CaptureOptions {
     /** Rolling buffer sizes. */
     maxRequests?: number;