fa-mcp-sdk 0.4.69 → 0.4.71

package/cli-template/.claude/skills/{deploy-mcp → create-mcp-wizard}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: deploy-mcp
-description: "Implement an fa-mcp MCP server end-to-end in this already-scaffolded project: verify Agent Tester OpenAI creds, seed dev-time secrets and lenient config, push the scaffold to GitLab (creating a new repo OR reusing an existing one when instructed), draft an implementation plan, implement tools/prompts/resources, iterate via the Agent Tester headless API, then push the finished work. Use when the user asks to develop/implement/deploy the MCP server in this project, mentions 'deploy-mcp', 'развернуть MCP', 'реализовать MCP', or supplies a feature brief."
+name: create-mcp-wizard
+description: "Implement an fa-mcp MCP server end-to-end in this already-scaffolded project: verify Agent Tester OpenAI creds, seed dev-time secrets and lenient config, push the scaffold to GitLab (creating a new repo OR reusing an existing one when instructed), draft an implementation plan, implement tools/prompts/resources, iterate via the Agent Tester headless API, then push the finished work. Use when the user asks to develop/implement/deploy the MCP server in this project, mentions 'create-mcp-wizard', 'развернуть MCP', 'реализовать MCP', or supplies a feature brief."
 disable-model-invocation: true
 allowed-tools: Bash(node *), Bash(yarn *), Bash(npm *), Bash(git *), Bash(pwd), Bash(cd *), Bash(curl *), Read, Write, Edit, Glob, Grep
 ---
@@ -34,6 +34,13 @@ All supporting scripts live in `${CLAUDE_SKILL_DIR}/scripts/` and are invoked wi
   by the CLI / skill infrastructure and by the SDK maintainer. Do NOT modify, add, or delete files
   inside them unless the accompanying text explicitly instructs you to. This applies to every step
   below — implementation, tests, dev report, everything.
+- **Reporting language**. Language for all generated artifacts (`claudedocs/*.md`, commit
+  messages, user-facing summaries) is resolved in this order:
+    1. Explicit directive in the feature brief.
+    2. Else, contents of `preferred-language.txt` in the project root, if it exists.
+    3. Else — English.
+  Translate prose — headings and body text — to the resolved language; leave code, paths, YAML
+  keys, and CLI commands as-is. Report the resolved language and its source in the Step 1 summary.
 
 ## Step 1 — Scan the accompanying text for requirements
 
@@ -50,8 +57,10 @@ Before touching code, read every message/file the user attached and extract:
 - **Agent Tester OpenAI creds** — `apiKey` (required for Step 2) and `baseURL` (optional — Azure /
   proxy / local LLM). If the text already supplies them, use those. If `config/local.yaml` already
   has a working `agentTester.openAi.apiKey`, re-use it instead of asking again.
+- **Reporting language** — resolve per the Ground rule above; record it for later steps.
 
-Summarize what you found to the user in 3-6 bullets and get a one-line confirmation before proceeding.
+Summarize what you found to the user in 3-6 bullets (including the resolved reporting language
+and its source) and get a one-line confirmation before proceeding.
 
 ## Step 2 — Verify Agent Tester OpenAI credentials
 
@@ -128,7 +137,7 @@ what belongs in the initial commit. If the tree contains scratch notes, local-on
 anything the user flagged as not-for-commit, stash it with an untracked-inclusive stash:
 
 ```
-git stash push -u -m "deploy-mcp: pre-initial-push stash" -- <paths>
+git stash push -u -m "create-mcp-wizard: pre-initial-push stash" -- <paths>
 ```
 
 Announce what you stashed so the user can recover it later via `git stash list` / `git stash pop`.
@@ -205,7 +214,8 @@ OR switch to branch 4a if the "collision" is in fact the already-existing target
 
 ## Step 6 — Draft and commit to a plan
 
-Create `claudedocs/impl-plan.md` (create the directory if needed). Structure:
+Create `claudedocs/impl-plan.md` (create the directory if needed) in the reporting language.
+Structure:
 
 ```markdown
 # Implementation Plan — <project name>
@@ -245,7 +255,9 @@ Create `claudedocs/impl-plan.md` (create the directory if needed). Structure:
 - [ ] `yarn typecheck` clean
 - [ ] `yarn test:mcp`, `:mcp-http`, `:mcp-sse` all green
 - [ ] Agent Tester iterations done, `claudedocs/test-log.md` has entries
-- [ ] `claudedocs/dev-report.md` written
+- [ ] `claudedocs/dev-report.md` written (full report)
+- [ ] `claudedocs/breef-report.md` written (brief of work + problems — same content echoed to console)
+- [ ] `claudedocs/dev-problems.md` written (blockers, failed checks, open questions)
 - [ ] Final GitLab push (Step 10) complete
 ```
 
