@stackbone/sdk 0.1.0-alpha.7 → 0.1.0-alpha.8

package/workflow.d.cts

@@ -1,7 +1,7 @@
 export { defineHook, sleep } from 'workflow';
 import { Client } from 'eve/client';
-import { A as AgentName, W as WorkflowTriggerOptions, a as WorkflowStartHandle, S as ScheduledWorkflow } from './workflow-scheduler-DXCNKDOS.cjs';
-export { b as AgentRegistry } from './workflow-scheduler-DXCNKDOS.cjs';
+import { A as AgentName, S as ScheduledWorkflow, W as WorkflowName } from './agent-registry-BNXuj88Q.cjs';
+export { a as AgentRegistry, b as StartWorkflowAndWaitOptions, c as StartWorkflowOptions, d as WorkflowRegistry, e as WorkflowStartHandle, s as startWorkflow, f as startWorkflowAndWait } from './agent-registry-BNXuj88Q.cjs';
 import { RagIngestOutput } from '@stackbone/rag-core';
 export { RagIngestInput, RagIngestOutput } from '@stackbone/rag-core';
 export { C as CallConnectorOptions, a as ConnectionAccessor, b as ConnectorCallError, c as ConnectorHandle, P as Principal, S as StackboneConnections, d as callConnector, e as connection } from './call-connector-CYDw_yG5.cjs';
