Repository navigation
fix(ai): preserve host rendering and metadata in grouped tools - #248
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Enabling transcript tool grouping bypassed the host renderer, row metadata and styling. Route group children through the same host-aware body selection as ordinary items, retaining the built-in fallback. Group children use non-interactive keyed columns; item data attributes update without remounting their bodies.
Four mounted regressions fail before the fix and pass afterward, covering custom/default rendering, streamed content and metadata, keyed child retention, disclosure and disposal. The complete 147-case native test_lui target and Melange @web build pass; changed functions pass the 64-line AST check. No Dune changes, warning suppression, unsafe casts or vendoring. Actual Mapre browser acceptance follows installed-package review.
The new decision validates individually. The full document check reports two pre-existing legacy document paths; those unrelated files are unchanged.