@taptap/instant-games-open-mcp 1.24.0 → 1.24.2

package/README.md

@@ -52,8 +52,8 @@ Maker 本地开发按“初始化用 CLI，开发循环用 MCP”拆分。首次
 npx -y -p @taptap/maker taptap-maker init
 ```
 
-CLI 负责一次性流程：Git 检查、PAT 保存、TapTap token 换取、app 列表选择、AI dev kit
-准备、Maker Git clone、MCP 配置写入与基础验证。安装或修改 MCP 配置后，Claude Code /
+CLI 负责一次性流程：Git 检查、PAT 保存、TapTap token 换取、app 列表选择、Maker Git
+clone、AI dev kit 准备、MCP 配置写入与基础验证。安装或修改 MCP 配置后，Claude Code /
 Codex / Cursor 通常需要重启会话、刷新 MCP 或新开窗口才会出现新的 MCP tools；但当前终端
 里的 CLI 初始化流程可以继续完成到 PAT 鉴权和项目绑定。
 
@@ -132,9 +132,9 @@ Maker 现在同时内置三个工作流 skill：
 - `taptap-maker-dev-kit-guide`：介绍 clone 时安装到项目目录的 AI dev kit，明确 `CLAUDE.md`、`examples/`、`templates/`、`urhox-libs/` 的用途。
 - `update-taptap-mcp`：引导用户更新本地 npx 缓存里的 `@taptap/maker`，并提醒 Maker MCP 推荐安装到 user/global scope。
 
-初始化流程里，PAT 验证通过、用户选择 app 后，`taptap-maker init` 会自动准备本地 AI dev kit。
+初始化流程里，PAT 验证通过、用户选择 app 后，`taptap-maker init` 会先完成 Maker Git checkout，再自动准备本地 AI dev kit。
 
-CLI 会根据 `TAPTAP_MCP_ENV` 自动选择下载源：`production`（默认）使用 `https://urhox-demo-platform.spark.xd.com/ai-dev-kit/pd/stable/ai-dev-kit.zip`，`rnd` 使用 `https://urhox-demo-platform.spark.xd.com/ai-dev-kit/rnd/latest/ai-dev-kit.zip`，解压开发环境文档、引擎 API、demo、Lua 工具和本地 AI skills 到当前目录；解压复制完成后会自动运行 `tools/install-skills.sh all`（Linux/macOS）或 `tools/install-skills.ps1 all`（Windows），把 dev kit skills 安装到各 Agent 的发现目录。CLI 会先输出 `AI skills install started: <script>`，完成后输出 `AI skills install result: claude=N, codex=N, cursor=N, gemini=N`；脚本缺失、跳过或失败时也会输出原因，失败会带上平台、脚本、命令、stdout 和 stderr，方便 AI 与用户直接判断安装情况。流程会跳过 ZIP 里的顶层 `scripts` 目录并删除下载 ZIP，避免和 Maker 项目代码冲突。clone 前会先生成 `.gitignore.dev-kit-before-clone` 临时 block，clone 成功后自动合并到远端 `.gitignore`，防止这些本地开发环境文件、Agent skill 目录和 `.maker/` 本地运行状态被提交到 Maker Git。
+CLI 会根据 `TAPTAP_MCP_ENV` 自动选择下载源：`production`（默认）使用 `https://urhox-demo-platform.spark.xd.com/ai-dev-kit/pd/stable/ai-dev-kit.zip`，`rnd` 使用 `https://urhox-demo-platform.spark.xd.com/ai-dev-kit/rnd/latest/ai-dev-kit.zip`，checkout 后解压开发环境文档、引擎 API、demo、Lua 工具和本地 AI skills 到当前目录，并用 dev kit 覆盖同名本地辅助文件；解压复制完成后会自动运行 `tools/install-skills.sh all`（Linux/macOS）或 `tools/install-skills.ps1 all`（Windows），把 dev kit skills 安装到各 Agent 的发现目录。CLI 会先输出 `AI skills install started: <script>`，完成后输出 `AI skills install result: claude=N, codex=N, cursor=N, gemini=N`；脚本缺失、跳过或失败时也会输出原因，失败会带上平台、脚本、命令、stdout 和 stderr，方便 AI 与用户直接判断安装情况。流程会跳过 ZIP 里的顶层 `scripts` 目录并删除下载 ZIP，避免和 Maker 项目代码冲突。dev-kit 准备阶段会生成 `.gitignore.dev-kit-before-clone` 临时 block，准备成功后自动合并到远端 `.gitignore`，防止这些本地开发环境文件、Agent skill 目录和 `.maker/` 本地运行状态被提交到 Maker Git。
 
 `maker://status` 和 `maker_status_lite` 会输出已随包内置的 skill 名称和文档路径：`taptap-maker-local`、`taptap-maker-dev-kit-guide` 与 `update-taptap-mcp`。Maker 操作目标是用户当前项目目录；若 MCP 进程 cwd 是临时对话目录，Agent 应把用户当前项目目录作为 `target_dir` 传入，不扫描其他项目。已绑定项目会检查 `CLAUDE.md`、`examples/`、`templates/`、`urhox-libs/`，并输出 `skill_install_status` 和 `skill_install_summary` 说明 `.claude/.codex/.cursor/.gemini` 下的 skill 安装状态；缺失时用 `taptap-maker dev-kit update` 恢复本地 AI dev kit 并刷新 `.gitignore` 管理块。
 

