{"version":"2.1.267","anchor":"compliance-taint-restriction-check-consolidated-behind-a-hel","canonical_anchor":"compliance-taint-restriction-check-consolidated-behind-a-hel","heading":"Compliance-taint restriction check consolidated behind a helper, semantics likely unchanged","tier":"internal","area":"Compliance","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/compliance-taint-restriction-check-consolidated-behind-a-hel","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Compliance-taint restriction check consolidated behind a helper, semantics likely unchanged\n\nCompliance-taint restriction check refactored to use a shared helper function\n\n**Unclear.** Whether the consolidation changes behavior in any edge case is not confirmed.\n\n**What**\n\nThe check that determines whether a compliance taint denies a given restriction now calls a single shared helper function instead of iterating directly over an internal lookup map. The finding indicates this is a code cleanup rather than a behavior change.\n\n**Why**\n\nThis is an internal restructuring that consolidates logic into one place; it is not expected to change what gets restricted or allowed.\n\n- Area: Compliance\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}