Integrate the map trigger recipients use case in events controller

Editor assessment

A service-oriented commit that benefits from the api scope, and 'integrate' is a proper imperative verb. The subject is dense with domain vocabulary — 'map trigger recipients use case' — which is precise for insiders but opaque to anyone reading the changelog cold; still, naming the destination (events controller) helps. At roughly 78 characters overall it slightly exceeds the 72-character comfort zone. The missing body is the bigger issue: a use-case integration usually implies wiring, DI changes, or behavioral side effects, and one paragraph on what the mapping does to outgoing event payloads would make this self-documenting.