[codex] Expose sync timeout as queryable error

[chengzeyi]

What changed

• Added WavespeedSyncTimeoutException and exported it from package entrypoints.
• Treat server-side sync timeout as non-retryable to avoid duplicate submissions when maxRetries is set.
• Preserve successful run() return shape.
• Return structured processing detail from runNoThrow() with taskId and resultUrl.
• Updated README/docs and added regression tests for run() and runNoThrow().

Why

A sync timeout means the task is still processing asynchronously. SDK callers need to distinguish that from a failed prediction and must be able to query the task later.

User impact

run(..., { enableSyncMode: true }) raises WavespeedSyncTimeoutException on sync timeout. Callers using runNoThrow() can inspect detail.status === "processing", detail.taskId, and detail.resultUrl.

Validation

• npm test -- --runInBand
• npm run build
• git diff --check

[claude]

Claude encountered an error —— View job

---

I'll analyze this and get back to you.

[claude]

Claude encountered an error —— View job

---

I'll analyze this and get back to you.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a1ed49e7a5

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Require processing status for sync timeout classification

For a sync-mode response such as { status: 'failed', code: 5004 }, this classifies WaveSpeed's generic timeout error code as a still-running sync timeout before checking the task status. That makes run() throw a non-retryable WavespeedSyncTimeoutException and makes runNoThrow() report detail.status === 'processing' even though the task is terminally failed; require status === 'processing' or the sync-timeout message when treating 5004 as queryable.

Useful? React with 👍 / 👎.