summer-engine 3.0.0 → 3.2.0

package/integrations/README.md

@@ -2,10 +2,11 @@
 
 One folder per supported client. This directory is the single place that
 says which agents Summer supports and how each one consumes the library.
-Adding a new agent (e.g. Grok) = one folder here (plus, if it has a manifest
-file, a builder in `scripts/generate-registry/manifests.ts` and a target in
-`scripts/generate-registry/targets.ts`) + `npm run generate:registry` —
-never hand-editing root files.
+Adding a new agent = one row in `src/installer/agent-table.ts` + one folder
+here + an empty entry in `scripts/generate-registry/targets.ts` (plus, if it
+has a manifest file, a builder in `scripts/generate-registry/manifests.ts`) +
+`npm run generate:registry` — never hand-editing root files. Tests fail when
+the table, this directory, and targets.ts disagree.
 
 Each folder contains:
 
@@ -18,8 +19,8 @@ installs every skill (`skills install --all`, preview included; `--stable-only`
 skips preview) in the SAME scope,
 so a user-scope MCP config never ends up beside project-scope skills.
 `--scope project` moves both; `--recommended` installs only the recommended
-subset. Clients whose MCP config is user-only (cline, roo-code, lm-studio,
-gemini) fall back to user scope with a warning. `.mcp.json` at the repo root
+subset. Clients whose MCP config is user-only (see the table) fall back to user
+scope with a warning. `.mcp.json` at the repo root
 (the MCP pointer the claude / codex / cursor / factory manifests share) is
 generated too — `registry/generated/mcp.json -> .mcp.json`.
 - `manifest-target.json` — mapping of generated file -> repo-root destination
@@ -52,19 +53,47 @@ How the plugin manifests reference skills, and what is verified:
 
 | Client | Manifest generated in this repo | `summer setup` writes |
 |---|---|---|