package/dist/maker.js

@@ -28891,7 +28891,7 @@ var DEV_KIT_IGNORE_BEGIN = "# >>> TapTap Maker AI dev kit (local only) >>>";
 var DEV_KIT_IGNORE_END = "# <<< TapTap Maker AI dev kit (local only) <<<";
 var DEV_KIT_GITIGNORE_STAGING_FILE = ".gitignore.dev-kit-before-clone";
 var DEV_KIT_REQUIRED_ENTRIES = ["CLAUDE.md", "examples", "templates", "urhox-libs"];
-var ALWAYS_IGNORED_LOCAL_ENTRIES = [".DS_Store", ".maker"];
+var ALWAYS_IGNORED_LOCAL_ENTRIES = [".DS_Store", ".maker", ".installer"];
 var DEV_KIT_MANAGED_ENTRY_CANDIDATES = [
   ".claude",
   ".cli",
@@ -31213,7 +31213,7 @@ function compactRuntimeLogEntry(entry) {
 }
 
 // src/maker/server/mcp.ts
-var VERSION = true ? "1.24.0" : "dev";
+var VERSION = true ? "1.24.2" : "dev";
 var DEFAULT_BUILD_TIMEOUT_MS = 10 * 60 * 1e3;
 var PREVIEW_REFRESH_TIMEOUT_MS = 15 * 1e3;
 var WATCHER_STOP_TIMEOUT_MS = 1500;
@@ -32914,7 +32914,6 @@ async function runInit(parsed, ctx) {
     env,
     selected_app_id: selected.id
   });
