npm - dominds - Versions diffs - 1.2.7 → 1.3.1 - Mend

dominds 1.2.7 → 1.3.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (104) hide show

package/dist/static/index.html CHANGED Viewed

@@ -52,7 +52,7 @@
         padding: 20px;
       }
     </style>
-    <script type="module" crossorigin src="/assets/index-D3TQbAKh.js"></script>
+    <script type="module" crossorigin src="/assets/index-DMbwqOm6.js"></script>
     <link rel="stylesheet" crossorigin href="/assets/index-BiNcBn_U.css">
   </head>
   <body>

package/dist/tools/ctrl.js CHANGED Viewed

@@ -332,8 +332,8 @@ exports.clearMindTool = {
     name: 'clear_mind',
     description: 'Clear dialog mind and start a new course, optionally adding a reminder.',
     descriptionI18n: {
-        en: 'Clear dialog mind and start a new course. Prepare a "Continuation Package" (first step, key location info, run/verification info, volatile details) as reminder_content so you can resume quickly.',
-        zh: '清理头脑并开启新一程对话。建议准备一个"接续包"（① 第一步操作，② 关键定位信息，③ 运行/验证信息，④ 临时细节）作为 reminder_content，以便快速接续。',
+        en: 'Clear dialog mind and start a new course. If needed, pass reminder_content so you can resume quickly. Prefer a structured "Continuation Package" when still clear-headed; if context is already degraded, rough bridge notes are acceptable and can be reorganized in the new course.',
+        zh: '清理头脑并开启新一程对话。若需要，可传入 reminder_content 以便快速接续。头脑还清楚时，优先整理成结构化"接续包"；若上下文已吃紧到发乱，粗略过桥笔记也可以，进入新一程后再重新整理。',
     },
     parameters: {
         type: 'object',
@@ -341,7 +341,7 @@ exports.clearMindTool = {
         properties: {
             reminder_content: {
                 type: 'string',
-                description: 'Optional reminder content (Continuation Package) to add.',
+                description: 'Optional reminder content to add. Prefer structured continuation notes when possible; rough bridge notes are also acceptable if context is already degraded.',
             },
         },
     },

package/dist/tools/prompts/control/en/index.md CHANGED Viewed

@@ -26,9 +26,9 @@
 control is Dominds' **dialog control toolset** for managing dialog state, reminders, and taskdocs:
-- **Reminder management**: Temporary reminders, valid in current dialog
+- **Reminder management**: Dialog-local working set; usually keep it small, prefer continuation-package cleanup before `clear_mind`, but rough multi-reminder carry-over is allowed when context is already degraded
 - **Taskdoc operations**: Update task contracts (goals/constraints/progress)
-- **Context maintenance**: Manage temporary state during dialog
+- **Context maintenance**: Reduce cognitive load without losing key resume state
 ## Quick Navigation
@@ -50,11 +50,12 @@ control is Dominds' **dialog control toolset** for managing dialog state, remind
 ### Reminder
-Reminders are **session-level** temporary information for:
+Reminders are **session-level** temporary working-set information for:
 - Marking pending tasks
-- Tracking current task progress
+- Tracking current next steps / blockers
 - Recording blocking issues
+- Holding continuation-package bridge notes before `clear_mind`
 ### Taskdoc

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

@@ -27,13 +27,15 @@
 ### 1. Reminder
-Reminders are **session-level** temporary information for tracking pending items in the current dialog.
+Reminders are **session-level** temporary working-set information for tracking pending items and resume clues in the current dialog.
 **Characteristics:**
 - Valid only in current dialog
 - Automatically cleared after dialog ends
 - Can be added, modified, or deleted at any time
+- Should stay compact, scannable, and directly actionable by default
+- Before `clear_mind`, prefer a structured continuation-package reminder when still clear-headed; if already degraded, rough multi-reminder carry-over is acceptable
 **Difference from memory:**
 | Feature | reminder | memory |
@@ -72,9 +74,9 @@ Taskdoc is a **task contract** defining goals, constraints, and progress.
 ### 1. Reminder Usage Scenarios
-- **Task marking**: Mark currently processing tasks
-- **Blocking records**: Record encountered blocking issues
-- **Todo list**: Track pending items
+- **Current working set**: next step, blockers, key pointers
+- **Easy-to-lose details**: temporary paths, ids, commands, sample inputs
+- **Course transition**: continuation-package notes before `clear_mind`, including rough multi-reminder carry-over when already degraded
 ### 2. Taskdoc Update Timing
@@ -84,12 +86,14 @@ Taskdoc is a **task contract** defining goals, constraints, and progress.
 ### 3. Update Strategy
-- Keep concise: Only modify necessary content each update
-- Use clear markers: Use clear format to mark completed/in-progress/pending
-- Sync state: Ensure goals, constraints, and progress remain consistent
+- Keep concise: reminders are often 1-3 items; prefer `update_reminder` to compress/merge
+- Separate carriers: shared decisions/status belong in Taskdoc; reminders keep local resume details
+- Collapse before clearing: if you are still clear-headed, rewrite into a structured continuation-package reminder; if already degraded, 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
 ## Limitations and Notes
 1. Reminders are not persisted after dialog ends
 2. Taskdoc updates use full section replacement, ensure to merge existing content
 3. `change_mind` does not reset dialog rounds
+4. A continuation-package reminder should keep only details not already covered by Taskdoc but easy to lose during resume

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

@@ -23,6 +23,11 @@
 Add reminder.
+Use when:
+- Adding a new temporary working-set item
+- Creating continuation-package notes before `clear_mind`; rough bridge notes are acceptable when context is already degraded
 **Parameters:**
 - `content` (required): Reminder content
@@ -62,6 +67,12 @@ deleted_at: <deletion timestamp>
 Update reminder content.
+Use when:
+- Compressing / merging existing reminders
+- Rewriting pre-clear resume info into continuation-package notes
+- Removing details that have already been promoted into Taskdoc
 **Parameters:**
 - `reminder_no` (required): Reminder number (1-based)
@@ -184,3 +195,11 @@ status: error
 error_code: <error code>
 message: <error message>
 ```
+## Reminder Content Guidance
+- Normal reminders should stay concise, fresh, and directly actionable; often 1-3 items total
+- For a continuation package, prefer structured notes when clear-headed: next step, key pointers, run/verify, easy-to-lose volatile details
+- If already in caution/critical and muddled, rough multi-reminder bridge notes are acceptable; reconcile them first in the new course
+- Keep only details not already covered by Taskdoc; do not repeat team-shared status
+- Do not paste long logs, large tool outputs, or raw material into reminders

package/dist/tools/prompts/control/zh/index.md CHANGED Viewed

@@ -26,9 +26,9 @@
 control 是 Dominds 的**对话控制工具集**，用于管理对话状态、提醒和差遣牒：
-- **提醒管理**：临时提醒，在当前对话中有效
+- **提醒管理**：当前对话内的临时工作集；默认保持少量，换程前优先整理接续包，若上下文已乱也允许先带多条粗略提醒项过桥
 - **差遣牒操作**：更新任务契约（goals/constraints/progress）
-- **上下文维护**：管理对话过程中的临时状态
+- **上下文维护**：在不丢关键恢复线索的前提下降低认知负载
 ## 快速导航
@@ -50,11 +50,12 @@ control 是 Dominds 的**对话控制工具集**，用于管理对话状态、
 ### 提醒（Reminder）
-提醒是**会话级别**的临时信息，用于：
+提醒是**会话级别**的临时工作集，用于：
 - 标记待处理事项
-- 追踪当前任务进度
+- 追踪当前下一步/阻塞
 - 记录阻塞问题
+- 在 `clear_mind` 前承载接续包；若已发乱，可先带多条粗略提醒项过桥
 ### 差遣牒（Taskdoc）

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

@@ -27,13 +27,15 @@
 ### 1. 提醒（Reminder）
-提醒是**会话级别**的临时信息，用于在当前对话中追踪待处理事项。
+提醒是**会话级别**的临时工作集，用于在当前对话中追踪待处理事项与恢复线索。
 **特点：**
 - 仅在当前对话中有效
 - 对话结束后自动清除
 - 可随时添加、修改、删除
+- 默认应保持少量、可扫读、可直接指导下一步
+- 准备 `clear_mind` 时，头脑清楚则优先压缩成结构化接续包提醒项；若已吃紧/告急，也可先保留多条粗略提醒项过桥
 **与 memory 的区别：**
 | 特性 | reminder | memory |
@@ -72,9 +74,9 @@
 ### 1. 提醒使用场景
-- **任务标记**：标记当前正在处理的任务
-- **阻塞记录**：记录遇到的阻塞问题
-- **待办清单**：追踪待处理事项
+- **当前工作集**：当前下一步、阻塞、关键定位信息
+- **易丢细节**：临时路径、id、命令、样例输入
+- **换程接续**：在 `clear_mind` 前整理接续包；若已发乱，可先保留多条粗略提醒项
 ### 2. 差遣牒更新时机
@@ -84,12 +86,14 @@
 ### 3. 更新策略
-- 保持简洁：每次更新只修改必要内容
-- 明确标注：用清晰的格式标记已完成/进行中/待处理
-- 同步状态：确保 goals、constraints、progress 保持一致
+- 保持简洁：默认提醒项常见 1–3 条，优先 `update_reminder` 压缩/合并
+- 区分载体：团队共享决策/状态写入差遣牒，提醒项只留本地恢复所需细节
+- 换程前收束：若头脑清楚，优先整理成结构化接续包提醒项；若已发乱，先保留多条粗略提醒项过桥也可以，但新一程第一步就要收敛
+- 拒绝原料堆积：不要把长日志/大段 tool output 直接塞进提醒项
 ## 限制与注意事项
 1. 提醒在对话结束后不会持久化
 2. 差遣牒更新使用整段替换，请确保合并已有内容
 3. `change_mind` 不重置对话轮次
+4. 接续包提醒项只保留差遣牒未覆盖、但恢复工作容易丢的细节

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

@@ -23,6 +23,11 @@
 添加提醒。
+**适用：**
+- 添加新的临时工作集条目
+- 若准备 `clear_mind`，也可新建接续包提醒项；若已发乱，先记粗略过桥信息也可以
 **参数：**
 - `content`（必需）：提醒内容
@@ -62,6 +67,12 @@ deleted_at: <删除时间戳>
 更新提醒内容。
+**适用：**
+- 压缩/合并现有提醒项
+- 把换程前需要保留的信息整理成接续包；若已发乱，也可先保留多条粗略提醒项
+- 删除已写入差遣牒、无需在提醒项重复保留的内容
 **参数：**
 - `reminder_no`（必需）：提醒编号（1-based）
@@ -184,3 +195,11 @@ status: error
 error_code: <错误代码>
 message: <错误消息>
 ```
+## 提醒项内容建议
+- 默认提醒项应保持短、新、能直接指导下一步，常见 1–3 条
+- 若用于接续包，头脑清楚时优先结构化内容：下一步行动、关键定位、运行/验证、容易丢的临时细节
+- 若已吃紧/告急，先保留多条粗略提醒项也可以；进入新一程后第一步就收敛整理
+- 接续包只保留差遣牒未覆盖的细节；不要重复团队共享状态
+- 不要把长日志、大段 tool output、原始材料直接塞进提醒项

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "dominds",
-  "version": "1.2.7",
+  "version": "1.3.1",
   "description": "DevOps Mindsets — Sustainable Agentic Product Lifecycle",
   "type": "commonjs",
   "private": false,
@@ -51,11 +51,11 @@
     "pnpm": ">=10.30.2 <11"
   },
   "dependencies": {
+    "@longrun-ai/codex-auth": "^0.8.0",
     "@anthropic-ai/sdk": "^0.78.0",
-    "@longrun-ai/codex-auth": "^0.7.0",
+    "openai": "^6.25.0",
     "@modelcontextprotocol/sdk": "^1.27.1",
     "async-mutex": "^0.5.0",
-    "openai": "^6.25.0",
     "ws": "^8.19.0",
     "yaml": "^2.8.2",
     "zod": "^4.3.6"