Historical version
This page records design, operation, or validation facts from an earlier release. It is not current V7.17.3 guidance. Start from the documentation hub for current instructions.
V7.2.0 Release Notes¶
Chinese: Chinese documentation
Version: 7.2.0
Key changes¶
- Python 3.11 is now the minimum. Windows and Ubuntu CI both cover Python 3.11 and 3.13, while the installer and complete validator fail closed on older interpreters.
- Complete validation now snapshots the Git index, tracked and untracked content digests, deletions, link types, and interrupt paths before and after execution; validation output must be outside the repository.
- Controlled evolution checks evidence by signal type: model escalation requires actual-model coverage, negative outcomes require terminal-outcome coverage, and unrelated missing telemetry no longer blocks other signals. Coverage is calculated over unique
task_idvalues. - Eleven real Codex host-routing scenarios now verify Plugin installation and enablement, fresh independent tasks, prompts without explicit Skill names, and byte-count/SHA-256 binding of final reports. The result explicitly does not claim a host-signed internal router trace.
- The installer supports Codex CLI 0.152.1's strict local Marketplace schema by removing known-incompatible top-level
owner/interfacefields while preserving unknown external metadata. long-running-task-memoryandmulti-agent-independent-reviewno longer duplicate controlled-evolution guidance; both route tocontrolled-evolution-governanceas the single authoritative entry point.
Unchanged safety boundaries¶
execution_authorization=NONE- Plugin installation still fails closed on unverified Codex CLI versions
- Skill activation does not expand file, Git, environment, production, or data authority
- The automatic sub-agent ceiling remains
gpt-5.6-terra + high
Acceptance boundary¶
Package routing regression proves only static cases and tool contracts and records routing_host_observation=NOT_EVALUATED. Real-host acceptance, complete local installation, remote publication, and post-download artifact verification are recorded separately; a PASS at one stage does not substitute for readback at another.