-| claude | `.claude-plugin/plugin.json`, `.claude-plugin/marketplace.json`, `.mcp.json` | MCP: `~/.claude.json` (user) / `.mcp.json` (project); skills: `~/.claude/skills/` (user) / `.claude/skills/` (project); slash commands from `commands/` to `~/.claude/commands/` |
-| codex | `.codex-plugin/plugin.json` | MCP: `~/.codex/config.toml` (TOML); skills: `.agents/skills/` |
-| cursor | `.cursor-plugin/plugin.json` | MCP: `~/.cursor/mcp.json` / `.cursor/mcp.json`; skills: `.cursor/rules/` |
-| factory | `.factory-plugin/plugin.json` | nothing — there is no `summer setup factory` target. Install via the plugin marketplace: `droid plugin marketplace add https://github.com/summerengine/summer` then `droid plugin install summer@summer-engine`. Factory reads MCP from the plugin's `.mcp.json` and skills only from a root `skills/` dir (this package ships them under `library/skills/`, so the manifest `skills` array is not read by Factory — open gap) |
-| gemini | `gemini-extension.json` | extension dir `~/.gemini/extensions/summer-engine/`: the generated manifest (renamed `summer-engine` to match the dir, MCP launcher swapped to `npx -y summer-engine@latest mcp`) + `GEMINI.md` + `AGENTS.md`; skills: `~/.gemini/extensions/summer-engine/skills/<slug>/SKILL.md` (Gemini extension-skill discovery; user scope only) |
-| windsurf (Devin Desktop) | — | MCP: `~/.codeium/windsurf/mcp_config.json`; rules: `.windsurfrules` |
-| cline | — | MCP: VS Code global storage (`saoudrizwan.claude-dev`); rules: `.clinerules` |
-| roo-code | — | MCP: VS Code global storage (`rooveterinaryinc.roo-cline`); rules: `.clinerules` |
-| kilo-code | — | MCP: VS Code global storage `kilocode.kilo-code/settings/mcp_settings.json` (user) / `.kilocode/mcp.json` (project); rules: `~/.kilocode/rules/` (user) / `.kilocode/rules/` (project) |
-| github-copilot | — | MCP: `~/.copilot/mcp-config.json` / `.mcp.json`; skills: `~/.copilot/skills/` or `.github/skills/` |
-| vscode-copilot | — | MCP: VS Code user-profile `mcp.json` / `.vscode/mcp.json`; skills: `~/.copilot/skills/` or `.github/skills/` |
-| opencode | — (JS plugin via npm `main`, `.opencode/plugins/summer.js`) | MCP entry in `opencode.json` (`type: "local"`, array `command`); skills: the plugin registers `library/skills/` via `skills.paths`; `skills install --agent opencode` additionally writes `agents/summer/` markdown |
-| lm-studio | — | MCP: `~/.lmstudio/mcp.json` (app-global); no skills folder — guidance via `summer_get_agent_playbook` |
+| claude | `.claude-plugin/plugin.json`, `.claude-plugin/marketplace.json`, `.mcp.json` | MCP: `~/.claude.json`; Windows `%USERPROFILE%/.claude.json` / `.mcp.json`; skills: `~/.claude/skills` / `.claude/skills` (`<skill>/SKILL.md`) |
+| claude-desktop | — | MCP: `~/Library/Application Support/Claude/claude_desktop_config.json`; Linux `~/.config/Claude/claude_desktop_config.json`; Windows `%APPDATA%/Claude/claude_desktop_config.json`; no skills folder (MCP only) |
+| codex | `.codex-plugin/plugin.json` | MCP: `~/.codex/config.toml`; Windows `%USERPROFILE%/.codex/config.toml` / `.codex/config.toml`; skills: `~/.agents/skills` / `.agents/skills` (`<skill>/SKILL.md`) |
+| cursor | `.cursor-plugin/plugin.json` | MCP: `~/.cursor/mcp.json`; Windows `%USERPROFILE%/.cursor/mcp.json` / `.cursor/mcp.json`; skills: `~/.cursor/skills` / `.cursor/skills` (`<skill>/SKILL.md`) |
+| windsurf | — | MCP: `~/.codeium/windsurf/mcp_config.json`; Windows `%USERPROFILE%/.codeium/windsurf/mcp_config.json`; skills: `~/.codeium/windsurf/skills` / `.windsurf/skills` (`<skill>/SKILL.md`) |
+| antigravity | — | MCP: `~/.gemini/config/mcp_config.json`; Windows `%USERPROFILE%/.gemini/config/mcp_config.json` / `.agents/mcp_config.json`; skills: `~/.gemini/config/skills` / `.agents/skills` (`<skill>/SKILL.md`) |
+| gemini (legacy) | `gemini-extension.json` | MCP: `~/.gemini/extensions/summer-engine/gemini-extension.json`; Windows `%USERPROFILE%/.gemini/extensions/summer-engine/gemini-extension.json`; skills: `~/.gemini/extensions/summer-engine/skills` (`<skill>/SKILL.md`) |
+| cline | — | MCP: `~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json`; Linux `~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json`; Windows `%APPDATA%/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json`; skills: `~/.cline/skills` / `.cline/skills` (`<skill>/SKILL.md`) |
+| cline-cli | — | MCP: `~/.cline/data/settings/cline_mcp_settings.json`; Windows `%USERPROFILE%/.cline/data/settings/cline_mcp_settings.json`; skills: `~/.cline/skills` / `.cline/skills` (`<skill>/SKILL.md`) |
+| roo-code (legacy) | — | MCP: `~/Library/Application Support/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json`; Linux `~/.config/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json`; Windows `%APPDATA%/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json`; skills: `~/Documents/Roo/Rules` / `.clinerules` (rule files `summer-<skill>.md`) |
+| kilo-code | — | MCP: `~/.config/kilo/kilo.json`; Windows `%APPDATA%/kilo/kilo.json` / `kilo.json`; skills: `~/.kilo/skills` / `.kilo/skills` (`<skill>/SKILL.md`) |
+| github-copilot | — | MCP: `~/.copilot/mcp-config.json`; Windows `%USERPROFILE%/.copilot/mcp-config.json` / `.mcp.json`; skills: `~/.copilot/skills` / `.github/skills` (`<skill>/SKILL.md`) |
+| vscode-copilot | — | MCP: `~/Library/Application Support/Code/User/mcp.json`; Linux `~/.config/Code/User/mcp.json`; Windows `%APPDATA%/Code/User/mcp.json` / `.vscode/mcp.json`; skills: `~/.copilot/skills` / `.github/skills` (`<skill>/SKILL.md`) |
+| visual-studio | — | MCP: `~/.mcp.json`; Windows `%USERPROFILE%/.mcp.json` / `.mcp.json`; no skills folder (MCP only) |
+| copilot-jetbrains | — | MCP: `~/.config/github-copilot/intellij/mcp.json`; Windows `%APPDATA%/github-copilot/intellij/mcp.json`; no skills folder (MCP only) |
+| opencode | — | MCP: `~/.config/opencode/opencode.json`; Windows `%APPDATA%/opencode/opencode.json` / `opencode.json`; skills: `~/.config/opencode/skills` / `.opencode/skills` (`<skill>/SKILL.md`) |
+| zed | — | MCP: `~/.config/zed/settings.json`; Windows `%APPDATA%/zed/settings.json`; skills: `~/.agents/skills` / `.agents/skills` (`<skill>/SKILL.md`) |
+| kiro | — | MCP: `~/.kiro/settings/mcp.json`; Windows `%USERPROFILE%/.kiro/settings/mcp.json` / `.kiro/settings/mcp.json`; skills: `~/.kiro/skills` / `.kiro/skills` (`<skill>/SKILL.md`) |
+| goose | — | MCP: `~/.config/goose/config.yaml`; Windows `%APPDATA%/Block/goose/config/config.yaml`; skills: `~/.config/agents/skills` / `.agents/skills` (`<skill>/SKILL.md`) |
+| hermes | — | MCP: `~/.hermes/config.yaml`; Windows `%USERPROFILE%/.hermes/config.yaml`; skills: `~/.hermes/skills` / `.hermes/skills` (`<skill>/SKILL.md`) |
+| trae | — | MCP: `.trae/mcp.json` / `.trae/mcp.json`; no skills folder (MCP only) |
+| qwen-code | — | MCP: `~/.qwen/settings.json`; Windows `%USERPROFILE%/.qwen/settings.json` / `.qwen/settings.json`; skills: `~/.qwen/skills` / `.qwen/skills` (`<skill>/SKILL.md`) |
+| kimi-code | — | MCP: `~/.kimi-code/mcp.json`; Windows `%USERPROFILE%/.kimi-code/mcp.json` / `.kimi-code/mcp.json`; skills: `~/.kimi-code/skills` / `.kimi-code/skills` (`<skill>/SKILL.md`) |
+| crush | — | MCP: `~/.config/crush/crushrc`; Windows `%USERPROFILE%/.config/crush/crushrc` / `.crushrc`; skills: `~/.config/crush/skills` / `.crush/skills` (`<skill>/SKILL.md`) |
+| amp | — | MCP: `~/.config/amp/settings.json`; Windows `%APPDATA%/amp/settings.json`; skills: `~/.config/amp/skills` / `.agents/skills` (`<skill>/SKILL.md`) |
+| factory | `.factory-plugin/plugin.json` | MCP: `~/.factory/mcp.json`; Windows `%USERPROFILE%/.factory/mcp.json` / `.factory/mcp.json`; skills: `~/.factory/skills` / `.factory/skills` (`<skill>/SKILL.md`) |
+| junie | — | MCP: `~/.junie/mcp/mcp.json`; Windows `%USERPROFILE%/.junie/mcp/mcp.json` / `.junie/mcp/mcp.json`; no skills folder (MCP only) |
+| warp | — | MCP: `~/.warp/.mcp.json`; Windows `%USERPROFILE%/.warp/.mcp.json` / `.warp/.mcp.json`; skills: `~/.warp/skills` / `.warp/skills` (`<skill>/SKILL.md`) |
+| rovo-dev | — | MCP: `~/.rovodev/mcp.json`; Windows `%USERPROFILE%/.rovodev/mcp.json`; skills: `~/.rovodev/skills` / `.rovodev/skills` (`<skill>/SKILL.md`) |
+| qoder | — | MCP: `~/.qoder/settings.json`; Windows `%USERPROFILE%/.qoder/settings.json` / `.mcp.json`; skills: `~/.qoder/skills` / `.qoder/skills` (`<skill>/SKILL.md`) |
+| grok-build | — | MCP: `~/.grok/config.toml`; Windows `%USERPROFILE%/.grok/config.toml` / `.grok/config.toml`; skills: `~/.grok/skills` / `.grok/skills` (`<skill>/SKILL.md`) |
+| mistral-vibe | — | MCP: `~/.vibe/config.toml`; Windows `%USERPROFILE%/.vibe/config.toml` / `.vibe/config.toml`; skills: `~/.vibe/skills` / `.vibe/skills` (`<skill>/SKILL.md`) |
+| lm-studio | — | MCP: `~/.lmstudio/mcp.json`; Windows `%USERPROFILE%/.lmstudio/mcp.json`; no skills folder (MCP only) |
 
 Source of truth for the setup paths: `src/installer/agent-config.ts` and
 `src/cli/commands/skills.ts`.
