dominds 1.20.1 → 1.20.2

package/dist/llm/defaults.yaml

@@ -102,13 +102,13 @@ providers:
     models:
       gpt-5.5:
         name: GPT-5.5
-        optimal_max_tokens: 350000
+        optimal_max_tokens: 200000
         # Caution remediation reinjection cadence in generation turns (default: 10).
         caution_remediation_cadence_generations: 10
-        context_length: 400000
+        context_length: 272000
         input_length: 272000
-        output_length: 128000
-        context_window: '400K'
+        output_length: 32768
+        context_window: '272K'
       gpt-5.4:
         name: GPT-5.4
         optimal_max_tokens: 200000
@@ -871,13 +871,13 @@ providers:
     models:
       gpt-5.5:
         name: GPT-5.5
-        optimal_max_tokens: 350000
+        optimal_max_tokens: 200000
         # Caution remediation reinjection cadence in generation turns (default: 10).
         caution_remediation_cadence_generations: 10
-        context_length: 1000000
-        input_length: 1000000
-        output_length: 128000
-        context_window: '1M'
+        context_length: 272000
+        input_length: 272000
+        output_length: 32768
+        context_window: '272K'
       gpt-5.5-pro:
         name: GPT-5.5 Pro
         optimal_max_tokens: 600000

package/dist/llm/gen/failure-classifier.js

@@ -234,6 +234,25 @@ function isOpenAiLikeRejectedFailure(error) {
     const status = readErrorStatus(error);
     return isHighConfidenceRejectedStatus(status);
 }
