Description

Restore LiteLLM-backed integrations that were temporarily hard-disabled, while constraining the Python dependency to stay below 1.82.6 so installs do not resolve into the compromised release window.

Related Issue

• N/A

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Performance improvement
• Test update

Changes Made

• Reverted the temporary LiteLLM hard-disable across bot tools, VLM/embedder/rerank config entry points, and provider exports.
• Resolved the CLI provider conflict introduced after #937 so the LiteLLM-backed path is restored cleanly.
• Pinned litellm to >=1.0.0,<1.82.6 in project metadata and lockfile to avoid the compromised versions and newer unconfirmed releases.

Testing

• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have tested this on the following platforms:
  • Linux
  • macOS
  • Windows

Checklist

• My code follows the project's coding style
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• Any dependent changes have been merged and published

Screenshots (if applicable)

• N/A

Additional Notes

• Local verification run: python -m pytest --override-ini addopts='' tests/unit/test_litellm_embedder.py
• This PR intentionally keeps LiteLLM below 1.82.6 until the upstream incident is fully closed and a clearly safe version is communicated.