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

{
Historical spend correction has greater scope and risk: it requires safe, repeatable data mutation, pricing-version handling, policy semantics, auditability, and operational safeguards. Custom routing is architecturally significant but can largely be isolated behind a routing extension interface and proxy integration.
}
https://github.com/berriai/litellm/issues/31835 5:4 https://github.com/berriai/litellm/issues/25297