@@ -353,8 +365,9 @@ agent prompt, handler logic, error message — per `FA-MCP-SDK-DOC/08-agent-test
 fix, rebuild (`yarn cb`), restart, and re-run the scenario. After restart, in-memory sessions on
 the server are wiped — delete the stale `claudedocs/.agent-session` file before re-running.
 
-Log every iteration in `claudedocs/test-log.md` (session header + per-scenario: sent / expected /
-received / tools used / result / diagnosis / fix). This is the audit trail.
+Log every iteration in `claudedocs/test-log.md` in the reporting language (session header +
+per-scenario: sent / expected / received / tools used / result / diagnosis / fix). This is the
+audit trail.
 
 Stop the server with `node scripts/kill-port.js <port>` (or Ctrl+C) when you're done iterating.
 
@@ -373,9 +386,22 @@ yarn test:mcp-sse
 
 Zero errors, zero warnings that matter, all transport tests green.
 
-Write `claudedocs/dev-report.md` per the structure in `CLAUDE.md` → "Development Report"
-(what was built, architecture decisions, agent prompt rationale, test coverage, Agent Tester findings,
-configuration, known limitations).
+Write `claudedocs/dev-report.md` in the reporting language, following the structure in
+`CLAUDE.md` → "Development Report" (what was built, architecture decisions, agent prompt rationale,
+test coverage, Agent Tester findings, configuration, known limitations).
+
+Alongside the full report, produce two companion files in the reporting language:
+
+- **`claudedocs/breef-report.md`** — a brief of the work done and problems encountered. Keep it
+  short and scannable (not a duplicate of `dev-report.md`): what was implemented, what passed,
+  what failed, the key problems in 1–2 lines each. The same content is echoed verbatim to the
+  console as part of the "Final report" step below — that is the primary way the user sees it.
+- **`claudedocs/dev-problems.md`** — a focused list of what could NOT be done / tested / connected
+  to during this session, plus any open questions, unresolved blockers, or decisions the user
+  needs to make. Include: failed external connections (DB, upstream API, AD, Consul, etc.),
+  tests that were skipped or disabled and why, missing creds, ambiguous requirements from the
+  brief, anything deferred. If there are no problems, write the file anyway with a single
+  "No outstanding issues." line so the user can see the check was done.
 
 ## Step 10 — Final GitLab push
 
@@ -386,7 +412,7 @@ implemented feature and pushes it on top of the scaffold commit.
 content that shouldn't ship to the remote, stash it first:
 
 ```
-git stash push -u -m "deploy-mcp: pre-final-push stash" -- <paths>
+git stash push -u -m "create-mcp-wizard: pre-final-push stash" -- <paths>
 ```
 
 Leave anything stashed from Step 5 still stashed — if it shouldn't be in the initial commit, it
@@ -423,8 +449,14 @@ Tell the user:
    (Step 5) and the feature push (Step 10) landed on `main`.
 3. Summary of tools/resources/prompts/endpoints that were implemented.
 4. Any flagged limitations from the dev report.
-5. Link to `claudedocs/impl-plan.md`, `claudedocs/test-log.md`, `claudedocs/dev-report.md`.
+5. Links to `claudedocs/impl-plan.md`, `claudedocs/test-log.md`, `claudedocs/dev-report.md`,
+   `claudedocs/breef-report.md`, `claudedocs/dev-problems.md`.
 6. Anything still stashed from Step 5 / Step 10 (so the user remembers to `git stash pop` or drop).
+7. **Echo the full contents of `claudedocs/breef-report.md` to the console** (in the reporting
+   language, as written). This is the brief of work done + problems — it must appear inline in
+   the chat, not only as a file link, so the user can read it without opening the file. If
+   `claudedocs/dev-problems.md` contains anything other than "No outstanding issues.", also call
+   that out explicitly and point at the file.
 
 ## Troubleshooting
 

package/cli-template/.claude/skills/{deploy-mcp → create-mcp-wizard}/scripts/headless-test.js

@@ -1,6 +1,6 @@
 #!/usr/bin/env node
 /**
- * Thin wrapper around POST /agent-tester/api/chat/test — used by the deploy-mcp skill
+ * Thin wrapper around POST /agent-tester/api/chat/test — used by the create-mcp-wizard skill
  * to exercise the freshly-built MCP server through the full agent loop.
  *
  * Usage:
@@ -107,4 +107,4 @@ const req = http.request({
 req.on('error', (e) => { console.error(`request error: ${e.message}`); process.exit(1); });
 req.on('timeout', () => { req.destroy(new Error('timeout')); });
 req.write(payload);
-req.end();
+req.end();

package/cli-template/.claude/skills/upgrade-guide/SKILL.md

@@ -110,10 +110,15 @@ Wait for completion. If it fails, report the error and stop.
 
 Run:
 ```bash
