Repair API Client Integration, Error & Retry Bugs

The likely issue is a contract mismatch around API client request construction, authentication, headers, serialization, response parsing, status/error mapping, pagination, rate limits, timeout budgets, retries, idempotency, SDK wrappers, and version compatibility. I would first define the invariant: Each API call has one documented request/response contract, one authority boundary, and retry semantics that never transform an unknown or partial outcome into a duplicate side effect. Then I would trace the smallest owning boundary, keep VERIFIED facts separate from LIKELY/UNKNOWN state, apply or propose the narrowest repair, and add deterministic normal, boundary, failure, retry/cancellation, and recovery tests. The workflow preserves authorization, privacy, security policy, public interfaces, user-visible behavior, and documented ownership. With repository/workspace access, findings can map to exact paths and focused local validation; with partial evidence, the result remains an explicit diagnosis/evidence map with no invented execution claims.