@chatsystem/client 1.3.2 → 2.0.0

package/README.md

@@ -101,6 +101,18 @@ Normal customer installations must omit this property and continue through the
 standard public installation endpoints. New presentation behavior belongs in
 the client itself; it must never be reimplemented in a host-specific adapter.
 
+## Browser regression tests
+
+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
+streaming and local interactive-widget preview scenarios.
+
+Run it from this directory with `npm run test:identity-gate`. It uses only local
+fixtures and fictional data. See
+[`e2e/identity-gate/README.md`](e2e/identity-gate/README.md) for the browser
+topology, safety boundary, failure artifacts and full-stack variant.
+
 ## Bundled JavaScript
 
 ```html
@@ -146,3 +158,23 @@ 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.
+
+## 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.