Preserve HTTP errors when response envelopes are unavailable - #36
Merged
Merged
Conversation
Member
Author
|
Reviewed final head
Success-response envelope checks and compatibility refusals remain strict. Valid error envelopes retain normalized diagnostic fields. Missing or broken envelopes preserve the HTTP failure instead of replacing it. Merge is ready. CLI 2.1.3 publication, required release evidence and the published storage-pressure repeat remain on #35. This does not close that issue or the parent diagnosis drill. |
rmcdaniel
marked this pull request as ready for review
September 30, 2026 10:47
This was referenced Sep 30, 2026
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.
Operator outcome
Preserve HTTP failures from Server and upstream proxies so operators receive the actual status and error details rather than an unrelated response-envelope error.
Addresses #35. The published storage-pressure repeat is required before closing the issue.
Validation
Consumers
This changes CLI diagnostics only. Server and SDK execution protocols, credentials and workflow semantics do not change. Package and native CLI distribution verification applies. Pinned application tuples retain their separately qualified CLI versions until adoption is justified.