@sub-zero/cocoa 0.1.0 → 0.2.0

package/README.md

@@ -1,6 +1,6 @@
 # Cocoa
 
-A bottom-right support chat bubble for any web application. Cocoa connects visitors
+A circular Cocoa portrait button that opens support chat at the bottom right of any web application. Cocoa connects visitors
 to your SubZero chatbot and puts conversations in **Agents → Chatbots**, where your
 team can view, reply, approve agent drafts, and take over.
 
@@ -135,10 +135,10 @@ redirects rejected. An allowed website origin controls embedding; it does not
 verify the visitor's identity. Do not provide account-specific private data
 based only on a name typed into chat.
 
-For Content Security Policy, allow the API under `connect-src`, the script source
+For Content Security Policy, allow `data:` under `img-src` for the bundled Cocoa portrait, the API under `connect-src`, the script source
 under `script-src`, and supply a valid nonce through the `nonce` option (or script
 nonce attribute) for the widget stylesheet. The widget uses DOM APIs and is
-compatible with Trusted Types enforcement. No remote fonts, images,
+compatible with Trusted Types enforcement. The supplied Cocoa portrait is bundled in the widget, so it needs no external image host. No remote fonts, images,
 iframes, analytics, model SDKs, or third-party styles are loaded.
 
 Existing SubZero chat webhooks and human approval policies apply unchanged. RDK
@@ -163,3 +163,9 @@ contains only `dist`, this README, and package metadata. Do not publish the priv
 Angular application root. Review the version and `npm pack --dry-run` output before
 publishing. No open-source license is granted (`UNLICENSED`); the source repository
 may be private.
+
+## Incident handoff
+
+The visible **Get further help** action opens a review form. The visitor chooses a correspondence email and explicitly submits an incident; neither opening chat nor mentioning an email creates one. The current visitor session authorizes creation in the chatbot's project. A confirmed reference survives reload, and failed submissions retain their text and idempotency key for retry. The team's follow-up is by email. The email is not verified account identity.
+
+Requires the SubZero chat-escalation API. Closed conversations can still submit while their visitor credential is valid; paused deployments cannot accept new submissions. No model call is needed for handoff. `reset()` clears the chat, pending form and visitor credential; call it on logout/account changes. SMTP acknowledgement delivery retries are at-least-once; a stable Message-ID assists threading but cannot guarantee exactly-once delivery by an external mail server.