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

{
The left issue requires tracing shared request state across concurrent async guardrail execution, redesigning token allocation and reverse mapping invariants, and adding regression coverage for ordering and collisions. The right issue is a narrowly scoped catalog-data update with comparatively low implementation risk.
}
https://github.com/berriai/litellm/issues/31959 8:1 https://github.com/berriai/litellm/issues/31075