build-acp-agentlisted

# Build ACP Agent Build the agent process that an ACP client launches. Do not build an editor plug-in or MCP server when the requirement is an editor-native coding agent. Read `references/acp-implementation-map.md` before selecting an SDK or registry distribution. ## Implementation Workflow 1. Define concrete client targets and the user-visible behavior they require. 2. Use ACP v1, the current latest protocol, and an official SDK when its language and runtime fit. Treat v2 and non-completed RFDs as experimental; do not ship them as the portable baseline. Use raw JSON-RPC only when an SDK cannot support a required platform or feature. 3. Implement initialization first: - negotiate `protocolVersion` - advertise only implemented agent capabilities - inspect client filesystem and terminal capabilities before using them - advertise real authentication methods and implementation information 4. Implement the required session baseline: new, prompt, cancel, and update. 5. Add optional load, resume, fork, list, close, modes, configuration, plans, slash commands, rich prompt content, or MCP transports only with matching capability declarations and tests. Keep draft `session/delete`, logout, elicitation, additional directories, and remote transports behind explicit experimental flags and interoperability tests. 6. Render tool calls, diffs, terminals, plans, and streamed content in the ACP structures the target clients understand. 7. Route dangerous