@chatsystem/client 1.3.3 → 2.0.0

package/README.md

@@ -158,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.