docs: add Tuning Engines LiteLLM route

[cerebrixos]

Hi opencode-litellm maintainers, we are an AI infrastructure team using OpenCode through LiteLLM with governed model routes. Since this plugin already discovers LiteLLM model_list entries, I added a small Tuning Engines upstream example that works with the existing configuration flow.

OpenCode and this plugin still own model discovery and picker wiring. Tuning Engines sits on the upstream model route for teams that need tenant policy, traces, approvals, and usage visibility around coding-agent traffic.

It would mean a lot to us if you are open to including this as an example for governed LiteLLM upstreams.

Validation:

• git diff --check

Summary by CodeRabbit

• Documentation
  • Added guide for routing OpenCode model traffic through a governed upstream using Tuning Engines
  • Includes configuration example and step-by-step setup instructions for API key management and service startup
  • Clarifies role separation between OpenCode and Tuning Engines components

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 3b339af3-94b1-4837-9fc7-28062dfa4d22

📥 Commits

Reviewing files that changed from the base of the PR and between 02943ac and de96a72.

📒 Files selected for processing (1)

• README.md

---

📝 Walkthrough

Walkthrough

This PR adds a documentation example to the README demonstrating how to route OpenCode model traffic through Tuning Engines as a governed upstream control plane. The addition includes a LiteLLM model_list YAML configuration block and shell commands to set up and run the integration.

Changes

Tuning Engines Integration Guide

Layer / File(s)	Summary
Governed upstream route documentation README.md	New example section showing LiteLLM model_list YAML configuration with openai/gpt-5.4-mini routing through Tuning Engines, environment variable setup, and shell commands to start LiteLLM and OpenCode. Clarifies that the plugin retains discovery and picker wiring while Tuning Engines serves as the governed control plane.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A rabbit hops through docs with glee, 🐰
Tuning Engines flow now plain to see,
Config and commands, side by side,
The governed upstream, our trusted guide! 🚀

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'docs: add Tuning Engines LiteLLM route' accurately describes the main change - adding documentation for routing through Tuning Engines via LiteLLM.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Warning

⚠️ This pull request might be slop. It has been flagged by CodeRabbit slop detection and should be reviewed carefully.