summer-engine 2.8.2 → 3.0.0

package/hooks/pre-commit-doctor.sh

@@ -1,49 +1,55 @@
 #!/usr/bin/env bash
 # Summer Engine — Pre-commit doctor hook (OPT-IN)
 #
-# Event:    PreToolUse (matcher: Bash, if: "Bash(git commit*)")
-# Purpose:  Run `summer doctor` before any git commit Claude is about to make.
-#           Block the commit on FAIL. Allow with warnings on WARN.
+# Event:    PreToolUse (matcher: "Bash", if: "Bash(git commit*)") — registered
+#           in hooks/hooks.json (Claude Code) and hooks/hooks-cursor.json.
+# Purpose:  Run `summer doctor` before any git commit the agent is about to
+#           make. Block the commit on fail. Allow with warnings on warning.
 #
-# Status:   OPT-IN. Not registered in the Summer plugin manifest by default.
-#
-# To enable, add to ~/.claude/settings.json (or .claude/settings.json):
-#
-#   {
-#     "hooks": {
-#       "PreToolUse": [
-#         {
-#           "matcher": "Bash",
-#           "hooks": [
-#             {
-#               "type": "command",
-#               "command": "${CLAUDE_PLUGIN_ROOT}/hooks/pre-commit-doctor.sh",
-#               "if": "Bash(git commit*)",
-#               "timeout": 15
-#             }
-#           ]
-#         }
-#       ]
-#     }
-#   }
-#
-# Then: chmod +x ${CLAUDE_PLUGIN_ROOT}/hooks/pre-commit-doctor.sh
+# Status:   OPT-IN. The hook is always registered but exits 0 immediately
+#           unless one of these is set:
+#             CLAUDE_PLUGIN_OPTION_ENABLE_PRE_COMMIT_DOCTOR=true
+#               Claude Code exports every plugin userConfig value to hook
+#               processes as CLAUDE_PLUGIN_OPTION_<KEY>; this is the
+#               `enable_pre_commit_doctor` toggle from plugin.json.
+#             SUMMER_PRE_COMMIT_DOCTOR=1
+#               Manual / other-host opt-in (also the envVar Gemini's
+#               gemini-extension.json `settings` entry maps to).
 #
 # Input:    JSON on stdin: { tool_name, tool_input: { command, ... }, ... }
-# Output:   On FAIL: stderr explanation, exit 2 (blocks commit).
-#           On WARN: stderr warnings, exit 0 (allows commit).
-#           On PASS or no `summer` CLI: silent, exit 0.
+# Output:   On fail: stderr explanation, exit 2 (blocks commit).
+#           On warning: stderr warnings, exit 0 (allows commit).
+#           On ok, opt-in unset, or no `summer` CLI on PATH: silent, exit 0.
+#           (No npx fallback: a cold `npx summer-engine` download would blow
+#           the 30s hook budget mid-commit. Install the CLI to use this hook.)
+#
+# Doctor JSON shape (src/core/capabilities/doctor.ts):
+#   { ok, checks: [{ id, label, status: "ok"|"warning"|"fail", message }], summary }
 #
 # Portability: bash 3.2+, POSIX-friendly. jq optional.
 
 set +e
 
+# ---------- Opt-in gate ----------
+is_truthy() {
+    case "$(printf '%s' "$1" | tr '[:upper:]' '[:lower:]')" in
+        1|true|yes|on) return 0 ;;
+        *) return 1 ;;
+    esac
+}
+if ! is_truthy "${CLAUDE_PLUGIN_OPTION_ENABLE_PRE_COMMIT_DOCTOR:-}" \
+   && ! is_truthy "${SUMMER_PRE_COMMIT_DOCTOR:-}"; then
+    cat >/dev/null
+    exit 0
+fi
+
 INPUT=$(cat)
 
 # ---------- Parse the command ----------
 COMMAND=""
 if command -v jq >/dev/null 2>&1; then
