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

{
Issue 34820 is harder because it requires safely redesigning asynchronous spend-queue flushing around failures and cancellation, coordinating scheduler shutdown behavior, preserving data integrity, and adding concurrency/regression coverage. Issue 28619 is primarily a documentation and chart-maintenance decision with limited implementation scope.
}
https://github.com/berriai/litellm/issues/34820 5:1 https://github.com/berriai/litellm/issues/28619