Capture more of OpenRouter's provider specific error details

[jr]

Follow-up to #10039

---

Important

Enhances OpenRouter error handling by parsing detailed error information using Zod schema and a helper function in openrouter.ts.

• Error Handling:
  • Introduces OpenRouterErrorResponseSchema using Zod in openrouter.ts to parse OpenRouter error responses.
  • Adds extractErrorFromMetadataRaw() to parse error messages from metadata.raw.
  • Updates handleStreamingError() and error handling in createMessage() and completePrompt() to use parsed error details.
• Interfaces:
  • Defines OpenRouterErrorResponse and OpenRouterError interfaces for structured error handling.

^{This description was created by for b355d57. You can customize this summary. It will automatically update as commits are pushed.}

[roomote]

Rooviewer   See task on Roo Cloud

Re-reviewed the enhanced OpenRouter error handling. The property path issue has been addressed in commit b355d57.

• Verify property path for metadata.raw - now correctly uses error?.metadata?.raw for streaming and openRouterError.error?.metadata?.raw for caught exceptions

Previous reviews

• a5f65a6: Review #1

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}

[ellipsis-dev]

This error handling logic is nearly identical to the one in completePrompt. Consider extracting it into a shared helper function to reduce duplication.

^{This comment was generated because it violated a code review rule: irule_tTqpIuNs8DV0QFGj.}

[mrubens]

This logic seems a little overly defensive - is it possible for the raw error to not be present if hasMetadataRaw is truthy?

[roomote]

The property path errorObj?.metadata?.raw differs from how handleOpenAIError accesses the same property ((error as any)?.error?.metadata?.raw). Based on the OpenAISdkError interface in telemetry.ts, SDK exceptions typically have metadata nested under error.error. If that's the case for OpenRouter SDK errors, this check would always be falsy and the enhanced error handling would never execute. Worth verifying the actual error structure from OpenRouter - you may need errorObj?.error?.metadata?.raw instead.

_{Fix it with Roo Code or mention @roomote and request a fix.}