/**
 * Scanner Regression Guard — exec locality (SMI-5880)
 *
 * Split out of scanner-regression-guard.test.ts to stay under the 500-line/file
 * CI gate. Companion to that file's "hostile-update detection (SMI-5535, R0
 * Wave 2A)" describe block — see that file for the base benign-to-malicious
 * rug-pull regression test this one extends.
 *
 * SMI-5880: escalateCodeExecution now only escalates a code_execution finding
 * to critical when its co-signal is WITHIN 40 lines. This test proves that
 * bound does NOT create a gap in hostile-update detection: detectSupplyChain()
 * (SecurityScanner.hostile-update.ts) pairs a NEW non-doc code_execution
 * finding of ANY severity with a NEW non-doc high/critical co-signal at ANY
 * distance, so a far-apart rug-pull still returns the 'hostile' verdict with
 * its supply-chain reason string — even though the code_execution finding
 * itself stays MEDIUM (unescalated within the scan) because its co-signal
 * sits well beyond the 40-line window.
 */
export {};
//# sourceMappingURL=scanner-regression-guard.exec-locality.test.d.ts.map