+
+Not supported on purpose (checked 2026-09-11): OpenHands CLI (its `[mcp] stdio_servers`
+inline-table array has a known upstream write bug), Xcode's agent folders (Apple
+documents the folder but not the file names), Pi (no MCP by design), Aider,
+ChatGPT desktop, Replit, Perplexity, JetBrains AI Assistant and Android Studio
+(UI-only MCP), Continue.dev (shut down), Void (archived), Cody (enterprise only).
+Grok Build also reads `~/.claude.json` and `.cursor/mcp.json`, so a Claude Code or
+Cursor setup already covers it; `summer setup grok-build` writes its own file too.

package/integrations/amp/README.md

@@ -0,0 +1,12 @@
+# Amp integration
+
+No manifest file is generated in this repo for Amp — `manifest-target.json`
+is intentionally empty. Support is delivered at install time by
+`summer setup amp` (aliases: `sourcegraph-amp`, `ampcode`), which writes:
+
+- MCP config: `~/.config/amp/settings.json`; Windows `%APPDATA%/amp/settings.json` (user); user scope only (project requests fall back with a warning).
+  Shape: `"amp.mcpServers".summer-engine = { command, args }`.
+- Skills: `~/.agents/skills` (user) or `.agents/skills` (project) as `<skill>/SKILL.md`.
+- After: Restart Amp so it reloads settings.json.
+
+Source of truth: `src/installer/agent-table.ts` (one row per agent).

package/integrations/amp/manifest-target.json

@@ -0,0 +1,3 @@
+{
+  "targets": []
+}

package/integrations/antigravity/README.md

@@ -0,0 +1,12 @@
+# Antigravity integration
+
+No manifest file is generated in this repo for Antigravity — `manifest-target.json`
+is intentionally empty. Support is delivered at install time by
+`summer setup antigravity` (aliases: `agy`, `google-antigravity`), which writes:
+
+- MCP config: `~/.gemini/config/mcp_config.json`; Windows `%USERPROFILE%/.gemini/config/mcp_config.json` (user); `.agents/mcp_config.json` (project).
+  Shape: `mcpServers.summer-engine = { command, args }`.
+- Skills: `~/.gemini/config/skills` (user) or `.agents/skills` (project) as `<skill>/SKILL.md`.
+- After: In Antigravity open the agent panel's MCP servers view and refresh; summer-engine appears in the list (IDE and CLI share this file).
+
+Source of truth: `src/installer/agent-table.ts` (one row per agent).

