import type { AdvisoryId, RuleId } from './types.js';
import type { OptimizeOptions, UsageProfile } from './types.js';
/**
 * Comparing two versions of a prompt.
 *
 * `optimize()` answers "how much fat is in this prompt". This answers a
 * different question, and the one a pull request actually raises: "somebody
 * edited this — did it get worse?"
 *
 * Sign convention, stated once and held everywhere: **every number here is a
 * delta, `after - before`, and positive means the change made things worse.**
 * That is deliberately the opposite of the rest of the codebase, where every
 * figure is a saving. Mixing the two conventions in one report is the single
 * easiest way to make a cost tool lie, so nothing in this module is called a
 * saving and nothing reuses that name.
 */
export interface RuleDelta {
    /** Rules that fire on the new version but did not on the old one. */
    newlyFiring: RuleId[];
    /** Rules that fired on the old version and no longer do. */
    noLongerFiring: RuleId[];
}
export interface AdvisoryDelta {
    /** Advisories the new version raises that the old one did not. */
    appeared: AdvisoryId[];
    /** Advisories the old version raised that the new one has resolved. */
    resolved: AdvisoryId[];
}
export interface PromptComparison {
    tokensBefore: number;
    tokensAfter: number;
    /** `after - before`. Positive means the prompt grew. */
    tokenDelta: number;
    /** The delta as a percentage of the old size. 0 when the old size was 0. */
    deltaPct: number;
    /** Monthly cost change in USD. Positive means it now costs more. */
    monthlyDeltaUsd: number;
    /** Per-call cost change in USD. Positive means it now costs more. */
    perCallDeltaUsd: number;
    rules: RuleDelta;
    advisories: AdvisoryDelta;
    usage: UsageProfile;
}
export interface CompareOptions extends OptimizeOptions {
    /**
     * Compare what the rules would leave, rather than what was written.
     *
     * Off by default, and that default matters: a pull request changed the file
     * on disk, so the file on disk is what the reviewer is being asked about.
     * Optimising both sides first would hide a prompt that doubled in length but
     * happened to double in courtesy, which is exactly the change worth seeing.
     */
    optimizeBoth?: boolean;
}
/**
 * Compares two prompt versions.
 *
 * Both sides go through `optimize()` regardless, because that is what produces
 * the rule and advisory findings — but by default the *token and cost figures*
 * come from the text as written. `optimizeBoth` switches the figures to the
 * optimised text, for a team that runs Trazum in their pipeline and cares
 * about what actually reaches the model.
 */
export declare function comparePrompts(before: string, after: string, options?: CompareOptions): PromptComparison;
//# sourceMappingURL=compare.d.ts.map