dsh-lead-mode 0.1.4 → 0.1.6

package/README.md

@@ -114,6 +114,37 @@ Three steps.
 
 **3. Let the model work.** With the delegation tools in place, the model splits the work, delegates to teammates, and waits for all of them before wrapping up. Without them, its first move is to tell you to enable the Team runtime.
 
+## Friendly link: dsh-context
+
+This plugin only does Lead mode. Visualising Team state and comms is **dsh-context**'s job, and that is a separate project:
+
+| Item | Value |
+|---|---|
+| Repository | https://github.com/bowenliang123/dsh-context |
+| Author | bowenliang123 |
+| License | Apache-2.0 |
+| Install | `dsh plugin --profile <your profile name> add dsh-context` |
+
+It does not ship with this plugin, and it is not a dependency of it. This plugin only points at it from the docs and the skill.
+
+### Why point there at all
+
+Tool calls read one at a time. `list_agents` gives one line of status; `team_task_list` gives task ownership. Seeing who is doing what, and who said what to whom, takes a page.
+
+dsh-context adds a **Fleet / 编队** tab to every session (right of **Context**), and the right sidebar's **Context** panel carries the same card.
+
+| Surface | Shows |
+|---|---|
+| Summary | Member status, live context, estimated cost, task progress |
+| Agent Network | The current agent, its parents, every subagent, one card each |
+| Fleet Members | Each member's role, model, latest reply, run time, steps, active task count |
+| Tasks | Team tasks and subagent delegations together, grouped by owner, with blocked-by chains |
+| Agent Comms | Who said what to whom. Team relays, mailbox deliveries, and the runtime's settlement notices |
+
+Picking a member on the graph or the member board narrows Tasks and Agent Comms to that one agent. Opening a message in Agent Comms shows the full record: which session log it came from, its sequence, whether the runtime wrote the settlement notice or the child sent it, and the complete closing report.
+
+The Lead mode skill names this entry point too, so the model points you here instead of restating progress itself.
+
 ## Required official bundles and versions
 
 This plugin ships none of the packages below. The host or an official bundle provides them; this plugin only declares version requirements in `peerDependencies`.

package/README.zh-CN.md

@@ -114,6 +114,37 @@ dsh plugin --profile <你的 profile 名> add https://github.com/xiebaiyuan/dsh-
 
 **3. 让模型干活。** 派活工具齐了，模型会自己拆活、派给 teammate、等齐再收尾。工具不齐，它第一句就是让你去开 Team 运行时。
 
+## 友链：dsh-context
+
+本插件只做 Lead 模式。团队状态与通信的可视化是 **dsh-context** 的活，那是另一个项目：
+
+| 项 | 值 |
+|---|---|
+| 仓库 | https://github.com/bowenliang123/dsh-context |
+| 作者 | bowenliang123 |
+| 许可 | Apache-2.0 |
+| 装法 | `dsh plugin --profile <你的 profile 名> add dsh-context` |
+
+它不随本插件安装，也不是本插件的依赖。本插件只在文档和 skill 里指个路。
+
+### 为什么指到这里
+
+工具调用只能一条条读。`list_agents` 给一行状态，`team_task_list` 给任务归属。要看整队谁在干什么、谁跟谁说了什么，得开一页。
+
+dsh-context 在每个会话里加一个 **编队 / Fleet** 标签页（在 **Context** 右边），右栏的 **Context** 面板里有同一张卡。
+
+| 区块 | 看什么 |
+|---|---|
+| 概要 | 成员状态、实时上下文、预估花费、任务进度 |
+| Agent Network | 当前 agent、它的父级、全部子代理，一人一张卡 |
+| Fleet Members | 每个成员的角色、模型、最新回复、运行时长、步数、在办任务数 |
+| Tasks | 团队任务与子代理派活放一起，按 owner 分组，带 blocked-by 链 |
+| Agent Comms | 谁跟谁说了什么。团队消息、邮箱投递、运行时的结算通知都在这里 |
+
+点图上的成员或成员卡，Tasks 与 Agent Comms 会收窄到那一个人。Agent Comms 里点开一条能看到完整记录：来自哪个会话日志、第几号事件、是运行时写的结算通知还是子代理自己发的、完整收尾报告。
+
+Lead 模式 skill 里也写了这个入口，所以派活时模型会直接让你去这儿看进度。
+
 ## 依赖的官方 bundle 与版本
 
 本插件不捆绑下面这些包。它们由宿主或官方 bundle 提供，本插件只在 `peerDependencies` 里声明版本要求。

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-lead-mode",
-  "version": "0.1.4",
+  "version": "0.1.6",
   "description": "Lead mode for DSH: an agent preset, a working-method skill, a dependency self-check, and two reminders that tell you to enable the official Agent Teams. | 给 DSH 加 Lead 模式：预设、skill、依赖自检、两条前置提醒。",
   "type": "module",
   "main": "lib/index.js",

package/skills/lead-mode/SKILL.md

@@ -159,6 +159,28 @@ teammate 继承你（Lead）在 spawn 那一刻的 provider 和 model。想换
 
 只有 Lead 能创建和打断 teammate（`interrupt_agent`）。打断不清空它排队的消息。
 
+### 想看全局，用 dsh-context 的编队页
+
+工具调用只能一条条读。要看整队的工作与通信，让用户开 **dsh-context** 的编队页。
+
+那是另一个项目，不随本插件安装，也不是本插件的依赖。仓库：https://github.com/bowenliang123/dsh-context（作者 bowenliang123，Apache-2.0）。
+
+装法：`dsh plugin --profile <你的 profile 名> add dsh-context`
+
+| 区块 | 看什么 |
+|---|---|
+| 概要 | 成员状态、实时上下文、预估花费、任务进度 |
+| Agent Network | 当前 agent、父级、全部子代理，一人一张卡 |
+| Fleet Members | 每个成员的角色、模型、最新回复、运行时长、步数、在办任务数 |
+| Tasks | 团队任务与子代理派活放一起，按 owner 分组，带 blocked-by 链 |
+| Agent Comms | 谁跟谁说了什么。团队消息、邮箱投递、运行时的结算通知都在这里 |
+
+入口：任意会话点 **编队 / Fleet** 标签页（在 **Context** 右边）。右栏的 **Context** 面板里有同一张卡。
+
+只有用户装了它，这个入口才存在。不确定就别让用户去找一个没有的页面。
+
+派活时可以直接告诉用户去这儿看进度，比自己复述一遍更清楚。
+
 ## 给最终答复前
 
 - 必需的 teammate 都等齐了再答。没等齐就说「还在跑」，别把半成品当结论。