2.2 KiB
2.2 KiB
id, title, status, wave, depends_on, plan, spec
| id | title | status | wave | depends_on | plan | spec | ||
|---|---|---|---|---|---|---|---|---|
| 05-remote-materialization | Remote materialization | done | 4 |
|
plan.md | ../../specs/tasks/system-design/attach-workspace-sources.md |
Task 05: Remote Materialization
Acceptance
- Agentctl can atomically clone/checkout a validated repository into a collision-checked workspace subdirectory with cancellation and cleanup defenses.
- Docker, SSH, and Sprites use their live agentctl clients and existing credential resolution to materialize and rescan repository sources; secrets are absent from logs and metadata.
- Container and remote folder requests are rejected before persistence or filesystem access, and the same executor capability is available to the frontend picker.
- New/reset environments rebuild all durable sources, and adapter tests cover failure rollback plus the future remote-Docker capability boundary.
Verification
cd apps/backend
rtk go test ./internal/agentctl/... ./internal/agent/runtime/lifecycle/... ./internal/backendapp/...
Files likely touched
apps/backend/internal/agentctl/client_workspace_sources.go(new)apps/backend/internal/agentctl/server/api/workspace_sources.go(new)apps/backend/internal/agentctl/server/api/workspace_sources_test.go(new)apps/backend/internal/agentctl/server/api/server.goapps/backend/internal/agentctl/server/process/manager.goapps/backend/internal/agent/runtime/lifecycle/executor_docker.goapps/backend/internal/agent/runtime/lifecycle/executor_ssh.goapps/backend/internal/agent/runtime/lifecycle/executor_sprites.goapps/backend/internal/agent/runtime/lifecycle/executor_remote_docker.goapps/backend/internal/agent/runtime/lifecycle/manager_launch.go- executor/materialization tests beside those files
Dependencies
Tasks 03 and 04.
Inputs
- Spec: executor source capabilities, credential boundary, persistence, failure modes.
- Existing
workspace/copy-files, remote copy-files, Docker prepare, SSH upload, and Sprites file uploader patterns.
Output contract
Summary, files changed, tests run, blockers, risks, divergence, and task/plan status updates.