@artooi/ag-ui-web-component 0.41.1 → 0.41.3

package/CHANGELOG.md

@@ -7,6 +7,60 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.41.3] — 2026-10-07
+
+### Fixed
+
+- **A resumed or forked run shows the turn it was sent with.** Picking Resume
+  or Fork in the checkpoint panel sent what the composer held and streamed the
+  answer, but drew no bubble for the turn, so the answer arrived under no
+  question. The save already held the turn, so a reload showed a question the
+  live transcript never had. The continuation now draws the turn the way Send
+  does, ahead of its answer, and tests hold that the live transcript and the
+  restored one agree after both a resume and a fork.
+- **`ag-ui-submit` fires for a continued turn.** A host listens to it as "the
+  user sent something", and a turn sent with Resume or Fork is one: only the
+  endpoint differs. The event fires once the continuation is the run in flight,
+  so a `sendMessage()` from a listener is refused rather than starting a second
+  run beside it, and a listener that stops it -- a new chat, a thread switch,
+  moving the element -- stops it before its request is made. Its
+  `detail.attachments` is empty, because a continuation sends only the
+  composer's text.
+
+### Changed
+
+- **Ships DOMPurify 3.4.16 and marked 18.0.14**, from the lockfile refresh
+  since 0.41.2. Both builds carry them inlined, the npm build as well as the
+  vendored bundle: only `@ag-ui/client` and `@ag-ui/core` are left to the
+  host's resolver, so a host's own lockfile does not choose which sanitiser
+  runs.
+
+## [0.41.2] — 2026-09-23
+
+### Changed
+
+- **The demo answers a denied approval with a result, as a real server does.**
+  The mock streamed a result only for the calls a person approved, and said so
+  in a comment: a denial was left for the model to answer. django-ag-ui streams
+  one for every answered call, and a denied one carries pydantic-ai's denial
+  message with `outcome: "denied"` on both carriers. With no result, the next
+  request answered the call as not finished, so the playground's own
+  multi-approval scenario came back from a reload with every declined card
+  reading "not finished". The mock also denies by default now, as pydantic-ai
+  does, so only an answer whose payload says `approved: true` runs the call.
+
+### Fixed
+
+- **A navigating tool's card reads done on the page it navigated to.** A tool
+  marked `x-navigates` reloads the page, and the next mount answers its call
+  with the landed page's result and continues the run. That result reached the
+  agent, but the call's card was never settled from it: it spun for the whole
+  continuation, and when the run finished, the sweep that closes any card still
+  open marked it "not finished" -- on the one call known to have finished. The
+  resume now settles the card from the result it sends, so it reads done with
+  that result while the continuation runs, and matches what a later reload
+  shows from the stored message.
+
 ## [0.41.1] — 2026-09-22
 
 ### Changed
@@ -4196,7 +4250,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.41.1...HEAD
+[Unreleased]: https://github.com/Artui/ag-ui-web-component/compare/v0.41.3...HEAD
+[0.41.3]: https://github.com/Artui/ag-ui-web-component/compare/v0.41.2...v0.41.3
+[0.41.2]: https://github.com/Artui/ag-ui-web-component/compare/v0.41.1...v0.41.2
 [0.41.1]: https://github.com/Artui/ag-ui-web-component/compare/v0.41.0...v0.41.1
 [0.41.0]: https://github.com/Artui/ag-ui-web-component/compare/v0.40.0...v0.41.0
 [0.40.0]: https://github.com/Artui/ag-ui-web-component/compare/v0.39.0...v0.40.0

package/README.md

@@ -2409,7 +2409,10 @@ Type the next turn in the composer, then pick a row:
 - **Resume** — continue that run.
 - **Fork** — branch it, leaving the original untouched.
 
-Both send to the matching server endpoint and stream into the same transcript.
+Both send to the matching server endpoint and stream into the same transcript. The
+turn you typed is drawn there ahead of the answer and announced with `ag-ui-submit`,
+exactly as a send is, so a host that keeps its own record of what the user said sees
+continued turns too.
 
 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**