{"version":"2.1.257","anchor":"hooks-gain-a-script-hook-type-with-an-external-runner-resu","canonical_anchor":"hooks-gain-a-script-hook-type-with-an-external-runner-resu","heading":"Hooks gain a 'script' hook type with an external-runner result protocol","tier":"use","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/hooks-gain-a-script-hook-type-with-an-external-runner-resu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Hooks gain a 'script' hook type with an external-runner result protocol\n\nHooks gain a script type whose results are recovered from started\/result\/exited markers in the output.\n\nHooks now support a new `hook.type === 'script'` kind. The process output scanner parses `<name> started`, `<name> result <json>`, and `<name> exited <code>` markers from stdout\/stderr to recover a structured result even when the script is launched through an intermediary runner or launcher. Conflicting or malformed markers set a `resultConflict` flag and produce a distinct \"no single verdict\" explanation.\n\n- Area: Hooks\n- Names: `hook.type: script`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 4\/5"}