Fixing Ollama Provider to match api endpoing and response structure a…

[DVG]

…s of today

What this does

When testing with Ollama and Deepseek-r1, both the completion URL and the expectations of the response structure were wrong as of the latest versions.

Type of change

• Bug fix
• New feature
• Breaking change
• Documentation
• Performance improvement

Scope check

• I read the Contributing Guide
• This aligns with RubyLLM's focus on LLM communication
• This isn't application-specific logic that belongs in user code
• This benefits most users, not just my specific use case

Quality check

• I ran overcommit --install and all hooks pass
• I tested my changes thoroughly
• I updated documentation if needed
• I didn't modify auto-generated files manually (models.json, aliases.json)

API changes

• Breaking change
• New public methods/classes
• Changed method signatures
• No API changes

Related issues

[crmne]

@DVG I downloaded the latest version of Ollama and I couldn't reproduce the error with qwen3. Is it specific to deepseek-r1? do you have a link to the documentation?

[crmne]

Not necessary.