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

{
32226 is harder because it requires tracing request-body handling across the MCP gateway boundary, correcting byte/text semantics without breaking JSON or streaming behavior, and adding regression coverage for multibyte boundary cases. 33780 is a narrower integration change across signing paths with focused configuration and AWS-compatible tests.
}
https://github.com/berriai/litellm/issues/32226 3:2 https://github.com/berriai/litellm/issues/33780