@wildix/wilma-agents-client 1.0.40 → 1.0.41

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -223,10 +223,11 @@ export interface VoiceInterruptionSettings {
223
223
  /**
224
224
  * One phrase in one language, for a capability that speaks a fixed line on the voice channel.
225
225
  * Which entry is spoken is decided by the call's current language — the one the call resolved
226
- * to at connect, or the one automatic detection switched to — matched on `language`.
227
- * Blank `text` means the agent says nothing in that language; it does NOT fall back to the
228
- * language-agnostic member beside the list, which would speak one language's text in another
229
- * language's voice.
226
+ * to at connect, or the one automatic detection switched to — matched on `language`
227
+ * CASE-INSENSITIVELY, the same rule `VoiceBotSpokenPhrase` states for the legacy stack, so a
228
+ * code written in either case reaches the same entry on either. Blank `text` means the agent
229
+ * says nothing in that language; it does NOT fall back to the language-agnostic member beside
230
+ * the list, which would speak one language's text in another language's voice.
230
231
  * @public
231
232
  */
232
233
  export interface AgentSpokenPhrase {
@@ -845,7 +846,7 @@ export interface AgentConnectorCapability {
845
846
  */
846
847
  startMessage?: string | undefined;
847
848
  /**
848
- * Mirrors `AgentTool.startMessages`. Stored for contract symmetry; the voice runtime does not read connector start messages yet (wilma-services docs/todo.md item 8).
849
+ * Forward-compatible per-language connector start messages, mirroring `AgentTool.startMessages`. Accepted and stored so clients can configure connector and tool phrases consistently, but currently ignored at execution time because the voice runtime does not read connector start messages yet. Runtime enablement is tracked in wilma-services docs/todo.md item 8.
849
850
  * @public
850
851
  */
851
852
  startMessages?: AgentSpokenPhrase[] | undefined;
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@wildix/wilma-agents-client",
3
3
  "description": "@wildix/wilma-agents-client client",
4
- "version": "1.0.40",
4
+ "version": "1.0.41",
5
5
  "scripts": {
6
6
  "build": "concurrently 'yarn:build:cjs' 'yarn:build:es' 'yarn:build:types'",
7
7
  "build:cjs": "tsc -p tsconfig.cjs.json",