{"version":"2.1.265","anchor":"hook-dispatch-events-gain-a-raise-field","canonical_anchor":"hook-dispatch-events-gain-a-raise-field","heading":"Hook dispatch events gain a 'raise' field","tier":"internal","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/hook-dispatch-events-gain-a-raise-field","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Hook dispatch events gain a 'raise' field\n\nInternal hook dispatch events gained a new 'raise' field, purpose unclear\n\n**Unclear.** What the `raise` field actually controls or affects is not shown by the evidence.\n\n**What**\n\nThe internal machinery that dispatches hooks (scripts or commands that run automatically at certain points, such as before or after a tool runs) now passes an extra `raise` value alongside the existing id, event, payload, environments, and origin fields when invoking a hook module's dispatch function.\n\n**Why**\n\nThis is an internal plumbing change. The evidence doesn't show what `raise` controls or what a hook author would observe differently.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}