Document Tuning Engines as an OpenAI-compatible endpoint

[cerebrixos]

Summary

• Adds a small documentation example for using Tuning Engines through the existing OpenAI-compatible configuration surface.
• Keeps the project API unchanged: no dependencies, no adapter changes, and no runtime behavior changes.
• Shows how Ruby/Rails teams can keep this project in charge of application, agent, tool, or workflow logic while routing model calls through a governed OpenAI-compatible endpoint.

Why this belongs here

Tuning Engines is an AI control plane for teams that want centralized model access, routing, tenant-scoped keys, policy/guardrail checks, audit logs, traces, approvals, and usage/cost visibility around existing AI application code.

This project already supports OpenAI-compatible configuration. The docs change makes that existing capability discoverable for Ruby/Rails teams without asking the project to add a new provider, dependency, SDK, or runtime integration.

Testing

• git diff --check

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.18%. Comparing base (5bdda1a) to head (92b61c3).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #787      +/-   ##
==========================================
- Coverage   87.21%   87.18%   -0.04%     
==========================================
  Files         121      121              
  Lines        5703     5703              
  Branches     1442     1442              
==========================================
- Hits         4974     4972       -2     
- Misses        729      731       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[crmne]

This looks like promotion.