Check if this issue is valid — if so, understand the root cause and fix it. At src/core/tracing/adapters/ApiSpanAdapter.ts, line 233:

<comment>Timeout failures are not counted because the abort check only matches `AbortError`, while this code aborts with `new Error(...)` as the reason.</comment>

<file context>
@@ -178,4 +167,76 @@ export class ApiSpanAdapter implements SpanExportAdapter {
+        throw new Error(`Remote export failed: ${parsed.message}`);
+      }
+    } catch (error) {
+      if (error instanceof Error && error.name === "AbortError") {
+        this.timeoutCount += 1;
+        throw error;
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At docs/nextjs-initialization.md, line 207:

<comment>The startup note overstates pre-ready capture semantics. It says all requests before `markAppAsReady()` are always recorded, but this feature is described as preserving only the first inbound pre-app-start request.</comment>

<file context>
@@ -184,17 +184,31 @@ More context on setting up instrumentations for Next.js apps can be found [here]
+   - `recording.sampling.mode` comes from `.tusk/config.yaml` and defaults to `fixed`
+   - `recording.sampling.min_rate` is only used in `adaptive` mode and defaults to `0.001` when omitted
+
+> **Note:** Requests before `TuskDrift.markAppAsReady()` are always recorded. Sampling applies to normal inbound traffic after startup.
 
 ### Method 1: Init Parameter
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At src/core/tracing/TdSpanExporter.ts, line 102:

<comment>Preserve `null` when no export latency has been observed instead of coercing it to `0` during aggregation.</comment>

<file context>
@@ -71,6 +80,39 @@ export class TdSpanExporter implements SpanExporter {
+        failureCount: accumulator.failureCount + snapshot.failureCount,
+        timeoutCount: accumulator.timeoutCount + snapshot.timeoutCount,
+        circuitOpen: accumulator.circuitOpen || snapshot.circuitState === "open",
+        lastExportLatencyMs: Math.max(
+          accumulator.lastExportLatencyMs ?? 0,
+          snapshot.lastExportLatencyMs ?? 0,
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At src/core/sampling/AdaptiveSamplingController.ts, line 205:

<comment>When adaptive load shedding drives `effectiveRate` to exactly 0 (hot/warm state with `minRate = 0`), the reason is misreported as `"not_sampled"` instead of `"load_shed"`. This breaks observability: operators cannot distinguish "configured rate is zero" from "adaptive controller suppressed all traffic".</comment>

<file context>
@@ -0,0 +1,283 @@
+    if (effectiveRate <= 0) {
+      return {
+        shouldRecord: false,
+        reason: this.state === "critical_pause" ? "critical_pause" : "not_sampled",
+        mode: this.config.mode,
+        state: this.state,
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At src/core/tracing/DriftBatchSpanProcessor.ts, line 51:

<comment>`void this.flushOneBatch()` discards the returned promise. If the exporter throws synchronously inside `export()`, the resulting rejection is unhandled and can crash the process. Add a `.catch()` at these fire-and-forget call sites, or wrap the `this.exporter.export(...)` call in a try/catch that calls `resolve()`.</comment>

<file context>
@@ -0,0 +1,152 @@
+    this.config = config;
+    this.mode = mode;
+    this.interval = setInterval(() => {
+      void this.flushOneBatch();
+    }, this.config.scheduledDelayMillis);
+    this.interval.unref?.();
</file context>