/**
 * Everything one Deno host installs to run and manage workflow runs.
 *
 * Storage and lifecycle write to the same databases, so the host owns one
 * connection registry and hands the same one to each. Installing them
 * separately still works — each allocates its own — but a host doing both would
 * then have two authoritative writers for one file, which is the invariant the
 * registry exists to hold.
 */
import type { Operation } from "effection";
import type { WorkflowExecutionTransitions } from "../lifecycle/execution.js";
import type { LegacyWorkflowSourceReader } from "../lifecycle/source.js";
import { type WorkflowRunStorageOptions } from "./provider.js";
/** What one host installs, and the version-1 source capability it may carry. */
export interface WorkflowRunHostOptions extends WorkflowRunStorageOptions {
    /**
     * How this host turns a retained version-1 definition back into Markdown.
     *
     * Captured in the lifecycle provider's closure, never installed into a scope
     * and never reachable by name. A host that supplies none can inspect and
     * control runs and cannot begin, fork or export a Git one.
     */
    readonly legacySource?: LegacyWorkflowSourceReader;
}
export declare function useWorkflowRunHost(options: WorkflowRunHostOptions): Operation<WorkflowExecutionTransitions>;