Skip to content

fix(cli): identify recovery API operations in HTTP failures - #8

Merged
WillieCubed merged 1 commit into
mainfrom
codex/recovery-api-operation-labels
Oct 11, 2026
Merged

WillieCubed merged 1 commit into
mainfrom
codex/recovery-api-operation-labels

Conversation

@WillieCubed

Copy link
Copy Markdown
Contributor

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

  • Match existing request methods and path templates to nine fixed labels: six capture reads and three restore writes, plus an unknown fallback.
  • Include only the fixed operation label and HTTP status in HTTP failure messages. Raw methods, paths, queries, identifiers, headers, bodies and binding values remain absent from diagnostics.
  • Record capture 38168366416's HTTP 403 as unresolved evidence. Its denied endpoint and any required permission remain unknown.

Request order, response guards, pagination, capture/restore validation and CAS checks are unchanged. Only studio/websites.py and docs/rollout.md differ 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.

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
WillieCubed marked this pull request as ready for review October 11, 2026 19:41
@WillieCubed
WillieCubed merged commit a13ccab into main Oct 11, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant