fix(chat): render replaced content during gradual stage playback - #1077
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
blove
enabled auto-merge (squash)
September 9, 2026 01:13
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
1 participant
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.
Gradual homepage playback showed raw A2UI JSON in the final beat: the render tool replaces an introductory assistant message with a longer payload under the same ID, while the content classifier only reset for shorter replacements. Detect non-append replacements so the message is classified and parsed again.
Adds regressions for longer A2UI and equal-length JSON replacements, plus a homepage browser test that advances through the render beat in small steps and edits the resulting form.
Validation: both new unit regressions failed before the fix; 51 classifier tests, 59 chat component tests, and all 10 homepage browser tests pass afterward. Website production build passes. Reproduced the original failure with Chrome DevTools MCP on production; production re-verification follows deployment.