@revturbine/sdk 0.2.79 → 0.2.80

package/dist/index.d.ts

@@ -12926,6 +12926,8 @@ declare class RevTurbineCustomerSdk {
      * session so a render loop can never flood the channel.
      */
     private readonly emittedResolutionDiagnostics;
+    /** Session dedup for {@link reportSdkError}, keyed by `reason`. */
+    private readonly emittedSdkErrors;
     private static readonly RESOLUTION_DIAGNOSTIC_SESSION_CAP;
     /**
      * Gate for `resolution_failure` diagnostics (plan 144 TASK-21). Honors BOTH
@@ -12947,6 +12949,25 @@ declare class RevTurbineCustomerSdk {
      * `(reason, primary handle)` for the session and capped.
      */
     private emitResolutionFailure;
+    /**
+     * Report that the SDK itself failed (plan 182 TASK-5).
+     *
+     * `sdk_error` was declared in the meta taxonomy with no emitter. This is the
+     * "the SDK malfunctioned" signal — distinct from `resolution_failure`, which
+     * means a *decision* produced nothing. It rides the same anonymous
+     * `events_sdk_meta` lane: no tenant, no user, no placement identity.
+     *
+     * Deduped on `reason` for the session and capped, mirroring
+     * {@link emitResolutionFailure} — an SDK failing inside a render loop must
+     * not become a telemetry flood. Best-effort and never throwing: this is
+     * called from `catch` blocks, so it must not manufacture a second failure.
+     *
+     * @param reason Stable, categorical cause (e.g. `provider_init_failed`) —
+     *   what dashboards group by.
+     * @param message Human-readable detail for triage, sent on the same footing
+     *   as `sdk_validation_warning`'s message, which already ships on this lane.
+     */
+    reportSdkError(reason: string, message?: string): void;
     /** Fire the one anonymous `sdk_init` adoption beacon at startup. */
     private emitSdkInitTelemetry;
     /**