@@ -71,85 +71,6 @@ declare function requestApproval<TPayload = unknown>(options: RequestApprovalOpt
  */
 declare function eveAgent(name: AgentName): Client;
 
-/**
- * Augmentable registry of the workspace's WORKFLOW names. By default it is empty,
- * so `startWorkflow(name, ...)` / `startWorkflowAndWait(name, ...)` accept any
- * `string` (today's behavior, validated only at runtime against the injected
- * name→ref registry). `stackbone dev` generates an ambient
- * `.stackbone/workflows.d.ts` from the project's `stackbone.config.ts` workflow
- * list and augments this interface so the names become a closed set:
- *
- *   declare module '@stackbone/sdk/workflow' {
- *     interface WorkflowRegistry {
- *       onboarding: true;
- *       qualifyLead: true;
- *     }
- *   }
- *
- * Once augmented, `startWorkflow('qualifyLead', ...)` is fine and
- * `startWorkflow('typo', ...)` is a compile error — the editor also autocompletes
- * the declared names. Mirrors the `AgentRegistry` augmentable-interface pattern
- * used for `eveAgent`.
- */
-interface WorkflowRegistry {
-}
-/**
- * The set of workflow names the trigger helpers accept, derived from the
- * augmentable `WorkflowRegistry`. The tuple wrap (`[X] extends [never]`) defeats
- * the conditional-type distributivity a bare `keyof WorkflowRegistry extends
- * never` would trigger:
- *
- * - empty registry  -> `string` (today's loose behavior: any name, checked at
- *   runtime when the workflow resolves it against the manifest);
- * - augmented registry -> the union of declared workflow names (typo = compile error).
- */
-type WorkflowName = [keyof WorkflowRegistry] extends [never] ? string : keyof WorkflowRegistry;
-
-/** Options for {@link startWorkflow}. See {@link WorkflowTriggerOptions}. */
-type StartWorkflowOptions = WorkflowTriggerOptions;
-
-/**
- * Start the workflow named `name` with its own independent run and return its
- * `{ runId }` immediately — fire-and-forget. The input is validated against the
- * target's declared input schema BEFORE the run is enqueued; a name that does
- * not resolve, or input that violates the schema, rejects without starting
- * anything.
- *
- * `name` is typed `WorkflowName` — a loose `string` by default, narrowed to the
- * workspace's declared workflow names once `stackbone dev` has generated
- * `.stackbone/workflows.d.ts` (see `workflow-registry.ts`), so a typo becomes a
- * compile error.
- *
- * MUST be called from inside a running workflow (the runtime binds the starter on
- * first dispatch); calling it elsewhere throws.
- *
- * DURABILITY: the enqueue runs in a `"use step"`, so once it completes a parent
- * restart resumes with the memoized `{ runId }` and does NOT re-enqueue. A crash
- * WHILE the step is mid-flight re-runs it (at-least-once) — the same shape the
- * eve-agent-from-step path has; for fire-and-forget fan-out this is acceptable.
- * Use {@link startWorkflowAndWait} when you need the child's result.
- */
-declare function startWorkflow(name: WorkflowName, input: unknown, opts?: StartWorkflowOptions): Promise<WorkflowStartHandle>;
-
-/** Options for {@link startWorkflowAndWait}. See {@link WorkflowTriggerOptions}. */
-type StartWorkflowAndWaitOptions = WorkflowTriggerOptions;
-/**
- * Start the workflow named `name` with its own independent run and durably wait
- * for it to finish, returning its terminal output (validated against the
- * target's declared output schema). Use this when one workflow needs another's
- * result to continue.
- *
- * The input is validated against the target's declared input schema BEFORE the
- * run is enqueued; a name that does not resolve, or input that violates the
- * schema, rejects without starting anything. `TOutput` lets the caller name the
- * expected output shape (defaults to `unknown`).
- *
- * `name` is typed `WorkflowName` — narrowed to the workspace's declared workflow
- * names once `stackbone dev` has generated `.stackbone/workflows.d.ts`. MUST be
- * called from inside a running workflow.
- */
-declare function startWorkflowAndWait<TOutput = unknown>(name: WorkflowName, input: unknown, opts?: StartWorkflowAndWaitOptions): Promise<TOutput>;
-
 /** Content the helper stages on the caller's behalf (text or raw bytes). */
 type IngestContent = string | Uint8Array;
 /** The two input shapes {@link ingestDocuments} accepts. */
@@ -204,4 +125,4 @@ declare function unschedule(name: WorkflowName): Promise<void>;
  */
 declare function listSchedules(): Promise<ScheduledWorkflow[]>;
 
-export { type ApprovalDecision, type ApprovalFallback, type IngestContent, type IngestDocumentsArgs, type IngestDocumentsOptions, type RequestApprovalOptions, ScheduledWorkflow, type StartWorkflowAndWaitOptions, type StartWorkflowOptions, WORKFLOW_HOOK_RESUME_KIND, type WorkflowName, type WorkflowRegistry, WorkflowStartHandle, eveAgent, ingestDocuments, listSchedules, requestApproval, scheduleWorkflow, startWorkflow, startWorkflowAndWait, unschedule };
+export { type ApprovalDecision, type ApprovalFallback, type IngestContent, type IngestDocumentsArgs, type IngestDocumentsOptions, type RequestApprovalOptions, ScheduledWorkflow, WORKFLOW_HOOK_RESUME_KIND, WorkflowName, eveAgent, ingestDocuments, listSchedules, requestApproval, scheduleWorkflow, unschedule };

package/workflow.d.ts

@@ -1,7 +1,7 @@
 export { defineHook, sleep } from 'workflow';
 import { Client } from 'eve/client';
-import { A as AgentName, W as WorkflowTriggerOptions, a as WorkflowStartHandle, S as ScheduledWorkflow } from './workflow-scheduler-DXCNKDOS.js';
-export { b as AgentRegistry } from './workflow-scheduler-DXCNKDOS.js';
+import { A as AgentName, S as ScheduledWorkflow, W as WorkflowName } from './agent-registry-BNXuj88Q.js';
+export { a as AgentRegistry, b as StartWorkflowAndWaitOptions, c as StartWorkflowOptions, d as WorkflowRegistry, e as WorkflowStartHandle, s as startWorkflow, f as startWorkflowAndWait } from './agent-registry-BNXuj88Q.js';
 import { RagIngestOutput } from '@stackbone/rag-core';
 export { RagIngestInput, RagIngestOutput } from '@stackbone/rag-core';
 export { C as CallConnectorOptions, a as ConnectionAccessor, b as ConnectorCallError, c as ConnectorHandle, P as Principal, S as StackboneConnections, d as callConnector, e as connection } from './call-connector-CYDw_yG5.js';
@@ -71,85 +71,6 @@ declare function requestApproval<TPayload = unknown>(options: RequestApprovalOpt
  */
 declare function eveAgent(name: AgentName): Client;
 
-/**
- * Augmentable registry of the workspace's WORKFLOW names. By default it is empty,
- * so `startWorkflow(name, ...)` / `startWorkflowAndWait(name, ...)` accept any
- * `string` (today's behavior, validated only at runtime against the injected
- * name→ref registry). `stackbone dev` generates an ambient
- * `.stackbone/workflows.d.ts` from the project's `stackbone.config.ts` workflow
- * list and augments this interface so the names become a closed set:
- *
- *   declare module '@stackbone/sdk/workflow' {
- *     interface WorkflowRegistry {
- *       onboarding: true;
- *       qualifyLead: true;
- *     }
- *   }
- *
- * Once augmented, `startWorkflow('qualifyLead', ...)` is fine and
- * `startWorkflow('typo', ...)` is a compile error — the editor also autocompletes
- * the declared names. Mirrors the `AgentRegistry` augmentable-interface pattern
- * used for `eveAgent`.
- */
-interface WorkflowRegistry {
-}
-/**
- * The set of workflow names the trigger helpers accept, derived from the
- * augmentable `WorkflowRegistry`. The tuple wrap (`[X] extends [never]`) defeats
- * the conditional-type distributivity a bare `keyof WorkflowRegistry extends
- * never` would trigger:
- *
- * - empty registry  -> `string` (today's loose behavior: any name, checked at
- *   runtime when the workflow resolves it against the manifest);
- * - augmented registry -> the union of declared workflow names (typo = compile error).
- */
-type WorkflowName = [keyof WorkflowRegistry] extends [never] ? string : keyof WorkflowRegistry;
-
-/** Options for {@link startWorkflow}. See {@link WorkflowTriggerOptions}. */
-type StartWorkflowOptions = WorkflowTriggerOptions;
-
-/**
- * Start the workflow named `name` with its own independent run and return its
- * `{ runId }` immediately — fire-and-forget. The input is validated against the
- * target's declared input schema BEFORE the run is enqueued; a name that does
- * not resolve, or input that violates the schema, rejects without starting
- * anything.
- *
- * `name` is typed `WorkflowName` — a loose `string` by default, narrowed to the
- * workspace's declared workflow names once `stackbone dev` has generated
- * `.stackbone/workflows.d.ts` (see `workflow-registry.ts`), so a typo becomes a
- * compile error.
- *
- * MUST be called from inside a running workflow (the runtime binds the starter on
- * first dispatch); calling it elsewhere throws.
- *
- * DURABILITY: the enqueue runs in a `"use step"`, so once it completes a parent
- * restart resumes with the memoized `{ runId }` and does NOT re-enqueue. A crash
- * WHILE the step is mid-flight re-runs it (at-least-once) — the same shape the
- * eve-agent-from-step path has; for fire-and-forget fan-out this is acceptable.
- * Use {@link startWorkflowAndWait} when you need the child's result.
- */
-declare function startWorkflow(name: WorkflowName, input: unknown, opts?: StartWorkflowOptions): Promise<WorkflowStartHandle>;
-
-/** Options for {@link startWorkflowAndWait}. See {@link WorkflowTriggerOptions}. */
-type StartWorkflowAndWaitOptions = WorkflowTriggerOptions;
-/**
- * Start the workflow named `name` with its own independent run and durably wait
- * for it to finish, returning its terminal output (validated against the
- * target's declared output schema). Use this when one workflow needs another's
- * result to continue.
- *
- * The input is validated against the target's declared input schema BEFORE the
- * run is enqueued; a name that does not resolve, or input that violates the
- * schema, rejects without starting anything. `TOutput` lets the caller name the
- * expected output shape (defaults to `unknown`).
- *
- * `name` is typed `WorkflowName` — narrowed to the workspace's declared workflow
- * names once `stackbone dev` has generated `.stackbone/workflows.d.ts`. MUST be
- * called from inside a running workflow.
- */
-declare function startWorkflowAndWait<TOutput = unknown>(name: WorkflowName, input: unknown, opts?: StartWorkflowAndWaitOptions): Promise<TOutput>;
-
 /** Content the helper stages on the caller's behalf (text or raw bytes). */
 type IngestContent = string | Uint8Array;
 /** The two input shapes {@link ingestDocuments} accepts. */
@@ -204,4 +125,4 @@ declare function unschedule(name: WorkflowName): Promise<void>;
  */
 declare function listSchedules(): Promise<ScheduledWorkflow[]>;
 
-export { type ApprovalDecision, type ApprovalFallback, type IngestContent, type IngestDocumentsArgs, type IngestDocumentsOptions, type RequestApprovalOptions, ScheduledWorkflow, type StartWorkflowAndWaitOptions, type StartWorkflowOptions, WORKFLOW_HOOK_RESUME_KIND, type WorkflowName, type WorkflowRegistry, WorkflowStartHandle, eveAgent, ingestDocuments, listSchedules, requestApproval, scheduleWorkflow, startWorkflow, startWorkflowAndWait, unschedule };
+export { type ApprovalDecision, type ApprovalFallback, type IngestContent, type IngestDocumentsArgs, type IngestDocumentsOptions, type RequestApprovalOptions, ScheduledWorkflow, WORKFLOW_HOOK_RESUME_KIND, WorkflowName, eveAgent, ingestDocuments, listSchedules, requestApproval, scheduleWorkflow, unschedule };

package/workflow.js

@@ -16047,6 +16047,55 @@ var SecretsFacade = class {
     }
   }
 };
