T-OKV9-claude-code-agent-driver-and-the-sdlc-agent-call-verb
State: planning/proposed · Impact: medium · Complexity: large
The agent executor has a driver seam and no driver. The implement step and the review prompts need a Claude Code driver that lives outside the engine crate.
Proposed
Section titled “Proposed”sdlc agent call --output json over the agent-call package runs one harness session and streams
progress. A registered driver in the SDLC adapter maps the executor’s start, progress, heartbeat,
and finished events onto it.
Acceptance criteria
Section titled “Acceptance criteria”- AC-1: A judgment DAG with the Claude Code driver completes end to end on a fixture, with heartbeats extending the lease.
- AC-2: The driver is registered by name from outside the foreman crate; the crate’s vendor-name test still passes.
Out of scope
Section titled “Out of scope”- Other harnesses.
Dependencies
Section titled “Dependencies”Depends on
Section titled “Depends on”T-FW23-rebase-and-merge-the-foreman-implementation-stack-bottom-up