Background
The current BDD scenarios in tests/bdd_repository_cloning.rs exercise clone_repository_into_workspace (an internal, feature-gated engine function) via a mockall mock of ContainerExecClient. The stable public API surface (RepositoryRef, BranchName, WorkspacePath, and podbot::api::clone_repository_into_workspace) is not exercised end-to-end.
Required action
Redesign the BDD helper layer so that the When step invokes only the stable public API, passing already-constructed domain value objects. Infrastructure wiring should be injected via an in-process test double that implements the public adapter interface, not the internal ContainerExecClient.
References
Background
The current BDD scenarios in
tests/bdd_repository_cloning.rsexerciseclone_repository_into_workspace(an internal, feature-gated engine function) via amockallmock ofContainerExecClient. The stable public API surface (RepositoryRef,BranchName,WorkspacePath, andpodbot::api::clone_repository_into_workspace) is not exercised end-to-end.Required action
Redesign the BDD helper layer so that the
Whenstep invokes only the stable public API, passing already-constructed domain value objects. Infrastructure wiring should be injected via an in-process test double that implements the public adapter interface, not the internalContainerExecClient.References