autosnippet 3.2.8 → 3.2.10

package/lib/external/ai/AiProvider.js

@@ -20,6 +20,51 @@ export class AiProvider {
     this._circuitThreshold = config.circuitThreshold || 5; // 触发熔断的连续失败次数
     this._circuitOpenedAt = 0; // 熔断打开时间
     this._circuitCooldownMs = 30_000; // 初始冷却 30 秒
+
+    // ── Provider 级全局并发闸门 + 429 冷却窗 ──
+    this._maxConcurrency = Math.max(1, Number(config.maxConcurrency || process.env.ASD_AI_MAX_CONCURRENCY || 4));
+    this._activeRequests = 0;
+    this._requestQueue = [];
+    this._rateLimitedUntil = 0;
+  }
+
+  async _acquireRequestSlot() {
+    if (this._activeRequests < this._maxConcurrency) {
+      this._activeRequests += 1;
+      return;
+    }
+    await new Promise((resolve) => this._requestQueue.push(resolve));
+    this._activeRequests += 1;
+  }
+
+  _releaseRequestSlot() {
+    this._activeRequests = Math.max(0, this._activeRequests - 1);
+    const next = this._requestQueue.shift();
+    if (next) {
+      next();
+    }
+  }
+
+  async _waitForRateLimitWindow() {
+    const waitMs = (this._rateLimitedUntil || 0) - Date.now();
+    if (waitMs > 0) {
+      await new Promise((r) => setTimeout(r, waitMs));
+    }
+  }
+
+  _setRateLimitWindow(waitMs) {
+    const safeWait = Math.max(0, Number(waitMs) || 0);
+    if (safeWait <= 0) {
+      return;
+    }
+    const until = Date.now() + safeWait;
+    if (until > (this._rateLimitedUntil || 0)) {
+      this._rateLimitedUntil = until;
+      this._log?.(
+        'warn',
+        `[RateLimit] ${this.name} enters cooldown ${Math.round(safeWait / 1000)}s (global)`
+      );
+    }
   }
 
   /**
@@ -81,9 +126,9 @@ export class AiProvider {
    * 带工具声明的结构化对话 — 原生函数调用 API
    *
    * 支持原生函数调用的 Provider（Gemini / OpenAI / Claude）覆盖此方法,
-   * 返回结构化 functionCall 而非文本，ChatAgent 据此跳过正则解析。
+   * 返回结构化 functionCall 而非文本，AgentRuntime 据此跳过正则解析。
    *
-   * 默认实现降级为 chat()，由 ChatAgent 进行文本解析。
+   * 默认实现降级为 chat()，由 AgentRuntime 进行文本解析。
    *
    * 统一消息格式 (Provider-Agnostic):
    *   - { role: 'user', content: 'text' }
@@ -150,35 +195,6 @@ export class AiProvider {
     return this.extractJSON(response, openChar, closeChar);
   }
 
-  /**
-   * 从源码文件批量提取 Recipe 结构（AI 驱动）
-   * 默认实现使用 chat() + 标准提示词；子类可覆盖以使用专用 API
-   * @param {string} targetName - SPM Target 名称
-   * @param {Array<{name:string,content:string}>} filesContent
-   * @param {object} [options] - 可选参数
-   * @returns {Promise<Array<object>>}
-   */
-  async extractRecipes(targetName, filesContent, options = {}) {
-    const prompt = this._buildExtractPrompt(targetName, filesContent, options);
-    const parsed = await this.chatWithStructuredOutput(prompt, {
-      openChar: '[',
-      closeChar: ']',
-      temperature: 0.3,
-      maxTokens: 32768,
-    });
-    if (!Array.isArray(parsed)) {
-      this._log(
-        'warn',
-        `[extractRecipes] structured output parse failed for target: ${targetName}`
-      );
-      return [];
-    }
-    if (parsed.length === 0) {
-      this._log('info', `[extractRecipes] AI returned empty array for target: ${targetName}`);
-    }
-    return parsed;
-  }
-
   /**
    * 内部日志辅助（子类可通过 this.logger 覆盖）
    */