package/integrations/antigravity/manifest-target.json

@@ -0,0 +1,3 @@
+{
+  "targets": []
+}

package/integrations/claude-desktop/README.md

@@ -0,0 +1,12 @@
+# Claude Desktop integration
+
+No manifest file is generated in this repo for Claude Desktop — `manifest-target.json`
+is intentionally empty. Support is delivered at install time by
+`summer setup claude-desktop` (aliases: `claude-app`, `claudedesktop`), which writes:
+
+- MCP config: `~/Library/Application Support/Claude/claude_desktop_config.json`; Linux `~/.config/Claude/claude_desktop_config.json`; Windows `%APPDATA%/Claude/claude_desktop_config.json` (user); user scope only (project requests fall back with a warning).
+  Shape: `mcpServers.summer-engine = { command, args }`.
+- Skills: none. Claude Desktop has no skills folder. The MCP server ships summer_get_agent_playbook, so the model can pull Summer guidance in-chat.
+- After: Quit and reopen Claude Desktop; the summer-engine tools appear under the tools menu in a new chat.
+
+Source of truth: `src/installer/agent-table.ts` (one row per agent).

package/integrations/claude-desktop/manifest-target.json

@@ -0,0 +1,3 @@
+{
+  "targets": []
+}

package/integrations/cline/README.md

@@ -1,13 +1,12 @@
-# Cline integration
+# Cline (VS Code) integration
 
-No manifest file is generated in this repo for Cline — `manifest-target.json`
+No manifest file is generated in this repo for Cline (VS Code) — `manifest-target.json`
 is intentionally empty. Support is delivered at install time by
-`summer setup cline`, which writes:
+`summer setup cline` (aliases: `cline-vscode`), which writes:
 
-- MCP config: Cline's VS Code global storage (extension
-  `saoudrizwan.claude-dev`). User scope only — Cline has no project-scoped MCP
-  config today; project requests fall back to user scope with a warning.
-- Skills: `summer skills install --agent cline` writes rule files to Cline's
-  user rules directory (user scope) or `./.clinerules` (project scope).
+- MCP config: `~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json`; Linux `~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json`; Windows `%APPDATA%/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json` (user); user scope only (project requests fall back with a warning).
+  Shape: `mcpServers.summer-engine = { command, args }`.
+- Skills: `~/.cline/skills` (user) or `.cline/skills` (project) as `<skill>/SKILL.md`.
+- After: Restart VS Code so Cline reloads its MCP config.
 
-Source of truth: `src/installer/agent-config.ts`, `src/cli/commands/skills.ts`.
+Source of truth: `src/installer/agent-table.ts` (one row per agent).

package/integrations/cline-cli/README.md

@@ -0,0 +1,12 @@
+# Cline CLI integration
+
+No manifest file is generated in this repo for Cline CLI — `manifest-target.json`
+is intentionally empty. Support is delivered at install time by
+`summer setup cline-cli` (aliases: `clinecli`), which writes:
+
+- MCP config: `~/.cline/data/settings/cline_mcp_settings.json`; Windows `%USERPROFILE%/.cline/data/settings/cline_mcp_settings.json` (user); user scope only (project requests fall back with a warning).
+  Shape: `mcpServers.summer-engine = { command, args }`.
+- Skills: `~/.cline/skills` (user) or `.cline/skills` (project) as `<skill>/SKILL.md`.
+- After: Restart the Cline CLI so it reloads its MCP settings.
+
+Source of truth: `src/installer/agent-table.ts` (one row per agent).

package/integrations/cline-cli/manifest-target.json

@@ -0,0 +1,3 @@
+{
+  "targets": []
+}

package/integrations/copilot-jetbrains/README.md

@@ -0,0 +1,12 @@
+# GitHub Copilot in JetBrains IDEs integration
+
+No manifest file is generated in this repo for GitHub Copilot in JetBrains IDEs — `manifest-target.json`
+is intentionally empty. Support is delivered at install time by
+`summer setup copilot-jetbrains` (aliases: `jetbrains-copilot`, `intellij-copilot`, `copilot-intellij`), which writes:
+
+- MCP config: `~/.config/github-copilot/intellij/mcp.json`; Windows `%APPDATA%/github-copilot/intellij/mcp.json` (user); user scope only (project requests fall back with a warning).
+  Shape: undefined.
+- Skills: none. Copilot in JetBrains documents no skills folder; the MCP server ships summer_get_agent_playbook for in-chat guidance.
+- After: Restart the JetBrains IDE and open Copilot Chat in Agent mode; summer-engine shows in the tools list.
+
+Source of truth: `src/installer/agent-table.ts` (one row per agent).

package/integrations/copilot-jetbrains/manifest-target.json

@@ -0,0 +1,3 @@
+{
+  "targets": []
+}

package/integrations/crush/README.md

