dominds 1.19.3 → 1.20.2

package/dist/runtime/driver-messages.d.ts

@@ -24,12 +24,15 @@ export declare function formatDomindsNoteTellaskForTeammatesOnly(language: Langu
 export declare function formatDomindsNoteQ4HRegisterFailed(language: LanguageCode, args: {
     error: string;
 }): string;
+export type ContextHealthV3RemediationDialogScope = 'mainDialog' | 'sideDialog';
 export type ContextHealthV3RemediationGuideArgs = {
     kind: 'caution';
     mode: 'soft';
+    dialogScope: ContextHealthV3RemediationDialogScope;
 } | {
     kind: 'critical';
     mode: 'countdown';
+    dialogScope: ContextHealthV3RemediationDialogScope;
     promptsRemainingAfterThis: number;
     promptsTotal: number;
 };

package/dist/runtime/driver-messages.js

@@ -372,8 +372,28 @@ function formatDomindsNoteQ4HRegisterFailed(language, args) {
         `- Next: retry; if this keeps failing, delete the dialog's \`q4h.yaml\` (will drop pending questions) or check server logs.`);
 }
 function formatAgentFacingContextHealthV3RemediationGuide(language, args) {
+    const isSideDialog = args.dialogScope === 'sideDialog';
     if (language === 'zh') {
         if (args.kind === 'caution' && args.mode === 'soft') {
+            if (isSideDialog) {
+                return [
+                    `${formatSystemNoticePrefix(language)} 上下文状态：🟡 吃紧`,
+                    '',
+                    '这是一条运行时处置指令，不是新的用户诉求；不要只回复“收到/好的/我先整理提醒项”，而要直接执行下面的处置动作。',
+                    '',
+                    '影响：对话历史中的工具调用/结果信息很多已经过时，成为你的思考负担。',
+                    '',
+                    '行动：你当前处于支线对话。本程不要维护差遣牒，也不要整理差遣牒更新提案；当前目标是维护足够详尽的接续包提醒项，然后主动 clear_mind 开启新一程继续工作。',
+                    '',
+                    '提醒项应覆盖：当前对话历史中下一程需要知道的讨论细节、下一步行动、关键定位信息、运行/验证信息、临时路径/ID/样例输入，以及任何恢复工作容易丢的判断依据。提醒项长度没有技术限制，宁可完整一些；允许写成多条粗略提醒项，不必在当前程强行压成单条。',
+                    '',
+                    '当前已处于吃紧处置阶段：不要继续扩张上下文，也不要提前进入“按接续包做清醒复核”的模式；真正清理冗余、合并提醒项，放到系统开启新一程后再做。',
+                    '',
+                    '操作：',
+                    '- 优先新增详尽接续包提醒项：add_reminder({ "content": "..." })',
+                    '- 只有在确实能就地复用现有提醒项、且不会额外增加当前程认知负担时，才更新：update_reminder({ "reminder_id": "<现有 reminder_id>", "content": "..." })',
+                ].join('\n');
+            }
             return [
                 `${formatSystemNoticePrefix(language)} 上下文状态：🟡 吃紧`,
                 '',
@@ -381,15 +401,36 @@ function formatAgentFacingContextHealthV3RemediationGuide(language, args) {
                 '',
                 '影响：对话历史中的工具调用/结果信息很多已经过时，成为你的思考负担。',
                 '',
-                '行动：先尽量保住易丢信息。当前处于吃紧处置阶段时，优先把已经掌握的事实直接记进新提醒项过桥（下一步行动 + 关键定位信息 + 运行/验证信息 + 容易丢的临时细节）；允许先带着一定冗余，也允许先写成多条粗略提醒项，不必在当前程强行压成单条。',
+                '行动：你当前处于主线对话。先把当前对话历史中尚未落实到文档、且下一程需要知会的讨论细节落到差遣牒合适章节。然后再把差遣牒仍未覆盖、但恢复工作会丢的信息记进新提醒项过桥（下一步行动 + 关键定位信息 + 运行/验证信息 + 容易丢的临时细节）；允许先带着一定冗余，也允许先写成多条粗略提醒项，不必在当前程强行压成单条。',
                 '',
-                '当前已处于吃紧处置阶段：不要继续扩张上下文，也不要提前进入“按接续包做清醒复核”的模式；那是系统真正开启新一程后的第一步。当前程的目标是先把差遣牒未覆盖、但恢复工作会丢的信息带过桥；真正清理冗余、合并提醒项，放到新一程再做。然后主动 clear_mind，开启新一程对话继续工作。',
+                '当前已处于吃紧处置阶段：不要继续扩张上下文，也不要提前进入“按接续包做清醒复核”的模式；那是系统真正开启新一程后的第一步。当前程的目标是先把未落文档的讨论细节补进差遣牒，再把差遣牒仍未覆盖、但恢复工作会丢的信息带过桥；真正清理冗余、合并提醒项，放到新一程再做。然后主动 clear_mind，开启新一程对话继续工作。',
                 '',
                 '操作：',
+                '- 先写差遣牒：mind_more({ "items": ["..."] })；需要删旧/重排/压缩时改用 change_mind({ ... })',
                 '- 优先新增过桥提醒项：add_reminder({ "content": "..." })',
                 '- 只有在确实能就地复用现有提醒项、且不会额外增加当前程认知负担时，才更新：update_reminder({ "reminder_id": "<现有 reminder_id>", "content": "..." })',
             ].join('\n');
         }
+        if (isSideDialog) {
+            return [
+                `${formatSystemNoticePrefix(language)} 上下文状态：🔴 告急`,
+                '',
+                '这是一条运行时处置指令，不是新的用户诉求；不要只回复“收到/好的/我先整理提醒项”，而要直接执行下面的处置动作。',
+                '',
+                `系统最多再提醒你 ${args.promptsRemainingAfterThis} 次，之后将自动清理头脑开启新一程对话。`,
+                '',
+                '行动：你当前处于支线对话。本程不要维护差遣牒，也不要整理差遣牒更新提案；当前目标是尽快维护足够详尽的接续包提醒项，然后 clear_mind。',
+                '',
+                '提醒项应覆盖：当前对话历史中下一程需要知道的讨论细节、下一步行动、关键定位信息、运行/验证信息、临时路径/ID/样例输入，以及任何恢复工作容易丢的判断依据。提醒项长度没有技术限制，宁可完整一些；允许写成多条粗略提醒项，甚至带一定冗余也可以，不必在当前程强行整理干净。',
+                '',
+                '操作：',
+                '- 优先新增详尽接续包提醒项：add_reminder({ "content": "..." })',
+                '- 只有在确实能就地复用现有提醒项、且不会额外增加当前程认知负担时，才更新：update_reminder({ "reminder_id": "<现有 reminder_id>", "content": "..." })',
+                '- clear_mind({})',
+                '',
+                '当前处于告急处置阶段时，不要提前做“新一程清醒复核”；系统真正开启新一程后，第一步才是重新审视并整理：删除冗余、纠正偏激/失真思路、合并并压缩成高质量提醒项。',
+            ].join('\n');
+        }
         return [
             `${formatSystemNoticePrefix(language)} 上下文状态：🔴 告急`,
             '',
@@ -397,17 +438,37 @@ function formatAgentFacingContextHealthV3RemediationGuide(language, args) {
             '',
             `系统最多再提醒你 ${args.promptsRemainingAfterThis} 次，之后将自动清理头脑开启新一程对话。`,
             '',
-            '行动：尽快保住易丢信息，然后 clear_mind。当前处于告急处置阶段时，优先直接新增提醒项把事实带过桥；允许先保留多条粗略提醒项，甚至带一定冗余也可以，不必在当前程强行整理干净。',
+            '行动：你当前处于主线对话。尽快保住易丢信息，然后 clear_mind。当前处于告急处置阶段时，先把当前对话历史中尚未落实到文档、且下一程需要知会的讨论细节落到差遣牒合适章节。然后再把差遣牒仍未覆盖、但恢复工作会丢的信息新增提醒项带过桥；允许先保留多条粗略提醒项，甚至带一定冗余也可以，不必在当前程强行整理干净。',
             '',
             '操作：',
+            '- 先写差遣牒：mind_more({ "items": ["..."] })；需要删旧/重排/压缩时改用 change_mind({ ... })',
             '- 优先新增过桥提醒项：add_reminder({ "content": "..." })',
             '- 只有在确实能就地复用现有提醒项、且不会额外增加当前程认知负担时，才更新：update_reminder({ "reminder_id": "<现有 reminder_id>", "content": "..." })',
             '- clear_mind({})',
             '',
-            '接续包要点：下一步行动 + 关键定位信息 + 运行验证方式 + 容易丢的临时细节；不要重复差遣牒已有内容。当前处于告急处置阶段时，不要提前做“新一程清醒复核”；系统真正开启新一程后，第一步才是重新审视并整理：删除冗余、纠正偏激/失真思路、合并并压缩成高质量提醒项。',
+            '接续包要点：下一步行动 + 关键定位信息 + 运行验证方式 + 容易丢的临时细节；不要重复差遣牒已有内容，本程刚落入差遣牒的讨论细节只需提示下一程先查差遣牒。当前处于告急处置阶段时，不要提前做“新一程清醒复核”；系统真正开启新一程后，第一步才是重新审视并整理：删除冗余、纠正偏激/失真思路、合并并压缩成高质量提醒项。',
         ].join('\n');
     }
     if (args.kind === 'caution' && args.mode === 'soft') {
+        if (isSideDialog) {
+            return [
+                `${formatSystemNoticePrefix(language)} Context state: 🟡 caution`,
+                '',
+                'This is a runtime remediation instruction, not a new user request; do not reply with a standalone "acknowledged/ok/I will organize reminders first", and instead perform the remediation actions directly.',
+                '',
+                'Impact: stale call/results in dialog history are creating cognitive noise.',
+                '',
+                'Action: you are in a Side Dialog. Do not maintain Taskdoc in this course, and do not draft Taskdoc update proposals. The current goal is to maintain sufficiently detailed continuation-package reminders, then proactively clear_mind to start a new dialog course.',
+                '',
+                'Reminders should cover: discussion details from current dialog history that the next course needs to know, next actions, key pointers, run/verify info, volatile paths/IDs/sample inputs, and any reasoning needed to resume safely. Reminder length has no technical limit, so prefer being complete; rough multi-reminder carry-over is acceptable, and you do not need to force everything into one clean reminder in the current course.',
+                '',
+                'You are already in caution remediation for the current course, so do not keep expanding context and do not switch early into “clear-headed continuation-package review” mode; reminder cleanup and dedup belong to the new course.',
+                '',
+                'Operations:',
+                '- Prefer adding a detailed continuation-package reminder first: add_reminder({ "content": "..." })',
+                '- Only if an existing reminder is clearly the right place, and updating it would not add extra cognitive load in the current course: update_reminder({ "reminder_id": "<existing reminder_id>", "content": "..." })',
+            ].join('\n');
+        }
         return [
             `${formatSystemNoticePrefix(language)} Context state: 🟡 caution`,
             '',
@@ -415,15 +476,36 @@ function formatAgentFacingContextHealthV3RemediationGuide(language, args) {
             '',
             'Impact: stale call/results in dialog history are creating cognitive noise.',
             '',
-            'Action: first preserve easy-to-lose information. In caution remediation, prefer writing already observed facts into new bridge reminders directly (next step + key pointers + run/verify info + easy-to-lose volatile details). Some redundancy is acceptable, and rough multi-reminder carry-over is acceptable too; do not force everything into one clean reminder in the current course.',
+            'Action: you are in the Main Dialog. First record current-dialog discussion details that are not yet documented but the next course needs to know into the appropriate Taskdoc sections. Then write information still not covered by Taskdoc but easy to lose into new bridge reminders (next step + key pointers + run/verify info + easy-to-lose volatile details). Some redundancy is acceptable, and rough multi-reminder carry-over is acceptable too; do not force everything into one clean reminder in the current course.',
             '',
-            'You are already in caution remediation for the current course, so do not keep expanding context and do not switch early into “clear-headed continuation-package review” mode; that is the first step only after the system actually starts the new course. In the current course, the goal is to carry forward details not already covered by Taskdoc; reminder cleanup and dedup belong to the new course. Then proactively clear_mind to start a new dialog course.',
+            'You are already in caution remediation for the current course, so do not keep expanding context and do not switch early into “clear-headed continuation-package review” mode; that is the first step only after the system actually starts the new course. In the current course, the goal is to first fill Taskdoc with undocumented discussion details, then carry forward details still not covered by Taskdoc; reminder cleanup and dedup belong to the new course. Then proactively clear_mind to start a new dialog course.',
             '',
             'Operations:',
+            '- First write Taskdoc: mind_more({ "items": ["..."] }); use change_mind({ ... }) instead when deletion/reordering/compression is needed',
             '- Prefer adding a bridge reminder first: add_reminder({ "content": "..." })',
             '- Only if an existing reminder is clearly the right place, and updating it would not add extra cognitive load in the current course: update_reminder({ "reminder_id": "<existing reminder_id>", "content": "..." })',
         ].join('\n');
     }
+    if (isSideDialog) {
+        return [
+            `${formatSystemNoticePrefix(language)} Context state: 🔴 critical`,
+            '',
+            'This is a runtime remediation instruction, not a new user request; do not reply with a standalone "acknowledged/ok/I will organize reminders first", and instead perform the remediation actions directly.',
+            '',
+            `System will remind you ${args.promptsRemainingAfterThis} more time(s), then automatically clear mind.`,
+            '',
+            'Action: you are in a Side Dialog. Do not maintain Taskdoc in this course, and do not draft Taskdoc update proposals. The current goal is to maintain sufficiently detailed continuation-package reminders as soon as possible, then clear_mind.',
+            '',
+            'Reminders should cover: discussion details from current dialog history that the next course needs to know, next actions, key pointers, run/verify info, volatile paths/IDs/sample inputs, and any reasoning needed to resume safely. Reminder length has no technical limit, so prefer being complete; multiple rough reminders, including some redundancy, are acceptable as a bridge.',
+            '',
+            'Operations:',
+            '- Prefer adding a detailed continuation-package reminder first: add_reminder({ "content": "..." })',
+            '- Only if an existing reminder is clearly the right place, and updating it would not add extra cognitive load in the current course: update_reminder({ "reminder_id": "<existing reminder_id>", "content": "..." })',
+            '- clear_mind({})',
+            '',
+            'During critical remediation in the current course, do not start the new-course cleanup early; once the system actually starts the new course, the first step is to reconcile rough bridge reminders by removing redundancy, correcting biased or distorted bridge notes, and merging/compressing them into high-quality reminders.',
+        ].join('\n');
+    }
     return [
         `${formatSystemNoticePrefix(language)} Context state: 🔴 critical`,
         '',
@@ -431,14 +513,15 @@ function formatAgentFacingContextHealthV3RemediationGuide(language, args) {
         '',
         `System will remind you ${args.promptsRemainingAfterThis} more time(s), then automatically clear mind.`,
         '',
-        'Action: preserve easy-to-lose information, then clear_mind. In critical remediation, prefer adding bridge reminders directly. Multiple rough reminders, including some redundancy, are acceptable as a bridge; do not spend the current course forcing them into a clean final package.',
+        'Action: you are in the Main Dialog. Preserve easy-to-lose information, then clear_mind. In critical remediation, first record current-dialog discussion details that are not yet documented but the next course needs to know into the appropriate Taskdoc sections. Then add bridge reminders for information still not covered by Taskdoc but easy to lose. Multiple rough reminders, including some redundancy, are acceptable as a bridge; do not spend the current course forcing them into a clean final package.',
         '',
         'Operations:',
+        '- First write Taskdoc: mind_more({ "items": ["..."] }); use change_mind({ ... }) instead when deletion/reordering/compression is needed',
         '- Prefer adding a bridge reminder first: add_reminder({ "content": "..." })',
         '- Only if an existing reminder is clearly the right place, and updating it would not add extra cognitive load in the current course: update_reminder({ "reminder_id": "<existing reminder_id>", "content": "..." })',
         '- clear_mind({})',
         '',
-        'Continuation package: next step + key pointers + run/verify info + easy-to-lose volatile details. Do not duplicate Taskdoc content. During critical remediation in the current course, do not start the new-course cleanup early; once the system actually starts the new course, the first step is to reconcile rough bridge reminders by removing redundancy, correcting biased or distorted bridge notes, and merging/compressing them into high-quality reminders.',
+        'Continuation package: next step + key pointers + run/verify info + easy-to-lose volatile details. Do not duplicate Taskdoc content; for discussion details just written into Taskdoc in this course, only remind the next course to review Taskdoc first. During critical remediation in the current course, do not start the new-course cleanup early; once the system actually starts the new course, the first step is to reconcile rough bridge reminders by removing redundancy, correcting biased or distorted bridge notes, and merging/compressing them into high-quality reminders.',
     ].join('\n');
 }
 function formatDomindsNoteDirectSelfCall(language) {

package/dist/server/setup-routes.js

@@ -20,7 +20,6 @@ const log = (0, log_1.createLogger)('setup-routes');
 const TEAM_YAML_PATH = path_1.default.join('.minds', 'team.yaml');
 const RTWS_LLM_YAML_PATH = path_1.default.join('.minds', 'llm.yaml');
 const RTWS_ENV_LOCAL_PATH = '.env.local';
-const BUILTIN_DEFAULTS_YAML_PATH = path_1.default.join(__dirname, '..', 'llm', 'defaults.yaml');
 const DOMINDS_ENV_BLOCK_START = '# >>> dominds env >>>';
 const DOMINDS_ENV_BLOCK_END = '# <<< dominds env <<<';
 async function buildSetupStatusResponse() {
@@ -85,15 +84,16 @@ async function buildSetupStatusResponse() {
 }
 async function buildSetupFileResponse(kind) {
     if (kind === 'defaults_yaml') {
+        const builtinDefaultsYamlPath = (0, client_1.getBuiltinDefaultsYamlPath)();
         try {
-            const raw = await promises_1.default.readFile(BUILTIN_DEFAULTS_YAML_PATH, 'utf-8');
-            return { success: true, kind, path: BUILTIN_DEFAULTS_YAML_PATH, raw };
+            const raw = await (0, client_1.readBuiltinDefaultsYamlRaw)();
+            return { success: true, kind, path: builtinDefaultsYamlPath, raw };
         }
         catch {
             return {
                 success: false,
                 kind,
-                path: BUILTIN_DEFAULTS_YAML_PATH,
+                path: builtinDefaultsYamlPath,
                 error: 'Failed to read defaults.yaml',
             };
         }
@@ -260,7 +260,7 @@ async function handleWriteRtwsLlmYaml(rawBody) {
 }
 async function loadBuiltinProviders() {
     try {
-        const raw = await promises_1.default.readFile(BUILTIN_DEFAULTS_YAML_PATH, 'utf-8');
+        const raw = await (0, client_1.readBuiltinDefaultsYamlRaw)();
         const doc = yaml_1.default.parseDocument(raw);
         const parsed = doc.toJS();
         if (!isRecord(parsed) || !isRecord(parsed.providers)) {

package/dist/tool.d.ts

@@ -87,10 +87,18 @@ export declare function getReminderOwnerName(reminder: Pick<Reminder, 'owner'>):
 export declare function reminderOwnedBy(reminder: Reminder, owner: ReminderOwner | string): boolean;
 export type ReminderTreatment = 'drop' | 'keep' | 'update';
 export type ReminderUpdateResult = KernelReminderUpdateResult;
+export type ReminderWakeEvent = Readonly<{
+    eventId: string;
+    reminderId: string;
+    content: string;
+    updatedContent?: string;
+    updatedMeta?: JsonValue;
+}>;
 export interface ReminderOwner {
     readonly name: string;
     updateReminder(dlg: Dialog, reminder: Reminder): Promise<ReminderUpdateResult>;
     renderReminder(dlg: Dialog, reminder: Reminder): Promise<ChatMessage>;
+    waitForReminderWakeEvent?(dlg: Dialog, reminders: readonly Reminder[], signal: AbortSignal): Promise<ReminderWakeEvent | readonly ReminderWakeEvent[] | null>;
 }
 export declare function validateArgs(schema: JsonSchema, args: unknown): {
     ok: true;

package/dist/tools/builtins.js

@@ -97,6 +97,7 @@ function manualSpecFor(toolsetId) {
 (0, registry_1.registerTool)(ctrl_1.updateReminderTool);
 (0, registry_1.registerTool)(ctrl_1.clearMindTool);
 (0, registry_1.registerTool)(ctrl_1.changeMindTool);
+(0, registry_1.registerTool)(ctrl_1.mindMoreTool);
 (0, registry_1.registerTool)(ctrl_1.recallTaskdocTool);
 // Team management tools (scoped to `.minds/**`)
 for (const tool of team_mgmt_1.teamMgmtTools) {
@@ -139,13 +140,14 @@ for (const tool of team_mgmt_1.teamMgmtTools) {
     ctrl_1.updateReminderTool,
     ctrl_1.clearMindTool,
     ctrl_1.changeMindTool,
+    ctrl_1.mindMoreTool,
     ctrl_1.recallTaskdocTool,
 ]);
 (0, registry_1.setToolsetMeta)('control', {
     source: 'dominds',
     descriptionI18n: {
-        en: 'Dialog control: manage reminders, Taskdoc sections, and course resets via clear_mind/change_mind.',
-        zh: '对话控制：维护提醒项、差遣牒分段，并通过 clear_mind/change_mind 管理对话进程。',
+        en: 'Dialog control: manage reminders, Taskdoc sections, and course resets.',
+        zh: '对话控制：维护提醒项、差遣牒分段，并管理对话进程重置。',
     },
     promptFilesI18n: promptFilesFor('control'),
     manualSpec: manualSpecFor('control'),

package/dist/tools/ctrl.d.ts

@@ -14,6 +14,7 @@
  * - update_reminder: Update reminder content
  * - clear_mind: Start a new course, optionally add a reminder
  * - change_mind: Update a `.tsk/` Taskdoc section without starting a new course
+ * - mind_more: Append entries to a `.tsk/` Taskdoc section without starting a new course
  * - recall_taskdoc: Read a Taskdoc section from `*.tsk/` by (category, selector)
  *
  * USAGE CONTEXT:
@@ -31,4 +32,5 @@ export declare const addReminderTool: FuncTool;
 export declare const updateReminderTool: FuncTool;
 export declare const clearMindTool: FuncTool;
 export declare const changeMindTool: FuncTool;
+export declare const mindMoreTool: FuncTool;
 export declare const recallTaskdocTool: FuncTool;