@@ -193,147 +209,6 @@ export class AiProvider {
     }
   }
 
-  /**
-   * 构建 extractRecipes 标准提示词（语言自适应 + Skill 增强）
-   */
-  _buildExtractPrompt(targetName, filesContent, options = {}) {
-    const files = filesContent.map((f) => `--- FILE: ${f.name} ---\n${f.content}`).join('\n\n');
-
-    // 检测文件主要语言
-    const langProfile = this._detectLanguageProfile(filesContent);
-
-    // AST 代码结构分析注入 — 帮助 AI 理解继承体系、设计模式、代码规模
-    const astSection = options.astContext
-      ? `\n# Code Structure Analysis (AST)\nThe following is a Tree-sitter AST analysis of the project. Use this structural context to better understand class hierarchies, design patterns, and code quality when extracting recipes:\n\n${options.astContext.substring(0, 3000)}\n`
-      : '';
-
-    // 用户语言偏好 — 控制 AI 输出人类可读字段的语言
-    const langInstruction = this._buildLangInstruction(options.lang);
-
-    // comprehensive 模式：全量分析整个文件，不跳过任何有意义的方法
-    if (options.comprehensive) {
-      return `# Role
-You are a ${langProfile.role} performing a **comprehensive full-file analysis**.
-
-# Goal
-Thoroughly analyze ALL code in "${targetName}" and create Recipe entries for **every significant method, function, or code block**.
-This is a full-file analysis — do NOT skip methods just because they seem "simple" or "standard".
-${astSection}
-
-# What to extract
-- **Every** complete method/function with 5+ lines of implementation
-- Initialization and configuration methods (init, viewDidLoad, setup, configure)
-- Event handlers and action methods
-- Data processing and business logic
-- Protocol/delegate implementations
-- ANY code block that a developer might reference, learn from, or reuse
-
-# Extraction Rules
-- Extract **BROADLY** — include all meaningful code units, not just "clever" or "novel" patterns
-- Each recipe must be a **complete, standalone** code unit with full signature and body
-- Put the complete code in \`content.pattern\`, and a meaningful project writeup in \`content.markdown\`
-- Preserve the file's actual code. Use \`<#placeholder#>\` ONLY for literal strings/values a developer would customize
-- Every recipe must be traceable to real code in the file. Do NOT invent code
-- Include relevant \`headers\` (import/require lines) that the code depends on
-- You **MUST** extract at least ONE recipe — every source file has something worth capturing
-- For each recipe, provide a concise \`doClause\` (imperative sentence) and a \`topicHint\` group label
-
-${langProfile.extractionExamples}
-
-# Output (JSON Array)
-Each item MUST use the following V3 KnowledgeEntry structure:
-- title (string): Descriptive English name
-- description (string): 2-3 sentences explaining what this code does, written as a project-specific guide
-- trigger (string): @shortcut (kebab-case, e.g. "@url-parser")
-- kind (string): "rule" | "pattern" | "fact" — rule = always-do/never-do, pattern = reusable recipe with code, fact = reference info
-- knowledgeType (string): "code-pattern" | "architecture" | "best-practice" | "code-standard" | "code-relation" | "data-flow" | "event-and-data-flow" | "module-dependency" | "boundary-constraint" | "code-style" | "solution" | "anti-pattern"
-- complexity (string): "basic" | "intermediate" | "advanced"
-- scope (string): "universal" | "project-specific" | "team-convention"
-- category: ${langProfile.categories}
-- language: "${langProfile.primaryLanguage}"
-- content (object): { "pattern": "<complete function/method/class from the file>", "markdown": "<project-specific writeup: what this pattern does, when to use it, key design decisions>", "rationale": "<why this pattern is designed this way — design trade-offs, alternatives considered>" }
-- reasoning (object): { "whyStandard": "<why this is a standard/best-practice worth following>", "sources": ["<source file names>"], "confidence": <0.0-1.0> }
-- headers (string[]): Required import/require lines
-- tags (string[]): Search keywords
-- doClause (string): One-sentence imperative: what to do (e.g. "Use dependency injection via constructor")
-- dontClause (string): What NOT to do (e.g. "Don't instantiate services with new directly")
-- whenClause (string): When this pattern applies (e.g. "When creating a new ViewController subclass")
-- topicHint (string): Group label for related patterns (e.g. "Networking", "UI-Layout", "Error-Handling")
-- coreCode (string): Minimal 3-10 line code skeleton that captures the essence. Must be syntactically complete — balanced brackets/parentheses, never start with } or ) and never end with { or (
-- usageGuide (string): ### 章节格式使用指南 — 描述何时使用此模式、步骤和注意事项
-- constraints (object, optional): { "preconditions": ["<conditions that must be true before using this pattern>"], "sideEffects": ["<observable side effects of using this code>"], "boundaries": ["<usage limitations or scope restrictions>"] }
-- aiInsight (string, optional): One-sentence concise insight — the single most important takeaway about this code pattern
-
-IMPORTANT: content.pattern must contain the COMPLETE source code. content.markdown must be a meaningful project-specific writeup, NOT just a copy of description. content.rationale must explain WHY this pattern is designed this way. reasoning.whyStandard must explain WHY this pattern matters.
-${langInstruction}
-Return ONLY a JSON array. Do NOT return an empty array.
-
-Files Content:
-${files}`;
-    }
-
-    return `# Role
-You are a ${langProfile.role} extracting production-quality reusable code patterns.
-
-# Goal
-Extract meaningful, complete code patterns from "${targetName}". Each recipe must provide real value to a developer.
-${astSection}
-
-# What makes a GOOD recipe
-- A **complete function/method** or **logical code block** (10-40 lines typically), NOT individual statements
-- Code that demonstrates a **real design pattern**: ${langProfile.patternExamples}
-- Code that a developer would actually **copy-paste and adapt** for a new feature
-
-# What makes a BAD recipe (AVOID these)
-- Trivial 2-3 line snippets like just a single assignment or import
-- Overly generic code that doesn't reflect the file's actual logic
-- Breaking a single function into multiple tiny recipes
-
-# Extraction Strategy
-For each function/method/class in the file, ask: "Would a developer benefit from having this as a reusable template?" If yes, extract the **complete unit** with its full body.
-
-${langProfile.extractionExamples}
-
-# Rules
-1. \`content.pattern\` must contain a **complete function/method or logical unit** — include the signature and full body
-2. \`content.markdown\` must be a meaningful project-specific writeup explaining what this code does and when to use it
-3. Preserve the file's actual code. Use \`<#placeholder#>\` ONLY for literal strings/values a developer would customize
-4. Every recipe must be traceable to real code in the file. Do NOT invent code
-5. Include relevant \`headers\` (import/require lines) that the code depends on
-6. Every recipe must have a concise \`doClause\` and a \`topicHint\` group label
-
-# Output (JSON Array)
-Each item MUST use the following V3 KnowledgeEntry structure:
-- title (string): Descriptive English name
-- description (string): 2-3 sentences explaining what this code does, written as a project-specific guide
-- trigger (string): @shortcut (kebab-case, e.g. "@url-parser")
-- kind (string): "rule" | "pattern" | "fact" — rule = always-do/never-do, pattern = reusable recipe with code, fact = reference info
-- knowledgeType (string): "code-pattern" | "architecture" | "best-practice" | "code-standard" | "code-relation" | "data-flow" | "event-and-data-flow" | "module-dependency" | "boundary-constraint" | "code-style" | "solution" | "anti-pattern"
-- complexity (string): "basic" | "intermediate" | "advanced"
-- scope (string): "universal" | "project-specific" | "team-convention"
-- category: ${langProfile.categories}
-- language: "${langProfile.primaryLanguage}"
-- content (object): { "pattern": "<complete function/method/class from the file>", "markdown": "<project-specific writeup: what this pattern does, when to use it, key design decisions>", "rationale": "<why this pattern is designed this way — design trade-offs, alternatives considered>" }
-- reasoning (object): { "whyStandard": "<why this is a standard/best-practice worth following>", "sources": ["<source file names>"], "confidence": <0.0-1.0> }
-- headers (string[]): Required import/require lines
-- tags (string[]): Search keywords
-- doClause (string): One-sentence imperative: what to do (e.g. "Use dependency injection via constructor")
-- dontClause (string): What NOT to do (e.g. "Don't instantiate services with new directly")
-- whenClause (string): When this pattern applies (e.g. "When creating a new ViewController subclass")
-- topicHint (string): Group label (e.g. "Networking", "UI-Layout")
-- coreCode (string): Minimal 3-10 line code skeleton that captures the essence. Must be syntactically complete — balanced brackets/parentheses, never start with } or ) and never end with { or (
-- usageGuide (string): ### 章节格式使用指南 — 描述何时使用此模式、步骤和注意事项
-- constraints (object, optional): { "preconditions": ["<conditions that must be true before using this pattern>"], "sideEffects": ["<observable side effects of using this code>"], "boundaries": ["<usage limitations or scope restrictions>"] }
-- aiInsight (string, optional): One-sentence concise insight — the single most important takeaway about this code pattern
-
-IMPORTANT: content.pattern must contain the COMPLETE source code. content.markdown must be a meaningful project-specific writeup, NOT just a copy of description. content.rationale must explain WHY this pattern is designed this way. reasoning.whyStandard must explain WHY this pattern matters.
-${langInstruction}
-Return ONLY a JSON array. If no meaningful patterns found, return [].
-
-Files Content:
-${files}`;
-  }
-
   /**
    * 根据用户语言偏好生成输出语言指令
    * @param {string} [lang] - 语言代码，如 'zh', 'en'
@@ -856,7 +731,12 @@ ${items}`;
     }
 
     for (let attempt = 0; attempt <= retries; attempt++) {
+      let slotAcquired = false;
       try {
+        await this._waitForRateLimitWindow();
+        await this._acquireRequestSlot();
+        slotAcquired = true;
+
         const result = await fn();
         // 成功 → 完全重置熔断器（包括冷却时间）
         this._circuitFailures = 0;
@@ -886,6 +766,16 @@ ${items}`;
             causeCode === 'UND_ERR_SOCKET');
         const isRetryable = err.status === 429 || err.status >= 500 || isNetworkError;
 
+        // 429：触发 provider 级冷却窗，抑制并发重试风暴
+        if (err.status === 429) {
+          const retryAfterMs = Number(err.retryAfterMs || 0);
+          const adaptiveCooldown = Math.max(
+            retryAfterMs,
+            Math.round(baseDelay * 2 ** attempt * 1.5 + Math.random() * 1000)
+          );
+          this._setRateLimitWindow(adaptiveCooldown);
+        }
+
         // 首次失败记录详细诊断（含 cause）
         if (attempt === 0 && (isNetworkError || err.cause)) {
           this._log?.(
@@ -921,6 +811,10 @@ ${items}`;
           `[_withRetry] attempt ${attempt + 1} failed (${err.message}), retrying in ${Math.round(delay / 1000)}s…`
         );
         await new Promise((r) => setTimeout(r, delay));
+      } finally {
+        if (slotAcquired) {
+          this._releaseRequestSlot();
+        }
       }
     }
   }

package/lib/external/ai/providers/GoogleGeminiProvider.js

@@ -15,7 +15,12 @@ const EMBED_MODEL = 'models/gemini-embedding-001';
 
 export class GoogleGeminiProvider extends AiProvider {
   constructor(config = {}) {
-    super(config);
+    super({
+      ...config,
+      maxConcurrency:
+        config.maxConcurrency ||
+        Number(process.env.ASD_GEMINI_MAX_CONCURRENCY || process.env.ASD_AI_MAX_CONCURRENCY || 2),
+    });
     this.name = 'google-gemini';
     this.model = config.model || 'gemini-3-flash-preview';
     this.apiKey = config.apiKey || process.env.ASD_GOOGLE_API_KEY || '';
@@ -110,10 +115,12 @@ export class GoogleGeminiProvider extends AiProvider {
         ];
       }
 
-      // toolChoice → Gemini mode
-      body.toolConfig = {
-        functionCallingConfig: { mode: this.#toGeminiMode(toolChoice) },
-      };
+      // toolChoice → Gemini mode (仅在有工具声明时设置，无工具时设 toolConfig 可能导致空响应)
+      if (body.tools) {
+        body.toolConfig = {
+          functionCallingConfig: { mode: this.#toGeminiMode(toolChoice) },
+        };
+      }
 
       // 系统指令
       if (systemPrompt) {
@@ -421,6 +428,20 @@ export class GoogleGeminiProvider extends AiProvider {
         signal: controller.signal,
       });
       if (!res.ok) {
+        const retryAfterHeader = res.headers.get('retry-after');
+        let retryAfterMs = 0;
+        if (retryAfterHeader) {
+          const sec = Number(retryAfterHeader);
+          if (Number.isFinite(sec) && sec > 0) {
+            retryAfterMs = sec * 1000;
+          } else {
+            const when = Date.parse(retryAfterHeader);
+            if (Number.isFinite(when)) {
+              retryAfterMs = Math.max(0, when - Date.now());
+            }
+          }
+        }
+
         let detail = '';
         try {
           const j = await res.json();
@@ -430,6 +451,9 @@ export class GoogleGeminiProvider extends AiProvider {
         }
         const err = new Error(`Gemini API error: ${res.status}${detail ? ` — ${detail}` : ''}`);
         err.status = res.status;
+        if (retryAfterMs > 0) {
+          err.retryAfterMs = retryAfterMs;
+        }
         throw err;
       }
       return await res.json();

package/lib/external/mcp/handlers/bootstrap/BootstrapSession.js

@@ -16,7 +16,7 @@
  */
 
 import crypto from 'node:crypto';
