import type { WorkflowDefinition } from "../flow/types.ts";
/**
 * The file suffix that marks a workflow module inside the workflows directory. Lives here rather than
 * in workflow-catalog.ts so that files loaded UNDER this loader (builtin/create.workflow.ts) can name
 * it without importing catalog machinery, whose graph reaches `@earendil-works/pi-coding-agent` — a
 * module that only resolves in the extension's own loader, never in this one.
 */
export declare const WORKFLOW_SUFFIX = ".workflow.ts";
/**
 * Load a workflow `.ts` file at runtime (spec §1.4: "loaded via PI's existing TypeScript
 * loader ... on `/workflow run`"). Uses `jiti` — the same TS-loading approach PI's own CLI
 * depends on — so no separate build step is required for workflow authors.
 *
 * Runtime caching is disabled deliberately. A fresh jiti still integrates with Node's process-wide
 * CommonJS cache by default, which would return the first failed candidate after `/workflow create`
 * repaired that same entry path (and can likewise retain a stale relative helper module).
 *
 * Accepts either `export default workflow` or `export const workflow = ...`.
 */
export declare function loadWorkflowFile(absolutePath: string): Promise<WorkflowDefinition>;
//# sourceMappingURL=load-workflow.d.ts.map