/**
 * Repeatedly evaluate a user-provided JavaScript expression until it returns
 * a truthy value (or the timeout fires).
 *
 * Why `operationType: 'eval'`:
 * - The expression IS user-controlled JS — the same risk surface as
 *   `electron_eval`. Routing through the eval security pipeline ensures
 *   `validateEvalContent` runs against the actual code.
 * - The handler dispatch reads `parsed.code` for eval commands; we use the
 *   field name `code` here to match.
 *
 * Resolution strings:
 * - `Condition met: <stringified result> (waited <ms>ms)`
 * - `Timeout: condition did not become truthy within <ms>ms`
 * - `Error in expression: <message>` if evaluation throws
 *
 * Polls every 100ms via `setInterval`; the wrapped expression runs inside a
 * `try/catch` so transient errors (e.g. a property not yet defined) don't
 * abort the wait.
 */
export declare const waitForFunction: import("../types").CommandModule;