-    COMMAND=$(printf '%s' "$INPUT" | jq -r '.tool_input.command // empty' 2>/dev/null)
+    # Claude Code PreToolUse: .tool_input.command; Cursor beforeShellExecution: .command
+    COMMAND=$(printf '%s' "$INPUT" | jq -r '.tool_input.command // .command // empty' 2>/dev/null)
 fi
 if [ -z "$COMMAND" ]; then
     COMMAND=$(printf '%s' "$INPUT" \
@@ -77,23 +83,23 @@ WARN_MSGS=""
 
 if command -v jq >/dev/null 2>&1; then
     FAIL_MSGS=$(printf '%s' "$DOCTOR_OUT" \
-        | jq -r '.checks[]? | select(.status == "FAIL") | "  - " + (.name // "?") + ": " + (.message // "")' 2>/dev/null)
+        | jq -r '.checks[]? | select((.status // "" | ascii_downcase) == "fail") | "  - " + (.label // .name // "?") + ": " + (.message // "")' 2>/dev/null)
     WARN_MSGS=$(printf '%s' "$DOCTOR_OUT" \
-        | jq -r '.checks[]? | select(.status == "WARN") | "  - " + (.name // "?") + ": " + (.message // "")' 2>/dev/null)
+        | jq -r '.checks[]? | select((.status // "" | ascii_downcase) | IN("warning", "warn")) | "  - " + (.label // .name // "?") + ": " + (.message // "")' 2>/dev/null)
     [ -n "$FAIL_MSGS" ] && HAS_FAIL=1
     [ -n "$WARN_MSGS" ] && HAS_WARN=1
 else
     # Fallback: substring sniffing
-    if printf '%s' "$DOCTOR_OUT" | grep -q '"status"[[:space:]]*:[[:space:]]*"FAIL"'; then
+    if printf '%s' "$DOCTOR_OUT" | grep -q '"status"[[:space:]]*:[[:space:]]*"(FAIL|fail)"'; then
         HAS_FAIL=1
         FAIL_MSGS=$(printf '%s' "$DOCTOR_OUT" \
-            | grep -oE '"status"[[:space:]]*:[[:space:]]*"FAIL"[^}]*"message"[[:space:]]*:[[:space:]]*"[^"]*"' \
+            | grep -oE '"status"[[:space:]]*:[[:space:]]*"(FAIL|fail)"[^}]*"message"[[:space:]]*:[[:space:]]*"[^"]*"' \
             | sed -E 's/.*"message"[[:space:]]*:[[:space:]]*"([^"]*)"/  - \1/')
     fi
-    if printf '%s' "$DOCTOR_OUT" | grep -q '"status"[[:space:]]*:[[:space:]]*"WARN"'; then
+    if printf '%s' "$DOCTOR_OUT" | grep -q '"status"[[:space:]]*:[[:space:]]*"(WARN|warn|warning)"'; then
         HAS_WARN=1
         WARN_MSGS=$(printf '%s' "$DOCTOR_OUT" \
-            | grep -oE '"status"[[:space:]]*:[[:space:]]*"WARN"[^}]*"message"[[:space:]]*:[[:space:]]*"[^"]*"' \
+            | grep -oE '"status"[[:space:]]*:[[:space:]]*"(WARN|warn|warning)"[^}]*"message"[[:space:]]*:[[:space:]]*"[^"]*"' \
             | sed -E 's/.*"message"[[:space:]]*:[[:space:]]*"([^"]*)"/  - \1/')
     fi
 fi
@@ -101,11 +107,11 @@ fi
 # ---------- FAIL: block ----------
 if [ "$HAS_FAIL" -eq 1 ]; then
     {
-        echo "=== Summer doctor: FAIL — commit blocked ==="
+        echo "=== Summer doctor: fail — commit blocked ==="
         echo "$FAIL_MSGS"
         echo ""
         echo "Fix the failures above, or run: summer doctor"
-        echo "To bypass once: disable the pre-commit-doctor hook in settings.json."
+        echo "To bypass: turn off the plugin option enable_pre_commit_doctor (or unset SUMMER_PRE_COMMIT_DOCTOR)."
         echo "============================================"
     } >&2
     exit 2
@@ -114,7 +120,7 @@ fi
 # ---------- WARN: allow with notice ----------
 if [ "$HAS_WARN" -eq 1 ]; then
     {
-        echo "=== Summer doctor: WARN — commit allowed ==="
+        echo "=== Summer doctor: warning — commit allowed ==="
         echo "$WARN_MSGS"
         echo "============================================"
     } >&2

package/hooks/run-hook.cmd

