The bridge half for statifier_oban's event family, [:statifier_oban, ...] - what happens between a chart's delayed send or invoke and the durable job row, frozen by that package's docs/adr/0006-telemetry-events-for-the-durable-seams.md and tabulated in its docs/telemetry.md.

A separate setup call, per st-ADR-0062 and ots-ADR-0002 decision 2:

OpentelemetryStatifier.setup()
OpentelemetryStatifier.Oban.setup()

This module bridges statifier_oban's fourteen events and nothing else. Oban's own [:oban, :job, ...] spans are opentelemetry_oban's to produce, and a host wanting both attaches both - the reason statifier_oban deliberately emits no duration, no attempt timing and no queue wait is that Oban already does.

What it produces

Every event in this family is a point - that contract has no :start/:stop pairs, because Oban owns every interval it could bracket - and the seams land differently, exactly as the contract describes:

• The scheduling seam (:scheduled, :schedule_rejected, :cancelled, :enqueued, :enqueue_rejected and the invoke :cancelled) fires synchronously on the process that drove the macrostep. When that macrostep's span is open in that same process, these become span events on it: the chart's decision and its durable consequence in one span.
• The delivery seam (:fired, the two :discarded, :delivered, :failed) fires inside an Oban job, days later and usually on another node. Those become their own spans, linked to the trace that armed the timer through caller_context when the host stamped a W3C traceparent there. A link and never a parent: parenthood would hold the arming trace open for the length of the delay. With no caller_context, the span is simply unlinked - the ordinary detached case, correlated by statifier.session_id.
• The fan-out seam (:fan_out, :child_started, :unstarted_cancelled) splits across the two shapes above rather than adding a third. :fan_out and :child_started fire inside Oban jobs - the fan-out worker, and one child-start worker per item - and both carry caller_context, so they take the delivery shape: a root span linked to the trace that planned the invocation. That link is what makes every chunk child reachable from the parent's dispatch step by an edge rather than only by a shared statifier.session_id. :unstarted_cancelled carries no caller_context and so has no link source; it fires from the sweep, synchronously on whichever process ran it, so it takes the scheduling shape and lands as a span event on the span open there, becoming its own root only when there is none. Its count is the fact worth having in the trace, and both shapes put it there.

:child_started is a linked root, not a parent. statifier_oban emits it after the child-starter seam returns, so by the time the bridge sees it the child's own statifier_persistence.run.step span has already opened and closed in that process: there is no window in which this bridge could have the start span open around them. Nesting them under it would need an event the contract does not have, and reaching past the public events for one is what st-ADR-0062 and ots-ADR-0002 forbid. A host with its own durable driver that wants the nesting has the sanctioned door - OpentelemetryStatifier.Parent.register/2 - and everyone else gets the link edge, which is what the reachability question actually asks for.

scope is the correlation key here (it is either a live session's id or a host's durable run id, and this package cannot tell which), and it maps onto statifier.session_id - the rename happens here, once, where the mapping is visible, exactly as statifier_oban's note asks.

The event list

The 14 names below are literal here rather than read from StatifierOban.Telemetry.events/0, for the reason OpentelemetryStatifier.Persistence's moduledoc gives: bridging a sibling must not make that sibling - and Oban, and a database - a dependency of every host that wants statechart tracing.

The list is not checked by hand either. statifier_oban is a only: :test, runtime: false dependency, and test/opentelemetry_statifier/sibling_event_drift_test.exs asserts this list against StatifierOban.Telemetry.events/0 on every gate run.