@lightworkai.official/debug-capture 0.19.5 → 0.19.7

package/README.md

@@ -201,7 +201,8 @@ knowing before you ship:
   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`.
+  Needs `identity`. `avoid` (0.19.6): `false` keeps it where you put it even
+  over your page's own floating controls; a selector names more of them.
 
 ## The other half: letting people track what they reported
 
@@ -487,7 +488,16 @@ panel's head has เปิดในระบบแจ้งปัญหา (0.19
 panel was on (the chat, the person's tickets, or the one open). The team can
 call from the chat too, and the person can ask for a call back there (0.19.4):
 the ring card says จากแชทกับทีมงาน instead of a ticket's key, and its fallback
-opens their chat. The bubble's look is the support desk's to set (0.19.5, its
+opens their chat. Your page's own floating controls come first (0.19.6): a
+toolbar, a FAB, a bottom bar, a sticky action bar, or a control that stays put
+on a page that does not scroll is never covered — the button takes the nearest
+free place, up its own side or in the other corner when that is nearer than a
+long climb, and back where it was once that is free again (0.19.7). Content that scrolls
+under it is not in the way. `chat: { avoid: false }` turns this off,
+`avoid: ".my-dock"` names a piece of your page it would not see. The desk can
+also give a page its own place — hidden there, or a corner and a height — by
+its path (ปุ่มแชท › ตำแหน่งปุ่ม); a person who moved the button keeps their
+place, except where it is hidden. The bubble's look is the support desk's to set (0.19.5, its
 ปุ่มแชท settings page): its face, colour and words, read with the first answer;
 your own `label` in code still wins. A desk can turn the bubble off for every
 host at once. `chat: { show: () => boolean }` decides per person or per page

package/dist/config.d.ts

@@ -64,8 +64,11 @@ export interface DebugCaptureConfig {
      *            { algorithm: 'HS256', expiresIn: '1h' })
      *
      * The SECRET NEVER REACHES THE BROWSER. This callback fetches the finished
-     * token from your own backend; it is called per request, so cache it on your
-     * side until it is close to expiring.
+     * token from your own backend. Mint a FRESH one on every call — never hand
+     * back a kept one: besides its own reads, the widget signs the person in with
+     * it (the chat panel, the portal, a call), and a sign-in takes a token only
+     * while it is two minutes old, and only once. Sharing one request already in
+     * flight is fine.
      *
      * Returning null means "nobody is signed in" — the panel says so rather than
      * failing.
@@ -229,6 +232,12 @@ export interface ChatOptions {
      * `refreshSupportChat()`.
      */
     show?: () => boolean;
+    /**
+     * Out of the page's own way (0.19.6): the bubble steps aside from the page's floating controls — a toolbar, a FAB, a
+     * bottom bar, a fixed sidebar — to the nearest free place. On unless `false`; a CSS selector names more of your own
+     * to keep clear of, whatever their position (`"[data-floating], .my-dock"`). The desk can turn it off too (ปุ่มแชท).
+     */
+    avoid?: boolean | string;
 }
 /** The bubble's place, from `chat`: null when it is off. */
 export declare function chatPlace(chat: DebugCaptureConfig["chat"]): {