-import { SessionStore } from '../../../../service/chat/memory/SessionStore.js';
+import { SessionStore } from '../../../../service/agent/memory/SessionStore.js';
 import { ExternalSubmissionTracker } from './ExternalSubmissionTracker.js';
 
 // ── 常量 ────────────────────────────────────────────────────

package/lib/external/mcp/handlers/bootstrap/ExternalSubmissionTracker.js

@@ -1,15 +1,15 @@
 /**
  * ExternalSubmissionTracker — 外部 Agent 提交追踪与质量评估
  *
- * HandoffProtocol v2 的外部 Agent 对应模块。
- * 内部 Agent 使用 EvidenceCollector 从 toolCall 中收集证据，
+ * 质量门控的外部 Agent 对应模块。
+ * 内部 Agent 使用 EvidenceCollector 从 toolCall 中收集证据 (bootstrap-gate.js)，
  * 外部 Agent 使用 ExternalSubmissionTracker 从 submit_knowledge 调用中积累证据。
  *
  * 职责:
  *   - 追踪每个维度的 submit_knowledge 提交 (recipe 元数据 + 引用文件)
  *   - 从提交内容构建 evidenceMap (filePath → 引用摘要)
  *   - 从 dimension_complete 的 analysisText 提取负空间信号
- *   - 计算维度级质量评分 (类似 HandoffProtocol.buildQualityScores)
+ *   - 计算维度级质量评分 (对应 bootstrap-gate.js 的 buildQualityScores)
  *   - 为下游维度提供结构化跨维度证据
  *
  * 设计对应关系:

package/lib/external/mcp/handlers/bootstrap/MissionBriefingBuilder.js

@@ -37,7 +37,7 @@ const SIZE_THRESHOLDS = {
 /**
  * 将 base-dimensions 中的维度定义转换为 Mission Briefing 中的维度任务对象
  *
- * 取自 AnalystAgent.buildAnalystPrompt() + DIMENSION_CONFIGS_V3 + ProducerAgent.STYLE_GUIDE
+ * 取自 bootstrap-analyst.buildAnalystPrompt() + DIMENSION_CONFIGS_V3 + StyleGuide
  *
  * @param {object} dim — base-dimensions.js 中的维度定义
  * @param {object[]} skills — 已加载的 bootstrap skills

package/lib/external/mcp/handlers/bootstrap/pipeline/IncrementalBootstrap.js

@@ -16,7 +16,7 @@
  */
 
 import { BootstrapSnapshot } from './BootstrapSnapshot.js';
