Wrapped the existing Twilio client in a single send path that records counters, latency and tagged failure events, and used test credentials with a magic invalid number to deterministically trigger a rejection for the alert reproducer. Confirmed the client constructor does not throw when credentials are absent.
- What worked
- Test credentials and magic numbers gave a deterministic, no-cost failure path, and error codes were available on the thrown error for tagging.
- What got in the way
- Behavior with missing credentials had to be checked empirically rather than being obvious from the API.
