/**
 * Application-creation workflow definition.
 *
 * The five steps Shep walks every new application through, with the
 * friendly non-technical title/description the user sees in the
 * tracker card AND the focused agent-facing prompt the orchestrator
 * sends for that step.
 *
 * History note: earlier versions had `plan`/`content`/`deps`/`style`
 * steps that were folded away, and a `scaffold` step that ran bun
 * bootstrap + `bunx shadcn init` + a bash flatten one-liner inside an
 * agent turn. `scaffold` was deleted in v4 because doing it inside
 * the agent turn repeatedly failed in three ways: (1) bun might not
 * be on PATH, (2) `shadcn init --template vite` creates a child
 * directory that needed a fragile flatten, (3) the final `bun add`
 * was sometimes skipped. All four phases now run deterministically
 * in `BunShadcnScaffolder` at application-creation time, BEFORE the
 * first agent turn ever starts. The agent lands on a flat, ready-to-
 * code project and its very first step is `components`.
 *
 * Key design notes:
 *   - The orchestrator (`RunWorkflowUseCase`) sends each step's
 *     `prompt` as a user turn against the SAME interactive session,
 *     so the agent has full history from the previous steps.
 *   - The very first step's prompt is decorated with a brief-read
 *     directive by `CreateApplicationUseCase` so the agent reads
 *     `SHEP_BRIEF.md` before doing anything else. Subsequent steps
 *     can just say "do X" because the brief is already loaded.
 *   - Titles and descriptions are user-facing. Never put code, paths,
 *     or jargon in them — they show in step cards next to avatars.
 */
export interface WorkflowStepDefinition {
    /** Stable key persisted in `workflow_steps.step_key`. */
    stepKey: string;
    /** User-facing card title. */
    title: string;
    /** User-facing card subtitle. */
    description: string;
    /** Focused agent prompt for this step. Sent as a user turn. */
    prompt: string;
}
export interface WorkflowDefinition {
    /** Versioned logical id persisted in `workflow_steps.workflow_id`. */
    id: string;
    /** Ordered step list. */
    steps: WorkflowStepDefinition[];
}
export declare const APPLICATION_CREATION_WORKFLOW_ID = "application-creation-v4";
/**
 * The canonical application-creation workflow. Bumping the `id`
 * suffix ("-v1" → "-v2") triggers a new set of step rows for any
 * session that starts after the bump, without touching existing
 * data. Old rows remain queryable by their old workflow id.
 */
export declare const APPLICATION_CREATION_WORKFLOW: WorkflowDefinition;
//# sourceMappingURL=application-creation.workflow.d.ts.map