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

{
Issue 21347 is harder because it requires designing and integrating broad schema-conformance validation across many providers, response shapes, streaming paths, and ongoing compatibility workflows. Issue 34733 is narrower, focused on making an accounting update path concurrency-safe and reliably persisted, though it still carries distributed-systems testing risk.
}
https://github.com/berriai/litellm/issues/21347 4:1 https://github.com/berriai/litellm/issues/34733