@roarkanalytics/cli 0.37.1 → 0.39.0

package/man/roark-call-create.1

@@ -27,7 +27,7 @@ Interface type of the call (PHONE or WEB) One of: PHONE, WEB. Required.
 Direction of the call (INBOUND or OUTBOUND) One of: INBOUND, OUTBOUND. Required.
 .TP
 \fB\-\-ended\-status\fR \fI<value>\fR
-High\-level call end status, indicating how the call terminated One of: PARTICIPANTS_DID_NOT_SPEAK, AGENT_DID_NOT_ANSWER, AGENT_DID_NOT_SPEAK, AGENT_STOPPED_SPEAKING, AGENT_ENDED_CALL, AGENT_TRANSFERRED_CALL, AGENT_BUSY, AGENT_ERROR, CUSTOMER_ENDED_CALL, VOICE_MAIL_REACHED, SILENCE_TIME_OUT, PHONE_CALL_PROVIDER_CONNECTION_ERROR, CUSTOMER_DID_NOT_ANSWER, CUSTOMER_DID_NOT_SPEAK, CUSTOMER_STOPPED_SPEAKING, CUSTOMER_BUSY, DIAL_ERROR, MAX_DURATION_REACHED, UNKNOWN. Optional.
+High\-level call end status, indicating how the call terminated One of: PARTICIPANTS_DID_NOT_SPEAK, AGENT_DID_NOT_ANSWER, AGENT_DID_NOT_SPEAK, AGENT_STOPPED_SPEAKING, AGENT_ENDED_CALL, AGENT_SAID_END_CALL_PHRASE, AGENT_TRANSFERRED_CALL, AGENT_BUSY, AGENT_ERROR, CUSTOMER_ENDED_CALL, VOICE_MAIL_REACHED, SILENCE_TIME_OUT, PHONE_CALL_PROVIDER_CONNECTION_ERROR, CUSTOMER_DID_NOT_ANSWER, CUSTOMER_DID_NOT_SPEAK, CUSTOMER_STOPPED_SPEAKING, CUSTOMER_BUSY, DIAL_ERROR, MAX_DURATION_REACHED, UNKNOWN. Optional.
 .TP
 \fB\-\-transcript\fR \fI<value>\fR
 List of transcript entries made during the call Optional.

package/man/roark-simulation-plan-create.1

@@ -6,82 +6,17 @@ roark\-simulation\-plan\-create \- Create a run plan
 .B roark simulation plan create
 [\fIoptions\fR]
 .SH "DESCRIPTION"
-Creates a new simulation run plan. To run a simulation, use POST /v1/simulation/run instead: it starts a run from a plan or from an inline configuration, and takes runtime variables. Create a plan here when you want a reusable, named one to run later.
+Creates a new simulation run plan. To run a simulation, use POST /v1/simulation/run instead: it starts a run from a plan or from an inline configuration, and takes runtime variables. Create a plan here when you want a reusable, named one to run later. Send `template` instead of a full configuration to save one of the built\-in templates as a plan. It takes the same fields as the template variant of POST /v1/simulation/run, builds the same plan, and never starts it. To compare one property, attach the flow once and send `comparisonProperty` with the `comparisonValues` to run: the plan attaches the flow once per value.
 .SH "API"
 POST /v1/simulation/plan
-.SH "OPTIONS"
+.SH "REQUEST BODY"
+This endpoint accepts one of several request shapes, so the body is supplied as JSON through \e\-\e\-data or on standard input rather than as individual flags.
 .TP
-\fB\-\-name\fR \fI<value>\fR
-Name of the run plan Required.
+\fBCreateRunPlanFromConfig\fR
+Requires name, direction, maxSimulationDurationSeconds, agentEndpoints.
 .TP
