Respect blocking PostToolUse hooks in code mode

[abhinav-oai]

Summary

Make blocking hook behavior reliable for tools invoked from code mode.

Previously, a PostToolUse hook could block a completed tool result, but code mode would still return the original typed result to JavaScript. The hook appeared blocked in hook telemetry while the running script continued with the result.

This change:

• rejects the nested JavaScript tool promise when PostToolUse blocks
• normalizes decision: "block" and exit code 2 to the same blocking behavior
• surfaces the hook feedback as the rejected promise's error
• adds end-to-end coverage for the relevant PreToolUse and PostToolUse interactions

Hook semantics in code mode

Hook behavior	Code-mode result
PreToolUse block	Reject the promise before the tool executes
PreToolUse updatedInput	Execute the rewritten invocation and return its result
PostToolUse decision: "block"	Execute the tool, then reject the promise with the hook reason
PostToolUse exit code 2	Same behavior as decision: "block"
PostToolUse continue: false	Preserve the existing feedback-only behavior; do not reject the promise

Test coverage

Added or strengthened end-to-end coverage proving that:

• a PreToolUse block rejects the JavaScript promise before execution
• a PreToolUse input rewrite executes only the rewritten command
• JavaScript receives the rewritten command's result
• PostToolUse decision: "block" rejects after the command executes
• PostToolUse exit code 2 has the same behavior
• the hook observes the original completed tool response
• the blocked original result does not reach JavaScript
• existing direct-mode replacement behavior remains intact
• continue: false without a reason produces deterministic fallback feedback

[abhinav-oai]

feedback_message remains the single message channel for both direct and code mode

should_block only determines whether code mode rejects with that message

[abhinav-oai]

continue:false remains feedback-only in code mode just like in direct mode

Only explicit PostToolUse blocking signals (decision:block or exit code 2) set should_block and reject the promise

[pakrym-oai]

can you delete this?