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

{
The right issue is harder because it requires tracing deployment identity through multiple proxy, passthrough, normalization, and spend-logging paths, then preserving consistent behavior without affecting cost attribution or analytics. The left issue is more localized to timeout propagation and error reporting.
}
https://github.com/berriai/litellm/issues/35472 3:1 https://github.com/berriai/litellm/issues/14635