/**
 * method-catalog-update.ts, asking a daemon whether it is keeping itself current.
 *
 * The self-update loop already knew all of this: its cadence, how many checks
 * in a row had thrown and what the last one said, a release it had downloaded
 * and verified and was holding until the daemon went idle, and a release a
 * crash-loop rollback had rejected and will not reinstall. All of it lived in
 * one process's memory and a log file, so the only way to answer "is this
 * daemon updating itself" was shell access to the host.
 *
 * That is the gap these two verbs close, and the reason it matters is on the
 * record: a daemon whose update checks had been failing stayed on an old build
 * while three releases shipped, and every surface reported it as healthy,
 * because "has not updated" and "cannot update" produce identical silence.
 *
 * `update.check` runs the SAME tick the schedule runs, not a second path, so
 * an on-demand check and the hourly one cannot come to different conclusions.
 * It does not force an install: a verified swap still waits for a moment when
 * no work is in flight, which is what `pendingVersion` reports.
 */
import type { GatewayMethodDescriptor } from './method-catalog-shared.js';
export declare const builtinGatewayUpdateMethodDescriptors: readonly GatewayMethodDescriptor[];
//# sourceMappingURL=method-catalog-update.d.ts.map