import type { StepProviderOptions } from '../../core/models/workflow-types.js';
import type { PermissionMode } from '../../core/models/types.js';
import type { ProviderType } from '../../core/workflow/types.js';
/**
 * Provider/model/options for a non-workflow agent (task summarizer, sync conflict resolver,
 * non-assistant interactive persona). Mirrors the assistant seam's `ResolvedAssistantProvider`:
 * `runtimeManaged` is true only when an active runtime.yaml provider section owns the resolution,
 * in which case `providerOptions` come from the same `defaults` profile and the caller must not
 * fall back to the legacy `resolveNonWorkflowProviderOptions` path.
 */
export interface ResolvedNonWorkflowProvider {
    provider?: ProviderType;
    model?: string;
    providerOptions?: StepProviderOptions;
    permissionMode?: PermissionMode;
    runtimeManaged: boolean;
}
/**
 * Resolve the non-workflow provider/model/options. When an active runtime.yaml provider section
 * exists its `defaults` profile wins (order.md #1136) and its provider/model/options are carried
 * from a single profile, with env (`TAKT_PROVIDER`/`TAKT_MODEL`) overrides composed on top the
 * same way the selector/assistant seams do; otherwise the legacy config.yaml resolution runs
 * unchanged (env overrides are already folded into the loaded config there) and the caller keeps
 * resolving options via `resolveNonWorkflowProviderOptions`. A mixed configuration fails fast
 * inside `resolveRuntimeNonWorkflowProvider`, consistent with the sibling selector/assistant seams.
 */
export declare function resolveNonWorkflowProviderModel(cwd: string): ResolvedNonWorkflowProvider;
//# sourceMappingURL=nonWorkflowProvider.d.ts.map