@webpieces/ai-hook-rules 0.4.702 → 0.4.704

package/src/adapters/detect-ai.js

@@ -0,0 +1,47 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.AI_TYPE_SH = exports.AI_TYPE_TOKEN_SH = void 0;
+exports.detectAiType = detectAiType;
+/**
+ * THE discriminator, and the only one. Codex's PreToolUse envelope carries a REQUIRED `turn_id`;
+ * Claude Code's has no such key. Everything else in the two envelopes is the same key names
+ * (`hook_event_name`, `tool_name`, `tool_input`, `cwd`, `session_id`, `transcript_path`), which is
+ * exactly why one positive key is the whole test rather than a shape heuristic.
+ *
+ * Exported as a TWIN — an sh fragment and a JS predicate — because L0 has two halves that must
+ * answer the identical question: the rendered POSIX-sh shim (which has no JSON parser and scrapes
+ * text) and this binary (which has the parsed object). That is the same pattern
+ * ../bin/l0-allowlist.ts already uses for `L0_ALLOW_ERE_SH` / `L0_ALLOW_JS`, and detect-ai.spec.ts
+ * asserts the two agree over a corpus the same way.
+ *
+ * The sh half is an APPROXIMATION and says so out loud: it matches the six bytes `"turn_id":` in the
+ * raw payload, so a Claude payload that happened to embed that exact quoted-key-with-colon spelling
+ * inside a string value would be misread as Codex. Matching a JSON key from sh without a JSON parser
+ * cannot do better, the spelling is contrived (an agent grepping for `turn_id` types it bare), and
+ * the consequence of the miss is bounded: the Codex path is a SUPERSET of guards, never fewer.
+ *
+ * NOT WIRED INTO THE RENDERED SHIM IN THIS CHANGE. `committedShimStale()` compares the committed
+ * `.claude/webpieces/ai-hook.sh` against `renderShim()` of the INSTALLED release, so changing the
+ * renderer and regenerating the artifact together makes L0 fault S fire for everyone mid-upgrade.
+ * The constant ships here first; the shim consumes it a release later.
+ */
+exports.AI_TYPE_TOKEN_SH = '"turn_id":';
+/**
+ * Sets `AI` to the literal `AiType` value — `codex` or `claude-code` — from `$PAYLOAD`. The values
+ * are the SAME strings the TypeScript union carries, so the twin test can compare them byte for byte
+ * instead of translating between two vocabularies (translation is where twins drift).
+ */
+exports.AI_TYPE_SH = `case "$PAYLOAD" in *'${exports.AI_TYPE_TOKEN_SH}'*) AI=codex ;; *) AI=claude-code ;; esac`;
+/**
+ * JS twin of AI_TYPE_SH. Asks the precise question the sh half approximates: is `turn_id` a key of
+ * the top-level envelope?
+ */
+// webpieces-disable no-any-unknown -- the argument IS unparsed JSON from another process's stdout; naming a type here would assert a shape we have not yet established, which is the question this function exists to answer
+// webpieces-disable no-function-outside-class -- twin of an sh fragment in the dependency-free adapter layer; it must stay callable on a tree too broken to build a DI container, exactly like isAllowed()
+function detectAiType(payload) {
+    if (payload === null || typeof payload !== 'object')
+        return 'claude-code';
+    // webpieces-disable no-any-unknown -- narrowing the same unparsed JSON; the index signature is the widest true statement about it
+    return 'turn_id' in payload ? 'codex' : 'claude-code';
+}
+//# sourceMappingURL=detect-ai.js.map