-\fB\-\-description\fR \fI<value>\fR
-Description of the run plan Optional.
-.TP
-\fB\-\-direction\fR \fI<value>\fR
-Direction of the simulation (INBOUND or OUTBOUND) One of: INBOUND, OUTBOUND. Required.
-.TP
-\fB\-\-iteration\-count\fR \fI<value>\fR
-Number of iterations to run for each test case (1\-10000) Optional.
-.TP
-\fB\-\-max\-concurrent\-jobs\fR \fI<value>\fR
-Maximum number of concurrent simulation jobs Optional.
-.TP
-\fB\-\-max\-simulation\-duration\-seconds\fR \fI<value>\fR
-Maximum duration in seconds for each simulation Required.
-.TP
-\fB\-\-silence\-timeout\-seconds\fR \fI<value>\fR
-Timeout in seconds for silence detection Optional.
-.TP
-\fB\-\-max\-no\-response\-retries\fR \fI<value>\fR
-How many more times to run a test case when the agent under test never responds: it never speaks on a call or never replies in a chat (0\-10). 0 turns retries off. Failed checks and failures on Roark’s side are never retried. Each retry is a separate attempt, billed like any other, so a plan retrying N times can place up to N + 1 calls per test case. Every silent attempt stays on the run with its own call; the run settles once each test case has a final attempt, and the agent never spoke verdict is judged on each test case’s last attempt. Optional.
-.TP
-\fB\-\-no\-response\-retry\-backoff\-seconds\fR \fI<value>\fR
-Seconds a retry waits before it dials (30\-600). Only used when `maxNoResponseRetries` is above 0. Optional.
-.TP
-\fB\-\-end\-call\-phrases\fR \fI<value>\fR
-Phrases that trigger end of call. Empty array disables the feature. Repeatable. Optional.
-.TP
-\fB\-\-end\-call\-reasons\fR \fI<value>\fR
-Semantic conditions that trigger end of call. The LLM evaluates the conversation against these conditions. Empty array disables the feature. Repeatable. Optional.
-.TP
-\fB\-\-execution\-mode\fR \fI<value>\fR
-Execution mode (PARALLEL or SEQUENTIAL) One of: PARALLEL, SEQUENTIAL_SAME_RUN_PLAN, SEQUENTIAL_PROJECT. Optional.
-.TP
-\fB\-\-scenarios\fR \fI<value>\fR
-Deprecated: use `flows` instead. Scenarios to include in this run plan. The same scenario ID can appear multiple times with different variables. Optional.
-.TP
-\fB\-\-flows\fR \fI<value>\fR
-Customer flows to include in this run plan. The same flow can appear more than once with a different persona override, different variables, or different `overrides`: attaching it once per value of one property is how you compare that property without a template. Optional.
-.TP
-\fB\-\-personas\fR \fI<value>\fR
-Personas to include in this run plan. Required with `scenarios`; ignored with `flows`, where each variant carries its own persona. Optional.
-.TP
-\fB\-\-agent\-endpoints\fR \fI<value>\fR
-Agent endpoints to include in this run plan Required.
-.TP
-\fB\-\-metrics\fR \fI<value>\fR
-Metric definitions to include in this run plan. Reference each by `id` (UUID) or `slug`. Optional when the attached `flows` carry the grading: metrics a flow declares itself (with `includeFlowMetrics`), or the Agent Expectations and Keypad Entry metrics a run adds for flows with expectations or expected keypad entries (with `includeAutomaticMetrics`). A plan with nothing to grade is rejected with a 400. Optional.
-.TP
-\fB\-\-include\-flow\-metrics\fR
-Also collect each attached flow's own metrics, on top of the `metrics` named here. Default true, which is what you want when you brought your own flows and their graders. Set false for a run whose metric list is meant to be exhaustive: a template like Load Testing or Voicemail deliberately grades a narrow set, and inheriting every flow metric on top multiplies analysis cost across the volume without adding signal. GET /v1/simulation/template returns the value each template expects. Optional.
-.TP
-\fB\-\-include\-automatic\-metrics\fR
-Let the run add metrics by itself off the attached flows, on top of the `metrics` named here. Two attach this way today: Agent Expectations wherever an attached flow has agent expectations written on it, and Keypad Entry wherever one has steps where the agent is expected to press keys. Both grade something authored on the flow that nothing else measures, which is why it is on by default. Set false when the `metrics` list is meant to be exhaustive: a plan testing only whether the caller can complete the flow may not want the agent graded on its expectations as well. False also pins the plan against any automatic metric Roark adds later. Optional.
-.TP
-\fB\-\-comparison\-property\fR \fI<value>\fR
-The property this run plan investigates: the one thing its arms differ by. Set it and the run report compares the arms on that property, so a run answers "what did background noise cost" rather than just "what did each arm score". Every value is a field already recorded on each call, so the report can label an arm `CRYING_BABY` rather than repeating a flow variant's title. Omit it and the report still compares when it can: it detects which property varies across the arms. Setting it is what tells the written summary what you were trying to find out, which detection cannot infer. One of: ACCENT, AGE, BACKGROUND_NOISE, BACKGROUND_NOISE_VOLUME, BASE_EMOTION, CONFIRMATION_STYLE, GENDER, INTENT_CLARITY, LANGUAGE, INTERRUPTION, MEMORY_RELIABILITY, RESPONSE_TIMING, SPEECH_CLARITY, SPEECH_PACE. Optional.
-.TP
-\fB\-\-comparison\-baseline\fR \fI<value>\fR
-The reference value of `comparisonProperty`, for example `NONE` for `BACKGROUND_NOISE` or `NORMAL` for `SPEECH_PACE`: shown first in the results. Must be a value that property can take. Whether a value did significantly worse does not depend on it: that is decided against every other value combined (see `sweepAttribution`). Stored rather than assumed, so the report can say "compared against US accent" instead of implying Roark decided which value is normal. Most properties have an obvious baseline and the dashboard prefills it; `GENDER` has none, so choose the one you are testing against. Optional.
-.TP
-\fB\-\-comparison\-values\fR \fI<value>\fR
-Which values of `comparisonProperty` to run. This is what the plan costs: the flow is attached once per value, so ten values is ten times the calls of one. Omit it to run every value the property has, which for `ACCENT` is more than twenty. Send a subset to narrow the sweep, for example three accents you actually serve. A `comparisonBaseline` outside this set is rejected, because it would anchor every difference to an arm the run never made. Not stored as a field: the arms are the values. Reading the plan back returns them as its flow attachments. Repeatable. Optional.
-.TP
-\fB\-\-enrich\-with\-live\-conversation\fR
-Merge the customer's own recording of the real call into each simulation, so metrics can be scored against the live leg as well as the simulated one. This is the API equivalent of the dashboard's live\-enrichment toggle. With this on, the run provisions a phone number and holds each call open for up to 15 minutes waiting for a matching call to be posted to POST /v1/call. A call matches on the provisioned number (`roarkPhoneNumber` on the job) with a start time inside the simulation window. If nothing arrives, the simulation still completes and any `LIVE`\-sourced metric produces no value. Required by any metric whose `requiresLiveConversation` is true: without it that metric is silently skipped. Optional.
-.TP
-\fB\-\-auto\-run\fR
-Deprecated: use POST /v1/simulation/run, which starts a run and accepts runtime `variables` as well. This flag runs the plan with only the values pinned on it. Optional.
+\fBCreateRunPlanFromTemplate\fR
+Requires template, agentEndpoints, direction.
 .SH "GLOBAL OPTIONS"
 .TP
 \fB\-\-data\fR \fI<json>\fR
