Epic: ship WordPress Studio editor connectors

## Goal

Track the full WordPress Studio connector plan across VS Code-family editors and coding-agent surfaces. Build with WordPress should be the source of truth for generated setup artifacts, shared Studio MCP config, shared skills, and marketplace/listing requirements.

## Scope

- VS Code Marketplace extension for WordPress Studio.
- Cursor plugin/export flow and listing checklist.
- Devin CLI output.
- Devin Desktop / Windsurf Cascade lineage and naming.
- Antigravity research and connector output if official integration surfaces exist.
- Shared Studio MCP setup contract used across editor outputs.

## Existing related issues

- #45 tracks broader official agent marketplace submission.
- #60 tracks Windsurf/Cascade marketplace submission and should be interpreted in the Devin Desktop / Windsurf Cascade lineage.

## Desired architecture

Build with WordPress owns the agent/editor-facing layer:

- shared WordPress skills in `skills/`;
- generated editor/agent packages under `plugins/`;
- shared `wordpress-studio` MCP config that launches `studio mcp`;
- shared `wordpress-telemetry` MCP bootstrap;
- surface-specific manifests, docs, verification, and marketplace packaging.

WordPress Studio owns the runtime:

- local sites;
- `studio` CLI;
- `studio mcp`;
- Studio auth and site operations.

## Child work

Create and link follow-up issues for:

- VS Code Marketplace extension.
- Cursor plugin/listing/export.
- Devin CLI and Devin Desktop / Windsurf Cascade alignment.
- Antigravity research and implementation.
- Shared Studio MCP setup contract and verification.

## Acceptance criteria

- Every supported editor surface has a linked tracking issue.
- Existing generated outputs remain documented and verified.
- Planned surfaces are clearly marked as research/planned rather than implied support.
- Marketplace publishing requirements are captured before implementation starts.
- `pnpm build` and `pnpm verify` remain the gate for generated outputs.

## AI assistance

- **AI assistance:** Yes
- **Tool(s):** OpenCode (GPT-5.5)
- **Used for:** Drafting this tracking issue from the editor connector planning discussion; Chris remains responsible for prioritization and review.

Start by reading the existing outputs in skills/ and plugins/ and the shared Studio MCP and telemetry setup described in the issue. Map each supported editor surface to a follow-up issue, document planned versus supported integrations, and run pnpm build and pnpm verify to confirm generated outputs remain valid.

Written by the indexing model from the issue text.