+function isOpenAiLikeContextWindowRejectedFailure(args) {
+    if (args.lowerCode === 'context_length_exceeded') {
+        return true;
+    }
+    if (args.lowerMessage.includes('context window') &&
+        (args.lowerMessage.includes('exceeds') || args.lowerMessage.includes('exceeded'))) {
+        return true;
+    }
+    if (args.lowerMessage.includes('context limit exceeded')) {
+        return true;
+    }
+    if (args.lowerMessage.includes('maximum context length')) {
+        return true;
+    }
+    if (args.lowerMessage.includes('context_length_exceeded')) {
+        return true;
+    }
+    return args.lowerMessage.includes('too many tokens') && args.lowerMessage.includes('context');
+}
 function isOpenAiLikeRateLimitFailure(error) {
     const lowerMessage = buildFailureMessage(error).toLowerCase();
     const status = readErrorStatus(error);
@@ -267,7 +286,9 @@ function classifyOpenAiLikeFailure(error) {
     const lowerMessage = message.toLowerCase();
     const status = readErrorStatus(error);
     const code = readErrorCode(error);
-    if (isOpenAiLikeRejectedFailure(error)) {
+    const lowerCode = typeof code === 'string' ? code.trim().toLowerCase() : undefined;
+    if (isOpenAiLikeRejectedFailure(error) ||
+        isOpenAiLikeContextWindowRejectedFailure({ lowerMessage, lowerCode })) {
         return {
             kind: 'rejected',
             message,

package/dist/persistence.js

@@ -4709,7 +4709,7 @@ class DialogPersistence {
             genseq,
             content,
         };
-        await this.appendEvent(dialog.id, course, ev, dialog.status);
+        await this.appendEvent(dialog.id, course, attachRootGenerationRef(dialog, ev), dialog.status);
     }
     /**
      * Capture the current byte offset of a course JSONL file.

package/dist/tools/ctrl.js

@@ -371,7 +371,7 @@ function getCtrlMessages(language) {
             tooManyArgsChangeMind: '参数格式不对。用法：change_mind({ selector: string, category?: string, content: string })',
             invalidFormatMindMore: '参数格式不对。用法：mind_more({ items: string[], sep?: string, selector?: string, category?: string })（selector 默认 progress）',
             mindMoreItemsRequired: '需要提供要追加的条目（items），且每一项都必须是非空字符串。\n' +
-                '示例：mind_more({"items":["- 下一步：复核验证结果","- 阻塞：无"]})',
+                '示例：mind_more({"items":["- 下一步：复核验证结果（详见 <文档路径>#<章节>）","- 阻塞：等待 API 验收口径确认"]})',
             invalidFormatRecallTaskdoc: '参数格式不对。用法：recall_taskdoc({ category: string, selector: string })',
             taskDocContentRequired: '需要提供差遣牒内容（content）。\n' +
                 '示例：\n' +
@@ -408,7 +408,7 @@ function getCtrlMessages(language) {
         tooManyArgsChangeMind: 'Error: Invalid args. Use: change_mind({ selector: string, category?: string, content: string })',
         invalidFormatMindMore: 'Error: Invalid args. Use: mind_more({ items: string[], sep?: string, selector?: string, category?: string }) (selector defaults to progress).',
         mindMoreItemsRequired: 'Error: items are required, and every item must be a non-empty string.\n' +
-            'Example: mind_more({"items":["- Next: review verification results","- Blocker: none"]})',
+            'Example: mind_more({"items":["- Next: review verification results (details: <doc-path>#<section>)","- Blocker: API acceptance criteria pending"]})',
         invalidFormatRecallTaskdoc: 'Error: Invalid args. Use: recall_taskdoc({ category: string, selector: string })',
         taskDocContentRequired: 'Error: Taskdoc content is required (content).\n' +
             'Copy/paste example:\n' +
@@ -1016,6 +1016,7 @@ exports.recallTaskdocTool = {
                 ? `\n\n⚠️ 已截断：内容过大（${bytes} bytes），仅回显前 ${maxSize} bytes。`
                 : `\n\n⚠️ Truncated: content is too large (${bytes} bytes); showing first ${maxSize} bytes.`
             : '';
-        return (0, tool_1.toolSuccess)(`**recall_taskdoc:** \`${relPath}\`\n\n---\n${clipped}\n---${note}`);
+        const closingSeparatorPrefix = clipped.endsWith('\n') ? '' : '\n';
+        return (0, tool_1.toolSuccess)(`**recall_taskdoc:** \`${relPath}\`\n\n---\n${clipped}${closingSeparatorPrefix}---${note}`);
     },
 };

package/dist/tools/prompts/control/en/principles.md

@@ -77,6 +77,8 @@ Taskdoc is a **task contract** and the task's **team-shared source of current tr
 - Does not reset dialog rounds
 - Changes visible to all teammates
 - When writing `progress`, assume teammates will skim it to synchronize on the current task truth rather than read your private process log
+- Do not keep blindly calling `mind_more` until `progress` becomes a chronology; when the bulletin board starts accumulating duplicates, stale entries, or noisy history, use `change_mind` to condense it around facts that are still effective now
+- Detailed investigations, long logs, full plans, acceptance records, and expanded rationale belong in formal rtws documentation; Taskdoc should keep only the key point, current conclusion, next step, and a location pointer such as path/section/command
 
 ## Tool Overview
 
@@ -129,8 +131,10 @@ Taskdoc is a **task contract** and the task's **team-shared source of current tr
 - Keep concise: reminders are often 1-3 items; prefer `update_reminder` to compress/merge
 - Separate carriers: information that must synchronize the team's current effective state, key decisions, next steps, or still-active blockers belongs in `progress`, the quasi-real-time task bulletin board; reminders keep local resume details
 - Team-facing: keep `progress` scannable and centered on what is still effective now; do not let it degrade into a personal log, raw chronology, scratchpad, or stale history pile. Use `mind_more` for small additions and `change_mind` when cleanup/reordering/compression is needed
+- Condense when needed: `mind_more` is not the default bookkeeping move. If one topic already has several phase notes, prefer `change_mind` to merge them into the current summary; put the detailed expansion in formal rtws documentation and keep a document pointer in Taskdoc
 - Collapse before clearing: the Main Dialog first records undocumented discussion details the next course needs to know into the appropriate Taskdoc sections, then creates a structured continuation-package reminder; a Side Dialog must not maintain Taskdoc or draft Taskdoc update proposals, and should directly maintain sufficiently detailed continuation-package reminders. If the current course is already under system remediation, rough multi-reminder carry-over is acceptable but must be reconciled first in the new course
 - Avoid raw-material dumps: do not paste long logs or large tool outputs into reminders
+- Documentation layering: Taskdoc says “what the team should sync on / do next now”; formal rtws documentation carries “why, how, detailed evidence, and the full process”. When Taskdoc references formal rtws documentation, use a stable path/section name/relevant command instead of copying the full content
 
 ### 4. What Belongs in `progress`
 
@@ -139,16 +143,18 @@ Taskdoc is a **task contract** and the task's **team-shared source of current tr
   - blockers that are confirmed and still active
   - the next step the team should currently align on
   - completed stage closures and remaining gaps
+  - a short summary of content already written to formal rtws documentation, plus a pointer to that document
 - Poor fits for `progress`:
   - “I just read file X”
   - “I might try a small idea next”
   - scratch notes only useful to the current speaker
   - historical traces whose current validity is unclear
+  - detailed expansions, long logs, full plans, or acceptance-record text that belongs in formal rtws documentation
 
 ## Limitations and Notes
 
 1. `dialog` reminders end with the dialog; `personal` reminders stay visible in all later dialogs you lead
-2. Use `mind_more` for small Taskdoc additions; use `change_mind` for full-section replacement and merge existing content first
+2. Use `mind_more` for small Taskdoc additions; use `change_mind` for full-section replacement and merge existing content first. Do not treat `mind_more` as a chronology tool; when cleanup, stale-entry removal, or same-topic consolidation is needed, use `change_mind`
 3. `mind_more` / `change_mind` do not reset dialog rounds
 4. A continuation-package reminder should keep only details still not covered by Taskdoc but easy to lose during resume; in the Main Dialog, undocumented discussion details from current dialog history that the next course needs to know should be written to the appropriate Taskdoc sections first; in a Side Dialog under caution/critical remediation, maintain sufficiently detailed continuation-package reminders only
 5. Do not turn `personal` reminders into a long-term fact dump; move durable knowledge into `personal_memory`

package/dist/tools/prompts/control/en/scenarios.md

@@ -117,21 +117,23 @@ replyTellaskBack({
 
 ### Scenario Description
 
-Announce the current effective state, key decisions, next step, and still-active blockers to the whole team rather than writing a private chronology.
+Announce the current effective state, key decisions, next step, and still-active blockers to the whole team rather than writing a private chronology. If details have been organized into formal rtws documentation, `progress` should keep only the summary and document pointer.
 
 ### Example
 
 ```typescript
 // Small additions that are still effective now
 mind_more({
-  items: ['- Next: verify control / team_mgmt manuals and tests are aligned'],
+  items: [
+    '- Next: verify control / team_mgmt manuals and tests are aligned (details: <doc-path>#<section>)',
+  ],
 });
 
-// Full-section replacement when cleanup, reordering, or compression is needed
+// Full-section replacement when cleanup, reordering, same-topic consolidation, or chronology compression is needed
 change_mind({
   selector: 'progress',
   content:
-    '## Progress\n\n### Current Effective State\n- The memory-carrier boundary cleanup is complete; next we strengthen the Taskdoc bulletin-board semantics\n\n### Decisions In Effect\n- `personal_memory` is no longer treated as a short-term junk drawer\n- `team_memory` now carries only long-lived team conventions and invariants\n\n### Next Step\n- Add stronger `progress` bulletin-board guidance in control / team_mgmt manuals\n\n### Still-Active Blockers\n- None',
+    '## Progress\n\n### Current Effective State\n- The memory-carrier boundary cleanup is complete; next we strengthen the Taskdoc bulletin-board semantics; details: <doc-path>#<section>\n\n### Decisions In Effect\n- `personal_memory` is no longer treated as a short-term junk drawer\n- `team_memory` now carries only long-lived team conventions and invariants\n\n### Next Step\n- Add stronger `progress` bulletin-board guidance in control / team_mgmt manuals\n\n### Still-Active Blockers\n- None',
 });
 ```
 
@@ -193,7 +195,7 @@ recall_taskdoc({
 
 ### Scenario Description
 
-Maintain taskdoc integrity and consistency, and keep `progress` as a team-scannable current-truth snapshot.
+Maintain taskdoc integrity and consistency, and keep `progress` as a team-scannable current-truth snapshot; put detailed expansion in formal rtws documentation and keep only the summary plus location pointer in Taskdoc.
 
 ### Example
 
@@ -202,6 +204,6 @@ Maintain taskdoc integrity and consistency, and keep `progress` as a team-scanna
 change_mind({
   selector: 'progress',
   content:
-    '## Progress\n\n### Current Effective State\n- The boundary wording has been propagated into handbook sources and tests\n\n### Decisions In Effect\n- role assets / personal_memory / team_memory / Taskdoc-progress / reminders now have separated responsibilities\n\n### Next Step\n- Re-verify control manual wording, Taskdoc display text, and boundary tests\n\n### Still-Active Blockers\n- None',
+    '## Progress\n\n### Current Effective State\n- The boundary wording has been propagated into handbook sources and tests; details: <doc-path>#<section>\n\n### Decisions In Effect\n- role assets / personal_memory / team_memory / Taskdoc-progress / reminders now have separated responsibilities\n\n### Next Step\n- Re-verify control manual wording, Taskdoc display text, and boundary tests\n\n### Still-Active Blockers\n- None',
 });
 ```

package/dist/tools/prompts/control/en/tools.md

@@ -175,7 +175,10 @@ Append entries to a Taskdoc section; defaults to `progress`, reducing full-secti
 
 ```typescript
 mind_more({
-  items: ['- Next: review verification results', '- Blocker: none'],
+  items: [
+    '- Next: review verification results (details: <doc-path>#<section>)',
+    '- Blocker: API acceptance criteria pending',
+  ],
 });
 ```
 
@@ -183,7 +186,9 @@ mind_more({
 
 - Append-only: it does not deduplicate, rewrite, or compress old content
 - Good for adding one or two still-effective states, decisions, next steps, or blockers to `progress`
+- Not for appending every investigation step, long log, full plan, or acceptance record as a chronology; those details belong in formal rtws documentation, while Taskdoc keeps the summary and document pointer
 - If stale entries must be removed, reordered, or compressed, use `change_mind` for a full-section replacement
+- When one topic already has several phase notes, prefer `change_mind` to merge them into a concise current announcement instead of continuing to call `mind_more`
 
 ### 7. recall_taskdoc
 
@@ -257,7 +262,9 @@ update_reminder({
 
 ```typescript
 mind_more({
-  items: ['- Next: strengthen the bulletin-board semantics of Taskdoc `progress`'],
+  items: [
+    '- Next: strengthen the bulletin-board semantics of Taskdoc `progress` (details: <doc-path>#<section>)',
+  ],
 });
 ```
 
@@ -267,7 +274,7 @@ mind_more({
 change_mind({
   selector: 'progress',
   content:
-    '## Progress\n\n### Current Effective State\n- The handbook boundary split is now agreed: role assets / personal long-lived experience / Taskdoc-progress / reminders\n\n### Decisions In Effect\n- `persona / knowhow / pitfalls` no longer absorb daily member experience\n- `personal_memory` is reserved for one member\\'s reusable long-lived experience\n\n### Next Step\n- Strengthen the bulletin-board semantics of Taskdoc `progress`\n\n### Still-Active Blockers\n- None',
+    '## Progress\n\n### Current Effective State\n- The handbook boundary split is now agreed: role assets / personal long-lived experience / Taskdoc-progress / reminders; details: <doc-path>#<section>\n\n### Decisions In Effect\n- `persona / knowhow / pitfalls` no longer absorb daily member experience\n- `personal_memory` is reserved for one member\\'s reusable long-lived experience\n\n### Next Step\n- Strengthen the bulletin-board semantics of Taskdoc `progress`\n\n### Still-Active Blockers\n- None',
 });
 ```
 

package/dist/tools/prompts/control/zh/principles.md

@@ -77,6 +77,8 @@
 - 不重置对话轮次
 - 变更对所有队友可见
 - 写入 `progress` 时，应默认假设全队成员会用它快速同步“当前任务真相”，而不是阅读你的个人过程记录
+- 不要无脑连续使用 `mind_more` 把 `progress` 写成流水账；当公告牌开始堆积、重复或含过期信息时，用 `change_mind` 按当前仍有效的事实压缩整理
+- 细节展开、调查过程、长日志、方案全文和验收记录应落进 rtws 正式文档；差遣牒只保留要点、当前结论、下一步，以及指向正式文档的路径/章节/命令等定位 pointer
 
 ## 工具概览
 
@@ -129,8 +131,10 @@
 - 保持简洁：默认提醒项常见 1–3 条，优先 `update_reminder` 压缩/合并
 - 区分载体：需要向全队同步的当前有效状态、关键决策、下一步与仍成立阻塞，写入 `progress` 这一准实时任务公告牌；提醒项只留个人/当前对话恢复所需细节
 - 面向全队：`progress` 应保持可扫读、以“当前仍有效”为准，不要退化成个人日志、流水账、临时便签或历史残影堆积；少量新增用 `mind_more`，需要清旧/重排/压缩时用 `change_mind`
+- 按需整理：`mind_more` 不是默认记账动作。若同一主题已有多条阶段性记录，优先用 `change_mind` 合并成当前摘要；把细节放进 rtws 正式文档，并在差遣牒里保留文档定位 pointer
 - 换程前收束：主线对话先把尚未落实到文档、且下一程需要知会的讨论细节写入差遣牒合适章节，再整理结构化接续包提醒项；支线对话不要维护差遣牒，也不要整理差遣牒更新提案，直接维护足够详尽的接续包提醒项。若系统已把当前程切到吃紧/告急处置态，则先保留多条粗略提醒项过桥也可以；当前程只做落文档/保信息 + `clear_mind`（支线只做保信息 + `clear_mind`），系统真正开启新一程后第一步再收敛
 - 拒绝原料堆积：不要把长日志/大段 tool output 直接塞进提醒项
+- 文档分层：差遣牒写“现在应如何同步/推进”，正式文档写“为什么、怎么做、详细证据和完整过程”。差遣牒需要引用正式文档时，写稳定路径/章节名/相关命令，而不是复制整段内容
 
 ### 4. `progress` 内容取舍
 
@@ -139,16 +143,18 @@
   - 当前已确认、仍成立的 blocker
   - 当前全队应共识的下一步
   - 当前阶段性闭环与尚未闭环的 gap
+  - 已落正式文档的关键内容摘要，以及定位该文档的 pointer
 - 不适合写进 `progress`：
   - “我刚刚看了什么文件”
   - “我准备先试一个小想法”
   - 只对当前说话者自己有用的临时便签
   - 无法判断是否仍然有效的历史痕迹
+  - 可在 rtws 正式文档中承载的细节展开、长日志、完整方案或验收记录全文
 
 ## 限制与注意事项
 
 1. `dialog` 提醒会随对话结束而结束；`personal` 提醒会在所有由你主理的后续对话里继续可见
-2. 差遣牒少量新增可用 `mind_more` 追加；整段替换用 `change_mind`，请确保合并已有内容
+2. 差遣牒少量新增可用 `mind_more` 追加；整段替换用 `change_mind`，请确保合并已有内容。不要把 `mind_more` 当流水账工具；需要整理、去旧、合并同主题记录时直接 `change_mind`
 3. `mind_more` / `change_mind` 不重置对话轮次
 4. 接续包提醒项只保留差遣牒仍未覆盖、但恢复工作容易丢的细节；主线对话应先把当前对话历史中应由下一程知会的未落文档讨论细节写入差遣牒合适章节；支线对话在吃紧/告急时只维护足够详尽的接续包提醒项
 5. 不要把 `personal` 提醒堆成长期事实仓库；耐久知识应迁到 `personal_memory`

package/dist/tools/prompts/control/zh/scenarios.md

@@ -116,21 +116,21 @@ replyTellaskBack({
 
 ### 场景描述
 
-把当前有效状态、关键决策、下一步与仍成立阻塞公告给全队，而不是写个人流水账。
+把当前有效状态、关键决策、下一步与仍成立阻塞公告给全队，而不是写个人流水账。若细节已整理到 rtws 正式文档，`progress` 只写摘要和文档定位 pointer。
 
 ### 示例
 
 ```typescript
 // 少量新增当前仍有效的公告条目
 mind_more({
-  items: ['- 下一步：复核 control / team_mgmt 手册与测试是否对齐'],
+  items: ['- 下一步：复核 control / team_mgmt 手册与测试是否对齐（详见 <文档路径>#<章节>）'],
 });
 
-// 需要清理旧项、重排或压缩时，整章替换
+// 需要清理旧项、重排、同主题合并或压缩流水账时，整章替换
 change_mind({
   selector: 'progress',
   content:
-    '## Progress\n\n### 当前有效状态\n- 已完成三类记忆载体边界收口，准备补 Taskdoc 公告牌属性\n\n### 已生效决策\n- `personal_memory` 不再作为短期杂物柜\n- `team_memory` 只承接团队长期共识与不变量\n\n### 下一步\n- 在 control / team_mgmt 手册中补强 `progress` 的公告牌语义\n\n### 仍成立阻塞\n- 无',
+    '## Progress\n\n### 当前有效状态\n- 已完成三类记忆载体边界收口，准备补 Taskdoc 公告牌属性；细节见 <文档路径>#<章节>\n\n### 已生效决策\n- `personal_memory` 不再作为短期杂物柜\n- `team_memory` 只承接团队长期共识与不变量\n\n### 下一步\n- 在 control / team_mgmt 手册中补强 `progress` 的公告牌语义\n\n### 仍成立阻塞\n- 无',
 });
 ```
 
@@ -192,7 +192,7 @@ recall_taskdoc({
 
 ### 场景描述
 
-维护差遣牒的完整性和一致性，并确保 `progress` 始终是可供全队扫读的当前真相快照。
+维护差遣牒的完整性和一致性，并确保 `progress` 始终是可供全队扫读的当前真相快照；细节展开放入 rtws 正式文档，差遣牒只保留摘要和定位 pointer。
 
 ### 示例
 
@@ -201,6 +201,6 @@ recall_taskdoc({
 change_mind({
   selector: 'progress',
   content:
-    '## Progress\n\n### 当前有效状态\n- 边界口径已统一到手册源头与测试\n\n### 已生效决策\n- 角色级资产 / personal_memory / team_memory / Taskdoc-progress / reminders 的职责已经切开\n\n### 下一步\n- 复验 control 手册、Taskdoc 展示文案与边界测试\n\n### 仍成立阻塞\n- 无',
+    '## Progress\n\n### 当前有效状态\n- 边界口径已统一到手册源头与测试；细节见 <文档路径>#<章节>\n\n### 已生效决策\n- 角色级资产 / personal_memory / team_memory / Taskdoc-progress / reminders 的职责已经切开\n\n### 下一步\n- 复验 control 手册、Taskdoc 展示文案与边界测试\n\n### 仍成立阻塞\n- 无',
 });
 ```

package/dist/tools/prompts/control/zh/tools.md

@@ -175,7 +175,7 @@ updated_at: <更新时间戳>
 
 ```typescript
 mind_more({
-  items: ['- 下一步：复核验证结果', '- 阻塞：无'],
+  items: ['- 下一步：复核验证结果（详见 <文档路径>#<章节>）', '- 阻塞：等待 API 验收口径确认'],
 });
 ```
 
@@ -183,7 +183,9 @@ mind_more({
 
 - 只追加，不会自动去重、改写或压缩旧内容
 - 适合给 `progress` 补一两条当前仍有效的状态、决策、下一步或阻塞
+- 不适合把每一步调查过程、长日志、完整方案或验收记录当流水账追加进去；这些细节应写入 rtws 正式文档，差遣牒只写摘要和文档定位 pointer
 - 若需要删除陈旧项、重排结构或压缩公告牌，仍使用 `change_mind` 做整章替换
+- 当同一主题已经有多条阶段记录时，优先 `change_mind` 合并成当前仍有效的简明公告，而不是继续 `mind_more`
 
 ### 7. recall_taskdoc
 
@@ -255,7 +257,7 @@ update_reminder({
 
 ```typescript
 mind_more({
-  items: ['- 下一步：补齐 Taskdoc `progress` 的公告牌属性说明'],
+  items: ['- 下一步：补齐 Taskdoc `progress` 的公告牌属性说明（详见 <文档路径>#<章节>）'],
 });
 ```
 
@@ -265,7 +267,7 @@ mind_more({
 change_mind({
   selector: 'progress',
   content:
-    '## Progress\n\n### 当前有效状态\n- 手册边界方案已确定：角色级资产 / 个人长期经验 / Taskdoc-progress / reminders 分流\n\n### 已生效决策\n- `persona / knowhow / pitfalls` 不承接成员日常经验\n- `personal_memory` 只承接成员自己的长期可复用经验\n\n### 下一步\n- 补齐 Taskdoc `progress` 的公告牌属性说明\n\n### 仍成立阻塞\n- 无',
+    '## Progress\n\n### 当前有效状态\n- 手册边界方案已确定：角色级资产 / 个人长期经验 / Taskdoc-progress / reminders 分流；细节见 <文档路径>#<章节>\n\n### 已生效决策\n- `persona / knowhow / pitfalls` 不承接成员日常经验\n- `personal_memory` 只承接成员自己的长期可复用经验\n\n### 下一步\n- 补齐 Taskdoc `progress` 的公告牌属性说明\n\n### 仍成立阻塞\n- 无',
 });
 ```
 

package/dist/utils/task-package.js

@@ -189,7 +189,7 @@ async function updateTaskPackageByChangeMindTarget(params) {
     await ensureTaskPackage(taskPackageDirFullPath, updatedBy);
     const filePath = taskPackageFilePathForChangeMindTarget(taskPackageDirFullPath, target);
     await fs.promises.mkdir(path.dirname(filePath), { recursive: true });
-    await fs.promises.writeFile(filePath, content, 'utf8');
+    await writeMarkdownFileWithCanonicalEnding(filePath, content);
 }
 async function appendTaskPackageByChangeMindTarget(params) {
     const { taskPackageDirFullPath, target, content, sep, updatedBy } = params;
@@ -198,7 +198,16 @@ async function appendTaskPackageByChangeMindTarget(params) {
     await fs.promises.mkdir(path.dirname(filePath), { recursive: true });
     const current = await readTextFileIfPresent(filePath);
     const next = current === null || current.trim() === '' ? content : joinForAppend(current, content, sep);
-    await fs.promises.writeFile(filePath, next, 'utf8');
+    await writeMarkdownFileWithCanonicalEnding(filePath, next);
+}
+async function writeMarkdownFileWithCanonicalEnding(filePath, content) {
+    await fs.promises.writeFile(filePath, withCanonicalMarkdownFileEnding(content), 'utf8');
+}
+function withCanonicalMarkdownFileEnding(content) {
+    const stripped = stripTrailingMarkdownFileNewlines(content);
+    if (stripped === '')
+        return '';
+    return `${stripped}\n`;
 }
 function taskPackageFilePathForChangeMindTarget(taskPackageDirFullPath, target) {
     switch (target.kind) {
@@ -271,18 +280,23 @@ async function readTaskPackageSections(taskPackageDirFullPath) {
     return { goals, constraints, progress };
 }
 function formatSectionBodyI18n(state) {
-    // Injection must be deterministic and treat section bodies as opaque markdown.
+    // Injection must be deterministic and treat section bodies as opaque markdown,
+    // except for file-final newlines that only encode on-disk formatting.
     // If a required file is missing, inject an empty body (status should be shown elsewhere).
     if (state.kind === 'present')
-        return state.content;
+        return stripTrailingMarkdownFileNewlines(state.content);
     return '';
 }
 function formatBearInMindBody(state) {
     if (state.kind !== 'present')
         return null;
-    if (state.content.trim() === '')
+    const content = stripTrailingMarkdownFileNewlines(state.content);
+    if (content.trim() === '')
         return null;
-    return state.content;
+    return content;
+}
+function stripTrailingMarkdownFileNewlines(content) {
+    return content.replace(/(?:\r\n?|\n)+$/u, '');
 }
 function formatEffectiveTaskDocFromSections(language, sections, bearInMind) {
     // Deterministic framing only; section bodies are treated as opaque markdown.
@@ -470,7 +484,7 @@ async function updateTaskPackageSection(params) {
     const { taskPackageDirFullPath, section, content, updatedBy } = params;
     await ensureTaskPackage(taskPackageDirFullPath, updatedBy);
     const filePath = path.join(taskPackageDirFullPath, taskPackageFilenameForSection(section));
-    await fs.promises.writeFile(filePath, content, 'utf8');
+    await writeMarkdownFileWithCanonicalEnding(filePath, content);
 }
 async function readTaskPackageExtraSectionsIndex(taskPackageDirFullPath) {
     const maxEntries = 64;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dominds",
-  "version": "1.20.1",
+  "version": "1.20.2",
   "description": "Dominds CLI and aggregation shell for the LongRun AI kernel/runtime packages.",
   "type": "commonjs",
   "publishConfig": {