Effect-native wide spans, delivery, propagation, and exporters

Vendor-neutral spans, metrics, and error reporting backed by a pluggable OTLP provider. Off by default; the telemetry runtime is loaded only when explicitly enabled.

Browser telemetry for OnePatch — page views, clicks, errors and fetch spans, correlated with your backend traces.

Your telemetry surface as a typed, versioned contract — declare the spans and attributes your service emits, validate live spans against them, and diff the surface across commits to catch breaking trace changes before they ship.

Time spans, especially for financial technology.

Stackflow plugin for Sentry browser tracing. Automatically creates navigation spans and breadcrumbs for activity transitions (`push`, `pop`, `replace`) and step transitions (`stepPush`, `stepPop`, `stepReplace`).

A `remark` plugin for Pandoc-style bracketed spans.

Adds OpenTelemetry tracing auto-instrumentation in the browser. Collects spans on network events and sends them to Sumo Logic.

BonkLM VoltOps OTel adapter — emits OTel spans with bonklm.scanner / severity / action / category attributes (Story 3.10)

Bridge autotel and Effect v4: Effect.withSpan spans export through autotel's global TracerProvider

Source spans, diagnostic codes, and error formatting for Intent Language.

Trace execution spans all across your application.

OpenTelemetry bridge: OTel spans → loomtrace trace format.

OpenInference-compliant OpenTelemetry tracing for reactive-agents — maps AgentEvent stream to semantic spans

A micromark syntax extension for Pandoc-style bracketed spans.

Server-side OpenTelemetry preload for Ripplo — streams backend spans into test runs

Add tracing spans to each request handler for core components library

A queryable semantic index over the @cssdoc/core model, plus a host-agnostic Usage abstraction and source spans — the shared data layer for cssdoc's linters and language server.

Debugs, logs, and spans — one API. Disabled logs skip argument evaluation entirely via optional chaining. ~3KB, zero dependencies.

`@zuplo/otel` instruments your Zuplo API with [OpenTelemetry](https://opentelemetry.io/) — incoming requests, policies, handlers, and outbound `fetch` — and exports the resulting spans to the Zuplo-managed trace ingest and/or to any OTLP/HTTP destination(