dominds 0.1.0

package/dist/minds/minds-i18n.js

@@ -0,0 +1,131 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.defaultPersonaText = defaultPersonaText;
+exports.noneText = noneText;
+exports.noneRequiredFieldsText = noneRequiredFieldsText;
+exports.funcToolUsageLabels = funcToolUsageLabels;
+exports.funcToolRulesText = funcToolRulesText;
+exports.taskdocCanonicalCopy = taskdocCanonicalCopy;
+exports.memoryPreambleLabels = memoryPreambleLabels;
+exports.sharedScopeLabel = sharedScopeLabel;
+exports.personalScopeLabel = personalScopeLabel;
+exports.memoriesSummaryTitle = memoriesSummaryTitle;
+exports.memoriesSummarySectionShared = memoriesSummarySectionShared;
+exports.memoriesSummarySectionPersonal = memoriesSummarySectionPersonal;
+exports.memoriesSummaryLineShared = memoriesSummaryLineShared;
+exports.memoriesSummaryLinePersonal = memoriesSummaryLinePersonal;
+exports.sharedMemoriesHeader = sharedMemoriesHeader;
+exports.personalMemoriesHeader = personalMemoriesHeader;
+function defaultPersonaText(language) {
+    return language === 'zh' ? '你是一个乐于助人的助手。' : 'You are a helpful assistant.';
+}
+function noneText(language) {
+    return language === 'zh' ? '无。' : 'None.';
+}
+function noneRequiredFieldsText(language) {
+    return language === 'zh' ? '无' : 'None';
+}
+function funcToolUsageLabels(language) {
+    if (language === 'zh') {
+        return {
+            toolLabel: '函数工具',
+            invocationLabel: '调用方式',
+            invocationBody: '原生函数工具调用（严格 JSON 参数）',
+            requiredLabel: '必填字段',
+            parametersLabel: '参数',
+        };
+    }
+    return {
+        toolLabel: 'Function Tool',
+        invocationLabel: 'Invocation',
+        invocationBody: 'native function calling with strict JSON arguments',
+        requiredLabel: 'Required fields',
+        parametersLabel: 'Parameters',
+    };
+}
+function funcToolRulesText(language) {
+    return language === 'zh'
+        ? `\n- 对所有函数工具一律使用原生 function-calling；不要尝试用诉请行（例如 \`!?@name\`）调用它们。\n- 参数必须是严格 JSON：与 schema 精确匹配，包含所有 required 字段，不允许额外字段。`
+        : `\n- Use native function-calling for all function tools listed; do not attempt tellask lines (e.g., \`!?@name\`) for these.\n- Provide strict JSON arguments that match the tool schema exactly; include all required fields; no extra fields.`;
+}
+function taskdocCanonicalCopy(language) {
+    if (language === 'zh') {
+        return [
+            '**Taskdoc 封装与访问限制**',
+            '',
+            '- 任何 `.tsk/` 目录及其子路径（`**/*.tsk/**`）都是封装状态：禁止使用任何通用文件工具读取/写入/列目录（例如 `read_file` / `write_file` / `list_dir` 等）。',
+            '- 更新 Taskdoc 只能使用函数工具 `change_mind`（按章节整段替换；顶层用 `selector`，额外章节用 `category + selector`）。',
+            '- 读取“不会自动注入上下文”的额外章节，只能使用函数工具 `recall_taskdoc({ category, selector })`。',
+            '',
+            '**Taskdoc 自动注入规则（系统提示）**',
+            '',
+            '- 系统提示会把“有效 Taskdoc”自动注入到模型上下文中。',
+            '- 一定会注入顶层三段：`goals.md`、`constraints.md`、`progress.md`（按此顺序）。',
+            '- 可选注入 `bearinmind/`（仅固定白名单，最多 6 个文件）：`contracts.md`、`acceptance.md`、`grants.md`、`runbook.md`、`decisions.md`、`risks.md`。',
+            '- 若存在 `bearinmind/` 注入块，它会以 `## Bear In Mind` 出现在 `## Constraints` 与 `## Progress` 之间，并按以上固定顺序拼接。',
+            '- 除此之外，`.tsk/` 内任何其他目录/文件都不会被自动注入正文（系统只会注入一个“额外章节索引”用于提示；需要时用 `recall_taskdoc` 显式读取）。',
+        ].join('\n');
+    }
+    return [
+        '**Taskdoc encapsulation & access restrictions**',
+        '',
+        '- Any `.tsk/` directory and its subpaths (`**/*.tsk/**`) are encapsulated state: general file tools MUST NOT read/write/list them (e.g. `read_file` / `write_file` / `list_dir`).',
+        '- Taskdoc updates MUST go through the function tool `change_mind` (whole-section replace; use top-level `selector`, or `category + selector` for extra sections).',
+        '- To read extra sections that are NOT auto-injected, use the function tool `recall_taskdoc({ category, selector })`.',
+        '',
+        '**Taskdoc auto-injection rules (system prompt)**',
+        '',
+        '- The system prompt auto-injects the “effective Taskdoc” into the model context.',
+        '- It always injects the three top-level sections in order: `goals.md`, `constraints.md`, `progress.md`.',
+        '- It may also inject `bearinmind/` (fixed whitelist only; max 6 files): `contracts.md`, `acceptance.md`, `grants.md`, `runbook.md`, `decisions.md`, `risks.md`.',
+        '- If present, the injected block appears as `## Bear In Mind` between `## Constraints` and `## Progress`, and the files are concatenated in the fixed order above.',
+        '- No other directories/files inside `.tsk/` are auto-injected as body content (only an “extra sections index” may be injected for discoverability; use `recall_taskdoc` when needed).',
+    ].join('\n');
+}
+function memoryPreambleLabels(language) {
+    if (language === 'zh') {
+        return {
+            pathLabel: '路径',
+            lastModifiedLabel: '最后修改',
+            sizeLabel: '大小',
+            wordsLabel: '词数',
+            bytesUnit: '字节',
+            manageWithLabel: '可用工具',
+        };
+    }
+    return {
+        pathLabel: 'Path',
+        lastModifiedLabel: 'Last modified',
+        sizeLabel: 'Size',
+        wordsLabel: 'Words',
+        bytesUnit: 'bytes',
+        manageWithLabel: 'Manage with',
+    };
+}
+function sharedScopeLabel(language) {
+    return language === 'zh' ? '团队共享记忆' : 'Team Shared Memory';
+}
+function personalScopeLabel(language, agentId) {
+    return language === 'zh' ? `个人记忆 (@${agentId})` : `Personal Memory (@${agentId})`;
+}
+function memoriesSummaryTitle(language) {
+    return language === 'zh' ? '## 记忆摘要\n' : '## Memories Summary\n';
+}
+function memoriesSummarySectionShared(language) {
+    return language === 'zh' ? '### 共享' : '### Shared';
+}
+function memoriesSummarySectionPersonal(language) {
+    return language === 'zh' ? '### 个人\n' : '### Personal\n';
+}
+function memoriesSummaryLineShared(language, path) {
+    return language === 'zh' ? `- 共享: ${path}` : `- Shared: ${path}`;
+}
+function memoriesSummaryLinePersonal(language, path) {
+    return language === 'zh' ? `- 个人: ${path}` : `- Personal: ${path}`;
+}
+function sharedMemoriesHeader(language) {
+    return language === 'zh' ? '## 共享记忆' : '## Shared Memories';
+}
+function personalMemoriesHeader(language) {
+    return language === 'zh' ? '## 个人记忆\n' : '## Personal Memories\n';
+}

