operate-acp-agent-integrationlisted

# Operate ACP Agent Integration Operate an existing ACP agent without confusing client setup, agent-native configuration, and protocol behavior. Read `references/acp-operations-map.md` for the current connection and failure map. ## Preflight 1. Name the ACP client and ACP agent/server process. 2. Treat ACP v1 as the current latest protocol and v2 as draft design work. Check the capabilities negotiated by the actual pair; do not infer wire compatibility from SDK package versions or implement a draft RFD as stable. 3. Check the canonical ACP Registry with the managed ACP registry checker. 4. If the agent is missing, use its official local executable only when the client supports custom agents. Keep registry absence distinct from missing ACP support. 5. Run the agent's documented non-interactive health or version check before opening the client. For Hermes, check `hermes acp --version`, `hermes acp --check`, `hermes doctor`, and `hermes status` as needed. ACP reuses Hermes provider credentials, config, skills, and state; it does not create a separate provider setup. ## Connect And Validate 1. Configure the client launch command and environment with the smallest required surface. 2. Confirm stdout is reserved for JSON-RPC and human-readable logs go to stderr. 3. Inspect the initialization response for protocol version, agent capabilities, authentication methods, and implementation identity. 4. Complete agent-owned or terminal authentication before