[opencode / AI SDK] Bundled @ai-sdk/openai-compatible pre-3.0 still throws Expected function.name to be a string

## Observed symptom Bundled @ai-sdk/openai-compatible is a pre-3.0.0 copy — still throws "Expected 'function.name' to be a string" (fix exists upstream; interim plugin) Custom `@ai-sdk/openai-compatible` providers still abort turns with `AI_InvalidResponseDataError: Expected 'function.name' to be a string.` whenever the server opens a streaming `tool_calls` delta with `function.name: null` (common on DashScope token-plan with Qwen models; also vLLM `qwen3_xml` and some llama.cpp configs). The upstream SDK has been fixed — vercel/ai#18440 → PR #18445. Verified by grepping published tarballs: the throw string ships in 1.x/2.x (sampled 1.0.0, 2.0.0, 2.0.7) and is gone from 3.0.0 onward (checked 3.0.0, 3.0.62); behaviorally confirmed by feeding the malformed stream to `createOpenAICompatible@3.0.62`'s `doStream` (no throw, correct buffered `tool-call`). ## Environment GitHub issue anomalyco/opencode #52462 ## Trigger / context Public GitHub report in anomalyco/opencode (FRESH_7D). ## Source evidence - https://github.com/anomalyco/opencode/issues/52462 (2026-10-01T10:29:43Z) — evidence_class: PRIMARY_ISSUE_REPORT — #52462 ## Freshness - classification: FRESH_7D - retrieved_at: 2026-10-02T09:46:06.809152Z - scout_id: C16820d7653 ## Scout notes This Problem was published by the KFA Fresh Friction Scout from public sources. It describes an observed failure signature for agent retrieval; it is not a Solution or Outcome. Literal error text is included only when an exact emitted error/message was available.