/**
 * Result of dispatching one authored schedule via the dev-only HTTP route.
 */
export interface DispatchScheduleInDevResult {
    readonly scheduleId: string;
    readonly sessionIds: readonly string[];
}
/**
 * Error raised when the dev-only schedule dispatch route is given a
 * schedule id that does not match any compiled authored schedule.
 *
 * The route handler maps this to an HTTP 404 with the list of available
 * schedule ids so callers can correct their request without grepping the
 * server's logs.
 */
export declare class UnknownDevScheduleError extends Error {
    readonly availableScheduleIds: readonly string[];
    readonly scheduleId: string;
    constructor(scheduleId: string, availableScheduleIds: readonly string[]);
}
/**
 * Dispatches one compiled authored schedule in-process inside the running
 * dev server. Used by the dev-only `POST /eve/v1/dev/schedules/:scheduleId`
 * HTTP route to fire a schedule out-of-band without registering it with
 * Nitro's cron scheduler.
 *
 * The dispatch path is the same one the production cron handler uses:
 * `dispatchScheduleTask` resolves the compiled schedule, loads the agent
 * bundle, and invokes `ScheduleDispatcher.trigger(...)`. The dev server's
 * workflow runtime owns the resulting sessions, so the caller can stream
 * them via the existing `/eve/v1/session/:sessionId/stream` route as soon
 * as this resolves.
 *
 * Re-resolves authored schedule registrations from disk on every call so
 * the route picks up edits made by the authored-source watcher without a
 * dev-server restart.
 */
export declare function dispatchScheduleInDev(input: {
    readonly appRoot: string;
    readonly scheduleId: string;
}): Promise<DispatchScheduleInDevResult>;