Repository navigation
docs: clarify agent integration boundaries - #217
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Summary
Clarifies the async boundary, application-owned transcript pattern, continuation/media replay contract, configuration ownership, and strict tool-argument behavior for agent-framework integrations. Adds a boundary test for the documented supported OpenAI transcript round trip.
Related issue
None
Test plan
uv run pytest tests/providers/test_errors.py tests/interaction/test_continuation.py -v— 28 passed.uv run rumdl check docs/agent-loop.md docs/configuration.md docs/conversations-and-agents.md— passed.uv run mkdocs build --strict— passed.just check— Ruff, rumdl, mypy, and 450 non-API tests passed.Notes
The docs keep media transport explicit: OpenAI-style text/tool transcripts can be imported, while PDFs, images, audio, video, and provider-native media remain application records reconstructed as Pollux
Sourcevalues. Display reasoning is documented as output data rather than replay history.just checkpasses