@naturali/sdk 0.36.1 → 0.37.0

package/dist/index.d.cts

@@ -633,7 +633,7 @@ type BoardOnEnter = {
   on_complete?: Array<BoardCompletionRule>;
   /**
    * Where a card goes when the dispatch fails terminally. Accepts either a declared move, or a column reachable from this one by exactly one declared move (which is resolved to that move — reads report the move name). Omit to leave a failed card in place for a person.
-   * **Known limitation — does not fire for a `tool` column.** The platform underneath reports a failed tool run as a *completed* dispatch, so a tool column's `on_failure` is never reached and its `on_complete` rules are evaluated instead, against the failed run's partial state. A catch-all `{"when": true}` rule on a tool column will therefore fire on failed work — including into a terminal column, which closes the card. Until this is fixed upstream, prefer an explicit rule that tests a field the tool really returns, so a failed run matches nothing and the card parks for a person. Agent columns are unaffected.
+   * Fires for both kinds of column. A failed dispatch never reaches `on_complete`, so a catch-all `{"when": true}` rule cannot advance a card on failed work, and the failure leaves no `last_result` behind.
    *
    */
   on_failure?: string | null;
@@ -1896,16 +1896,12 @@ type TaskTransitionRecord = {
    */
   transition: string | null;
   /**
-   * What kind of actor made the move. `automation` is a column's own `on_complete` routing or its `on_failure`.
+   * What kind of principal made the move. `automation` is a column's own `on_complete` routing or its `on_failure`.
    * A move made through this API reports `api_key`: every call naturali makes reaches the platform under one service credential, so the record cannot distinguish a person from an integration. `user` is reserved for when it can.
+   * There is no `principal_id` counterpart. For a human or API move it would identify naturali's own service credential, which says nothing about the caller; for an `automation` move what caused the move is already reported by `generation_id` / `orchestration_run_id`.
    *
    */
-  actor_kind: 'user' | 'api_key' | 'automation';
-  /**
-   * For an `automation` move, what caused it (the generation or run). Null otherwise — for a human or API move the underlying value identifies naturali's own service credential, which says nothing about the caller.
-   *
-   */
-  actor_id: string | null;
+  principal_kind: 'user' | 'api_key' | 'automation';
   /**
    * The agent generation that caused the move, when one did.
    */

package/dist/index.d.mts

@@ -633,7 +633,7 @@ type BoardOnEnter = {
   on_complete?: Array<BoardCompletionRule>;
   /**
    * Where a card goes when the dispatch fails terminally. Accepts either a declared move, or a column reachable from this one by exactly one declared move (which is resolved to that move — reads report the move name). Omit to leave a failed card in place for a person.
-   * **Known limitation — does not fire for a `tool` column.** The platform underneath reports a failed tool run as a *completed* dispatch, so a tool column's `on_failure` is never reached and its `on_complete` rules are evaluated instead, against the failed run's partial state. A catch-all `{"when": true}` rule on a tool column will therefore fire on failed work — including into a terminal column, which closes the card. Until this is fixed upstream, prefer an explicit rule that tests a field the tool really returns, so a failed run matches nothing and the card parks for a person. Agent columns are unaffected.
+   * Fires for both kinds of column. A failed dispatch never reaches `on_complete`, so a catch-all `{"when": true}` rule cannot advance a card on failed work, and the failure leaves no `last_result` behind.
    *
    */
   on_failure?: string | null;
@@ -1896,16 +1896,12 @@ type TaskTransitionRecord = {
    */
   transition: string | null;
   /**
-   * What kind of actor made the move. `automation` is a column's own `on_complete` routing or its `on_failure`.
+   * What kind of principal made the move. `automation` is a column's own `on_complete` routing or its `on_failure`.
    * A move made through this API reports `api_key`: every call naturali makes reaches the platform under one service credential, so the record cannot distinguish a person from an integration. `user` is reserved for when it can.
+   * There is no `principal_id` counterpart. For a human or API move it would identify naturali's own service credential, which says nothing about the caller; for an `automation` move what caused the move is already reported by `generation_id` / `orchestration_run_id`.
    *
    */
-  actor_kind: 'user' | 'api_key' | 'automation';
-  /**
-   * For an `automation` move, what caused it (the generation or run). Null otherwise — for a human or API move the underlying value identifies naturali's own service credential, which says nothing about the caller.
-   *
-   */
-  actor_id: string | null;
+  principal_kind: 'user' | 'api_key' | 'automation';
   /**
    * The agent generation that caused the move, when one did.
    */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@naturali/sdk",
-  "version": "0.36.1",
+  "version": "0.37.0",
   "description": "TypeScript SDK for the naturali.ai API, generated from its OpenAPI specs",
   "type": "module",
   "sideEffects": false,
@@ -37,7 +37,7 @@
     "tsx": "^4.23.1",
     "typescript": "~6.0.3",
     "vitest": "^4.1.10",
-    "@naturali/api": "0.36.1"
+    "@naturali/api": "0.37.0"
   },
   "scripts": {
     "generate": "tsx scripts/generate.ts",