@artooi/ag-ui-web-component 0.36.0 → 0.38.0

package/CHANGELOG.md

@@ -7,6 +7,143 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.38.0] — 2026-09-14
+
+### Changed
+
+- **`src/ui/` is grouped by concern instead of being 37 modules in one flat
+  directory.** A flat directory that size is a table of contents nobody reads: the
+  placement arithmetic, the inline cards, the chart renderer and the clipboard
+  payload builder were neighbours only in the sense that all of them draw
+  something. They are now eight directories -- `placement/`, `transcript/`,
+  `progress/`, `excerpts/`, `charts/`, `interrupts/`, `history/` and `composer/`
+  -- with `styles.ts` and `ui_strings.ts` left at the group root because every one
+  of the eight reads them.
+
+  The split is by the question a module answers, never by the kind of export it
+  has. `interrupts/` holds the approval, confirmation and question cards because
+  all three pause a run to ask the user something; `tool_call_card.ts` is also a
+  card and sits in `progress/` instead, because it reports work rather than asking
+  for a decision. A `cards/` directory would have held all four and said nothing
+  about any of them. `CLAUDE.md` now states the rule, since the eight structural
+  rules it had all governed a file and none governed a directory.
+
+  Moves only. No module's contents changed, and the published surface is
+  unchanged: the same 92 runtime exports, the same 173 declared names, and every
+  emitted declaration line identical to the release before it.
+
+- **The element's event detail shapes are their own modules.** `ag_ui_chat.ts`
+  declared thirteen exported types alongside the `AgUiChat` class, so a consumer
+  looking up `RunFinishedDetail` opened a file of several thousand lines to read
+  twenty. The nine `detail` shapes and the `ToolRun` one of them lists are now in
+  `src/core/events/`, and `MessageRole`, `ActivityRenderer` and
+  `ActivityRegistration` at the `src/core/` root -- one symbol per file, like
+  everything else in the package.
+
+  The file shrank by only about a hundred lines, which is not the point: the point
+  is that each of these thirteen now has an import path a reader can go to, and
+  the element's contract with its host is no longer interleaved with the
+  implementation of it. Consumers importing from the package entry point see no
+  difference; the names and the shapes are the same.
+
+### Fixed
+
+- **A text message carrying no content no longer draws an empty bubble.**
+  `TOOL_CALL_START` names the assistant message a call belongs to, and a
+  response whose first part is a tool call has no text to open that message
+  with. pydantic-ai 2.37 began opening and closing an empty message there so
+  that `parentMessageId` names one the stream actually announced -- before that
+  it named a message no event carried, which a client could only answer by
+  inventing an id matching nothing echoed back. The envelope is a correctness
+  fix on the server side, it is legal AG-UI, and any server may send one.
+
+  Drawing it put an empty bubble above **every** tool call. Measured in
+  Chromium it was 16px tall and laid out between the question and the card, so
+  it read as a gap rather than as nothing.
+
+  The sharper half is that `#renderHistoricMessage` has always declined to draw
+  a bubble for an assistant message with no text, so the transcript during a run
+  disagreed with the same conversation after a reload. This is the live path
+  adopting a rule the restore path already stated, and the test asserts the two
+  against each other rather than against separate literals, so they cannot drift
+  apart again.
+
+  The guard tests the buffer for emptiness rather than blankness on purpose:
+  whitespace is content a server chose to send, and trimming would make the
+  client the judge of what counts as an answer.
+
+- **`StateDetail` was documented as if it were `FeedbackDetail`.** The two
+  interfaces sat next to each other and `StateDetail`'s doc comment had drifted
+  above `FeedbackDetail`'s own, so `FeedbackDetail` carried two comments,
+  `StateDetail` carried none, and an editor offered the wrong one for both. It
+  survived because a stray comment is invisible in a file long enough to hold both
+  declarations screens apart from their reader; putting one symbol in one file is
+  what made it obvious. Nothing about either type changed.
+
+## [0.37.0] — 2026-09-06
+
+### Fixed
+
+- **The README attribute gate only checked one direction, so it could not see its
+  own weakening.** It asked whether every attribute the element *reads* is
+  documented; an attribute falling out of the scanned set shrinks the set being
+  filtered, so the answer stays empty and nothing goes red. Adding a
+  variable-named read and raising the declared count -- without teaching the
+  matcher the new helper -- dropped two attributes out of the scan and the whole
+  suite still passed. Verified by doing exactly that: 1651 tests green.
+
+  There is now a reverse check. It refuses a documented row that nothing
+  consumes, and "consumes" had to be defined carefully: four documented
+  attributes (`density`, `data-side`, `data-small-viewport`, `data-answer-well`)
+  are host-set and read by the stylesheet alone through `:host([...])`, never by
+  any `getAttribute` call. A first version that looked only at JavaScript called
+  all four stale, which would have deleted four working rows.
+
+- **A message sent with no `endpoint` disappeared without a word.** The send path
+  returned early when the attribute was unset, and by then the two visible halves
+  of a successful send had already happened: the user's bubble was in the
+  transcript and `ag-ui-submit` had been dispatched. So the composer cleared, the
+  message appeared to go, Send never became Stop, no request was made, and
+  nothing at all reached the console. What that looks like is an agent ignoring
+  you, and what it gets reported as is a server that never answers.
+
+  The refusal stays -- there is nowhere to send to, and an agent built on an
+  empty endpoint would post to the current page -- but both audiences are now
+  told, because they need different things. A `console.error` names the missing
+  attribute and what to set it to, since a missing attribute is the page's
+  mistake and the page's author is not reading the transcript. A `not-connected`
+  run notice tells the reader their message went nowhere, because the honest
+  alternative to one muted line is an indefinite wait in front of their own
+  question. Both fire on every attempt rather than once: a one-shot report is the
+  same silence again for the second try, which is the try a puzzled user makes.
+
+- **Picking a run to continue with an empty composer closed the panel over
+  nothing.** A continuation sends only the new turn -- the server supplies
+  everything before it from the snapshot -- so with nothing typed there was
+  nothing to send, and the handler returned. The row's button had already
+  dismissed the panel by then, so the widget visibly reacted and then did
+  nothing, which reads as a resume that was attempted and lost rather than one
+  that never started. It now says what the composer still needs, above the input
+  and cleared by the next keystroke, and puts the caret there.
+
+- **A `data-strings` or `data-skills` value that would not parse was discarded
+  without a word.** Quoting JSON inside an HTML attribute is fiddly, and the
+  result of getting it wrong was indistinguishable from never having set the
+  attribute: the strings stayed English, or the palette came up empty, with
+  nothing anywhere naming the attribute. Both now warn on the console, naming
+  which one and what to check -- the answer `data-paste-attach` already gave for
+  a value it could not read. Console only: a page author's typo is not the
+  reader's business, nothing the reader did was refused, and the widget is still
+  perfectly usable without the override.
+
+### Changed
+
+- The composer hint above the input is no longer only a skills affordance: it
+  also carries the message above. Its `skill-hint` `part` is unchanged, since
+  renaming a part is breaking and a second hint in the same slot would be worse
+  than one whose name is older than its job. Two new `UiStrings` keys,
+  `notConnected` and `continueNeedsTurn`, are overridable like every other.
+
 ## [0.36.0] — 2026-09-05
 
 ### Added
