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

{
The right issue is harder because it requires designing and integrating a durable cross-provider error taxonomy and router-health API, aligning internal state with externally consumed metadata, preserving compatibility, and adding broad tests and documentation. The left issue is comparatively localized debugging and correction of an Azure request-path parameter propagation defect.
}
https://github.com/berriai/litellm/issues/33371 4:1 https://github.com/berriai/litellm/issues/26897