docs(common): clarify retries are handled by client layer, not RuntimeTransport #11572
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.
Updated doc comments in crates/common/src/provider/runtime_transport.rs to align with the architecture where retry/backoff (including CUPS) is implemented via RetryBackoffLayer at the provider/client layer. The previous wording implied retries occurred within RuntimeTransport, which was misleading. This corrects the documentation to match actual behavior and prevent incorrect API expectations.