You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(rules): RISK-008 detect one-sided consequential-damages waiver for any party label (v1.1.0)
What was wrong: RISK-008 (one-sided consequential-damages waiver) detected the
one-sided clause only when the protected party was labeled Provider/Vendor/
Company, so a waiver protecting only the Supplier, Licensor, Seller, Customer,
etc. slipped through entirely and never fired.
How it was fixed: broadened the one-sided-trigger party vocabulary to match the
beneficiary counter's list (adding Seller to both so the two stay in sync). The
existing ">=2 distinct beneficiaries" guard still clears a genuinely mutual
"X … and Y shall not be liable …" clause, so a mutual Seller/Buyer waiver stays
silent.
Proof: a new RISK-008.test.ts pins the one-sided waivers (Supplier / Licensor)
firing and the mutual / "neither party" waivers staying silent (7 tests). Full
suite green (5649 passing). RISK-008 is a launch rule, so all four golden corpora
(integration v2/v3, tests/golden/v3, tests/golden/v4, tests/golden/v4/bundle)
were checked with a finding-level delta before regen — zero finding drift across
every fixture (version-only hash bump; RISK-008 only).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
0 commit comments