fix(provider): coerce numeric tool call IDs for OpenAI-compatible providers

[Qiiks]

Issue for this PR

Fixes #19947

Type of change

• Bug fix

What does this PR do?

Some OpenAI-compatible providers (e.g. NVIDIA NIM kimi-k2.5) return numeric tool call IDs instead of strings, violating the OpenAI API spec. This causes Zod validation errors when the AI SDK processes responses.

The fix adds coercion at two points:

1. Fetch interceptor (provider.ts): For @ai-sdk/openai-compatible responses, numeric IDs in tool_calls[].id and delta.tool_calls[].id are converted to strings before the AI SDK processes them. Both JSON and SSE streaming responses are handled.

2. Part hydration (message-v2.ts): For backwards compatibility, numeric callID values stored in existing sessions are coerced to strings when loaded from the database.

The coercion functions were extracted to a shared utility (src/util/coerce-tool-call-ids.ts) to keep them usable across layers.

How did you verify your code works?

• 16 unit tests covering coerceNumericToolCallIds and transformSSEStream (numeric coercion, string passthrough, nested objects, delta.tool_calls, SSE parsing, [DONE] passthrough, invalid JSON passthrough, multiple events)
• bun typecheck passes with zero errors
• Existing provider tests still pass (258/260, 2 pre-existing timeouts unrelated to this change)
• Verified the coercion mutates the object correctly through type assertions

Checklist

• I have tested my changes locally
• I have not included unrelated changes in this PR

[github-actions]

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

1. Open an issue describing the bug/feature (if one doesn't exist)
2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

[krasnikau-andrei]

I tried this version on NVIDIA Nim Devstral, and the bug still persists

[github-actions]

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

• The PR was created more than 1 month ago
• The PR had fewer than 2 positive reactions
• Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.