+function getWorkflowScheduler() {
+  {
+    throw new Error("No workflow scheduler is bound. `scheduleWorkflow` / `unschedule` / `listSchedules` can only be called inside a running workflow runtime \u2014 the runtime binds the scheduler on its first dispatch.");
+  }
+}
+__name(getWorkflowScheduler, "getWorkflowScheduler");
+
+// src/surfaces/agent-local/workflows/schedule-workflow.ts
+async function scheduleWorkflow(name, input, cron) {
+  return getWorkflowScheduler().schedule(name, input, cron);
+}
+__name(scheduleWorkflow, "scheduleWorkflow");
+async function unschedule(name) {
+  return getWorkflowScheduler().unschedule(name);
+}
+__name(unschedule, "unschedule");
+async function listSchedules() {
+  return getWorkflowScheduler().listSchedules();
+}
+__name(listSchedules, "listSchedules");
+function getWorkflowStarter() {
+  {
+    throw new Error("No workflow starter is bound. `startWorkflow` / `startWorkflowAndWait` can only be called from inside a running workflow \u2014 the runtime binds the starter on its first dispatch.");
+  }
+}
+__name(getWorkflowStarter, "getWorkflowStarter");
+
+// src/surfaces/agent-local/workflows/start-workflow.ts
+async function startWorkflow(name, input, opts) {
+  "use step";
+  return getWorkflowStarter().start(name, input, opts);
+}
+__name(startWorkflow, "startWorkflow");
+
+// src/surfaces/agent-local/workflows/start-workflow-and-wait.ts
+async function startWorkflowAndWait(name, input, opts) {
+  "use step";
+  return await getWorkflowStarter().startAndWait(name, input, opts);
+}
+__name(startWorkflowAndWait, "startWorkflowAndWait");
+
+// src/surfaces/agent-local/workflows/workflows-accessor.ts
+var workflows = {
+  start: startWorkflow,
+  startAndWait: startWorkflowAndWait,
+  schedule: scheduleWorkflow,
+  unschedule,
+  listSchedules
+};
 function agentRegistry() {
   const raw = process.env["AGENT_URLS"];
   if (!raw) {
@@ -17176,6 +17225,24 @@ var StackboneClient = class {
     return agent;
   }
   /**
+  * Namespaced workflow trigger + schedule surface — `stackbone.workflows.start(...)`
+  * / `.startAndWait(...)` / `.schedule(...)` / `.unschedule(...)` / `.listSchedules()`.
+  * Start another workflow by name (fire-and-forget or durable sub-routine) and
+  * manage dynamic cron triggers, all from inside a running workflow.
+  *
+  * These are peer-free shims over the ambient `WorkflowStarter` / `WorkflowScheduler`
+  * the runtime injects on first dispatch — they import NO `workflow` / `eve` peer,
+  * so (like `connection` / `agent`) they are wired directly onto the client and
+  * pull nothing new into the main barrel. This is the namespaced form of the loose
+  * `startWorkflow(...)` / `scheduleWorkflow(...)` exports (now `@deprecated`) on the
+  * `@stackbone/sdk/workflow` subpath; both delegate to the same implementation, so
+  * `start` / `startAndWait` keep their `"use step"` durability. The peer-bound
+  * authoring API (`requestApproval` / `defineHook` / `sleep`) stays on that subpath.
+  */
+  get workflows() {
+    return workflows;
+  }
+  /**
   * Pending surface — runtime not built. Every method returns
   * `not_implemented`. Mem0 is a third-party integration, not a Stackbone
   * Agent Protocol capability, so this surface is intentionally not gated.
@@ -17317,26 +17384,6 @@ function eveAgent(name) {
   });
 }
 __name(eveAgent, "eveAgent");
-function getWorkflowStarter() {
-  {
-    throw new Error("No workflow starter is bound. `startWorkflow` / `startWorkflowAndWait` can only be called from inside a running workflow \u2014 the runtime binds the starter on its first dispatch.");
-  }
-}
-__name(getWorkflowStarter, "getWorkflowStarter");
-
-// src/surfaces/agent-local/workflows/start-workflow.ts
-async function startWorkflow(name, input, opts) {
-  "use step";
-  return getWorkflowStarter().start(name, input, opts);
-}
-__name(startWorkflow, "startWorkflow");
-
-// src/surfaces/agent-local/workflows/start-workflow-and-wait.ts
-async function startWorkflowAndWait(name, input, opts) {
-  "use step";
-  return await getWorkflowStarter().startAndWait(name, input, opts);
-}
-__name(startWorkflowAndWait, "startWorkflowAndWait");
 
 // src/surfaces/agent-local/workflows/ingest-documents.ts
 async function ingestDocuments(args, opts = {}) {
@@ -17366,26 +17413,6 @@ async function stageContent(collection, content, contentType) {
   return storageKey;
 }
 __name(stageContent, "stageContent");
-function getWorkflowScheduler() {
-  {
-    throw new Error("No workflow scheduler is bound. `scheduleWorkflow` / `unschedule` / `listSchedules` can only be called inside a running workflow runtime \u2014 the runtime binds the scheduler on its first dispatch.");
-  }
-}
-__name(getWorkflowScheduler, "getWorkflowScheduler");
-
-// src/surfaces/agent-local/workflows/schedule-workflow.ts
-async function scheduleWorkflow(name, input, cron) {
-  return getWorkflowScheduler().schedule(name, input, cron);
-}
-__name(scheduleWorkflow, "scheduleWorkflow");
-async function unschedule(name) {
-  return getWorkflowScheduler().unschedule(name);
-}
-__name(unschedule, "unschedule");
-async function listSchedules() {
-  return getWorkflowScheduler().listSchedules();
-}
-__name(listSchedules, "listSchedules");
 
 export { WORKFLOW_HOOK_RESUME_KIND, callConnector, connection, eveAgent, ingestDocuments, listSchedules, requestApproval, scheduleWorkflow, startWorkflow, startWorkflowAndWait, unschedule };
 //# sourceMappingURL=workflow.js.map