/**
 * transport/screen.ts — pure predicates over a captured terminal frame.
 *
 * Deliberately dependency-free so the transport layer itself can use them
 * without importing anything that imports the transport back.
 */
/** The line Claude's input box is drawn on. */
export declare const INPUT_LINE: RegExp;
/** A horizontal rule; the input box is bounded by two of them. */
export declare const CLAUDE_UI: RegExp;
/** A shell prompt: a line ending in a common prompt terminator. */
export declare const SHELL_PROMPT: RegExp;
/**
 * A row of the background-agents panel Claude draws UNDER its status lines
 * while agents run: a "main" header, one `◯ <agent> <task> · <time> · <tokens>`
 * row per agent, an overflow count, and the navigation hint. Up to a dozen
 * lines, all Claude's own, all below the closing rule.
 */
export declare const AGENT_PANEL: RegExp;
/** Collapse whitespace so wrapped and padded terminal text compares sanely. */
export declare function flatten(s: string): string;
/**
 * True when Claude's input box is LIVE at the bottom of the screen.
 *
 * "Contains a box somewhere" is not enough, and the difference is a safety
 * issue. When Claude exits — crashes, is suspended, or is ended cleanly — its
 * whole UI stays in the terminal's scrollback while a shell prompt appears
 * underneath. A frame-wide search still finds the rules and the `❯`, declares
 * the session ready, and the caller types into a live shell, where zsh
 * EXECUTES the text.
 *
 * A live box is therefore required to be at the bottom: the closing rule near
 * the end of the visible frame, with nothing shell-prompt-shaped after it.
 */
export declare function isClaudeReady(frame: string): boolean;
/**
 * The lines inside Claude's input box.
 *
 * Identified structurally — the region between the last two horizontal rules —
 * because the `❯` marker also matches every echoed message in the transcript.
 */
export declare function inputBoxLines(frame: string): string[];
/**
 * Is the input box drawn and holding nothing?
 *
 * The distinction that matters for a freshly spawned session. `isClaudeReady`
 * asks whether the box EXISTS, which is the right question for "can this
 * session accept input at all" and the wrong one for "is it safe to type now":
 * a session launched with a queued `/Name … \n go` preamble draws its box with
 * that preamble sitting inside it, unsubmitted. Typing a work order at that
 * moment appends to the queued text instead of replacing it — the dispatcher
 * and the preamble interleave, and so does anything the user types.
 *
 * Observed 2026-08-04: a spawned session received its Todoist work order while
 * `/Name Voice Notes` and `go` were both still queued in the box.
 *
 * Emptiness — not idleness. A busy session with an empty box queues typed input
 * correctly and must still count as ready, which is what the original comment
 * on `waitForReady` was protecting and what waiting for the screen to settle
 * would have broken.
 */
export declare function isInputBoxEmpty(frame: string): boolean;
/** Index of the line opening the bottom input box, or -1. */
export declare function inputBoxStart(frame: string): number;
/**
 * Has `needle` left the input box and landed in the transcript?
 *
 * Presence on screen is not enough: unsubmitted text in the box is also
 * present. Submission is the moment it appears while the box no longer holds it.
 */
export declare function hasBeenSubmitted(frame: string, needle: string): boolean;
//# sourceMappingURL=screen.d.ts.map