adapter-drift-audit

# Adapter Drift Audit Audit an IronLint adapter against its coding harness's **current** contract and report drift. **Read-only.** You produce findings and recommendations. You do NOT edit adapter files, you do NOT write the watermark, and you do NOT audit `ironlint` core. The maintainer reads the report and decides what to change. ## When to use - "Is the claude-code adapter still up to date with Claude Code's hooks?" - Periodic adapter maintenance / contract-drift sweeps. - After a harness ships a new version and you want to know what the adapter missed. ## Inputs A harness name as the invocation argument: `claude-code`, `codex`, `pi`, or `opencode`. Each maps to `references/<harness>.md`. Only harnesses with a reference file can be audited. ### Codex specifics Codex is a `PreToolUse`-hook harness like claude-code, but its own docs frame the hook as a *guardrail*, not a hard enforcement boundary — factor that into impact judgments (a codex drift degrades a guardrail; the same drift on claude-code degrades the enforcement point itself). - **Doc sources**: `developers.openai.com/codex/hooks` (hooks reference) and the `codex-rs/hooks/` source tree (ground truth for the exit/JSON decision contract — verified this way once already; see the 2026-07-02 codex adapter design spec under `specs/`). - **Re-verify first**: the `tool_input.command` `apply_patch` envelope shape (`*** Begin Patch` / `*** Add File:` / `*** Update File:` / `*** Delete File:` / `*** End Patch`) that ...