@@ -1,23 +1,30 @@
-#!/usr/bin/env bash
-# Cross-platform hook dispatcher.
-# Usage: run-hook.cmd <hook-name>
-# Reads stdin, forwards to <plugin-root>/hooks/<hook-name>.sh
-# On Windows, Claude Code / Cursor / Codex invoke this via Git-Bash.
-
-HOOK_NAME="$1"
-shift || true
-
-HOOK_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-HOOK_SCRIPT="$HOOK_DIR/$HOOK_NAME.sh"
-
-if [ ! -f "$HOOK_SCRIPT" ]; then
-  # Missing hook = no-op (don't break the host).
-  exit 0
-fi
-
-if [ ! -x "$HOOK_SCRIPT" ]; then
-  # Not executable yet (likely fresh checkout). Fall back to bash invocation.
-  exec bash "$HOOK_SCRIPT" "$@"
-fi
-
-exec "$HOOK_SCRIPT" "$@"
+:; exec bash "$(dirname "$0")/run-hook.sh" "$@"
+@echo off
+rem Summer Engine hook dispatcher — bash / cmd.exe polyglot.
+rem
+rem   bash (macOS, Linux, Git Bash): line 1 is a no-op ":" followed by an exec
+rem   into run-hook.sh; nothing below it is ever parsed. No shebang on purpose:
+rem   bash falls back to running a shebang-less file as a script, and cmd.exe
+rem   would otherwise print an error for the "#!" line.
+rem   cmd.exe / PowerShell (Windows without a bash hook shell): line 1 is a
+rem   label and is skipped; the batch below locates Git Bash and forwards, or
+rem   exits 0 so a missing bash never blocks the host.
+rem
+rem Usage: run-hook.cmd <hook-name>   (stdin is forwarded untouched)
+setlocal
+set "HOOK_DIR=%~dp0"
+where bash >nul 2>nul
+if %errorlevel%==0 (
+  bash "%HOOK_DIR%run-hook.sh" %*
+  exit /b %errorlevel%
+)
+if exist "%ProgramFiles%\Git\bin\bash.exe" (
+  "%ProgramFiles%\Git\bin\bash.exe" "%HOOK_DIR%run-hook.sh" %*
+  exit /b %errorlevel%
+)
+if exist "%LocalAppData%\Programs\Git\bin\bash.exe" (
+  "%LocalAppData%\Programs\Git\bin\bash.exe" "%HOOK_DIR%run-hook.sh" %*
+  exit /b %errorlevel%
+)
+echo Summer hooks need Git Bash on Windows; skipping hook. 1>&2
+exit /b 0

package/hooks/run-hook.sh

@@ -0,0 +1,20 @@
+#!/usr/bin/env bash
+# Cross-platform hook dispatcher (bash side).
+# Usage: run-hook.sh <hook-name>
+# Reads stdin, forwards to <plugin-root>/hooks/<hook-name>.sh
+# Hosts reference run-hook.cmd, a bash/cmd.exe polyglot that lands here on
+# every platform that has bash (macOS, Linux, Git Bash / WSL on Windows).
+
+HOOK_NAME="$1"
+shift || true
+
+HOOK_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+HOOK_SCRIPT="$HOOK_DIR/$HOOK_NAME.sh"
+
+if [ ! -f "$HOOK_SCRIPT" ]; then
+  # Missing hook = no-op (don't break the host).
+  exit 0
+fi
+
+# Always go through bash: fresh checkouts / npm tarballs may drop the exec bit.
+exec bash "$HOOK_SCRIPT" "$@"

package/hooks/session-start.sh

@@ -25,10 +25,17 @@ PROJECT_DIR="${CLAUDE_PROJECT_DIR:-$(pwd)}"
 LINES=()
 
 # Line 1: Summer ready + skill count
+# The count is the number of Summer skills actually loaded by THIS host — the
+# plugin's bundled library when running as a plugin. Outside a plugin root we
+# cannot tell Summer skills from the user's own, so the number is dropped
+# rather than reporting the whole library as if it were installed.
 SKILL_COUNT=""
-if command -v summer >/dev/null 2>&1; then
-    # `summer skills count` is best-effort; ignore failure
-    SKILL_COUNT=$(summer skills count 2>/dev/null | grep -oE '[0-9]+' | head -1)
+PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT:-${CURSOR_PLUGIN_ROOT:-}}"
+if [ -n "$PLUGIN_ROOT" ] && [ -d "${PLUGIN_ROOT}/library/skills" ]; then
+    SKILL_COUNT=$(find "${PLUGIN_ROOT}/library/skills" -mindepth 2 -maxdepth 2 -name SKILL.md 2>/dev/null | grep -c .)
+    case "$SKILL_COUNT" in
+        ''|0|*[!0-9]*) SKILL_COUNT="" ;;
+    esac
 fi
 if [ -n "$SKILL_COUNT" ]; then
     LINES+=("Summer ready. ${SKILL_COUNT} skills.")
