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

{
#26237 is harder because it spans worker lifecycle, startup readiness, retry/recovery behavior, distributed configuration state, and traffic-gating semantics, with substantial operational and regression risk. #34732 is narrower, primarily requiring an atomic distributed admission/reservation mechanism and related accounting tests.
}
https://github.com/berriai/litellm/issues/26237 3:1 https://github.com/berriai/litellm/issues/34732