-import { SessionStore } from '../../../../../service/chat/memory/SessionStore.js';
+import { SessionStore } from '../../../../../service/agent/memory/SessionStore.js';
 
 // ──────────────────────────────────────────────────────────────
 // IncrementalBootstrap 类

package/lib/external/mcp/handlers/bootstrap/pipeline/dimension-context.js

@@ -1,15 +1,15 @@
 /**
  * pipeline/dimension-context.js — 跨维度上下文管理 (v6)
  *
- * ⚠️ 内部 Agent 专用 — 被 orchestrator.js 的 AnalystAgent 调用。
+ * ⚠️ 内部 Agent 专用 — 被 orchestrator.js 的 PipelineStrategy analyze 阶段调用。
  *    外部 Agent 不使用此模块（外部 Agent 的跨维度上下文由 BootstrapSession.js + EpisodicMemory 管理）。
  *
- * 在内部 Analyst/Producer 双 Agent 按维度分批生产候选时，维护跨维度的上下文:
+ * 在 PipelineStrategy 按维度分批执行时，维护跨维度的上下文:
  *   - 项目基础信息 (不变)
  *   - 已完成维度的 DimensionDigest (累积)
  *   - 已提交候选的摘要列表 (累积)
  *
- * 确保每个维度的 AnalystAgent 都能看到前序维度的分析结论，
+ * 确保每个维度的 Analyst 阶段都能看到前序维度的分析结论，
  * 实现跨维度透明互补。
  *
  * @module pipeline/dimension-context
@@ -73,7 +73,7 @@ export class DimensionContext {
   }
 
   /**
-   * 构建给 ChatAgent 的上下文快照
+   * 构建给 Agent 的上下文快照
    *
    * @param {string} currentDimId — 当前维度 ID
    * @returns {DimensionContextSnapshot}
@@ -115,7 +115,7 @@ export class DimensionContext {
 
   /**
    * 获取所有维度摘要的紧凑文本表示
-   * 用于 ChatAgent prompt 中注入
+   * 用于 Agent prompt 中注入
    *
    * @returns {string}
    */
