Merge pull request #82 from Automattic/devin-windsurf-alignment

Align Windsurf docs with Devin Desktop

Author: chubes4

README.md

@@ -42,7 +42,7 @@ Generated outputs are available for:
 - Pi
 - Qodo
 - Roo Code
-- Windsurf/Cascade
+- Devin Desktop
 - Zed
 
 The shared WordPress workflow:
@@ -94,10 +94,10 @@ Each build packages the shared `skills/` directory into the surfaces that can co
 | Pi | `plugins/pi/` | `package.json` with `pi-package` metadata and `skills/` |
 | Qodo | `plugins/qodo/` | `AGENTS.md`, `skills/`, MCP setup documented for Qodo Agentic Tools |
 | Roo Code | `plugins/roo-code/` | `.roo/mcp.json`, `.roo/rules/`, `.roo/rules-code/`, `skills/` |
-| Windsurf/Cascade | `plugins/windsurf/` | `.devin/rules/`, `mcp_config.json`, `skills/` |
+| Devin Desktop | `plugins/devin-desktop/` | `.devin/rules/`, `mcp_config.json`, `skills/` |
 | Zed | `plugins/zed/` | `AGENTS.md`, `.agents/skills/`, `.zed/settings.json` |
 
-Some outputs intentionally stop at workspace files or setup guidance because that is what the official agent surface supports today. For example, Pi does not expose built-in MCP configuration, Qodo documents MCP through Agentic Tools or enterprise allow-lists, and Conductor keeps MCP setup in app/provider settings rather than a repository-local MCP file.
+Some outputs intentionally stop at workspace files or setup guidance because that is what the official agent surface supports today. For example, Pi does not expose built-in MCP configuration, Qodo documents MCP through Agentic Tools or enterprise allow-lists, and Conductor keeps MCP setup in app/provider settings rather than a repository-local MCP file. Devin Desktop output lives under `plugins/devin-desktop/`; Cascade's official MCP config destination still uses `~/.codeium/windsurf/mcp_config.json`.
 
 ## Testing
 

docs/README.md

@@ -51,7 +51,7 @@ This bootstrap surface is grounded in the repository source inventory: `package.
 
 ## Current generated surfaces
 
-Build with WordPress currently generates outputs for Aider, Amp, Claude Code, Cline, Codex, Conductor, Continue, Cursor, Devin CLI, Factory Droid, Gemini, GitHub Copilot, Hermes, Junie, Kilo Code, OpenClaw, OpenCode, Pi, Qodo, Roo Code, Windsurf/Cascade, and Zed.
+Build with WordPress currently generates outputs for Aider, Amp, Claude Code, Cline, Codex, Conductor, Continue, Cursor, Devin CLI, Devin Desktop, Factory Droid, Gemini, GitHub Copilot, Hermes, Junie, Kilo Code, OpenClaw, OpenCode, Pi, Qodo, Roo Code, and Zed.
 
 See [Generated outputs](generated-outputs.md#generated-package-matrix) for each surface's output directory and native files.
 

docs/architecture.md

@@ -65,7 +65,7 @@ Repository-native names used across the source and generated outputs:
     ├── pi/
     ├── qodo/
     ├── roo-code/
-    ├── windsurf/
+    ├── devin-desktop/
     └── zed/
 ```
 

docs/generated-outputs.md

@@ -49,7 +49,7 @@ pnpm build:telemetry-mcp
 | Pi | `plugins/pi/` | `package.json` with `pi-package` metadata and `skills/`. |
 | Qodo | `plugins/qodo/` | `AGENTS.md`, `skills/`, and MCP setup guidance for Qodo Agentic Tools. |
 | Roo Code | `plugins/roo-code/` | `.roo/mcp.json`, `.roo/rules/`, `.roo/rules-code/`, `skills/`. |
-| Windsurf/Cascade | `plugins/windsurf/` | `.devin/rules/`, `mcp_config.json`, `skills/`. |
+| Devin Desktop | `plugins/devin-desktop/` | `.devin/rules/`, `mcp_config.json`, `skills/`. The generated output uses the Devin Desktop name; Cascade's official MCP config destination still uses `~/.codeium/windsurf/mcp_config.json`. |
 | Zed | `plugins/zed/` | `AGENTS.md`, `.agents/skills/`, `.zed/settings.json`. |
 
 Some surfaces support a complete plugin/marketplace package. Others only support workspace instructions, local settings, or user-facing setup notes. The generator should use the best supported native integration point for each surface.

…ndsurf/.devin/rules/wordpress-com-mcp.md …esktop/.devin/rules/wordpress-com-mcp.mdplugins/windsurf/.devin/rules/wordpress-com-mcp.md renamed to plugins/devin-desktop/.devin/rules/wordpress-com-mcp.md plugins/windsurf/.devin/rules/wordpress-com-mcp.md renamed to plugins/devin-desktop/.devin/rules/wordpress-com-mcp.md

@@ -1,13 +1,17 @@
-# WordPress.com for Windsurf Cascade
+# WordPress.com for Devin Desktop
 
-This Windsurf/Cascade output packages the shared WordPress agent substrate from the `build-with-wordpress` source repo for WordPress.com work.
+This Devin Desktop output packages the shared WordPress agent substrate from the `build-with-wordpress` source repo for WordPress.com work.
 
-## What is Windsurf-specific
+## What is Devin Desktop-specific
 
 - Cascade rules live in `.devin/rules/*.md`, which the official docs list as the preferred workspace rule location.
 - `mcp_config.json` is shaped for Cascade's MCP configuration file at `~/.codeium/windsurf/mcp_config.json`.
 - The rules tell Cascade when to use WordPress.com MCP tools and how to route WordPress implementation work.
 
+## Migration from Windsurf
+
+Windsurf/Cascade is now part of the Devin Desktop lineage, so this generated package lives at `plugins/devin-desktop/`. Cascade's official MCP config path still uses `~/.codeium/windsurf/mcp_config.json`, so the setup instructions keep that destination path while the repository output uses the Devin Desktop name.
+
 ## What is shared
 
 - The WordPress.com MCP path uses the existing `wordpress-studio` MCP server; this output does not add a new backend service.
@@ -17,10 +21,10 @@ This Windsurf/Cascade output packages the shared WordPress agent substrate from
 
 ## Setup
 
-1. Install Devin Desktop / Windsurf and complete onboarding.
+1. Install Devin Desktop and complete onboarding.
 2. Optionally install the `windsurf` command in `PATH` during onboarding.
 3. Build this repo with `pnpm build`.
-4. Copy the servers from `plugins/windsurf/mcp_config.json` into `~/.codeium/windsurf/mcp_config.json`.
+4. Copy the servers from `plugins/devin-desktop/mcp_config.json` into `~/.codeium/windsurf/mcp_config.json`.
 5. In Cascade MCP settings, confirm both servers are enabled:
    - `wordpress-studio`
    - `wordpress-telemetry`