Server Instructions

ACP v1 Architecture

Public API routes are defined in server/packages/sandbox-agent/src/router.rs.
ACP runtime/process bridge is in server/packages/sandbox-agent/src/acp_runtime.rs.
/v1 is the only active API surface for sessions/prompts (/v1/acp/{server_id}).
Keep binary filesystem transfer endpoints as dedicated HTTP APIs:
- GET /v1/fs/file
- PUT /v1/fs/file
- POST /v1/fs/upload-batch
- Rationale: host-owned cross-agent-consistent behavior and large binary transfer needs that ACP JSON-RPC is not suited to stream efficiently.
- Maintain ACP variants in parallel only when they share the same underlying filesystem implementation; SDK defaults should still prefer HTTP for large/binary transfers.
/v1/* must remain hard-removed (410) and /opencode/* stays disabled (503) until Phase 7.
Agent install logic (native + ACP agent process + lazy install) is handled by server/packages/agent-management/.

Every #[utoipa::path(...)] handler needs a summary line + description lines in its doc comment.
Every responses(...) entry must include description.
Regenerate docs/openapi.json after endpoint contract changes.
Keep CLI and HTTP endpoint behavior aligned (docs/cli.mdx).

Primary v1 integration coverage:

Run:

cargo test -p sandbox-agent --test v1_api
cargo test -p sandbox-agent --test v1_agent_process_matrix