import { type BundleFetchResult, type SkillsBundle } from "../content";
/**
 * Print a failed bundle fetch with the same UX conventions as license activate
 * errors, and mark the process as failed.
 */
export declare function printBundleFailure(result: Extract<BundleFetchResult, {
    ok: false;
}>): void;
/** How the entitlement-shrink guard resolved. Anything but "proceed" means: do not install. */
export type RemovalConfirmation = "proceed" | "declined" | "refused-non-interactive";
/**
 * Entitlement-shrink guard, shared by EVERY installBundle caller. installBundle
 * prunes every installed skill the bundle no longer carries, which is correct
 * after a real plan downgrade — but the same pruning fires when the SERVER's
 * entitlement data is wrong, and on 2026-08-02 a server-side category defect
 * removed 9 skills from every Pro install that synced. Deleting installed
 * skills is never something this CLI may do silently: confirm interactively,
 * or require an explicit --yes when unattended. Extracted from sync because
 * `license activate`/`upgrade` install bundles through the same seam and
 * carried no guard at all.
 */
export declare function confirmProspectiveRemovals(previous: Record<string, string>, bundle: SkillsBundle, options?: {
    yes?: boolean;
}): Promise<RemovalConfirmation>;
/**
 * `enterprise-skills sync` — re-fetch the tier-filtered skill bundle for the
 * stored license key and reinstall it into ~/.enterprise-skills, printing
 * per-skill version changes against the previously installed manifest.
 */
export declare function syncCommand(options?: {
    yes?: boolean;
}): Promise<void>;
//# sourceMappingURL=sync.d.ts.map