Document agent execution flow and source entry points - #25
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.
The project overview now gives agent execution its own design entry and links the buyer and merchant loops, shared dispatch, protocol adapter, and budget implementation. The runtime guide explains complete-response validation before tool dispatch, result ownership, conversation and memory versions, and both native build entry points.
The English and Chinese overviews remain aligned. Historical and final acceptance records retain their separate versions and counts.
Validation:
git diff --checkpassed.This change only edits Markdown. No application code, dependency, or measured result changed; no new local business tests or benchmarks were run.