@@ -0,0 +1,12 @@
+# Crush integration
+
+No manifest file is generated in this repo for Crush — `manifest-target.json`
+is intentionally empty. Support is delivered at install time by
+`summer setup crush` (aliases: `charm-crush`), which writes:
+
+- MCP config: `~/.config/crush/crushrc`; Windows `%USERPROFILE%/.config/crush/crushrc` (user); `.crushrc` (project).
+  Shape: `mcp.summer-engine = { type: "stdio", command, args }`.
+- Skills: `~/.agents/skills` (user) or `.agents/skills` (project) as `<skill>/SKILL.md`.
+- After: Restart Crush so it reloads crushrc.
+
+Source of truth: `src/installer/agent-table.ts` (one row per agent).

package/integrations/crush/manifest-target.json

@@ -0,0 +1,3 @@
+{
+  "targets": []
+}

package/integrations/github-copilot/README.md

@@ -1,12 +1,12 @@
 # GitHub Copilot CLI integration
 
-No manifest file is generated in this repo for Copilot CLI —
-`manifest-target.json` is intentionally empty. Support is delivered at install
-time by `summer setup github-copilot`, which writes:
+No manifest file is generated in this repo for GitHub Copilot CLI — `manifest-target.json`
+is intentionally empty. Support is delivered at install time by
+`summer setup github-copilot` (aliases: `copilot`, `copilot-cli`, `github-copilot-cli`), which writes:
 
-- MCP config: `~/.copilot/mcp-config.json` (user scope) or `./.mcp.json`
-  (project scope), in Copilot's MCP config format.
-- Skills: `summer skills install --agent github-copilot` writes skill files to
-  `~/.copilot/skills/` (user scope) or `./.github/skills/` (project scope).
+- MCP config: `~/.copilot/mcp-config.json`; Windows `%USERPROFILE%/.copilot/mcp-config.json` (user); `.mcp.json` (project).
+  Shape: `mcpServers.summer-engine = { type: "local", command, args, tools: ["*"] }`.
+- Skills: `~/.copilot/skills` (user) or `.github/skills` (project) as `<skill>/SKILL.md`.
+- After: Restart Copilot CLI, or run /mcp reload and /skills reload in the active session.
 
-Source of truth: `src/installer/agent-config.ts`, `src/cli/commands/skills.ts`.
+Source of truth: `src/installer/agent-table.ts` (one row per agent).

package/integrations/goose/README.md

@@ -0,0 +1,12 @@
+# Goose integration
+
+No manifest file is generated in this repo for Goose — `manifest-target.json`
+is intentionally empty. Support is delivered at install time by
+`summer setup goose` (aliases: `block-goose`, `codename-goose`), which writes:
+
+- MCP config: `~/.config/goose/config.yaml`; Windows `%APPDATA%/Block/goose/config/config.yaml` (user); user scope only (project requests fall back with a warning).
+  Shape: `extensions.summer-engine = { type: stdio, cmd, args, enabled, timeout }` (YAML).
+- Skills: `~/.config/agents/skills` (user) or `.agents/skills` (project) as `<skill>/SKILL.md`.
+- After: Restart Goose (CLI or Desktop); summer-engine is listed under Extensions.
+
+Source of truth: `src/installer/agent-table.ts` (one row per agent).

package/integrations/goose/manifest-target.json

@@ -0,0 +1,3 @@
+{
+  "targets": []
+}

package/integrations/grok-build/README.md

@@ -0,0 +1,12 @@
+# Grok Build integration
+
+No manifest file is generated in this repo for Grok Build — `manifest-target.json`
+is intentionally empty. Support is delivered at install time by
+`summer setup grok-build` (aliases: `grok`, `xai-grok`), which writes:
+
+- MCP config: `~/.grok/config.toml`; Windows `%USERPROFILE%/.grok/config.toml` (user); `.grok/config.toml` (project).
+  Shape: `[mcp_servers.summer-engine]` table (TOML).
+- Skills: `~/.agents/skills` (user) or `.agents/skills` (project) as `<skill>/SKILL.md`.
+- After: Restart Grok Build so it reloads config.toml (it also reads ~/.claude.json and .cursor/mcp.json).
+
+Source of truth: `src/installer/agent-table.ts` (one row per agent).

package/integrations/grok-build/manifest-target.json

@@ -0,0 +1,3 @@
+{
+  "targets": []
+}

package/integrations/hermes/README.md

@@ -0,0 +1,12 @@
+# Hermes Agent integration
+
+No manifest file is generated in this repo for Hermes Agent — `manifest-target.json`
+is intentionally empty. Support is delivered at install time by
+`summer setup hermes` (aliases: `hermes-agent`, `nous-hermes`), which writes:
+
+- MCP config: `~/.hermes/config.yaml`; Windows `%USERPROFILE%/.hermes/config.yaml` (user); user scope only (project requests fall back with a warning).
+  Shape: `mcp_servers.summer-engine = { command, args }` (YAML).
+- Skills: `~/.hermes/skills` (user) or `.agents/skills` (project) as `<skill>/SKILL.md`. Project skills need `hermes skills trust` before Hermes loads them.
+- After: Run /reload-mcp in Hermes Agent (or restart it).
+
+Source of truth: `src/installer/agent-table.ts` (one row per agent).

