Sender verified

A sending identity passed verification and the newsletter can send from it: its verification_status became verified. Two things reach that state, a newly provisioned sender the provider already considered verified, and a check on an existing sender coming back clean.

Load-bearing rather than cosmetic: sending from an unverified sender is refused with sender_not_verified, so this event is the signal that sending is unblocked.

Commune re-checks sending identities in the background as well as when a creator asks it to, so treat a repeat of this event for one sender as normal rather than as a second, different verification. Failing verification is a real state too, but is not among the topics Commune publishes.

Delivered as a single HTTPS POST to the consumer's registered endpoint, with the message as the JSON request body. Respond 2xx to acknowledge. Anything else, or a timeout, is retried with backoff, so acknowledge fast and do the work afterwards.