@@ -123,7 +58,7 @@ Send the stored credential to a base URL set by a project .roark.json. Refused b
 .PP
 .RS 4
 .nf
-roark simulation plan create \-\-name <value> \-\-direction <value> \-\-max\-simulation\-duration\-seconds <value> \-\-agent\-endpoints <value>
+roark simulation plan create \-\-data '{ ... }'
 .fi
 .RE
 .SH "ENVIRONMENT"

package/man/roark-simulation-plan-update.1

@@ -79,13 +79,13 @@ Whether to also collect each attached flow's own metrics, on top of this plan's
 Whether to let the run add metrics by itself off the attached flows. See `POST /v1/simulation/plan`. Optional.
 .TP
 \fB\-\-comparison\-property\fR \fI<value>\fR
-The property this plan investigates. Send `null` to clear the comparison; omit the field to leave it unchanged. See `POST /v1/simulation/plan`. The pair moves together. Sending `comparisonProperty` also sets `comparisonBaseline` to whatever this request carries, or to `null` if it carries none, because a baseline is a value of one specific property and keeping the old one would store a pair that is not valid. One of: ACCENT, AGE, BACKGROUND_NOISE, BACKGROUND_NOISE_VOLUME, BASE_EMOTION, CONFIRMATION_STYLE, GENDER, INTENT_CLARITY, LANGUAGE, INTERRUPTION, MEMORY_RELIABILITY, RESPONSE_TIMING, SPEECH_CLARITY, SPEECH_PACE. Optional.
+The property this plan investigates. Send `null` to clear the comparison; omit the field to leave it unchanged. See `POST /v1/simulation/plan`. The pair moves together. Sending `comparisonProperty` without `comparisonBaseline` keeps the stored baseline when the property is unchanged and the baseline is still one of the values being run. Otherwise it becomes the new property's norm, or `null` when that norm is not being run either, because a baseline is a value of one specific property. One of: ACCENT, AGE, BACKGROUND_NOISE, BACKGROUND_NOISE_VOLUME, BASE_EMOTION, CONFIRMATION_STYLE, GENDER, INTENT_CLARITY, LANGUAGE, INTERRUPTION, MEMORY_RELIABILITY, RESPONSE_TIMING, SPEECH_CLARITY, SPEECH_PACE. Optional.
 .TP
 \fB\-\-comparison\-baseline\fR \fI<value>\fR
 The reference value, shown first in the results. See `POST /v1/simulation/plan`. A real value cannot be sent on its own: the property it belongs to decides which values are legal, and an omitted property means "leave unchanged", which this endpoint cannot check a baseline against. Send `comparisonProperty` with it, or get a `400`. `null` on its own IS allowed, and clears just the baseline while leaving the property set. Nothing needs validating when clearing, and a property with no baseline is a real state: the report falls back to that property's own norm, and `GENDER` has no norm to fall back to. Optional.
 .TP
 \fB\-\-comparison\-values\fR \fI<value>\fR
