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

{
The right issue is harder because it requires propagating deployment-resolution metadata through router, proxy response, header, streaming, and compatibility paths, with broader API and regression-test impact. The left issue is more concentrated in tracing span ordering and processor lifecycle handling, though it carries integration-specific correctness risk.
}
https://github.com/berriai/litellm/issues/25503 3:2 https://github.com/berriai/litellm/issues/33511