@avallon-labs/sdk 56.0.0 → 57.0.0-staging.1288

package/dist/index.d.ts

@@ -3312,6 +3312,9 @@ type ScheduleAction = {
     scope?: {
         [key: string]: string | number | boolean | null;
     } | null;
+} | {
+    type: "execute_tool";
+    tool_id: string;
 };
 
 /**
@@ -3372,7 +3375,7 @@ type ScheduleRule = {
 type CreateScheduleBody = {
     action: ScheduleAction;
     rule: ScheduleRule;
-    /** Environments the schedule fires in. `live` resolves the worker at its live version, `test` at its test version. Listing both fires every occurrence twice, once per version. */
+    /** Environments the schedule fires in. `live` resolves the worker or tool at its live version, `test` at its test version. Listing both fires every occurrence twice, once per version. */
     environments?: CreateScheduleBodyEnvironmentsItem[];
     /**
      * Human-readable name, e.g. "Nightly claim sweep"
@@ -3400,6 +3403,9 @@ type ScheduleActionOutput = {
     scope?: {
         [key: string]: string | number | boolean | null;
     } | null;
+} | {
+    type: "execute_tool";
+    tool_id: string;
 };
 
 /**
@@ -5170,6 +5176,7 @@ type DispatchTargetType = (typeof DispatchTargetType)[keyof typeof DispatchTarge
 declare const DispatchTargetType: {
     readonly worker_run: "worker_run";
     readonly extractor_job: "extractor_job";
+    readonly tool_call: "tool_call";
 };
 
 /**
@@ -13427,7 +13434,7 @@ declare const UpdateScheduleBodyEnvironmentsItem: {
 
 type UpdateScheduleBody = {
     rule?: ScheduleRule;
-    /** Environments the schedule fires in. `live` resolves the worker at its live version, `test` at its test version. Listing both fires every occurrence twice, once per version. */
+    /** Environments the schedule fires in. `live` resolves the worker or tool at its live version, `test` at its test version. Listing both fires every occurrence twice, once per version. */
     environments?: UpdateScheduleBodyEnvironmentsItem[];
     /** Human-readable name. Send null to clear it. */
     name?: string | null;
@@ -16368,7 +16375,7 @@ declare const getListDispatchesUrl: (params?: ListDispatchesParams) => string;
  *
  * `attempts` counts how many times the occurrence has been picked up, not how many times it failed: a dispatch carried out on the first pickup ends at `attempts: 1`, and a higher count means earlier pickups did not complete.
  *
- * `target` is what the occurrence produced — a worker run, or an extractor job for an email whose inbox extracts or a call whose voice agent extracts. It is null until the dispatch is carried out.
+ * `target` is what the occurrence produced: a worker run, an extractor job (for an email whose inbox extracts or a call whose voice agent extracts), or a tool call (for an `execute_tool` schedule). It is null until the dispatch is carried out, and for a tool call until the tool has run.
  *
  * Narrow to one trigger with `trigger_type` and `trigger_id` — the schedule's ID for a schedule, the email's ID for an email, the request's ID for an information request, the call's ID for a call. `trigger_id` requires `trigger_type`.
  * @summary List dispatches
@@ -17610,13 +17617,13 @@ declare const getCreateScheduleUrl: () => string;
 /**
  * Create a schedule that performs an action, either repeatedly or once.
  *
- * `action` describes **what** happens — today only `trigger_worker`, which starts a worker run with the given scope. `rule` describes **when**: `recurring` carries one or more `patterns`, and fires whenever any of them comes round. A pattern fires every hour at `minute`, narrowed by `hours` and `weekdays` — so `hours: [9]` is daily at 09:00, `hours: [12], weekdays: [1]` is Mondays at noon, and `hours: [9, 13, 17], weekdays: [1, 2, 3, 4, 5]` is three times a day on weekdays. Give a second pattern to mix cadences: hourly on weekdays plus 09:00, 11:00 and 18:00 at weekends is two patterns on one schedule. Patterns overlap harmlessly — two that land on the same minute fire once. Every set is read in the schedule's own time zone — an IANA identifier such as `America/Chicago`, resolved across DST transitions. `once` fires a single time at a UTC instant.
+ * `action` describes **what** happens: `trigger_worker` starts a worker run with the given scope, and `execute_tool` executes a tool without parameters. `rule` describes **when**: `recurring` carries one or more `patterns`, and fires whenever any of them comes round. A pattern fires every hour at `minute`, narrowed by `hours` and `weekdays` — so `hours: [9]` is daily at 09:00, `hours: [12], weekdays: [1]` is Mondays at noon, and `hours: [9, 13, 17], weekdays: [1, 2, 3, 4, 5]` is three times a day on weekdays. Give a second pattern to mix cadences: hourly on weekdays plus 09:00, 11:00 and 18:00 at weekends is two patterns on one schedule. Patterns overlap harmlessly — two that land on the same minute fire once. Every set is read in the schedule's own time zone — an IANA identifier such as `America/Chicago`, resolved across DST transitions. `once` fires a single time at a UTC instant.
  *
- * `environments` says **which worker version** each occurrence runs: `live` resolves the worker at its live version, `test` at its test version. Give both to soak a candidate version on the same cadence and scope as production — every occurrence then fires twice, producing one run per environment. Omit it to fire in `live` only.
+ * `environments` says **which version** of the worker or tool each occurrence runs: `live` resolves it at its live version, `test` at its test version. Give both to soak a candidate version on the same cadence as production — every occurrence then fires twice, once per environment. Omit it to fire in `live` only.
  *
  * The response's `next_run_at` is the first occurrence strictly after the moment of creation; a rule that resolves to no such occurrence is rejected. Create with `enabled: false` to stage a recurring schedule without letting it fire. A one-off is always enabled: delete it to cancel it, and its `next_run_at` becomes null once it has fired.
  *
- * Requires the `schedules:write` permission.
+ * Requires the `schedules:write` permission, and `tools:execute` for an `execute_tool` action.
  * @summary Create a schedule
  */
 declare const createSchedule: (createScheduleBody?: CreateScheduleBody, options?: Parameters<typeof customFetch>[1]) => Promise<CreateScheduleEnvelope>;

package/dist/index.js

@@ -6810,7 +6810,8 @@ var DispatchStatus = {
 // generated/models/dispatchTargetType.ts
 var DispatchTargetType = {
   worker_run: "worker_run",
-  extractor_job: "extractor_job"
+  extractor_job: "extractor_job",
+  tool_call: "tool_call"
 };
 
 // generated/models/dispatchTriggerType.ts