{"version":"2.1.271","anchor":"plugin-validator-now-flags-manifest-hooks-that-declare-add","canonical_anchor":"plugin-validator-now-flags-manifest-hooks-that-declare-add","heading":"Plugin validator now flags manifest hooks that declare $ additions but never register engine.create","tier":"internal","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/plugin-validator-now-flags-manifest-hooks-that-declare-add","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Plugin validator now flags manifest hooks that declare $ additions but never register engine.create\n\nPlugin validator now flags manifests that declare engine hook types but never register an engine.create hook\n\n**What**\n\nThe validator that checks plugin manifests now compares a plugin's declared 'types contract' (which members it promises to implement on the engine interface) against what the plugin actually registers. If the manifest declares members on `EngineInterface` but the plugin never registers a handler for the `engine.create` event, a new diagnostic is now emitted.\n\n**Why**\n\nThis catches plugins that describe capabilities in their manifest but never actually wire them up, surfacing a mismatch that would otherwise go unnoticed until the plugin failed to behave as declared.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}