feat: support Codex and Claude local surfaces

packages/casan-devkit/templates/claude/README.md

@@ -6,6 +6,10 @@ installer does this). It wires the four Claude Code lifecycle hooks
 bridge so a developer can type prompts normally while every certified turn still
 carries an H1→H7 trace and an H6 record.
 
+Claude Code shares these project settings across its CLI, official VS Code
+extension, and JetBrains integration. Claude Desktop and claude.ai are separate
+products and are not covered by this local project-hook integration.
+
 - The hook command resolves the repo root via `$CLAUDE_PROJECT_DIR`, so **no
   machine-specific path is committed**.
 - It invokes `.casan/casan-hook.py`. That bootstrap reads project config,

packages/casan-devkit/templates/codex/README.md

@@ -5,6 +5,11 @@ handler calls `.casan/casan-hook.py`, which resolves and verifies the pinned
 global harness before dispatching the Codex adapter. No custom `[casan]` TOML
 keys are required.
 
+This one integration covers the local Codex runtime across the desktop app,
+CLI, and IDE extension. It does not claim coverage for Codex Cloud/Web, where a
+repo-local process and its `.casan/casan-hook.py` bootstrap are not the local
+execution boundary.
+
 Important Codex-specific facts (Spike-20 §4.2):
 
 - **Trust review is mandatory.** Codex loads project-local hooks only after the