@ghyper9023/pi-dev-workflow 0.5.0 → 0.6.0

package/extensions/workflow-engine.ts

@@ -447,13 +447,19 @@ function captureBaseline(cwd: string): void {
  *
  * Uses git-format status codes (M, A, D) for display consistency.
  * Deduplicates against existing _workflowFileChanges.
+ *
+ * The dedup key includes stepIndex (filePath:stepIndex) so the same file
+ * can appear across different workflow steps (e.g., created by worker in
+ * loop-group, then reviewed by reviewer) without being collapsed into one.
+ * Without :stepIndex, the Set dedup would wrongly skip a file modified in
+ * a later step just because it was already tracked in an earlier step.
  */
 function updateToolsFromGit(cwd: string, stepIndex: number, agentName: string): void {
 	const currentChanges = getGitDiffChanges(cwd);
-	const seen = new Set(_workflowFileChanges.map(c => c.filePath));
-
+	const seen = new Set(_workflowFileChanges.map(c => `${c.filePath}:${c.stepIndex}`));
+	
 	for (const change of currentChanges) {
-		if (seen.has(change.path)) continue;
+		if (seen.has(`${change.path}:${stepIndex}`)) continue;
 
 		// ── Baseline filtering ──────────────────────────────
 		// Skip files that were already dirty at workflow start and haven't been touched.
@@ -470,7 +476,13 @@ function updateToolsFromGit(cwd: string, stepIndex: number, agentName: string):
 			}
 		}
 
-		seen.add(change.path);
+		// Skip files in .pi-dev-output/ — these are workflow-generated artifacts (plans, reviews)
+		// and should NOT be reported as user repo changes. Real git clients (VSCode, Zed) also
+		// ignore this directory (it's in .gitignore). This filter is defense-in-depth.
+		// Note: git always uses forward slashes in paths, even on Windows.
+		if (change.path.startsWith(".pi-dev-output/")) continue;
+
+		seen.add(`${change.path}:${stepIndex}`);
 		const type: FileChangeEntry["type"] =
 			change.status === "A" ? "new" :
 			change.status === "D" ? "delete" :
@@ -883,47 +895,6 @@ function addWidgetSubStepTool(stepIndex: number, agentName: string, tool: string
 		if (!sub.tools) sub.tools = [];
 		sub.tools.push(tool);
 		if (sub.tools.length > 20) sub.tools = sub.tools.slice(-20); // keep last 20
-
-		// Also track as file change for checkpoint
-		// Support both old format ("edit: path") and new git-format ("M   path", "A   path", "D   path")
-		const oldMatch = tool.match(/^(edit|new|delete|read):\s*(.+)/i);
-		const gitMatch = !oldMatch ? tool.match(/^([MAD])\s{2,}(.+)$/) : null;
-		if (oldMatch) {
-			const changeType = oldMatch[1]!.toLowerCase() as FileChangeEntry["type"];
-			const filePath = oldMatch[2]!.trim();
-			const exists = _workflowFileChanges.some(
-				c => c.filePath === filePath && c.type === changeType && c.stepIndex === stepIndex && c.agent === agentName,
-			);
-			if (!exists && filePath.length > 3) {
-				_workflowFileChanges.push({
-					agent: agentName,
-					stepIndex,
-					type: changeType,
-					filePath,
-					timestamp: new Date().toISOString(),
-				});
-			}
-		} else if (gitMatch) {
-			const gitStatus = gitMatch[1]!;
-			const changeType: FileChangeEntry["type"] =
-				gitStatus === "A" ? "new" :
-				gitStatus === "D" ? "delete" :
-				"edit";
-			const filePath = gitMatch[2]!.trim();
-			const exists = _workflowFileChanges.some(
-				c => c.filePath === filePath && c.type === changeType && c.stepIndex === stepIndex && c.agent === agentName,
-			);
-			if (!exists && filePath.length > 3) {
-				_workflowFileChanges.push({
-					agent: agentName,
-					stepIndex,
-					type: changeType,
-					filePath,
-					timestamp: new Date().toISOString(),
-				});
-			}
-		}
-
 		refreshWidget();
 	}
 }
