dominds 1.17.3 → 1.17.5

package/dist/apps-host/host.js

@@ -82,7 +82,16 @@ function parseReminderRequest(value) {
         if (echoback === null) {
             throw new Error('Invalid app tool reminder request: upsert.echoback must be boolean');
         }
-        return { kind: 'upsert', ownerRef, content, meta, position, echoback };
+        const renderModeRaw = value['renderMode'];
+        const renderMode = renderModeRaw === undefined
+            ? undefined
+            : renderModeRaw === 'plain' || renderModeRaw === 'markdown'
+                ? renderModeRaw
+                : null;
+        if (renderMode === null) {
+            throw new Error('Invalid app tool reminder request: upsert.renderMode must be plain|markdown');
+        }
+        return { kind: 'upsert', ownerRef, content, meta, position, echoback, renderMode };
     }
     throw new Error(`Invalid app tool reminder request kind: ${String(kind)}`);
 }
@@ -138,7 +147,9 @@ function isReminderState(value) {
     if (meta !== undefined && !isJsonValue(meta))
         return false;
     const echoback = value['echoback'];
-    return echoback === undefined || typeof echoback === 'boolean';
+    const renderMode = value['renderMode'];
+    return ((echoback === undefined || typeof echoback === 'boolean') &&
+        (renderMode === undefined || renderMode === 'plain' || renderMode === 'markdown'));
 }
 function isReminderApplyResult(value) {
     if (!isRecord(value))

package/dist/apps-host/ipc-types.js

@@ -46,7 +46,15 @@ function parseReminderState(v, at) {
     const echoback = echobackRaw === undefined ? undefined : typeof echobackRaw === 'boolean' ? echobackRaw : null;
     if (echoback === null)
         throw new Error(`Invalid ${at}.echoback: must be boolean`);
-    return { content, meta: metaRaw, echoback };
+    const renderModeRaw = v['renderMode'];
+    const renderMode = renderModeRaw === undefined
+        ? undefined
+        : renderModeRaw === 'plain' || renderModeRaw === 'markdown'
+            ? renderModeRaw
+            : null;
+    if (renderMode === null)
+        throw new Error(`Invalid ${at}.renderMode: must be plain|markdown`);
+    return { content, meta: metaRaw, echoback, renderMode };
 }
 function parseReminderApplyRequest(v, at) {
     if (!isRecord(v))
@@ -75,6 +83,14 @@ function parseReminderApplyRequest(v, at) {
         const echoback = echobackRaw === undefined ? undefined : typeof echobackRaw === 'boolean' ? echobackRaw : null;
         if (echoback === null)
             throw new Error(`Invalid ${at}.echoback: must be boolean`);
+        const renderModeRaw = v['renderMode'];
+        const renderMode = renderModeRaw === undefined
+            ? undefined
+            : renderModeRaw === 'plain' || renderModeRaw === 'markdown'
+                ? renderModeRaw
+                : null;
+        if (renderMode === null)
+            throw new Error(`Invalid ${at}.renderMode: must be plain|markdown`);
         return {
             kind: 'upsert',
             ownerRef,
@@ -82,6 +98,7 @@ function parseReminderApplyRequest(v, at) {
             meta: metaRaw,
             position,
             echoback,
+            renderMode,
         };
     }
     if (kind === 'delete') {

package/dist/dialog-fork.js

@@ -38,6 +38,7 @@ function cloneReminderSnapshot(snapshot) {
         meta: snapshot.meta,
         echoback: snapshot.echoback,
         scope: snapshot.scope ?? 'dialog',
+        renderMode: snapshot.renderMode ?? 'markdown',
         createdAt: snapshot.createdAt,
         priority: snapshot.priority,
     });

package/dist/dialog.d.ts

@@ -294,6 +294,7 @@ export declare abstract class Dialog {
     get activeGenSeq(): number;
     get activeGenSeqOrUndefined(): number | undefined;
     get activeGenCourseOrUndefined(): number | undefined;
+    get hasActiveGeneration(): boolean;
     /**
      * Check if generation has started for the current course.
      * Used to ensure subdialog_final_response_evt arrives after parent events.

package/dist/dialog.js

@@ -374,6 +374,7 @@ class Dialog {
             meta,
             echoback: options?.echoback,
             scope: options?.scope ?? 'dialog',
+            renderMode: options?.renderMode,
         });
         const insertIndex = position !== undefined ? position : this.reminders.length;
         if (insertIndex < 0 || insertIndex > this.reminders.length) {
@@ -405,6 +406,7 @@ class Dialog {
             scope: oldReminder.scope,
             createdAt: oldReminder.createdAt,
             priority: oldReminder.priority,
+            renderMode: options?.renderMode ?? oldReminder.renderMode,
         });
         this.reminders[index] = updatedReminder;
         this.touchReminders();
@@ -479,6 +481,7 @@ class Dialog {
                             scope: reminder.scope,
                             createdAt: reminder.createdAt,
                             priority: reminder.priority,
+                            renderMode: reminder.renderMode,
                         });
                         const contentChanged = updatedReminder.content !== reminder.content;
                         const metaChanged = updatedReminder.meta !== reminder.meta;
@@ -539,8 +542,10 @@ class Dialog {
             content: r.content,
             meta: r.meta,
             reminder_id: r.id,
+            renderRevision: (0, tool_1.computeReminderRenderRevision)(r),
             echoback: (0, tool_1.reminderEchoBackEnabled)(r),
             scope: r.scope,
+            renderMode: r.renderMode ?? 'markdown',
         }));
         // Emit full_reminders_update event with complete reminder list including metadata
         const fullRemindersEvt = {
@@ -581,6 +586,9 @@ class Dialog {
     get activeGenCourseOrUndefined() {
         return this._activeGenCourse;
     }
+    get hasActiveGeneration() {
+        return this._activeGenCourse !== undefined;
+    }
     /**
      * Check if generation has started for the current course.
      * Used to ensure subdialog_final_response_evt arrives after parent events.

package/dist/docs/dialog-system.md

@@ -246,9 +246,9 @@ flowchart TD
 **Sideline delivery rule (normative)**:
 
 - If a sideline dialog has completed all assigned goals and can deliver the final result, it MUST reply directly with the response body; do not use `tellaskBack` to send final delivery.
-- Runtime treats that direct reply as the completion delivery to the tellasker dialog and injects the work-language marker automatically (`【Completed】` in English work language, and the localized Chinese completion marker in Chinese work language).
+- Runtime treats that direct reply as the completion delivery to the tellasker dialog and injects the work-language marker automatically (`【Completed】` in English work language, `【最终完成】` in Chinese work language).
 - If any goal is incomplete, the dialog is blocked, or critical context is missing, it MUST issue `tellaskBack({ tellaskContent: "..." })` to request clarification or next-step confirmation before proceeding.
-- **FBR exception**: FBR sideline dialogs are tellask-free (no `tellaskBack`); they must list missing context and return.
+- **FBR exception**: FBR sideline dialogs forbid all tellask calls (including `tellaskBack` / `tellask` / `tellaskSessionless` / `askHuman`); they must list missing context and return.
 
 **Inter-dialog transfer and markers (normative)**:
 
@@ -259,9 +259,10 @@ flowchart TD
     - Regular completed sideline reply: `【Completed】`
     - FBR sideline reply: `【FBR-Direct Reply】` or `【FBR-Reasoning Only】`
   - Chinese work language:
-    - Ask-back reply: `【TellaskBack】`
-    - Regular completed sideline reply: `【Completed】`
-    - FBR sideline reply: `【FBR-Direct Reply】` or `【FBR-Reasoning Only】`
+    - Ask-back reply: `【回问诉请】`
+    - Regular completed sideline reply: `【最终完成】`
+    - FBR sideline reply: `【FBR-直接回复】` or `【FBR-仅推理】`
+- If the requester defines a “reply/delivery format” inside the tellask body, keep it to the business delivery structure; do not require responder-side hand-written markers, because runtime injects those markers automatically.
 - Source-dialog model raw is naturally preserved in source-dialog persistence; inter-dialog transfer must not rewrite or overwrite that source raw.
 - Template-wrapped transfer is allowed: a model output from one dialog may be embedded into a runtime template and sent as the body to another dialog.
 

package/dist/docs/dialog-system.zh.md

@@ -242,7 +242,7 @@ flowchart TD
 
 - 只有当所有目标完成时，支线对话才可直接正常回复诉请者对话。
 - 若任何目标未完成或关键信息缺失，必须先用 `tellaskBack({ tellaskContent: "..." })` 回问诉请者对话再继续。
-- **FBR 例外**：FBR 支线对话禁止任何诉请（包括 `tellaskBack`），只能列出缺口与阻塞原因并直接回复。
+- **FBR 例外**：FBR 支线对话禁止一切 tellask（包括 `tellaskBack` / `tellask` / `tellaskSessionless` / `askHuman`），只能列出缺口与阻塞原因并直接回复。
 
 **跨对话传递与标记（强制）**：
 
@@ -256,6 +256,7 @@ flowchart TD
     - 回问诉请回贴：`【TellaskBack】`
     - 常规支线完成回贴：`【Completed】`
     - FBR 回贴：`【FBR-Direct Reply】` 或 `【FBR-Reasoning Only】`
+- 若诉请方在正文中定义“回贴格式/交付格式”，只写业务交付结构即可；不得要求被诉请者手写任何标记，因为这些标记由运行时自动注入。
 - 源对话的模型原始输出（raw）天然保留在源对话持久记录中；跨对话传递不得改写或覆盖该源 raw。
 - 允许将“某对话的模型原文”拼接进运行时模板后，作为传递到另一对话的正文（即模板化传递是规范路径）。
 

package/dist/docs/fbr.md

@@ -126,7 +126,7 @@ If the model attempts any other tool/function call, runtime MUST hard-reject it
 
 ### 4.3 Tellask restriction: none allowed
 
-FBR sideline dialogs MUST NOT issue any teammate Tellasks (including `tellaskBack({ tellaskContent: "..." })` or `askHuman({ tellaskContent: "..." })`).
+FBR sideline dialogs MUST NOT issue any tellask call (including `tellaskBack({ tellaskContent: "..." })`, `tellask({ ... })`, `tellaskSessionless({ ... })`, or `askHuman({ tellaskContent: "..." })`).
 If critical context is missing, the FBR sideline should **list the missing items** and why they block reasoning, then return.
 
 ### 4.4 Output contract (easy to distill)

package/dist/docs/fbr.zh.md

@@ -122,7 +122,7 @@ FBR 支线对话的 system prompt 必须明确包含（措辞可不同，但语
 
 ### 4.3 诉请限制：一律禁止
 
-FBR 支线对话不得发起任何队友诉请（包括 `tellaskBack({ tellaskContent: "..." })` 或 `askHuman({ tellaskContent: "..." })`）。
+FBR 支线对话不得发起任何 tellask 调用（包括 `tellaskBack({ tellaskContent: "..." })`、`tellask({ ... })`、`tellaskSessionless({ ... })` 或 `askHuman({ tellaskContent: "..." })`）。
 若关键上下文缺失，应**列出缺口与阻塞原因**，然后直接回复。
 
 ### 4.4 输出契约（在 FBR 内部完成去噪）

package/dist/docs/mcp-support.md

@@ -423,9 +423,12 @@ servers:
     # Tool name transforms (optional)
     transform: []
 
-    # Optional per-toolset manual shown to agents
+    # Optional manual information
+    # - contentFile: formal runtime manual for man({ "toolsetId": "<serverId>" })
+    # - content/sections: extra inline team-management guidance
     # (missing manual does NOT make the toolset unavailable)
     manual:
+      contentFile: ".minds/manuals/<serverId>"
       content: "What this MCP toolset is for"
       sections:
         - title: "When To Use"

package/dist/docs/team_mgmt-toolset.md

@@ -385,15 +385,15 @@ Notes:
 - MCP tool names are global across all toolsets (built-in + MCP). Collisions cause tools to be
   skipped and should surface via Problems + logs.
 - `mcp_admin` is a built-in toolset that contains `mcp_restart` (best-effort per-server restart).
-- Optional per-toolset manual can live in `.minds/mcp.yaml` at `servers.<serverId>.manual` using:
-  - `content`: overview text
-  - `sections`: chapterized guidance (`[{ title, content }]` or `{ "<title>": "<content>" }`)
+- Optional manual information can live in `.minds/mcp.yaml` at `servers.<serverId>.manual`:
+  - `contentFile`: the topic-file directory prefix for the formal runtime manual; the final `man({ "toolsetId": "<serverId>" })` content shown to the LLM is loaded from here
+  - `content` / `sections`: inline team-management guidance shown in the `team_mgmt` MCP chapter (`sections` supports `[{ title, content }]` or `{ "<title>": "<content>" }`)
 - Missing manual does **not** mean the toolset is unavailable; it means team-manager documentation
   is incomplete. Agents should continue by reading each tool’s own description/arguments.
 - Team-manager recommendation: after MCP config validation passes, carefully read each exposed tool
-  description, discuss intended rtws usage with the human user, then write
-  `servers.<serverId>.manual` that captures typical usage patterns, primary intent directions, and
-  unavailable-case business handling rules.
+  description, discuss intended rtws usage with the human user, then write the formal manual into
+  `manual.contentFile`; if extra team-management interpretation is still useful, add inline
+  `content + sections` alongside it.
 - Use a semi-structured chapter shape: high-value sections often include `When To Use`,
   `Guardrails`, and `Business Handling When Unavailable`, but do not force every toolset into one
   fixed template. Start from the real business goal, then decide which sections deserve depth,
@@ -431,8 +431,9 @@ servers:
     # Tool name transforms
     transform: [] # optional
 
-    # Optional toolset manual for agents
+    # Optional manual information
     manual:
+      contentFile: ".minds/manuals/<serverId>" # formal runtime manual for man({ "toolsetId": "<serverId>" })
       content: "What this MCP toolset is for"
       sections:
         - title: "When To Use"

package/dist/docs/team_mgmt-toolset.zh.md

@@ -322,11 +322,11 @@ members:
 
 - MCP 工具名称在所有工具集（内置 + MCP）中是全局的。冲突导致工具被跳过，应通过问题 + 日志暴露
 - `mcp_admin` 是一个内置工具集，包含 `mcp_restart`（每个服务器最佳努力重启）
-- 可选手册：可在 `.minds/mcp.yaml` 的 `servers.<serverId>.manual` 为每个 MCP toolset 提供手册：
-  - `content`：总说明
-  - `sections`：章节化指导（`[{ title, content }]` 或 `{ "<title>": "<content>" }`）
+- 可选手册：可在 `.minds/mcp.yaml` 的 `servers.<serverId>.manual` 提供手册相关信息：
+  - `contentFile`：正式 runtime 手册的 topic 文件目录前缀；`man({ "toolsetId": "<serverId>" })` 最终给 LLM 看的正文从这里加载
+  - `content` / `sections`：补充给 `team_mgmt` MCP 章节看的 inline 团队管理说明（`sections` 支持 `[{ title, content }]` 或 `{ "<title>": "<content>" }`）
 - 没有手册 **不代表** 该 toolset 不可用；这只表示团队管理文档覆盖不足。智能体应继续依据每个工具自身的 description/参数来使用。
-- 建议团队管理者在 MCP 配置验证通过后：先精读该 server 暴露的每个工具说明，再与人类用户讨论本 rtws 的使用意图，最后把“典型用法 + 主要意图方向 + 不可用时业务处置规约”沉淀为 `servers.<serverId>.manual`。
+- 建议团队管理者在 MCP 配置验证通过后：先精读该 server 暴露的每个工具说明，再与人类用户讨论本 rtws 的使用意图，然后把正式手册沉淀到 `manual.contentFile`；如仍需额外写团队管理层解释，再补 inline `content + sections`。
 - 章节组织建议采用“半结构化”：可优先考虑 `何时使用`、`安全边界`、`不可用时业务处置` 这类高价值章节，但不要求所有 toolset 都照抄同一模板。应从真实业务目标出发，决定哪些章节需要展开、哪些只需一句话、哪些可以合并或改名成更贴切的标题。
 - 对每个 MCP toolset，建议刻意写明“不可用时业务处置规约”，至少回答：
   - 当前 toolset 暂不可达时，是否必须找协调者/专员接手
@@ -360,8 +360,9 @@ servers:
     # 工具名称转换
     transform: [] # 可选
 
-    # 可选：给智能体看的 toolset 手册
+    # 可选：手册相关信息
     manual:
+      contentFile: ".minds/manuals/<serverId>" # 正式 runtime 手册（供 man({ "toolsetId": "<serverId>" }) 读取）
       content: "该 MCP toolset 的用途说明"
       sections:
         - title: "何时使用"

package/dist/docs/tellask-collab.md

@@ -109,19 +109,19 @@ That is a workflow break. The model should send the Tellask directly.
     - Regular completed sideline reply: `【Completed】`
     - FBR reply: `【FBR-Direct Reply】` or `【FBR-Reasoning Only】`
   - Chinese work language:
-    - Ask-back reply: `【TellaskBack】`
-    - Regular completed sideline reply: `【Completed】`
-    - FBR reply: `【FBR-Direct Reply】` or `【FBR-Reasoning Only】`
-- If the requester defines a “reply format” in tellask body, it must explicitly say “no hand-written markers; Dominds auto-injects markers”; do not require responder-side hand-written markers.
+    - Ask-back reply: `【回问诉请】`
+    - Regular completed sideline reply: `【最终完成】`
+    - FBR reply: `【FBR-直接回复】` or `【FBR-仅推理】`
+- If the requester defines a “reply/delivery format” in tellask body, keep it to the business delivery structure; do not require responder-side hand-written markers, because Dominds runtime injects those markers automatically.
 - Source-dialog model raw is naturally preserved in source-dialog persistence; inter-dialog transfer must not rewrite or overwrite that source raw.
 - Template-wrapped transfer is allowed: model output from one dialog can be embedded into a runtime template and sent as another dialog body.
 
 **Sideline delivery rule**:
 
 - If a sideline dialog has completed all goals and can deliver the final result, it MUST reply directly with the response body; do not use `tellaskBack` to send final delivery.
-- Runtime treats that direct reply as the completion delivery to the tellasker dialog and injects the work-language marker automatically (`【Completed】` in English work language, and the localized Chinese completion marker in Chinese work language).
+- Runtime treats that direct reply as the completion delivery to the tellasker dialog and injects the work-language marker automatically (`【Completed】` in English work language, `【最终完成】` in Chinese work language).
 - If any goal is incomplete, the dialog is blocked, or critical context is missing, it MUST issue `tellaskBack({ tellaskContent: "..." })` before proceeding; do not post plain-text intermediate status updates while unfinished.
-- **FBR exception**: FBR forbids all tellasks (including `tellaskBack` / `askHuman`); list missing context + reasoning and return.
+- **FBR exception**: FBR forbids all tellask calls (including `tellaskBack` / `tellask` / `tellaskSessionless` / `askHuman`); list missing context + reasoning and return.
 - If a human user inserts a message or asks a follow-up in the sideline: just reply normally; no need to report back to the upstream requester.
 
 Note: no extra "Status: ..." line is required; the first-line marker is the stage reminder.

package/dist/docs/tellask-collab.zh.md

@@ -109,7 +109,7 @@
     - 回问诉请回贴：`【TellaskBack】`
     - 常规支线完成回贴：`【Completed】`
     - FBR 回贴：`【FBR-Direct Reply】` 或 `【FBR-Reasoning Only】`
-- 若诉请方在正文中定义“回贴格式”，必须写明“禁止手写标记，由 Dominds 自动注入”；不得要求被诉请者手写任何标记。
+- 若诉请方在正文中定义“回贴格式/交付格式”，只写业务交付结构即可；不得要求被诉请者手写任何标记，这些标记由 Dominds 运行时自动注入。
 - 源对话模型原始输出（raw）天然保留在源对话持久记录中；跨对话传递不得改写或覆盖该源 raw。
 - 允许将“某对话的模型原文”拼接进运行时模板后，作为传递到另一对话的正文（模板化传递是规范路径）。
 
@@ -117,7 +117,7 @@
 
 - 只有当所有目标完成时，支线对话才可直接正常回复诉请者对话（直接发正文即可，不需要调用 tellaskBack；运行时自动注入完成标记）。
 - 若任何目标未完成或关键信息缺失，必须先用 `tellaskBack({ tellaskContent: "..." })` 回问诉请者对话再继续；不得发送普通文本中间汇报。
-- **FBR 例外**：FBR 禁止任何诉请（包括 `tellaskBack` / `askHuman`）；只列缺口 + 推理与摘要并直接回复。
+- **FBR 例外**：FBR 禁止一切 tellask（包括 `tellaskBack` / `tellask` / `tellaskSessionless` / `askHuman`）；只列缺口 + 推理与摘要并直接回复。
 - 若人类用户在支线对话中插入消息或补问：直接正常回复，不需要向诉请者汇报。
 
 说明：不需要额外的 “Status: …” 行；首行标记即为阶段提醒。

package/dist/mcp/manual-problems.d.ts

@@ -0,0 +1,33 @@
+export type McpToolsetManualSection = {
+    title: string;
+    content: string;
+};
+export type McpToolsetManual = {
+    content?: string;
+    contentFile?: string;
+    sections: ReadonlyArray<McpToolsetManualSection>;
+};
+export type McpToolsetManualState = {
+    kind: 'missing';
+} | {
+    kind: 'invalid';
+    errorText: string;
+} | {
+    kind: 'present';
+    manual: McpToolsetManual;
+};
+export type McpToolsetManualByServer = {
+    manualByServerId: ReadonlyMap<string, McpToolsetManual>;
+    invalidByServerId: ReadonlyMap<string, string>;
+    warningTextByServerId: ReadonlyMap<string, string>;
+};
+export declare function emptyMcpToolsetManualByServer(): McpToolsetManualByServer;
+export declare function mcpToolsetManualProblemPrefix(serverId: string): string;
+export declare function mcpWorkspaceManualProblemPrefix(): string;
+export declare function parseMcpManualByServer(rawText: string): McpToolsetManualByServer;
+export declare function reconcileMcpToolsetManualProblems(params: {
+    serverIds: ReadonlyArray<string>;
+    manualInfo: McpToolsetManualByServer;
+    measureRenderedWorkspaceMcpTopicRawChars: () => Promise<number>;
+    workspaceManualPath: string;
+}): Promise<void>;