Repository navigation
fix(cli): identify recovery API operations in HTTP failures - #8
Merged
Merged
Conversation
Keep provider diagnostics within the shared transport. Fixed method/path labels identify denied recovery operations without exposing URLs, query identifiers, headers, bodies or credentials. Preserve requests and recovery validation. Static Ruff, Python syntax and diff checks passed. Existing failed capture 38168366416 remains evidence; no denied endpoint or permission is inferred. No tests were added or manually run, and provider diagnosis remains pending. Co-authored-by: Codex <noreply@openai.com>
WillieCubed
marked this pull request as ready for review
October 11, 2026 19:41
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.
TL;DR
Add safe operation context to Worker recovery HTTP failures on the exact published v0.1.9 source baseline (
d59c5ed117013a59edd97f6e9e766896188a6a76). No release version is assigned here.Changes
unknownfallback.Request order, response guards, pagination, capture/restore validation and CAS checks are unchanged. Only
studio/websites.pyanddocs/rollout.mddiffer from v0.1.9; there is no S3 code or transport contract change.Static Ruff, Python syntax and diff checks passed. No tests were added or manually run; automatic CI provides the existing regression gates.
Follow-ups and Next Work
Review automatic CI before any separately authorized merge or publication. Real hosted operation diagnosis and successful artifact-bound recovery capture remain pending. No release, tag, product pin, permission change, provider request or capture retry is included in this PR.