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

{
#26335 is harder because it spans provider-specific file behavior, managed-files integration, persistence metadata, and enterprise-hook compatibility, requiring broader investigation and end-to-end validation. #33204 is comparatively localized to async scheduling, initialization synchronization, and regression tests around routing concurrency.
}
https://github.com/berriai/litellm/issues/26335 2:1 https://github.com/berriai/litellm/issues/33204