Bug Description

The SDK crashes with SyntaxError: Unexpected end of JSON input when the server returns an empty response body without proper Content-Length: 0 header or 204 status code.

Steps to Reproduce

1. Make an API call that returns an empty body with status 200
2. SDK attempts to parse the empty body as JSON
3. Crashes at client.gen.ts:167

Error Message

SyntaxError: Unexpected end of JSON input
    at json (unknown)
    at <anonymous> (../sdk/js/src/v2/gen/client/client.gen.ts:167:33)

Expected Behavior

• Empty responses should be handled gracefully (return {})
• Malformed JSON should provide actionable error messages with status code and URL

Root Cause

1. Client-side: SDK only checks for status === 204 or Content-Length === "0" before attempting JSON parse. Empty body with 200 status and no Content-Length header falls through to response.json() which throws.

2. Server-side: OPTIONS handler in /packages/console/app/src/routes/zen/v1/models.ts returns status: 200 with null body instead of status: 204.

Proposed Fix

• Read response as text first, only parse if non-empty
• Add try-catch with contextual error messages for malformed JSON
• Fix server to return proper 204 status for empty responses

Related Issues

• Unexpected end of json #7715 - Same bug report (duplicate)
• fix(sdk): improve JSON parsing error handling with contextual messages #7618 - Similar fix attempt (error messages only, doesn't prevent the crash)

Not Related (different root causes)

• JSON parsing failed: Text #2188, task tool "SyntaxError: Unexpected end of JSON input" #3034, Incomplete JSON when writing out files #5890, [Bug] JSON Parse Error with Zhipu GLM-4.7: Stream chunks are concatenated incorrectly #7692 - These are about model-generated malformed JSON, not SDK response parsing