npm - dominds - Versions diffs - 0.7.1 → 0.7.3 - Mend

dominds 0.7.1 → 0.7.3

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 (120) hide show

package/dist/static/index.html CHANGED Viewed

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

package/dist/tools/context-health.js CHANGED Viewed

@@ -39,12 +39,12 @@ function formatContextHealthOwnerHeader(args) {
         ];
         if (!snapshot) {
             lines.push('- 状态：未知（尚未获取上下文统计）');
-            lines.push('- 优先动作：change_mind(progress) → clear_mind');
+            lines.push('- 现在就做：用提醒项收敛关键细节（update_reminder）→ change_mind(progress) → clear_mind');
             return lines.join('\n');
         }
         if (snapshot.kind !== 'available') {
             lines.push('- 状态：未知（token 统计不可用）');
-            lines.push('- 优先动作：change_mind(progress) → clear_mind');
+            lines.push('- 现在就做：用提醒项收敛关键细节（update_reminder）→ change_mind(progress) → clear_mind');
             return lines.join('\n');
         }
         switch (snapshot.level) {
@@ -53,16 +53,16 @@ function formatContextHealthOwnerHeader(args) {
                 return lines.join('\n');
             }
             case 'caution': {
-                lines.push('- 状态：🟡 黄（警告）');
-                lines.push('- 优先动作：change_mind(progress) → clear_mind');
+                lines.push('- 状态：🟡 黄（必须尽快清理）');
+                lines.push('- 硬规程：先 update_reminder 收敛工作集 → 再 change_mind(progress) → 然后 clear_mind');
                 return lines.join('\n');
             }
             case 'critical': {
-                lines.push('- 状态：🔴 红（危险）');
+                lines.push('- 状态：🔴 红（硬闸门）');
                 if (remainingGenTurns !== undefined) {
-                    lines.push(`- 倒数：剩余 ${remainingGenTurns} 次生成机会；到 0 系统将自动开启新一轮以保持稳定性`);
+                    lines.push(`- 倒数：剩余 ${remainingGenTurns} 次生成机会；到 0 系统将被动开启新一轮/新回合以保持稳定性`);
                 }
-                lines.push('- 立刻：change_mind(progress) → clear_mind');
+                lines.push('- 禁止继续推进实现：先 update_reminder 收敛工作集 → 再 change_mind(progress) → 然后 clear_mind');
                 return lines.join('\n');
             }
             default: {

package/dist/utils/task-doc.js CHANGED Viewed

@@ -120,33 +120,33 @@ If you provided a regular file path (e.g. a \`.md\`), that is unexpected. Please
                 return [
                     `**差遣牒结构（封装差遣牒 \`*.tsk/\`）：**`,
                     `- 我们的差遣牒是一个 \`*.tsk/\` 目录，分为 3 个分段：\`goals\` / \`constraints\` / \`progress\`。`,
-                    `- 维护方式：每次调用函数工具 \`change_mind\` 必须指定一个分段（selector: \`!goals\` / \`!constraints\` / \`!progress\`）；可在同一轮中多次调用 \`change_mind\` 来一次更新多个分段。`,
+                    `- 维护方式：每次 \`!?@change_mind\` 必须指定一个分段（\`!goals\` / \`!constraints\` / \`!progress\`）；可在同一条消息中连续发出多个 \`!?@change_mind\` 来一次更新多个分段。`,
                     ``,
                     `**分段状态：**`,
                     `- \`goals.md\`：${goalsZh}`,
                     `- \`constraints.md\`：${constraintsZh}`,
                     `- \`progress.md\`：${progressZh}`,
                     ``,
-                    `若某个分段缺失，请用函数工具 \`change_mind\` 创建（不要用通用文件工具）：`,
-                    `- \`change_mind({\"selector\":\"!goals\",\"content\":\"...\"})\``,
-                    `- \`change_mind({\"selector\":\"!constraints\",\"content\":\"...\"})\``,
-                    `- \`change_mind({\"selector\":\"!progress\",\"content\":\"...\"})\``,
+                    `若某个分段缺失，请用 \`!?@change_mind\` 创建（不要用通用文件工具）：`,
+                    `- \`!?@change_mind !goals\\n!?<content>\``,
+                    `- \`!?@change_mind !constraints\\n!?<content>\``,
+                    `- \`!?@change_mind !progress\\n!?<content>\``,
                 ].join('\n');
             }
             return [
                 `**Task Doc Constitution (Encapsulated \`*.tsk/\`):**`,
                 `- Our Task Doc is a \`*.tsk/\` directory with exactly 3 sections: \`goals\` / \`constraints\` / \`progress\`.`,
-                `- Maintenance: each function tool call \`change_mind\` must target one section (selector: \`!goals\` / \`!constraints\` / \`!progress\`). You may call \`change_mind\` multiple times in a single turn to update multiple sections.`,
+                `- Maintenance: each \`!?@change_mind\` call must target one section (\`!goals\` / \`!constraints\` / \`!progress\`). You may include multiple \`!?@change_mind\` calls in a single message to update multiple sections.`,
                 ``,
                 `**Sections:**`,
                 `- \`goals.md\`: ${goalsStatus}`,
                 `- \`constraints.md\`: ${constraintsStatus}`,
                 `- \`progress.md\`: ${progressStatus}`,
                 ``,
-                `If any section is missing, create it with the function tool \`change_mind\` (never via general file tools):`,
-                `- \`change_mind({\"selector\":\"!goals\",\"content\":\"...\"})\``,
-                `- \`change_mind({\"selector\":\"!constraints\",\"content\":\"...\"})\``,
-                `- \`change_mind({\"selector\":\"!progress\",\"content\":\"...\"})\``,
+                `If any section is missing, create it with \`!?@change_mind\` (never via general file tools):`,
+                `- \`!?@change_mind !goals\\n!?<content>\``,
+                `- \`!?@change_mind !constraints\\n!?<content>\``,
+                `- \`!?@change_mind !progress\\n!?<content>\``,
             ].join('\n');
         })();
         const effectiveDoc = (0, task_package_1.formatEffectiveTaskDocFromSections)(language, sections);