@@ -1130,7 +1101,7 @@ async function runAgentWithProgress(
 	const result = await spawnSubagent(agent, task, _workflowCwd, signal, timeoutMs, (progress) => {
 		// Try to parse tool calls from progress messages
 		// Only match if it looks like a file path (contains a dot or path separator)
-		const toolMatch = progress.match(/(edit|read|write|new|bash|grep|find|ls|delete|remove)\s*[:：]\s*(\S+)/i);
+		const toolMatch = progress.match(/(edit|read|write|new|bash|grep|find|ls|delete|remove)\s*[:：]\s*([\w./\\-]+)/i);
 		if (toolMatch) {
 			const toolType = toolMatch[1]!.toLowerCase();
 			const target = toolMatch[2]!;
@@ -1141,12 +1112,14 @@ async function runAgentWithProgress(
 				_widgetExtraToolCount++;
 			}
 		}
-		// Detect output file paths — ONLY match explicit .pi-dev-output paths, never free-form text
-		const outputMatch = progress.match(/\.pi-dev-output\/[^\s,;)\]}]{5,}\.\w+/i);
-		if (outputMatch) {
-			const pathCandidate = outputMatch[0]!.trim();
-			if (pathCandidate.length > 15 && pathCandidate.length < 300) {
-				addWidgetSubStepOutput(stepIndex, agentName, pathCandidate);
+		// Detect output file paths — only match .pi-dev-output paths belonging to current workflow
+		if (_workflowId) {
+			const outputMatch = progress.match(/\.pi-dev-output\/[^\s,;)\]}'"`]{5,}\.\w+/i);
+			if (outputMatch) {
+				const pathCandidate = outputMatch[0]!.trim().replace(/["'`\\]+$/g, '');
+				if (pathCandidate.length > 15 && pathCandidate.length < 300 && pathCandidate.includes(_workflowId)) {
+					addWidgetSubStepOutput(stepIndex, agentName, pathCandidate);
+				}
 			}
 		}
 	}, _workflowId ? { workflowId: _workflowId } : undefined);
@@ -1163,127 +1136,47 @@ async function runAgentWithProgress(
 		toolCount: _widgetExtraToolCount,
 	});
 
-	// ── Post-completion: parse subagent output for tool calls and file paths ──
-	// Progress messages from spawnSubagent rarely contain tool info,
-	// so we scan the full output after completion.
+	// ── Post-completion: file change detection via git diff ONLY ──
+	// We do NOT parse agent output text for file paths — that approach is fragile and
+	// produces false positives (e.g., matching JS property names like `.push`, `.length`
+	// from code snippets). Instead, we rely entirely on git diff --name-status, which is
+	// the same approach used by VSCode, Zed, and every other professional git client.
+	// It's deterministic, noise-free, and always produces correct relative paths.
 	const allOutput = (result.output || "") + "\n" + (result.stderr || "");
 	const finalOutput = extractFinalOutput(result.output) || result.output;
 	const searchText = allOutput + "\n" + finalOutput;
 