@@ -57,18 +64,22 @@ if [ -f "${PROJECT_DIR}/project.godot" ]; then
     fi
 fi
 
-# Line 3: doctor FAIL one-liner (only on FAIL — silent on PASS/WARN)
+# Line 3: doctor fail one-liner (only on status "fail" — silent on ok/warning).
+# Doctor JSON (src/core/capabilities/doctor.ts): checks[].status is lowercase
+# "ok" | "warning" | "fail". Only runs when a `summer` CLI is on PATH: the
+# documented npx install never puts one there, and a cold `npx summer-engine`
+# fetch would exceed the 10s SessionStart budget, so we degrade silently.
 if command -v summer >/dev/null 2>&1; then
     DOCTOR_OUT=$(summer doctor --json 2>/dev/null)
     if [ -n "$DOCTOR_OUT" ]; then
         FAIL_REASON=""
         if command -v jq >/dev/null 2>&1; then
             FAIL_REASON=$(printf '%s' "$DOCTOR_OUT" \
-                | jq -r 'first(.checks[]? | select(.status == "FAIL") | .message) // empty' 2>/dev/null)
+                | jq -r 'first(.checks[]? | select((.status // "" | ascii_downcase) == "fail") | .message) // empty' 2>/dev/null)
         else
-            # Crude fallback: first "message" near a "FAIL"
+            # Crude fallback: first "message" near a "fail"
             FAIL_REASON=$(printf '%s' "$DOCTOR_OUT" \
-                | grep -oE '"status"[[:space:]]*:[[:space:]]*"FAIL"[^}]*"message"[[:space:]]*:[[:space:]]*"[^"]*"' \
+                | grep -oE '"status"[[:space:]]*:[[:space:]]*"(FAIL|fail)"[^}]*"message"[[:space:]]*:[[:space:]]*"[^"]*"' \
                 | head -1 \
                 | grep -oE '"message"[[:space:]]*:[[:space:]]*"[^"]*"' \
                 | sed 's/.*"message"[[:space:]]*:[[:space:]]*"//;s/"$//')

package/integrations/README.md

