Restore both required Docker E2E profiles without changing application code:
make in the shared e2e-base, because the host verification suite
now contains workflow tests that spawn make and e2e-core currently fails
with ENOENT;--locked flag from the image-time Rust fetch,
because todo2code publishes a Rust library and deliberately ignores
Cargo.lock. The disposable E2E image may resolve the library dependency
graph from sdk/rust/Cargo.toml before testing it.The repair is limited to Dockerfile.e2e. It does not add a committed Rust
lockfile, change dependency manifests, application source, runtime images or
OpenRouter behavior.
e2e-core includes make and completes without spawn make
ENOENT.e2e-full resolves the intentionally unlocked Rust library and
completes without a missing-lockfile error.make docker-smoke, make e2e-core, make e2e-full, host
verification and governance checks pass.Dockerfile.e2e.The human owner explicitly approved ticket-056 in the active conversation on
2026-08-08. This Markdown note records the transition to EDIT; it is not
trusted merge authorization.
Host verification, Docker smoke, core E2E and full E2E all pass. The
implementation changes only Dockerfile.e2e. Koru and Validator App approved
exact head 1752f3d63c0ce6fd2ae14b83067e593e999a5439; protected PR #72 passed
the governance ruleset and merged as main@5f8e831.