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

{
Nested access-group composition is harder because it changes authorization data modeling and resolution semantics, requiring recursive expansion, cycle protection, propagation/invalidation behavior, compatibility handling, and broad API, persistence, and test coverage. The budget fix is risky due to distributed concurrency and atomic accounting, but is more narrowly scoped to admission and storage coordination.
}
https://github.com/berriai/litellm/issues/28032 3:2 https://github.com/berriai/litellm/issues/34732