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

{
#33210 requires tracing and repairing cross-cutting request-finalization, cost tracking, callback, and persistence behavior across passthrough and router flows, with regression coverage for logging integrations. #32142 is comparatively localized to path interpretation in the MCP server and should require narrower code changes and tests.
}
https://github.com/berriai/litellm/issues/33210 4:1 https://github.com/berriai/litellm/issues/32142