@@ -3477,7 +3614,9 @@ hosts that both arrange the page the way it expects.
 ### Notes
 - First release — exercising the automated npm OIDC publish pipeline end-to-end.
 
-[Unreleased]: https://github.com/Artui/ag-ui-web-component/compare/v0.36.0...HEAD
+[Unreleased]: https://github.com/Artui/ag-ui-web-component/compare/v0.38.0...HEAD
+[0.38.0]: https://github.com/Artui/ag-ui-web-component/compare/v0.37.0...v0.38.0
+[0.37.0]: https://github.com/Artui/ag-ui-web-component/compare/v0.36.0...v0.37.0
 [0.36.0]: https://github.com/Artui/ag-ui-web-component/compare/v0.35.2...v0.36.0
 [0.35.2]: https://github.com/Artui/ag-ui-web-component/compare/v0.35.1...v0.35.2
 [0.35.1]: https://github.com/Artui/ag-ui-web-component/compare/v0.35.0...v0.35.1

package/README.md

@@ -173,14 +173,14 @@ another origin, add `credentials="include"` too; see
 
 | Attribute | Property | Notes |
 | --- | --- | --- |
-| `endpoint` | `endpoint` | The AG-UI endpoint URL. Required to send. Reflecting getter + setter. |
+| `endpoint` | `endpoint` | The AG-UI endpoint URL. Required to send: without it a send is refused with a `console.error` naming the missing attribute and a `not-connected` run notice in the transcript. Reflecting getter + setter. |
 | `credentials` | `credentials` | Cookie policy for every request the element makes: `omit` / `same-origin` / `include`. Unset means the browser default (`same-origin`), which sends no cookies cross-origin. See [Authenticating requests](#authenticating-requests). |
 | `title-text` | — | Header label; defaults to `"Assistant"`. Live: writing it after the element connects re-labels the header. See [When each attribute is read](#when-each-attribute-is-read). |
 | `data-tool-display` | `toolDisplay` | Tool-call card detail: `inline` / `minimal` / `compact` / `full` (default `full`). |
 | `data-text-animation` | — | Incoming-text reveal: `none` (default) / `fade` / `word`. |
 | `data-prompt-chips` | — | Present (bare, or any value but `"false"`) to surface skills as chips. |
 | `data-slash-commands` | — | Present (bare, or any value but `"false"`) to enable the `/`-command palette. |
-| `data-skills` | — | Inline JSON skill catalog. |
+| `data-skills` | — | Inline JSON skill catalog. A value that will not parse is ignored and reported on the console, rather than reading as an empty catalog. |
 | `data-skills-url` | — | URL of a JSON skill catalog (fetched with the element's headers and cookie policy). |
 | `data-tools-url` | — | URL of a server tool-label catalog (`[{ name, summary, description? }]`), fetched with the element's headers and cookie policy; labels tool-call cards for server-side tools. |
 | `user-key` | `userKey` | Who the stored conversation belongs to — any string identifying the signed-in principal. Joins the storage namespace, and **changing it purges what the previous principal left behind**. Live (not connect-time): a logout is the host's to announce. See [Who the stored conversation belongs to](#who-the-stored-conversation-belongs-to-user-key). |
@@ -192,7 +192,7 @@ another origin, add `credentials="include"` too; see
 | `data-attachment-max-bytes` | — | Client-side upload size cap in bytes (default 10 MiB; `0` disables). The server stays authoritative. |
 | `data-transcribe-url` | — | URL of the voice-transcription endpoint (django-ag-ui's `TranscribeView`); reveals the composer's mic button. See [Voice input](#voice-input). |
 | `data-theme-toggle` | — | Boolean: show a built-in header light⇄dark toggle (persists per tab). Off by default. See [Theme toggle](#theme-toggle). |
-| `data-strings` | `strings` | Partial JSON override of the UI string table (localization). The property wins key-by-key over the attribute; see [Internationalization](#internationalization-i18n). |
+| `data-strings` | `strings` | Partial JSON override of the UI string table (localization). The property wins key-by-key over the attribute; a value that will not parse is ignored and reported on the console. See [Internationalization](#internationalization-i18n). |
 | `data-icon-url` | — | Header (and launcher) icon image URL. A slotted `slot="icon"` wins; see [Header & launcher icon](#header-and-launcher-icon). |
 | `data-launcher-icon-url` | — | Icon image URL for the collapsed launcher only, when it should differ from the header's. Falls back to `data-icon-url`; a slotted `slot="launcher"` wins over both. |
 | `data-unread-badge` | — | **On by default.** `="false"` hides the launcher's unread badge; the count and the `ag-ui-unread` event keep running. See [Collapsing to the launcher](#collapsing-to-the-launcher). |
@@ -2312,6 +2312,10 @@ Type the next turn in the composer, then pick a row:
 
 Both send to the matching server endpoint and stream into the same transcript.
 
+Picking a row with an empty composer says so above the input and puts the caret
+there, rather than closing the panel over nothing: a continuation sends **only**
+the new turn, so with nothing typed there is nothing to send.
+
 ### One URL, three endpoints
 
 `data-runs-url` is the only thing to configure. `resume/<id>/` and `fork/<id>/`
@@ -2873,7 +2877,7 @@ component sets, so a new one cannot ship undocumented.
 | Follow-up suggestions | `suggestions`, `suggestion-chip` |
 | Message actions | `message-actions`, `message-action` (plus `message-action-retry`, `message-action-copy`, `message-action-up`, `message-action-down`), and the icon holder inside each: `message-action-icon` (plus `message-action-icon-retry`, `message-action-icon-copy`, `message-action-icon-up`, `message-action-icon-down`) |
 | Queued messages | `queued`, `queued-chip` |
-| Run notices | `run-notice` (plus `run-notice-interrupted`, `run-notice-attachment-pending`, `run-notice-compaction`, `run-notice-skill`, `run-notice-history-replaced`, `run-notice-chart-undrawable`, `run-notice-surface`), `run-notice-icon`, `run-notice-text`, `run-notice-undo` |
+| Run notices | `run-notice` (plus `run-notice-interrupted`, `run-notice-attachment-pending`, `run-notice-compaction`, `run-notice-skill`, `run-notice-history-replaced`, `run-notice-chart-undrawable`, `run-notice-surface`, `run-notice-not-connected`), `run-notice-icon`, `run-notice-text`, `run-notice-undo` |
 | Tool cards | `tool-card`, `tool-card-head`, `tool-card-icon`, `tool-card-name`, `tool-card-status`, `tool-card-decision`, `tool-card-toggle`, `tool-card-body`, `tool-card-section` (plus `tool-card-args-section`, `tool-card-result-section`), `tool-card-section-label` (plus `tool-card-args-label`, `tool-card-result-label`), `tool-card-args`, `tool-card-result`, `tool-card-approval`, `tool-card-subagent` |
 | Delegated sub-agents | `subagent`, `subagent-row`, `subagent-icon`, `subagent-status`, `subagent-steps`, `subagent-step`, `subagent-step-icon`, `subagent-step-name` |
 | Client-side confirmation | `confirm`, `confirm-body`, `confirm-args`, `confirm-actions`, `confirm-button` (plus `confirm-confirm`, `confirm-cancel`, `confirm-always`) |
@@ -2881,7 +2885,7 @@ component sets, so a new one cannot ship undocumented.
 | Typed question | `question`, `question-body`, `question-options`, `question-choice`, `question-choice-text`, `question-radio`, `question-input`, `question-actions`, `question-button` |
 | Composer | `composer`, `composer-surface`, `composer-tools`, `input`, `send`, `attach-button`, `voice-button` |
 | Attachments | `attachment-tray`, `attachment-chips` (the read-only chips on sent bubbles), and the shared chip parts `attachment-chip`, `attachment-chip-icon`, `attachment-chip-name`, `attachment-chip-size`, `attachment-chip-bar`, `attachment-chip-bar-fill`, `attachment-chip-retry`, `attachment-chip-remove` |
-| Skills | `skill-chips`, `skill-chip`, `skill-palette`, `skill-item`, `skill-item-title`, `skill-item-desc`, `skill-item-token`, `skill-hint` (the missing-placeholder hint) |
+| Skills | `skill-chips`, `skill-chip`, `skill-palette`, `skill-item`, `skill-item-title`, `skill-item-desc`, `skill-item-token`, `skill-hint` (the composer hint: a skill’s missing placeholders, and a run continuation with nothing typed) |
 | Thread drawer | `drawer`, `drawer-backdrop`, `drawer-panel`, `drawer-header`, `drawer-title`, `drawer-new`, `drawer-close`, `drawer-filter`, `drawer-list`, `drawer-empty`, `drawer-row`, `drawer-row-select`, `drawer-row-title`, `drawer-row-time`, `drawer-row-preview`, `drawer-row-actions`, `drawer-row-rename`, `drawer-row-delete`, `drawer-rename-input`, `drawer-confirm`, `drawer-confirm-label`, `drawer-confirm-yes`, `drawer-confirm-no` |
 | Charts | `chart-block`, `chart-title`, `chart-legend` |
 | Checkpoints panel | `checkpoints`, `checkpoints-header`, `checkpoints-title`, `checkpoints-list`, `checkpoints-empty`, `checkpoint-row`, `checkpoint-label`, `checkpoint-time`, `checkpoint-id`, `checkpoint-branch`, `checkpoint-action` (plus `checkpoint-resume`, `checkpoint-fork`) |