/**
 * App — Phase 3 root that mounts the Phase 1 StatusLine + Phase 2 Prompt
 * together and exposes a minimal command surface.
 *
 * This is the integration that proves the Ink tree can replace the
 * sticky-bottom panel of the existing renderer wholesale: status row on
 * top, suggestions list, prompt at the bottom. The host (eventually
 * interactiveShell.ts) drives state via the props on this component.
 *
 * Phase 4 will add a `<Static>` chat-history block above this component;
 * the API stays the same — only the host's rendering of past events
 * changes.
 */
import React from 'react';
import { type StatusLineProps } from './StatusLine.js';
import { type PromptProps } from './Prompt.js';
import { type ChatItem } from './ChatStatic.js';
export interface Suggestion {
    label: string;
    hint?: string;
}
export interface AppProps {
    /** Past chat events. Rendered via <Static> so scrollback is permanent. */
    history?: ChatItem[];
    /**
     * In-progress assistant message. Streaming deltas accumulate here so
     * the text grows in place; once the model emits its `response` event
     * the controller moves the final text into `history` and clears
     * this. Without this slot, every delta would create its own
     * <Static> entry — which is what produced the "one word per line"
     * symptom users saw in 1.1.0/1.1.1.
     */
    streamingMessage?: string | null;
    status?: StatusLineProps;
    prompt: PromptProps;
    suggestions?: Suggestion[];
}
export declare const App: React.FC<AppProps>;
//# sourceMappingURL=App.d.ts.map