add-editorlisted

# Add Editor Integration (ACP / MCP) Use Deus's **memory** and **evolution** layers from inside an external editor (or any MCP-capable client) by composing them onto the editor's *own* coding agent — you do not run Deus's container in the editor. The editor's agent keeps handling editor mechanics (diffs, permissions, buffers); Deus's two MCP servers supply the "brain": - **`deus-memory`** → `memory_recall` (semantic recall over your vault). - **`deus-evolution`** → `get_reflections` / `log_interaction` / `get_active_prompt` / `record_feedback` (the reflexion loop). This skill *performs* the wiring interactively. For the **why** (compose-not-port rationale, caveats, why reflexion learns from mistakes not stated style), read [`docs/EDITOR_INTEGRATION.md`](../../../docs/EDITOR_INTEGRATION.md) — do not duplicate that reasoning here; just point the user at it if they ask. **Principle:** when a precondition is missing, fix it (create the venv, pull the model). Only pause for genuine user decisions (which editor, employer-machine containment, target project). Use `AskUserQuestion` for every user-facing choice. --- ## 0. Scope — two independent parts Tell the user this skill has two parts they can run independently: 1. **Machine-level editor config (steps 1-5)** — wires the two MCP servers into the editor. Run **once per machine**. 2. **Per-project instruction file (step 6)** — the close-the-loop `AGENTS.md`. Run **once per repo** you want the loop active in. If they