@cloudbase/cloudbase-mcp 2.17.0-beta.2 → 2.17.1

package/dist/index.js

@@ -38,7 +38,6 @@ const auth_js_1 = __webpack_require__(7291);
 const cloudbase_manager_js_1 = __webpack_require__(3431);
 const logger_js_1 = __webpack_require__(3039);
 const tool_result_js_1 = __webpack_require__(9835);
-const rag_js_1 = __webpack_require__(4215);
 const env_setup_js_1 = __webpack_require__(6978);
 /**
  * Simplify environment list data by keeping only essential fields for AI assistant
@@ -495,19 +494,6 @@ async function enrichEnvInfoWithBilling(params) {
         return params.result;
     }
 }
-async function getGuidePrompt(server) {
-    if (getCurrentIde(server) === "CodeBuddy" ||
-        process.env.CLOUDBASE_GUIDE_PROMPT === "false") {
-        return "";
-    }
-    try {
-        return await (0, rag_js_1.getClaudePrompt)();
-    }
-    catch (promptError) {
-        (0, logger_js_1.debug)("Failed to get CLAUDE prompt", { error: promptError });
-        return "";
-    }
-}
 function normalizeOptionalToolString(value) {
     return typeof value === "string" && value.trim().length > 0
         ? value.trim()
@@ -1166,23 +1152,7 @@ function registerEnvTools(server) {
                 default:
                     throw new Error(`不支持的查询类型: ${action}`);
             }
-            let responseText = JSON.stringify(result, null, 2);
-            // For info action, append CLAUDE.md prompt content (skip for CodeBuddy IDE)
-            const currentIde = server.ide || process.env.INTEGRATION_IDE;
-            if (action === "info" && currentIde !== "CodeBuddy" && process.env.CLOUDBASE_GUIDE_PROMPT !== "false") {
-                try {
-                    const promptContent = await (0, rag_js_1.getClaudePrompt)();
-                    if (promptContent) {
-                        responseText += `\n\n⚠️ 重要提示：后续所有云开发相关的开发工作必须严格遵循以下开发规范和最佳实践：\n\n${promptContent}`;
-                    }
-                }
-                catch (promptError) {
-                    (0, logger_js_1.debug)("Failed to get CLAUDE prompt in envQuery", {
-                        error: promptError,
-                    });
-                    // Continue without prompt if fetch fails
-                }
-            }
+            const responseText = JSON.stringify(result, null, 2);
             return {
                 content: [
                     {
@@ -1572,7 +1542,7 @@ ${envIdSection}
 ## 环境信息
 - 操作系统: ${os_1.default.type()} ${os_1.default.release()}
 - Node.js版本: ${process.version}
-- MCP 版本：${process.env.npm_package_version || "2.17.0-beta.2" || 0}
+- MCP 版本：${process.env.npm_package_version || "2.17.1" || 0}
 - 系统架构: ${os_1.default.arch()}
 - 时间: ${new Date().toISOString()}
 - 请求ID: ${requestId}
@@ -4291,7 +4261,7 @@ deleteCollection: 删除集合`),
     // writeNoSqlDatabaseContent
     server.registerTool?.("writeNoSqlDatabaseContent", {
         title: "修改 NoSQL 数据库数据记录",
-        description: "修改 NoSQL 数据库数据记录。可按 MongoDB updateOne/updateMany 的心智模型理解：部分更新必须使用 $set/$inc/$push 等更新操作符；如果直接传 { field: value } 这类普通对象，底层会把它当作替换内容，存在覆盖整条文档的风险。更新嵌套对象中的某个字段时必须使用点号路径（如 { \"$set\": { \"address.city\": \"shenzhen\" } }），若写成 { \"$set\": { \"address\": { \"city\": \"shenzhen\" } } } 则整个 address 对象会被替换，同级其他字段将丢失。若集合中的角色/档案文档会在前端通过 `db.collection(...).doc(uid)` 读取，请确保文档 `_id` 就是该 `uid`；不要用 `query={\"uid\":\"...\"}` + `upsert=true` 去更新 `users` / `profiles`，否则经常会生成一个不同的 `_id`，导致后续 `doc(uid)` 读取命中不到。",
+        description: "修改 NoSQL 数据库数据记录。可按 MongoDB updateOne/updateMany 的心智模型理解：部分更新必须使用 `$set`、`$inc`、`$push` 等更新操作符；如果直接传“字段到值的普通对象”这类内容，底层会把它当作替换内容，存在覆盖整条文档的风险。更新嵌套对象中的某个字段时必须使用点号路径，例如把 `address.city` 设为 `shenzhen`；如果把整个 `address` 对象作为 `$set` 的值传入，则整个 `address` 对象会被替换，同级其他字段将丢失。若集合中的角色/档案文档会在前端通过 `db.collection(...).doc(uid)` 读取，请确保文档 `_id` 就是该 `uid`；不要用按 `uid` 条件查询再配合 `upsert=true` 的方式去更新 `users` / `profiles`，否则经常会生成一个不同的 `_id`，导致后续 `doc(uid)` 读取命中不到。",
         inputSchema: {
             action: zod_1.z
                 .enum(["insert", "update", "delete"])
@@ -4312,7 +4282,7 @@ deleteCollection: 删除集合`),
             update: zod_1.z
                 .union([zod_1.z.object({}).passthrough(), zod_1.z.string()])
                 .optional()
-                .describe("更新内容(对象或字符串,推荐对象)(update 操作必填)。按 MongoDB 更新语义传入 MgoUpdate：部分更新请使用 $set/$inc/$unset/$push 等操作符，例如 { \"$set\": { \"status\": \"pending\" } }；不要直接传 { \"status\": \"pending\" }，否则可能替换整条文档。更新嵌套字段时必须用点号路径，如 { \"$set\": { \"address.city\": \"shenzhen\" } }，不要写成 { \"$set\": { \"address\": { \"city\": \"shenzhen\" } } }（会替换整个 address 对象）。"),
+                .describe("更新内容(对象或字符串,推荐对象)(update 操作必填)。按 MongoDB 更新语义传入 MgoUpdate：部分更新请使用 `$set`、`$inc`、`$unset`、`$push` 等操作符，例如使用 `$set` 更新 `status`；不要直接传“字段到值的普通对象”，否则可能替换整条文档。更新嵌套字段时必须使用点号路径，例如通过 `$set` 更新 `address.city`；不要把整个 `address` 对象作为 `$set` 的值传入，否则会替换整个 `address` 对象。"),
             isMulti: zod_1.z
                 .boolean()
                 .optional()
@@ -5583,7 +5553,6 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
 };
 Object.defineProperty(exports, "__esModule", ({ value: true }));
 exports.resolveSkillSearchRoots = resolveSkillSearchRoots;
-exports.getClaudePrompt = getClaudePrompt;
 exports.registerRagTools = registerRagTools;
 const adm_zip_1 = __importDefault(__webpack_require__(2872));
 const fs = __importStar(__webpack_require__(7932));
@@ -5592,7 +5561,6 @@ const os = __importStar(__webpack_require__(8116));
 const path = __importStar(__webpack_require__(2521));
 const zod_1 = __webpack_require__(2971);
 const cloudbase_manager_js_1 = __webpack_require__(3431);
-const claude_prompt_js_1 = __webpack_require__(8359);
 const json_content_js_1 = __webpack_require__(4365);
 const logger_js_1 = __webpack_require__(3039);
 // 1. 枚举定义
@@ -5958,34 +5926,6 @@ async function downloadResources() {
     });
     return resourceDownloadPromise;
 }
-// Get CLAUDE.md prompt content
-// Priority: 1. From downloaded template, 2. Fallback to embedded constant
-async function getClaudePrompt() {
-    try {
-        // Try to get from downloaded template
-        const extractDir = await downloadWebTemplate();
-        const claudePath = path.join(extractDir, "CLAUDE.md");
-        try {
-            const content = await fs.readFile(claudePath, "utf8");
-            return content;
-        }
-        catch (error) {
-            // CLAUDE.md not found in template, use fallback
-            (0, logger_js_1.warn)("[getClaudePrompt] CLAUDE.md not found in template, using fallback", {
-                error,
-                path: claudePath,
-            });
-            return claude_prompt_js_1.FALLBACK_CLAUDE_PROMPT;
-        }
-    }
-    catch (error) {
-        // Template download failed, use fallback
-        (0, logger_js_1.warn)("[getClaudePrompt] Template download failed, using fallback", {
-            error,
-        });
-        return claude_prompt_js_1.FALLBACK_CLAUDE_PROMPT;
-    }
-}
 async function registerRagTools(server) {
     // 联网搜索
     server.registerTool?.("searchWeb", {
@@ -8671,7 +8611,7 @@ class TelemetryReporter {
         const nodeVersion = process.version; // Node.js版本
         const arch = os_1.default.arch(); // 系统架构
         // 从构建时注入的版本号获取MCP版本信息
-        const mcpVersion = process.env.npm_package_version || "2.17.0-beta.2" || 0;
+        const mcpVersion = process.env.npm_package_version || "2.17.1" || 0;
         return {
             userAgent: `${osType} ${osRelease} ${arch} ${nodeVersion} CloudBase-MCP/${mcpVersion}`,
             deviceId: this.deviceId,
@@ -8962,6 +8902,7 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
 Object.defineProperty(exports, "__esModule", ({ value: true }));
 exports.MANAGE_FUNCTION_ACTIONS = exports.QUERY_FUNCTION_ACTIONS = exports.TRIGGER_CONFIG_EXAMPLES = exports.SUPPORTED_TRIGGER_TYPES = exports.DEFAULT_NODEJS_RUNTIME = exports.SUPPORTED_NODEJS_RUNTIMES = exports.RECOMMENDED_RUNTIMES = exports.DEFAULT_RUNTIME = exports.ALL_SUPPORTED_RUNTIMES = exports.SUPPORTED_RUNTIMES = void 0;
 exports.formatRuntimeList = formatRuntimeList;
+exports.validateTimerCron = validateTimerCron;
 exports.shouldInstallDependencyForFunction = shouldInstallDependencyForFunction;
 exports.resolveEventFunctionRuntime = resolveEventFunctionRuntime;
 exports.buildFunctionOperationErrorMessage = buildFunctionOperationErrorMessage;
@@ -9065,12 +9006,32 @@ const VPC_SCHEMA = zod_1.z.object({
     vpcId: zod_1.z.string(),
     subnetId: zod_1.z.string(),
 });
+const SEVEN_FIELD_CRON_REGEX = /^\s*\S+\s+\S+\s+\S+\s+\S+\s+\S+\s+\S+\s+\S+\s*$/;
+function validateTimerCron(config) {
+    const trimmed = config.trim();
+    const fields = trimmed.split(/\s+/);
+    if (fields.length === 5) {
+        throw new Error(`timer 触发器的 cron 表达式必须使用 7 段格式（秒 分 时 日 月 星期 年），不支持标准 5 段格式。` +
+            `\n收到 5 段: "${trimmed}"` +
+            `\n正确示例: "0 */5 * * * * *"（每 5 分钟执行），"0 0 2 1 * * *"（每月 1 号 2 点）`);
+    }
+    if (fields.length < 7) {
+        throw new Error(`timer 触发器的 cron 表达式必须使用 7 段格式（秒 分 时 日 月 星期 年），当前只有 ${fields.length} 段。` +
+            `\n正确示例: "0 */5 * * * * *"（每 5 分钟执行），"0 0 2 1 * * *"（每月 1 号 2 点）`);
+    }
+    return trimmed;
+}
 const TRIGGER_SCHEMA = zod_1.z.object({
     name: zod_1.z.string().describe("触发器名称"),
     type: zod_1.z.enum(exports.SUPPORTED_TRIGGER_TYPES).describe("触发器类型"),
     config: zod_1.z
         .string()
-        .describe("触发器配置，timer 使用 7 段 cron：second minute hour day month week year"),
+        .describe("触发器配置。timer 必须使用 CloudBase 7 段 cron 格式：秒 分 时 日 月 星期 年。" +
+        "⚠️ 不支持标准 5 段 cron（如 */5 * * * * 是错误的）。" +
+        "正确示例：0 */5 * * * * *（每5分钟）、0 0 2 1 * * *（每月1号2点）、0 30 9 * * * *（每天9:30）")
+        .refine((val) => SEVEN_FIELD_CRON_REGEX.test(val), {
+        message: "timer 触发器的 cron 表达式必须使用 7 段格式（秒 分 时 日 月 星期 年），不支持 5 段格式。正确示例：0 */5 * * * * *",
+    }),
 });
 const CREATE_FUNCTION_SCHEMA = zod_1.z.object({
     name: zod_1.z.string().describe("函数名称"),
@@ -9733,6 +9694,12 @@ function registerFunctionTools(server) {
                 if (!input.triggers?.length) {
                     throw new Error("createFunctionTrigger 操作时，triggers 参数是必需的");
                 }
+                // Validate timer cron format before sending to CloudBase
+                for (const trigger of input.triggers) {
+                    if (trigger.type === "timer") {
+                        validateTimerCron(trigger.config);
+                    }
+                }
                 const cloudbase = await getManager();
                 const result = await cloudbase.functions.createFunctionTriggers(input.functionName, input.triggers);
                 (0, cloudbase_manager_js_1.logCloudBaseResult)(server.logger, result);
@@ -9964,7 +9931,10 @@ function registerFunctionTools(server) {
                 .enum(exports.MANAGE_FUNCTION_ACTIONS)
                 .describe("写操作类型，例如 createFunction、invokeFunction、attachLayer"),
             func: CREATE_FUNCTION_SCHEMA.optional().describe("createFunction 操作的函数配置"),
-            functionRootPath: zod_1.z.string().optional().describe("函数根目录（父目录绝对路径）"),
+            functionRootPath: zod_1.z.string().optional().describe("函数根目录（父目录绝对路径）。" +
+                "本地应按 cloudfunctions/<functionName>/index.js 布局，" +
+                "此参数传 cloudfunctions 目录的绝对路径（如 /abs/path/cloudfunctions），不要传到函数名子目录。" +
+                "SDK 会自动拼接函数名子目录。"),
             force: zod_1.z.boolean().optional().describe("createFunction 时是否覆盖"),
             functionName: zod_1.z.string().optional().describe("函数名称。大多数 action 使用该字段作为统一目标"),
             zipFile: zod_1.z.string().optional().describe("代码包的 base64 编码"),
@@ -11040,7 +11010,7 @@ function registerSetupTools(server) {
         title: "下载项目模板",
         description: `自动下载并部署CloudBase项目模板。⚠️ **MANDATORY FOR NEW PROJECTS** ⚠️
 
-**CRITICAL**: This tool MUST be called FIRST when starting a new project.\n\n支持的模板:\n- react: React + CloudBase 全栈应用模板\n- vue: Vue + CloudBase 全栈应用模板\n- miniprogram: 微信小程序 + 云开发模板  \n- uniapp: UniApp + CloudBase 跨端应用模板\n- rules: 只包含AI编辑器配置文件（包含Cursor、WindSurf、CodeBuddy等所有主流编辑器配置），适合在已有项目中补充AI编辑器配置\n\n支持的IDE类型:\n- all: 下载所有IDE配置\n- cursor: Cursor AI编辑器\n- 其他IDE类型见下方列表\n\n注意：如果未传入 ide 参数且无法从环境变量检测到 IDE，将提示错误并要求传入 ide 参数\n- windsurf: WindSurf AI编辑器\n- codebuddy: CodeBuddy AI编辑器\n- claude-code: Claude Code AI编辑器\n- cline: Cline AI编辑器\n- gemini-cli: Gemini CLI\n- opencode: OpenCode AI编辑器\n- qwen-code: 通义灵码\n- baidu-comate: 百度Comate\n- openai-codex-cli: OpenAI Codex CLI\n- augment-code: Augment Code\n- github-copilot: GitHub Copilot\n- roocode: RooCode AI编辑器\n- tongyi-lingma: 通义灵码\n- trae: Trae AI编辑器\n- qoder: Qoder AI编辑器\n- antigravity: Google Antigravity AI编辑器\n- vscode: Visual Studio Code\n- kiro: Kiro AI编辑器\n- aider: Aider AI编辑器\n\n特别说明：\n- rules 模板会自动包含当前 mcp 版本号信息（版本号：${ true ? "2.17.0-beta.2" : 0}），便于后续维护和版本追踪\n- 下载 rules 模板时，如果项目中已存在 README.md 文件，系统会自动保护该文件不被覆盖（除非设置 overwrite=true）`,
+**CRITICAL**: This tool MUST be called FIRST when starting a new project.\n\n支持的模板:\n- react: React + CloudBase 全栈应用模板\n- vue: Vue + CloudBase 全栈应用模板\n- miniprogram: 微信小程序 + 云开发模板  \n- uniapp: UniApp + CloudBase 跨端应用模板\n- rules: 只包含AI编辑器配置文件（包含Cursor、WindSurf、CodeBuddy等所有主流编辑器配置），适合在已有项目中补充AI编辑器配置\n\n支持的IDE类型:\n- all: 下载所有IDE配置\n- cursor: Cursor AI编辑器\n- 其他IDE类型见下方列表\n\n注意：如果未传入 ide 参数且无法从环境变量检测到 IDE，将提示错误并要求传入 ide 参数\n- windsurf: WindSurf AI编辑器\n- codebuddy: CodeBuddy AI编辑器\n- claude-code: Claude Code AI编辑器\n- cline: Cline AI编辑器\n- gemini-cli: Gemini CLI\n- opencode: OpenCode AI编辑器\n- qwen-code: 通义灵码\n- baidu-comate: 百度Comate\n- openai-codex-cli: OpenAI Codex CLI\n- augment-code: Augment Code\n- github-copilot: GitHub Copilot\n- roocode: RooCode AI编辑器\n- tongyi-lingma: 通义灵码\n- trae: Trae AI编辑器\n- qoder: Qoder AI编辑器\n- antigravity: Google Antigravity AI编辑器\n- vscode: Visual Studio Code\n- kiro: Kiro AI编辑器\n- aider: Aider AI编辑器\n\n特别说明：\n- rules 模板会自动包含当前 mcp 版本号信息（版本号：${ true ? "2.17.1" : 0}），便于后续维护和版本追踪\n- 下载 rules 模板时，如果项目中已存在 README.md 文件，系统会自动保护该文件不被覆盖（除非设置 overwrite=true）`,
         inputSchema: {
             template: zod_1.z
                 .enum(["react", "vue", "miniprogram", "uniapp", "rules"])
@@ -12567,322 +12537,6 @@ module.exports = __WEBPACK_EXTERNAL_MODULE_fs_promises_f8dae9d1__;
 
 module.exports = __WEBPACK_EXTERNAL_MODULE_os__;
 
-/***/ }),
-
-/***/ 8359:
-/***/ ((__unused_webpack_module, exports) => {
-
-
-Object.defineProperty(exports, "__esModule", ({ value: true }));
-exports.FALLBACK_CLAUDE_PROMPT = void 0;
-// Fallback CLAUDE.md prompt content
-// This is used when template download fails or CLAUDE.md is not found in the template
-exports.FALLBACK_CLAUDE_PROMPT = `---
-description: CloudBase AI Development Rules Guide - Provides scenario-based best practices to ensure development quality
-globs: *
-alwaysApply: true
----
-
-# CloudBase AI Development Rules Guide
-
-## Quick Reference for AI
-
-**⚠️ CRITICAL: Read this section first based on your project type**
-
-### When Developing a Web Project:
-1. **Environment Check**: Query environment info only when the task actually needs environment metadata, deployment, or an env ID. For existing applications with active TODOs or unfinished handlers, do not spend turns on hosting or domain queries unless the user explicitly asks for deployment.
-1. **Execution Mode for Existing-Code Tasks**: If the task is to complete an existing application, wire TODO logic, or repair a broken flow, do **not** enter design-only, brainstorming-only, or spec-only flows first. Gather only the minimum context needed, then implement directly. Do not stop after “project exploration complete”.
-1. **Existing File Focus (MANDATORY)**: For an existing Web app with active pages or TODO-bearing files, do not broad-scan the whole repo before coding. First inspect only the task-critical files: \`src/lib/backend.*\`, \`src/lib/auth.*\`, \`src/lib/cms-service.*\`, \`src/lib/storage-service.*\`, and the page/components that already consume those APIs. Then implement those TODOs before doing any wide repo exploration.
-1. **Task Tool Discipline**: For targeted repair tasks, do not spend many turns in \`TaskCreate\`, \`TaskUpdate\`, or project-management loops. At most keep one short checklist. After that, write code. Do not let task-management consume the turn budget.
-1. **No README / UI-Design Detour For Existing Apps**: If the repo already contains the target pages and only backend TODOs are missing, skip README-driven discovery and skip UI-design workflows unless the task explicitly asks for a visual redesign. Backend wiring is the priority.
-1. **No Broad Grep / Glob Sweep**: In targeted repair tasks, do not recursively Grep / Glob the whole repo for long periods. Open the known TODO-bearing files directly and start editing.
-3. **⚠️ UI Design (CRITICAL)**: **MUST read \`rules/ui-design/rule.md\` FIRST before generating any page, interface, component, or style** - This is NOT optional. You MUST explicitly read this file and output the design specification before writing any UI code.
-4. **Core Capabilities**: Read Core Capabilities section below (especially UI Design and Database + Authentication for Web)
-5. **Platform Rules**: Read \`rules/web-development/rule.md\` for platform-specific rules (SDK integration, static hosting, build configuration)
-6. **Authentication**: Read \`rules/auth-web/rule.md\` - **MUST use Web SDK built-in authentication**
-   - \`accessKey\` can only be a real Publishable Key obtained from CloudBase auth/app config. Never use \`envId\`, a username, or any placeholder string as \`accessKey\`.
-   - If you do not have a real Publishable Key yet, do not fabricate one. First query or configure auth readiness, or initialize without \`accessKey\` if the login flow itself is what will establish end-user identity.
-7. **Cloud Storage (when files are uploaded from browser code)**: Read \`rules/cloud-storage-web/rule.md\` before implementing upload / preview / temp URL flows. For local dev origins (for example Vite on \`127.0.0.1\` / \`localhost\`), query current security domains first and compare against the returned whitelist entry format (usually \`host:port\`, such as \`127.0.0.1:4173\` or \`localhost:5173\`). If \`envQuery(action="domains")\` reports missing local entries or returns a \`next_step\`, execute that \`envDomainManagement\` step before relying on \`app.uploadFile()\`. After upload, do not handcraft a storage URL from \`envId\`, bucket domain, or \`cloudPath\`; resolve an actual browser-usable URL through \`app.getTempFileURL()\` using the returned \`fileID\`.
-7. **Database**: 
-   - NoSQL: \`rules/no-sql-web-sdk/rule.md\`
-   - MySQL: \`rules/relational-database-web/rule.md\` + \`rules/relational-database-mcp/rule.md\`
-
-### When Developing a Mini Program Project:
-1. **Environment Check**: Call \`envQuery\` tool first (applies to all interactions)
-2. **⚠️ UI Design (CRITICAL)**: **MUST read \`rules/ui-design/rule.md\` FIRST before generating any page, interface, component, or style** - This is NOT optional. You MUST explicitly read this file and output the design specification before writing any UI code.
-3. **Core Capabilities**: Read Core Capabilities section below (especially UI Design and Database + Authentication for Mini Program)
-4. **Platform Rules**: Read \`rules/miniprogram-development/rule.md\` for platform-specific rules (project structure, WeChat Developer Tools, wx.cloud usage)
-5. **Authentication**: Read \`rules/auth-wechat/rule.md\` - **Naturally login-free, get OPENID in cloud functions**
-6. **Database**: 
-   - NoSQL: \`rules/no-sql-wx-mp-sdk/rule.md\`
-   - MySQL: \`rules/relational-database-mcp/rule.md\` (via MCP tools)
-
----
-
-## Core Capabilities (Must Be Done Well)
-
-As the most important part of application development, the following four core capabilities must be done well, without needing to read different rules for different platforms:
-
-### 1. ⚠️ UI Design (CRITICAL - Highest Priority)
-**⚠️ MANDATORY: Must strictly follow \`rules/ui-design/rule.md\` rules for ALL design work**
-
-**🚨 CRITICAL ENFORCEMENT: You MUST explicitly read the file \`rules/ui-design/rule.md\` before generating ANY UI code. This is NOT a suggestion - it is a MANDATORY requirement.**
-
-**Before generating ANY page, interface, component, or style:**
-1. **MUST FIRST explicitly read \`rules/ui-design/rule.md\` file** - Use file reading tools to read this file, do NOT skip this step
-2. **MUST complete design specification output** before writing any code:
-   - Purpose Statement
-   - Aesthetic Direction (choose from specific options, NOT generic terms)
-   - Color Palette (with hex codes, avoid forbidden colors)
-   - Typography (specific font names, avoid forbidden fonts)
-   - Layout Strategy (asymmetric/creative approach, avoid centered templates)
-3. **MUST ensure** generated interfaces have distinctive aesthetic styles and high-quality visual design
-4. **MUST avoid** generic AI aesthetics (common fonts, clichéd color schemes, templated designs)
-
-**This applies to ALL tasks involving:**
-- Page generation
-- Interface creation
-- Component design
-- Style/visual effects
-- Any frontend visual elements
-
-**⚠️ VIOLATION DETECTION: If you find yourself writing UI code without first reading \`rules/ui-design/rule.md\`, STOP immediately and read the file first.**
-
-### 2. Database + Authentication
-**Strengthen database and authentication capabilities**
-
-**Authentication**:
-- **Web Projects**: 
-  - Must use CloudBase Web SDK built-in authentication, refer to \`rules/auth-web/rule.md\`
-  - For username-style accounts, use \`auth.signUp({ username, password })\` and \`auth.signInWithPassword({ username, password })\`
-  - Do not use email-only helpers or email-only input semantics when the account identifier is a plain username string
-  - When an existing schema or fixture already provides role/profile metadata in \`users\`, \`profiles\`, or \`user_roles\`, reuse that collection instead of inventing yet another one. In role-based content-management flows, a \`user_roles\` collection keyed by \`uid\` is an acceptable and validated pattern.
-  - For browser-side file upload / preview flows, read \`rules/cloud-storage-web/rule.md\`; on local dev origins, verify the required local host entries (for example \`127.0.0.1:4173\`, \`localhost:5173\`) are already in the environment security-domain whitelist before depending on \`app.uploadFile()\`. If \`envQuery(action="domains")\` returns missing local entries or a \`next_step\`, execute that \`envDomainManagement\` action first. After upload, use \`app.getTempFileURL()\` to resolve the preview/download URL instead of constructing a URL string manually.
-  - Platform development rules: Refer to \`rules/web-development/rule.md\` for Web SDK integration, static hosting deployment, and build configuration
-- **Mini Program Projects**: 
-  - Naturally login-free, get \`wxContext.OPENID\` in cloud functions, refer to \`rules/auth-wechat/rule.md\`
-  - Platform development rules: Refer to \`rules/miniprogram-development/rule.md\` for mini program project structure, WeChat Developer Tools integration, and CloudBase capabilities
-- **Node.js Backend**: Refer to \`rules/auth-nodejs/rule.md\`
-
-**Database Operations**:
-- **Web Projects**:
-  - NoSQL Database: Refer to \`rules/no-sql-web-sdk/rule.md\`
-  - For content collections that only need owner-only writes, simple permissions such as \`READONLY\` can be a good fit. But for CMS-style collections that require **app-level admin users** to edit/delete any record while editors can only edit/delete their own records, a \`CUSTOM\` rule is expected.
-  - A validated CMS article rule shape is: \`{"read":"auth.uid != null","create":"auth.uid != null","update":"auth.uid != null && (get('database.user_roles.' + auth.uid).role == 'admin' || doc.authorId == auth.uid)","delete":"auth.uid != null && (get('database.user_roles.' + auth.uid).role == 'admin' || doc.authorId == auth.uid)"}\`.
-  - For that CMS pattern, frontend writes can stay on \`.doc(id).update()\` / \`.doc(id).remove()\`. Do not force a \`where(...)\` rewrite unless the task explicitly requires a different rule design.
-  - MySQL Relational Database: Refer to \`rules/relational-database-web/rule.md\` (Web application development) and \`rules/relational-database-mcp/rule.md\` (Management via MCP tools)
-  - Platform development rules: Refer to \`rules/web-development/rule.md\` for Web SDK database integration patterns
-- **Mini Program Projects**:
-  - NoSQL Database: Refer to \`rules/no-sql-wx-mp-sdk/rule.md\`
-  - MySQL Relational Database: Refer to \`rules/relational-database-mcp/rule.md\` (via MCP tools)
-  - Platform development rules: Refer to \`rules/miniprogram-development/rule.md\` for mini program database integration and wx.cloud usage
-- **Data Model Creation** (Universal): Refer to \`rules/data-model-creation/rule.md\`
-
-### 3. Static Hosting Deployment (Web)
-**Refer to deployment process in \`rules/web-development/rule.md\`**
-- Use CloudBase static hosting after build completion
-- Deploy using \`uploadFiles\` tool
-- \`uploadFiles\` is only for static hosting deployment; do not use it for COS / cloud storage uploads. For storage objects, use \`manageStorage(action="upload")\`
-- If the task is local verification or an unfinished application repair with a dev server workflow, skip static hosting deployment unless the user explicitly asks for a deployed URL
-- Remind users that CDN has a few minutes of cache after deployment
-- Generate markdown format access links with random queryString
-
-### 4. Backend Deployment (Cloud Functions or CloudRun)
-**Refer to \`rules/cloudrun-development/rule.md\`**
-- **Cloud Function Deployment**: Prefer \`queryFunctions\` to inspect current state, then use \`manageFunctions\` with \`action="createFunction"\` or \`action="updateFunctionCode"\`.
-- In agent / non-interactive runs, treat \`manageFunctions\` as the default deployment path for both Event and HTTP functions; do not fall back to CLI login flows unless MCP tools are unavailable.
-- For HTTP functions, create or update them through \`manageFunctions\` with \`func.type="HTTP"\` instead of relying on \`tcb fn deploy\` as the primary path.
-- **CloudRun Deployment**: Use \`manageCloudRun\` tool for containerized deployment
-- Ensure backend code supports CORS, prepare Dockerfile (for container type)
-
-## Development Process Standards
-
-**Important: To ensure development quality, AI must complete the following steps before starting work:**
-
-### 0. Environment Check (First Step)
-After user inputs any content, first check CloudBase environment status:
-- Ensure current CloudBase environment ID is known
-- If not present in conversation history and the task needs env metadata or deployment, call \`envQuery\` tool with parameter \`action=info\` to query current environment information and environment ID
-- **Important**: When environment ID configuration is involved in code later, automatically use the queried environment ID, no need for manual user input
-
-### 1. Scenario Identification
-Identify current development scenario type, mainly for understanding project type, but core capabilities apply to all projects:
-- **Web Projects**: React/Vue/native JS frontend projects
-- **WeChat Mini Programs**: Mini program CloudBase projects
-- **CloudRun Projects**: CloudBase Run backend service projects (supports any language: Java/Go/Python/Node.js/PHP/.NET, etc.)
-- **Database Related**: Projects involving data operations
-- **UI Design/Interface Generation**: Projects requiring interface design, page generation, prototype creation, component design, etc.
-
-### 2. Platform-Specific Quick Guide
-
-**Web Projects - Required Rule Files:**
-- \`rules/web-development/rule.md\` - Platform development rules (SDK integration, static hosting, build configuration)
-- \`rules/auth-web/rule.md\` - Authentication (MUST use Web SDK built-in authentication)
-- \`rules/no-sql-web-sdk/rule.md\` - NoSQL database operations
-- \`rules/relational-database-web/rule.md\` - MySQL database operations (Web)
-- \`rules/relational-database-mcp/rule.md\` - MySQL database management (MCP tools)
-- \`rules/cloudbase-platform/rule.md\` - Universal CloudBase platform knowledge
-
-**Mini Program Projects - Required Rule Files:**
-- \`rules/miniprogram-development/rule.md\` - Platform development rules (project structure, WeChat Developer Tools, wx.cloud)
-- \`rules/auth-wechat/rule.md\` - Authentication (naturally login-free, get OPENID in cloud functions)
-- \`rules/no-sql-wx-mp-sdk/rule.md\` - NoSQL database operations
-- \`rules/relational-database-mcp/rule.md\` - MySQL database operations (via MCP tools)
-- \`rules/cloudbase-platform/rule.md\` - Universal CloudBase platform knowledge
-
-**Universal Rule Files (All Projects):**
-- **⚠️ \`rules/ui-design/rule.md\`** - **MANDATORY - HIGHEST PRIORITY** - Must read FIRST before any UI/page/component/style generation
-- \`rules/data-model-creation/rule.md\` - Data model creation and MySQL modeling
-- \`rules/spec-workflow/rule.md\` - Standard software engineering process (if needed)
-
-### 3. Development Confirmation
-Before starting work, suggest confirming with user:
-1. "I identify this as a [scenario type] project"
-2. "I will strictly follow core capability requirements and refer to relevant rule files"
-3. "Please confirm if my understanding is correct"
-
-## Core Behavior Rules
-0. **Existing-Code Completion Bias**: For existing applications with TODOs or broken flows, implementation is the goal. Do not hand off to a design-only phase, do not stop at exploration, and do not treat a summary of findings as task completion. After minimal context gathering, write code and wire the real backend flow.
-0. **No Broad Exploration For TODO Apps**: When the repo already exposes TODO markers in backend integration files, do not keep globbing, summarizing, or reading unrelated files. Open the TODO-bearing files and implement them.
-0. **No Task-Loop Derailment**: In targeted repair tasks, avoid repeated \`TaskCreate\` / \`TaskUpdate\` cycles. One minimal checklist is enough; the rest of the budget should go to file edits, tool calls, and verification.
-0. **Do Not Delegate Or Defer**: In targeted repair tasks, do not invoke design copilots, brainstorming helpers, or delegated agent flows before the core TODO files are implemented. Finish the direct file edits first.
-1. **Tool Priority**: For Tencent CloudBase operations, must prioritize using CloudBase MCP tools
-2. **Project Understanding**: First read current project's README.md, follow project instructions for development. Exception: for existing applications where the missing work is clearly in known backend integration files, skip README-first and go straight to those files.
-4. **Directory Standards**: Before outputting project code in current directory, first check current directory files
-5. **Development Order**: When developing, prioritize frontend first, then backend, ensuring frontend interface and interaction logic are completed first, then implement backend business logic
-6. **⚠️ UI Design Rules Mandatory Application**: When tasks involve generating pages, interfaces, components, styles, or any frontend visual elements, **MUST FIRST explicitly read the file \`rules/ui-design/rule.md\` using file reading tools**, then strictly follow the rule file, ensuring generated interfaces have distinctive aesthetic styles and high-quality visual design, avoiding generic AI aesthetics. **You MUST output the design specification before writing any UI code.** Exception: for existing applications where page structure is already fixed and only backend integration is missing, do not trigger the UI-design workflow.
-7. **Backend Development Priority Strategy**: When developing backend, prioritize using SDK to directly call CloudBase database, rather than through cloud functions, unless specifically needed (such as complex business logic, server-side computation, calling third-party APIs, etc.)
-8. **Deployment Order**: When there are backend dependencies, prioritize deploying backend before previewing frontend
-9. **Interactive Confirmation**: Clarify requirements when needed, and confirm before executing high-risk operations
-10. **Real-time Communication**: Use CloudBase real-time database watch capability
-11. **⚠️ Authentication Rules**: When users develop projects, if user login authentication is needed, must use built-in authentication functions, must strictly distinguish authentication methods by platform
-   - **Web Projects**: **MUST use CloudBase Web SDK built-in authentication** (e.g., \`auth.toDefaultLoginPage()\`), refer to \`rules/auth-web/rule.md\`
-   - **Username-style Web accounts**: Use \`auth.signUp({ username, password })\` for registration and \`auth.signInWithPassword({ username, password })\` for login. Do not use \`signInWithEmailAndPassword\` / \`signUpWithEmailAndPassword\` when the identifier is not an email address.
-   - **Web initialization**: Only set \`accessKey\` when you have a real Publishable Key. Never set \`accessKey: envId\` or any made-up string.
-   - **Mini Program Projects**: **Naturally login-free**, get \`wxContext.OPENID\` in cloud functions, refer to \`rules/auth-wechat/rule.md\`
-
-## Development Workflow
-
-### Development
-
-1. **Project Bootstrap Discipline**: 
-   - Prefer the existing project structure and scripts when they already exist
-   - For new projects, keep the initial structure consistent and avoid mixing unrelated frameworks in one workspace
-   - If you bootstrap or copy an existing starter manually, hidden files and project config must be carried over as well
-
-2. **⚠️ UI Design Document Reading (MANDATORY)**: 
-   - **Before generating ANY page, interface, component, or style, MUST FIRST explicitly read the file \`rules/ui-design/rule.md\` using file reading tools**
-   - **MUST output the design specification** (Purpose Statement, Aesthetic Direction, Color Palette, Typography, Layout Strategy) before writing any UI code
-   - This is NOT optional - you MUST read the file and follow the design thinking framework and frontend aesthetics guidelines
-   - Avoid generating generic AI aesthetic style interfaces
-
-3. **Mini Program TabBar Material Download - Download Remote Material Links**: Mini program Tabbar and other material images must use **png** format, must use downloadRemoteFile tool to download files locally. Can select from Unsplash, wikimedia (generally choose 500 size), Pexels, Apple official UI and other resources
-
-If remote links are needed in the application, can continue to call uploadFile to upload and obtain temporary access links and cloud storage cloudId
-
-3. **Query Professional Knowledge from Knowledge Base**: If uncertain about any CloudBase knowledge, can use searchKnowledgeBase tool to intelligently search CloudBase knowledge base (supports CloudBase and cloud functions, mini program frontend knowledge, etc.), quickly obtain professional documents and answers through vector search
-
-4. **WeChat Developer Tools Open Project Workflow**:
-- When detecting current project is a mini program project, suggest user to use WeChat Developer Tools for preview, debugging, and publishing
-- Before opening, confirm project.config.json has appid field configured. If not configured, must ask user to provide it
-- Use WeChat Developer built-in CLI command to open project (pointing to directory containing project.config.json):
-  - Windows: \`"C:\\Program Files (x86)\\Tencent\\微信web开发者工具\\cli.bat" open --project "项目根目录路径"\`
-  - macOS: \`/Applications/wechatwebdevtools.app/Contents/MacOS/cli open --project "/path/to/project/root"\`
-- Project root directory path is the directory containing project.config.json file
-
-### Deployment Process
-
-1. **Cloud Function Deployment Process**: Prefer \`queryFunctions\` to query current functions, then call \`manageFunctions\` with \`action="createFunction"\` or \`action="updateFunctionCode"\` to deploy cloud function code. In agent / non-interactive runs, keep deployment on MCP tools instead of CLI login flows. For HTTP functions, set \`func.type="HTTP"\` when creating them. Only need to point \`functionRootPath\` to the parent directory of the cloud function directory (for example, the absolute path of the \`cloudfunctions\` directory). No need for code compression or other preprocessing.
-
-2. **CloudRun Deployment Process**: For non-cloud function backend services (Java, Go, PHP, Python, Node.js, etc.), use manageCloudRun tool for deployment. Ensure backend code supports CORS, prepare Dockerfile, then call manageCloudRun for containerized deployment. For details, refer to \`rules/cloudrun-development/rule.md\`
-
-3. **Static Hosting Deployment Process**: Deploy using uploadFiles tool for static hosting only. If the task needs a COS object that must be queried or polled with the storage SDK, use \`manageStorage\` / \`queryStorage\` instead. For local verification or unfinished application repairs, do not deploy hosting unless the user explicitly asks for deployment. After deployment, remind users that CDN has a few minutes of cache. Can generate markdown format access links with random queryString. For details, refer to \`rules/web-development/rule.md\`
-
-### Documentation Generation Rules
-
-1. You will generate a README.md file after generating the project, containing basic project information, such as project name, project description. Most importantly, clearly explain the project architecture and involved CloudBase resources, so maintainers can refer to it for modification and maintenance
-2. After deployment, if it's a web project, can write the official deployment access address in the documentation
-
-### Configuration File Rules
-
-1. To help others who don't use AI understand what resources are available, can generate a cloudbaserc.json file after generation
-
-### MCP Interface Call Rules
-When calling MCP services, you need to fully understand the data types of all interfaces to be called, as well as return value types. If you're not sure which interface to call, first check the documentation and tool descriptions, then determine which interface and parameters to call based on the documentation and tool descriptions. Do not have incorrect method parameters or parameter type errors.
-
-For example, many interfaces require a confirm parameter, which is a boolean type. If you don't provide this parameter, or provide incorrect data type, the interface will return an error.
-
-### Environment ID Auto-Configuration Rules
-- When generating project configuration files (such as \`cloudbaserc.json\`, \`project.config.json\`, etc.), automatically use the environment ID queried by \`envQuery\`
-- In code examples involving environment ID, automatically fill in current environment ID, no need for manual user replacement
-- In deployment and preview related operations, prioritize using already queried environment information
-
-## Professional Rule File Reference
-
-**Note**: For detailed information, refer to the specific skill files. This section provides quick reference only.
-
-### Platform Development Skills
-- **Web**: \`rules/web-development/rule.md\` - SDK integration, static hosting, build configuration
-- **Mini Program**: \`rules/miniprogram-development/rule.md\` - Project structure, WeChat Developer Tools, wx.cloud
-- **CloudRun**: \`rules/cloudrun-development/rule.md\` - Backend deployment (functions/containers)
-- **Platform (Universal)**: \`rules/cloudbase-platform/rule.md\` - Environment, authentication, services
-
-### Authentication Skills
-- **Web**: \`rules/auth-web/rule.md\` - **MUST use Web SDK built-in authentication**
-- **Mini Program**: \`rules/auth-wechat/rule.md\` - **Naturally login-free, get OPENID in cloud functions**
-- **Node.js**: \`rules/auth-nodejs/rule.md\`
-- **HTTP API**: \`rules/auth-http-api/rule.md\`
-
-### Database Skills
-- **NoSQL (Web)**: \`rules/no-sql-web-sdk/rule.md\`
-- **NoSQL (Mini Program)**: \`rules/no-sql-wx-mp-sdk/rule.md\`
-- **MySQL (Web)**: \`rules/relational-database-web/rule.md\`
-- **MySQL (MCP)**: \`rules/relational-database-mcp/rule.md\`
-- **Data Model Creation**: \`rules/data-model-creation/rule.md\`
-
-### 🎨 ⚠️ UI Design Skill (CRITICAL - Read FIRST)
-- **\`rules/ui-design/rule.md\`** - **MANDATORY - HIGHEST PRIORITY**
-  - **MUST read FIRST before generating ANY interface/page/component/style**
-  - Design thinking framework, complete design process, frontend aesthetics guidelines
-  - **NO EXCEPTIONS**: All UI work requires reading this file first
-
-### Workflow Skills
-- **Spec Workflow**: \`rules/spec-workflow/rule.md\` - Standard software engineering process (requirements, design, tasks)
-
-## Development Quality Checklist
-
-To ensure development quality, recommend completing the following checks before starting tasks:
-
-### Recommended Steps
-0. **[ ] Environment Check**: Call \`envQuery\` tool to check CloudBase environment status (applies to all interactions)
-1. **[ ] Scenario Identification**: Clearly identify what type of project this is (Web/Mini Program/Database/UI)
-3. **[ ] Core Capability Confirmation**: Confirm all four core capabilities have been considered
-   - UI Design: Have you explicitly read the file \`rules/ui-design/rule.md\` using file reading tools?
-   - Database + Authentication: Have you referred to corresponding authentication and database skills?
-   - Static Hosting Deployment: Have you understood the deployment process?
-   - Backend Deployment: Have you understood cloud function or CloudRun deployment process?
-4. **[ ] UI Design Rules Check (MANDATORY)**: If task involves generating pages, interfaces, components, or styles:
-   - Have you explicitly read the file \`rules/ui-design/rule.md\` using file reading tools? (Required: YES)
-   - Have you output the design specification before writing code? (Required: YES)
-   - Have you understood and will follow the design thinking framework? (Required: YES)
-5. **[ ] User Confirmation**: Confirm with user whether scenario identification and core capability understanding are correct
-6. **[ ] Rule Execution**: Strictly follow core capability requirements and relevant rule files for development
-
-### ⚠️ Common Issues to Avoid
-- **❌ DO NOT skip reading UI design document** - Must explicitly read \`rules/ui-design/rule.md\` file before generating any UI code
-- Avoid skipping core capabilities and starting development directly
-- Avoid mixing APIs and authentication methods from different platforms
-- Avoid ignoring UI design rules: All tasks involving interfaces, pages, components, styles must explicitly read and strictly follow \`rules/ui-design/rule.md\`
-- Avoid ignoring database and authentication standards: Must use correct authentication methods and database operation methods
-- Important technical solutions should be confirmed with users
-
-### Quality Assurance
-If development is found to not comply with standards, can:
-- Point out specific issues
-- Require re-execution of rule check process
-- Clearly specify rule files that need to be followed`;
-
-
 /***/ }),
 
 /***/ 9097:
@@ -14785,7 +14439,7 @@ var __webpack_exports__ = {};
 var exports = __webpack_exports__;
 
 Object.defineProperty(exports, "BJ", ({ value: true }));
-exports.j8 = exports.fO = exports.gk = exports.Yh = exports.JA = exports.xz = exports.RX = exports.pk = exports.ZS = exports.vY = exports.q8 = exports.bM = exports.fW = exports._k = exports.T$ = exports.$n = exports.S = exports.bT = exports.ri = exports.BS = exports.R8 = exports.z3 = exports.pq = exports.R4 = exports.ps = exports.v7 = exports.S7 = exports.dD = exports.Gh = void 0;
+exports.Os = exports.j8 = exports.fO = exports.gk = exports.Yh = exports.JA = exports.xz = exports.RX = exports.pk = exports.ZS = exports.vY = exports.q8 = exports.bM = exports.fW = exports._k = exports.T$ = exports.$n = exports.S = exports.bT = exports.ri = exports.BS = exports.R8 = exports.z3 = exports.pq = exports.R4 = exports.ps = exports.v7 = exports.S7 = exports.dD = exports.Gh = void 0;
 exports.SJ = getInteractiveServerAsync;
 // CloudBase MCP Server Library
 var server_js_1 = __webpack_require__(1422);
@@ -14825,6 +14479,7 @@ Object.defineProperty(exports, "Yh", ({ enumerable: true, get: function () { ret
 Object.defineProperty(exports, "gk", ({ enumerable: true, get: function () { return functions_js_1.formatRuntimeList; } }));
 Object.defineProperty(exports, "fO", ({ enumerable: true, get: function () { return functions_js_1.SUPPORTED_NODEJS_RUNTIMES; } }));
 Object.defineProperty(exports, "j8", ({ enumerable: true, get: function () { return functions_js_1.DEFAULT_NODEJS_RUNTIME; } }));
+Object.defineProperty(exports, "Os", ({ enumerable: true, get: function () { return functions_js_1.validateTimerCron; } }));
 /**
  * Get interactive server instance (CommonJS compatible)
  */
@@ -14867,5 +14522,6 @@ const __webpack_exports__resetCloudBaseManagerCache = __webpack_exports__.bM;
 const __webpack_exports__shouldRegisterTool = __webpack_exports__.T$;
 const __webpack_exports__simplifyEnvList = __webpack_exports__.ZS;
 const __webpack_exports__telemetryReporter = __webpack_exports__.v7;
+const __webpack_exports__validateTimerCron = __webpack_exports__.Os;
 const __webpack_exports__warn = __webpack_exports__.R8;
-export { __webpack_exports__ALL_SUPPORTED_RUNTIMES as ALL_SUPPORTED_RUNTIMES, __webpack_exports__DEFAULT_NODEJS_RUNTIME as DEFAULT_NODEJS_RUNTIME, __webpack_exports__DEFAULT_RUNTIME as DEFAULT_RUNTIME, __webpack_exports__RAW_IDE_FILE_MAPPINGS as RAW_IDE_FILE_MAPPINGS, __webpack_exports__RECOMMENDED_RUNTIMES as RECOMMENDED_RUNTIMES, __webpack_exports__SUPPORTED_NODEJS_RUNTIMES as SUPPORTED_NODEJS_RUNTIMES, __webpack_exports__SUPPORTED_RUNTIMES as SUPPORTED_RUNTIMES, __webpack_exports__StdioServerTransport as StdioServerTransport, __webpack_exports___esModule as __esModule, __webpack_exports__createCloudBaseManagerWithOptions as createCloudBaseManagerWithOptions, __webpack_exports__createCloudBaseMcpServer as createCloudBaseMcpServer, __webpack_exports__enableCloudMode as enableCloudMode, __webpack_exports__envManager as envManager, __webpack_exports__error as error, __webpack_exports__formatRuntimeList as formatRuntimeList, __webpack_exports__getCloudBaseManager as getCloudBaseManager, __webpack_exports__getCloudModeStatus as getCloudModeStatus, __webpack_exports__getDefaultServer as getDefaultServer, __webpack_exports__getEnvId as getEnvId, __webpack_exports__getInteractiveServerAsync as getInteractiveServerAsync, __webpack_exports__getLoginState as getLoginState, __webpack_exports__info as info, __webpack_exports__isCloudMode as isCloudMode, __webpack_exports__logout as logout, __webpack_exports__reportToolCall as reportToolCall, __webpack_exports__reportToolkitLifecycle as reportToolkitLifecycle, __webpack_exports__resetCloudBaseManagerCache as resetCloudBaseManagerCache, __webpack_exports__shouldRegisterTool as shouldRegisterTool, __webpack_exports__simplifyEnvList as simplifyEnvList, __webpack_exports__telemetryReporter as telemetryReporter, __webpack_exports__warn as warn };
+export { __webpack_exports__ALL_SUPPORTED_RUNTIMES as ALL_SUPPORTED_RUNTIMES, __webpack_exports__DEFAULT_NODEJS_RUNTIME as DEFAULT_NODEJS_RUNTIME, __webpack_exports__DEFAULT_RUNTIME as DEFAULT_RUNTIME, __webpack_exports__RAW_IDE_FILE_MAPPINGS as RAW_IDE_FILE_MAPPINGS, __webpack_exports__RECOMMENDED_RUNTIMES as RECOMMENDED_RUNTIMES, __webpack_exports__SUPPORTED_NODEJS_RUNTIMES as SUPPORTED_NODEJS_RUNTIMES, __webpack_exports__SUPPORTED_RUNTIMES as SUPPORTED_RUNTIMES, __webpack_exports__StdioServerTransport as StdioServerTransport, __webpack_exports___esModule as __esModule, __webpack_exports__createCloudBaseManagerWithOptions as createCloudBaseManagerWithOptions, __webpack_exports__createCloudBaseMcpServer as createCloudBaseMcpServer, __webpack_exports__enableCloudMode as enableCloudMode, __webpack_exports__envManager as envManager, __webpack_exports__error as error, __webpack_exports__formatRuntimeList as formatRuntimeList, __webpack_exports__getCloudBaseManager as getCloudBaseManager, __webpack_exports__getCloudModeStatus as getCloudModeStatus, __webpack_exports__getDefaultServer as getDefaultServer, __webpack_exports__getEnvId as getEnvId, __webpack_exports__getInteractiveServerAsync as getInteractiveServerAsync, __webpack_exports__getLoginState as getLoginState, __webpack_exports__info as info, __webpack_exports__isCloudMode as isCloudMode, __webpack_exports__logout as logout, __webpack_exports__reportToolCall as reportToolCall, __webpack_exports__reportToolkitLifecycle as reportToolkitLifecycle, __webpack_exports__resetCloudBaseManagerCache as resetCloudBaseManagerCache, __webpack_exports__shouldRegisterTool as shouldRegisterTool, __webpack_exports__simplifyEnvList as simplifyEnvList, __webpack_exports__telemetryReporter as telemetryReporter, __webpack_exports__validateTimerCron as validateTimerCron, __webpack_exports__warn as warn };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cloudbase/cloudbase-mcp",
-  "version": "2.17.0-beta.2",
+  "version": "2.17.1",
   "description": "腾讯云开发 MCP Server，通过AI提示词和MCP协议+云开发，让开发更智能、更高效,当你在Cursor/ VSCode GitHub Copilot/WinSurf/CodeBuddy/Augment Code/Claude Code等AI编程工具里写代码时，它能自动帮你生成可直接部署的前后端应用+小程序，并一键发布到腾讯云开发 CloudBase。",
   "main": "./dist/index.cjs",
   "module": "./dist/index.js",