/**
 * Ink internals reset — the Command Code pattern, adapted for stock Ink 6.6.0
 * without a bundler.
 *
 * Why: `<Static>` renders each item once and freezes it, so resize-reflow and
 * tool-block expand/collapse (which need to re-render history) don't work.
 * Remounting `<Static>` via a `key` bump re-paints everything — BUT Ink
 * accumulates the re-emitted items in its internal `fullStaticOutput`, causing
 * duplicate "phantom" lines. Resetting `fullStaticOutput` + `lastOutput` before
 * the remount fixes that.
 *
 * Stock Ink doesn't expose the instance. Its `package.json` `exports` field
 * blocks `ink/build/instances.js` as a subpath, BUT importing the file by its
 * resolved absolute path (derived from the exported main entry) bypasses
 * package-exports enforcement — no bundler required.
 *
 * This is internals-poking, so it's shape-guarded: if a future Ink changes the
 * internal field names or the instances store, `resetInkStatic` returns false
 * and callers fall back to the frozen-on-resize behavior (no crash). Mirror of
 * Command Code's `registerInkControl` + `warnPatchSkipped`.
 */
/** Pre-load the internal instances store (async; call once at TUI start). */
export declare function warmInkReset(): Promise<void>;
/**
 * Reset Ink's accumulated Static output + last-frame tracking so a `<Static>`
 * remount repaints cleanly. Returns false (no-op) if the internals are
 * unavailable or shaped differently than expected.
 */
export declare function resetInkStatic(stdout: object): boolean;