/**
 * True when resuming this session will start a FRESH CLI instead of restoring
 * its history: the adapter can only resume a precise `cliSessionId` (no
 * `--continue` / "latest" fallback — those risk loading a SIBLING botmux
 * session's conversation) and no id was persisted.
 *
 * Upper layers use this to distinguish "logical route reactivated" from "CLI
 * history restored" in user-facing copy (closed-session card, resume receipt),
 * so users are never told history is back when the next spawn is actually a
 * blank session. The worker independently demotes resume→fresh (with its
 * existing fresh-demotion notice) via the same adapter capability flag.
 */
export declare function resumeStartsFresh(session: {
    cliId?: string;
    cliSessionId?: string;
}): boolean;
//# sourceMappingURL=resume-fresh-policy.d.ts.map