@lightworkai.official/debug-capture 0.14.2 → 0.15.0

package/README.md

@@ -86,11 +86,14 @@ Where the support desk opens request types to its reporters (ใครขอไ
 - **แจ้งปัญหา**: the screen share starts inside that press, then the report
   form, as it has always been.
 - **คำขอ**: the request form straight away, with **no screen share asked
-  for**. The person picks what they need from the desk's types (a card each,
-  with how long the team aims to take), a title and details; the page's
+  for**. The person picks what they need from the desk's types — the one chosen
+  shows its description and how long the team aims to take, the rest stay one
+  line, and from 7 types there is a search — a title and details; the page's
   address travels with it, the page's logs do not.
 
-The form keeps both cards, so it can be switched any time with nothing typed
+The form then names the choice in its heading (รายงานปัญหา or
+ขอให้ทีมดำเนินการ) and keeps one quiet line to switch — **เป็นคำขอ?
+เลือกเรื่องที่ขอ** or **เป็นปัญหาที่ต้องแก้? แจ้งปัญหาแทน** — with nothing typed
 lost: from a report to คำขอ the screenshot comes along (and can be unticked);
 from a request to แจ้งปัญหา the share is asked for at that press — refused, the
 request stays as it was. A request is filed typed, its steps begun on the
@@ -191,6 +194,8 @@ knowing before you ship:
   secret the defaults do not know about.
 - **`module(pathname)`** — becomes the ticket's category. Defaults to the first
   path segment.
+- **`ring`** — a call from the support team rings in your app (see below).
+  Default `true`; `false` leaves calls to the support host.
 
 ## The other half: letting people track what they reported
 
@@ -336,6 +341,31 @@ thrown for you to handle.
 
 `supportPortalUrl(host, realmKey, token, returnTo?)` is pure and safe to call on a server.
 
+### A call from the support team rings here (0.15)
+
+The support team can call a reporter from their ticket — voice, and their screen
+if they choose to share it. The call happens on the support host; what this
+package adds is the **ring, in your app**: with `identity` configured and calls
+switched on for the desk, the widget holds the person's own live connection to
+the support host (the one their portal tab holds, proven with the same signed
+token, told about their own tickets and calls and nothing else). A call then
+shows as a card — *ทีมงานกำลังโทรหาคุณ · เรื่อง ACME-12* — with **ไม่รับ** and
+**เปิดเพื่อรับสาย**, a soft ring and the tab's title. Opening it takes them to
+that ticket on the support host, signed in, where they answer.
+
+Nothing to wire: it starts with `installDebugCapture()`, once the page has
+settled. It stays silent — no connection, no card, no console noise — without
+`identity`, with calls off for the desk, against a support host older than 0.15,
+or when the token is refused. To leave calls to the support host and its
+invitation instead:
+
+```ts
+configureDebugCapture({ /* … */, ring: false });
+```
+
+A host that renders its own UI (`installDebugCapture({ ui: false })`) can start
+and stop it itself with `startLiveRing()` / `stopLiveRing()`.
+
 
 ## Installing
 

package/dist/config.d.ts

@@ -139,6 +139,17 @@ export interface DebugCaptureConfig {
     screenshotFallback?: () => Promise<ToPng | null>;
     /** UI language. Only affects the built-in reporter's own strings. */
     locale?: "th" | "en";
+    /**
+     * The ring for a call from the support team. Default true.
+     *
+     * With `identity` set and calls switched on for the desk, the reporter's own
+     * live connection to the support host is held here — the one their portal
+     * tab holds, proven with the same signed token — so a call from the team
+     * rings in this app, as a card, and opens the reporter's request on the
+     * support host to answer it (the call itself happens there). `false` leaves
+     * calls to the support host and the invitation the team sends.
+     */
+    ring?: boolean;
     /**
      * Where this library's own notifications go.
      *