guard-core 3.1.0 compatibility: cloud-provider set typing + lazy-init test alignment (v 7.1.1)
- Fixed — refresh_cloud_ip_ranges() normalizes block_cloud_providers to set[str] before forwarding to guard-core's cloud handler (set-invariance mypy fix; runtime unchanged).
- Fixed (tests) — Redis-init test opts into lazy_init=False to assert the eager cloud/geo-IP wiring path.
- Compatibility — Patch-level, no public API change; explains that v7.1.0's CI completed ~6 min before guard-core 3.1.0 published, leaving the two 3.1.0-only changes unexercised until now, plus user guidance on the lazy_init=True background-warm-up behavior.
- Requires — guard-core>=3.1.0 (unconstrained in pyproject; documented for upgrade guidance).
Full Changelog: 7.1.0...7.1.1