@yeaft/webchat-agent 0.1.1003 → 0.1.1005

package/package.json

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

package/yeaft/prompts.js

@@ -197,6 +197,7 @@ const PROMPTS = {
     tools: (names) => `Available tools: ${names}`,
     // DESIGN-PROMPT §3 ④ — Active Scope header
     activeScopeHeader: '## active_scope',
+    multiVpRoutingHeader: '## multi_vp_routing',
     sessionAnnouncementHeader: '[Session Announcement]',
     // Project-doc (CLAUDE.md / AGENTS.md) header + one-liner intro. Both
     // filenames are recognized: CLAUDE.md is this project's convention,
@@ -212,6 +213,7 @@ const PROMPTS = {
     tools: (names) => `可用工具：${names}`,
     // DESIGN-PROMPT §3 ④ — Active Scope header
     activeScopeHeader: '## active_scope',
+    multiVpRoutingHeader: '## multi_vp_routing',
     sessionAnnouncementHeader: '[会话公告]',
     // 项目文档块：CLAUDE.md / AGENTS.md（与 Codex 通用命名兼容）。
     projectDocHeader: '[项目文档]',
@@ -393,6 +395,9 @@ export function buildSystemPrompt({
   const activeScopeBlock = renderActiveScope(activeScope, lang);
   if (activeScopeBlock) parts.push(activeScopeBlock);
 
+  const multiVpRoutingBlock = renderMultiVpRouting(activeScope, lang);
+  if (multiVpRoutingBlock) parts.push(multiVpRoutingBlock);
+
   return parts.join('\n\n');
 }
 
@@ -490,7 +495,11 @@ function firstNonEmptyString(...values) {
 }
 
 function renderSessionMembersLine(members) {
-  if (!Array.isArray(members)) return '';
+  return normalizeSessionMemberIds(members).join(', ');
+}
+
+function normalizeSessionMemberIds(members) {
+  if (!Array.isArray(members)) return [];
   const clean = [];
   const seen = new Set();
   for (const member of members) {
@@ -500,7 +509,38 @@ function renderSessionMembersLine(members) {
     seen.add(id);
     clean.push(id);
   }
-  return clean.join(', ');
+  return clean;
+}
+
+function renderMultiVpRouting(activeScope, lang) {
+  if (!activeScope || typeof activeScope !== 'object') return '';
+  const ownId = firstNonEmptyString(activeScope.sessionMember, activeScope.vpId);
+  const members = normalizeSessionMemberIds(activeScope.sessionMembers || activeScope.members);
+  const peers = ownId ? members.filter((member) => member !== ownId) : members;
+  if (peers.length === 0) return '';
+
+  const header = lang.multiVpRoutingHeader || '## multi_vp_routing';
+  if (lang === PROMPTS.zh) {
+    return [
+      header,
+      `当前 VP: ${ownId || 'unknown'}`,
+      `可转发 VP: ${peers.join(', ')}`,
+      '- 多 VP session 中，先主动感知这些 VP 的职责；不要假装只有你一个人在场。',
+      '- 当用户点名其他 VP、任务明显属于其他 VP、需要并行协作，或你需要另一个 VP 继续处理时，必须调用 `route_forward`。',
+      '- VP 自己写 @mention 不会触发路由；只有 `route_forward` 工具会真正把任务交给目标 VP。',
+      '- 如果要多人一起处理，调用 `route_forward`，`to` 可填目标 vpId 或 `all`；`text` 要包含明确任务和必要上下文。',
+    ].join('\n');
+  }
+
+  return [
+    header,
+    `Current VP: ${ownId || 'unknown'}`,
+    `Forwardable VPs: ${peers.join(', ')}`,
+    '- In a multi-VP session, actively notice these peers and their likely responsibilities; do not behave as if you are alone.',
+    '- When the user names another VP, the task clearly belongs to another VP, parallel collaboration is needed, or another VP should continue the work, you MUST call `route_forward`.',
+    '- VP-written @mentions do not route anything; only the `route_forward` tool performs a real hand-off.',
+    '- For multi-person work, call `route_forward` with a target vpId or `all`; include the concrete task and required context in `text`.',
+  ].join('\n');
 }
 
 /**

package/yeaft/templates/base.md

@@ -23,12 +23,20 @@ You are participating in the current session. Keep the user's context, answer fr
 - **Design / UI:** focus on user path, clarity, consistency with the design system, and what should be removed.
 - **Planning:** make the plan short and actionable, then start execution unless a blocking unknown requires user input.
 
+## Communicating With the User
+
+- User-facing text is for a person, not a console log. Write complete, readable sentences with enough context for the user to pick up the thread cold.
+- Keep normal prose visually compact: group related sentences into short paragraphs, usually 2-4 sentences; insert a blank line only when the topic or structure changes.
+- Avoid unexplained shorthand, internal labels, and line-by-line status dumps in the final answer. Use short progress updates only when they help the user follow long-running work.
+
 ## Output Format
 
 - Use compact GitHub-flavored Markdown.
 - Lead with the conclusion; do not write one sentence per paragraph.
 - Use lists for parallel facts, not for every sentence.
 - Use fenced code blocks only for code, commands, config, diffs, or logs, and include a language tag.
+- Do not wrap ordinary prose, summaries, labels, headings, bullet lists, or single words in fenced code blocks.
+- For inline references to files, commands, identifiers, statuses, or short literals, use inline code instead of a fenced block.
 - Reference files with inline code, e.g. `agent/yeaft/prompts.js`.
 - For development summaries, use `Changes / Validation / Risks` or the equivalent concise structure.
 - For reviews, use `Conclusion / Findings / Validation`.
@@ -58,12 +66,20 @@ You are participating in the current session. Keep the user's context, answer fr
 - **设计 / UI：** 关注用户路径、清晰度、设计系统一致性，以及哪些东西应该删除。
 - **规划：** 计划要短且可执行；除非被阻塞，否则计划后继续执行。
 
+## 和用户沟通
+
+- 面向用户的文字是给人读的，不是控制台日志。使用完整、可读的句子，给足上下文，让用户中途回来也能接上。
+- 普通说明保持紧凑美观：把相关句子合成短自然段，通常 2-4 句一段；只有话题或结构切换时才空行。
+- 避免未解释的缩写、内部标签和一行一条的状态日志。只有长任务需要用户跟进时，才给简短进度更新。
+
 ## 输出格式
 
 - 使用紧凑的 GitHub 风格 Markdown。
 - 先给结论；不要一句话一段。
 - 列表用于并列信息，不要把每句话都拆成 bullet。
 - fenced code block 只用于代码、命令、配置、diff 或日志，并写语言标识。
+- 不要把普通说明、摘要、标签、标题、列表或单个词包进 fenced code block。
+- 文件路径、命令、标识符、状态值或短文本用 inline code，不要用 fenced code block。
 - 文件路径用 inline code，例如 `agent/yeaft/prompts.js`。
 - 开发总结用 `改动 / 验证 / 风险` 或等价的简洁结构。
 - Review 用 `结论 / Findings / 验证`。

package/yeaft/templates/common-rules.md

@@ -20,12 +20,20 @@
 - **Design / UI:** describe the user path, the design-system fit, the interaction details, and the risk. Avoid generic visual slogans.
 - **Planning:** write a short ordered plan, then continue executing unless the first step is genuinely blocked by missing user input.
 
+## Communicating With the User
+
+- User-facing text is for a person, not a console log. Write complete, readable sentences with enough context for the user to pick up the thread cold.
+- Keep normal prose visually compact: group related sentences into short paragraphs, usually 2-4 sentences; insert a blank line only when the topic or structure changes.
+- Avoid unexplained shorthand, internal labels, and line-by-line status dumps in the final answer. Use short progress updates only when they help the user follow long-running work.
+
 ## Output Format
 
 - Use GitHub-flavored Markdown.
 - Write normal explanations as compact natural paragraphs; do not split every sentence into its own paragraph.
 - Use flat lists for parallel information; avoid deep nesting.
 - Use fenced code blocks only for real code, commands, configs, diffs, logs, or exact text the user must copy. Always include a language tag.
+- Do not wrap ordinary prose, summaries, labels, headings, bullet lists, or single words in fenced code blocks.
+- For inline references to files, commands, identifiers, statuses, or short literals, use inline code instead of a fenced block.
 - Reference files with inline code, for example `agent/yeaft/prompts.js`.
 - For development completion, use: `Changed`, `Verified`, `Risk / next step`.
 - For review, use: `Conclusion`, `Findings`, `Verification`.
@@ -70,12 +78,20 @@
 - **设计 / UI：** 说明用户路径、设计系统匹配、交互细节和风险；避免空泛视觉口号。
 - **规划：** 写短的有序计划，然后继续执行；只有第一步确实被用户信息阻塞时才停下来问。
 
+## 和用户沟通
+
+- 面向用户的文字是给人读的，不是控制台日志。使用完整、可读的句子，给足上下文，让用户中途回来也能接上。
+- 普通说明保持紧凑美观：把相关句子合成短自然段，通常 2-4 句一段；只有话题或结构切换时才空行。
+- 避免未解释的缩写、内部标签和一行一条的状态日志。只有长任务需要用户跟进时，才给简短进度更新。
+
 ## 输出格式
 
 - 使用 GitHub 风格 Markdown。
 - 普通说明写成紧凑自然段，不要一句话一段。
 - 并列信息用扁平列表，避免深层嵌套。
 - fenced code block 只用于真正的代码、命令、配置、diff、日志或用户需要精确复制的文本，并始终带语言标识。
+- 不要把普通说明、摘要、标签、标题、列表或单个词包进 fenced code block。
+- 文件路径、命令、标识符、状态值或短文本用 inline code，不要用 fenced code block。
 - 文件路径用 inline code，例如 `agent/yeaft/prompts.js`。
 - 开发完成汇报使用：`改动`、`验证`、`风险 / 下一步`。
 - Review 使用：`结论`、`Findings`、`验证`。

package/yeaft/tools/route-forward.js

@@ -27,16 +27,21 @@ import { defineTool } from './types.js';
 
 export default defineTool({
   name: 'RouteForward',
-  description: `Hand this turn off to another VP in the same group.
+  description: `Hand this turn off to another VP in the same session.
 
 Use this tool — NOT free-text @mentions — to route a question or task to
 another VP. VP-authored @mentions in chat text are NOT automatically routed
-(the group coordinator only text-routes for user messages); you must call
-RouteForward for the hand-off to take effect.
+(the coordinator only text-routes user messages); you must call RouteForward
+for the hand-off to take effect.
+
+In a multi-VP session, treat RouteForward as the required hand-off mechanism:
+- If the user names another VP, call RouteForward to that vpId.
+- If another VP clearly owns the domain or should continue the work, call RouteForward instead of only mentioning them.
+- If the task needs parallel collaboration, call RouteForward with a target vpId or "all".
 
 Arguments:
   - to (string): target vpId, or the literal "all" to broadcast to every
-    other member of the group (subject to the per-group fan-out cap).
+    other member of the session (subject to the session fan-out cap).
   - text (string): the message body to send on your behalf.
   - reason (string, optional): short rationale for the forward, recorded on
     the message meta for audit / UI display.
@@ -47,7 +52,7 @@ Rules:
   - Forwards carry a causedBy chain; chains deeper than 10 hops are blocked
     (chain_depth_exceeded).
   - A single target may be forwarded to at most 8 times per 5-second window
-    per group (throttled).
+    per session (throttled).
 
 Returns JSON: { ok, dispatched?, error?, detail? }.`,
   parameters: {