-node ./node_modules/fa-mcp-sdk/scripts/update-doc.js
+node ./node_modules/fa-mcp-sdk/scripts/update-sdk.js
 ```
 
-This copies the latest `FA-MCP-SDK-DOC/` from the SDK into the project.
+This copies the latest `FA-MCP-SDK-DOC/` and `.claude/` from the SDK into the project.
+
+**Pinned folders.** Any folder under the project's `.claude/` that contains a direct file named
+`pin` is preserved as-is — the script neither deletes it nor overwrites it with template content.
+Drop a `pin` file into `.claude/skills/<your-skill>/` (or any other `.claude/` subdirectory) to
+protect local customizations from being reset on upgrade.
 
 ## Step 4: Analyze Changes in SDK Between Versions
 
@@ -187,7 +192,7 @@ Map of template file → project file (the CLI `bin/fa-mcp.js` applies these tra
 | `node_modules/fa-mcp-sdk/cli-template/.claude/skills/<skill>/`    | `.claude/skills/<skill>/`                   | overwrite unless locally customized |
 | `node_modules/fa-mcp-sdk/cli-template/r/<name>.xml`               | `.run/<name>.run.xml`                       | **Renamed** — see rule below |
 | `node_modules/fa-mcp-sdk/cli-template/gitignore`                  | `.gitignore`                                | source has no leading dot |
-| `node_modules/fa-mcp-sdk/cli-template/FA-MCP-SDK-DOC/`            | `FA-MCP-SDK-DOC/`                           | auto-updated by `update-doc.js` |
+| `node_modules/fa-mcp-sdk/cli-template/FA-MCP-SDK-DOC/`            | `FA-MCP-SDK-DOC/`                           | auto-updated by `update-sdk.js` |
 
 #### Rule: package.json — ADD ONLY new dependencies, do NOT touch anything else
 
@@ -286,7 +291,7 @@ Generated: <timestamp>
 ### New Configuration Keys
 
 <For each new key, provide:>
-- Key path (e.g., `webServer.adminAuth.type`)
+- Key path (e.g., `webServer.auth.enabled`)
 - Default value
 - Description
 - Whether it needs to be added to the project's config
@@ -403,7 +408,7 @@ changes specifically affect THIS project. Add a section to the guide:
 - When comparing YAML configs, preserve comments and structure.
 - **Correlate config file changes**: when `config/default.yaml` changes, ALWAYS also check `config/_local.yaml` in the SDK. Report whether `_local.yaml` has analogous changes or needs manual updates. Also advise checking the project's `config/local.yaml` for stale overrides that may conflict with the new defaults.
 - **Do not forget `config/local.yaml` in the project**: the project's `config/local.yaml` overrides `config/default.yaml`. When new keys are added or sections restructured in `default.yaml`, explicitly instruct the user to verify that their `config/local.yaml` doesn't have stale overrides that conflict with the new structure, and to add any new keys there too if they want non-default values.
-- Do not modify project files other than `package.json` (via yarn add) and `FA-MCP-SDK-DOC/` (via update-doc.js) unless the user explicitly asks.
+- Do not modify project files other than `package.json` (via yarn add) and `FA-MCP-SDK-DOC/` (via update-sdk.js) unless the user explicitly asks.
 - The migration guide must contain ACTIONABLE instructions with exact code/config snippets — not vague recommendations.
 - If GitHub API is unavailable or rate-limited, fall back to comparing files directly from `node_modules/fa-mcp-sdk/` against project files.
 - Write the guide in the language detected from the user's arguments (default: **English**). Translate all headings, prose, and descriptions. Keep file paths, YAML keys, code blocks, and shell commands in English.

package/cli-template/gitignore

@@ -90,3 +90,4 @@ glm.sh
 /.serena/
 /.playwright-mcp/
 /claudedocs/
+preferred-language.txt

package/cli-template/package.json

@@ -22,7 +22,7 @@
     "generate-token": "node node_modules/fa-mcp-sdk/dist/core/auth/token-generator/server.js",
     "dead:exports": "ts-prune",
     "dead:files": "knip",
-    "update-sdk-docs": "node ../scripts/update-doc.js",
+    "update-sdk-docs": "node ../scripts/update-sdk.js",
     "postinstall": "node ../scripts/npm/patch_node_modules.js",
     "check-llm": "node node_modules/fa-mcp-sdk/dist/core/agent-tester/check-llm.js",
     "consul:unreg": "node node_modules/fa-mcp-sdk/dist/core/consul/deregister.js",
@@ -50,7 +50,7 @@
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.29.0",
     "dotenv": "^17.4.1",
-    "fa-mcp-sdk": "^0.4.69"
+    "fa-mcp-sdk": "^0.4.71"
   },
   "devDependencies": {
     "@types/express": "^5.0.6",

package/cli-template/r/{update-doc.js.xml → update-sdk.js.xml}

@@ -1,5 +1,5 @@
-<component name="ProjectRunConfigurationManager">
-  <configuration default="false" name="update-doc.js" type="NodeJSConfigurationType" nameIsGenerated="true" path-to-js-file="scripts/update-doc.js" working-dir="$PROJECT_DIR$">
-    <method v="2" />
-  </configuration>
-</component>
+<component name="ProjectRunConfigurationManager">
+  <configuration default="false" name="update-sdk.js" type="NodeJSConfigurationType" nameIsGenerated="true" path-to-js-file="scripts/update-sdk.js" working-dir="$PROJECT_DIR$">
+    <method v="2" />
+  </configuration>
+</component>

package/cli-template/readme-docs/SKILLS.md

@@ -140,7 +140,7 @@ Characteristics:
 
 ---
 
-### `/deploy-mcp` — End-to-End MCP Server Implementation
+### `/create-mcp-wizard` — End-to-End MCP Server Implementation
 
 Orchestrates the full implementation workflow from feature brief to a live GitLab repo. The project
 must already be scaffolded by the `fa-mcp` CLI — this skill picks up from `yarn install` onwards.
@@ -169,20 +169,25 @@ Pipeline (10 steps):
 
 Characteristics:
 
-- **Launch**: **command-only** via `/deploy-mcp`. `disable-model-invocation: true` — does NOT
+- **Launch**: **command-only** via `/create-mcp-wizard`. `disable-model-invocation: true` — does NOT
   trigger on implicit mentions
 - **Input**: feature brief comes from the accompanying user message(s) and attached files. OpenAI
   and GitLab creds may be supplied inline or asked interactively
 - **Ground rules**: every step explicit and verified; free-form inputs asked in plain prose (never
   predefined options); exclusions from the brief honoured; dev defaults intentionally lenient;
   `.claude/`, `deploy/`, `FA-MCP-SDK-DOC/` are NOT modified unless the brief explicitly says to
+- **Reporting language**: all generated artifacts (`claudedocs/*.md`, commit messages, user-facing
+  summaries) are written in a language resolved in this order: (1) explicit directive in the
+  feature brief, else (2) contents of `preferred-language.txt` in the project root, else
+  (3) English. Prose (headings + body) is translated; code, paths, YAML keys, and CLI commands
+  stay as-is
 - **Output**: implemented project + `claudedocs/{impl-plan,test-log,dev-report}.md`, GitLab repo
   with two commits on `main` (scaffold + feature)
 
 **Examples:**
 
 ```
-/deploy-mcp
-/deploy-mcp реализуй инструменты из task.md, OpenAI key sk-..., GitLab group mcp-servers
-/deploy-mcp implement tools from the message; repo уже существует, push to git@gitlab.example:ai/mcp-foo.git
+/create-mcp-wizard
+/create-mcp-wizard реализуй инструменты из task.md, OpenAI key sk-..., GitLab group mcp-servers
+/create-mcp-wizard implement tools from the message; repo уже существует, push to git@gitlab.example:ai/mcp-foo.git
 ```

package/config/_local.yaml

@@ -24,6 +24,26 @@
 #     #> Override the Consul service name to look up (defaults to the alias key)
 #     consulServiceName: <consulServiceName>
 
+#> ========================================================================
+#> ADMIN PANEL
+#> Token generation & validation UI served at /admin.
+#> Supports 4 authentication methods: permanentServerTokens, basic, jwtToken, ntlm.
+#> ========================================================================
+adminPanel:
+  #> Enable/disable admin panel. false — /admin is not mounted at all.
+  enabled: true
+  #> Authentication type: 'permanentServerTokens' | 'basic' | 'jwtToken' | 'ntlm' | 'none'
+  #> Accepts a single type (string) or multiple types (array):
+  #>   authType: 'basic'
+  #>   authType: ['jwtToken', 'basic']
+  #> 'none' / null / empty array / not set → panel opens WITHOUT authentication
+  #>   (convenience for local development and debugging; do NOT use in production).
+  #> For permanentServerTokens, basic, jwtToken — uses credentials from webServer.auth section.
+  #> For ntlm — uses AD configuration from ad.domains section.
+  #> When multiple types are set (e.g. ['jwtToken', 'basic']), the login page shows tabs
+  #> to choose between Token and Login (username/password) authentication.
+  authType: 'basic'
+
 #> Active Directory / LDAP settings.
 #> Used for authentication/authorization (e.g., NTLM in admin panel) and checking user membership in AD groups.
 ad:
@@ -325,21 +345,3 @@ webServer:
   #> Requires valid Authorization header (any method configured in webServer.auth).
   #> ========================================================================
   genJwtApiEnable: false
-
-  #> ========================================================================
-  #> ADMIN PANEL AUTHENTICATION
-  #> Token generation page available at /admin endpoint
-  #> Supports 4 authentication methods: permanentServerTokens, basic, jwtToken, ntlm
-  #> ========================================================================
-  adminAuth:
-    #> Enable/disable admin panel
-    enabled: true
-    #> Authentication type for admin panel: 'permanentServerTokens' | 'basic' | 'jwtToken' | 'ntlm'
-    #> Accepts a single type (string) or multiple types (array):
-    #>   type: 'basic'
-    #>   type: ['jwtToken', 'basic']
-    #> For permanentServerTokens, basic, jwtToken — uses credentials from webServer.auth section
-    #> For ntlm — uses AD configuration from ad.domains section (no additional credentials needed)
-    #> When multiple types are set (e.g. ['jwtToken', 'basic']), the login page shows tabs
-    #> to choose between Token and Login (username/password) authentication.
-    type: 'basic'

package/config/local.yaml

@@ -11,6 +11,9 @@ agentTester:
     baseURL: https://litellm.finam.ru/v1
     exposeToClient: true
 
+adminPanel:
+  enabled: true
+  authType: [ 'permanentServerTokens', 'basic', 'jwtToken' ]
 
 ad:
   domains:
@@ -104,7 +107,3 @@ webServer:
 
 
   genJwtApiEnable: false
-  adminAuth:
-    enabled: true
-    # 'permanentServerTokens' | 'basic' | 'jwtToken' | 'ntlm'
-    type: [ 'permanentServerTokens', 'basic', 'jwtToken' ]

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "fa-mcp-sdk",
   "productName": "FA MCP SDK",
-  "version": "0.4.69",
+  "version": "0.4.71",
   "description": "Core infrastructure and templates for building Model Context Protocol (MCP) servers with TypeScript",
   "type": "module",
   "main": "dist/core/index.js",

package/scripts/update-sdk.js

@@ -0,0 +1,111 @@
+#!/usr/bin/env node
+import { cpSync, existsSync, mkdirSync, readFileSync, readdirSync, rmSync, writeFileSync } from 'fs';
+import { basename, dirname, join, relative, sep } from 'path';
+
+const templateDir = join(process.cwd(), './node_modules/fa-mcp-sdk/cli-template');
+const cwd = process.cwd();
+
+const targets = [
+  { name: 'FA-MCP-SDK-DOC', src: join(templateDir, 'FA-MCP-SDK-DOC'), dest: join(cwd, 'FA-MCP-SDK-DOC') },
+  {
+    name: '.claude',
+    src: join(templateDir, '.claude'),
+    dest: join(cwd, '.claude'),
+    preserve: ['settings.json'],
+    respectPin: true,
+  },
+];
+
+// A folder containing a direct file named `pin` is preserved untouched —
+// it is neither deleted nor overwritten with new content from the template.
+function findPinnedFolders (rootDir) {
+  const pinned = new Set();
+  if (!existsSync(rootDir)) {return pinned;}
+  const walk = (currentDir) => {
+    const entries = readdirSync(currentDir, { withFileTypes: true });
+    if (entries.some((e) => e.isFile() && e.name === 'pin')) {
+      const rel = relative(rootDir, currentDir);
+      if (rel) {pinned.add(rel);}
+      return;
+    }
+    for (const entry of entries) {
+      if (entry.isDirectory()) {walk(join(currentDir, entry.name));}
+    }
+  };
+  walk(rootDir);
+  return pinned;
+}
+
+function isInsidePinned (relPath, pinned) {
+  if (!relPath) {return false;}
+  if (pinned.has(relPath)) {return true;}
+  for (const p of pinned) {
+    if (relPath.startsWith(p + sep)) {return true;}
+  }
+  return false;
+}
+
+function cleanExceptPinned (rootDir, pinned) {
+  if (!existsSync(rootDir)) {return;}
+  const walk = (currentDir) => {
+    const entries = readdirSync(currentDir, { withFileTypes: true });
+    for (const entry of entries) {
+      const full = join(currentDir, entry.name);
+      const fullRel = relative(rootDir, full);
+      if (pinned.has(fullRel)) {continue;}
+      const hasPinnedDescendant = [...pinned].some((p) => p.startsWith(fullRel + sep));
+      if (entry.isDirectory() && hasPinnedDescendant) {
+        walk(full);
+      } else {
+        rmSync(full, { recursive: true, force: true });
+      }
+    }
+  };
+  walk(rootDir);
+}
+
+for (const { name, src, dest, preserve = [], respectPin = false } of targets) {
+  if (!existsSync(src)) {
+    console.error('Source not found:', src);
+    process.exit(1);
+  }
+  const saved = {};
+  for (const file of preserve) {
+    const p = join(dest, file);
+    if (existsSync(p)) {saved[file] = readFileSync(p);}
+  }
+
+  const pinned = respectPin ? findPinnedFolders(dest) : new Set();
+
+  if (existsSync(dest)) {
+    if (pinned.size > 0) {
+      cleanExceptPinned(dest, pinned);
+    } else {
+      rmSync(dest, { recursive: true });
+    }
+  }
+
+  cpSync(src, dest, {
+    recursive: true,
+    filter: (srcPath) => {
+      if (preserve.includes(basename(srcPath))) {return false;}
+      if (respectPin && pinned.size > 0) {
+        const rel = relative(src, srcPath);
+        if (isInsidePinned(rel, pinned)) {return false;}
+      }
+      return true;
+    },
+  });
+
+  for (const [file, content] of Object.entries(saved)) {
+    const p = join(dest, file);
+    mkdirSync(dirname(p), { recursive: true });
+    writeFileSync(p, content);
+  }
+
+  if (pinned.size > 0) {
+    console.log(`${name} updated (pinned folders preserved: ${[...pinned].join(', ')})`);
+  } else {
+    console.log(`${name} updated`);
+  }
+}

package/scripts/update-doc.js

@@ -1,36 +0,0 @@
-#!/usr/bin/env node
-import { cpSync, existsSync, mkdirSync, readFileSync, rmSync, writeFileSync } from 'fs';
-import { basename, dirname, join } from 'path';
-
-const templateDir = join(process.cwd(), './node_modules/fa-mcp-sdk/cli-template');
-const cwd = process.cwd();
-
-const targets = [
-  { name: 'FA-MCP-SDK-DOC', src: join(templateDir, 'FA-MCP-SDK-DOC'), dest: join(cwd, 'FA-MCP-SDK-DOC') },
-  { name: '.claude', src: join(templateDir, '.claude'), dest: join(cwd, '.claude'), preserve: ['settings.json'] },
-];
-
-for (const { name, src, dest, preserve = [] } of targets) {
-  if (!existsSync(src)) {
-    console.error('Source not found:', src);
-    process.exit(1);
-  }
-  const saved = {};
-  for (const file of preserve) {
-    const p = join(dest, file);
-    if (existsSync(p)) saved[file] = readFileSync(p);
-  }
-  if (existsSync(dest)) {
-    rmSync(dest, { recursive: true });
-  }
-  cpSync(src, dest, {
-    recursive: true,
-    filter: (srcPath) => !preserve.includes(basename(srcPath)),
-  });
-  for (const [file, content] of Object.entries(saved)) {
-    const p = join(dest, file);
-    mkdirSync(dirname(p), { recursive: true });
-    writeFileSync(p, content);
-  }
-  console.log(`${name} updated`);
-}