/**
 * Manual hot-reload trigger. The dashboard fires this after the user
 * edits config via a wizard, toggles an adapter, etc. — but the route
 * handlers that mutate config call tryReload() inline too, so this is
 * mainly for cases where the user knows they changed env vars or
 * something outside the dashboard's mutation surface.
 *
 * - POST /api/reload
 */
import type { IncomingMessage, ServerResponse } from "node:http";
import type { RouteContext } from "../route-context.js";
export declare function handle(req: IncomingMessage, res: ServerResponse, ctx: RouteContext): Promise<boolean>;
//# sourceMappingURL=reload.d.ts.map