fix: expand tool support to reduce 'Invalid tool name' errors

[RomneyDa]

Summary

• Azure: Add gpt-5, gpt-4.1, o1, o4 model prefixes (was only gpt-4, o3)
• Ollama: Add glm-4/glm-5, deepseek, and dolphin model families
• DeepSeek provider: Add deepseek-coder (was only deepseek-chat/deepseek-reasoner)
• OpenRouter: Add deepseek/deepseek-v3 and deepseek/deepseek-coder prefixes

Root cause

When a model is not recognized in PROVIDER_TOOL_SUPPORT (core/llm/toolSupport.ts), Continue falls back to a text-based tool calling format injected into the system message. The model is expected to output tool calls in a specific structured format ( ```tool / tool_name: / begin_arg: / end_arg blocks). When models don't follow this format exactly, the parser at core/tools/systemMessageTools/toolCodeblocks/parseSystemToolCall.ts:47 throws "Invalid tool name".

All 11 reported issues are models that do support native tool calling but were missing from the allowlist, causing them to fall through to the fragile text-based path.

Fixes

Fixes #10678, #11594, #11431, #11218, #10900, #10272, #10156, #10143, #10050, #9891, #9839

Test plan

• Verify existing core/llm/toolSupport.test.ts tests pass
• Test with an Ollama glm-4 or deepseek model — should use native tool calling instead of system message fallback
• Test with Azure gpt-5-mini — should use native tool calling

---

Summary by cubic

Expands tool support so native tool calling is used for more Azure, Ollama, DeepSeek, and OpenRouter models, eliminating "Invalid tool name" errors. Prevents fallback to the fragile system-message tool format for these families.

• Bug Fixes
  • Azure: recognize gpt-5, gpt-4.1, o1, o4 prefixes.
  • Ollama: recognize glm-4, glm-5, deepseek, dolphin.
  • DeepSeek: recognize deepseek-coder* in the provider.
  • OpenRouter: recognize deepseek/deepseek-v3 and deepseek/deepseek-coder*.

^{Written for commit 7335493. Summary will update on new commits.}

[continue]

Docs Review: No documentation updates needed.

This PR expands the internal model allowlist in toolSupport.ts to fix 'Invalid tool name' errors for Azure, Ollama, DeepSeek, and OpenRouter models that support native tool calling.

The existing Model Capabilities documentation already:

• Explains how auto-detection works and links to toolSupport.ts for implementation details
• Provides guidance on manually configuring capabilities for unrecognized models
• Covers the affected model families (DeepSeek, GLM, etc.) in the capability tables

Since this is a bug fix improving auto-detection accuracy rather than introducing new features or configuration options, no documentation changes are required.

[cubic-dev-ai]

No issues found across 1 file