package/integrations/hermes/manifest-target.json

@@ -0,0 +1,3 @@
+{
+  "targets": []
+}

package/integrations/junie/README.md

@@ -0,0 +1,12 @@
+# Junie integration
+
+No manifest file is generated in this repo for Junie — `manifest-target.json`
+is intentionally empty. Support is delivered at install time by
+`summer setup junie` (aliases: `jetbrains-junie`), which writes:
+
+- MCP config: `~/.junie/mcp/mcp.json`; Windows `%USERPROFILE%/.junie/mcp/mcp.json` (user); `.junie/mcp/mcp.json` (project).
+  Shape: `mcpServers.summer-engine = { command, args }`.
+- Skills: none. Junie has no skills folder; put project guidance in .junie/guidelines.md. The MCP server ships summer_get_agent_playbook for in-chat guidance.
+- After: Restart the JetBrains IDE so Junie reloads its MCP config.
+
+Source of truth: `src/installer/agent-table.ts` (one row per agent).

package/integrations/junie/manifest-target.json

@@ -0,0 +1,3 @@
+{
+  "targets": []
+}

package/integrations/kilo-code/README.md

@@ -2,15 +2,11 @@
 
 No manifest file is generated in this repo for Kilo Code — `manifest-target.json`
 is intentionally empty. Support is delivered at install time by
-`summer setup kilo-code`, which writes:
+`summer setup kilo-code` (aliases: `kilo`, `kilocode`), which writes:
 
-- MCP config: Kilo Code's VS Code global storage
-  (`<VS Code user dir>/globalStorage/kilocode.kilo-code/settings/mcp_settings.json`,
-  user scope) or `./.kilocode/mcp.json` (project scope).
-- Skills: `summer setup kilo-code` installs the whole library in the same
-  scope as the MCP config (user by default), as rule files in
-  `~/.kilocode/rules/summer-<skill>.md` (user) or `./.kilocode/rules/`
-  (project). `summer skills install --agent kilo-code` on its own defaults
-  to project scope; pass `--scope user` to match a user-scope MCP config.
+- MCP config: `~/.config/kilo/kilo.json`; Windows `%APPDATA%/kilo/kilo.json` (user); `kilo.json` (project).
+  Shape: `mcp.summer-engine = { type: "local", command: [npx, ...], enabled: true }`.
+- Skills: `~/.kilo/skills` (user) or `.kilo/skills` (project) as `<skill>/SKILL.md`.
+- After: Restart Kilo (CLI or the VS Code extension) so it reloads kilo.json.
 
-Source of truth: `src/installer/agent-config.ts`, `src/cli/commands/skills.ts`.
+Source of truth: `src/installer/agent-table.ts` (one row per agent).

package/integrations/kimi-code/README.md

@@ -0,0 +1,12 @@
+# Kimi Code CLI integration
+
+No manifest file is generated in this repo for Kimi Code CLI — `manifest-target.json`
+is intentionally empty. Support is delivered at install time by
+`summer setup kimi-code` (aliases: `kimi`, `kimi-cli`, `kimicode`), which writes:
+
+- MCP config: `~/.kimi-code/mcp.json`; Windows `%USERPROFILE%/.kimi-code/mcp.json` (user); `.kimi-code/mcp.json` (project).
+  Shape: `mcpServers.summer-engine = { command, args }`.
+- Skills: `~/.agents/skills` (user) or `.agents/skills` (project) as `<skill>/SKILL.md`.
+- After: Restart Kimi Code CLI so it reconnects its MCP servers.
+
+Source of truth: `src/installer/agent-table.ts` (one row per agent).

package/integrations/kimi-code/manifest-target.json

@@ -0,0 +1,3 @@
+{
+  "targets": []
+}

package/integrations/kiro/README.md

@@ -0,0 +1,12 @@
+# Kiro integration
+
+No manifest file is generated in this repo for Kiro — `manifest-target.json`
+is intentionally empty. Support is delivered at install time by
+`summer setup kiro` (aliases: `kiro-ide`, `aws-kiro`), which writes:
+
+- MCP config: `~/.kiro/settings/mcp.json`; Windows `%USERPROFILE%/.kiro/settings/mcp.json` (user); `.kiro/settings/mcp.json` (project).
+  Shape: `mcpServers.summer-engine = { command, args }`.
+- Skills: `~/.kiro/skills` (user) or `.kiro/skills` (project) as `<skill>/SKILL.md`.
+- After: Kiro reloads MCP config on save; open the MCP Servers view to confirm summer-engine is connected.
+
+Source of truth: `src/installer/agent-table.ts` (one row per agent).

package/integrations/kiro/manifest-target.json

@@ -0,0 +1,3 @@
+{
+  "targets": []
+}

package/integrations/lm-studio/README.md

@@ -1,12 +1,12 @@
 # LM Studio integration
 
