Domain events

Every event is a final readonly class in RoundlyConsulting\Events\Events, implements ShouldDispatchAfterCommit — a rolled-back write dispatches nothing — and holds models. None broadcasts by itself; if you broadcast from a listener, render references, never class names.

use Illuminate\Support\Facades\Event as EventBus;   // Models\Event shadows Laravel's facade name
use RoundlyConsulting\Events\Events\AttendeeCheckedIn;
use RoundlyConsulting\Events\Events\RsvpCancelled;

EventBus::listen(RsvpCancelled::class, function (RsvpCancelled $cancelled): void {
    if ($cancelled->wasPaid) {
        // refund $cancelled->rsvp->payment_reference at your provider
    }
});

EventBus::listen(AttendeeCheckedIn::class, function (AttendeeCheckedIn $in): void {
    logger()->info('door scan', ['event' => $in->result->rsvp->event->uuid, 'first' => $in->result->firstCheckIn]);
});

Import Laravel’s facade under another name — the package’s Models\Event shadows Event. Listeners see the committed rows.

• The package listens to lifecycle’s LifecycleTransitioning and LifecycleTransitioned — the sequence, the cancellation effects, the phase events above — and to its own events for the notices. Fake only the events you assert; Testing explains why.
• InvitationSent carries the plain token: keep it out of logs and encrypt queued listeners (ShouldBeEncrypted).