Multi-step API flows need cleanup on all failure modes, not just non-2xx responses

When implementing multi-step API flows (e.g. upload then set permissions then insert), cleanup of earlier steps on later failure must cover three distinct failure modes: non-2xx HTTP responses (checked via resp.is_success), HTTP exceptions (timeouts, connection resets, raised as httpx.HTTPError), and mutation-level failures (e.g. GraphQL success: false without a top-level error). Initial implementations commonly only handle non-2xx responses, leaving orphaned artifacts on timeout or transport errors.

Structure multi-step flows so cleanup runs on all failure paths: non-2xx check, except HTTPError, and mutation success flag. Use best-effort cleanup (suppress cleanup errors) to avoid masking the original failure.