peczenyj / GDPR-IAB-TCFv2 / 25532590212

96%

main: 96%

push

github

feat(validator): emit distinct ReasonPublisherRestriction* codes (Phase 6.4) (#68)

The Validator now inspects publisher restrictions for each
(vendor, purpose) pair before delegating to the parser, and emits a
Failure carrying the precise restriction-driven Reason* code when a
restriction contradicts the configured legal basis:

* RestrictionType NotAllowed (0)             -> ReasonPublisherRestrictionNotAllowed
* RestrictionType RequireConsent (1) on LI   -> ReasonPublisherRestrictionRequireConsent
* RestrictionType RequireLegitimateInterest (2) on consent
                                              -> ReasonPublisherRestrictionRequireLegitimateInterest

Each Failure also carries the structured restriction_type field, so
downstream consumers can react programmatically without parsing
strings. The matching restriction (e.g. RequireConsent on a consent
purpose) is a legal coexistence and falls through to the parser
delegate as before.

Notes:
* Limited to non-flexible purposes. The flex API may flip basis based
  on the restriction itself, so what looks like a contradiction at
  the rule level can still pass; that path keeps the existing
  generic vendor-not-allowed code.
* Golden corpus regenerated (`REGEN_CORPUS=1 prove -lr t/07-golden.t`):
  the v284_li_p7 scenario now reports one of three precise reasons
  where it previously reported a single generic reason.

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

22 of 23 new or added lines in 1 file covered. (95.65%)

1063 of 1112 relevant lines covered (95.59%)

10876.84 hits per line