Kafka publishing succeeds but the DB transaction rolls back. How could consumers receive an event for data that does not exist?

Tests whether you identify this as the inverse dual-write hazard -- publishing before the DB commit is confirmed -- and that the fix is the same outbox pattern: only publish events that were committed in the same local transaction as the state change, never before.