Sorting LiteLLM GitHub issues by difficulty to implement. Higher = harder.

{
The left is harder because it requires cross-cutting changes to persistence, pricing/version selection, billing semantics, repeatable execution, auditability, and operational safety. The right is mainly a configuration-resolution and routing-graph feature, with recursion, validation, and compatibility risks but a narrower runtime scope.
}
https://github.com/berriai/litellm/issues/31835 3:1 https://github.com/berriai/litellm/issues/28125