-  await prepareDevKit(targetDir, ctx);
   const cloneResult = await cloneMakerProject({
     appId: selected.id,
     targetDir,
@@ -32926,6 +32925,10 @@ async function runInit(parsed, ctx) {
     throw appendPatRecoveryUrl(error2, parsed);
   });
   emit(ctx, "clone", "Maker project cloned or fetched", cloneResult);
+  await prepareDevKit(targetDir, ctx, {
+    finalizeGitignore: true,
+    forceInstall: true
+  });
   if (!skipMcpInstall) {
     const ides = parseIdeList(stringOption(parsed, "register_mcp") || "codex,cursor,claude");
     const installResults = installMcpConfigs({
@@ -33342,17 +33345,20 @@ async function resolveProjectSelection(parsed, projects, options) {
     return selected;
   }
 }
-async function prepareDevKit(targetDir, ctx) {
+async function prepareDevKit(targetDir, ctx, options = {}) {
   const before = inspectAiDevKit(targetDir);
-  if (before.ready) {
-    writeDevKitStagedGitignore(
-      path9.join(targetDir, DEV_KIT_GITIGNORE_STAGING_FILE),
-      listPresentDevKitManagedEntries(targetDir)
-    );
+  if (before.ready && !options.forceInstall) {
     try {
       const skillInstaller = installAiDevKitSkills(targetDir, {
         onStart: (event) => emitSkillInstallerStart(ctx, event)
       });
+      writeDevKitStagedGitignore(
+        path9.join(targetDir, DEV_KIT_GITIGNORE_STAGING_FILE),
+        listPresentDevKitManagedEntries(targetDir)
+      );
+      if (options.finalizeGitignore) {
+        finalizeStagedDevKitGitignore(targetDir);
+      }
       emit(
         ctx,
         "dev_kit",
@@ -33363,6 +33369,13 @@ async function prepareDevKit(targetDir, ctx) {
         }
       );
     } catch (error2) {
+      writeDevKitStagedGitignore(
+        path9.join(targetDir, DEV_KIT_GITIGNORE_STAGING_FILE),
+        listPresentDevKitManagedEntries(targetDir)
+      );
+      if (options.finalizeGitignore) {
+        finalizeStagedDevKitGitignore(targetDir);
+      }
       const detail = error2 instanceof Error ? error2.message : String(error2);
       emit(ctx, "dev_kit_warning", `AI skills install failed; clone will continue
 ${detail}`, {
@@ -33374,8 +33387,12 @@ ${detail}`, {
   try {
     const result = await installAiDevKit({
       targetDir,
+      preserveExisting: options.preserveExisting,
       onSkillInstallerStart: (event) => emitSkillInstallerStart(ctx, event)
     });
+    if (options.finalizeGitignore) {
+      finalizeStagedDevKitGitignore(targetDir);
+    }
     emit(ctx, "dev_kit", formatDevKitInstallMessage("AI dev kit prepared", result), result);
     emitDevKitSkillInstallerFailure(
       ctx,

package/dist/proxy.js

@@ -29137,7 +29137,7 @@ var LogWriter = class {
 };
 
 // src/mcp-proxy/proxy.ts
-var VERSION = true ? "1.24.0" : "dev";
+var VERSION = true ? "1.24.2" : "dev";
 var LOCAL_PROXY_TAG = "local";
 var TapTapMCPProxy = class {
   constructor(config2) {

package/dist/server.js

@@ -6090,7 +6090,7 @@ class MultiplayerManager {
 // 导出
 // export default MultiplayerManager;
 // module.exports = MultiplayerManager;
-// window.MultiplayerManager = MultiplayerManager;`}]}}};var ws;ws="1.24.0";async function FRe(){return Go(Rm,"api_event_relations")}async function BRe(){return Go(Rm,"protocol_template")}async function SD(){return Go(Rm,"complete_example")}async function URe(){return`# TapTap 多人联机集成指南
+// window.MultiplayerManager = MultiplayerManager;`}]}}};var ws;ws="1.24.2";async function FRe(){return Go(Rm,"api_event_relations")}async function BRe(){return Go(Rm,"protocol_template")}async function SD(){return Go(Rm,"complete_example")}async function URe(){return`# TapTap 多人联机集成指南
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@taptap/instant-games-open-mcp",
-  "version": "1.24.0",
+  "version": "1.24.2",
   "type": "module",
   "description": "TapTap Open API MCP Server - Documentation and Management APIs for TapTap Minigame and H5 Games (Leaderboard, and more features coming)",
   "main": "dist/server.js",

package/skills/taptap-maker-local/SKILL.md

@@ -15,8 +15,8 @@ This skill covers:
 
 - initialize local Maker development
 - run the Maker CLI initialization flow
-- prepare local AI dev kit before project binding
 - clone a Maker project
+- prepare local AI dev kit after project checkout
 - choose a Maker app from the CLI app list
 - explain PAT, Git, project binding, and editor reloads
 - inspect local changes
@@ -33,7 +33,7 @@ post-build runtime log polling loop belongs to the local Maker CLI watcher.
 Keep this split clear:
 
 - Skill: user intent, step order, whether to ask the user, friendly explanations, failure recovery.
-- CLI: save PAT, fetch app list, prepare dev kit, clone, install MCP config, verify local setup,
+- CLI: save PAT, fetch app list, clone, prepare dev kit, install MCP config, verify local setup,
   and run the local runtime log watcher.
 - MCP tools/resources: inspect Maker status, run the combined commit/push/build path, and support
   one-shot runtime log pulls.
@@ -133,8 +133,10 @@ Keep the user-facing explanation short:
 
 ## AI Dev Kit Preparation
 
-`taptap-maker init` prepares local development environment files in the current working directory
-before it checks out the Maker project.
+`taptap-maker init` checks out the Maker project before preparing local development environment
+files in the current working directory. Init reinstalls the dev kit after checkout and allows
+dev-kit files to overwrite same-path local helper files; the managed `.gitignore` block keeps
+those files local-only so they are not submitted to Maker Git.
 
 `taptap-maker doctor` and `maker://status` check the dev-kit top-level entries for an already bound
 Maker project. If `CLAUDE.md`, `examples/`, `templates/`, or `urhox-libs/` are missing, run
@@ -161,18 +163,19 @@ resources to the local AI/Agent:
 
 The CLI is responsible for deterministic file operations:
 
-- extract the ZIP into the current directory
+- extract the ZIP into the current directory after checkout
 - skip the ZIP top-level `scripts` directory because it conflicts with Maker project code
 - delete the downloaded `ai-dev-kit.zip` after extraction
 - write a temporary `.gitignore.dev-kit-before-clone` block for installed dev-kit entries
-- after Maker clone succeeds, merge that block into the checked-out `.gitignore`
+- after dev-kit preparation succeeds, merge that block into the checked-out `.gitignore`
 - keep the dev-kit files local-only so they are not submitted to Maker Git
 
 Do not hand-write a custom download/unzip script while this CLI command is available.
 
-If clone fails because dev-kit network access is unavailable, explain that the Maker project can
-still be cloned, but local AI development docs/API/demo support may be incomplete. Ask whether
-the user wants to retry or continue without the dev kit.
+If dev-kit network access is unavailable after clone succeeds, explain that the Maker project is
+already checked out, but local AI development docs/API/demo support may be incomplete. Ask whether
+the user wants to retry `taptap-maker init` for a full post-checkout dev-kit reinstall or continue
+without the dev kit.
 
 If clone or fetch fails with Maker Git output, inspect the returned error fields instead of asking
 the user to delete local files immediately. Treat `retryable: yes`, `classification:
@@ -280,12 +283,13 @@ Do not delete, move, or overwrite user files during this check.
 
 ## Clone Directory Safety
 
-Before clone, the Maker CLI checks local files and reports conflicts. The AI dev kit may create
-local-only files before clone, so explain this in non-technical terms:
+Before clone, the Maker CLI checks local files and reports conflicts. The current init flow installs
+the AI dev kit after checkout, so a fresh directory should not get checkout conflicts from newly
+generated dev-kit files. Explain this in non-technical terms:
 
 - existing local config folders such as `.claude`, `.mcp`, `.skill`, `.config`, `.ini` are kept
 - normal local files are kept unless they conflict with files from the Maker project
-- if conflicts are reported, tell the user exactly which files block clone and ask whether to move,
+- if conflicts are reported, tell the user exactly which pre-existing files block clone and ask whether to move,
   rename, or choose another directory
 
 Do not delete or overwrite user files to make clone work unless the user explicitly asks.
@@ -306,8 +310,8 @@ directory over manual cleanup.
 ### `.gitignore` Merge During Clone
 
 The Maker CLI stages the dev-kit managed ignore block in
-`.gitignore.dev-kit-before-clone` instead of writing `.gitignore` before checkout. After Maker
-clone succeeds, the CLI merges that managed block into the checked-out `.gitignore` and
+`.gitignore.dev-kit-before-clone` while preparing the dev kit. After the Maker checkout and dev-kit
+preparation both succeed, the CLI merges that managed block into the checked-out `.gitignore` and
 removes the temporary file.
 
 If clone still reports conflicts for files other than `.gitignore.dev-kit-before-clone`, do not