{"version":"2.1.277","anchor":"second-condition-added-to-a-feature-availability-gate-for-tw","canonical_anchor":"second-condition-added-to-a-feature-availability-gate-for-tw","heading":"Second condition added to a feature-availability gate for two related capabilities","tier":"internal","area":"Feature Gates","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/second-condition-added-to-a-feature-availability-gate-for-tw","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Second condition added to a feature-availability gate for two related capabilities\n\nTwo related capabilities now require an extra runtime condition on top of the existing enabled-list check\n\n**Unclear.** What the added runtime condition actually checks, and which two capabilities these are, is not established by the evidence.\n\n**What**\n\nTwo nearly identical feature-availability checks, each for a related tool\/capability, now require an additional runtime condition (`ryn(H0e)` and `ryn(_Te)` respectively) to pass, on top of the existing check against the enabled-features list.\n\n**Why**\n\nThis narrows when these two capabilities are considered available, adding a further runtime condition beyond simply being enabled.\n\n- Area: Feature Gates\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}