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

{
The left issue is harder because it involves correcting shared persistence, batching, retry, and data-integrity behavior across multiple spend paths, with higher concurrency and regression risk. The right issue is comparatively localized to response normalization in one provider integration and can likely be addressed with focused parsing and tests.
}
https://github.com/berriai/litellm/issues/29292 4:1 https://github.com/berriai/litellm/issues/29156