/**
 * SMI-5879 G-5 fixture-corpus corroboration — CORE twin.
 * @module packages/core/tests/security/smi5879-corroboration.core
 *
 * Version-regression check: pre-port `SecurityScanner` (the committed golden,
 * generated at `PRE_PORT_BASELINE_SHA` — see
 * `docs/internal/implementation/smi-5879-g5-corroboration-spec.md` §0/§4) vs
 * THIS branch's HEAD `SecurityScanner`, over the shared fixture corpus,
 * asserting every non-AI `RiskScoreBreakdown` key is unchanged. It is NOT
 * `scripts/tests/indexer/parity.test.ts`'s core/Node/Deno twin-parity check —
 * see `scripts/indexer/smi5879-corroboration.types.ts`'s header for the full
 * distinction.
 *
 * PRE-PORT VACUOUSNESS WARNING: PR #2192 (the evidence-tier port to the edge
 * twin) has not merged as of this file's authorship. Until it does, "current
 * HEAD" and "pre-port baseline" are the SAME scanner, so a green run here is
 * NOT yet evidence the port preserved non-AI scoring — it is the scanner
 * compared to itself. This check starts being meaningful the moment #2192
 * lands; do not read a pre-merge green as validation of anything.
 *
 * `packages/core` never imports from `scripts/` (an established repo
 * boundary — see `smi5879-corroboration.types.ts`'s own header), so this
 * file duplicates the ~5-line content materialiser/hasher and the two small
 * key-list constants below rather than importing
 * `scripts/tests/indexer/smi5879-corroboration.fixtures.ts` /
 * `scripts/indexer/smi5879-corroboration.types.ts` across that boundary.
 * `contentSha256` re-verification (assertion 2 below) makes any divergence
 * between the two copies a loud test failure, never a silent one.
 */
export {};
//# sourceMappingURL=smi5879-corroboration.core.test.d.ts.map