@@ -176,12 +176,12 @@ export class DimensionContext {
 }
 
 /**
- * 从 ChatAgent 的最终回复中解析 DimensionDigest
+ * 从 Agent 的最终回复中解析 DimensionDigest
  *
- * ChatAgent 被要求在回复末尾包含 JSON 格式的 dimensionDigest。
+ * Agent 被要求在回复末尾包含 JSON 格式的 dimensionDigest。
  * 此函数从自由格式文本中提取该 JSON 块。
  *
- * @param {string} reply — ChatAgent 的完整回复文本
+ * @param {string} reply — Agent 的完整回复文本
  * @returns {DimensionDigest|null}
  */
 export function parseDimensionDigest(reply) {

package/lib/external/mcp/handlers/bootstrap/pipeline/noAiFallback.js

@@ -1,7 +1,7 @@
 /**
  * noAiFallback.js — AI 不可用时的规则化降级知识提取
  *
- * 当 ChatAgent / AI Provider 不可用时，从 Phase 1-4 的结构化数据中
+ * 当 AgentRuntime / AI Provider 不可用时，从 Phase 1-4 的结构化数据中
  * 提取基础知识候选和 Project Skill，覆盖以下维度：
  *
  *   ✅ project-profile     — 从 langStats + depGraph + targets 构建项目技术画像