Greptile Summary

Injects x-should-retry: false into the response headers when a 429 carries a retry-after value above 60 seconds, preventing the Anthropic SDK from sleeping for the full quota-refresh duration and letting OpenClaw's failover layer take over. The implementation is correct — parseFloat with an isNaN guard safely ignores HTTP-date format values, the response body stream is properly transferred before buildManagedResponse wraps it, and the header injection is a no-op for SDKs that don't inspect x-should-retry.

Confidence Score: 5/5

Safe to merge — only finding is a P2 model constant naming preference in the test fixture.

The core logic is correct: 429 detection, numeric parse with NaN guard, threshold comparison, header injection, and response body stream transfer all work as intended. Four new tests cover the meaningful branches. The single comment is a P2 style preference (test model constant claude-opus-4-7 vs sonnet-4.6) with no behavioral impact.

No files require special attention.

This is a comment left during a code review.
Path: src/agents/provider-transport-fetch.test.ts
Line: 99-103

Comment:
**Prefer `sonnet-4.6` for Anthropic test model constants**

Per the repo testing guidelines, new tests should use `sonnet-4.6` (not `claude-opus-4-7`) as the canonical Anthropic model fixture. The model ID has no effect on the 429 logic being tested, so the swap is mechanical.

```suggestion
    const anthropicModel = {
      id: "sonnet-4.6",
      provider: "anthropic",
      api: "anthropic-messages",
      baseUrl: "https://api.anthropic.com/v1",
    } as unknown as Model<"anthropic-messages">;
```

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "fix: skip SDK retry on 429 with retry-af..." | Re-trigger Greptile}

Landed via rebase as b09aed8.\n\nValidation:\n- Verified OpenAI/Anthropic Stainless SDK retry behavior: both honor x-should-retry: false before retrying 408/409/429/5xx and parsing retry-after-ms / retry-after.\n- Local: pnpm test src/agents/provider-transport-fetch.test.ts (10/10).\n- Local: pnpm check:changed (386 files, 4062 passed / 4 skipped).\n- CI: standard check/build/test/extension shards green on head 14e15506ef.\n- CI: qa-lab parity gate stayed red with the same mock agentic pack result seen before landing (4/11 pass, 7/11 fail); not blocking merge.\n\nThanks @jetd1!