feat: Default requests to a 30 second timeout

[razor-x]

Part of a four-SDK change adding a default HTTP timeout (ruby, python, csharp).

Problem

Requests had no timeout, so a hung connection blocked the caller indefinitely. Axios defaults timeout to 0, which means no timeout at all, and the SDK never set it.

Changes

• Set the Axios timeout to 30 seconds by default, matching the API's own request timeout.
• Add a timeout option, in milliseconds, so callers can raise, lower, or disable it.
• Precedence keeps the low-level escape hatch authoritative: axiosOptions.timeout still wins over the timeout option.

const seam = new SeamHttp({ apiKey: 'your-api-key', timeout: 60000 })

Set timeout to 0 to disable it. A request that times out rejects with an Axios ETIMEDOUT error and is retried according to the retry options.

Note that the code is ETIMEDOUT rather than the more familiar ECONNABORTED because this SDK pins adapter: 'fetch', and the fetch adapter raises timeouts through composeSignals. The XHR and http adapters would report ECONNABORTED.

Behavior change

Requests that previously ran longer than 30 seconds will now fail with ETIMEDOUT instead of hanging. The timeout option is the opt-out.

Testing

test/seam/connect/timeout.test.ts covers the default, the timeout option, axiosOptions precedence, and a request that actually aborts.

Note for reviewers

Retries multiply the timeout. With the default of 2 retries, a fully hung endpoint is now bounded at roughly 90 seconds rather than forever. Retry behavior is otherwise untouched here.

🤖 Generated with Claude Code

https://claude.ai/code/session_01XMgDauUA2R9u2THCHmMgv1