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

{
The right issue is harder because it crosses pass-through routing, response-format normalization, guardrail enforcement semantics, and likely multiple provider and streaming paths. The left issue appears more localized to streaming error-state termination and callback lifecycle handling, with a narrower validation surface.
}
https://github.com/berriai/litellm/issues/32201 3:2 https://github.com/berriai/litellm/issues/13786