/**
 * @file
 *
 * Records which Appium server on a port this harness started, so a later run
 * that finds a server already listening can tell **provenance**: one of our own
 * servers left over from an earlier run, or a foreign one the user manages.
 *
 * The preflight adopts any server that answers `/status`, and adoption is the
 * right default — starting a second server on an occupied port cannot work. But
 * adopting silently means a wedged leftover (see `wedged-appium-server.ts`) is
 * indistinguishable from a healthy server, and the harness has no basis on which
 * to decide whether restarting it is its call to make. The marker supplies that
 * basis: a server we started may be restarted, a foreign one is only ever
 * reported.
 *
 * The marker is a small JSON sentinel next to the setup lock (`setup-lock.ts`),
 * keyed by port, and is deliberately tolerant — a missing, unreadable, or
 * mismatched marker simply reads as "not ours".
 */
/**
 * Identifies the Appium server this harness started on a port.
 */
export interface AppiumServerMarker {
    /**
    PID of the spawned server process (the shell wrapper that owns the server's process tree).
     */
    readonly pid: number;
    /**
    The port the server was started on.
     */
    readonly port: number;
    /**
    When the server was started (`Date.now()` epoch milliseconds).
     */
    readonly startedAtInMilliseconds: number;
    /**
     * When a run tried to stop this server and could not verify it exited
     * (`Date.now()` epoch milliseconds), or `undefined` when no stop has failed.
     *
     * Its presence means the server is a **known-doomed leftover**: it was ours,
     * we asked it to die, and it did not. See {@link recordAppiumServerStopAttempt}.
     */
    readonly stopAttemptedAtInMilliseconds?: number | undefined;
}
/**
 * Parameters for {@link writeAppiumServerMarker}.
 */
export interface WriteAppiumServerMarkerParams {
    /**
    PID of the spawned server process.
     */
    readonly pid: number;
    /**
    The port the server was started on.
     */
    readonly port: number;
}
/**
 * Checks whether the marked server is still running, which is what makes an
 * adopted server ours to restart.
 *
 * A dead PID means the marker outlived its server, so whatever answers on that
 * port now is somebody else's — the marker proves nothing about it.
 *
 * @param marker - The marker read for the port, or `undefined` when there is none.
 * @returns `true` when an earlier run of this harness started the server now listening.
 */
export declare function checkIsHarnessOwnedAppiumServer(marker: AppiumServerMarker | undefined): boolean;
/**
 * Removes the marker for a port. Called once the marked server has been stopped,
 * so a later run does not mistake a recycled PID for our server.
 *
 * @param port - The Appium server port.
 */
export declare function clearAppiumServerMarker(port: number): void;
/**
 * Reads the marker for a port.
 *
 * @param port - The Appium server port.
 * @returns The marker, or `undefined` when there is none, it is unreadable, or it does not describe this port.
 */
export declare function readAppiumServerMarker(port: number): AppiumServerMarker | undefined;
/**
 * Records that a run tried to stop the marked server and could not verify it
 * exited — **instead of** clearing the marker.
 *
 * Clearing it would be the worst of both worlds: the leftover keeps serving, and
 * the next run reads it as a foreign, user-managed server it must never touch
 * (`checkIsHarnessOwnedAppiumServer` needs the marker to convict it). Keeping
 * the marker, stamped, says exactly what is true — this is ours, and it outlived
 * our teardown — which is what lets the next run refuse to adopt it and replace
 * it instead.
 *
 * @param port - The Appium server port.
 */
export declare function recordAppiumServerStopAttempt(port: number): void;
/**
 * Records the server this run just started, stamping it with the current time so
 * a later run can report how long it has been up.
 *
 * @param params - The started server's PID and port.
 */
export declare function writeAppiumServerMarker(params: WriteAppiumServerMarkerParams): void;