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

{
28235 is harder because it requires coordinated persistence, concurrency-safe accounting, authentication enforcement, lifecycle resets, backward compatibility, and broad regression coverage across core budget paths. 33371 is mainly an interface and classification-contract extension around existing routing state, with narrower implementation boundaries.
}
https://github.com/berriai/litellm/issues/28235 3:1 https://github.com/berriai/litellm/issues/33371