@soat/sdk 0.109.0 → 0.110.0

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.
package/dist/index.cjs CHANGED
@@ -1106,7 +1106,7 @@ var ApiKeys = class {
1106
1106
  /**
1107
1107
  * Create an API key
1108
1108
  *
1109
- * Creates a new API key for the authenticated user. - `project_id` is optional. When set, the key is scoped to that single project. When omitted or null, the key is **unscoped** and spans every project its owner can reach. - If `policy_ids` is provided, the key's effective permissions are the intersection of the user's policies and the key's policies. - Otherwise the key inherits the user's permissions (confined to the key's project when scoped). - When the request is narrowed beyond its credential's own grant (an OAuth access token, a trigger run-as token, a run token, an IAM token, or an `On-Behalf-Of` assertion), it returns `403 CREDENTIAL_NARROWED`: a key would outlive that narrowing. - When the request is authenticated with a **project-scoped API key**, the new key is confined to that same project: omitting `project_id` defaults to it, naming a different project returns `403 API_KEY_PROJECT_SCOPE`, and `project_id: null` (an unscoped key) is likewise refused. Minting an unscoped key requires an unscoped credential. - When the request is authenticated with an **API key narrowed by `policy_ids`**, the new key stays inside that boundary: omitting `policy_ids` inherits the caller's own, a non-empty subset of them is accepted, and an empty list or any other policy returns `403 API_KEY_POLICY_BOUNDARY`.
1109
+ * Creates a new API key for the authenticated user. - `project_id` is optional. When set, the key is scoped to that single project. When omitted or null, the key is **unscoped** and spans every project its owner can reach. - If `policy_ids` is provided, the key's effective permissions are the intersection of the user's policies and the key's policies. - Otherwise the key inherits the user's permissions (confined to the key's project when scoped). - When the request is narrowed beyond its credential's own grant (an OAuth access token, an IAM token, an `On-Behalf-Of` assertion, or a call durable work makes under its stored authority), it returns `403 CREDENTIAL_NARROWED`: a key would outlive that narrowing. - When the request is authenticated with a **project-scoped API key**, the new key is confined to that same project: omitting `project_id` defaults to it, naming a different project returns `403 API_KEY_PROJECT_SCOPE`, and `project_id: null` (an unscoped key) is likewise refused. Minting an unscoped key requires an unscoped credential. - When the request is authenticated with an **API key narrowed by `policy_ids`**, the new key stays inside that boundary: omitting `policy_ids` inherits the caller's own, a non-empty subset of them is accepted, and an empty list or any other policy returns `403 API_KEY_POLICY_BOUNDARY`.
1110
1110
  *
1111
1111
  */
1112
1112
  static createApiKey(options) {
@@ -4229,7 +4229,7 @@ var Playbooks = class {
4229
4229
  /**
4230
4230
  * Run a node of a case
4231
4231
  *
4232
- * Runs one node now. The cascade already runs every node whose inputs are set once a write, a settle or a resume makes it runnable, and never reruns a `failed` or `done` one: this is how a failed node is retried, and how a `done` node is recomputed after an upgrade changed its executor. A `collect` node takes its own input values as its output, any other node starts its executor with the node's input values mapped through the executor's `input`. The executor runs as the author of the case's playbook version, whose permission to start it is checked again here (`403 PLAYBOOK_EXECUTOR_FORBIDDEN`); an author that no longer exists is `409 PLAYBOOK_AUTHOR_UNAVAILABLE`. Only a `ready`, `stale`, `failed` or `done` node with every required input set runs; anything else is `409 PLAYBOOK_NODE_NOT_RUNNABLE`. A paused case is `409 PLAYBOOK_CASE_PAUSED`, and a case in a paused project `409 PROJECT_PAUSED`.
4232
+ * Runs one node now. The cascade already runs every node whose inputs are set once a write, a settle or a resume makes it runnable, and never reruns a `failed` or `done` one: this is how a failed node is retried, and how a `done` node is recomputed after an upgrade changed its executor. A `collect` node takes its own input values as its output, any other node starts its executor with the node's input values mapped through the executor's `input`. The executor runs as the author of the case's playbook version, whose permission to start it is checked again here (`403 PLAYBOOK_EXECUTOR_FORBIDDEN`); an author that no longer exists is `409 WORK_AUTHORITY_MISSING`. Only a `ready`, `stale`, `failed` or `done` node with every required input set runs; anything else is `409 PLAYBOOK_NODE_NOT_RUNNABLE`. A paused case is `409 PLAYBOOK_CASE_PAUSED`, and a case in a paused project `409 PROJECT_PAUSED`.
4233
4233
  *
4234
4234
  * An `upstream` node has no executor: running it pulls the current output of the node it names in the bound case, which must be `done`. This is the only way to refresh one that an upstream change left `stale`.
4235
4235
  *
package/dist/index.d.cts CHANGED
@@ -462,9 +462,13 @@ type Agent = {
462
462
  [key: string]: unknown;
463
463
  }> | null;
464
464
  /**
465
- * Policies capping every generation: it runs as the caller's permissions intersected with these. Null is no cap.
465
+ * Under `run_as: caller`, the policies capping the caller's permissions on every generation; null is no cap. Under `run_as: agent`, the agent's own grant.
466
466
  */
467
467
  policy_ids?: Array<string> | null;
468
+ /**
469
+ * What `policy_ids` are. `caller`: a turn runs as the caller's permissions intersected with `policy_ids`. `agent`: a turn runs as `policy_ids` alone, and the caller needs only `agents:CreateAgentGeneration` on the agent. See [Execution Identity](/docs/modules/agents#execution-identity).
470
+ */
471
+ run_as?: 'caller' | 'agent';
468
472
  /**
469
473
  * Sampling temperature
470
474
  */
@@ -732,9 +736,13 @@ type CreateAgentRequest = {
732
736
  */
733
737
  step_rules?: Array<AgentStepRule>;
734
738
  /**
735
- * Policies capping every generation: it runs as the caller's permissions intersected with these. The caller must hold every grant they carry inside the agent's project, else `403 POLICY_GRANT_NOT_HELD`. See [Execution Identity](/docs/modules/agents#execution-identity).
739
+ * Under `run_as: caller`, the policies capping the caller's permissions on every generation; under `run_as: agent`, the agent's own grant. The caller must hold every grant they carry inside the agent's project, else `403 POLICY_GRANT_NOT_HELD`. See [Execution Identity](/docs/modules/agents#execution-identity).
736
740
  */
737
741
  policy_ids?: Array<string>;
742
+ /**
743
+ * What `policy_ids` are: `caller` (default) caps the caller, `agent` makes them the agent's own grant. `agent` requires a non-empty `policy_ids`, else `400 AGENT_RUN_AS_REQUIRES_POLICIES`.
744
+ */
745
+ run_as?: 'caller' | 'agent';
738
746
  /**
739
747
  * Sampling temperature passed to the model. Omitted, the provider's default applies.
740
748
  */
@@ -880,9 +888,13 @@ type UpdateAgentRequest = {
880
888
  */
881
889
  step_rules?: Array<AgentStepRule> | null;
882
890
  /**
883
- * Replaces the policies capping every generation; `null` removes the cap. The caller must hold every grant of each policy it adds inside the agent's project, else `403 POLICY_GRANT_NOT_HELD`. See [Execution Identity](/docs/modules/agents#execution-identity).
891
+ * Replaces `policy_ids`; `null` removes them. The caller must hold every grant of each policy it adds inside the agent's project, else `403 POLICY_GRANT_NOT_HELD`. See [Execution Identity](/docs/modules/agents#execution-identity).
884
892
  */
885
893
  policy_ids?: Array<string> | null;
894
+ /**
895
+ * Replaces what `policy_ids` are: `caller` caps the caller, `agent` makes them the agent's own grant. An agent left `run_as: agent` with no `policy_ids` is `400 AGENT_RUN_AS_REQUIRES_POLICIES`.
896
+ */
897
+ run_as?: 'caller' | 'agent';
886
898
  /**
887
899
  * Sampling temperature passed to the model; `null` restores the provider's default.
888
900
  */
@@ -3064,9 +3076,13 @@ type AgentResourceProperties = {
3064
3076
  active_tool_ids?: Array<string> | null;
3065
3077
  }> | null;
3066
3078
  /**
3067
- * Policies capping every generation. The deployer must hold every grant they carry inside the agent's project, else `403 POLICY_GRANT_NOT_HELD`.
3079
+ * Under `run_as: caller`, the policies capping the caller's permissions on every generation; under `run_as: agent`, the agent's own grant. The deployer must hold every grant they carry inside the agent's project, else `403 POLICY_GRANT_NOT_HELD`.
3068
3080
  */
3069
3081
  policy_ids?: Array<string> | null;
3082
+ /**
3083
+ * What `policy_ids` are: `caller` (default) caps the caller, `agent` makes them the agent's own grant and requires a non-empty `policy_ids`.
3084
+ */
3085
+ run_as?: 'caller' | 'agent';
3070
3086
  /**
3071
3087
  * Sampling temperature
3072
3088
  */
@@ -7671,7 +7687,7 @@ type Task = {
7671
7687
  */
7672
7688
  pause_reason?: string | null;
7673
7689
  /**
7674
- * Server-owned. How many machine-driven transitions have run back-to-back with no outside intervention — a dispatch outcome routed through `on_complete`/`on_failure`, or a `transition-task` call made by a dispatched run or agent with its run-as token. Any move by a person, a plain API key, or an approval resolution resets it to `0`. Once it would exceed the server's limit (`TASK_AUTOMATION_CHAIN_LIMIT`, default 50) the next such transition is refused with `TASK_AUTOMATION_CHAIN_LIMIT`, bounding a cycle composed across workflows and orchestrations.
7690
+ * Server-owned. How many machine-driven transitions have run back-to-back with no outside intervention — a dispatch outcome routed through `on_complete`/`on_failure`, or a `transition-task` call made by a dispatched run or agent under its stored authority. Any move by a person, a plain API key, or an approval resolution resets it to `0`. Once it would exceed the server's limit (`TASK_AUTOMATION_CHAIN_LIMIT`, default 50) the next such transition is refused with `TASK_AUTOMATION_CHAIN_LIMIT`, bounding a cycle composed across workflows and orchestrations.
7675
7691
  */
7676
7692
  automation_chain_depth?: number;
7677
7693
  /**
@@ -30926,7 +30942,7 @@ export declare class ApiKeys {
30926
30942
  /**
30927
30943
  * Create an API key
30928
30944
  *
30929
- * Creates a new API key for the authenticated user. - `project_id` is optional. When set, the key is scoped to that single project. When omitted or null, the key is **unscoped** and spans every project its owner can reach. - If `policy_ids` is provided, the key's effective permissions are the intersection of the user's policies and the key's policies. - Otherwise the key inherits the user's permissions (confined to the key's project when scoped). - When the request is narrowed beyond its credential's own grant (an OAuth access token, a trigger run-as token, a run token, an IAM token, or an `On-Behalf-Of` assertion), it returns `403 CREDENTIAL_NARROWED`: a key would outlive that narrowing. - When the request is authenticated with a **project-scoped API key**, the new key is confined to that same project: omitting `project_id` defaults to it, naming a different project returns `403 API_KEY_PROJECT_SCOPE`, and `project_id: null` (an unscoped key) is likewise refused. Minting an unscoped key requires an unscoped credential. - When the request is authenticated with an **API key narrowed by `policy_ids`**, the new key stays inside that boundary: omitting `policy_ids` inherits the caller's own, a non-empty subset of them is accepted, and an empty list or any other policy returns `403 API_KEY_POLICY_BOUNDARY`.
30945
+ * Creates a new API key for the authenticated user. - `project_id` is optional. When set, the key is scoped to that single project. When omitted or null, the key is **unscoped** and spans every project its owner can reach. - If `policy_ids` is provided, the key's effective permissions are the intersection of the user's policies and the key's policies. - Otherwise the key inherits the user's permissions (confined to the key's project when scoped). - When the request is narrowed beyond its credential's own grant (an OAuth access token, an IAM token, an `On-Behalf-Of` assertion, or a call durable work makes under its stored authority), it returns `403 CREDENTIAL_NARROWED`: a key would outlive that narrowing. - When the request is authenticated with a **project-scoped API key**, the new key is confined to that same project: omitting `project_id` defaults to it, naming a different project returns `403 API_KEY_PROJECT_SCOPE`, and `project_id: null` (an unscoped key) is likewise refused. Minting an unscoped key requires an unscoped credential. - When the request is authenticated with an **API key narrowed by `policy_ids`**, the new key stays inside that boundary: omitting `policy_ids` inherits the caller's own, a non-empty subset of them is accepted, and an empty list or any other policy returns `403 API_KEY_POLICY_BOUNDARY`.
30930
30946
  *
30931
30947
  */
30932
30948
  static createApiKey<ThrowOnError extends boolean = false>(options: Options<CreateApiKeyData, ThrowOnError>): RequestResult<CreateApiKeyResponses, CreateApiKeyErrors, ThrowOnError>;
@@ -32517,7 +32533,7 @@ export declare class Playbooks {
32517
32533
  /**
32518
32534
  * Run a node of a case
32519
32535
  *
32520
- * Runs one node now. The cascade already runs every node whose inputs are set once a write, a settle or a resume makes it runnable, and never reruns a `failed` or `done` one: this is how a failed node is retried, and how a `done` node is recomputed after an upgrade changed its executor. A `collect` node takes its own input values as its output, any other node starts its executor with the node's input values mapped through the executor's `input`. The executor runs as the author of the case's playbook version, whose permission to start it is checked again here (`403 PLAYBOOK_EXECUTOR_FORBIDDEN`); an author that no longer exists is `409 PLAYBOOK_AUTHOR_UNAVAILABLE`. Only a `ready`, `stale`, `failed` or `done` node with every required input set runs; anything else is `409 PLAYBOOK_NODE_NOT_RUNNABLE`. A paused case is `409 PLAYBOOK_CASE_PAUSED`, and a case in a paused project `409 PROJECT_PAUSED`.
32536
+ * Runs one node now. The cascade already runs every node whose inputs are set once a write, a settle or a resume makes it runnable, and never reruns a `failed` or `done` one: this is how a failed node is retried, and how a `done` node is recomputed after an upgrade changed its executor. A `collect` node takes its own input values as its output, any other node starts its executor with the node's input values mapped through the executor's `input`. The executor runs as the author of the case's playbook version, whose permission to start it is checked again here (`403 PLAYBOOK_EXECUTOR_FORBIDDEN`); an author that no longer exists is `409 WORK_AUTHORITY_MISSING`. Only a `ready`, `stale`, `failed` or `done` node with every required input set runs; anything else is `409 PLAYBOOK_NODE_NOT_RUNNABLE`. A paused case is `409 PLAYBOOK_CASE_PAUSED`, and a case in a paused project `409 PROJECT_PAUSED`.
32521
32537
  *
32522
32538
  * An `upstream` node has no executor: running it pulls the current output of the node it names in the bound case, which must be `done`. This is the only way to refresh one that an upstream change left `stale`.
32523
32539
  *
package/dist/index.d.mts CHANGED
@@ -462,9 +462,13 @@ type Agent = {
462
462
  [key: string]: unknown;
463
463
  }> | null;
464
464
  /**
465
- * Policies capping every generation: it runs as the caller's permissions intersected with these. Null is no cap.
465
+ * Under `run_as: caller`, the policies capping the caller's permissions on every generation; null is no cap. Under `run_as: agent`, the agent's own grant.
466
466
  */
467
467
  policy_ids?: Array<string> | null;
468
+ /**
469
+ * What `policy_ids` are. `caller`: a turn runs as the caller's permissions intersected with `policy_ids`. `agent`: a turn runs as `policy_ids` alone, and the caller needs only `agents:CreateAgentGeneration` on the agent. See [Execution Identity](/docs/modules/agents#execution-identity).
470
+ */
471
+ run_as?: 'caller' | 'agent';
468
472
  /**
469
473
  * Sampling temperature
470
474
  */
@@ -732,9 +736,13 @@ type CreateAgentRequest = {
732
736
  */
733
737
  step_rules?: Array<AgentStepRule>;
734
738
  /**
735
- * Policies capping every generation: it runs as the caller's permissions intersected with these. The caller must hold every grant they carry inside the agent's project, else `403 POLICY_GRANT_NOT_HELD`. See [Execution Identity](/docs/modules/agents#execution-identity).
739
+ * Under `run_as: caller`, the policies capping the caller's permissions on every generation; under `run_as: agent`, the agent's own grant. The caller must hold every grant they carry inside the agent's project, else `403 POLICY_GRANT_NOT_HELD`. See [Execution Identity](/docs/modules/agents#execution-identity).
736
740
  */
737
741
  policy_ids?: Array<string>;
742
+ /**
743
+ * What `policy_ids` are: `caller` (default) caps the caller, `agent` makes them the agent's own grant. `agent` requires a non-empty `policy_ids`, else `400 AGENT_RUN_AS_REQUIRES_POLICIES`.
744
+ */
745
+ run_as?: 'caller' | 'agent';
738
746
  /**
739
747
  * Sampling temperature passed to the model. Omitted, the provider's default applies.
740
748
  */
@@ -880,9 +888,13 @@ type UpdateAgentRequest = {
880
888
  */
881
889
  step_rules?: Array<AgentStepRule> | null;
882
890
  /**
883
- * Replaces the policies capping every generation; `null` removes the cap. The caller must hold every grant of each policy it adds inside the agent's project, else `403 POLICY_GRANT_NOT_HELD`. See [Execution Identity](/docs/modules/agents#execution-identity).
891
+ * Replaces `policy_ids`; `null` removes them. The caller must hold every grant of each policy it adds inside the agent's project, else `403 POLICY_GRANT_NOT_HELD`. See [Execution Identity](/docs/modules/agents#execution-identity).
884
892
  */
885
893
  policy_ids?: Array<string> | null;
894
+ /**
895
+ * Replaces what `policy_ids` are: `caller` caps the caller, `agent` makes them the agent's own grant. An agent left `run_as: agent` with no `policy_ids` is `400 AGENT_RUN_AS_REQUIRES_POLICIES`.
896
+ */
897
+ run_as?: 'caller' | 'agent';
886
898
  /**
887
899
  * Sampling temperature passed to the model; `null` restores the provider's default.
888
900
  */
@@ -3064,9 +3076,13 @@ type AgentResourceProperties = {
3064
3076
  active_tool_ids?: Array<string> | null;
3065
3077
  }> | null;
3066
3078
  /**
3067
- * Policies capping every generation. The deployer must hold every grant they carry inside the agent's project, else `403 POLICY_GRANT_NOT_HELD`.
3079
+ * Under `run_as: caller`, the policies capping the caller's permissions on every generation; under `run_as: agent`, the agent's own grant. The deployer must hold every grant they carry inside the agent's project, else `403 POLICY_GRANT_NOT_HELD`.
3068
3080
  */
3069
3081
  policy_ids?: Array<string> | null;
3082
+ /**
3083
+ * What `policy_ids` are: `caller` (default) caps the caller, `agent` makes them the agent's own grant and requires a non-empty `policy_ids`.
3084
+ */
3085
+ run_as?: 'caller' | 'agent';
3070
3086
  /**
3071
3087
  * Sampling temperature
3072
3088
  */
@@ -7671,7 +7687,7 @@ type Task = {
7671
7687
  */
7672
7688
  pause_reason?: string | null;
7673
7689
  /**
7674
- * Server-owned. How many machine-driven transitions have run back-to-back with no outside intervention — a dispatch outcome routed through `on_complete`/`on_failure`, or a `transition-task` call made by a dispatched run or agent with its run-as token. Any move by a person, a plain API key, or an approval resolution resets it to `0`. Once it would exceed the server's limit (`TASK_AUTOMATION_CHAIN_LIMIT`, default 50) the next such transition is refused with `TASK_AUTOMATION_CHAIN_LIMIT`, bounding a cycle composed across workflows and orchestrations.
7690
+ * Server-owned. How many machine-driven transitions have run back-to-back with no outside intervention — a dispatch outcome routed through `on_complete`/`on_failure`, or a `transition-task` call made by a dispatched run or agent under its stored authority. Any move by a person, a plain API key, or an approval resolution resets it to `0`. Once it would exceed the server's limit (`TASK_AUTOMATION_CHAIN_LIMIT`, default 50) the next such transition is refused with `TASK_AUTOMATION_CHAIN_LIMIT`, bounding a cycle composed across workflows and orchestrations.
7675
7691
  */
7676
7692
  automation_chain_depth?: number;
7677
7693
  /**
@@ -30926,7 +30942,7 @@ export declare class ApiKeys {
30926
30942
  /**
30927
30943
  * Create an API key
30928
30944
  *
30929
- * Creates a new API key for the authenticated user. - `project_id` is optional. When set, the key is scoped to that single project. When omitted or null, the key is **unscoped** and spans every project its owner can reach. - If `policy_ids` is provided, the key's effective permissions are the intersection of the user's policies and the key's policies. - Otherwise the key inherits the user's permissions (confined to the key's project when scoped). - When the request is narrowed beyond its credential's own grant (an OAuth access token, a trigger run-as token, a run token, an IAM token, or an `On-Behalf-Of` assertion), it returns `403 CREDENTIAL_NARROWED`: a key would outlive that narrowing. - When the request is authenticated with a **project-scoped API key**, the new key is confined to that same project: omitting `project_id` defaults to it, naming a different project returns `403 API_KEY_PROJECT_SCOPE`, and `project_id: null` (an unscoped key) is likewise refused. Minting an unscoped key requires an unscoped credential. - When the request is authenticated with an **API key narrowed by `policy_ids`**, the new key stays inside that boundary: omitting `policy_ids` inherits the caller's own, a non-empty subset of them is accepted, and an empty list or any other policy returns `403 API_KEY_POLICY_BOUNDARY`.
30945
+ * Creates a new API key for the authenticated user. - `project_id` is optional. When set, the key is scoped to that single project. When omitted or null, the key is **unscoped** and spans every project its owner can reach. - If `policy_ids` is provided, the key's effective permissions are the intersection of the user's policies and the key's policies. - Otherwise the key inherits the user's permissions (confined to the key's project when scoped). - When the request is narrowed beyond its credential's own grant (an OAuth access token, an IAM token, an `On-Behalf-Of` assertion, or a call durable work makes under its stored authority), it returns `403 CREDENTIAL_NARROWED`: a key would outlive that narrowing. - When the request is authenticated with a **project-scoped API key**, the new key is confined to that same project: omitting `project_id` defaults to it, naming a different project returns `403 API_KEY_PROJECT_SCOPE`, and `project_id: null` (an unscoped key) is likewise refused. Minting an unscoped key requires an unscoped credential. - When the request is authenticated with an **API key narrowed by `policy_ids`**, the new key stays inside that boundary: omitting `policy_ids` inherits the caller's own, a non-empty subset of them is accepted, and an empty list or any other policy returns `403 API_KEY_POLICY_BOUNDARY`.
30930
30946
  *
30931
30947
  */
30932
30948
  static createApiKey<ThrowOnError extends boolean = false>(options: Options<CreateApiKeyData, ThrowOnError>): RequestResult<CreateApiKeyResponses, CreateApiKeyErrors, ThrowOnError>;
@@ -32517,7 +32533,7 @@ export declare class Playbooks {
32517
32533
  /**
32518
32534
  * Run a node of a case
32519
32535
  *
32520
- * Runs one node now. The cascade already runs every node whose inputs are set once a write, a settle or a resume makes it runnable, and never reruns a `failed` or `done` one: this is how a failed node is retried, and how a `done` node is recomputed after an upgrade changed its executor. A `collect` node takes its own input values as its output, any other node starts its executor with the node's input values mapped through the executor's `input`. The executor runs as the author of the case's playbook version, whose permission to start it is checked again here (`403 PLAYBOOK_EXECUTOR_FORBIDDEN`); an author that no longer exists is `409 PLAYBOOK_AUTHOR_UNAVAILABLE`. Only a `ready`, `stale`, `failed` or `done` node with every required input set runs; anything else is `409 PLAYBOOK_NODE_NOT_RUNNABLE`. A paused case is `409 PLAYBOOK_CASE_PAUSED`, and a case in a paused project `409 PROJECT_PAUSED`.
32536
+ * Runs one node now. The cascade already runs every node whose inputs are set once a write, a settle or a resume makes it runnable, and never reruns a `failed` or `done` one: this is how a failed node is retried, and how a `done` node is recomputed after an upgrade changed its executor. A `collect` node takes its own input values as its output, any other node starts its executor with the node's input values mapped through the executor's `input`. The executor runs as the author of the case's playbook version, whose permission to start it is checked again here (`403 PLAYBOOK_EXECUTOR_FORBIDDEN`); an author that no longer exists is `409 WORK_AUTHORITY_MISSING`. Only a `ready`, `stale`, `failed` or `done` node with every required input set runs; anything else is `409 PLAYBOOK_NODE_NOT_RUNNABLE`. A paused case is `409 PLAYBOOK_CASE_PAUSED`, and a case in a paused project `409 PROJECT_PAUSED`.
32521
32537
  *
32522
32538
  * An `upstream` node has no executor: running it pulls the current output of the node it names in the bound case, which must be `done`. This is the only way to refresh one that an upstream change left `stale`.
32523
32539
  *
package/dist/index.mjs CHANGED
@@ -1105,7 +1105,7 @@ var ApiKeys = class {
1105
1105
  /**
1106
1106
  * Create an API key
1107
1107
  *
1108
- * Creates a new API key for the authenticated user. - `project_id` is optional. When set, the key is scoped to that single project. When omitted or null, the key is **unscoped** and spans every project its owner can reach. - If `policy_ids` is provided, the key's effective permissions are the intersection of the user's policies and the key's policies. - Otherwise the key inherits the user's permissions (confined to the key's project when scoped). - When the request is narrowed beyond its credential's own grant (an OAuth access token, a trigger run-as token, a run token, an IAM token, or an `On-Behalf-Of` assertion), it returns `403 CREDENTIAL_NARROWED`: a key would outlive that narrowing. - When the request is authenticated with a **project-scoped API key**, the new key is confined to that same project: omitting `project_id` defaults to it, naming a different project returns `403 API_KEY_PROJECT_SCOPE`, and `project_id: null` (an unscoped key) is likewise refused. Minting an unscoped key requires an unscoped credential. - When the request is authenticated with an **API key narrowed by `policy_ids`**, the new key stays inside that boundary: omitting `policy_ids` inherits the caller's own, a non-empty subset of them is accepted, and an empty list or any other policy returns `403 API_KEY_POLICY_BOUNDARY`.
1108
+ * Creates a new API key for the authenticated user. - `project_id` is optional. When set, the key is scoped to that single project. When omitted or null, the key is **unscoped** and spans every project its owner can reach. - If `policy_ids` is provided, the key's effective permissions are the intersection of the user's policies and the key's policies. - Otherwise the key inherits the user's permissions (confined to the key's project when scoped). - When the request is narrowed beyond its credential's own grant (an OAuth access token, an IAM token, an `On-Behalf-Of` assertion, or a call durable work makes under its stored authority), it returns `403 CREDENTIAL_NARROWED`: a key would outlive that narrowing. - When the request is authenticated with a **project-scoped API key**, the new key is confined to that same project: omitting `project_id` defaults to it, naming a different project returns `403 API_KEY_PROJECT_SCOPE`, and `project_id: null` (an unscoped key) is likewise refused. Minting an unscoped key requires an unscoped credential. - When the request is authenticated with an **API key narrowed by `policy_ids`**, the new key stays inside that boundary: omitting `policy_ids` inherits the caller's own, a non-empty subset of them is accepted, and an empty list or any other policy returns `403 API_KEY_POLICY_BOUNDARY`.
1109
1109
  *
1110
1110
  */
1111
1111
  static createApiKey(options) {
@@ -4228,7 +4228,7 @@ var Playbooks = class {
4228
4228
  /**
4229
4229
  * Run a node of a case
4230
4230
  *
4231
- * Runs one node now. The cascade already runs every node whose inputs are set once a write, a settle or a resume makes it runnable, and never reruns a `failed` or `done` one: this is how a failed node is retried, and how a `done` node is recomputed after an upgrade changed its executor. A `collect` node takes its own input values as its output, any other node starts its executor with the node's input values mapped through the executor's `input`. The executor runs as the author of the case's playbook version, whose permission to start it is checked again here (`403 PLAYBOOK_EXECUTOR_FORBIDDEN`); an author that no longer exists is `409 PLAYBOOK_AUTHOR_UNAVAILABLE`. Only a `ready`, `stale`, `failed` or `done` node with every required input set runs; anything else is `409 PLAYBOOK_NODE_NOT_RUNNABLE`. A paused case is `409 PLAYBOOK_CASE_PAUSED`, and a case in a paused project `409 PROJECT_PAUSED`.
4231
+ * Runs one node now. The cascade already runs every node whose inputs are set once a write, a settle or a resume makes it runnable, and never reruns a `failed` or `done` one: this is how a failed node is retried, and how a `done` node is recomputed after an upgrade changed its executor. A `collect` node takes its own input values as its output, any other node starts its executor with the node's input values mapped through the executor's `input`. The executor runs as the author of the case's playbook version, whose permission to start it is checked again here (`403 PLAYBOOK_EXECUTOR_FORBIDDEN`); an author that no longer exists is `409 WORK_AUTHORITY_MISSING`. Only a `ready`, `stale`, `failed` or `done` node with every required input set runs; anything else is `409 PLAYBOOK_NODE_NOT_RUNNABLE`. A paused case is `409 PLAYBOOK_CASE_PAUSED`, and a case in a paused project `409 PROJECT_PAUSED`.
4232
4232
  *
4233
4233
  * An `upstream` node has no executor: running it pulls the current output of the node it names in the bound case, which must be `done`. This is the only way to refresh one that an upstream change left `stale`.
4234
4234
  *
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@soat/sdk",
3
- "version": "0.109.0",
3
+ "version": "0.110.0",
4
4
  "description": "TypeScript SDK for SOAT — open-source infrastructure for production-ready AI agents.",
5
5
  "keywords": [
6
6
  "ai-agents",