Repository navigation
fix(chat): require validated generative UI action execution - #1290
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
The public generative UI example could claim that a filter was applied without calling the data tool. Require a structured operation decision, validate the full tool batch before changing the dashboard, and derive action responses from the accepted results. Failed or malformed batches retain the prior dashboard and report that no changes were applied.
Extend the real graph and SDK fixtures, native continuation coverage, and Angular example coverage. Update the guide and Code views to show all four backend modules. Native confirmation and rollback rules remain intact.
CI also exposed broken declarations in a newly published floating LangSmith transitive dependency used by the standalone middleware consumer verifier. Derive its provider dependency graph from the existing root lock, preserve incompatible nested versions, and verify the installed graph before strict type and runtime checks. Package dependencies and repository locks are unchanged.
Validation passed: 38 graph tests, 21 SDK fixtures, 76 native unit tests, 15 React browser tests, 2 Angular browser tests, 92 registry tests, and 1,687 website tests. Five local website embedding journeys passed with no runtime requests. Relevant builds, lint, parity checks, and agent context generation passed. The verification repair passed 37 focused/shared vendor tests and fresh strict isolated consumer runs under Node 24 and Node 22/npm 10.
The first PR CI attempt passed the affected GenUI browser suites, website checks, and security analysis; its middleware declaration failure was reproduced and repaired. Fresh checks on the complete updated commit are required before merge.
Actual-main deployment checks and a fresh public three-turn conversation will be verified after merge; local fixture results do not establish public model behavior.