@nopaque/sdk 0.4.0 → 0.7.0

package/CHANGELOG.md

@@ -4,6 +4,72 @@ All notable changes to this project will be documented in this file.
 The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.7.0] - 2026-08-19
+
+### Fixed
+
+- `waitForRun()` could return before the run's verdict was written, giving
+  `outcome: undefined` and no step results on a run that had actually passed.
+  A re-fetch of the same id moments later returned the real verdict. The
+  container emits `run_status_changed{status:'completed'}` and
+  `run_completed{outcome}` as separate SQS messages with no ordering
+  guarantee, and the API skips undefined fields on write, so a status-only
+  message marks the run terminal with no outcome. Polling keyed on `status`
+  alone, so it returned that intermediate row. `completed` now also requires a
+  decided verdict; `failed` and `cancelled` still settle immediately, since
+  neither carries one.
+
+### Added
+
+- `TestStepResult` and `TestRunDetails`. `testing.runs.get()` and
+  `waitForRun()` return `TestRunDetails` — the run row plus `stepResults`,
+  `fullTranscript` and an inline `config` snapshot, all of which the API has
+  always sent and neither SDK declared.
+  - Named `TestStepResult`, not `StepResult`: the latter is already exported
+    for mapping and is an unrelated shape.
+
+## [0.6.0] - 2026-08-19
+
+### Fixed
+
+- `TestRun.outcome` replaces `TestRun.result`. The API has never sent a
+  `result` field, so `run.result` read as `undefined` on every run including
+  passing ones, and the declared values (`pass`/`fail`/`partial`) did not exist.
+  The real field is `outcome`, with uppercase values
+  `PASS | FAIL | ERROR | INCONCLUSIVE | pending` — the same `TestRunOutcome`
+  the list, aggregate and mission-run types already used. Only the full
+  `TestRun` entity had drifted. The removed `TestRunResult` type described a
+  field that never existed.
+- `ProfileItem` is now the discriminated union the API actually returns, keyed
+  on `type`: `ProfileVoiceItem` (`audioId`) or `ProfileDataItem`
+  (`datasetId` + `itemId`). It was previously `{id, label, value}` with both
+  `label` and `value` required — `value` does not exist on either variant, and
+  `label` is deprecated server-side and usually absent. `openapi.yaml` had this
+  right as a `oneOf`; the SDK was the drifted surface.
+- `profiles.addItem()`, `updateItem()` and `deleteItem()` return the updated
+  `Profile`, which is what all three routes send. They were typed as returning
+  a `ProfileItem` (and `deleteItem` discarded the body entirely).
+- `AddProfileItemRequest` is a union requiring `type` plus the matching id
+  field, replacing the invented `{label, value}`. `UpdateProfileItemRequest`
+  takes `label` / `description` — the only two fields the handler reads.
+- Removed `Profile.matchedLabels`, which appears nowhere in the API.
+
+## [0.5.0] - 2026-08-18
+
+### Added
+
+- `MappingJobConfig` now carries the full configuration surface the API accepts.
+  Previously it exposed 9 of the 13 documented fields, and the four it omitted
+  included `vertical` — which the API **requires** whenever `mappingMode` is
+  `dtmf-audio` or `full-audio`. Audio mapping jobs were therefore impossible to
+  create from the SDK; only `dtmf` worked.
+  - `vertical` — `FSI | Healthcare | EnergyUtilities | Telecoms | General`.
+  - `probeMode` — security-probe flag. Rejected by the API in combination with
+    `mappingMode: 'dtmf'`.
+  - `repeatConfig` — `{ behavior, maxExplorations? }` for revisited-menu handling.
+  - `enrichmentConfig` — `{ enabled, types? }` for the post-run enrichment pipeline.
+- New exported types: `Vertical`, `RepeatBehavior`, `RepeatConfig`, `EnrichmentConfig`.
+
 ## [0.4.0] - 2026-08-12
 
 ### Added

package/dist/index.cjs

@@ -133,7 +133,7 @@ function resolveConfig(opts) {
 }
 
 // src/version.ts
-var VERSION = true ? "0.4.0" : "0.0.0-dev";
+var VERSION = true ? "0.7.0" : "0.0.0-dev";
 
 // src/userAgent.ts
 function composeUserAgent() {
@@ -1260,8 +1260,9 @@ var ProfilesResource = class extends Resource {
       requestOptions
     });
   }
+  /** Returns the updated profile, as all three item routes do. */
   async deleteItem(profileId, itemId, requestOptions) {
-    await this.transport.request(
+    return await this.transport.request(
       "DELETE",
       `/profiles/${profileId}/items/${itemId}`,
       { requestOptions }
@@ -1387,6 +1388,11 @@ var SweepsResource = class extends Resource {
 
 // src/resources/testing.ts
 var RUN_TERMINAL_STATUSES3 = /* @__PURE__ */ new Set(["completed", "failed", "cancelled"]);
+function isRunSettled(run) {
+  if (run.status === void 0 || !RUN_TERMINAL_STATUSES3.has(run.status)) return false;
+  if (run.status !== "completed") return true;
+  return run.outcome != null && run.outcome !== "pending";
+}
 var TestingConfigsResource = class extends Resource {
   async create(body, requestOptions) {
     return await this.transport.request("POST", "/testing/configs", { body, requestOptions });
@@ -1487,7 +1493,7 @@ var TestingRunsResource = class extends Resource {
   async waitForRun(runId, opts = {}) {
     return await waitFor({
       fetch: () => this.get(runId, opts.requestOptions),
-      isTerminal: (run) => run.status !== void 0 && RUN_TERMINAL_STATUSES3.has(run.status),
+      isTerminal: isRunSettled,
       timeout: opts.timeout,
       initialInterval: opts.pollInterval,
       intervalCap: opts.intervalCap,