@naturali/cli 0.78.3 → 0.78.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/dist/index.mjs +23 -5
  2. package/package.json +2 -2
package/dist/index.mjs CHANGED
@@ -14,7 +14,7 @@ var __exportAll = (all, no_symbols) => {
14
14
  };
15
15
  //#endregion
16
16
  //#region package.json
17
- var version = "0.78.3";
17
+ var version = "0.78.4";
18
18
  //#endregion
19
19
  //#region ../sdk/src/generated/core/bodySerializer.gen.ts
20
20
  const serializeFormDataPair = (data, key, value) => {
@@ -2483,7 +2483,9 @@ var Generations = class {
2483
2483
  /**
2484
2484
  * List generations
2485
2485
  *
2486
- * Returns generations the caller can access, optionally filtered by agent, trace, and status. Replaces the former per-trace generations endpoint (use the trace_id query filter).
2486
+ * Returns generations the caller can access, optionally filtered by agent, trace, orchestration run, node, and status. Replaces the former per-trace generations endpoint (use the trace_id query filter).
2487
+ *
2488
+ * Filtering by `orchestration_run_id` is the supported way to get from an orchestration run to the generations its agent nodes produced: a node execution record carries no generation id, so the pointer lives here, alongside the run's other attribution columns.
2487
2489
  *
2488
2490
  */
2489
2491
  static listGenerations(options) {
@@ -2525,7 +2527,7 @@ var Generations = class {
2525
2527
  *
2526
2528
  * Clears the generation's content — `metadata`, `error`, `extraction`, and the internal recovery state of a paused run — and stamps `content_redacted_at`.
2527
2529
  *
2528
- * The usage and audit skeleton is preserved: ids, timestamps, status, stop reason, and the attribution fields (`action_id`, `trigger_id`, `orchestration_run_id`, `node_id`, `agent_version`, `routing`) the billing ledger reads. A purged generation reads back as that skeleton, not a 404.
2530
+ * The usage and audit skeleton is preserved: ids, timestamps, status, stop reason, and the attribution fields (`action_id`, `trigger_id`, `orchestration_run_id`, `node_id`, `node_attempt`, `agent_version`, `routing`) the billing ledger reads. A purged generation reads back as that skeleton, not a 404.
2529
2531
  *
2530
2532
  * This does **not** delete the parent trace's steps object, which holds this generation's content alongside its siblings'. To erase the run's content completely, purge the trace (`DELETE /v1/projects/{project_id}/traces/{trace_id}/content`), which cascades here.
2531
2533
  *
@@ -10101,7 +10103,7 @@ const routes = {
10101
10103
  "list-generations": {
10102
10104
  serviceClass: "Generations",
10103
10105
  operationId: "listGenerations",
10104
- description: "Returns generations the caller can access, optionally filtered by agent, trace, and status. Replaces the former per-trace generations endpoint (use the trace_id query filter).",
10106
+ description: "Returns generations the caller can access, optionally filtered by agent, trace, orchestration run, node, and status. Replaces the former per-trace generations endpoint (use the trace_id query filter). Filtering by `orchestration_run_id` is the supported way to get from an orchestration run to the generations its agent nodes produced: a node execution record carries no generation id, so the pointer lives here, alongside the run's other attribution columns.",
10105
10107
  moduleDocsUrl: "https://docs.naturali.ai/docs/modules/generations",
10106
10108
  httpMethod: "get",
10107
10109
  pathParams: ["project_id"],
@@ -10109,6 +10111,8 @@ const routes = {
10109
10111
  "agent_id",
10110
10112
  "trace_id",
10111
10113
  "initiator_generation_id",
10114
+ "orchestration_run_id",
10115
+ "node_id",
10112
10116
  "status",
10113
10117
  "limit",
10114
10118
  "offset"
@@ -10142,6 +10146,20 @@ const routes = {
10142
10146
  "type": "string",
10143
10147
  "in": "query"
10144
10148
  },
10149
+ {
10150
+ "name": "orchestration_run_id",
10151
+ "description": "Filter by the orchestration run that dispatched the generation. This is how a run is traced back to what its agent nodes did — a node execution record stores no generation id.\n",
10152
+ "required": false,
10153
+ "type": "string",
10154
+ "in": "query"
10155
+ },
10156
+ {
10157
+ "name": "node_id",
10158
+ "description": "Filter by the orchestration node that dispatched the generation. Combine with `orchestration_run_id` to narrow to one node of one run; a retried node returns one generation per `node_attempt`.\n",
10159
+ "required": false,
10160
+ "type": "string",
10161
+ "in": "query"
10162
+ },
10145
10163
  {
10146
10164
  "name": "status",
10147
10165
  "description": "Filter by lifecycle status",
@@ -10222,7 +10240,7 @@ const routes = {
10222
10240
  "purge-generation-content": {
10223
10241
  serviceClass: "Generations",
10224
10242
  operationId: "purgeGenerationContent",
10225
- description: "Clears the generation's content — `metadata`, `error`, `extraction`, and the internal recovery state of a paused run — and stamps `content_redacted_at`. The usage and audit skeleton is preserved: ids, timestamps, status, stop reason, and the attribution fields (`action_id`, `trigger_id`, `orchestration_run_id`, `node_id`, `agent_version`, `routing`) the billing ledger reads. A purged generation reads back as that skeleton, not a 404. This does **not** delete the parent trace's steps object, which holds this generation's content alongside its siblings'. To erase the run's content completely, purge the trace (`DELETE /v1/projects/{project_id}/traces/{trace_id}/content`), which cascades here. Idempotent — purging an already-purged generation succeeds and leaves the original `content_redacted_at` in place.",
10243
+ description: "Clears the generation's content — `metadata`, `error`, `extraction`, and the internal recovery state of a paused run — and stamps `content_redacted_at`. The usage and audit skeleton is preserved: ids, timestamps, status, stop reason, and the attribution fields (`action_id`, `trigger_id`, `orchestration_run_id`, `node_id`, `node_attempt`, `agent_version`, `routing`) the billing ledger reads. A purged generation reads back as that skeleton, not a 404. This does **not** delete the parent trace's steps object, which holds this generation's content alongside its siblings'. To erase the run's content completely, purge the trace (`DELETE /v1/projects/{project_id}/traces/{trace_id}/content`), which cascades here. Idempotent — purging an already-purged generation succeeds and leaves the original `content_redacted_at` in place.",
10226
10244
  moduleDocsUrl: "https://docs.naturali.ai/docs/modules/generations",
10227
10245
  httpMethod: "delete",
10228
10246
  pathParams: ["project_id", "generation_id"],
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@naturali/cli",
3
- "version": "0.78.3",
3
+ "version": "0.78.4",
4
4
  "description": "Command-line interface for the naturali.ai API, generated from its OpenAPI specs",
5
5
  "type": "module",
6
6
  "bin": {
@@ -30,7 +30,7 @@
30
30
  "tsx": "^4.23.1",
31
31
  "typescript": "~6.0.3",
32
32
  "vitest": "^4.1.10",
33
- "@naturali/sdk": "0.78.3"
33
+ "@naturali/sdk": "0.78.4"
34
34
  },
35
35
  "scripts": {
36
36
  "generate": "tsx scripts/generate.ts",