Reconciliation and Durable Sync — The Backstop That Makes Webhooks Trustworthy
Everything in this series hardened the event path — and post 1's contract still stands: delivery is not guaranteed, eventually. Endpoints stay down past retry horizons, subscriptions get misconfigured, providers have incidents too, and events from before your integration existed never arrive at all. The final discipline accepts this and closes the loop: periodic reconciliation against the source of truth, convergence-oriented sync design, and the backfill machinery that makes "we missed a week" a procedure instead of a crisis. This is what turns a webhook integration into a synchronization system.
Non-delivery is in the contract, so build the backstop: modified-since sweeps through the same version-gated upserts (healing and counting missed deliveries), deliberate deletion detection, and rehearsed resumable backfill. The end state is a sync engine: events for latency, reconciliation for truth, replay for recovery.