/**
 * Traces seeder for `respan demo`.
 *
 * Ingests the supplied multi-agent service-desk traces (see trace-fixtures.ts)
 * into the authenticated account. All trace-specific logic lives here; the
 * orchestrator stays service-agnostic.
 *
 * Traces are treated as append-only run history: every `respan demo` run ingests a
 * fresh batch stamped at the current time, with freshly-generated trace/span ids.
 * Trace id + timestamps differ on every run, so runs never collide — there is no
 * dedup-skip and no teardown (`respan demo clear` leaves traces in place).
 *
 * Two workflow identifiers, on purpose:
 *   - `traceloop.workflow.name` is set to the shared constant `demo`
 *     (`span_workflow_name`, a filterable field) on every span, so one marker
 *     drives the dashboard filter and link across all demo traces.
 *   - the root span's NAME is set to the fixture's unique `workflow`
 *     (e.g. `demo.meridian-portal_outage-12`) — shown in the dashboard Workflow
 *     column, and unique per scenario. The platform dedups identical span CONTENT
 *     within a run (independent of trace id / timestamp), and the dataset repeats
 *     some scenarios with a byte-identical root span; a unique root name keeps each
 *     one distinct so all 12 ingest without a rejected span.
 *
 * Ingestion is a raw OTLP POST to `/v2/traces` (the SDK does not expose it).
 */
import { Seeder } from './types.js';
export declare const tracesSeeder: Seeder;