Why: Implementation changes must be mechanically tied to a successful CLI transport instead of relying on agents to follow prose.
Evidence: Admission tests went RED without apply/admit; 10 admission, 41 agent-exec, and 62 task tests now pass with exact staged-content matching.
Impact: Adds validated transport fast-forwarding and rejects unproven implementation commits while exempting task cards and approved plan/spec paths.
Refs: feature/agent-cli-enforcement
Why: Codex CLI is permitted only after every normal execution profile exhausts three safe attempts, with no host implementation fallback.
Evidence: The emergency RED test lacked the fourth Codex attempt before implementation; 32 controller/history executions now pass.
Impact: Adds one emergency attempt for implementation, repair, and test roles while preserving fail-stop statuses and review isolation.
Refs: feature/agent-cli-enforcement
Why: Each non-Codex execution profile must receive three safe attempts before routing advances.
Evidence: The focused RED test observed one retryme launch before implementation; the controller and history suites now pass 31 executions.
Impact: Retries only unavailable and failed-clean outcomes; existing fail-stop statuses remain immediate.
Refs: feature/agent-cli-enforcement
Why: PR #567 CI runs without a global Git user identity, causing every successful agent transport commit to fail with exit 128.
Evidence: The focused no-identity regression plus AgentExecControllerTests and AgentExecHistoryTests pass (30 executions total); git diff --check passes.
Impact: Supplies a deterministic non-secret identity only to git commit-tree; routing, receipts, and transport validation are unchanged.
Refs: #567
Why: retain which CLI handled each task so routing can improve from real outcomes over time
Evidence: AgentExecHistoryTests and git diff --check
Impact: appends sanitized source-external JSONL records without changing run outcomes
Refs: feature/goal-first-delivery
weichen