@loadstrike/loadstrike-sdk 1.0.20801 → 1.0.21301

package/README.md

@@ -5,11 +5,12 @@ LoadStrike is a developer-first load testing SDK for Node.js applications, servi
 ## What This SDK Is For
 
 - Author scenario-based load tests in TypeScript or JavaScript.
+- Generate safe starter scenarios from captured HAR, OpenTelemetry trace JSON, browser recordings, or message pairs with Trace-to-test Autopilot.
 - Exercise HTTP and event-driven workflows across multiple steps.
 - Apply load simulations, thresholds, and custom metrics to real transactions.
-- Generate local reports and, on eligible plans, publish observability data to supported sinks.
+- Generate local reports and, on Business and Enterprise, publish observability data to supported sinks.
 
-Built-in transport coverage includes HTTP, Kafka, RabbitMQ, NATS, Redis Streams, Azure Event Hubs, Push Diffusion, and delegate-based custom streams. Local report output supports HTML, Markdown, TXT, and CSV, and eligible plans can publish to InfluxDB, TimescaleDB, Grafana Loki, Datadog, Splunk HEC, and OpenTelemetry Collector.
+Built-in transport coverage includes HTTP, Kafka, RabbitMQ, NATS, Redis Streams, Azure Event Hubs, Push Diffusion, and delegate-based custom streams. Local report output supports HTML, Markdown, TXT, and CSV, and Business and Enterprise can publish to InfluxDB, TimescaleDB, Grafana Loki, Datadog, Splunk HEC, and OpenTelemetry Collector.
 
 ## Requirements
 
@@ -52,6 +53,12 @@ const result = await LoadStrikeRunner
 
 `run()` returns the detailed run result, including generated report files, scenario statistics, metrics, and sink status.
 
+## Trace-To-Test Autopilot
+
+Use `LoadStrikeAutopilot.generate(...)` to infer a starter plan from a captured artifact. Check `result.Readiness` and `result.ReadinessFailures` first; call `result.buildScenario()` only when it is `LoadStrikeAutopilotReadiness.Ready`, then execute the scenario through the normal runner with a valid `RunnerKey`.
+
+Use `SecretBindings` to map redaction locations such as `header:Authorization` or `body:$.client_secret` to environment variables, `TrackingSelector` when the selector cannot be inferred, and `EndpointBindings`, `AllowedReplayHosts`, or `BaseUrlRewrite` when a replay target must be bound. Secret values are resolved when the generated scenario runs; they are not written into the generated plan. Any gate satisfied by user setup is omitted from `ReadinessFailures`.
+
 ## Runner Keys
 
 Runnable workloads require a `RunnerKey`. Supply it with `.withRunnerKey(...)` or through your application configuration before calling `run()`.

package/dist/cjs/autopilot-contracts.js

@@ -0,0 +1,11 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.LoadStrikeAutopilotReadiness = void 0;
+exports.LoadStrikeAutopilotReadiness = {
+    Ready: "Ready",
+    RequiresSecrets: "RequiresSecrets",
+    RequiresEndpointBinding: "RequiresEndpointBinding",
+    RequiresTargetBinding: "RequiresTargetBinding",
+    RequiresTrackingSelector: "RequiresTrackingSelector",
+    RequiresReview: "RequiresReview"
+};