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

{
The right issue is harder because it requires tracing an asynchronous lifecycle across API handling, persistence, polling, provider-specific completion states, cost accounting, retries, and regression coverage. The left issue is a localized performance refactor with a comparatively narrow implementation and validation surface.
}
https://github.com/berriai/litellm/issues/35131 4:1 https://github.com/berriai/litellm/issues/31861