@chatsystem/client 1.3.3 → 2.0.1

package/README.md

@@ -103,6 +103,13 @@ the client itself; it must never be reimplemented in a host-specific adapter.
 
 ## Browser regression tests
 
+Local-preview feedback is translated through `react-intl`: completing or closing
+the form explicitly says that this was a demo and no answers were transmitted.
+The generic renderer does not promise storage, support handling or Slack delivery.
+The server-owned Tool presentation explains its own production journey (for
+example, the support-request inbox and optional Slack channel). This copy remains
+visible after completion without adding a Tool-name switch or browser protocol.
+
 The package has a Playwright suite under `e2e/identity-gate`. It builds this
 library, mounts it inside a fictional customer website, and drives a real
 headless Chromium through identity delegation, redirect/resume, shared-runtime
@@ -158,3 +165,49 @@ programmatic browser API so the provider functions remain JavaScript values:
 
 This passes the provider to the same internal `App` and identity session used
 by the npm package. Do not place callbacks or secrets in `data-*` attributes.
+
+## Custom CSS and layout
+
+Put custom rules in the Agent's `CSSRules`, which are inserted after the default
+widget styles inside its Shadow DOM. Host-page styles cannot select elements
+inside that boundary. A custom `cssHref` can also provide the widget stylesheet.
+
+| Selector | Layout contract |
+| --- | --- |
+| `.chatBox` | Chat surface; in launcher mode, the actual floating window |
+| `.chatsystem-widget-window` | Launcher window only; owns viewport positioning |
+| `.chatsystem-widget-surface` | Clips window contents and inherits its background and corners |
+| `.launcher` | Floating launcher button |
+| `.chatsystem-interactive-widget` | Form panel inside the scrolling conversation |
+
+For example, these Agent rules move the launcher and its window to the left:
+
+```css
+.chatsystem-widget-window, .launcher { left: 18px; right: auto; }
+.chatsystem-interactive-widget { border-radius: 6px; }
+```
+
+Legacy `.chatBox` positioning rules remain supported. Inline chat stays in normal
+document flow. Interactive forms stay in the message flow and scroll with it;
+they do not create a floating overlay. Defaults remain overridable in both the
+constructable stylesheet and style-tag fallback paths.
+
+## Completed AI answers per discussion
+
+The API controls the discussion allowance through
+`CompanySettingsDTO.api.settings.maxAiResponsesPerDiscussion`. Only completed,
+persisted final AI answers consume it; user messages, Tool exchanges,
+intermediate text and human support do not. This is not a context/token limit.
+The widget disables AI input at the limit and offers a new conversation.
+
+Shared chatbox/launcher views use the same absolute completion count. Validated
+`ai.response.completed` receipts are discussion-scoped, replay-safe and retained
+in local conversation history. Server admission remains authoritative if that
+history or a receipt is missing. A busy discussion is not quota exhaustion.
+
+This migration requires shared 2.0.0 and a compatible API; upgrade pinned widgets
+explicitly. No React prop, script data attribute or `mount()` option changes.
+Publish the npm component and standalone S3 bundle independently. Custom runtime
+adapters must return the new required settings field, expose `discussionId` and
+forward completion events through their existing NDJSON stream; `message_end`
+alone does not prove durable completion.