docs: document direct agent resource workflows - #38
Merged
Merged
Conversation
danielblignaut
marked this pull request as ready for review
September 7, 2026 21:06
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.
Document native permission-controlled resource operations following capability-proposal retirement. Add the managed connection guide for account reuse, user/bot ownership, secure setup and external-channel handoff, plus bounded session-history search documentation.
Validation: provider-page generation, publication-boundary, Mintlify build validation, broken-link and accessibility checks pass. All 71 MDX files pass the accessibility check.
Publish alongside the matching API and client release; existing proposal callers must migrate before retirement migrations run. No manual application deployment or package publication is included. Architecture decisions and complete engineering records remain in the owning API and Dispatch repositories.