@@ -0,0 +1,70 @@
+# integrations/ — the complete, honest map of agent support
+
+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.
+
+Each folder contains:
+
+- `README.md` — what gets generated where, or (for clients with no manifest
+  file in this repo) exactly what `summer setup <client>` writes at install
+  time: MCP config path and skills destination.
+
+`summer setup <client>` (default `--scope user`) writes the MCP config AND
+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
+(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
+  (empty when nothing is generated). Mirrors
+  `scripts/generate-registry/targets.ts`; a test fails if they drift.
+
+Generated root dot-files (`.claude-plugin/plugin.json`, `gemini-extension.json`,
+…) are build artifacts of `integrations/<agent>` + `library/` — their
+`_generated` banner says so ("GENERATED from integrations/<agent> — do not
+edit; npm run generate:registry"). CI `--check` fails on any drift between
+`library/`, `registry/generated/`, and the applied root files.
+
+How the plugin manifests reference skills, and what is verified:
+
+- **Claude Code** — the plugin-manifest `skills` field accepts a string or an
+  array of `./`-relative directory paths and *extends* the default `skills/`
+  scan (Claude Code plugins reference, "Plugin manifest schema"). The
+  generated `.claude-plugin/plugin.json` lists one entry per skill
+  (`./library/skills/<slug>/`). The docs do not say whether a listed
+  directory is loaded as one skill or scanned for skill subfolders, and this
+  repo has not yet loaded the generated manifest through the real plugin
+  path (the smoke tests exercise the `summer setup` install path, not the
+  marketplace one) — treat the marketplace install as unverified until that
+  run exists.
+- **Codex** — `.codex-plugin/plugin.json` carries the same per-skill `skills`
+  array. Whether Codex reads that field, and with which type, is
+  **unverified**; the v2 manifest carried it and nobody has confirmed a load.
+- **Factory** — reads skills only from a root `skills/` directory; the
+  manifest's `skills` array is not read (open gap, see the table).
+
+| 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` |
+
+Source of truth for the setup paths: `src/installer/agent-config.ts` and
+`src/cli/commands/skills.ts`.

package/integrations/claude/README.md

@@ -0,0 +1,19 @@
+# Claude Code integration
+
+Generated by `scripts/generate-registry` from `library/**/resource.yaml`:
+
+- `registry/generated/plugin.claude.json` -> `.claude-plugin/plugin.json`
+  (plugin manifest: full skill list at `./library/skills/<slug>/`, hooks,
+  MCP pointer, userConfig; version stamped from `package.json`).
+- `registry/generated/marketplace.claude.json` -> `.claude-plugin/marketplace.json`
+  (marketplace listing wrapper).
+
+The MCP pointer `./.mcp.json` these manifests reference is generated as
+well (`registry/generated/mcp.json -> .mcp.json`, owned by the claude target).
+
+The MCP pointer `./.mcp.json` these manifests reference is generated as
+well (`registry/generated/mcp.json -> .mcp.json`).
+
+Never edit the destination files by hand — edit `library/` resources or the
+manifest builders in `scripts/generate-registry/manifests.ts`, then run
+`npm run generate:registry`. CI `--check` fails on any drift.

package/integrations/claude/manifest-target.json

@@ -0,0 +1,16 @@
+{
+  "targets": [
+    {
+      "generated": "plugin.claude.json",
+      "destination": ".claude-plugin/plugin.json"
+    },
+    {
+      "generated": "marketplace.claude.json",
+      "destination": ".claude-plugin/marketplace.json"
+    },
+    {
+      "generated": "mcp.json",
+      "destination": ".mcp.json"
+    }
+  ]
+}

package/integrations/cline/README.md

@@ -0,0 +1,13 @@
+# Cline integration
+
+No manifest file is generated in this repo for Cline — `manifest-target.json`
+is intentionally empty. Support is delivered at install time by
+`summer setup cline`, 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).
+
+Source of truth: `src/installer/agent-config.ts`, `src/cli/commands/skills.ts`.

package/integrations/cline/manifest-target.json

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

package/integrations/codex/README.md

@@ -0,0 +1,15 @@
+# Codex integration
+
+Generated by `scripts/generate-registry` from `library/**/resource.yaml`:
+
+- `registry/generated/plugin.codex.json` -> `.codex-plugin/plugin.json`
+  (plugin manifest with the Codex app-store `interface` block; full skill
+  list at `./library/skills/<slug>/` — the pre-v3 four-skill gap was a bug and
+  is fixed by generation; version stamped from `package.json`).
+
+The MCP pointer `./.mcp.json` these manifests reference is generated as
+well (`registry/generated/mcp.json -> .mcp.json`, owned by the claude target).
+
+Never edit the destination file by hand — edit `library/` resources or
+`scripts/generate-registry/manifests.ts`, then run
+`npm run generate:registry`. CI `--check` fails on any drift.

package/integrations/codex/manifest-target.json

@@ -0,0 +1,5 @@
+{
+  "targets": [
+    { "generated": "plugin.codex.json", "destination": ".codex-plugin/plugin.json" }
+  ]
+}

package/integrations/cursor/README.md

@@ -0,0 +1,16 @@
+# Cursor integration
+
+Generated by `scripts/generate-registry` from `library/**/resource.yaml`:
+
+- `registry/generated/plugin.cursor.json` -> `.cursor-plugin/plugin.json`
+  (Cursor plugin manifest: displayName/publisher/category, cursor-specific
+  hooks file `./hooks/hooks-cursor.json`, full skill list at
+  `./library/skills/<slug>/` — the pre-v3 four-skill gap was a bug and is fixed
+  by generation; version stamped from `package.json`).
+
+The MCP pointer `./.mcp.json` these manifests reference is generated as
+well (`registry/generated/mcp.json -> .mcp.json`, owned by the claude target).
+
+Never edit the destination file by hand — edit `library/` resources or
+`scripts/generate-registry/manifests.ts`, then run
+`npm run generate:registry`. CI `--check` fails on any drift.

package/integrations/cursor/manifest-target.json

@@ -0,0 +1,5 @@
+{
+  "targets": [
+    { "generated": "plugin.cursor.json", "destination": ".cursor-plugin/plugin.json" }
+  ]
+}

package/integrations/factory/README.md

@@ -0,0 +1,26 @@
+# Factory (Droid) integration
+
+Generated by `scripts/generate-registry` from `library/**/resource.yaml`:
+
+- `registry/generated/plugin.factory.json` -> `.factory-plugin/plugin.json`
+  (metadata manifest, now including the full skill list at
+  `./library/skills/<slug>/` — the pre-v3 manifest listed zero skills, which
+  was a bug fixed by generation; version stamped from `package.json`).
+
+There is no `summer setup factory` target (`summer setup` rejects `factory`).
+Install through the plugin marketplace instead:
+
+```
+droid plugin marketplace add https://github.com/summerengine/summer
+droid plugin install summer@summer-engine --scope user
+```
+
+Factory reads MCP servers from the plugin's root `.mcp.json` (generated) and
+skills ONLY from a root `skills/<name>/SKILL.md` directory; it has no `skills`
+manifest field, so the array in `plugin.factory.json` is inert and this package
+(skills under `library/skills/`) currently exposes no skills to Factory. Open
+gap; fix is a root `skills/` layout, not a setup target.
+
+Never edit the destination file by hand — edit `library/` resources or
+`scripts/generate-registry/manifests.ts`, then run
+`npm run generate:registry`. CI `--check` fails on any drift.

package/integrations/factory/manifest-target.json

@@ -0,0 +1,5 @@
+{
+  "targets": [
+    { "generated": "plugin.factory.json", "destination": ".factory-plugin/plugin.json" }
+  ]
+}

package/integrations/gemini/README.md

@@ -0,0 +1,26 @@
+# Gemini CLI integration
+
+Generated by `scripts/generate-registry` from `library/**/resource.yaml`:
+
+- `registry/generated/gemini-extension.json` -> `gemini-extension.json`
+  (extension manifest: MCP server, GEMINI.md context file, settings; version
+  stamped from `package.json`). The `skills` array is emitted for parity with
+  the other manifests but Gemini has no such field — it discovers extension
+  skills from `<extension>/skills/<name>/SKILL.md` and ignores unknown keys.
+
+`summer setup gemini` writes `~/.gemini/extensions/summer-engine/`:
+
+- `gemini-extension.json` — the generated manifest above with install-time
+  overrides: `name` becomes `summer-engine` (Gemini requires the manifest name
+  to match the extension directory), `mcpServers.summer-engine` becomes the
+  standard launcher (`npx -y summer-engine@latest mcp`, `cmd.exe /c` wrapped on
+  Windows) because `${extensionPath}` holds no npm package, `skills` and the
+  `_generated` banner are dropped.
+- `GEMINI.md` and `AGENTS.md` (the context file and the file it imports).
+- `skills/<slug>/SKILL.md` for every library skill (via
+  `skills install --all --agent gemini`); Gemini extensions are user-scoped, so
+  `--scope project` falls back to user with a warning.
+
+Never edit the destination file by hand — edit `library/` resources or
+`scripts/generate-registry/manifests.ts`, then run
+`npm run generate:registry`. CI `--check` fails on any drift.

package/integrations/gemini/manifest-target.json

@@ -0,0 +1,5 @@
+{
+  "targets": [
+    { "generated": "gemini-extension.json", "destination": "gemini-extension.json" }
+  ]
+}

package/integrations/github-copilot/README.md

@@ -0,0 +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:
+
+- 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).
+
+Source of truth: `src/installer/agent-config.ts`, `src/cli/commands/skills.ts`.

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

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

package/integrations/kilo-code/README.md

@@ -0,0 +1,16 @@
+# Kilo Code integration
+
+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:
+
+- 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.
+
+Source of truth: `src/installer/agent-config.ts`, `src/cli/commands/skills.ts`.

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

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

package/integrations/lm-studio/README.md

@@ -0,0 +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:
+
+- 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.
+
+Source of truth: `src/installer/agent-config.ts`, `src/installer/setup.ts`.

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

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

package/integrations/opencode/README.md

@@ -0,0 +1,15 @@
+# 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`.
+
+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).

package/integrations/opencode/manifest-target.json

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

package/integrations/roo-code/README.md

@@ -0,0 +1,13 @@
+# Roo Code integration
+
+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:
+
+- 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).
+
+Source of truth: `src/installer/agent-config.ts`, `src/cli/commands/skills.ts`.

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

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

package/integrations/vscode-copilot/README.md

@@ -0,0 +1,12 @@
+# VS Code Copilot integration
+
+No manifest file is generated in this repo for VS Code Copilot —
+`manifest-target.json` is intentionally empty. Support is delivered at install
+time by `summer setup vscode-copilot`, which writes:
+
+- MCP config: VS Code's user-profile `mcp.json` (user scope) or
+  `./.vscode/mcp.json` (project scope), in VS Code's MCP config format.
+- Skills: `summer skills install --agent vscode-copilot` writes skill files to
+  `~/.copilot/skills/` (user scope) or `./.github/skills/` (project scope).
+
+Source of truth: `src/installer/agent-config.ts`, `src/cli/commands/skills.ts`.

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

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