Repository navigation
feat(examples): add native React Deep Agents Planning preview - #1294
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.
Adds a native React example to the existing Deep Agents Planning guide. The chat shows validated live todos and labels a plan saved only after successful native submission, correlated
write_todosevidence, and an exact owned terminal checkpoint. Failed, stopped, malformed, and uncertain updates retain the last confirmed plan; a new conversation clears it. Finishing a response leaves unfinished todo statuses intact.The React Docs/Code/Run preview uses the unchanged
da-planninggraph and shared deployment. Angular stays the default. The registry, source assets, frontend assembly, and website fixtures include the new example.Validation: 112 native tests; 4 compiled Python graph tests; 12 SDK/fixture tests; 9 native browser tests; 1690 website tests; 94 registry tests; 27 frontend matrix tests; 7 wiring tests; 6 inert website embedding browser tests. Native lint, native and website production builds, source and built boundaries, parity inventory, and assembly of 70 frontends passed. An isolated installed React consumer passed 27 browser scenarios. Independent specification and quality reviews approved the exact candidate.
The offline fixture executes the real compiled graph and buffers its output; its cancellation tests establish local delivery/ownership isolation, not production rollback. Full frontend coverage runs in isolated CI because unrelated local servers occupy three fleet ports. Actual-main deployment and a fresh bounded public Planning proof follow a green merge.