@yangdcm/dsh-expert-team 1.3.6 → 1.3.7
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 +46 -0
- package/README.en.md +7 -7
- package/README.md +7 -7
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,52 @@
|
|
|
3
3
|
本包遵循[语义化版本](https://semver.org/lang/zh-CN/)。dsh 宿主版本线的对应关系写在
|
|
4
4
|
`package.json` 的 `engines.dsh` 与 `dsh.compatibility` 里，插件市场按它判断"这个插件跟你的宿主兼不兼容"。
|
|
5
5
|
|
|
6
|
+
## 1.3.7
|
|
7
|
+
|
|
8
|
+
**修掉 1.3.6 两张手绘矢量图的文字重叠，并让 npm 页面也能显示 README 图片。**
|
|
9
|
+
|
|
10
|
+
纯文档/资产版本 —— `lib/`、`client.js` **零改动**，无依赖变化，`files` 字段未动。
|
|
11
|
+
|
|
12
|
+
### 两张 SVG：改为**分带布局**（band layout）
|
|
13
|
+
|
|
14
|
+
上一版的问题不是"画得不好"，而是**两条信息共用了同一 y 带**：
|
|
15
|
+
|
|
16
|
+
- `hero.svg`：指标行与副标题同带 ⇒ 大数字 `12` **压在副标题尾部**；副标题/页脚在深底上对比度偏低。
|
|
17
|
+
- `pipeline.svg`：「硬门」徽标与图例行同带 ⇒ 徽标**压住图例第三项**「同一阶段内并行扇出」，
|
|
18
|
+
「确认门」徽标也飘在图例那一行而不是它注记的方框上方。
|
|
19
|
+
|
|
20
|
+
改法：每张图先把垂直空间切成**互不重叠的带**，每个元素**只能落在自己的带内**，带范围写进文件注释便于后续修改。
|
|
21
|
+
|
|
22
|
+
- `hero.svg` 带表：B1 标题 `[44,84]` · B2 副标题 `[88,114]` · B3 命令框（左 x≤600）/ 指标（右 x≥636）`[118,178]`
|
|
23
|
+
· B4 进度条 `[190,210]` · B5 页脚 `[218,246]`。指标整体下移，数字与图注留 7px 净空；
|
|
24
|
+
副标题 `#94a3b8 → #c7d2fe`、页脚 `→ #a5b4fc`（深底对比度）。
|
|
25
|
+
- `pipeline.svg` 带表：B1 标题 `[30,60]` · B2 副标题 `[62,82]` · B3 图例 `[86,104]` · **B4 门徽标 `[110,136]`（独占一带）**
|
|
26
|
+
· B5 阶段行 `[140,212]` · B6 并行扇出 `[212,330]` · B7 角色 chip `[334,382]` · B8 工件脚注 `[400,440]`。
|
|
27
|
+
两个徽标各自落在**它注记的方框正上方**（硬门 → 规格评审 `x 428..532`；确认门 → 方案确认 `x 548..652`，
|
|
28
|
+
徽标 x 区间被断言**包含于**对应方框）；阶段行下移 24px，全图高度 `430 → 460`；阶段间箭头的线段改为在箭头**起点**处结束，
|
|
29
|
+
不再与箭头包围盒相交。
|
|
30
|
+
|
|
31
|
+
信息量未减：9 阶段、硬门/确认门的区分（规格评审=硬门；方案确认=确认门，默认开启、可在设置里关）、
|
|
32
|
+
DAG 并行扇出、角色 chip、工件脚注全部保留。
|
|
33
|
+
|
|
34
|
+
### 类级防复发：**真重叠自检**（这一环上一轮缺失）
|
|
35
|
+
|
|
36
|
+
上一轮只做了"矩形不越界"的几何自检，**抓不到"文字压文字"**。本次补上一次性自检脚本（`/tmp`，不提交）：
|
|
37
|
+
|
|
38
|
+
- 对每个 `<text>`/`<rect>`/`<path>` **估算包围盒**（CJK/全角按 `1.0em`、拉丁/数字按 `0.6em`，高 `1.2×font-size`，
|
|
39
|
+
上 `0.9` / 下 `0.3` 于基线；`path` 按 `M/H/V/L/l/v` 逐段追踪绝对坐标）；
|
|
40
|
+
- **两两检测"部分相交"**（完全包含＝父子/背景关系，允许并单独列出）；
|
|
41
|
+
- **校验元素不跨带**（强制分带布局）；另做 x 越界与"徽标在对应方框正上方"的语义断言。
|
|
42
|
+
|
|
43
|
+
有效性验证：脚本先对 **1.3.6 的两张图**运行，**复现了报告里的两处重叠**（坐标级：副标题 `64,95.4→682.8,112.2` × `12` `636,94.8→669.6,128.4`；
|
|
44
|
+
`rect@446,88` × 图例第三项 `420,96.1→519,109.3`）；修复后两张图 **0 部分相交、0 跨带**（hero 190 对、pipeline 3403 对比较）。
|
|
45
|
+
|
|
46
|
+
### npm 页面上的 README 图片
|
|
47
|
+
|
|
48
|
+
`files` 未含 `docs/` ⇒ README 里的**相对**路径在 npm 页面渲染不到。改为**绝对地址**
|
|
49
|
+
`https://raw.githubusercontent.com/yangdcm/dsh-expert-team/main/docs/images/<file>`（中英各 6 处），
|
|
50
|
+
`LICENSE` 链接同样改为绝对地址。这样 GitHub、npm、以及将来插件市场的抽图都能用，且**不必**动 `files`（不增大产物）。
|
|
51
|
+
|
|
6
52
|
## 1.3.6
|
|
7
53
|
|
|
8
54
|
**文档与素材：README 重写成"能一眼看懂它在干什么"的结构，并补上手绘矢量图。**
|
package/README.en.md
CHANGED
|
@@ -3,10 +3,10 @@
|
|
|
3
3
|
English | [中文](README.md)
|
|
4
4
|
|
|
5
5
|
[](https://www.npmjs.com/package/@yangdcm/dsh-expert-team)
|
|
6
|
-
[](LICENSE)
|
|
6
|
+
[](https://github.com/yangdcm/dsh-expert-team/blob/main/LICENSE)
|
|
7
7
|
[](https://github.com/yangdcm/dsh-expert-team/actions/workflows/ci.yml)
|
|
8
8
|
|
|
9
|
-
|
|
9
|
+
|
|
10
10
|
|
|
11
11
|
> **One sentence in, a gated team delivery out.** `/team build a payments module with login`
|
|
12
12
|
> assembles a 12-role expert team and runs
|
|
@@ -20,7 +20,7 @@ A plugin for [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness)
|
|
|
20
20
|
|---|---|---|---|---|
|
|
21
21
|
| own persona / `toolFilter` / `maxDepth: 1` | 1 hard gate + 1 approval gate | incl. a 136-entry mutation catalog and several ratchets | `dependencies: {}` | no bundler, no `prepare` hook |
|
|
22
22
|
|
|
23
|
-
|
|
23
|
+
|
|
24
24
|
|
|
25
25
|
<sub>Figure 1: the 9-phase gated pipeline. `spec-review` is a **hard gate** — if the SPEC.md
|
|
26
26
|
"boundaries and prohibitions" section is empty, the run does not advance (`lib/interception.js`).
|
|
@@ -67,24 +67,24 @@ answer them:
|
|
|
67
67
|
|
|
68
68
|
## What it looks like in action
|
|
69
69
|
|
|
70
|
-
|
|
70
|
+
|
|
71
71
|
|
|
72
72
|
<sub>Figure 2: **gate violations**. Look at the banner at the top — the violation and its refusal reason
|
|
73
73
|
(e.g. "SPEC.md's boundary section has entered `implement` but still has no 'expected rejection' row")
|
|
74
74
|
is decided by `lib/interception.js`, hooked onto the host's `tools/post-execute` waterfall, and surfaced
|
|
75
75
|
immediately. This is code, not a prompt reminder.</sub>
|
|
76
76
|
|
|
77
|
-
|
|
77
|
+
|
|
78
78
|
|
|
79
79
|
<sub>Figure 3: **the roster**. Look at the member list — who is running, on which model, and what it is doing;
|
|
80
80
|
expand a member for its tasks and artifacts. Models are configurable per role; heterogeneous models are used for cross-checking.</sub>
|
|
81
81
|
|
|
82
|
-
|
|
82
|
+
|
|
83
83
|
|
|
84
84
|
<sub>Figure 4: **phases and artifacts**. Look at the phase bar and the preview pane — the current phase, the phases
|
|
85
85
|
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>
|
|
86
86
|
|
|
87
|
-
|
|
87
|
+
|
|
88
88
|
|
|
89
89
|
<sub>Figure 5: **settings**. Look at the official `Settings → Expert team` page — 18 settings, Chinese labels,
|
|
90
90
|
**saved on change and applied immediately** (caps, rounds, the tier gate and the oscillation detector are recomputed
|
package/README.md
CHANGED
|
@@ -3,10 +3,10 @@
|
|
|
3
3
|
[English](README.en.md) | 中文
|
|
4
4
|
|
|
5
5
|
[](https://www.npmjs.com/package/@yangdcm/dsh-expert-team)
|
|
6
|
-
[](LICENSE)
|
|
6
|
+
[](https://github.com/yangdcm/dsh-expert-team/blob/main/LICENSE)
|
|
7
7
|
[](https://github.com/yangdcm/dsh-expert-team/actions/workflows/ci.yml)
|
|
8
8
|
|
|
9
|
-
|
|
9
|
+
|
|
10
10
|
|
|
11
11
|
> **一句话组队交付**：`/team 做一个带登录的支付模块` —— 自动组建 12 角色专家团，走
|
|
12
12
|
> 澄清 → 调研 → 设计 → 规格评审 → 方案确认 → 实现 → 审查 → 测试 → 交付 的门控流水线，
|
|
@@ -18,7 +18,7 @@
|
|
|
18
18
|
|---|---|---|---|---|
|
|
19
19
|
| 各带人设 / `toolFilter` / `maxDepth: 1` | 含 1 道硬门 + 1 道确认门 | 含 136 条变异目录与多组棘轮 | `dependencies: {}` | 无 bundler、无 `prepare` 钩子 |
|
|
20
20
|
|
|
21
|
-
|
|
21
|
+
|
|
22
22
|
|
|
23
23
|
<sub>图 1：9 阶段门控流水线。「规格评审」是**硬门** —— SPEC.md 的「边界与禁止项」没填就不放行（`lib/interception.js`）；「方案确认」是默认开启的**确认门**（`identity.keepPlanGate`，可在设置里关掉）；「实现」阶段按依赖 DAG **并行扇出**，多个实现者同时开工、各自只改自己那份文件。</sub>
|
|
24
24
|
|
|
@@ -59,19 +59,19 @@ $ /team 做一个带登录的支付模块
|
|
|
59
59
|
|
|
60
60
|
## 看一眼它在干什么
|
|
61
61
|
|
|
62
|
-
|
|
62
|
+
|
|
63
63
|
|
|
64
64
|
<sub>图 2：**门禁违规**。看顶部那条横幅 —— 违规项与拒绝理由（例如"SPEC.md 的边界章节已进入 `implement` 但仍无任何一行填写"）由 `lib/interception.js` 挂在宿主 `tools/post-execute` 上当场判出后推出，不是提示词提醒。</sub>
|
|
65
65
|
|
|
66
|
-
|
|
66
|
+
|
|
67
67
|
|
|
68
68
|
<sub>图 3：**角色编制**。看成员列表 —— 谁在跑、用哪个模型、当前在做什么；展开任一成员可看它的任务与产物。模型可按角色分别配置，异构模型用于交叉验证。</sub>
|
|
69
69
|
|
|
70
|
-
|
|
70
|
+
|
|
71
71
|
|
|
72
72
|
<sub>图 4：**阶段与工件**。看阶段条与预览区 —— 当前阶段、已过阶段、以及该阶段真正写下的工件正文（工件是唯一真源，浮层只是它的视图）。</sub>
|
|
73
73
|
|
|
74
|
-
|
|
74
|
+
|
|
75
75
|
|
|
76
76
|
<sub>图 5：**设置**。看官方 `设置 →「专家团」` 这一页 —— 18 个设置项、中文标签、**改动即保存并即时生效**（上限/轮次/档位门/振荡检测在进程内重算）；值存在宿主命名空间 `expert-team`，随插件市场的备份/恢复一起走。</sub>
|
|
77
77
|
|
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.7",
|
|
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",
|