-Which values of `comparisonProperty` to run. See `POST /v1/simulation/plan`. Omitting it keeps the arms the plan already has, so an edit that only renames the plan never widens a sweep you deliberately narrowed, and never multiplies what it costs. Repeatable. Optional.
+The arms to run. See `POST /v1/simulation/plan`. Omitting it keeps the arms the plan already has, pins included, so an edit that only renames the plan never widens a sweep you deliberately narrowed, and never multiplies what it costs. Send it with `comparisonProperty` and `flows`, which the arms are rebuilt from. Optional.
 .SH "GLOBAL OPTIONS"
 .TP
 \fB\-\-data\fR \fI<json>\fR

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "@roarkanalytics/cli",
-  "version": "0.37.1",
+  "version": "0.39.0",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "@roarkanalytics/cli",
-      "version": "0.37.1",
+      "version": "0.39.0",
       "license": "Apache-2.0",
       "dependencies": {
         "@roarkanalytics/sdk": "^4.23.0",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@roarkanalytics/cli",
-  "version": "0.37.1",
+  "version": "0.39.0",
   "description": "The official command line interface for the Roark API",
   "author": "Roark <james@roark.ai>",
   "type": "commonjs",

package/version.d.ts

@@ -1 +1 @@
-export declare const version = "0.37.1";
+export declare const version = "0.39.0";

package/version.js

@@ -10,4 +10,4 @@ exports.version = void 0;
 //
 // Do not edit: an edit here is overwritten, and the published number is whatever
 // package.json says.
-exports.version = '0.37.1'; // x-release-please-version
+exports.version = '0.39.0'; // x-release-please-version