/**
 * Migration 057: Workflow step persistence.
 *
 * Adds the `workflow_steps` table — one row per step of a multi-step
 * workflow executed inside an interactive session — and a `step_id`
 * column on `interactive_messages` so every persisted message is
 * grouped under the step that produced it.
 *
 * This replaces the fragile text-marker protocol (SHEP__PLAN /
 * SHEP__STEP_START / SHEP__STEP_FINISHED_RESULT) that previously
 * lived in the agent's output stream with a backend-orchestrator-
 * owned model. Two robustness properties follow directly from the
 * schema:
 *
 *   1. A step row transitions to `running` BEFORE the agent is
 *      invoked and to `done`/`failed` AFTER it returns. A browser
 *      refresh or daemon crash at any instant observes a correct
 *      SELECT — nothing is ever inferred from an in-memory field.
 *
 *   2. Every `InteractiveMessage` written during a turn carries the
 *      currently-active `step_id`, so grouping the conversation by
 *      step is a SQL filter, not a heuristic walk of the message
 *      stream.
 */
import type { MigrationParams } from 'umzug';
import type Database from 'better-sqlite3';
type Db = Database.Database;
export declare function up({ context: db }: MigrationParams<Db>): Promise<void>;
export declare function down({ context: db }: MigrationParams<Db>): Promise<void>;
export {};
//# sourceMappingURL=057-workflow-steps.d.ts.map