fix(hooks): emit permissionDecision under hookSpecificOutput — /freeze and /careful never fired

[jawadakram20]

The bug

careful/bin/check-careful.sh, freeze/bin/check-freeze.sh, and the check-gstack.sh hook generated by bin/gstack-team-init all printed their decision at the top level of the hook JSON:

{"permissionDecision":"deny","message":"..."}

Claude Code reads a PreToolUse decision from hookSpecificOutput.permissionDecision, with the human-readable string in permissionDecisionReason. A top-level permissionDecision matches neither the current schema nor the deprecated decision/reason shape, so it is ignored entirely and the hook is treated as "no opinion".

Impact — these are guardrails that silently did nothing

Skill	Intended	Actual
/freeze	Deny edits outside the freeze boundary	Edits proceeded
/careful	Ask before rm -rf, git reset --hard, DROP TABLE, kubectl delete, …	No prompt
team-mode check-gstack.sh	Block work when gstack isn't installed	Not blocked

/freeze is registered as a PreToolUse hook on Edit and Write specifically to deny them. In each case the user believes a safety net is armed while the tool call proceeds unimpeded — the failure mode is silent.

This was an inconsistency within gstack, not an unknown: the repo's own TypeScript hook (hosts/claude/hooks/question-preference-hook.ts) already emits the correct nested shape.

Why it survived

test/hook-scripts.test.ts asserted on the script's raw stdout:

expect(output.permissionDecision).toBe('ask');

That tests what the script prints, not what Claude Code consumes — so all 39 tests passed against a hook that could never fire. The assertions now read output.hookSpecificOutput?.permissionDecision / .permissionDecisionReason, which fails loudly if the shape regresses.

Verification

bun test test/hook-scripts.test.ts test/team-mode.test.ts test/investigate-freeze-path.test.ts
 67 pass
 0 fail

Manually confirmed the emitted JSON:

$ echo '{"tool_input":{"command":"rm -rf /var/data"}}' | bash careful/bin/check-careful.sh
{"hookSpecificOutput":{"hookEventName":"PreToolUse","permissionDecision":"ask","permissionDecisionReason":"[careful] Destructive: recursive delete (rm -r). This permanently removes files."}}

Allow paths still return {}, and in-boundary freeze edits still return {}.

[trunk-io]

Merging to main in this repository is managed by Trunk.

• To merge this pull request, check the box to the left or comment /trunk merge below.

After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here