dominds 0.7.6 → 0.8.2

package/dist/minds/system-prompt.js

@@ -36,82 +36,84 @@ function formatTeamIntro(team, selfAgentId, language) {
 }
 function buildSystemPrompt(input) {
     const fbrScopeRuleZh = input.dialogScope === 'mainline'
-        ? '- 每次扪心自问（FBR）之前，务必先基于当前可观测事实调用 \\`change_mind\\` 更新差遣牒，体现任务最新进展情况。\\`!?@self\\` 自诉请正文不要冗余包含差遣牒已有信息。'
-        : '- 每次扪心自问（FBR）之前，务必先基于当前可观测事实分析是否与差遣牒内容存在差异，并将发现的情况包含在 \\`!?@self\\` 自诉请正文中。';
+        ? '- 系统会持续自动监控上下文健康度：没有吃紧/告急提示时，可以安全进行 FBR。如果有吃紧/告急提示，系统会提醒你，应先处理（提炼 + clear_mind）。随后基于当前可观测事实调用 \\`change_mind\\` 更新差遣牒，体现任务最新进展情况。FBR 自诉请正文不要冗余包含差遣牒已有信息。'
+        : '- 系统会持续自动监控上下文健康度：没有吃紧/告急提示时，可以安全进行 FBR。如果有吃紧/告急提示，系统会提醒你，应先处理。随后基于当前可观测事实分析是否与差遣牒内容存在差异，并将发现的情况包含在 FBR 自诉请正文中。';
     const fbrScopeRuleEn = input.dialogScope === 'mainline'
-        ? '- Before every FBR, first call \\`change_mind\\` based on currently observable facts to update the Taskdoc with the latest task progress, do not redundantly include information already present in the Taskdoc in the \\`!?@self\\` tellask body.'
-        : '- Before every FBR, first analyze whether currently observable facts differ from the Taskdoc, and include the findings in the \\`!?@self\\` tellask body.';
+        ? '- Before every FBR, the system will automatically alert on context health status: if there are no yellow/red alerts, you can safely proceed with FBR. If there are yellow/red alerts, handle them first (distill + clear_mind). Then call \\`change_mind\\` based on currently observable facts to update the Taskdoc with the latest task progress; do not redundantly include information already present in the Taskdoc in the FBR FBR body.'
+        : '- Before every FBR, the system will automatically alert on context health status: if there are no yellow/red alerts, you can safely proceed with FBR. If there are yellow/red alerts, handle them first. Then analyze whether currently observable facts differ from the Taskdoc, and include the findings in the FBR FBR body.';
     const fbrPhaseContractZh = [
-        '- FBR 必须按“发起 → 等待回贴 → 综合决策”三段执行：\\`!?@self\\` 只代表发起，不代表你已完成这轮推理。',
-        '- 发出 \\`!?@self\\` 后必须进入等待态：在该次 FBR 支线回贴返回前，不得给出“最终下一步行动决策”。',
+        '- FBR 必须按“发起 → 等待回贴 → 综合决策”三段执行：发起 `freshBootsReasoning` 只代表发起，不代表你已完成这轮推理。',
+        '- 发出 `freshBootsReasoning` 后必须进入等待态：在该次 FBR 支线回贴返回前，不得给出“最终下一步行动决策”。',
         '- 若 \\`fbr-effort = N\\`，必须等待全部 N 条回贴后再综合；不得基于部分回贴提前定稿。',
         '- 综合阶段必须显式区分“证据（FBR 回贴事实）”与“决策（下一步行动）”；若关键事实仍缺失，先补事实再迭代 FBR。',
     ].join('\n');
     const fbrPhaseContractEn = [
-        '- FBR MUST follow three phases: “initiate -> wait for feedback -> synthesize and decide”. \\`!?@self\\` means initiation only, not completed reasoning.',
-        '- After emitting \\`!?@self\\`, enter wait state: do not output a final next-action decision before feedback from that FBR sideline returns.',
+        '- FBR MUST follow three phases: “initiate -> wait for feedback -> synthesize and decide”. Calling `freshBootsReasoning` means initiation only, not completed reasoning.',
+        '- After calling `freshBootsReasoning`, enter wait state: do not output a final next-action decision before feedback from that FBR sideline returns.',
         '- If \\`fbr-effort = N\\`, wait for all N feedback drafts before synthesis; do not finalize based on partial drafts.',
         '- During synthesis, explicitly separate “evidence (FBR feedback facts)” from “decision (next action)”; if key facts are still missing, collect facts first and iterate FBR.',
     ].join('\n');
     const teammatePhaseContractZh = [
         '- 队友诉请必须遵循“发起 → 等待 → 判定 → 续推”四段协议：若目标未达成，立即发出下一轮诉请推进。',
-        '- 对队友诉请而言，收到回贴即表示该轮调用已结束；不存在“对方仍在后台继续执行同一诉请”的默认语义。要继续必须显式再发一轮诉请（通常沿用同一 \\`!tellaskSession <slug>\\`）。',
+        '- 对队友诉请而言，收到回贴即表示该轮调用已结束；不存在“对方仍在后台继续执行同一诉请”的默认语义。要继续必须显式再发一轮诉请函数（通常 \\`tellask\\` 复用同一 \\`sessionSlug\\`）。',
         '- 只有在存在明确 pending tellask 时，才可声明“等待回贴/等待结果”；否则必须执行下一动作（直接诉请或本地执行）。',
-        '- 能由队友诉请完成的执行性工作，禁止转交 @human 做“转发员”；当你写“让 @X 执行 Y”时，必须在同一回复内直接发出 \\`!?@X ...\\`。',
-        '- 当你处于队友诉请触发的支线且需要澄清时，必须发回问诉请 \\`!?@tellasker\\`（禁止携带 \\`!tellaskSession\\`）。例如在 @fullstack 诉请你的支线中，禁止写 \\`!?@fullstack !tellaskSession ...\\` 回问；正确写法是 \\`!?@tellasker\\`。',
+        '- 能由队友诉请完成的执行性工作，禁止转交 \\`askHuman\\` 做“转发员”；当你写“让 @X 执行 Y”时，必须在同一回复内直接发出 \\`tellask\\` 或 \\`tellaskSessionless\\`。',
+        '- 当你处于队友诉请触发的支线且需要澄清时，必须使用 \\`tellaskBack\\` 回问上游诉请者；\\`tellaskBack\\` 不携带 \\`sessionSlug\\`。',
     ].join('\n');
     const teammatePhaseContractEn = [
         '- Teammate Tellasks MUST follow four phases: “initiate -> wait -> judge -> continue”. If the objective is not met, immediately send the next Tellask round.',
-        '- For teammate Tellasks, a delivered response closes that call round; there is no default “still running in background” state for the same Tellask. To continue, emit a new Tellask explicitly (usually reusing the same \\`!tellaskSession <slug>\\`).',
+        '- For teammate Tellasks, a delivered response closes that call round; there is no default “still running in background” state for the same Tellask. To continue, emit a new Tellask function call explicitly (usually \\`tellask\\` with the same \\`sessionSlug\\`).',
         '- You may claim “waiting for reply/result” only when a concrete pending Tellask exists; otherwise execute the next action now (direct Tellask or local action).',
-        '- Do not use @human as a relay for executable teammate work. If you write “ask @X to do Y”, emit \\`!?@X ...\\` in the same response.',
-        '- When you are in a teammate-triggered sideline and need clarification, you MUST issue TellaskBack via \\`!?@tellasker\\` (and it must NOT carry \\`!tellaskSession\\`). For example, in a sideline tellasked by @fullstack, do NOT ask back with \\`!?@fullstack !tellaskSession ...\\`; the correct form is \\`!?@tellasker\\`.',
+        '- Do not use \\`askHuman\\` as a relay for executable teammate work. If you write “ask @X to do Y”, emit \\`tellask\\` or \\`tellaskSessionless\\` in the same response.',
+        '- When you are in a teammate-triggered sideline and need clarification, you MUST issue \\`tellaskBack\\` to ask back upstream; \\`tellaskBack\\` must not carry \\`sessionSlug\\`.',
     ].join('\n');
     const collaborationProtocolZh = [
-        '- \\`!?@...\\` 仅用于诉请队友/@self/@human，不是函数工具调用通道。',
-        '- 函数工具只能通过原生 function-calling 调用；不要把工具名写进 \\`!?@...\\` 诉请头。',
-        '- 对队友诉请默认带 \\`!tellaskSession <slug>\\` 并在同一会话续推（适用于非 \\`!?@self\\` 且非 \\`!?@tellasker\\` 的目标）；仅在确认一次性诉请足够时才可省略，且需说明理由。',
-        '- 例外优先级（强制）：\\`!?@tellasker\\` 是回问诉请专用目标，不属于“队友长线诉请默认规则”；因此既不适用默认 \\`!tellaskSession\\`，也禁止携带 \\`!tellaskSession\\`。',
+        '- Tellask 统一走函数工具通道：\\`tellaskBack\\` / \\`tellask\\` / \\`tellaskSessionless\\` / \\`askHuman\\` / \\`freshBootsReasoning\\`。',
+        '- 对队友诉请默认使用 \\`tellask\\` 并复用 \\`sessionSlug\\`；仅在确认一次性诉请足够时才使用 \\`tellaskSessionless\\`，且需说明理由。',
+        '- 例外优先级（强制）：\\`tellaskBack\\` 仅用于回问上游诉请者，不适用队友长线默认规则，也不携带 \\`sessionSlug\\`。',
         '- 队友诉请阶段协议（强制）：',
         teammatePhaseContractZh,
     ].join('\n');
     const collaborationProtocolEn = [
-        '- \\`!?@...\\` is only for tellasking teammates/@self/@human; it is not a function-tool invocation channel.',
-        '- Function tools must be invoked through native function-calling only; do not put tool names in \\`!?@...\\` tellask headlines.',
-        '- For teammate tellasks, default to \\`!tellaskSession <slug>\\` and continue in that same session (applies to targets other than \\`!?@self\\` and \\`!?@tellasker\\`); omit only for a justified one-shot call.',
-        '- Mandatory exception precedence: \\`!?@tellasker\\` is TellaskBack-only and outside the teammate-session default; it therefore does not use the default \\`!tellaskSession\\` and must never carry \\`!tellaskSession\\`.',
+        '- Tellask must use the function-tool channel: \\`tellaskBack\\` / \\`tellask\\` / \\`tellaskSessionless\\` / \\`askHuman\\` / \\`freshBootsReasoning\\`.',
+        '- For teammate tellasks, default to \\`tellask\\` and continue with the same \\`sessionSlug\\`; use \\`tellaskSessionless\\` only for justified one-shot calls.',
+        '- Mandatory exception precedence: \\`tellaskBack\\` is ask-back-only and outside the teammate-session default; it does not carry \\`sessionSlug\\`.',
         '- Teammate Tellask phase contract (mandatory):',
         teammatePhaseContractEn,
     ].join('\n');
     const fbrGuidelinesZh = [
-        '- \\`!?@self\\` 是 FBR 特有机制，不属于“队友诉请”分类；请按本节规则执行，不要套用“队友诉请默认带 \\`!tellaskSession\\`”的规则。',
-        '- 当用户明确要求“做一次 FBR/扪心自问”，对话主理人必须用 \\`!?@self\\` 发起。',
+        '- FBR 由 \\`freshBootsReasoning\\` 触发，不属于普通队友诉请分类；请按本节规则执行。',
+        '- 当用户明确要求“做一次 FBR/扪心自问”，对话主理人必须发起 \\`freshBootsReasoning\\`。',
         fbrScopeRuleZh,
-        '- FBR 的默认入口是瞬态 \\`!?@self\\`（不带 \\`!tellaskSession\\`）；仅当明确需要可恢复的长期 FBR 会话时，才使用 \\`!?@self !tellaskSession <slug>\\`，并说明理由。',
-        '- 即使用户未明确要求，在诉诸 @human（Q4H）之前，若感觉目标不够清晰或难以决定下一步行动，应首先发起一次扪心自问，充分总结当前对话上下文的事实情况作为 FBR 正文；在收到该次 FBR 回贴前，不要提前下最终行动决策。',
+        '- FBR 的标准入口是 \\`freshBootsReasoning({ tellaskContent })\\`；禁止用 \\`tellask\\` / \\`tellaskSessionless\\` 对自己发起 self-target 诉请来替代。',
+        '- 即使用户未明确要求，在诉诸 \\`askHuman\\`（Q4H）之前，若感觉目标不够清晰或难以决定下一步行动，应首先发起一次扪心自问，充分总结当前对话上下文的事实情况作为 FBR 正文；在收到该次 FBR 回贴前，不要提前下最终行动决策。',
         '- FBR 阶段协议（强制）：',
         fbrPhaseContractZh,
         '- 鼓励 FBR 自我建议立即获取哪些未明事实，得到建议利用当前对话工具获取，再补足上下文迭代 FBR 直到获得清晰的下一步行动思路。',
     ].join('\n');
     const fbrGuidelinesEn = [
-        '- \\`!?@self\\` is an FBR-specific mechanism, not part of the teammate-tellask category; follow this section’s rules instead of teammate-tellask defaults.',
-        '- When the user explicitly requests “do an FBR / fresh boots reasoning”, the Dialog Responder must initiate \\`!?@self\\`.',
+        '- FBR is triggered by `freshBootsReasoning`, not by normal teammate tellasks; follow this section’s rules.',
+        '- When the user explicitly requests “do an FBR / fresh boots reasoning”, the Dialog Responder must call `freshBootsReasoning`.',
         fbrScopeRuleEn,
-        '- The default FBR entry is transient \\`!?@self\\` (without \\`!tellaskSession\\`); use \\`!?@self !tellaskSession <slug>\\` only when you explicitly need a resumable long-lived FBR thread, and explain why.',
-        '- Even without an explicit request, before resorting to @human (Q4H), if the goal is unclear or deciding the next action is difficult, you should first initiate FBR and summarize current dialog facts as the FBR body; do not finalize the next action before that FBR feedback returns.',
+        '- The standard FBR entry is \\`freshBootsReasoning({ tellaskContent })\\`; do not emulate FBR via self-targeted \\`tellask\\` / \\`tellaskSessionless\\`.',
+        '- Even without an explicit request, before resorting to \\`askHuman\\` (Q4H), if the goal is unclear or deciding the next action is difficult, you should first initiate FBR and summarize current dialog facts as the FBR body; do not finalize the next action before that FBR feedback returns.',
         '- FBR phase contract (mandatory):',
         fbrPhaseContractEn,
         '- Encourage FBR to recommend which missing facts to obtain immediately; then use the current dialog’s tools to fetch them, update context, and iterate FBR until a clear next action emerges.',
     ].join('\n');
     const tellaskInteractionRulesZh = [
-        '- 诉请（tellask）使用逐行前缀语法：只有第 0 列以 \\`!?\\` 开头的行才会被当作诉请行。',
-        '- 诉请块以连续 \\`!?...\\` 行组成；遇到第一行普通行即结束。',
-        '- 一个诉请块的第一行必须是 \\`!?@<name> ...\\`。',
+        '- \\`tellaskBack\\`：仅用于支线回问上游诉请者。',
+        '- \\`tellask\\`：用于可恢复的长线诉请（必须提供 \\`targetAgentId\\` / \\`sessionSlug\\` / \\`tellaskContent\\`）。',
+        '- \\`tellaskSessionless\\`：用于一次性诉请（必须提供 \\`targetAgentId\\` / \\`tellaskContent\\`）。',
+        '- \\`askHuman\\`：用于 Q4H（向人类请求必要澄清/决策/授权/缺失输入）。',
+        '- \\`freshBootsReasoning\\`：用于发起扪心自问（FBR）支线（仅需 \\`tellaskContent\\`）。',
     ].join('\n');
     const tellaskInteractionRulesEn = [
-        '- Tellask uses a line-prefix grammar: only lines starting at column 0 with \\`!?\\` are tellask lines.',
-        '- A tellask block is a consecutive run of \\`!?...\\` lines; the first non-\\`!?\\` line ends the block.',
-        '- The first tellask line in a block must start with \\`!?@<name> ...\\`.',
+        '- \\`tellaskBack\\`: ask back upstream from a sideline dialog only.',
+        '- \\`tellask\\`: resumable tellask (requires \\`targetAgentId\\` / \\`sessionSlug\\` / \\`tellaskContent\\`).',
+        '- \\`tellaskSessionless\\`: one-shot tellask (requires \\`targetAgentId\\` / \\`tellaskContent\\`).',
+        '- \\`askHuman\\`: Q4H for necessary clarification/decision/authorization/missing input.',
+        '- \\`freshBootsReasoning\\`: starts an FBR sideline dialog (requires \\`tellaskContent\\`).',
     ].join('\n');
     const functionToolRulesZh = [
         '- 回答必须基于可观测事实；为获取事实优先使用可用工具，缺乏观测事实时明确说明并请求/补充获取，不得臆测。',
@@ -146,15 +148,15 @@ function buildSystemPrompt(input) {
 ## 术语表
 
 - 诉请（Tellask）：对智能体的结构化请求。
-- 诉请头（Tellask headline）：诉请块第一行，形如 \`!?@<name> ...\`，结构化指令（如 \`!tellaskSession <slug>\`）写在这里。
-- 诉请正文（Tellask body）：诉请块内以 \`!?\` 开头但不以 \`!?@\` 开头的行，用于承载上下文/约束/验收。
+- 提及列表（mentionList）：仅用于 \`tellask\` / \`tellaskSessionless\` 的队友目标列表（\`@<agentId>\`）。
+- 诉请内容（tellaskContent）：tellask 系列函数的正文参数，用于承载上下文/约束/验收。
 - 对话主理人（Dialog Responder）：负责当前对话推进与输出的智能体。
 - 诉请者（tellasker）：发出诉请的对话主理人。
 - 被诉请者（tellaskee）：接收诉请的对话主理人/队友。
-- 回问诉请（TellaskBack）：支线对话用 \`!?@tellasker\` 回问诉请者以澄清。
-- 扪心自问（FBR）：仅由 \`!?@self\` 触发的“无工具”支线推理机制。
-- Q4H（Question for Human）：通过 \`!?@human\` 向人类请求必要的澄清/决策/授权/缺失输入。
-- 长线诉请（Tellask Session）：使用 \`!tellaskSession <slug>\` 的可恢复多轮协作。
+- 回问诉请（TellaskBack）：支线对话用 \`tellaskBack\` 回问诉请者以澄清。
+- 扪心自问（FBR）：由 \`freshBootsReasoning\` 触发的“无工具”支线推理机制。
+- Q4H（Question for Human）：通过 \`askHuman\` 向人类请求必要的澄清/决策/授权/缺失输入。
+- 长线诉请（Tellask Session）：使用 \`tellask\` + \`sessionSlug\` 的可恢复多轮协作。
 - 一次性诉请（Fresh Tellask）：一次性、不可恢复的诉请。
 - 主线对话（Mainline dialog）：承载共享差遣牒并负责整体推进的对话。
 - 支线对话（Sideline dialog）：为分项任务临时创建的工作对话。
@@ -178,9 +180,9 @@ ${input.envIntro}
 
 ## 团队目录
 
-**特殊成员**：人类（@human）是特殊团队成员。你可以使用 \`!?@human ...\` 发起 Q4H（Question for Human），用于请求必要的澄清/决策/授权/提供缺失输入，或汇报当前环境中无法由智能体自主完成的阻塞事项。
-**注意**：不要把可由智能体完成的执行性工作外包给 @human。向 @human 的请求应尽量最小化、可验证（给出需要的具体信息、预期格式/选项），并在得到答复后继续由智能体自主完成后续工作。
-**补充**：像“发起队友诉请/推进迭代/收集回贴”这类常规协作动作属于智能体的自主工作流，不要向 @human 询问“是否要执行”；直接执行并在必要时汇报进度即可。
+**Q4H 机制**：通过 \`askHuman\` 发起向人类请求（澄清/决策/授权/缺失输入），或汇报当前环境中无法由智能体自主完成的阻塞事项。
+**注意**：不要把可由智能体完成的执行性工作外包给 \`askHuman\`。Q4H 请求应尽量最小化、可验证（给出需要的具体信息、预期格式/选项），并在得到答复后继续由智能体自主完成后续工作。
+**补充**：像“发起队友诉请/推进迭代/收集回贴”这类常规协作动作属于智能体的自主工作流，不要向 \`askHuman\` 询问“是否要执行”；直接执行并在必要时汇报进度即可。
 
 你与以下智能体队友协作。使用他们的呼号与其交流、安排分项工作。
 
@@ -208,7 +210,7 @@ ${input.toolsetManualIntro}
 
 ## 交互协议
 
-### Tellask（仅用于队友/@self/@human）
+### Tellask Special Functions（队友/FBR/Q4H）
 ${tellaskInteractionRulesZh}
 
 ### 函数工具（仅原生 function-calling）
@@ -237,15 +239,15 @@ System notifications convey important state changes (e.g., context caution/criti
 ## Glossary
 
 - Tellask: a structured request addressed to an agent.
-- Tellask headline: the first line of a Tellask block, e.g. \`!?@<name> ...\`; directives like \`!tellaskSession <slug>\` go here.
-- Tellask body: lines starting with \`!?\` but not \`!?@\`, carrying context/constraints/acceptance.
+- Mention list (\`mentionList\`): teammate targets for \`tellask\` / \`tellaskSessionless\` only (\`@<agentId>\`).
+- Tellask content (\`tellaskContent\`): main call payload carrying context/constraints/acceptance.
 - Dialog Responder: the role responsible for driving a dialog and producing responses.
 - tellasker: the Dialog Responder that issued the Tellask.
 - tellaskee: the Dialog Responder/agent that receives the Tellask.
-- TellaskBack: a sideline uses \`!?@tellasker\` to ask the tellasker for clarification.
-- Fresh Boots Reasoning (FBR): a tool-less sideline reasoning mechanism triggered only by \`!?@self\`.
-- Q4H (Question for Human): use \`!?@human\` to request necessary clarification/decision/authorization/missing input from a human.
-- Tellask Session: resumable multi-turn work using \`!tellaskSession <slug>\`.
+- TellaskBack: a sideline uses \`tellaskBack\` to ask the tellasker for clarification.
+- Fresh Boots Reasoning (FBR): a tool-less sideline reasoning mechanism triggered by \`freshBootsReasoning\`.
+- Q4H (Question for Human): use \`askHuman\` to request necessary clarification/decision/authorization/missing input from a human.
+- Tellask Session: resumable multi-turn work using \`tellask\` with \`sessionSlug\`.
 - Fresh Tellask: a one-shot, non-resumable Tellask.
 - Mainline dialog: the dialog that owns the shared Taskdoc and overall progress.
 - Sideline dialog: a temporary dialog for a subtask.
@@ -269,9 +271,9 @@ ${input.envIntro}
 
 ## Team Directory
 
-**Special member**: Human (@human) is a special team member. You may use \`!?@human ...\` to ask a Q4H (Question for Human) when you need necessary clarification/decision/authorization/missing inputs, or to report blockers that cannot be completed autonomously in the current environment.
-**Note**: Do not outsource executable work to @human. Keep Q4H requests minimal and verifiable (ask for specific info, expected format/options), then continue the remaining work autonomously after receiving the answer.
-**Addendum**: Routine coordination actions (e.g., tellasking teammates, driving iterations, collecting replies) are part of the agent’s autonomous workflow; do not ask @human for permission to do them. Execute and report progress when needed.
+**Q4H mechanism**: Use \`askHuman\` when you need clarification/decision/authorization/missing inputs from a human, or when reporting blockers that cannot be completed autonomously in the current environment.
+**Note**: Do not outsource executable work through \`askHuman\`. Keep Q4H requests minimal and verifiable (ask for specific info, expected format/options), then continue the remaining work autonomously after receiving the answer.
+**Addendum**: Routine coordination actions (e.g., tellasking teammates, driving iterations, collecting replies) are part of the agent’s autonomous workflow; do not use \`askHuman\` for permission-seeking on those actions. Execute and report progress when needed.
 
 You collaborate with the following teammates. Use their call signs to address them.
 
@@ -299,7 +301,7 @@ ${input.toolsetManualIntro}
 
 ## Interaction Protocols
 
-### Tellask (teammates/@self/@human only)
+### Tellask Special Functions (teammates/FBR/Q4H)
 ${tellaskInteractionRulesEn}
 
 ### Function Tools (native function-calling only)