@yangdcm/dsh-expert-team 1.3.8 → 1.3.9
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.
- package/CHANGELOG.md +12 -0
- package/README.en.md +8 -4
- package/README.md +8 -4
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,18 @@
|
|
|
3
3
|
本包遵循[语义化版本](https://semver.org/lang/zh-CN/)。dsh 宿主版本线的对应关系写在
|
|
4
4
|
`package.json` 的 `engines.dsh` 与 `dsh.compatibility` 里，插件市场按它判断"这个插件跟你的宿主兼不兼容"。
|
|
5
5
|
|
|
6
|
+
## 1.3.9
|
|
7
|
+
|
|
8
|
+
**新增第二张真实画布截图：`事` 视图（任务依赖图）**（纯文档/资产：`lib/`、`client.js` 零改动）。
|
|
9
|
+
|
|
10
|
+
- 素材：真实 `dsh web` 全屏画布的 **`事 11`** 子标签 —— 11 个任务按依赖 DAG 并行推进，图例显示「已完成 7 / 失败 4」；
|
|
11
|
+
任务卡带 `T-01…T-05`、`repair-1/2`、`review-2/3`、`test-3` 与「任务·角色·判定」，节点右侧是轮次标记（`r3-a1` / `r2-a1`）。
|
|
12
|
+
它同时展示 **DAG 并行** 与 **失败的返工闭环**（`repair-1 → review-2 → repair-2 → review-3`）。
|
|
13
|
+
- 裁切：`sips -c 570 1005 --cropOffset 85 275`，去掉左侧工作区 / 会话侧栏与底部合成器 + 费用页脚，产物 **1005×570**（120 KB）。
|
|
14
|
+
- 核验（不靠肉眼）：用 Node `zlib` **直接解 PNG 字节**（不经过 `sips` 探针）抽样 7 个点，
|
|
15
|
+
裁图 `(x,y)` 与源图 `(x+275, y+85)` **逐像素相同** ⇒ 偏移精确、无像素改动。
|
|
16
|
+
- README(中英)：作为**图 3**（`Figure 3`）放在全屏画布（人）之后、三张窄浮层截图之前；其后图号顺延为图 4–7。
|
|
17
|
+
|
|
6
18
|
## 1.3.8
|
|
7
19
|
|
|
8
20
|
**定位前置 + 真实画布截图**（纯文档/资产版本 —— `lib/`、`client.js` 零改动）。
|
package/README.en.md
CHANGED
|
@@ -100,26 +100,30 @@ answer them:
|
|
|
100
100
|
|
|
101
101
|
<sub>Figure 2: **the full-screen canvas**. Look at the phase bar and progress, the roster (who is running, on which model), and the four views (people / tasks / artifacts / board) — one layer above the floating panel.</sub>
|
|
102
102
|
|
|
103
|
+
|
|
104
|
+
|
|
105
|
+
<sub>Figure 3: **the task dependency graph** — 11 tasks advance in parallel along the dependency DAG; 7 completed, 4 failed. A failure triggers `repair` plus **independent re-verification** (`repair-1 → review-2 → repair-2 → review-3`) until it passes or is honestly marked as needing revision — this is what the "rework does not converge" hard gate looks like in a real run.</sub>
|
|
106
|
+
|
|
103
107
|
|
|
104
108
|
|
|
105
|
-
<sub>Figure
|
|
109
|
+
<sub>Figure 4: **gate violations**. Look at the banner at the top — the violation and its refusal reason
|
|
106
110
|
(e.g. "SPEC.md's boundary section has entered `implement` but still has no 'expected rejection' row")
|
|
107
111
|
is decided by `lib/interception.js`, hooked onto the host's `tools/post-execute` waterfall, and surfaced
|
|
108
112
|
immediately. This is code, not a prompt reminder.</sub>
|
|
109
113
|
|
|
110
114
|
|
|
111
115
|
|
|
112
|
-
<sub>Figure
|
|
116
|
+
<sub>Figure 5: **the roster**. Look at the member list — who is running, on which model, and what it is doing;
|
|
113
117
|
expand a member for its tasks and artifacts. Models are configurable per role; heterogeneous models are used for cross-checking.</sub>
|
|
114
118
|
|
|
115
119
|
|
|
116
120
|
|
|
117
|
-
<sub>Figure
|
|
121
|
+
<sub>Figure 6: **phases and artifacts**. Look at the phase bar and the preview pane — the current phase, the phases
|
|
118
122
|
already passed, and the actual body of the artifact written in that phase (artifacts are the single source of truth; the overlay is just a view of them).</sub>
|
|
119
123
|
|
|
120
124
|
|
|
121
125
|
|
|
122
|
-
<sub>Figure
|
|
126
|
+
<sub>Figure 7: **settings**. Look at the official `Settings → Expert team` page — 18 settings, Chinese labels,
|
|
123
127
|
**saved on change and applied immediately** (caps, rounds, the tier gate and the oscillation detector are recomputed
|
|
124
128
|
in-process). Values live in the host namespace `expert-team`, so they travel with the plugin market's backup/restore.</sub>
|
|
125
129
|
|
package/README.md
CHANGED
|
@@ -91,21 +91,25 @@ $ /team 做一个带登录的支付模块
|
|
|
91
91
|
|
|
92
92
|
<sub>图 2：**全屏画布**。看阶段条与进度、团队编制（谁在跑、用哪个模型）、以及 `人 / 事 / 料 / 盘` 四个视角 —— 比浮层更完整的一层视图。</sub>
|
|
93
93
|
|
|
94
|
+
|
|
95
|
+
|
|
96
|
+
<sub>图 3：**任务依赖图** —— 11 个任务按依赖 DAG 并行推进；7 个完成、4 个失败。失败会触发 `repair` 与**独立复验**（`repair-1 → review-2 → repair-2 → review-3`），直到通过或被如实判为需修订 —— 这就是「返工不收敛」的硬门禁在真实运行里的样子。</sub>
|
|
97
|
+
|
|
94
98
|
|
|
95
99
|
|
|
96
|
-
<sub>图
|
|
100
|
+
<sub>图 4：**门禁违规**。看顶部那条横幅 —— 违规项与拒绝理由（例如"SPEC.md 的边界章节已进入 `implement` 但仍无任何一行填写"）由 `lib/interception.js` 挂在宿主 `tools/post-execute` 上当场判出后推出，不是提示词提醒。</sub>
|
|
97
101
|
|
|
98
102
|
|
|
99
103
|
|
|
100
|
-
<sub>图
|
|
104
|
+
<sub>图 5：**角色编制**。看成员列表 —— 谁在跑、用哪个模型、当前在做什么；展开任一成员可看它的任务与产物。模型可按角色分别配置，异构模型用于交叉验证。</sub>
|
|
101
105
|
|
|
102
106
|
|
|
103
107
|
|
|
104
|
-
<sub>图
|
|
108
|
+
<sub>图 6：**阶段与工件**。看阶段条与预览区 —— 当前阶段、已过阶段、以及该阶段真正写下的工件正文（工件是唯一真源，浮层只是它的视图）。</sub>
|
|
105
109
|
|
|
106
110
|
|
|
107
111
|
|
|
108
|
-
<sub>图
|
|
112
|
+
<sub>图 7：**设置**。看官方 `设置 →「专家团」` 这一页 —— 18 个设置项、中文标签、**改动即保存并即时生效**（上限/轮次/档位门/振荡检测在进程内重算）；值存在宿主命名空间 `expert-team`，随插件市场的备份/恢复一起走。</sub>
|
|
109
113
|
|
|
110
114
|
## 它为什么可靠
|
|
111
115
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@yangdcm/dsh-expert-team",
|
|
3
|
-
"version": "1.3.
|
|
3
|
+
"version": "1.3.9",
|
|
4
4
|
"description": "dsh「专家团」bundle：一句自然语言自动组建/持久化一支 12 角色多智能体团队，共享工作区协议 + 阶段门控编排 + 结构化交接 + 质量门禁/自动调度，实现者直接改代码并产出持久工件；带 live 团队浮层（质量门禁/覆盖率/工件预览）。 · Role-based multi-agent expert team for DeepSeek Harness: one sentence in, a staged and gated team delivery out.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"license": "MIT",
|