Add ACP Support

Feature Description

Command Code currently integrates with editors via MCP or headless mode(cmd -p --output-format json), but it cannot be embedded as an agent in editors/IDEs that speak the Agent Client Protocol (ACP). ACP is becoming the de-facto standard for editor–agent communication and is already supported by Zed, JetBrains IDEs, and Typstify, with adapters for Claude Code, Codex, OpenCode, and Cline.

Use Case

I write Typst documents in Typstify, whose v1.8.0 AI Assistant launches any ACP agent and augments it with editor-aware MCP tools: getActiveDocument, getDocumentOutline, queryDiagnostics, typstCompiler (PDF/PNG/SVG export), previewer control, and TPIX package search/download. Configuring Command Code as the agent would let me use its models, taste learning, skills, and plan mode directly inside the editor - with permission approvals in the UI and sessions I can resume - instead of switching to a terminal for every task.

Additional Context

No response

How important is this to you?

Blocking adoption or production use

Beginne damit, die vorhandenen MCP- und Headless-Integrationen zu lokalisieren, und überprüfe anschließend die ACP-Anforderungen für die Kommunikation zwischen Editor und Agent. Als abgeschlossen gilt die Aufgabe, wenn Command Code von ACP-kompatiblen Editoren mit der angeforderten Agenteninteraktion, der Genehmigung von Berechtigungen und fortsetzbaren Sitzungen gestartet werden kann.