deepseek-harness/examples/acp-agent/tests/snapshots/hook-codex-posttool-block/workspace/codex-hooks.json

{
  "hooks": {
    "PostToolUse": [
      {
        "matcher": "bash",
        "hooks": [
          { "type": "command", "command": "echo 'tool output rejected by codex policy: summarize instead' >&2; exit 2" }
        ]
      }
    ]
  }
}
test(hooks): snapshot the CC + Codex hook matrix end-to-end Load both hook bridges in the ACP example (dsh-hooks-claude → ./hooks.json, dsh-hooks-codex → ./codex-hooks.json) so the full-transcript snapshot tier can exercise each dialect against the real app. An absent config file is a silent no-op, so a scenario carries only the file it needs and the other bridge vanishes — verified byte-identical against every pre-existing snapshot. Add a scenario per hook point × its headline Decision outcome, both dialects: UserPromptSubmit block (authored, keyless) + context-fold, PreToolUse deny/ask, PostToolUse block/context, Stop force-continue. The mid-turn scenarios are recorded against the real API with the hook active, so the model's reaction to a denied/blocked/force-continued turn is part of the replayed transcript. SessionStart and SubagentStart are deliberately excluded (detached best-effort inject races the log position — a recorded golden fails 10/10 on its own replay), as is SubagentStop (observe-only, zero transcript footprint — a golden could never be proven to fail). Both stay on the bridges' unit coverage. See docs/rfc/implemented/testing/2026-07-04-hook-snapshot-matrix.md. 2026-07-04 00:40:35 +08:00			`{`
			`"hooks": {`
			`"PostToolUse": [`
			`{`
			`"matcher": "bash",`
			`"hooks": [`
			`{ "type": "command", "command": "echo 'tool output rejected by codex policy: summarize instead' >&2; exit 2" }`
			`]`
			`}`
			`]`
			`}`
			`}`