/**
 * @fileoverview fitness's fingerprint strategy for the host baseline/ratchet
 * plane (ADR-0036).
 *
 * fitness's identity is `sha256(filePath\nruleId\nmessage)` — it INCLUDES the
 * message but EXCLUDES line/column, so an unrelated line-shift (code added above
 * a finding) does not re-key the baseline and flap the ratchet. This is the
 * opposite policy from graph's location-based key (which excludes message because
 * several graph rules embed run-varying counts in their message), and both are
 * correct for their domain (ADR-0036: per-tool strategy, not a global algorithm).
 *
 * Byte-preserved from the pre-ADR-0036 `DEFAULT_VIOLATION_IDENTITY`
 * (`gate.ts`), now keyed off the `Signal` (the plane's currency) instead of a
 * `GateViolation` — the same three fields `extractViolationsFromEnvelope` read.
 * A `fingerprint-parity.test.ts` pins byte-equality against that oracle before
 * the old gate is deleted.
 *
 * Version 2 (ADR-0036 amendment, 2026-07-07): the hash formula is unchanged; the
 * bump records that baselines produced under this strategy are now disambiguated
 * by the host occurrence-ordinal in `stampFingerprints` (two distinct findings
 * sharing filePath+ruleId+message no longer collapse to one baseline row). The
 * id/version mismatch forces a one-time `--gate-save` re-capture; the fitness DB
 * baseline is CI-ephemeral so this is drop-and-recapture, not a data migration.
 */
/** fitness's message-hash baseline identity: `sha256(filePath\nruleId\nmessage)`. */
export declare const fitnessFingerprintStrategy: import("@opensip-cli/core").FingerprintStrategyDescriptor;
//# sourceMappingURL=baseline-strategy.d.ts.map