@filigran/chatbot 3.19.0 → 3.19.1

package/CHANGELOG.md

@@ -8,6 +8,32 @@ the versions follow [semantic versioning](https://semver.org/spec/v2.0.0.html).
 This file starts at 3.10.0; earlier releases are on the
 [releases page](https://github.com/FiligranHQ/filigran-ui/releases).
 
+## 3.19.1 — unreleased
+
+### Added
+
+- The panel speaks German, Italian, Korean, Russian and Simplified Chinese on
+  its own: a catalog for each, picked from `locale` by its language whatever
+  the region (`de-de`, `it-it`, `ko-kr`, `ru-ru`, `zh-cn`). Those languages
+  showed in English unless the host translated every key through `t`.
+  Traditional Chinese tags (`zh-TW`, `zh-HK`, `zh-Hant`) keep falling back.
+
+### Fixed
+
+- A refusal whose body has no `detail` shows its `error` when that is a
+  sentence, as the products' proxies answer (`{ "error": "..." }`, beside a
+  `status` or not), never a code (`invalid_token`, `Unauthorized`) nor a
+  status's reason phrase (`Not Found`, `Too Many Requests`). It shows above
+  the composer, in place of the answer, on a failed upload's chip, under the
+  conversation list and on a conversation that could not be loaded. The panel
+  showed its generic message instead.
+- The status line has its own wording when it has no agent's name (`The agent
+  is answering…`, `Consulting an agent…`, `Transferring to another agent…`),
+  where it filled the name with a lowercase `the agent`: `the agent is
+  answering…` started without a capital. A host translating through `t` in a
+  language the panel has no catalog for translates these three keys; it
+  translated `the agent` before, and shows them in English until it does.
+
 ## 3.19.0 — unreleased
 
 ### Added

package/README.md

@@ -520,8 +520,8 @@ conversation. If the endpoint responds with a non-2xx status, the component
 silently resets the stored id and starts fresh on the next message, except
 when it says nothing of the conversation: a `502`, `503` or `504` (or no
 answer at all) keeps the id and reads it back once the backend answers, and a
-`401` or `403` (expired credentials) keeps it, shows the response's `detail`
-(or "This conversation could not be loaded.") with a Retry button, and reads
+`401` or `403` (expired credentials) keeps it, shows the response's
+[reason](#a-refusals-reason) (or "This conversation could not be loaded.") with a Retry button, and reads
 it back as soon as `requestHeaders` change.
 
 Assistant history messages **should echo the same `attachments[]` array** that
@@ -583,7 +583,7 @@ the row reverts to its previous title.
 
 With [workspaces](#workspaces) on, the same route files a conversation:
 `{ "workspace_id": "uuid" }`, or `{ "workspace_id": null }` to take it out of
-its workspace. A refusal's `detail` is shown under the list.
+its workspace. A refusal's [reason](#a-refusals-reason) is shown under the list.
 
 ### Workspaces
 
@@ -659,6 +659,17 @@ Deletes a conversation from the history menu. Any 2xx response counts as
 success; deleting the active conversation resets the panel to a fresh chat so
 the next message never targets a dead conversation id.
 
+### A refusal's reason
+
+Where the panel shows why the backend refused a request, it reads the JSON body
+of the non-2xx answer: its `detail` when a string, or the `message` (or
+`detail`) of a `detail` object, as XTM One answers; else its `error` when that
+is a sentence, as the products' proxies answer (`{ "error": "..." }`, beside a
+`status` or not). A code (`invalid_token`, `Unauthorized`), a status's reason
+phrase (`Not Found`, `Too Many Requests`), anything else in the body (a
+top-level `message` included), a string over 500 characters or a body that is
+not JSON shows the panel's own, translated message.
+
 ### `POST {apiBaseUrl}/chat/messages`
 
 Sends a message and streams the response via SSE.
@@ -686,7 +697,7 @@ It must be JSON-serializable — a non-serializable value (circular reference,
 
 A refusal before the stream (a non-2xx answer: a rate limit, a refused
 option, an unknown conversation) shows the response's `detail` in place of the
-answer - a string, or the `message` (or `detail`) of an object - and
+answer ([its reason](#a-refusals-reason)), and
 "Unable to connect. Please check the configuration." when it has none; the
 handle's `send` resolves `'failed'`.
 
@@ -820,7 +831,7 @@ until the next send. On a non-2xx
 response or a network error nothing was stored: the optimistic user bubble is
 rolled back, the text is restored into the composer (prepended on its own line
 if the user already typed something new), the send resolves `'failed'` and the
-refusal's `detail`, when there is one, shows above the composer — so a backend
+refusal's [reason](#a-refusals-reason), when there is one, shows above the composer — so a backend
 without steering support degrades gracefully and the message is never silently
 lost. A `409` means no turn is running any more, an ordinary race: no notice
 shows, and with `holdSendsDuringTurn` the message is held and sent as the next
@@ -836,7 +847,7 @@ mentions or body fields of its own (`send`'s `extras`, `onBeforeSend`'s
 for the turn to end (`holdSendsDuringTurn`), and `onBeforeSend` is asked again,
 with `turnRunning: false`, before it goes out. A file that failed to upload
 neither steers nor waits, nor goes without that file: its chip says why (the
-upload's `detail`), and the composer offers no send, and says why, until the
+upload's [reason](#a-refusals-reason)), and the composer offers no send, and says why, until the
 user removes it. `send` and a voice
 call attach no files, so this never holds them. Esc stops generating.
 
@@ -1044,7 +1055,7 @@ chat) opts into six more routes, none with a default:
 
 | `apiEndpoints` key | Request | What it does |
 | --- | --- | --- |
-| `cancel` | `POST {cancel}` with `{ conversation_id }` | Stop asks the backend to end the turn; the panel keeps reading until the stream's `cancelled` frame (or lets go after 10 s, or at once on a network error or an answer of `{ "turn": "none" }`, reading the conversation back for an end it had not read yet). A Stop pressed before the panel's own send started its turn (its stream delivered nothing yet) carries `"awaiting_send": true`, and its `none` says nothing of that turn: the Stop stays pending and is sent again, without the flag, as the turn starts (or as the answer comes, the turn started meanwhile); any other answer reached a turn, and nothing goes again. A backend may keep a Stop with that flag for the send's turn, and must then take a second cancel of one turn; a Stop without it says nothing of a later send. A refusal (non-2xx) keeps the turn running and shows its `detail` above the composer |
+| `cancel` | `POST {cancel}` with `{ conversation_id }` | Stop asks the backend to end the turn; the panel keeps reading until the stream's `cancelled` frame (or lets go after 10 s, or at once on a network error or an answer of `{ "turn": "none" }`, reading the conversation back for an end it had not read yet). A Stop pressed before the panel's own send started its turn (its stream delivered nothing yet) carries `"awaiting_send": true`, and its `none` says nothing of that turn: the Stop stays pending and is sent again, without the flag, as the turn starts (or as the answer comes, the turn started meanwhile); any other answer reached a turn, and nothing goes again. A backend may keep a Stop with that flag for the send's turn, and must then take a second cancel of one turn; a Stop without it says nothing of a later send. A refusal (non-2xx) keeps the turn running and shows its [reason](#a-refusals-reason) above the composer |
 | `skipWait` | `POST {skipWait}` with `{ conversation_id }` | `Continue now` on `status: wait_start` (`{ seconds, reason }`), for as long as the pause lasts (see the status values) |
 | `events` | `GET {events}/{conversation_id}/events?client_id=<id>` → SSE | Turns this panel did not start (another tab, a reload mid-turn), `user_message`, `conversation_title`, `approval_resolved`; every frame of a turn names it (`turn_id`, below) |
 | `messagesPage` | `GET {messagesPage}/{conversation_id}/messages?before=<message id>&limit=50&supports_artifacts=true` → `{ messages, has_more }` | "Load earlier messages" past the restored ones, offered when the restore answers `has_more: true` |
@@ -1290,9 +1301,12 @@ both. The same variables may be set in CSS on an ancestor instead.
 
 ### Internationalization
 
-The panel speaks English, French, Spanish and Japanese on its own: it ships a
-catalog for each and picks one from `locale` (`fr-FR` reads French; English, or
-a language it lacks, is its own keys). A host in another language translates
+The panel speaks English, French, German, Italian, Spanish, Japanese, Korean,
+Russian and Simplified Chinese on its own: it ships a catalog for each and
+picks one from `locale` by its language, whatever the region (`fr-FR` reads
+French, `zh-cn` Chinese; English, or a language it lacks, is its own keys).
+Traditional Chinese (`zh-TW`, `zh-HK`, `zh-Hant`) has no catalog: it reads
+English unless the host translates it through `t`. A host in another language translates
 through `t`. A host with nothing to add only passes `locale`:
 
 ```tsx

package/dist/index.d.ts

@@ -570,7 +570,7 @@ interface ChatPanelProps {
     onMessageFeedback?: (messageId: string, feedback: MessageFeedback | null, message: ChatMessage) => void;
     /**
      * The user's language as a BCP 47 tag (`'fr'`, `'en-US'`): the language the
-     * panel speaks (its own catalog: en, es, fr, ja) where `t` does not
+     * panel speaks (its own catalog: en, de, es, fr, it, ja, ko, ru, zh-Hans) where `t` does not
      * translate a key, formats the time under each message and is the language
      * answers are read aloud in. Default: the browser's own, except that a host
      * passing `t` and no `locale` gets no catalog.
@@ -1264,7 +1264,7 @@ interface ChatFile {
     fileId?: string;
     /** Upload status: 'pending' while uploading, 'done' when uploaded, 'error' on failure. */
     uploadStatus?: 'pending' | 'done' | 'error';
-    /** Why the upload failed, as the backend said (`detail`), when it said. */
+    /** Why the upload failed, as the backend said, when it said: its reason (README, "A refusal's reason"). */
     uploadError?: string;
 }
 /** The conversation list's search, as a host's sections read it (`sidebarSections`). */