import { type ChantConfig } from "../../config.js";
import type { CommandContext } from "../registry.js";
export declare function makeTemporalClient(profileName: string | undefined, projectPath: string): Promise<{
    client: import("./run-client.js").TemporalClientHandle;
    profile: import("./run-client.js").WorkerProfile;
    config: ChantConfig;
}>;
export declare function runOpList(ctx: CommandContext): Promise<number>;
export declare function runOpStatus(ctx: CommandContext): Promise<number>;
export declare function runOpLog(ctx: CommandContext): Promise<number>;
/**
 * `chant run signal <name> <signal> [--components]` — sends a signal to a
 * running Op workflow by default, or a component workflow when `--components`
 * is passed (#589): the durable path's gate is otherwise unclearable from the
 * CLI. Resolves the workflow id via `componentWorkflowId` (`chant-component-
 * <name>`) instead of `resolveWorkflowId` (`chant-op-<name>`) in that case —
 * the two id spaces are kept distinct so an Op and a component can share a
 * name without colliding.
 */
export declare function runOpSignal(ctx: CommandContext): Promise<number>;
/** `chant run cancel <name> [--components]` — cancels an Op workflow by default, or a component workflow when `--components` is passed (#589), mirroring `runOpSignal`'s id resolution. */
export declare function runOpCancel(ctx: CommandContext): Promise<number>;
/**
 * `chant run <name>` dispatcher.
 *
 * Local mode is the default — it runs the Op in-process with no Temporal
 * server. `--temporal` opts into a cluster (gates, schedules, durable resume).
 * `--report` reads a past durable run and is therefore Temporal-only.
 *
 * `chant run --components <name|all>` (#585) is a separate target: discovered
 * `Component` declarations dispatched through the interpret driver
 * (`../../components/driver.ts`) rather than a `*.op.ts` Op. Checked first,
 * mirroring `runGraph`'s `if (ctx.args.components) return
 * runComponentGraph(ctx)` branch (../handlers/graph.ts).
 *
 * chant #1116 — `--report` with `--components` is checked and hard-errored
 * before that dispatch. There is no preview/dry-run mode for the component
 * driver: unlike the Op path (where `--report` reads a past Temporal run),
 * `runOpComponents` has never read `ctx.args.report` at all, so the flag was
 * silently ignored and the command fell through to a real dispatch — observed
 * live reaching an actual cloud shell-out. Erroring here is the safe minimum
 * called out on the issue; a real preview is future work.
 */
export declare function runOp(ctx: CommandContext): Promise<number>;
/**
 * `chant run --components <name|all> [--env <env>] [--temporal]` (#585, and
 * #589 for `--temporal`) — the interpret driver's CLI entrypoint. `args.path`
 * is the component name (or `all`), matching `chant run <name>`'s Op-dispatch
 * convention exactly (`args.path` is the Op name there too) rather than a
 * project directory — components are always discovered from the current
 * working directory, the same way Op discovery (`discoverOps()`) never takes
 * a project-path argument either.
 *
 * Local mode (the default) resolves the selector through `runComponents`
 * (`../../components/cli-support.ts`) and runs it on the local in-process
 * executor; gated components are rejected before any step runs (matching
 * `runOpLocal`'s pre-flight `findGate` guard) with an actionable message
 * pointing at `--temporal`.
 *
 * `--temporal` (#589) takes the durable path instead: compiles the named
 * component's composition to a Temporal workflow/worker (mirroring
 * `Temporal::Op` codegen — see `runComponentTemporal` below), and gates are
 * now ACCEPTED — a gate is durable wait-for-signal there, not a local
 * in-process block. Scoped to a single named component (`all --temporal` is
 * out of scope for #589: coordinating N durable workflows' cross-component
 * `dependsOn` durably is a follow-up, not part of "compile a component's
 * `deploy` composition into a durable orchestrator").
 *
 * On a successful run, auto-emits one release-ledger record per component
 * that published a digest (#597, `recordAutoReleasesForRun` above) — a
 * *post-run* CLI step, not a change to the driver itself (`../../components/
 * driver.ts` stays capability-agnostic and knows nothing about the ledger).
 * Opt out with `--no-release-record` or `chant.config.ts`'s
 * `release.autoRecord: false`; the default is ON. A failed run never reaches
 * this step, so it writes nothing.
 *
 * chant #1108 — resolves this invocation's declared build-time parameters
 * (`chant.config.ts`'s `buildParams`, against `--param`/`--params-file`/a
 * declared `env` mapping) the exact same way `chant build` does
 * (`resolveCliBuildParams`, shared with `buildCommand`), BEFORE either the
 * local or `--temporal` path discovers/imports any `*.component.ts` file.
 * Before this, `params.*` (`@intentius/chant/params`) was always `{}` under
 * this command, no matter what a component's `chant.config.ts` declared or a
 * CI job's environment supplied — see chant #1108. `chant.config.ts` is
 * loaded once here (with the same defensive fallback the post-run
 * auto-release check below used to apply itself) and reused for that check,
 * rather than loaded a second time.
 */
export declare function runOpComponents(ctx: CommandContext): Promise<number>;
/**
 * Run an Op in-process via the local executor — no Temporal worker, server, or
 * built `worker.ts`. Reads the Op config straight from discovery and resolves
 * activities from the Temporal lexicon package.
 */
export declare function runOpLocal(ctx: CommandContext): Promise<number>;
export declare function runOpUnknown(ctx: CommandContext): Promise<number>;
//# sourceMappingURL=run.d.ts.map