Repository navigation
RugSnare 1.4.3 - POLICY stop-rule (PIN-SPEC §3.1)
When the pin store's policyVersion differs from the running binary, diff now emits the POLICY finding and STOPS - exactly one finding, no tool-level classes (BREAKING, LOOSENED, COSMETIC, GONE, NEW) follow. Each re-graded class would look like ordinary drift to anyone who scrolled past the POLICY line. The spec says "stops for that pin", and now the code does too. Exit 1 with a hint: "re-run after rugsnare scan to grade under the current policy".
359 tests. Verified: sha256 57483327...6727 matches the on-chain pin. Native launcher unchanged (1.3.0-native.1).