/**
 * Resolve the DM recipient for a first-upgrade restart failure, inside the SAME
 * bot application that will send the notification.
 *
 * Critically, this ALSO registers the sending bot in the in-process bot
 * registry on BOTH resolution paths. The fresh `botmux restart` CLI is a new
 * process whose registry starts empty and is never populated elsewhere on the
 * restart path (loadBotsJson only reads the file). Without registration here,
 * the subsequent `sendUserMessage → getBotClient → getBot` throws
 * `Bot not registered`, which would silently defeat the notification on the
 * most common (persisted `ownerOpenId`) path. See PR #843 R2 review.
 */
export interface RestartFailureOwnerDeps {
    /** Register the sending bot so getBotClient can build its Lark client. */
    registerBot: (cfg: any) => void;
    /** Resolve stable allowedUsers entries through the sending app itself. */
    resolveAllowedUsers: (larkAppId: string, raw: string[]) => Promise<string[]>;
}
export declare function resolveRestartFailureOwner(bot: any, deps: RestartFailureOwnerDeps): Promise<string | undefined>;
//# sourceMappingURL=restart-failure-owner.d.ts.map