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

package/CHANGELOG.md

@@ -7,6 +7,79 @@ 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
@@ -3541,7 +3614,8 @@ 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.37.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