Greptile Summary

This PR adds a Messenger class that wraps multiple messaging adapters and provides automatic exception-based failover, trying each adapter in sequence until one succeeds or all have failed.

• Messenger.php: New orchestration class with constructor-time validation (empty list, non-adapter elements, mixed adapter/message types), a send() method with failover loop and aggregate error reporting, and helpers (getType, getMessageType, getMaxMessagesPerRequest).
• MessengerTest.php: 14 tests covering success path, single/multi-adapter failover, all-fail aggregation, type validation, and the explicit design decision that non-exception failure payloads do not trigger fallback.
• README.md: Usage example added for the Messenger with Twilio/Vonage failover scenario.

Confidence Score: 4/5

Safe to merge after confirming the open discussions from earlier review rounds are resolved; the core logic is sound but the failover mechanism has edge cases worth closing before shipping.

The implementation is well-structured and the test suite is thorough. However, the failover catch block covers only \Exception, meaning \Error subclasses thrown by adapters (e.g. \TypeError from a broken process() implementation) escape the loop and propagate immediately without trying subsequent adapters. That gap was raised in a prior round and remains unaddressed in the diff, leaving the failover guarantee incomplete for a real-world failure class that adapters can plausibly produce.

src/Utopia/Messaging/Messenger.php — the catch block and the soft-failure/getMaxMessagesPerRequest contract warrant a second look before merge.

Important Files Changed

_{Reviews (2): Last reviewed commit: "feat: add Messenger class for multiple a..." | Re-trigger Greptile}