thanhnvandClaude Opus 4.8
4bb184b935
Wave 0 + Wave 1 core of the transparent agentic-client integration: a
developer types prompts normally in Claude Code / Codex while every
certified turn still carries a full H1->H7 trace and an H6 record.
- agentic_bridge.py: stdlib-only lifecycle state machine (begin/pre-tool/
post-tool/telemetry/finalize/abort + report/doctor). Single-model
invariant (never calls a model), fail-closed at the side-effect point,
admission TTL + canonical-project/session binding, atomic state under
.specify/state/agentic-sessions/, secret redaction, null-not-zero H6.
- agentic-lifecycle.schema.json: client-agnostic JSON contract.
- adapters/claude-code + adapters/codex: thin hook renderers + config
templates that call the core bridge.
- phase-agentic-bridge-tests.sh: C1-C12 acceptance + threat suite (30/30).
- devkit templates/{claude,codex} + windows/install-agentic.ps1
(install/doctor/uninstall with manifest, path-safe).
- docs/casan Windows + security/bypass guides; plan status -> IMPLEMENTED.
- harden generate-agentops-dashboard.py aggregation against null H6 costs.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
CASAN Codex adoption template (Plan-20)
Drop hooks.json → .codex/hooks.json and merge config.toml into
.codex/config.toml in the target repo (the installer does this). It wires the
Codex lifecycle hooks to the CASAN agentic bridge via the thin renderer
packages/casan-harness/adapters/codex/codex_hook.py.
Important Codex-specific facts (Spike-20 §4.2):
- Trust review is mandatory. Codex loads project-local hooks only after the
user accepts a trust prompt. Run
casan doctor --client codex(or the bridgedoctorop) to confirm the trust/onboarding state — it is never hidden from a member. - Tool hooks are a guardrail, not a complete boundary. Hosted/specialized tools may fall outside hook coverage; a turn that uses an uncovered tool is downgraded (non-certified), not silently certified.
- Token/cost source is not assumed. Unless Codex supplies a stable usage
source, H6 records the number as
nullwithtelemetry_quality=partial— it is never invented (Spike-20 X6). - For enterprise enforcement, pin hooks via managed policy so a member cannot
disable them and set
CASAN_AGENTIC_INTEGRATION_MODE=managed_hookthrough the managed environment (not the committed config).
The command contract is stable (stdin JSON → exit 0 allow / exit 2 block); the
exact Codex payload key names are pinned during the Wave-3 payload spike, which
is why codex_hook.py reads several field aliases defensively.