/** CLI adapter for v3 Saved Workflows. Core policy lives in library-service. */
import type { RawParamInput } from '../workflows/shared/params.js';
import { listVisibleSavedWorkflows, loadVisibleSavedWorkflow, resolveVisibleSavedWorkflow, type SavedWorkflowActorContext } from '../workflows/v3/library-service.js';
export declare function formatSavedWorkflowCliShow(loaded: Awaited<ReturnType<typeof loadVisibleSavedWorkflow>>, context: SavedWorkflowActorContext, raw: boolean): string;
export declare function formatSavedWorkflowCliList(listed: Awaited<ReturnType<typeof listVisibleSavedWorkflows>>, json: boolean): string;
export declare function contextFromEnv(env?: NodeJS.ProcessEnv, startPid?: number): SavedWorkflowActorContext;
/**
 * `workflow run` immediately asks the live daemon to start the materialized
 * run. That daemon only resolves ids under its canonical v3 root, so accepting
 * a different CLI directory would create a valid but permanently orphaned run.
 * Core materialization keeps an injectable baseDir for tests/migrations; the
 * user-facing start command does not.
 */
export declare function assertDaemonManagedRunBaseDir(baseDir: string, canonical?: string): void;
/** Agent-facing CLI cannot prove the daemon's per-chat `canOperate` policy. */
export declare function assertAgentFacingSaveScope(args: readonly string[]): void;
export declare function assertAgentFacingAppendScope(dataDir: string, workflowId: string, context: SavedWorkflowActorContext, resolveVisible?: typeof resolveVisibleSavedWorkflow): Promise<void>;
/**
 * Parse Saved Workflow CLI params without confusing another option's value for
 * a bare `key=value` param. The null-prototype result and reserved-name guard
 * keep `__proto__` from becoming an inherited assignment rather than input.
 */
export declare function collectSavedWorkflowRawParams(args: string[]): Record<string, RawParamInput>;
export declare function cmdSavedWorkflow(sub: string, args: string[]): Promise<void>;
//# sourceMappingURL=saved-workflow.d.ts.map