How does the outbox pattern solve the dual-write problem?

It writes the event/message to be published into an outbox table in the SAME local database transaction as the actual business data change — since both are just INSERT statements in one transaction, they're genuinely atomic (both succeed or both roll back together). A separate process then reliably publishes the outbox rows afterward, closing the gap a separate network call would have left open.