-No manifest file is generated in this repo for LM Studio —
-`manifest-target.json` is intentionally empty. Support is delivered at install
-time by `summer setup lm-studio`, which writes:
+No manifest file is generated in this repo for LM Studio — `manifest-target.json`
+is intentionally empty. Support is delivered at install time by
+`summer setup lm-studio` (aliases: `lmstudio`, `lm_studio`), which writes:
 
-- MCP config: `~/.lmstudio/mcp.json`. This file is app-global (user scope
-  only); project-scope requests are treated as user scope with a warning.
-- Skills: LM Studio has no rules or skills folder. The MCP server ships
-  `summer_get_agent_playbook`, so the model pulls Summer guidance in-chat.
+- MCP config: `~/.lmstudio/mcp.json`; Windows `%USERPROFILE%/.lmstudio/mcp.json` (user); user scope only (project requests fall back with a warning).
+  Shape: `mcpServers.summer-engine = { command, args }`.
+- Skills: none. LM Studio has no rules or skills folder. The MCP server ships summer_get_agent_playbook, so the model can pull Summer guidance in-chat.
+- After: Open LM Studio, toggle on the summer-engine MCP server in the Program tab, and raise the loaded model's context length to 32k or higher.
 
-Source of truth: `src/installer/agent-config.ts`, `src/installer/setup.ts`.
+Source of truth: `src/installer/agent-table.ts` (one row per agent).

package/integrations/mistral-vibe/README.md

@@ -0,0 +1,12 @@
+# Mistral Vibe integration
+
+No manifest file is generated in this repo for Mistral Vibe — `manifest-target.json`
+is intentionally empty. Support is delivered at install time by
+`summer setup mistral-vibe` (aliases: `vibe`, `mistral`), which writes:
+
+- MCP config: `~/.vibe/config.toml`; Windows `%USERPROFILE%/.vibe/config.toml` (user); `.vibe/config.toml` (project).
+  Shape: undefined.
+- Skills: `~/.vibe/skills` (user) or `.agents/skills` (project) as `<skill>/SKILL.md`.
+- After: Restart Vibe so it reloads config.toml.
+
+Source of truth: `src/installer/agent-table.ts` (one row per agent).

package/integrations/mistral-vibe/manifest-target.json

@@ -0,0 +1,3 @@
+{
+  "targets": []
+}

package/integrations/opencode/README.md

@@ -1,15 +1,12 @@
 # OpenCode integration
 
-Nothing is generated for OpenCode today. OpenCode consumes the npm package as
-a JavaScript module (`.opencode/plugins/summer.js`, wired via the package's
-`main` field). The plugin's `config` hook appends `<package>/library/skills`
-to `skills.paths` (OpenCode's `<dir>/<name>/SKILL.md` layout) and its
-`experimental.chat.messages.transform` hook prepends the Summer orientation to
-the first user message once per session. `summer setup opencode` writes the
-MCP entry to `opencode.json` (`type: "local"`, array `command`) and installs
-skills as markdown under `agents/summer/`. `manifest-target.json` is
-intentionally empty. Install steps: `.opencode/INSTALL.md`.
+No manifest file is generated in this repo for OpenCode — `manifest-target.json`
+is intentionally empty. Support is delivered at install time by
+`summer setup opencode` (aliases: `open-code`), which writes:
 
-If OpenCode grows a declarative manifest, add its builder to
-`scripts/generate-registry/manifests.ts` and its target to
-`scripts/generate-registry/targets.ts` (mirrored here).
+- MCP config: `~/.config/opencode/opencode.json`; Windows `%APPDATA%/opencode/opencode.json` (user); `opencode.json` (project).
+  Shape: `mcp.summer-engine = { type: "local", command: [npx, ...], enabled: true }`.
+- Skills: `~/.agents/skills` (user) or `.agents/skills` (project) as `<skill>/SKILL.md`. OpenCode loads skills from this folder on the next session. Summer 3.0 wrote markdown under agents/summer and 3.1.0 wrote opencode/skills; `--force` removes both.
+- After: Restart OpenCode so it reloads opencode.json.
+
+Source of truth: `src/installer/agent-table.ts` (one row per agent).

package/integrations/qoder/README.md

@@ -0,0 +1,12 @@
+# Qoder CLI integration
+
+No manifest file is generated in this repo for Qoder CLI — `manifest-target.json`
+is intentionally empty. Support is delivered at install time by
+`summer setup qoder` (aliases: `qoder-cli`), which writes:
+
+- MCP config: `~/.qoder/settings.json`; Windows `%USERPROFILE%/.qoder/settings.json` (user); `.mcp.json` (project).
+  Shape: `mcpServers.summer-engine = { command, args }`.
+- Skills: `~/.qoder/skills` (user) or `.qoder/skills` (project) as `<skill>/SKILL.md`.
+- After: Restart Qoder CLI so it reloads its MCP settings (the Qoder IDE manages servers in its UI).
+
+Source of truth: `src/installer/agent-table.ts` (one row per agent).

package/integrations/qoder/manifest-target.json

@@ -0,0 +1,3 @@
+{
+  "targets": []
+}

package/integrations/qwen-code/README.md

@@ -0,0 +1,12 @@
+# Qwen Code integration
+
+No manifest file is generated in this repo for Qwen Code — `manifest-target.json`
+is intentionally empty. Support is delivered at install time by
+`summer setup qwen-code` (aliases: `qwen`, `qwencode`), which writes:
+
+- MCP config: `~/.qwen/settings.json`; Windows `%USERPROFILE%/.qwen/settings.json` (user); `.qwen/settings.json` (project).
+  Shape: `mcpServers.summer-engine = { command, args }`.
+- Skills: `~/.qwen/skills` (user) or `.qwen/skills` (project) as `<skill>/SKILL.md`.
+- After: Restart Qwen Code or run /mcp in a new session.
+
+Source of truth: `src/installer/agent-table.ts` (one row per agent).

package/integrations/qwen-code/manifest-target.json

@@ -0,0 +1,3 @@
+{
+  "targets": []
+}

package/integrations/roo-code/README.md

@@ -1,13 +1,14 @@
 # Roo Code integration
 
+> **Legacy.** Roo Code shut down on 2026-05-15. The extension may still run, but it is no longer maintained; consider Cline or Kilo Code.
+
 No manifest file is generated in this repo for Roo Code — `manifest-target.json`
 is intentionally empty. Support is delivered at install time by
-`summer setup roo-code`, which writes:
+`summer setup roo-code` (aliases: `roo`, `roocode`), which writes:
 
-- MCP config: Roo Code's VS Code global storage (extension
-  `rooveterinaryinc.roo-cline`). User scope only — no project-scoped MCP config
-  today; project requests fall back to user scope with a warning.
-- Skills: `summer skills install --agent roo-code` writes rule files to Roo
-  Code's user rules directory (user scope) or `./.clinerules` (project scope).
+- MCP config: `~/Library/Application Support/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json`; Linux `~/.config/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json`; Windows `%APPDATA%/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json` (user); user scope only (project requests fall back with a warning).
+  Shape: `mcpServers.summer-engine = { command, args }`.
+- Skills: `~/Documents/Roo/Rules` (user) or `.clinerules` (project) as rule files `summer-<skill>.md`.
+- After: Restart VS Code so Roo Code reloads its MCP config.
 