package/dist/minds/system-prompt.js

@@ -0,0 +1,281 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.formatTeamIntro = formatTeamIntro;
+exports.buildSystemPrompt = buildSystemPrompt;
+function formatTeamIntro(team, selfAgentId, language) {
+    const callSignLabel = language === 'zh' ? '呼号' : 'Call Sign';
+    const selfSuffix = language === 'zh' ? '（本人）' : ' (self)';
+    const focusLabel = language === 'zh' ? '关注' : 'Focus';
+    const visibleMembers = Object.values(team.members).filter((m) => m.hidden !== true);
+    if (visibleMembers.length === 0) {
+        return language === 'zh' ? '-（无可见队友）' : '- (no visible teammates)';
+    }
+    return visibleMembers
+        .map((m) => {
+        const isSelf = m.id === selfAgentId ? selfSuffix : '';
+        const gofor = (() => {
+            if (m.gofor === undefined)
+                return '';
+            if (typeof m.gofor === 'string')
+                return `\n  - ${focusLabel}:\n    - ${m.gofor}`;
+            if (Array.isArray(m.gofor)) {
+                if (m.gofor.length === 0)
+                    return '';
+                const list = m.gofor.map((t) => `    - ${t}`).join('\n');
+                return `\n  - ${focusLabel}:\n${list}`;
+            }
+            const entries = Object.entries(m.gofor);
+            if (entries.length === 0)
+                return '';
+            const list = entries.map(([k, v]) => `    - ${k}: ${v}`).join('\n');
+            return `\n  - ${focusLabel}:\n${list}`;
+        })();
+        return `- ${callSignLabel}: @${m.id}${isSelf} - ${m.name}${gofor}`;
+    })
+        .join('\n');
+}
+function buildSystemPrompt(input) {
+    if (input.language === 'zh') {
+        return `
+# Agent 系统提示
+
+## 身份
+- 成员 ID: \`${input.agent.id}\`
+- 全名: ${input.agent.name}
+
+## 语言模式
+- 你的内部工作语言是简体中文（用于系统提示、工具调用规则、队友/子对话叙事格式等）。
+- 你可能会收到一条短的引导信息，形如“用户可见回复语言：X”。当你对用户作答时，请优先遵循该引导；若未给出引导，则使用工作语言作答。
+
+## 角色设定
+${input.persona}
+
+## 知识
+${input.knowledge}
+
+## 经验
+${input.lessons}
+
+## 团队目录
+你与以下队友协作。使用他们的呼号与其交流。
+
+${input.teamIntro}
+
+## 交互能力
+你与队友的诉请（tellask）交互，使用一种极简的逐行前缀语法（对任意分片的流式输出鲁棒）。
+
+### 诉请（tellask）语法（务必精确遵守）
+**TL;DR（最重要的 6 条硬规则）**
+1) 只有“第 0 列以 \`!?\` 开头”的行才会被当作诉请行；其余都是普通 markdown。
+2) 一个诉请块会持续收集 \`!?...\` 行，直到遇到第一行“不以 \`!?\` 开头”的普通行才结束（推荐用空行分隔诉请块）。
+3) 一个诉请块的第一行必须是 \`!?@<name> ...\`（否则是 malformed）。
+4) 同一诉请块内：  
+   - 第一行是 headline；后续任何以 \`!?@\` 开头的行会继续追加到 headline（不会触发新工具）。  
+   - 以 \`!?\` 开头但不以 \`!?@\` 开头的行会进入 body。  
+5) **同一条消息里发起多个诉请：必须写多个诉请块，并用至少一行普通行分隔。**  
+6) **给队友发诉请（@tooling/@server/...）且需要跨轮协作：强烈建议带稳定的 \`!tellaskSession <tellaskSession>\`。**
+
+**\`!tellaskSession\`（跨轮协作的默认做法）**
+- 用途：让同一条工作流在多轮对话中可追踪，避免对方“每次像新工单”丢上下文。
+- 只写在 headline：\`!?@tooling !tellaskSession tooling-read-file-options ...\`（每个诉请块最多一次）。
+- 命名建议：\`<owner>-<area>-<short>\`，例如 \`tooling-read-file-options\`、\`server-ws-schema-v2\`。
+- 不要用于 \`!?@super\`（规则：\`@super\` 必须不带 \`!tellaskSession\`）。
+
+**关键易错点：当你需要在队友诉请中携带正文（步骤/上下文/验收标准等）时，正文每行也必须以 \`!?\` 开头，否则会被当作普通 markdown 分隔符导致 body 为空。**
+
+**常见坑（我们已经踩过）**
+- 连续写两行 \`!?@...\`：第二行不会触发第二个工具，会被并入同一诉请块 headline，导致“多余参数/格式不正确”等误导性错误。
+- 不要把多个工具调用写在同一个诉请块里：请用空行分隔成多个诉请块（空行本身就是普通行分隔符）。
+
+反例（会被合并成一个诉请块 headline）：
+\`\`\`plain-text
+!?@tool_a arg1
+!?@tool_b arg2
+\`\`\`
+
+正例（两个诉请块，用空行分隔）：
+\`\`\`plain-text
+!?@tool_a arg1
+
+!?@tool_b arg2
+\`\`\`
+
+**复制即用模板**
+- 队友诉请（带 topic）：
+\`\`\`plain-text
+!?@tooling !tellaskSession tooling-read-file-options
+!?请修复 read_file 的 parseReadFileOptions，并按验收用例回贴输出。
+\`\`\`
+- 队友诉请（带正文）：
+\`\`\`plain-text
+!?@pangu !tellaskSession ws-mod-guardrails
+!?请在工作区内定位所有仍在使用 tellask 工具语法（!?@tool）的地方，并迁移到函数工具调用；同时更新文档与测试故事。
+\`\`\`
+### 函数工具
+- 你必须通过原生 function-calling 发起函数工具调用。请提供严格的 JSON 参数对象，并且严格匹配工具 schema（不允许额外字段，必须包含所有 required 字段）。${input.funcToolRulesText}
+
+${input.funcToolUsageText || '没有可用的函数工具。'}
+
+### 函数工具调用 vs 诉请
+- 原生 function-calling 不能用于队友诉请：队友诉请必须使用 tellask。
+- tellask 文本不能用于函数工具调用：函数工具（包括对话控制/文件/文本编辑等）一律使用原生 function-calling。
+### 语法小抄（反模式）
+- 不要在 \`!?\` 前加项目符号、引用、编号或缩进（例如 \`- !?@tool\`、\`> !?@tool\`、\`  !?@tool\`）。
+- 当你只是提到呼号/工具名而不是发起诉请：不要让该行以 \`!?\` 开头；必要时用反引号包裹（例如 \`\`!?@pangu\`\`）。
+- mention ID 允许包含点号用于命名空间（例如 \`@team.lead\`）。末尾的点号视为标点并忽略（例如 \`@team.lead.\` 仍然指向 \`@team.lead\`）。
+
+### 特殊队友别名
+- \`!?@self\`：Fresh Boots Reasoning（FBR）自诉请。目标是当前 dialog 的 agentId，并创建一个新的、短暂的 subdialog（默认；最常用）。
+- \`!?@self !tellaskSession <tellaskSession>\`：带 tellaskSession 的 FBR 自诉请（少用）。仅当你明确需要可恢复的长期 workspace 时使用。
+- \`!?@super\`：Supdialog 诉请（Type A）**主语法**。只在 subdialog 内有效；诉请直接父对话（supdialog），暂时挂起该 subdialog，待父对话回复后再恢复。必须**不带** \`!tellaskSession\`。
+- \`!?@super\`：Supdialog 诉请（Type A）**主语法**。只在 subdialog 内有效；诉请直接父对话（supdialog），暂时挂起该 subdialog，待父对话回复后再恢复。必须**不带** \`!tellaskSession\`。
+  - \`!?@<supdialogAgentId>\`（不带 \`!tellaskSession\`）可作为语义容错，但优先使用 \`!?@super\`，尤其当 ID 可能相同（例如 FBR self-subdialogs）以避免歧义和意外自诉请混淆。
+
+### 工具集提示与队友诉请（tellask）
+
+${input.toolUsageText}${input.intrinsicToolInstructions
+            ? `\n### 对话控制工具\n${input.intrinsicToolInstructions}`
+            : '\n'}
+### 示例
+- 队友诉请：让 shell 专员运行命令（推荐写法）
+\`\`\`plain-text
+!?@<shell-specialist> !tellaskSession lint-types
+!?请在 repo root 执行：pnpm -C dominds lint:types
+!?回贴：exit_code + stdout/stderr（可截断，但需包含所有 TS error 行）
+\`\`\`
+
+- 队友诉请：带正文（普通行会自动结束该诉请块）
+\`\`\`plain-text
+!?@ux !tellaskSession ux-checklist
+!?请基于本 PR 的改动给出手工验收清单（严重度 + 复现步骤）。
+OK —— 我会等待你的结果，然后继续推进。
+\`\`\`
+
+- 反例：只写“我会请 shell 专员运行”，但没有诉请块（不会触发执行）
+\`\`\`plain-text
+我会请 shell 专员运行 pnpm -C dominds lint:types。
+\`\`\`
+
+- 反例：声称“已运行/已通过”，但没有看到回执（禁止）
+\`\`\`plain-text
+我已经让 shell 专员跑过了，lint:types 没问题。
+\`\`\`
+
+### 并发与编排
+- 同一条回复中的所有诉请会并发执行；在同一轮中，它们无法看到彼此的输出。
+- 让每个诉请都自给自足。
+- 需要前后依赖的步骤，请拆分到多轮，或使用编排器工具强制顺序。
+
+### 防止意外触发
+- 只有第 0 列以 \`!?\` 开头的行才会被解释为诉请行。
+- 行内的 \`!?\` 与 \`@\` 没有特殊含义。
+- 不确定时，不要在行首写 \`!?\`；需要展示字面量时用反引号包裹。
+`;
+    }
+    return `
+# Agent System Prompt
+
+## Identity
+- Member ID: \`${input.agent.id}\`
+- Full Name: ${input.agent.name}
+
+## Language Mode
+- Your internal working language is English (system prompt, tool rules, teammate/subdialog narrative formatting).
+- You may receive a short guide message like “User-visible response language: X”. When replying to the user, follow that guide; if absent, respond in the working language.
+
+## Persona
+${input.persona}
+
+## Knowledge
+${input.knowledge}
+
+## Lessons
+${input.lessons}
+
+## Team Directory
+You collaborate with the following teammates. Use their call signs to address them.
+
+${input.teamIntro}
+
+## Interaction Abilities
+You interact with teammates and "tellask" tools using a primitive line-prefix grammar designed to be robust under arbitrary streaming chunk boundaries.
+
+### Tellask Grammar
+- A tellask block consists of lines; every tellask line MUST begin at column 0 with literal \`!?\`. The \`!?\` prefix is not part of the payload.
+- Any line not starting with \`!?\` is normal markdown, and also acts as a separator: it terminates the current tellask block (if any). Therefore there is no explicit terminator.
+- The first tellask line in a block MUST start with \`!?@<name>\` to be considered valid. Otherwise the block still parses, but is reported as malformed and must be rendered by the UI.
+- Within a tellask block:
+  - Headline: starts from the first tellask line (after removing \`!?\`); subsequent lines starting with \`!?@\` extend the headline (multiline headline).
+  - Body: all tellask lines that start with \`!?\` but NOT \`!?@\` compose the body in order.
+- By default, a tellask block targets exactly one destination (the \`@name\` in the first line). However, for *teammate tellasks*, multiple teammate call signs appearing inside the headline (including multiline headlines) are treated as collective targets: Dominds will fan this out into one tellask per teammate with the same headLine/callBody payload. If you include \`!tellaskSession <tellaskSession>\`, it must appear at most once in the headline and applies to all targets. For multiple tool calls, you must still write multiple tellask blocks separated by normal lines.
+
+### Function Tools
+- You must invoke function tools via native function-calling. Provide a valid JSON object for the tool's arguments that strictly matches the tool schema (no extra fields, include all required fields).${input.funcToolRulesText}
+
+${input.funcToolUsageText || 'No function tools available.'}
+
+### Function Calling vs Tellask
+- Native function-calling cannot be used to tellask teammates: teammate tellasks must use tellask.
+- Tellask text cannot invoke function tools: all tools (including dialog control) must use native function-calling.
+
+### Anti-pattern Cheat Sheet
+- Do NOT prefix tellask lines with bullets, blockquotes, numbering, or indentation (e.g., \`- !?@tool\`, \`> !?@tool\`, \`  !?@tool\`).
+- When you are only mentioning a call sign/tool name and not making a tellask call, do not start the line with \`!?\`; wrap it in backticks if needed (e.g., \`\`!?@pangu\`\`).
+- Mention IDs may include dots for namespacing (e.g., \`@team.lead\`). A trailing dot is treated as punctuation and ignored (e.g., \`@team.lead.\` still targets \`@team.lead\`).
+
+### Teammate Tellasks
+- Prefer multi-teammate tellasks for parallel expertise. Keep requests specific and role-aware.
+
+### Special Teammate Aliases
+- \`!?@self\`: Fresh Boots Reasoning (FBR) self-call. Targets your current dialog agentId and creates a NEW ephemeral subdialog (default; most common).
+- \`!?@self !tellaskSession <tellaskSession>\`: FBR self-call with a registered tellask session (rare). Use only when you explicitly want a resumable long-lived fresh-boots workspace.
+- \`!?@super\`: Supdialog call (Type A) **primary syntax**. Only valid inside a subdialog; calls the direct parent dialog (supdialog), suspending this subdialog temporarily and then resuming with the parent's response. Must be used with NO \`!tellaskSession\`.
+  - \`!?@<supdialogAgentId>\` (no \`!tellaskSession\`) is a tolerated semantic fallback, but prefer \`!?@super\` especially when IDs might be identical (e.g., FBR self-subdialogs), to avoid ambiguity and accidental self-call confusion.
+
+### Toolset Prompts & Teammate Tellasks (Tellask)
+
+${input.toolUsageText}${input.intrinsicToolInstructions
+        ? `\n### Dialog Control Tools\n${input.intrinsicToolInstructions}`
+        : '\n'}
+### Examples
+- Single tellask call (no body)
+\`\`\`plain-text
+!?@tool_a arg1
+\`\`\`
+
+- Tellask call with a body (a normal line ends the block automatically)
+\`\`\`plain-text
+!?@pangu !tellaskSession fix-ws-mod
+!?1) Run lint/types
+!?2) Report errors and proposed fixes
+OK — I will wait for your results and then proceed.
+\`\`\`
+
+- Multiline headline + body
+\`\`\`plain-text
+!?@pangu Please do the following:
+!?@And keep the output concise
+!?1) Check logs/error.log
+!?2) Propose a fix
+\`\`\`
+
+- Multi-call (separate blocks)
+\`\`\`plain-text
+!?@tooling !tellaskSession tooling-read-file-options
+!?Please check why read_file options parsing is failing and propose a fix.
+
+!?@server !tellaskSession server-ws-func-tools
+!?Please review whether the WS handler needs updates for func-tool calls and report findings.
+\`\`\`
+
+### Concurrency & Orchestration
+- All calls in one response run concurrently; they cannot see each other's outputs in the same turn.
+- Design each call to be self-sufficient.
+- For dependent steps, split across turns or use an orchestrator tool to enforce sequencing.
+
+### Safety Against Accidental Mentions
+- Only lines beginning with \`!?\` at column 0 are interpreted as tellask lines.
+- Inline \`!?\` and \`@\` have no special meaning.
+- When in doubt, do not place \`!?\` at column 0; wrap literal examples in backticks.
+`;
+}