package/src/adapters/detect-ai.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"detect-ai.js","sourceRoot":"","sources":["../../../../../../packages/tooling/ai-hook-rules/src/adapters/detect-ai.ts"],"names":[],"mappings":";;;AAwCA,oCAIC;AA1CD;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACU,QAAA,gBAAgB,GAAG,YAAY,CAAC;AAE7C;;;;GAIG;AACU,QAAA,UAAU,GAAG,wBAAwB,wBAAgB,2CAA2C,CAAC;AAE9G;;;GAGG;AACH,6NAA6N;AAC7N,2MAA2M;AAC3M,SAAgB,YAAY,CAAC,OAAgB;IACzC,IAAI,OAAO,KAAK,IAAI,IAAI,OAAO,OAAO,KAAK,QAAQ;QAAE,OAAO,aAAa,CAAC;IAC1E,kIAAkI;IAClI,OAAO,SAAS,IAAK,OAAmC,CAAC,CAAC,CAAC,OAAO,CAAC,CAAC,CAAC,aAAa,CAAC;AACvF,CAAC","sourcesContent":["import { AiType } from '../core/agent-event';\n\n/**\n * THE discriminator, and the only one. Codex's PreToolUse envelope carries a REQUIRED `turn_id`;\n * Claude Code's has no such key. Everything else in the two envelopes is the same key names\n * (`hook_event_name`, `tool_name`, `tool_input`, `cwd`, `session_id`, `transcript_path`), which is\n * exactly why one positive key is the whole test rather than a shape heuristic.\n *\n * Exported as a TWIN — an sh fragment and a JS predicate — because L0 has two halves that must\n * answer the identical question: the rendered POSIX-sh shim (which has no JSON parser and scrapes\n * text) and this binary (which has the parsed object). That is the same pattern\n * ../bin/l0-allowlist.ts already uses for `L0_ALLOW_ERE_SH` / `L0_ALLOW_JS`, and detect-ai.spec.ts\n * asserts the two agree over a corpus the same way.\n *\n * The sh half is an APPROXIMATION and says so out loud: it matches the six bytes `\"turn_id\":` in the\n * raw payload, so a Claude payload that happened to embed that exact quoted-key-with-colon spelling\n * inside a string value would be misread as Codex. Matching a JSON key from sh without a JSON parser\n * cannot do better, the spelling is contrived (an agent grepping for `turn_id` types it bare), and\n * the consequence of the miss is bounded: the Codex path is a SUPERSET of guards, never fewer.\n *\n * NOT WIRED INTO THE RENDERED SHIM IN THIS CHANGE. `committedShimStale()` compares the committed\n * `.claude/webpieces/ai-hook.sh` against `renderShim()` of the INSTALLED release, so changing the\n * renderer and regenerating the artifact together makes L0 fault S fire for everyone mid-upgrade.\n * The constant ships here first; the shim consumes it a release later.\n */\nexport const AI_TYPE_TOKEN_SH = '\"turn_id\":';\n\n/**\n * Sets `AI` to the literal `AiType` value — `codex` or `claude-code` — from `$PAYLOAD`. The values\n * are the SAME strings the TypeScript union carries, so the twin test can compare them byte for byte\n * instead of translating between two vocabularies (translation is where twins drift).\n */\nexport const AI_TYPE_SH = `case \"$PAYLOAD\" in *'${AI_TYPE_TOKEN_SH}'*) AI=codex ;; *) AI=claude-code ;; esac`;\n\n/**\n * JS twin of AI_TYPE_SH. Asks the precise question the sh half approximates: is `turn_id` a key of\n * the top-level envelope?\n */\n// webpieces-disable no-any-unknown -- the argument IS unparsed JSON from another process's stdout; naming a type here would assert a shape we have not yet established, which is the question this function exists to answer\n// webpieces-disable no-function-outside-class -- twin of an sh fragment in the dependency-free adapter layer; it must stay callable on a tree too broken to build a DI container, exactly like isAllowed()\nexport function detectAiType(payload: unknown): AiType {\n    if (payload === null || typeof payload !== 'object') return 'claude-code';\n    // webpieces-disable no-any-unknown -- narrowing the same unparsed JSON; the index signature is the widest true statement about it\n    return 'turn_id' in (payload as Record<string, unknown>) ? 'codex' : 'claude-code';\n}\n"]}

package/src/adapters/hook-core.d.ts