-	// Detect file creation/modification patterns from agent's final output text
-	// The agent's response typically lists files using markdown backticks or bullet points
-	const filePatterns = [
-		// Markdown code blocks with file paths: `src/main.rs`, `path/to/file.ts`
-		/`([^`]+\.[a-zA-Z0-9_]+)`/g,
-		// Bullet points with file operation verbs: - Modify `src/main.rs`, * Created `file.ts`
-		/(?:^|\n)\s*[-*]\s*(?:modified|created|updated|edited|added|deleted|removed|changed|wrote|writes?)\s*[`"']?([^`"'\n,]+\.[a-zA-Z0-9_]+)[`"']?/gim,
-		// Descriptive: "I've modified src/main.rs", "reading config.json"
-		/(?:modified|created|updated|edited|added|deleted|removed|changed|wrote|write|writes|read|reads?)\s+(?:the\s+)?[`"']?([^`"'\n,]+\.[a-zA-Z0-9_]+)[`"']?/gi,
-		// Chinese patterns
-		/(?:编写|创建|修改|删除|读取|写入|更新)\s*(?:了|文件)?\s*[:：]?\s*[`"']?([^`"'\s,，]+\.[a-zA-Z0-9_]+)[`"']?/gi,
-		// File path with action prefix: "edit: src/file.ts", "new: src/file.ts"
-		/(?:^|\n)\s*(?:edit|new|delete|read|modify|create|update|add|remove)\s*[:：]\s*([^\n]+\.[a-zA-Z0-9_]+)/gim,
-	];
-	const seenTools = new Set<string>();
-	for (const pattern of filePatterns) {
+	// Find output file paths (plans, reviews) for display in the "output:" section
+	// These are workflow artifacts (.pi-dev-output/) — only show files belonging to
+	// the CURRENT workflow to avoid cross-contamination from previous runs.
+	// Note: file change detection itself relies exclusively on git diff below, not text parsing.
+	const seenOutputs = new Set<string>();
+	if (_workflowId) {
+		// Only match .pi-dev-output paths containing the current workflow UUID
+		const escapedId = _workflowId.replace(/[.*+?^${}()|[\]\\]/g, '\\$&');
+		const outputPattern = new RegExp(`\\.pi-dev-output\\/[^\\s,;)\\]}'"\\`]*${escapedId}[^\\s,;)\\]}'"\\`]*`, 'g');
 		let m;
-		while ((m = pattern.exec(searchText)) !== null) {
-			const filePath = m[1]!.trim()
-				.replace(/[`'"\)\(\]]+$/, "")
-				.replace(/^[`'"\)\(\[]+/, "")
-				.split(/[\s,;]/)[0]!;
-			// Validate it's a real file path
-			if (filePath.length > 3 && filePath.length < 300 && !seenTools.has(filePath)) {
-				// Skip common non-file matches
-				if (filePath.match(/^(the|a|an|this|that|it|its|my|your|our|their|some|any|all|each|every|both|few|many|several|most|other|another|such|what|which|whose|whom|when|where|why|how|who|being|having|doing|making|taking|giving|getting|setting|using|running|going|coming|looking|finding|keeping|putting)/i)) continue;
-				if (filePath.startsWith("http")) continue;
-				if (filePath.length < 6 && !filePath.includes("/")) continue;
-
-				// 额外过滤器：排除明显不是文件路径的脏数据
-				if (filePath.includes("${") || filePath.includes("\\n") || filePath.includes("\\t")) continue;  // 排除模板字符串和转义字符
-				if (filePath.includes("[]") || filePath.includes("{}")) continue;  // 排除数组/对象字面量
-				if (filePath.match(/^[\s,;)\]}]+$/)) continue;  // 排除纯符号
-				seenTools.add(filePath);
-				const fullMatch = m[0]!.toLowerCase();
-				// Determine operation type and convert to git status
-				let toolType = "edit";
-				if (fullMatch.includes("write") || fullMatch.includes("创建") || fullMatch.includes("new") || fullMatch.includes("add") || fullMatch.includes("created") || fullMatch.includes("added")) {
-					toolType = "new";
-				} else if (fullMatch.includes("delete") || fullMatch.includes("删除") || fullMatch.includes("remove") || fullMatch.includes("deleted") || fullMatch.includes("removed")) {
-					toolType = "delete";
-				} else if (fullMatch.includes("read") || fullMatch.includes("读取")) {
-					toolType = "read";
-				}
-				if (toolType !== "read") {
-					const gitStatus = toGitStatus(toolType);
-					addWidgetSubStepTool(stepIndex, agentName, `${gitStatus}   ${filePath}`);
-					_widgetExtraToolCount++;
-				}
+		while ((m = outputPattern.exec(searchText)) !== null) {
+			const path_ = m[0]!.trim();
+			if (path_.length > 15 && path_.length < 300 && !seenOutputs.has(path_)) {
+				seenOutputs.add(path_);
+				addWidgetSubStepOutput(stepIndex, agentName, path_);
 			}
 		}
-	}
-
-	// If we found no file tools from text patterns, try alternative approaches
-	// Look for explicit tool call patterns in the raw JSON output
-	if (seenTools.size === 0) {
-		const jsonLines = (result.output || "").split("\n");
-		for (const line of jsonLines) {
-			try {
-				const event = JSON.parse(line);
-				// Look for tool_use events in the JSON stream
-				if (event.type === "message_update" && event.assistantMessageEvent?.type === "tool_use") {
-					const toolName = event.assistantMessageEvent.name;
-					const args = event.assistantMessageEvent.args || {};
-					// write tool: args contains file_path
-					if (toolName === "write" && args.file_path) {
-						const fp = args.file_path.trim();
-						if (!seenTools.has(fp)) {
-							seenTools.add(fp);
-							addWidgetSubStepTool(stepIndex, agentName, `A   ${fp}`);
-							_widgetExtraToolCount++;
-						}
-					}
-					// edit tool: args contains file_path
-					if (toolName === "edit" && args.file_path) {
-						const fp = args.file_path.trim();
-						if (!seenTools.has(fp)) {
-							seenTools.add(fp);
-							addWidgetSubStepTool(stepIndex, agentName, `M   ${fp}`);
-							_widgetExtraToolCount++;
-						}
-					}
-				}
-			} catch { /* not JSON, skip */ }
-		}
-	}
-
-	// Find output file paths (.pi-dev-output, review reports, plan files)
-	// NOTE: Only match explicit paths in .pi-dev-output/ or known review/plan file patterns.
-	// The old pattern matching loose "output:" text was the root cause of "output::0.00004508" noise.
-	// File change detection now relies on git diff --name-status (updateToolsFromGit below),
-	// which is deterministic and noise-free.
-	const outputPathPatterns = [
-		// Direct reference to .pi-dev-output paths: ".pi-dev-output/pi-plans/xxx.md"
-		/\.pi-dev-output\/[a-zA-Z0-9_\/-]+\.[a-zA-Z0-9]+/g,
-		// Review file patterns: "review-20260520-162800.md"
-		/review-\d{8}-\d{6}\.md/g,
-		// Plan file patterns: "20260520-1628-*.md"
-		/\d{8}-\d{4,6}-[a-zA-Z0-9_-]+\.md/g,
-	];
-	const seenOutputs = new Set<string>();
-	for (const pattern of outputPathPatterns) {
+	} else {
+		// No workflow ID (unlikely): match .pi-dev-output paths conservatively
+		const outputPattern = /\.pi-dev-output\/[a-zA-Z0-9_\/-]+\.[a-zA-Z0-9]+/g;
 		let m;
-		while ((m = pattern.exec(searchText)) !== null) {
+		while ((m = outputPattern.exec(searchText)) !== null) {
 			const path_ = m[0]!.trim();
-			if (path_.length > 10 && path_.length < 300 && !seenOutputs.has(path_)) {
+			if (path_.length > 15 && path_.length < 300 && !seenOutputs.has(path_)) {
 				seenOutputs.add(path_);
 				addWidgetSubStepOutput(stepIndex, agentName, path_);
 			}
 		}
 	}
 
-
-	// ── Update file changes from git diff (more accurate than text scraping) ──
+	// ── Update file changes from git diff (more accurate than text scraping) ──	
 	updateToolsFromGit(_workflowCwd, stepIndex, agentName);
 	// Update sub-step status based on result
 	const subStatus: WorkflowSubStepWidgetState["status"] =
@@ -1350,33 +1243,19 @@ async function executeSingleStep(
 		throw new Error(`Agent 错误 (exit ${result.exitCode}): ${result.stderr.slice(0, 500)}`);
 	}
 
-	// ── Capture chain context for single-step agents ──
-	const agentChanges = _workflowFileChanges
-		.filter(c => c.stepIndex === stepIndex && c.agent === agentName)
-		.map(c => `${c.type === "new" ? "A" : c.type === "delete" ? "D" : "M"}   ${c.filePath}`);
-
-	let chainKey: string;
-	if (agentName === "planner") chainKey = "计划制定摘要";
-	else if (agentName === "docWriter") chainKey = "文档更新摘要";
-	else chainKey = `${agentName} 执行摘要`;
-
-	if (agentChanges.length > 0) {
-		const editCount = agentChanges.filter(c => c.startsWith("M")).length;
-		const newCount = agentChanges.filter(c => c.startsWith("A")).length;
-		const delCount = agentChanges.filter(c => c.startsWith("D")).length;
-		const statsParts: string[] = [];
-		if (editCount > 0) statsParts.push(`修改 ${editCount} 个`);
-		if (newCount > 0) statsParts.push(`新增 ${newCount} 个`);
-		if (delCount > 0) statsParts.push(`删除 ${delCount} 个`);
-		const statsLine = statsParts.length > 0 ? `改动统计: ${statsParts.join("，")}\n\n` : "";
-
-		updateChainContext(chainKey,
-			`${agentName} 已完成。\n` +
-			statsLine +
-			`变更文件列表:\n${agentChanges.join("\n")}`
-		);
-	} else {
-		updateChainContext(chainKey, `${agentName} 已完成执行，未检测到文件变更。`);
+	// ── Capture AI work summary as supplementary chain context ──
+	// We intentionally do NOT create chain contexts from _workflowFileChanges here.
+	// File-change-based chain contexts ("计划制定摘要"/"文档更新摘要") were removed in v0.6.0
+	// because their M/A/D counts provided negligible value for downstream agents compared
+	// to the agent's own free-text work summary. The file-change approach also created
+	// tight coupling between executeSingleStep and the _workflowFileChanges data structure.
+	const workSummary = extractFinalOutput(result.output);
+	if (workSummary) {
+		updateChainContext(`${agentName} 工作总结`, `${agentName} 已完成工作，以下是其工作总结：\n\n${workSummary}`);
+	} else if (result.output) {
+		// 保底：使用输出前 200 字符作为简略摘要
+		const fallback = result.output.slice(0, 200).trim();
+		if (fallback) updateChainContext(`${agentName} 工作总结`, fallback);
 	}
 }
 
@@ -1440,34 +1319,11 @@ async function executeLoopGroup(
             }
         }
 
-		// ── After loop agent completes: capture changes + stats for chain context ──
-		const loopAgentChanges = _workflowFileChanges
-			.filter(c => c.stepIndex === stepIndex && c.agent === step.loopAgentName)
-			.map(c => `${c.type === "new" ? "A" : c.type === "delete" ? "D" : "M"}   ${c.filePath}`);
-
-		// Use agent-specific keys so worker and trimmer changes coexist without overwriting
-		const chainKey = step.loopAgentName === "worker" ? "代码实施摘要" : "代码精简摘要";
-
-		if (loopAgentChanges.length > 0) {
-			const editCount = loopAgentChanges.filter(c => c.startsWith("M")).length;
-			const newCount = loopAgentChanges.filter(c => c.startsWith("A")).length;
-			const delCount = loopAgentChanges.filter(c => c.startsWith("D")).length;
-			const statsParts: string[] = [];
-			if (editCount > 0) statsParts.push(`修改 ${editCount} 个`);
-			if (newCount > 0) statsParts.push(`新增 ${newCount} 个`);
-			if (delCount > 0) statsParts.push(`删除 ${delCount} 个`);
-			const statsLine = statsParts.length > 0 ? `改动统计: ${statsParts.join("，")}\n\n` : "";
-
-			updateChainContext(chainKey,
-				`${step.loopAgentName === "worker" ? "代码实施" : "代码精简"}已完成。\n` +
-				statsLine +
-				`变更文件列表:\n${loopAgentChanges.join("\n")}` +
-				(planFileRelPath ? `\n\n实施计划: ${planFileRelPath}\n(可在 .pi-dev-output/pi-plans/ 中 grep UUID ${_workflowId} 找到)` : "")
-			);
-		} else {
-			updateChainContext(chainKey,
-				`${step.loopAgentName} 已完成执行，未检测到文件变更。\n` +
-				(planFileRelPath ? `实施计划: ${planFileRelPath}\n(可在 .pi-dev-output/pi-plans/ 中 grep UUID ${_workflowId} 找到)` : "")
+		// ── Capture loop agent work summary as supplementary chain context ──
+		const loopFinalText = extractFinalOutput(agentResult.output);
+		if (loopFinalText) {
+			updateChainContext(`${step.loopAgentName} 工作总结`,
+				`${step.loopAgentName} 已完成工作，以下是其工作总结：\n\n${loopFinalText}`
 			);
 		}
 
@@ -1509,20 +1365,14 @@ async function executeLoopGroup(
 			}
 		}
 
-		// ── After reviewer: capture review context for next loop ──
-		// Use agent-specific key so worker-reviewer and trimmer-reviewer feedback don't interfere
-		const reviewChainKey = step.loopAgentName === "worker" ? "代码审查反馈" : "精简审查反馈";
-		if (reviewSummary) {
-			const reviewCountParts: string[] = [];
-			if (reviewSummary.critical > 0) reviewCountParts.push(`严重 ${reviewSummary.critical} 个`);
-			if (reviewSummary.medium > 0) reviewCountParts.push(`中等 ${reviewSummary.medium} 个`);
-			if (reviewSummary.low > 0) reviewCountParts.push(`低 ${reviewSummary.low} 个`);
-			const reviewStats = reviewCountParts.length > 0 ? `发现 ${reviewCountParts.join("，")} 问题。` : "未发现问题。";
-
-			updateChainContext(reviewChainKey,
-				`${reviewStats}\n` +
-				`完整审查报告在 .pi-dev-output/pi-review/md/ 目录中，\n` +
-				`请在工作流输出目录中 grep UUID "${_workflowId}" 查找最新报告。`
+		// ── Capture reviewer work summary as supplementary chain context ──
+		// The old review-chain-context entries ("代码审查反馈"/"精简审查反馈") based on
+		// _workflowFileChanges were removed in v0.6.0 because they duplicated information
+		// from the review report file and polluted chain context with file-path-heavy data.
+		// Reuse already-parsed extractedOutput to avoid double parsing.
+		if (extractedOutput) {
+			updateChainContext(`审查工作总结`,
+				`审查者已完成审查，以下是其审查总结：\n\n${extractedOutput}`
 			);
 		}
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ghyper9023/pi-dev-workflow",
-  "version": "0.5.0",
+  "version": "0.6.0",
   "keywords": [
     "pi-package"
   ],

package/tests/test-workflow-engine-bugs.mjs

@@ -495,17 +495,19 @@ assert(singleStepFuncStart !== -1, "找到 executeSingleStep 函数");
 const singleStepEndSearch = source.indexOf("async function executeLoopGroup", singleStepFuncStart);
 const fullSingleStep = source.slice(singleStepFuncStart, singleStepEndSearch);
 
-const hasChainContextKey = fullSingleStep.includes('chainKey');
-assertTrue(hasChainContextKey, "executeSingleStep 中有 chainKey 变量");
+// Verify 工作总结 entries still exist (preserved - from extractFinalOutput)
+const hasWorkSummaryKey = fullSingleStep.includes('工作总结');
+assertTrue(hasWorkSummaryKey, "executeSingleStep 中保留 '工作总结' 条目");
 
-const hasUpdateChainContext = fullSingleStep.includes('updateChainContext(chainKey');
-assertTrue(hasUpdateChainContext, "executeSingleStep 中调用 updateChainContext");
+const hasWorkSummaryUpdate = fullSingleStep.includes('updateChainContext');
+assertTrue(hasWorkSummaryUpdate, "executeSingleStep 中仍有 updateChainContext 调用（工作总结）");
 
-const hasPlannerKey = fullSingleStep.includes('"计划制定摘要"');
-assertTrue(hasPlannerKey, "agentName === planner 时使用 '计划制定摘要' key");
+// Verify the removed summary keys are no longer present
+const hasPlannerKeyRemoved = !fullSingleStep.includes('"计划制定摘要"');
+assertTrue(hasPlannerKeyRemoved, "executeSingleStep 中已移除 '计划制定摘要' key");
 
-const hasDocWriterKey = fullSingleStep.includes('"文档更新摘要"');
-assertTrue(hasDocWriterKey, "agentName === docWriter 时使用 '文档更新摘要' key");
+const hasDocWriterKeyRemoved = !fullSingleStep.includes('"文档更新摘要"');
+assertTrue(hasDocWriterKeyRemoved, "executeSingleStep 中已移除 '文档更新摘要' key");
 
 
 console.log("\n═══ Bug H 测试 — Agent 前置元数据解析 ═══\n");
@@ -648,11 +650,123 @@ const reviewHasWorkflowId = reviewTaskParams.includes("workflowId");
 assertTrue(reviewHasWorkflowId, "buildReviewTask 接收 workflowId 参数");
 
 
+console.log("\n");
+
+console.log("═══ Bug J 测试 — _workflowFileChanges 仅来自 git diff ═══\n");
+
+// ── Test J1: _workflowFileChanges.push 仅出现在 updateToolsFromGit ──
+console.log("📋 测试 J1: _workflowFileChanges.push 仅出现在 updateToolsFromGit\n");
+
+// Count all _workflowFileChanges.push occurrences
+const pushMatches = [...source.matchAll(/_workflowFileChanges\.push\(/g)];
+assertEq(pushMatches.length, 1, "_workflowFileChanges.push 仅出现 1 次");
+
+// Verify the single push is inside updateToolsFromGit by checking
+// the function body of updateToolsFromGit contains the push.
+const updateToolsStart = source.indexOf("function updateToolsFromGit");
+const nextFuncStart = source.indexOf("function saveCheckpoint", updateToolsStart);
+const updateToolsBody = source.slice(updateToolsStart, nextFuncStart);
+const pushInUpdateTools = updateToolsBody.includes("_workflowFileChanges.push");
+assertTrue(pushInUpdateTools, "updateToolsFromGit 函数体内包含 _workflowFileChanges.push");
+
+// ── Test J2: addWidgetSubStepTool 不再污染 _workflowFileChanges ──
+console.log("\n📋 测试 J2: addWidgetSubStepTool 不再污染 _workflowFileChanges\n");
+
+const addWidgetFunc = source.slice(
+	source.indexOf("function addWidgetSubStepTool"),
+	source.indexOf("function addWidgetSubStepOutput")
+);
+const hasNoFileChangesRef = !addWidgetFunc.includes("_workflowFileChanges");
+assertTrue(hasNoFileChangesRef, "addWidgetSubStepTool 中不再引用 _workflowFileChanges");
+
+// ── Test J3: executeSingleStep 中不再有基于 _workflowFileChanges 的统计 ──
+console.log("\n📋 测试 J3: executeSingleStep 中不再有 '执行摘要' 类 chain context\n");
+
+const hasNoExecutorSummary = !fullSingleStep.includes('执行摘要');
+assertTrue(hasNoExecutorSummary, "executeSingleStep 中不再有 '执行摘要' chain context");
+
+// ── Test J4: executeLoopGroup 中不再有 "代码实施/精简摘要" chain context ──
+console.log("\n📋 测试 J4: executeLoopGroup 中不再有 '代码实施/精简摘要' chain context\n");
+
+const loopGroupStart = source.indexOf("async function executeLoopGroup");
+assert(loopGroupStart !== -1, "找到 executeLoopGroup 函数");
+const loopGroupBody = source.slice(loopGroupStart);
+const hasNoCodeImplSummary = !loopGroupBody.includes('"代码实施摘要"') && !loopGroupBody.includes('"代码精简摘要"');
+assertTrue(hasNoCodeImplSummary, "executeLoopGroup 中不再有 '代码实施摘要' 或 '代码精简摘要' chain context");
+
+const hasNoReviewFeedbackKey = !loopGroupBody.includes('"代码审查反馈"') && !loopGroupBody.includes('"精简审查反馈"');
+assertTrue(hasNoReviewFeedbackKey, "executeLoopGroup 中不再有 '代码审查反馈' 或 '精简审查反馈' chain context");
+
+// ── Test J5: 工作总结条目在所有 agent 函数中仍保留 ──
+console.log("\n📋 测试 J5: '工作总结' 条目在所有 agent 函数中仍保留\n");
+
+const hasWorkSummaryInSingleStep = fullSingleStep.includes('工作总结');
+assertTrue(hasWorkSummaryInSingleStep, "executeSingleStep 保留 '工作总结' 条目");
+
+const hasWorkSummaryInLoop = loopGroupBody.includes('工作总结');
+assertTrue(hasWorkSummaryInLoop, "executeLoopGroup 保留 '工作总结' 条目");
+
+
 console.log("\n=== 增强功能测试汇总 ===\n");
 console.log("📋 附加测试覆盖:");
-console.log("  - G: 链上下文传递 (executeSingleStep)");
+console.log("  - G: 链上下文传递 (executeSingleStep) — 已更新验证工作总结");
 console.log("  - H: Agent 前置元数据解析 + MCP/SKILL 移除");
 console.log("  - I: 工作流 UUID 溯源机制");
+console.log("  - J: _workflowFileChanges 仅来自 git diff");
+console.log("\n═══ Bug K 测试 — git diff 精准识别 + .pi-dev-output 过滤 ═══\n");
+
+// ── Test K1: filePatterns 已移除 — 不再用 regex 猜文件路径 ──
+console.log("📋 测试 K1: filePatterns 已移除\n");
+
+const hasFilePatterns = source.includes("const filePatterns = [");
+assertFalse(hasFilePatterns, "filePatterns 数组已移除（不再用 regex 嗅探文件路径）");
+
+// ── Test K2: seenTools 文本解析 fallback 已移除 ──
+console.log("\n📋 测试 K2: seenTools JSON fallback 已移除\n");
+
+const hasJsonFallback = source.includes("if (seenTools.size === 0)");
+assertFalse(hasJsonFallback, "seenTools JSON tool_use fallback 已移除");
+
+// ── Test K3: outputPathPatterns 统一 inline 模式已移除 ──
+console.log("\n📋 测试 K3: outputPathPatterns 已简化\n");
+
+const hasOutputPathPatterns = source.includes("const outputPathPatterns = [");
+assertFalse(hasOutputPathPatterns, "outputPathPatterns 数组已移除（替换为 inline workflowId 过滤）");
+
+// ── Test K4: updateToolsFromGit 有 .pi-dev-output/ 过滤 ──
+console.log("\n📋 测试 K4: updateToolsFromGit 过滤 .pi-dev-output/\n");
+
+const hasDotPiDevFilter = source.includes('change.path.startsWith(".pi-dev-output/")');
+assertTrue(hasDotPiDevFilter, "updateToolsFromGit 跳过 .pi-dev-output/ 路径");
+
+// ── Test K5: output 路径匹配使用 escapedId + workflowId ──
+console.log("\n📋 测试 K5: output 路径使用 workflowId 过滤\n");
+
+const hasEscapedId = source.includes("const escapedId = _workflowId.replace(");
+assertTrue(hasEscapedId, "output 路径匹配使用 escapedId");
+
+// ── Test K6: progress handler output match 使用 _workflowId ──
+console.log("\n📋 测试 K6: progress handler 使用 workflowId\n");
+
+const hasIncludesWorkflowId = source.includes("pathCandidate.includes(_workflowId)");
+assertTrue(hasIncludesWorkflowId, "progress handler 使用 pathCandidate.includes(_workflowId)");
+
+// ── Test K7: addWidgetSubStepTool 只来自 git diff + progress handler ──
+console.log("\n📋 测试 K7: addWidgetSubStepTool 只来自必要来源\n");
+
+// Verify the two known call sites exist:
+// 1. updateToolsFromGit: calls addWidgetSubStepTool with git status + path
+// 2. runAgentWithProgress progress handler: calls addWidgetSubStepTool with parsed toolMatch
+// Both are runtime call sites (not the function definition itself).
+assertTrue(source.includes("addWidgetSubStepTool(stepIndex, agentName, `${change.status}   ${change.path}`)"), "updateToolsFromGit 调用 addWidgetSubStepTool");
+assertTrue(source.includes("addWidgetSubStepTool(stepIndex, agentName, `${gitStatus}   ${target}`)"), "progress handler 调用 addWidgetSubStepTool");
+
+// ── Test K8: addWidgetSubStepOutput 仍存在 (output 路径展示有用) ──
+console.log("\n📋 测试 K8: addWidgetSubStepOutput 仍保留\n");
+
+const hasAddWidgetOutput = source.includes("function addWidgetSubStepOutput");
+assertTrue(hasAddWidgetOutput, "addWidgetSubStepOutput 函数声明仍保留");
+
 
 
 console.log("\n═══════════════════════════════════════════════════════\n");