@@ -164,7 +164,7 @@ If you provided a regular file path (e.g. a \`.md\`), that is unexpected. Please
 ${statusBlock}
 ⚠️ **注意：** 差遣牒是封装的。不要用文件工具去读/写/列目录 \`*.tsk/\` 下的任何路径。
-请用函数工具 \`change_mind\` 来更新（每次调用只更新一个分段；你可以在同一轮中多次调用来批量更新），例如：\`change_mind({\"selector\":\"!goals\",\"content\":\"...\"})\` / \`change_mind({\"selector\":\"!constraints\",\"content\":\"...\"})\` / \`change_mind({\"selector\":\"!progress\",\"content\":\"...\"})\`。`,
+请用 \`!?@change_mind !goals\` / \`!?@change_mind !constraints\` / \`!?@change_mind !progress\` 来更新（每次调用只更新一个分段；你可以在同一条消息里写多个 \`!?@change_mind\` 调用来批量更新）。`,
                 };
             }
             return {
@@ -177,7 +177,7 @@ ${statusBlock}
 ${statusBlock}
 ⚠️ **Note:** Task Docs are encapsulated. Do not use file tools to read/write/list anything under \`*.tsk/\`.
-Use the function tool \`change_mind\` to update (each call updates one section; you may call it multiple times in a single turn to batch updates), e.g. \`change_mind({\"selector\":\"!goals\",\"content\":\"...\"})\` / \`change_mind({\"selector\":\"!constraints\",\"content\":\"...\"})\` / \`change_mind({\"selector\":\"!progress\",\"content\":\"...\"})\`.`,
+Use \`!?@change_mind !goals\` / \`!?@change_mind !constraints\` / \`!?@change_mind !progress\` to update (each call updates one section; you may include multiple \`!?@change_mind\` calls in a single message to batch updates).`,
             };
         }
         if (language === 'zh') {
@@ -194,9 +194,9 @@ ${statusBlock}
 ${effectiveDoc}
 ---
-*用函数工具 \`change_mind\` 来替换分段（每次调用只替换一个分段；你可以在同一轮中多次调用来批量替换）。*
+*用 \`!?@change_mind !goals\` / \`!?@change_mind !constraints\` / \`!?@change_mind !progress\` 来替换分段（每次调用只替换一个分段；你可以在同一条消息里写多个 \`!?@change_mind\` 调用来批量替换）。*
-指令：不要对 \`*.tsk/\` 下的任何路径调用通用文件工具（\`read_file\`, \`overwrite_entire_file\`, \`preview_file_modification\`, \`apply_file_modification\`, \`list_dir\`, \`rm_file\`, \`rm_dir\`）。差遣牒状态只能通过显式的差遣牒操作进行管理。`,
+指令：不要对 \`*.tsk/\` 下的任何路径调用通用文件工具（\`!?@read_file\`, \`!?@replace_file_contents\`, \`!?@plan_file_modification\`, \`!?@apply_file_modification\`, \`!?@list_dir\`, \`!?@rm_file\`, \`!?@rm_dir\`）。差遣牒状态只能通过显式的差遣牒操作进行管理。`,
             };
         }
         return {
@@ -212,9 +212,9 @@ ${statusBlock}
 ${effectiveDoc}
 ---
-*Use the function tool \`change_mind\` to replace sections (each call replaces one section; you may call it multiple times in a single turn to batch replacements).*
+*Use \`!?@change_mind !goals\` / \`!?@change_mind !constraints\` / \`!?@change_mind !progress\` to replace sections (each call replaces one section; you may include multiple \`!?@change_mind\` calls in a single message to batch replacements).*
-Directive: Do not invoke any general file tools (\`read_file\`, \`overwrite_entire_file\`, \`preview_file_modification\`, \`apply_file_modification\`, \`list_dir\`, \`rm_file\`, \`rm_dir\`) on any path under \`*.tsk/\`. Task package state is managed only through explicit task-doc actions.`,
+Directive: Do not invoke any general file tools (\`!?@read_file\`, \`!?@replace_file_contents\`, \`!?@plan_file_modification\`, \`!?@apply_file_modification\`, \`!?@list_dir\`, \`!?@rm_file\`, \`!?@rm_dir\`) on any path under \`*.tsk/\`. Task package state is managed only through explicit task-doc actions.`,
         };
     }
     catch (error) {

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "dominds",
-  "version": "0.7.1",
+  "version": "0.7.3",
   "description": "DevOps Mindsets — Sustainable Agentic Product Lifecycle",
   "type": "commonjs",
   "private": false,

package/dist/docs/keep-going.zh.md DELETED Viewed

@@ -1,162 +0,0 @@
-# Keep-Going（鞭策）— 设计文档
-## 概述
-Dominds 根对话旨在长期运行。根对话"停止"（变为空闲）通常不是操作员想要的：他们希望智能体持续推进，直到：
-- 合法地暂停等待人类决策（Q4H），或
-- 合法地暂停等待子对话（tellask/backfill）。
-本文档指定了一个运行时机制（"keep-going"），仅针对**根/主对话**，防止对话停止：每当驱动程序即将停止时，它会自动发送一个简短的鞭策语（渲染为正常的用户气泡）并继续生成，除非对话处于合法暂停状态（Q4H 或待处理的子对话）。
-## 目标
-- 防止根对话停止，除非处于合法暂停状态（Q4H / 子对话）。
-- 保持行为可预测和有界（无无限循环）。
-- 使鞭策语文本可按工作区（rtws）和语言配置。
-- 提供清晰的用户控制的"禁用"机制。
-## 非目标
-- 自动完成/自动将对话标记为完成。
-- 将此行为应用于子对话（子对话保持范围，应向其调用者报告）。
-## 定义
-- **根/主对话**：`RootDialog`（`dlg.id.rootId === dlg.id.selfId`），主要对话线程。
-- **子对话**：`SubDialog`，为 tellask / 作用域工作创建。
-- **Q4H**："Questions for Human"，通过 `!?@human` 发起，暂停对话进度直到人类响应。
-## 预期的"正常"完成路径（推荐）
-当智能体需要人类决策来结束时（例如，确认选择或决定是否将对话标记为完成），正确的路径是：
-1. 智能体发出 Q4H（`!?@human`）并提供必要的上下文和明确的决策请求。
-2. WebUI 清楚地呈现 Q4H。
-3. 人类决定并：
-   - 手动将根对话标记为"完成"，或
-   - 提供请求的信息以便对话继续。
-这是"受控收敛"路径。keep-going 机制不应覆盖合法的暂停状态。
-## Keep-Going 行为（"自动继续"回退）
-### 触发条件（必须全部满足）
-- 对话是**根/主对话**（绝不会是子对话）。
-- 对话**未暂停**：
-  - 没有待处理的 Q4H，并且
-  - 没有待处理的子对话（等待回填）。
-- 驱动程序即将停止生成循环（即没有工具/函数输出需要另一次迭代）。
-### 操作
-运行时自动发送一个鞭策语（渲染为正常的用户气泡）并运行另一次生成迭代。
-### 有界性
-为避免无限循环，keep-going 有一个按对话的预算（每个成员的 `diligence-push-max`），控制对于给定对话在运行时强制 Q4H 暂停之前可以注入多少个自动继续的鞭策语。
-- 默认值：**3**
-- 如果 `< 1`，则该成员的 keep-going 有效禁用
-- 可通过 `.minds/team.yaml` 中的 `diligence-push-max` 按成员配置
-### Q4H 时重置
-当对话因待处理的 Q4H（Questions for Human）而暂停时，keep-going 注入计数器会被重置。这确保在人类回答 Q4H 并恢复对话后，对话会获得新的 keep-going 预算。
-### 预算耗尽 → 强制 Q4H
-当 keep-going 预算耗尽时，运行时会创建一个 Q4H 条目，询问人类是否继续或停止。这将"有界性"转换为合法的暂停点，并避免无限自动继续循环。
-### 禁用开关
-可以通过以下任一方式按 rtws 禁用 keep-going：
-- 如果选中的鞭策语文件存在但其内容为空/仅空白，则禁用 keep-going（不注入）。
-可以通过以下任一方式按成员禁用 keep-going：
-- 如果 `diligence-push-max < 1`，则该成员的 keep-going 被禁用（不注入）。
-## 鞭策语解析
-让 `<rtws>` 为当前运行时工作区（即 `process.cwd()`）。
-解析顺序：
-1. `<rtws>/.minds/diligence.<work-lang-id>.md`（例如，`diligence.zh.md`）
-2. `<rtws>/.minds/diligence.md`（语言无关的回退）
-3. 内置回退文本（硬编码的 i18n；`zh` 是规范的并嵌入在源代码中）
-如果上述顺序中第一个存在的文件具有空/空白内容，则**禁用** keep-going。
-注意：鞭策语文件中的 YAML frontmatter 会被运行时忽略。如果存在，它被视为非内容元数据并从提示正文中剥离。
-### 团队成员上限：`diligence-push-max`
-每个团队成员可以选择通过 `.minds/team.yaml` 限制 keep-going：
-```yaml
-members:
-  alice:
-    diligence-push-max: 10
-```
-规则：
-- 如果缺失，`diligence-push-max` 对于该成员默认为 **3**。
-- 如果 `diligence-push-max < 1`，则该成员的 keep-going 被禁用（不注入），即使鞭策语文件存在。
-- 内置影子成员 `fuxi` 和 `pangu` 默认为 `diligence-push-max: 0`，除非在 team.yaml 中显式覆盖。
-## UX 备注
-- Keep-going 是一个仅运行时的提示，但它应该是**可见的**：鞭策语渲染为正常的用户消息气泡（由运行时自动发送），以便操作员理解为什么会出现额外的迭代。
-- 用户应该观察到智能体在仅工具操作后继续简短的跟进。
-- 当智能体真正需要用户干预时，它应该使用 Q4H。Keep-going 不应试图"假装"完成。
-## 实现（后端）
-### 位置
-在 LLM 驱动程序循环中实现（`dominds/main/llm/driver.ts`），作为迭代后的小检查：
-1. 如果 `suspendForHuman` 为 true，则停止（Q4H / 子对话待处理）。
-2. 如果有任何工具反馈，则正常继续。
-3. 否则（仅限根），尝试 keep-going 自动继续：
-   - 如果禁用 → 正常停止。
-   - 如果预算耗尽 → 创建 Q4H 并停止。
-   - 否则 → 自动发送鞭策语并继续。
-### 消息类型
-我们将鞭策语作为自动发送的用户消息注入：
-- 类型为 `prompting_msg`、角色为 `'user'` 的 `ChatMessage`
-这确保了：
-- 它存在于模型上下文中
-- 它作为人类消息记录持久化
-- 它在聊天时间线中渲染为正常的用户气泡（像任何其他用户消息一样）
-## 可观察性
-建议的后续步骤（初始实现不需要）：
-- 当触发 keep-going 时添加结构化日志行，包括：
-  - 对话 id
-  - 语言
-  - 使用的鞭策语来源（语言特定/通用/内置/禁用）
-- 为"keep-going 触发"和"keep-going 因空文件禁用"添加可选的指标计数器。
-## 测试
-回归测试应覆盖：
-- 根对话：仅工具输出 → 鞭策语注入 → 继续响应
-- 根对话：空助手输出 → 鞭策语注入 → 继续响应
-- 子对话：无鞭策语注入
-- 工作区配置：
-  - 当语言特定文件缺失时，`.minds/diligence.md` 被遵守
-  - 空的鞭策语文件禁用 keep-going

package/dist/docs/showing-by-doing.md DELETED Viewed

@@ -1,208 +0,0 @@
-# Showing-by-Doing (做给祂看): Make Tellask Real
-Chinese version: [中文版](./showing-by-doing.zh.md)
-## Summary
-Dominds has a real, runtime-enforced Tellask mechanism (`!?@...`) and a real, runtime-enforced Fresh Boots Reasoning
-(FBR) mechanism (`!?@self`). Even if system prompts explain these mechanisms in detail, most foundation models were not
-trained in a world where “asking a teammate to run a shell command” is actually possible, so they often treat such text
-as aspirational or hypothetical.
-**Showing-by-Doing (做给祂看)** is a tiny, highly realistic “first impression” procedure executed at dialog creation
-time. It runs a short, real Tellask + real FBR round-trip so the model gains _felt-sense_ that:
-- teammate Tellasks are real and will be executed
-- tool outputs are real and will be returned
-- FBR is real and will produce a report back to the caller
-This makes subsequent use of Tellasks and `!?@self` FBR more reliable across the entire dialog lifecycle.
-As a consequence, we can **dramatically simplify system prompts**: keep only short, accurate statements of the Tellask/FBR
-contracts, and rely on Showing-by-Doing to establish “this is real and works here”.
-Related docs:
-- Tellask runtime: `dominds/docs/dialog-system.md`
-- Terminology (Mainline/Sideline): `dominds/docs/dominds-terminology.md`
-- FBR (`!?@self`): `dominds/docs/fbr.md`
-- Work language vs UI language: `dominds/docs/i18n.md`
----
-## Goals
-- Establish immediate trust that **Tellask is not “just prompt text”**: it is an executable, backend-driven mechanism.
-- Establish immediate trust that **FBR is not “just reasoning”**: it is a concrete sideline dialog that reports back.
-- Keep the procedure safe, small, and deterministic (default command: `uname -a`).
-- Persist and display the interaction so it is credible from multiple angles (backend record + frontend transcript).
-## Non-goals
-- Running arbitrary user-provided commands as part of dialog creation.
-- Collecting sensitive system information (beyond minimal OS/kernel identification).
-- Replacing proper documentation: this is an experiential supplement, not the main spec.
----
-## Definitions (user-facing)
-- **Mainline dialog**: the primary thread where the user and the main agent interact.
-- **Sideline dialog**: a temporary work thread created by Tellask / FBR, reporting results back to the mainline.
-- **Tellask**: a structured request (`!?@<memberId> ...`) from a tellasker to a tellaskee.
-- **Shell specialist**: a teammate designated to run shell commands safely (configured via `shell_specialists`).
-- **FBR**: Fresh Boots Reasoning, implemented as `!?@self` (a tool-less sideline dialog). See `dominds/docs/fbr.md`.
----
-## Runtime flow (at dialog creation)
-Showing-by-Doing runs **before** the first user message is processed (a “prelude”), unless the user opts out.
-### 1) Choose the shell execution path
-1. If the team config includes at least one `shell_specialists` member, pick one deterministically (e.g. the first).
-2. Otherwise, let the **Dominds runtime** execute the baseline command directly (not via agent tools).
-Note: team config validation normally requires `shell_specialists` to be non-empty if any teammate has shell tools, and
-also requires that only listed shell specialists have shell tools. In other words, “no `shell_specialists` configured”
-usually means “shell tools are disabled for all user-facing teammates”.
-Baseline command:
-- `uname -a`
-If `uname -a` fails (e.g. non-POSIX host), the runtime should fall back to a platform-appropriate equivalent, but the
-default “muscle memory” path is intentionally `uname -a` because it is common, low-risk, and quick.
-### 2) Real teammate Tellask: ask for `uname -a`
-If a shell specialist exists, the main agent (tellasker) issues **a real Tellask** to the shell specialist (tellaskee),
-in the server-wide **work language** (see `dominds/docs/i18n.md`).
-The Tellask body should be short and operational:
-- ask the shell specialist to run `uname -a`
-- ask them to return the raw output verbatim
-- ask them to include an error + alternative command if `uname` is not available
-The result must be recorded as a normal, debuggable transcript that clearly shows:
-- the Tellask headline + body
-- the shell specialist’s command execution
-- the returned output
-Minimal configuration example:
-```yaml
-# .minds/team.yaml
-shell_specialists:
-  - cmdr
-```
-### 3) Real FBR: reflect on what the environment implies
-After obtaining the environment snapshot (from the shell specialist or direct tool run), the main agent issues a real
-`!?@self` Tellask to trigger **FBR**.
-The FBR Tellask body should include:
-- the exact `uname -a` output
-- the main agent’s tool availability assumptions (e.g. “in mainline I may have `fs`/`os`/`mem`; in FBR you have no tools”)
-- the question: “What should I be careful about in this environment? Which CLI tools should I prioritize, and why?”
-The FBR response should return a compact report that the main agent can reuse, typically:
-- environment notes (OS family, kernel, container/VM hints if any)
-- do/don’t list (pitfalls)
-- a short “preferred commands” shortlist (e.g. `rg`, `sed`, `jq`, `tar`, `ps`, `lsof`, depending on host)
-### 4) Summarize into an “Environment Quickstart” note
-The main agent then writes a short, user-visible summary to the mainline dialog so the knowledge is explicit and
-searchable in the transcript.
----
-## Fallback behavior
-Showing-by-Doing should degrade gracefully:
-- **No `shell_specialists` configured**: the Dominds runtime runs `uname -a` directly, then do FBR.
-- **Shell specialist fails or times out**: the Dominds runtime runs `uname -a` directly and continue, marking the
-  specialist attempt as failed in the transcript.
-- **`uname` not available / command fails**: run FBR with “environment unknown”; the report should explicitly list what
-  is missing and suggest what to gather later.
----
-## Persistence, caching, and reuse
-### 1) Persist as real dialog records (backend + frontend)
-All Showing-by-Doing steps must be persisted as standard dialog artifacts (messages + events) so they remain credible:
-- they survive restarts (subject to normal dialog persistence rules)
-- they are debuggable in logs/storage
-- they are rendered in the WebUI transcript (ideally as a collapsible “Prelude” section)
-### 2) Process-wide cache (per teammate)
-To avoid repeating `uname -a` + FBR on every new dialog, the backend process may maintain a **server-scoped cache** keyed
-by (at minimum):
-- tellasker teammate id (the agent whose dialogs are being created)
-- an environment fingerprint derived from the `uname -a` output (exact string or hashed)
-Cache payload (recommended):
-- the full Showing-by-Doing transcript (Tellask + output + FBR + summary)
-- a short “Environment Quickstart” distilled form (for compact context injection)
-- timestamps + a version tag for future schema changes
-Reuse policy:
-- If a valid cache entry exists, a new dialog may **reuse** the cached transcript instead of re-running.
-- Reused entries should still be visible in the new dialog’s transcript, clearly labeled as “Reused from cache”.
-Invalidation (recommended):
-- invalidate when the environment fingerprint changes
-- allow a manual “Refresh environment snapshot” action for debugging
-### 3) Carry across `clear_mind`
-After each `clear_mind` (entering the next “journey stage”), do **not** rely on reminders for this.
-Instead, inject a small, stable **course prefix** into the model context at the start of each new course (i.e. the first
-few messages in the historical dialog section). This prefix should be a condensed transcript distilled from the original
-Showing-by-Doing run (shell snapshot + FBR highlights + quickstart), so the agent keeps its “felt-sense” of Tellask/FBR
-and environment constraints without re-running the prelude.
----
-## UX requirements (WebUI)
-### Display
-- Render Showing-by-Doing as a realistic transcript the user can inspect.
-- Prefer a collapsible “Prelude” section at the top of the dialog, with clear labels:
-  - “Teammate Tellask (shell)”
-  - “FBR (`!?@self`)”
-  - “Environment Quickstart”
-### Opt-out
-The dialog creation UI should include an explicit opt-out, e.g.:
-- Checkbox: “Skip Showing-by-Doing (do not run environment prelude)”
-If opted out, no prelude actions are executed and no prelude transcript is generated.
----
-## Safety notes
-- Default to a single, low-risk command (`uname -a`).
-- Do not run anything that modifies the filesystem or network as part of this prelude.
-- Treat the prelude transcript as user-visible by default; avoid including secrets or personally identifying details.