@@ -3,10 +3,10 @@ export type { HookMode };
 export type ShimStaleDecision = 'allow-cure' | 'pass' | 'deny';
 export declare function shimStaleRecoveryDecision(toolName: string, command: string, filePath: string): ShimStaleDecision;
 /**
- * Shared entry point for all three Claude Code PreToolUse adapters. `mode` selects which tool kinds
- * to validate; payloads outside the mode's scope pass through (emitAllow). Blocks by emitting a
- * PreToolUse `permissionDecision:"deny"` JSON on stdout (exit 0) — see claude-code-response.ts. Fails
- * CLOSED on any unexpected crash (emits a deny) so a broken hook never silently lets an edit through,
- * and the reason now surfaces in the Claude Code UI instead of being hidden on a stderr+exit-2 block.
+ * Shared entry point for every PreToolUse adapter. `mode` selects which tool kinds to validate;
+ * payloads outside the mode's scope pass through (emitAllow). Blocks by emitting a PreToolUse
+ * `permissionDecision:"deny"` JSON on stdout (exit 0) — see agent-response.ts. Fails CLOSED on any
+ * unexpected crash (emits a deny) so a broken hook never silently lets an edit through, and the reason
+ * surfaces in the agent's UI instead of being hidden on a stderr+exit-2 block.
  */
 export declare function runMain(mode: HookMode): Promise<void>;

package/src/adapters/hook-core.js

@@ -13,20 +13,18 @@ const load_config_1 = require("../core/load-config");
 const rules_config_1 = require("@webpieces/rules-config");
 const types_1 = require("../core/types");
 const to_error_1 = require("../core/to-error");
-const claude_code_response_1 = require("./claude-code-response");
+const agent_response_1 = require("./agent-response");
+const agent_payload_1 = require("./agent-payload");
+const agent_adapters_1 = require("./agent-adapters");
+const codex_subagent_guard_1 = require("./codex-subagent-guard");
 const shim_1 = require("../bin/shim");
 const shim_deny_reason_1 = require("../bin/shim-deny-reason");
 const hook_registration_1 = require("../bin/hook-registration");
 const l0_matrix_1 = require("../core/l0-matrix");
 const log_stream_1 = require("../core/log-stream");
 const l0_fault_codes_1 = require("../core/l0-fault-codes");
