/**
 * Early telemetry preload for the dev-server child.
 *
 * This module has ONE job: start the OpenTelemetry SDK before any instrumented
 * module (node:http, express, the ai-service) is loaded. OTel auto-instrumentation
 * patches modules at require time, so if the SDK starts late — as it did when the
 * only init was `configureTelemetry` at connect time — those modules load
 * unpatched and the dev-server exports nothing. The child entry (`dev.mts`)
 * imports this as its very first import so it runs before the SDK barrel.
 *
 * It intentionally does NOT init dd-trace/LLMObs. Those spans are created during
 * generation (after connect) and need the application id that is only known then,
 * so `configureTelemetry` still owns LLMObs. `configureTelemetry`'s own
 * `initNodeTelemetry` call becomes a no-op here: `initNodeTelemetry` returns the
 * already-created instance, so we init once, early.
 *
 * Config comes from the environment (available at process start), not the auth
 * file, so nothing here has to await a network/disk read. The endpoint and
 * environment tag are resolved by the shared `otlp-config` module, the same one
 * the lightweight parent uses, so parent and child agree on where telemetry goes.
 */
export {};
//# sourceMappingURL=preload.d.ts.map