{"version":"2.1.275","anchor":"plugin-op-host-refusal-messages-consolidated-behind-new-gate","canonical_anchor":"plugin-op-host-refusal-messages-consolidated-behind-new-gate","heading":"Plugin op host-refusal messages consolidated behind new gate helper","tier":"internal","area":"Plugin API","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/plugin-op-host-refusal-messages-consolidated-behind-new-gate","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Plugin op host-refusal messages consolidated behind new gate helper\n\nPlugin hook-refusal error messages now come from one shared helper function\n\n**What**\n\nWhen a plugin operation is refused because no matching hooks module is loaded, or because a loaded hooks module doesn't call that particular hook, both refusal messages now come from a single new shared helper function instead of being handled separately. The code path that runs the operation also now passes along the relevant scan information to the function that picks the runtime handler.\n\n**Why**\n\nThis is an internal cleanup that consolidates duplicate refusal logic; it should not change what message you see when a plugin operation is refused, just how that message gets produced internally.\n\n- Area: Plugin API\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}