-Source of truth: `src/installer/agent-config.ts`, `src/cli/commands/skills.ts`.
+Source of truth: `src/installer/agent-table.ts` (one row per agent).

package/integrations/rovo-dev/README.md

@@ -0,0 +1,12 @@
+# Rovo Dev CLI integration
+
+No manifest file is generated in this repo for Rovo Dev CLI — `manifest-target.json`
+is intentionally empty. Support is delivered at install time by
+`summer setup rovo-dev` (aliases: `rovodev`, `rovo`, `atlassian-rovo-dev`), which writes:
+
+- MCP config: `~/.rovodev/mcp.json`; Windows `%USERPROFILE%/.rovodev/mcp.json` (user); user scope only (project requests fall back with a warning).
+  Shape: undefined.
+- Skills: `~/.agents/skills` (user) or `.agents/skills` (project) as `<skill>/SKILL.md`.
+- After: Restart Rovo Dev CLI so it reconnects its MCP servers.
+
+Source of truth: `src/installer/agent-table.ts` (one row per agent).

package/integrations/rovo-dev/manifest-target.json

@@ -0,0 +1,3 @@
+{
+  "targets": []
+}

package/integrations/trae/README.md

@@ -0,0 +1,12 @@
+# Trae integration
+
+No manifest file is generated in this repo for Trae — `manifest-target.json`
+is intentionally empty. Support is delivered at install time by
+`summer setup trae` (aliases: `trae-ide`, `bytedance-trae`), which writes:
+
+- MCP config: `.trae/mcp.json` (user); `.trae/mcp.json` (project).
+  Shape: `mcpServers.summer-engine = { command, args }`.
+- Skills: none. Trae documents no skills folder; the MCP server ships summer_get_agent_playbook for in-chat guidance.
+- After: Restart Trae and open the MCP settings; summer-engine should show as connected.
+
+Source of truth: `src/installer/agent-table.ts` (one row per agent).

package/integrations/trae/manifest-target.json

@@ -0,0 +1,3 @@
+{
+  "targets": []
+}

package/integrations/visual-studio/README.md

@@ -0,0 +1,12 @@
+# GitHub Copilot in Visual Studio integration
+
+No manifest file is generated in this repo for GitHub Copilot in Visual Studio — `manifest-target.json`
+is intentionally empty. Support is delivered at install time by
+`summer setup visual-studio` (aliases: `vs`, `vs2026`, `visual-studio-2026`, `visualstudio`), which writes:
+
+- MCP config: `~/.mcp.json`; Windows `%USERPROFILE%/.mcp.json` (user); `.mcp.json` (project).
+  Shape: `servers.summer-engine = { type: "stdio", command, args }`.
+- Skills: none. Visual Studio's Copilot has no skills folder yet; the MCP server ships summer_get_agent_playbook for in-chat guidance.
+- After: Restart Visual Studio, open Copilot Chat in Agent mode, and enable summer-engine in the tools picker.
+
+Source of truth: `src/installer/agent-table.ts` (one row per agent).

package/integrations/visual-studio/manifest-target.json

@@ -0,0 +1,3 @@
+{
+  "targets": []
+}