{"version":"2.1.269","anchor":"pluginhook-execution-engine-rewritten-around-async-generato","canonical_anchor":"pluginhook-execution-engine-rewritten-around-async-generato","heading":"Plugin\/hook execution engine rewritten around async-generator streams","tier":"internal","area":"Plugin Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/pluginhook-execution-engine-rewritten-around-async-generato","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Plugin\/hook execution engine rewritten around async-generator streams\n\nPlugin and hook execution was rewritten to stream results and track per-handler timing and outcomes\n\n**Unclear.** The practical, user-visible effect of this rewrite (beyond internal timing\/outcome tracking) is not specified in the finding.\n\n**What**\n\nThe internal system that runs plugin and hook code was rebuilt around async generators (a way of producing a sequence of results piece by piece, or streaming, rather than all at once). The new version:\n\n- streams results in chunks as they become available\n\n- tracks per-handler timing, outcome, and chunk counts\n\n- supports a `.catch` handler with a grace window for handling failures\n\n- can chain or hand off execution between different plugin tiers\n\n**Why**\n\nThis is an internal rework of how plugin and hook code runs; the finding does not describe a specific new user-facing capability, but the added timing and outcome tracking suggests better visibility into how hooks and plugins perform and fail.\n\n- Area: Plugin Hooks\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}