-const HANDLED_FILE_TOOLS = new Set(['Write', 'Edit', 'MultiEdit']);
-// Read-only tools carry NO guard or code rule, but the guards hook owns the per-invocation audit log
-// (the `calls/` stream). When the guards matcher includes these (see setup.ts GUARDS_HOOK), a
-// log-and-allow fast path records every file the AI opens — so a human can later inspect whether it
-// read a project's design.json BEFORE editing the project. Never blocked. Scoped to Read for now;
-// widen (Grep/Glob/NotebookRead) later if desired.
-const READ_ONLY_TOOLS = new Set(['Read']);
+const ADAPTERS = new agent_adapters_1.AgentAdapters();
+const SUBAGENT_GUARD = new codex_subagent_guard_1.CodexSubagentSharedTreeGuard();
 function readStdin() {
     return new Promise((resolve) => {
         let data = '';
@@ -38,44 +36,6 @@ function readStdin() {
             resolve('');
     });
 }
-function safeParse(raw) {
-    if (!raw || raw.trim() === '')
-        return null;
-    // eslint-disable-next-line @webpieces/no-unmanaged-exceptions
-    try {
-        return JSON.parse(raw);
-    }
-    catch (err) {
-        const error = (0, to_error_1.toError)(err);
-        throw new types_1.InformAiError(`Malformed hook input from Claude Code stdin: ${error.message}`, { cause: error });
-    }
-}
-function normalizeToolKind(toolName) {
-    if (HANDLED_FILE_TOOLS.has(toolName))
-        return toolName;
-    return null;
-}
-function normalizeToolInput(toolKind, toolInput) {
-    const filePath = toolInput.file_path;
-    if (!filePath)
-        return null;
-    if (toolKind === 'Write') {
-        return new types_1.NormalizedToolInput(filePath, [
-            new types_1.NormalizedEdit('', toolInput.content || ''),
-        ]);
-    }
-    if (toolKind === 'Edit') {
-        return new types_1.NormalizedToolInput(filePath, [
-            new types_1.NormalizedEdit(toolInput.old_string || '', toolInput.new_string || ''),
-        ]);
-    }
-    if (toolKind === 'MultiEdit') {
-        const raw = Array.isArray(toolInput.edits) ? toolInput.edits : [];
-        const edits = raw.map((e) => new types_1.NormalizedEdit(e.old_string || '', e.new_string || ''));
-        return new types_1.NormalizedToolInput(filePath, edits);
-    }
-    return null;
-}
 // The rule name for a block's audit line: the FIRST rule the report cites, or `fallback` when the
 // report opens with no `[rule]` header (a hand-written guard message). Comma-joined when a report
 // cites several, so `rule=` never silently drops one.
@@ -84,14 +44,23 @@ function blockingRule(report, fallback) {
     const names = (0, rejection_log_1.extractRuleNames)(report);
     return names.length > 0 ? names.join(',') : fallback;
 }
-function handleBash(payload, cwd, mode) {
-    const command = payload.tool_input.command;
-    if (!command || command.trim() === '') {
-        (0, claude_code_response_1.emitAllow)();
+// webpieces-disable no-function-outside-class -- sibling of handleRead()/handleFileTool() in this module; the adapter is module-scope functions by design
+function handleBash(event, cwd, mode) {
+    const command = event.bash === null ? '' : event.bash.command;
+    if (command.trim() === '') {
+        (0, agent_response_1.emitAllow)();
+    }
+    // READ PARITY, and it can only ever be reached from a Codex event: the adapter leaves `reads`
+    // empty for Claude Code, which has a real `Read` tool and its own fast path. A Codex read arrives
+    // as `Bash` running a pager, so without this the read guard and the `calls/` audit trail see none
+    // of them. The command is STILL run through the bash guards below — this adds a verdict, it never
+    // replaces one.
+    for (const readPath of event.reads) {
+        handleRead(event, readPath, cwd, mode);
     }
     const result = (0, runner_1.runBash)(command, cwd, mode);
     if (!result) {
-        (0, claude_code_response_1.emitAllow)();
+        (0, agent_response_1.emitAllow)();
     }
     // NO DECISION LINE HERE. This used to write a generic `bash-guard` line because a Bash deny once
     // had no audit trail at all — but every layer now records its own: L1 into `L1-location/` with its
@@ -101,9 +70,10 @@ function handleBash(payload, cwd, mode) {
     // the guard actually judged, so a `cd`-relocated command scattered one block across two different
     // `.webpieces` directories.
     //
-    // Bash deny → pass 'Bash' so denyJson adds the ANSI-red systemMessage (the only field a Bash deny
-    // shows the human; permissionDecisionReason is invisible on Bash). See claude-code-response.ts.
-    (0, claude_code_response_1.emitDeny)(result.report, 'Bash', blockingRule(result.report, 'bash-guard'), result.fault);
+    // Bash deny → the event's kind is 'Bash', so denyJson adds the ANSI-red systemMessage (the only
+    // field a Bash deny shows the human; permissionDecisionReason is invisible on Bash). See
+    // agent-response.ts.
+    (0, agent_response_1.emitDeny)(event, result.report, blockingRule(result.report, 'bash-guard'), result.fault);
 }
 /**
  * The read-scoped guard pass. Returns normally to ALLOW; only calls emitDeny when the guard fires.
@@ -114,7 +84,7 @@ function handleBash(payload, cwd, mode) {
  * path deliberately inverts the policy: a broken read-guard degrades to a no-op, never to a wedge.
  */
 // webpieces-disable no-function-outside-class -- sibling of handleBash()/handleFileTool() in this module; the adapter is module-scope functions by design
-function handleRead(filePath, cwd, mode) {
+function handleRead(event, filePath, cwd, mode) {
     if (filePath === '')
         return;
     let result = null;
@@ -130,19 +100,36 @@ function handleRead(filePath, cwd, mode) {
     if (!result)
         return;
     (0, rejection_log_1.logRejection)('Read', new types_1.NormalizedToolInput(filePath, []), result, cwd);
-    (0, claude_code_response_1.emitDeny)(result.report, 'Read', blockingRule(result.report, 'read-guard'), result.fault);
+    (0, agent_response_1.emitDeny)(event, result.report, blockingRule(result.report, 'read-guard'), result.fault);
 }
-function handleFileTool(payload, cwd, mode) {
-    const toolKind = normalizeToolKind(payload.tool_name);
-    if (!toolKind) {
-        (0, claude_code_response_1.emitAllow)();
+/**
+ * The file/edit pipeline, run once per file the call touches.
+ *
+ * `event.files` is a LIST because ONE Codex `apply_patch` carries many files with mixed operations.
+ * A Claude Code event always has exactly one entry, so the loop runs once and the behaviour is the
+ * single-file behaviour it has always had.
+ */
+// webpieces-disable no-function-outside-class -- sibling of handleBash()/handleRead() in this module; the adapter is module-scope functions by design
+function handleFileTool(event, cwd, mode) {
+    if (event.files.length === 0) {
+        (0, agent_response_1.emitAllow)();
     }
-    const input = normalizeToolInput(toolKind, payload.tool_input);
-    if (!input) {
-        (0, claude_code_response_1.emitAllow)();
+    // A Codex SUBAGENT writing into the tree it shares with its coordinator. Returns null for every
+    // Claude Code event — that harness can hand a subagent its own worktree, and does.
+    const subagentBlock = SUBAGENT_GUARD.check(event, new rules_config_1.RepoRootFinder().resolveRepoRoot(cwd));
+    if (subagentBlock) {
+        (0, agent_response_1.emitDeny)(event, subagentBlock.report, codex_subagent_guard_1.CODEX_SUBAGENT_RULE, subagentBlock.fault);
     }
+    for (const file of event.files) {
+        handleOneFile(event, file, cwd, mode);
+    }
+    (0, agent_response_1.emitAllow)();
+}
+// webpieces-disable no-function-outside-class -- sibling of handleBash()/handleFileTool() in this module; the adapter is module-scope functions by design
+function handleOneFile(event, file, cwd, mode) {
+    const input = file.input;
     // Always allow edits to webpieces.config.json — it's the fix target when the config is broken.
-    // This exits BEFORE run(), so feature-branch-guard never sees a config edit; record that so the
+    // This returns BEFORE run(), so feature-branch-guard never sees a config edit; record that so the
     // audit trail explains why a config edit on a bad branch was not blocked (see decision-log.ts).
     if (path.basename(input.filePath) === load_config_1.CONFIG_FILENAME) {
         if (mode !== 'rules') {
@@ -150,22 +137,21 @@ function handleFileTool(payload, cwd, mode) {
             // root, not the AI's cwd — resolve it so a config edit from a subdir doesn't create a
             // stray `<subdir>/.webpieces` tree.
             const root = new rules_config_1.RepoRootFinder().resolveRepoRoot(cwd);
-            (0, decision_log_1.logGuardDecision)(root, new decision_log_1.GuardDecision('feature-branch-guard', toolKind, input.filePath, (0, decision_log_1.branchForLog)(root), 'ALLOW_EXEMPT', 'config-bypass (feature-branch-guard skipped)', '-', l0_fault_codes_1.L0_FAULT_NONE, (0, decision_log_1.matrixL2Row)('config-bypass (feature-branch-guard skipped)')));
+            (0, decision_log_1.logGuardDecision)(root, new decision_log_1.GuardDecision('feature-branch-guard', file.toolKind, input.filePath, (0, decision_log_1.branchForLog)(root), 'ALLOW_EXEMPT', 'config-bypass (feature-branch-guard skipped)', '-', l0_fault_codes_1.L0_FAULT_NONE, (0, decision_log_1.matrixL2Row)('config-bypass (feature-branch-guard skipped)')));
             // The guard's own refresh trigger lives inside its check(), which we skip here — so warm
             // the cache directly, otherwise a session that only edits webpieces.config.json never
             // refreshes the sync status. Fire-and-forget; never blocks the edit.
             (0, main_sync_refresh_1.triggerMainSyncRefresh)(root, (0, main_sync_timeout_1.branchStateHangTimeoutFor)(cwd));
         }
-        (0, claude_code_response_1.emitAllow)();
-    }
-    const result = (0, runner_1.run)(toolKind, input, cwd, mode);
-    if (!result) {
-        (0, claude_code_response_1.emitAllow)();
+        return;
     }
-    (0, rejection_log_1.logRejection)(toolKind, input, result, cwd);
-    // File-tool deny → pass the Write/Edit/MultiEdit kind so denyJson omits systemMessage (the reason
-    // already renders red natively for these tools). See claude-code-response.ts.
-    (0, claude_code_response_1.emitDeny)(result.report, toolKind, blockingRule(result.report, 'file-guard'), result.fault);
+    const result = (0, runner_1.run)(file.toolKind, input, cwd, mode);
+    if (!result)
+        return;
+    (0, rejection_log_1.logRejection)(file.toolKind, input, result, cwd);
+    // File-tool deny → the event's kind is 'File', so denyJson omits systemMessage (the reason
+    // already renders red natively for these tools). See agent-response.ts.
+    (0, agent_response_1.emitDeny)(event, result.report, blockingRule(result.report, 'file-guard'), result.fault);
 }
 // webpieces-disable no-function-outside-class -- pure decision helper beside the adapter's other module-scope functions; exported for direct unit testing.
 function shimStaleRecoveryDecision(toolName, command, filePath) {
@@ -187,8 +173,13 @@ function shimStaleRecoveryDecision(toolName, command, filePath) {
 // shimStaleRecoveryDecision): the whole L0 allowlist, any Read, and editing webpieces.config.json. We deny +
 // tell the AI; we do NOT silently rewrite the file under it. 'rules' hook skips it (guards owns the
 // shim). Returns normally (pass / nothing to do) or exits via emitAllow/emitDeny.
+//
+// It asks the allowlist about the RAW WIRE FIELDS, not about the normalized event, and that ordering is
+// deliberate: L0 has to hold on a tree too broken to trust anything above it, including the adapters.
+// The raw fields are the same key names in both harnesses (measured), so one reading serves both, and
+// the answer cannot change because a normalizer changed. `event` is here only to decorate the deny.
 // webpieces-disable no-function-outside-class -- sibling of handleBash()/handleFileTool() in this module; the adapter is module-scope functions by design
-function enforceCommittedShim(payload, cwd, mode) {
+function enforceCommittedShim(payload, event, cwd, mode) {
     // ONE root for the whole decision, resolved from the RUNNING MODULE (governingShimRoot), never from
     // `cwd`: the shim file we compare and the renderShim() we compare it TO must come from the same
     // install, or the check straddles two trees and can never converge (see governingShimRoot's header).
@@ -210,7 +201,7 @@ function enforceCommittedShim(payload, cwd, mode) {
     if (decision === 'pass')
         return;
     if (decision === 'allow-cure')
-        (0, claude_code_response_1.emitAllow)();
+        (0, agent_response_1.emitAllow)();
     // Drop the L0 matrix doc where the AI can read it and point the deny at it — a Read is entry 1 of
     // the same allowlist, so the pointer is always followable. Best-effort: no doc → no pointer.
     const root = new rules_config_1.RepoRootFinder().resolveRepoRoot(cwd);
@@ -224,96 +215,109 @@ function enforceCommittedShim(payload, cwd, mode) {
     // L0 fault S in GUARD_MATRIX.md's codebook — named as the blocking rule so the invocation line
     // says WHAT stopped the call, not merely that something did, and stamped as `fault=S` so the same
     // grep finds it here as in the sh half's `L0-shim/` stream.
-    // A subagent is discriminated by `agent_id`, which Claude Code populates on stdin only off the main
-    // loop (main falls back to the session id, so the field is absent). Its cure differs: the hooks
+    // A subagent is discriminated by `agent_id`, which BOTH harnesses populate on stdin only off the
+    // main loop (main falls back to the session id / leaves it empty). Its cure differs: the hooks
     // blocking it resolve through CLAUDE_PROJECT_DIR, which names the MAIN tree.
-    const inSubagent = (payload.agent_id ?? '') !== '';
-    (0, claude_code_response_1.emitDeny)((0, shim_deny_reason_1.shimStaleDenyReason)((0, shim_1.installedShimRulesVersion)(), shimRoot ?? '', drifted, inSubagent) + (0, l0_matrix_1.guardMatrixPointer)(docPath), payload.tool_name, 'committed-shim-stale', l0_fault_codes_1.L0_FAULT_SHIM_STALE);
+    const inSubagent = event.agentId !== '';
+    (0, agent_response_1.emitDeny)(event, (0, shim_deny_reason_1.shimStaleDenyReason)((0, shim_1.installedShimRulesVersion)(), shimRoot ?? '', drifted, inSubagent) + (0, l0_matrix_1.guardMatrixPointer)(docPath), 'committed-shim-stale', l0_fault_codes_1.L0_FAULT_SHIM_STALE);
 }
 /**
- * Shared entry point for all three Claude Code PreToolUse adapters. `mode` selects which tool kinds
- * to validate; payloads outside the mode's scope pass through (emitAllow). Blocks by emitting a
- * PreToolUse `permissionDecision:"deny"` JSON on stdout (exit 0) — see claude-code-response.ts. Fails
- * CLOSED on any unexpected crash (emits a deny) so a broken hook never silently lets an edit through,
- * and the reason now surfaces in the Claude Code UI instead of being hidden on a stderr+exit-2 block.
+ * Shared entry point for every PreToolUse adapter. `mode` selects which tool kinds to validate;
+ * payloads outside the mode's scope pass through (emitAllow). Blocks by emitting a PreToolUse
+ * `permissionDecision:"deny"` JSON on stdout (exit 0) — see agent-response.ts. Fails CLOSED on any
+ * unexpected crash (emits a deny) so a broken hook never silently lets an edit through, and the reason
+ * surfaces in the agent's UI instead of being hidden on a stderr+exit-2 block.
  */
 async function runMain(mode) {
-    // Captured from the payload as soon as it parses so the fail-closed catch below can tell denyJson
-    // which tool it is denying — a crash on a Bash call still gets the visible red systemMessage, a
-    // crash on a file tool does not. Empty (before parse / malformed input) → treated as non-Bash.
-    let toolName = '';
+    // Captured as soon as the ENVELOPE parses so the fail-closed catch below can tell denyJson which
+    // kind of call it is denying — a crash on a Bash call still gets the visible red systemMessage, a
+    // crash on a file tool does not. Null (before parse / malformed input) → treated as non-Bash.
+    let event = null;
     // eslint-disable-next-line @webpieces/no-unmanaged-exceptions
     try {
         const raw = await readStdin();
-        const payload = safeParse(raw);
+        const payload = new agent_payload_1.AgentPayloadParser().parse(raw);
         if (!payload) {
-            (0, claude_code_response_1.emitAllow)();
+            (0, agent_response_1.emitAllow)();
         }
-        toolName = payload.tool_name;
+        // The envelope shape first: it reads only `tool_name` and the identity fields, so it cannot
+        // fail, and it is what the crash path needs. The full normalization below reads `tool_input`
+        // and CAN fail (a malformed Codex patch envelope denies rather than being half-understood).
+        event = ADAPTERS.envelope(payload);
         // BEFORE enforceCommittedShim(), which can itself write a BLOCK line. See LogStream for why
         // all three of session/agent/hook are needed to keep concurrent writers off one file.
-        log_stream_1.logStream.identify(new log_stream_1.StreamIdentity(payload.session_id ?? '', payload.agent_id ?? '', mode));
+        log_stream_1.logStream.identify(new log_stream_1.StreamIdentity(event.sessionId, event.agentId, mode));
         // Prefer the payload cwd (the AI's actual working dir, follows a persisted `cd`) over
         // process.cwd(); they match today, but the payload is the authoritative signal and stays
         // correct if the hook is ever invoked from a fixed dir (e.g. via $CLAUDE_PROJECT_DIR).
         const cwd = payload.cwd ?? process.cwd();
         // Committed-shim self-guard: blocks real work while the committed shim is stale, but keeps the
         // recovery path open (cures, reads, config edit). See enforceCommittedShim / shimStaleRecoveryDecision.
-        enforceCommittedShim(payload, cwd, mode);
+        enforceCommittedShim(payload, event, cwd, mode);
+        event = ADAPTERS.toEvent(payload, cwd);
         // Read-only tools (Read): audit-log, warm the main-sync cache, then run the ONE read-scoped
         // guard (read-stale-guard) and allow. Runs BEFORE the general rule engine — no code-style rule
         // ever sees a Read, and the only way this path can deny is a stale `main`.
         // The audit trail still records every file the AI opened (see setup.ts).
-        if (READ_ONLY_TOOLS.has(payload.tool_name)) {
-            const readPath = payload.tool_input.file_path ?? '';
+        if (event.kind === 'Read') {
+            const readPath = event.reads.length > 0 ? event.reads[0] : '';
             if (mode !== 'rules') {
-                decision_log_1.invocationLog.begin(cwd, payload.tool_name, readPath);
+                decision_log_1.invocationLog.begin(cwd, event.rawToolName, readPath);
                 // Reads vastly outnumber edits, so refreshing here is what actually keeps the shared
                 // main-sync cache warm for feature-branch-guard. Detached; never slows the read.
                 (0, main_sync_refresh_1.triggerMainSyncRefresh)(cwd, (0, main_sync_timeout_1.branchStateHangTimeoutFor)(cwd));
             }
-            handleRead(readPath, cwd, mode);
-            (0, claude_code_response_1.emitAllow)();
+            handleRead(event, readPath, cwd, mode);
+            (0, agent_response_1.emitAllow)();
         }
         // Per-invocation guard log (the `calls/` stream): tool + command/file + live branch +
         // main-sync-status snapshot, on EVERY guards call, for later cleanup automation. Best-effort;
         // never blocks the call. (The committed shim is no longer silently healed here — a mismatch is
         // reported by the self-guard above, not rewritten out from under the AI.)
         if (mode !== 'rules') {
-            const target = payload.tool_name === 'Bash' ? (payload.tool_input.command ?? '') : (payload.tool_input.file_path ?? '');
-            decision_log_1.invocationLog.begin(cwd, payload.tool_name, target);
+            decision_log_1.invocationLog.begin(cwd, event.rawToolName, logTarget(event));
         }
-        if (payload.tool_name === 'Bash') {
+        if (event.kind === 'Bash') {
             // No code-style rule is bash-scoped, so the rules hook ignores Bash.
             if (mode === 'rules') {
-                (0, claude_code_response_1.emitAllow)();
+                (0, agent_response_1.emitAllow)();
             }
-            handleBash(payload, cwd, mode);
+            handleBash(event, cwd, mode);
             return;
         }
         // File payloads run in 'rules' (code-style), 'guards' (file-scoped guards like
         // feature-branch-guard), and 'all'. The runner filters to the right category.
-        handleFileTool(payload, cwd, mode);
+        handleFileTool(event, cwd, mode);
     }
     catch (err) {
         const error = (0, to_error_1.toError)(err);
-        denyForCrash(error, toolName);
+        denyForCrash(error, event);
     }
 }
+// What the `calls/` audit line names as the call's target: the command for a shell call, else the first
+// file it touches. A Codex `apply_patch` touching several files names the first — the rejection log and
+// the decision log carry the rest, per file.
+// webpieces-disable no-function-outside-class -- sibling of the module-scope hook entry points in this adapter
+function logTarget(event) {
+    if (event.kind === 'Bash')
+        return event.bash === null ? '' : event.bash.command;
+    return event.files.length > 0 ? event.files[0].input.filePath : '';
+}
 /**
  * The fail-closed boundary for anything that escaped the hook body. An escaped RuleFailError (a rule
- * that threw past the runner's per-rule catch) or an InformAiError (bad config/stdin) both carry an
- * AI-readable message; anything else is an unexpected bug. All three DENY and surface their reason,
- * because a hook that crashed established nothing and must never be read as an allow.
+ * that threw past the runner's per-rule catch) or an InformAiError (bad config/stdin, or a Codex patch
+ * envelope this parser refuses to guess at) both carry an AI-readable message; anything else is an
+ * unexpected bug. All three DENY and surface their reason, because a hook that crashed established
+ * nothing and must never be read as an allow.
  */
 // webpieces-disable no-function-outside-class -- sibling of the module-scope hook entry points in this adapter; a lone class for one terminal boundary would break the file's shape
-function denyForCrash(error, toolName) {
+function denyForCrash(error, event) {
     if (error instanceof types_1.RuleFailError) {
-        (0, claude_code_response_1.emitDeny)((0, rules_config_1.renderRuleFailForAi)(error), toolName, 'rule-crash');
+        (0, agent_response_1.emitDeny)(event, (0, rules_config_1.renderRuleFailForAi)(error), 'rule-crash');
     }
     if (error instanceof types_1.InformAiError) {
-        (0, claude_code_response_1.emitDeny)(error.message, toolName, 'bad-config-or-stdin');
+        (0, agent_response_1.emitDeny)(event, error.message, 'bad-config-or-stdin');
     }
-    (0, claude_code_response_1.emitDeny)(`[ai-hooks] hook crashed unexpectedly — failing closed: ${error.message}`, toolName, 'hook-crash');
+    (0, agent_response_1.emitDeny)(event, `[ai-hooks] hook crashed unexpectedly — failing closed: ${error.message}`, 'hook-crash');
 }
 //# sourceMappingURL=hook-core.js.map