@yeaft/webchat-agent 0.1.339 → 0.1.343

package/crew-i18n.js

@@ -22,9 +22,10 @@ const messages = {
 - 如果你遇到不确定的问题，@ 决策者 "${dm}"，而不是直接 @ human
 - 如果你是决策者且遇到需要人类判断的问题，才 @ human
 - 可以一次发多个 ROUTE 块来并行分配任务给不同角色
-- ROUTE 块必须在回复的最末尾
+- **🚨 ROUTE 块必须在回复的最末尾，且你的回复必须以 ROUTE 块结尾。不发 ROUTE = 工作白做，结果无法传递给下一个人**
 - 当你的任务已完成且不需要其他角色继续时，ROUTE 回决策者 "${dm}" 做总结
-- 在正文中可用 @角色name 提及某个角色（如 @developer），但这不会触发路由，仅供阅读`,
+- 在正文中可用 @角色name 提及某个角色（如 @developer），但这不会触发路由，仅供阅读
+- **严禁在 summary 字段中填写占位符文本（如"请审查代码变更..."）——必须填写你实际完成的工作内容**`,
 
     // Decision maker sections
     toolUsage: '# 工具使用',
@@ -131,11 +132,14 @@ ${isDevTeam ? '3' : '2'}. **任务完成** - 所有任务已完成，给出完
 
       // dev team
       developer: (dm) => `代码完成后，必须同时发两个 ROUTE 块分别交给审查者和测试者（缺一不可）。
-UI/交互方案不确定时找设计师确认。需求不明确时找决策者 "${dm}" 确认。`,
-      reviewer_dev: (dm) => `审查完成后：评分 ≥ 9分通过，ROUTE 给决策者 "${dm}" 报告通过。评分 < 9分打回给开发者修改。
-遇到架构层面的问题找决策者 "${dm}" 讨论。`,
+UI/交互方案不确定时找设计师确认。需求不明确时找决策者 "${dm}" 确认。
+**⚠️ 你的回复必须以 ROUTE 块结尾。不发 ROUTE = 代码无法进入审查流程。**`,
+      reviewer_dev: (dm) => `审查完成后：评分 ≥ 9分通过，ROUTE 给对应的测试者（如 rev-1 → test-1）告知审查通过、可以开始测试。评分 < 9分打回给开发者修改。
+遇到架构层面的问题找决策者 "${dm}" 讨论。
+**⚠️ 你的回复必须以 ROUTE 块结尾。不发 ROUTE = 审查结果无法传递。**`,
       tester_dev: (dm) => `测试完成后：全部通过则 ROUTE 给决策者 "${dm}" 报告通过。发现 bug 则编写复现测试，ROUTE 给开发者修复。
-遇到测试环境问题找决策者 "${dm}" 协调。`,
+遇到测试环境问题找决策者 "${dm}" 协调。
+**⚠️ 你的回复必须以 ROUTE 块结尾。不发 ROUTE = 测试结果无法传递。**`,
       designer_dev: (dm) => `设计完成后交给决策者 "${dm}" 审阅，通过后交给开发者实现。
 收到开发者的 UI 问题反馈时评估并调整设计方案。需求不明确找决策者 "${dm}" 确认。`,
 
@@ -156,7 +160,7 @@ UI/交互方案不确定时找设计师确认。需求不明确时找决策者 "
 - 测试: ${testLabel} (${testName})
 
 开发完成后，请同时发两个 ROUTE 块分别给 ${revName} 和 ${testName}：`,
-    devGroupBindingNote: '两者会并行工作，各自完成后独立 ROUTE 回 PM。',
+    devGroupBindingNote: '审查者完成后 ROUTE 给测试者开始测试，测试者完成后 ROUTE 回 PM。',
 
     implLoginPage: '实现登录页面',
     implLoginSummary: '请实现登录页面，包括表单验证和API调用',
@@ -265,9 +269,10 @@ UI/交互方案不确定时找设计师确认。需求不明确时找决策者 "
 - If you encounter an uncertain issue, @ the decision maker "${dm}" instead of directly @ human
 - Only @ human if you are the decision maker and the issue requires human judgment
 - You can send multiple ROUTE blocks to assign tasks to different roles in parallel
-- ROUTE blocks must be at the very end of your reply
+- **🚨 ROUTE blocks must be at the very end of your reply, and your reply MUST end with a ROUTE block. Not sending a ROUTE = your work is wasted, results cannot be passed to the next person**
 - When your task is complete and no further role handoff is needed, ROUTE back to the decision maker "${dm}" for summary
-- You can mention a role by @roleName in the body text (e.g., @developer) for reference only — this does not trigger routing`,
+- You can mention a role by @roleName in the body text (e.g., @developer) for reference only — this does not trigger routing
+- **Never use placeholder text in the summary field (e.g., "Please review code changes...") — you must describe your actual work**`,
 
     // Decision maker sections
     toolUsage: '# Tool Usage',
@@ -374,11 +379,14 @@ Execute stop-losses immediately when triggered and notify the decision maker. Re
 
       // dev team
       developer: (dm) => `After code is complete, you must send two ROUTE blocks simultaneously to reviewer and tester (both required).
-Check with designer for UI/interaction questions. Check with decision maker "${dm}" for unclear requirements.`,
-      reviewer_dev: (dm) => `After review: score >= 9 passes, ROUTE to decision maker "${dm}" to report approval. Score < 9: send back to developer with issues.
-Discuss architecture-level concerns with decision maker "${dm}".`,
+Check with designer for UI/interaction questions. Check with decision maker "${dm}" for unclear requirements.
+**⚠️ Your reply MUST end with ROUTE blocks. Not sending a ROUTE = code cannot enter the review process.**`,
+      reviewer_dev: (dm) => `After review: score >= 9 passes, ROUTE to the corresponding tester (e.g., rev-1 → test-1) to notify review passed and testing can begin. Score < 9: send back to developer with issues.
+Discuss architecture-level concerns with decision maker "${dm}".
+**⚠️ Your reply MUST end with a ROUTE block. Not sending a ROUTE = review results cannot be passed on.**`,
       tester_dev: (dm) => `After testing: all pass, ROUTE to decision maker "${dm}" to report approval. Bug found: write reproduction test, ROUTE to developer for fixing.
-Coordinate test environment issues with decision maker "${dm}".`,
+Coordinate test environment issues with decision maker "${dm}".
+**⚠️ Your reply MUST end with a ROUTE block. Not sending a ROUTE = test results cannot be passed on.**`,
       designer_dev: (dm) => `After design is complete, hand to decision maker "${dm}" for review, then to developer for implementation.
 Evaluate and adjust design based on developer UI feedback. Check with decision maker "${dm}" for unclear requirements.`,
 
@@ -399,7 +407,7 @@ Discuss with the decision maker when technical implementation is uncertain.`,
 - Tester: ${testLabel} (${testName})
 
 After development is complete, send two ROUTE blocks simultaneously to ${revName} and ${testName}:`,
-    devGroupBindingNote: 'Both will work in parallel and independently ROUTE back to PM when done.',
+    devGroupBindingNote: 'Reviewer ROUTEs to tester after review, tester ROUTEs back to PM after testing.',
 
     implLoginPage: 'Implement login page',
     implLoginSummary: 'Please implement the login page including form validation and API calls',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yeaft/webchat-agent",
-  "version": "0.1.339",
+  "version": "0.1.343",
   "description": "Remote agent for Yeaft WebChat — connects worker machines to the central server",
   "main": "index.js",
   "type": "module",