{"version":"2.1.267","anchor":"severity-threshold-config-no-longer-requires-two-feature-che","canonical_anchor":"severity-threshold-config-no-longer-requires-two-feature-che","heading":"Per-site\/per-key severity threshold now skips two feature-gate checks","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/severity-threshold-config-no-longer-requires-two-feature-che","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Per-site\/per-key severity threshold now skips two feature-gate checks\n\nSeverity threshold lookups no longer require two feature checks to pass before consulting per-site severity config\n\n**Unclear.** The finding does not say what user-visible effect, if any, this has since the explicit off case is still respected.\n\n**What** The function that computes per-key\/per-site severity thresholds (referred to as `t1`\/`t2`, also `dht`) used to require both an internal `_1()` and `On()` check to pass before it would consult the `severityBySite` config, otherwise falling back to a default. That early gate has been removed: the function now reads the site's severity config unconditionally (still honoring an explicit \"off\"), regardless of those two checks.\n\n**Why** Means severity thresholds configured per site now always take effect rather than being silently skipped when the two gate checks didn't both pass.\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}