import type { BatchOperation, ConditionalBatchCondition } from '../../storage/interface.ts';
import type { EngineInternals } from './internals.ts';
export type AtomicWorkflowCommitSideEffects = {
    conditions: ConditionalBatchCondition[];
    operations: BatchOperation[];
};
export declare function stageAtomicWorkflowCommitSideEffects(internals: EngineInternals, workflowId: string, sideEffects: AtomicWorkflowCommitSideEffects): void;
export declare function takePendingAtomicWorkflowCommitSideEffects(internals: EngineInternals, workflowId: string): AtomicWorkflowCommitSideEffects | undefined;
export declare function clearPendingAtomicWorkflowCommitSideEffects(internals: EngineInternals, workflowId: string): void;
/**
 * Non-destructively report whether a workflow's pending atomic side-effect buffer
 * already stages a `put` to `key`. Unlike {@link takePendingAtomicWorkflowCommitSideEffects},
 * this does NOT consume the buffer, so it is safe to call at a gate that runs before the
 * commit that will flush those same side-effects.
 *
 * The terminal-transition path (#446) needs this: `ctx.setFinalizerState()` stages the
 * `wf-finalizer-state:` put as a pending side-effect that the terminal batch flushes, but
 * a pre-batch `storage.get()` cannot see a staged-but-unflushed write. Peeking the buffer
 * lets the terminal batch stage its teardown marker atomically alongside that put — without
 * it, a `setFinalizerState` with no intervening checkpoint would commit the resource state
 * yet skip the teardown marker, silently leaking the external resource.
 */
export declare function pendingAtomicWorkflowCommitSideEffectsStagePut(internals: EngineInternals, workflowId: string, key: string): boolean;