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

{
Recurring availability schedules require new configuration schemas, timezone-aware window evaluation, overnight and boundary handling, credential inheritance across deployments, routing integration, backward compatibility, and broad testing. The logging issue is comparatively localized to sanitizing and validating a metadata field in two builders, with focused regression and security tests.
}
https://github.com/berriai/litellm/issues/34662 5:1 https://github.com/berriai/litellm/issues/34710