The :telemetry handler attached to every name OpentelemetryStatifier.Oban.events/0 returns.

Two clauses do the whole family, because the contract has exactly two seams and no pairs: a scheduling event lands on the span open in the emitting process - the macrostep span when the session is stepping there, the durable driver's step span when a durable run id is all the event carries - and a delivery event becomes its own span linked to the arming trace. The defensive posture is OpentelemetryStatifier.Handler's - no try/rescue, exhaustive clauses, a catch-all that drops rather than raises inside a host's Oban worker.