Repository navigation
docs: explain when agents should use batch or ordered processing - #267
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
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.
Recommend default batch processing for independent parallel agent work. Explain when ordered processing is useful through web-feature and compiler-optimization examples, including failure handling, retry position, and continued agent development.
Keep configuration and recovery guidance consistent, link the reviewed external integration example, and mark ordered processing as unreleased. This change updates documentation; package version remains 3.5.1.
Validation: native pre-push gates passed with 869 tests, 7 skips, 92.66% coverage, and all critical coverage floors. All 15 PR CI jobs passed: https://github.com/yongjip/mergetrain/actions/runs/38669052361. Also checked 23 relative document links and heading anchors, agent protocol, discovery metadata, release metadata, and whitespace.