dsh-workplan 1.8.1 → 1.8.2

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 CHANGED
@@ -1,3 +1,31 @@
1
+ ## 1.8.2 — 2026-10-30
2
+
3
+ **文档版:把两个卖点提到首页第一句,并删掉首屏的铺陈。不改运行时代码。**
4
+
5
+ > 反馈很直接:仓库首页看完还不知道卖点是什么,而且话太多。这一版只动文档:
6
+ > 第一句同时点明两个卖点,首屏压到「一句标语 + 一句定位 + 三条要点」,
7
+ > 长篇解释全部下移或折叠。技术结论、合规立场、测试数量都没有变。
8
+
9
+ ### 变更(文档)
10
+
11
+ - `README.md` / `README.en.md`:**第一句**即两个卖点 —— ①安全证据按 ISO/IEC 15408:2026(CC)
12
+ 公开、可自己核对(明说没有证书、不宣称"通过");②安装只要一条命令、零第三方运行时依赖。
13
+ - 首屏从"徽章 + 两段引用 + 长段标准科普"压到 5 行内;CC 三方分工的解释由 4 条长要点改为 1 段。
14
+ - `1.5.0 改了什么` / `1.4.3 修了什么` 两节折叠进 `<details>`,默认收起,内容一字未删。
15
+ - 计算出的就绪度表述统一为"EAL1 的 14 项组件:10 就绪 / 3 部分 / 1 外部实验室"。
16
+
17
+ ### 测试
18
+
19
+ - `npm run verify`:188 tests / 188 pass / 0 fail(无代码变更,仅版本号与文档)。
20
+
21
+ ### 升级
22
+
23
+ ```bash
24
+ dsh plugin --profile web add dsh-workplan@1.8.2
25
+ ```
26
+
27
+ ---
28
+
1
29
  ## 1.8.1 — 2026-10-30
2
30
 
3
31
  **补丁版:把 v1.8.0 里三处"文档说得比代码多"的地方改成一致,并补上一处真实的方法限制。**
package/README.en.md CHANGED
@@ -1,42 +1,37 @@
1
- # Task Progress (dsh-workplan)
1
+ # dsh-workplan
2
+
3
+ > **Two selling points, one line: an ISO/IEC 15408:2026 (CC) evidence pack you can verify yourself, and a one-command install with zero runtime dependencies.**
2
4
 
3
5
  [![verify](https://github.com/abbaababa/dsh-workplan/actions/workflows/verify.yml/badge.svg)](https://github.com/abbaababa/dsh-workplan/actions/workflows/verify.yml)
4
6
 
5
- **中文(简体)说明:** [README.md](README.md)
7
+ Adds "plan first → dispatch real department subagents → watch progress in the sidebar" to **DeepSeek Harness (DSH)**. No app, no DSH source patch, no page replacement.
6
8
 
7
- > Plan first, dispatch real department subagents, then show the progress in plain language.
8
- >
9
- > **No app to install, no DSH source to patch, no page replacement.** You get three things: a plan in the conversation, real subagents doing the work, and a **Task progress** panel in the sidebar.
9
+ - A task-decomposition block appears in the conversation first: stages, work items, departments, acceptance criteria
10
+ - Up to 5 real subagents run in parallel and write results back into the session
11
+ - The **Task progress** panel shows who is working, how far, and what is stuck
10
12
 
11
- ---
12
-
13
- ## 🌍 International security standard: the full evidence chain, and the honest boundary
13
+ **中文(简体)说明:** [README.md](README.md)
14
14
 
15
- **You have probably seen plugins claim "ISO/IEC 15408 / Common Criteria certified". For small open-source tools that claim is almost always false — CC's rules do not allow it.**
15
+ ---
16
16
 
17
- In plain words:
17
+ ## Why ISO/IEC 15408 is a selling point here — honestly
18
18
 
19
- - **ISO/IEC 15408** (a.k.a. **CC**, Common Criteria) is an international standard that answers one question: *"what can this software actually secure, and why should anyone believe it?"* The current edition is **2026** (not 2022).
20
- - CC splits the work three ways: **the developer supplies evidence → an accredited lab evaluates it → a national scheme issues the certificate**. The certificate comes from a third party; **software cannot certify itself**.
21
- - So any claim of "fully satisfies ISO/IEC 15408" without a **certificate number** is a false statement. This plugin has no certificate, and we **will not** write that.
19
+ **CC (Common Criteria, ISO/IEC 15408) works in three separated roles: the developer supplies evidence → an accredited lab evaluates it → a national scheme issues the certificate. Software cannot certify itself.** So "this plugin is CC certified", with no certificate number, is a false statement — we do not write it.
22
20
 
23
- So what did we do? **We produced the materials CC asks for, in the standard's own structure, and published them so you can verify everything yourself — without trusting us.**
21
+ We do the half that can be done by us: **build the materials the 2026 edition (not 2022) asks for, in its own structure, and publish them so anyone can check.**
24
22
 
25
- | What is published | What it is in the standard | Where |
23
+ | What is published | In the standard | Where |
26
24
  |---|---|---|
27
- | What this plugin protects, from whom, and where the boundary is | Security Target (ST) | [docs/cc/SECURITY-TARGET.md](docs/cc/SECURITY-TARGET.md) |
25
+ | What it protects, from whom, where the boundary is | Security Target (ST) | [docs/cc/SECURITY-TARGET.md](docs/cc/SECURITY-TARGET.md) |
28
26
  | Attack surface, 7 threats, countermeasures, residual risk | Vulnerability assessment (AVA) | [docs/cc/AVA-VULNERABILITY-ANALYSIS.md](docs/cc/AVA-VULNERABILITY-ANALYSIS.md) |
29
- | Class-by-class mapping, EAL1 readiness, what is still missing | Self-assessment | [docs/cc/CC-2026-ASSESSMENT.md](docs/cc/CC-2026-ASSESSMENT.md) |
30
- | Every third-party component, licence and hash | Life cycle (ALC) | [docs/SBOM.md](docs/SBOM.md) |
31
- | How to report a vulnerability, response times, deployment | Security policy | [SECURITY.md](SECURITY.md) |
27
+ | Class-by-class mapping, EAL1 readiness, what is missing | Self-assessment | [docs/cc/CC-2026-ASSESSMENT.md](docs/cc/CC-2026-ASSESSMENT.md) |
28
+ | Third-party components, licences, hashes | Life cycle (ALC) | [docs/SBOM.md](docs/SBOM.md) |
29
+ | How to report a vulnerability, response times | Security policy | [SECURITY.md](SECURITY.md) |
32
30
  | 188 automated tests, one command to re-run | Testing (ATE) | `npm run verify` |
33
31
 
34
- **Three sentences of conclusion:**
35
- 1. On engineering evidence, the material is close to **EAL1** — the lowest CC level (10 of 14 components ready, 3 partial, 1 that **only** an external lab can provide);
36
- 2. Certification itself costs lab time and money and **cannot be achieved by editing code**, so we do not pretend otherwise;
37
- 3. What we do claim is **checkable by anyone with 5 commands** — worth far more than the phrase "certified".
32
+ Status: of the 14 EAL1 components — CC's lowest level — **10 are ready, 3 partially ready, 1 can only come from an external lab**. What is missing is lab money and scheduling, not code, so we sell evidence and do not pretend to hold a certificate.
38
33
 
39
- Verify it yourself (copy-paste):
34
+ Check it yourself — 3 lines, copy-paste:
40
35
 
41
36
  ```bash
42
37
  git clone https://github.com/abbaababa/dsh-workplan.git && cd dsh-workplan
@@ -44,12 +39,9 @@ npm ci && npm run verify # expect: tests 188 /
44
39
  grep -RInE "child_process|execSync|eval\(|writeFileSync" src || echo "0 hits (expected)"
45
40
  ```
46
41
 
47
- > Remember one line: **a certificate is given by a third party; evidence is earned by the project. We give you the evidence, and we do not fake the certificate.**
48
-
49
- > **Self-correction record**: v1.8.1 fixed three places in v1.8.0 where the documentation promised more than the code did — the chart route is *not* auth-checked, the suite does *not* cover the auth/truncation branches, and the EAL1 matrix marked a self-contradicting component as ready. What we got wrong, and why, is recorded in the [CHANGELOG](CHANGELOG.md) and [§6.1 of the assessment](docs/cc/CC-2026-ASSESSMENT.md). **We even write down where we were wrong.**
50
-
51
-
52
- ---
42
+ > Remember one line: **a certificate is given by a third party; evidence is earned by the project.**
43
+ >
44
+ > **Self-correction record**: v1.8.1 publicly fixed three places in v1.8.0 where the documentation claimed more than the code did (the chart route is not auth-checked, the suite does not cover the auth/truncation branches, and the EAL1 matrix marked a self-contradicting component as ready). Details in the [CHANGELOG](CHANGELOG.md) and [assessment §6.1](docs/cc/CC-2026-ASSESSMENT.md).
53
45
 
54
46
  ## What it actually does
55
47
 
@@ -85,7 +77,7 @@ The full contract — roles, data shapes, state machine, recovery, and the three
85
77
  ## Install
86
78
 
87
79
  ```bash
88
- dsh plugin --profile web add dsh-workplan@1.8.1
80
+ dsh plugin --profile web add dsh-workplan@1.8.2
89
81
  ```
90
82
 
91
83
  Restart the DSH Web process (or reload the page) so the bundle is picked up.
@@ -157,7 +149,8 @@ grep -RInE "writeFileSync|child_process|eval\(" src
157
149
  npm audit --omit=dev
158
150
  ```
159
151
 
160
- ## What 1.5.0 changes (progress you can see)
152
+ <details>
153
+ <summary><b>What 1.5.0 changes (progress you can see)</b> (click to expand)</summary>
161
154
 
162
155
  1.5.0 is presentation-only: the collapsed plan card swaps its single grey line ("本计划 0/8 做好了" plus a 54×5px bar) for an actual chart.
163
156
 
@@ -174,7 +167,10 @@ None of the counts disappeared — the legend always carries all four buckets wi
174
167
 
175
168
  No new dependencies, `plan.ts` / `runtime.ts` untouched; rollback is documented in [CHANGELOG.md](CHANGELOG.md).
176
169
 
177
- ## What 1.4.3 fixes
170
+ </details>
171
+
172
+ <details>
173
+ <summary><b>What 1.4.3 fixes</b> (click to expand)</summary>
178
174
 
179
175
  1.4.3 is a counting-consistency release. The plugin used to keep two sources of truth — live subtask state and a cached stats snapshot — so the panel could disagree with reality.
180
176
 
@@ -187,6 +183,8 @@ No new dependencies, `plan.ts` / `runtime.ts` untouched; rollback is documented
187
183
 
188
184
  The fix removes the cached snapshot: every number is derived at serialisation time by one function, guarded by 7 invariants and mutation tests. Full report: [docs/fix-report-derived-counts-1.4.3.md](docs/fix-report-derived-counts-1.4.3.md).
189
185
 
186
+ </details>
187
+
190
188
  ## FAQ
191
189
 
192
190
  **Nothing happens after installing.** Restart DSH Web; confirm `dsh-workplan` is in `~/.dsh/profiles/web/package.json`.
package/README.md CHANGED
@@ -1,42 +1,37 @@
1
- # 任务进度(dsh-workplan)
1
+ # dsh-workplan
2
2
 
3
- [![verify](https://github.com/abbaababa/dsh-workplan/actions/workflows/verify.yml/badge.svg)](https://github.com/abbaababa/dsh-workplan/actions/workflows/verify.yml)
3
+ > **两个卖点,一句话:安全证据按 ISO/IEC 15408:2026(CC)公开、自己就能验;安装只要一条命令、零第三方运行时依赖。**
4
4
 
5
- **English (US) — plain-language guide:** [README.en.md](README.en.md)
5
+ [![verify](https://github.com/abbaababa/dsh-workplan/actions/workflows/verify.yml/badge.svg)](https://github.com/abbaababa/dsh-workplan/actions/workflows/verify.yml)
6
6
 
7
- > 给 **DeepSeek Harness(DSH)** 加一个「先拆任务、再真的派人去做、最后让你一眼看懂进度」的能力。
8
- >
9
- > **不用装 App,不改 DSH 源码,不替换页面。** 装上以后多三样东西:对话里的计划、真的部门子 Agent、左侧栏一个「任务进度」面板。
7
+ 给 **DeepSeek Harness(DSH)** 加一段「先拆计划 → 真派部门子 Agent 去做 → 左侧栏实时看进度」的能力。不装 App、不改 DSH 源码、不换页面。
10
8
 
11
- ---
9
+ - 对话里先出【任务分解】:阶段、子任务、部门、验收标准,一样不缺
10
+ - 最多 5 个真实子 Agent 并行执行,结果写回会话
11
+ - 左侧栏「任务进度」:谁在做、做到哪、哪件卡住了
12
12
 
13
- ## 🌍 国际安全标准:我们公开了完整证据链,也公开了边界
13
+ **English (US) — plain-language guide:** [README.en.md](README.en.md)
14
14
 
15
- **你可能在别的插件介绍里见过「通过 ISO/IEC 15408 / Common Criteria 认证」。这句话在开源小工具上基本都是假的,因为 CC 的规矩不允许。**
15
+ ---
16
16
 
17
- 先说人话版:
17
+ ## 为什么敢拿 ISO/IEC 15408 当卖点,又不算吹牛
18
18
 
19
- - **ISO/IEC 15408**(简称 **CC**,通用准则)是一份国际标准,专门回答一个问题:*"一个软件在安全上到底能做到什么,凭什么让人信?"* 最新版是 **2026 年版**(不是 2022 版)。
20
- - CC 的规矩是三方分工:**写代码的人交材料 → 独立实验室去测 → 国家认证机构发证书**。证书由第三方签发,**软件自己不能给自己发**。
21
- - 所以任何"我这个插件完全满足 ISO/IEC 15408"的说法,只要没给出**证书编号**,就是不实陈述。本插件没有证书,我们**不会**这么写。
19
+ **CC(Common Criteria,ISO/IEC 15408)的规矩是三方分工:开发者交材料 → 独立实验室评测 → 国家机构发证。软件不能给自己发证。** 所以「本插件已通过 CC 认证」这句话,没有证书编号就是假的——这种话我们不说。
22
20
 
23
- 那我们做了什么?**把 CC 要求的那套材料,按标准结构真做出来、公开出来、让任何人不信任我们也能自己核对。**
21
+ 我们做的是能自己做的那一半:**按 2026 版(不是 2022 版)标准的结构,把材料真做出来、公开出来,任何人都能自己核对。**
24
22
 
25
- | 我们公开的 | 对应标准里的东西 | 在哪儿看 |
23
+ | 我们公开的 | 对应标准 | 在哪儿 |
26
24
  |---|---|---|
27
- | 这个插件保护什么、防谁、边界在哪 | 安全目标(ST) | [docs/cc/SECURITY-TARGET.md](docs/cc/SECURITY-TARGET.md) |
25
+ | 保护什么、防谁、边界在哪 | 安全目标(ST) | [docs/cc/SECURITY-TARGET.md](docs/cc/SECURITY-TARGET.md) |
28
26
  | 攻击面、7 条威胁、对策、残留风险 | 脆弱性评定(AVA) | [docs/cc/AVA-VULNERABILITY-ANALYSIS.md](docs/cc/AVA-VULNERABILITY-ANALYSIS.md) |
29
- | 逐类对照 + EAL1 就绪度 + 还缺什么 | 符合性自评估 | [docs/cc/CC-2026-ASSESSMENT.md](docs/cc/CC-2026-ASSESSMENT.md) |
30
- | 用了哪些别人的代码、许可证、哈希 | 生命周期(ALC) | [docs/SBOM.md](docs/SBOM.md) |
27
+ | 逐类对照 + EAL1 就绪度 + 还缺什么 | 自评估 | [docs/cc/CC-2026-ASSESSMENT.md](docs/cc/CC-2026-ASSESSMENT.md) |
28
+ | 第三方组件、许可证、哈希 | 生命周期(ALC) | [docs/SBOM.md](docs/SBOM.md) |
31
29
  | 漏洞怎么报、多久回、部署怎么配 | 安全策略 | [SECURITY.md](SECURITY.md) |
32
30
  | 188 项自动化测试,一条命令复跑 | 测试(ATE) | `npm run verify` |
33
31
 
34
- **结论就三句**:
35
- 1. 工程实践上,材料已接近 CC 最低等级 **EAL1** 的要求(14 项组件里 10 项已就绪、3 项部分具备、1 项**完全**必须靠外部实验室);
36
- 2. 认证本身要花外部实验室的钱和时间,**不是改代码能解决的**,所以我们不吹;
37
- 3. 我们吹的是**能被任何人 5 条命令验证的事实**——这比一句"已通过认证"值钱得多。
32
+ 现状:CC 最低等级 **EAL1** 的 14 项组件里,**10 项就绪、3 项部分具备、1 项只能靠外部实验室**。差的不是代码,是认证要花的实验室费用与排期——所以我们只卖证据,不冒充分证。
38
33
 
39
- 自己验证(复制即用):
34
+ 自己验,3 行,复制即用:
40
35
 
41
36
  ```bash
42
37
  git clone https://github.com/abbaababa/dsh-workplan.git && cd dsh-workplan
@@ -44,13 +39,9 @@ npm ci && npm run verify # 期望:tests 188 /
44
39
  grep -RInE "child_process|execSync|eval\(|writeFileSync" src || echo "0 命中(预期)"
45
40
  ```
46
41
 
47
- > 一句话记住:**"有证书"是第三方给的,"有证据"是自己挣的。我们给你后者,并且不冒充前者。**
42
+ > 一句话记住:**有证书是第三方给的,有证据是自己挣的。**
48
43
  >
49
- > **自我更正记录**:v1.8.1 更正了 v1.8.0 里三处"文档写得比代码多"的地方(图表路由其实不鉴权、
50
- > 自测并未覆盖鉴权/截断分支、EAL1 矩阵把一个自相矛盾的组件判成就绪)。更正过程与原因记在
51
- > [CHANGELOG](CHANGELOG.md) 与 [自评估报告 §6.1](docs/cc/CC-2026-ASSESSMENT.md)。**我们连自己说错的话都会写出来。**
52
-
53
- ---
44
+ > **自我更正记录**:v1.8.1 公开更正了 v1.8.0 里三处「文档写得比代码多」的地方(图表路由其实不鉴权、自测并未覆盖鉴权与截断分支、EAL1 矩阵把一个自相矛盾的组件判成就绪),详情见 [CHANGELOG](CHANGELOG.md) 与 [自评估 §6.1](docs/cc/CC-2026-ASSESSMENT.md)。
54
45
 
55
46
  ## 它到底做了什么(用大白话讲)
56
47
 
@@ -75,7 +66,7 @@ grep -RInE "child_process|execSync|eval\(|writeFileSync" src || echo "0 命中
75
66
  ## 一键安装
76
67
 
77
68
  ```bash
78
- dsh plugin --profile web add dsh-workplan@1.8.1
69
+ dsh plugin --profile web add dsh-workplan@1.8.2
79
70
  ```
80
71
 
81
72
  装完**重启一次 DSH Web**(或重新载入当前页面)让插件生效。
@@ -163,7 +154,8 @@ grep -RInE "writeFileSync|child_process|eval\(" src # 应无命中
163
154
  npm audit --omit=dev
164
155
  ```
165
156
 
166
- ## 1.5.0 改了什么(进度一眼可见)
157
+ <details>
158
+ <summary><b>1.5.0 改了什么(进度一眼可见)</b>(点开看)</summary>
167
159
 
168
160
  1.5.0 只改展示层:把计划卡折叠态那行「本计划 0/8 做好了 + 一根 54×5px 的小条」换成图表组合。
169
161
 
@@ -180,7 +172,10 @@ npm audit --omit=dev
180
172
 
181
173
  没有新增依赖,`plan.ts` / `runtime.ts` 无改动;回滚方式见 [CHANGELOG.md](CHANGELOG.md)。
182
174
 
183
- ## 1.4.3 修了什么(为什么值得升级)
175
+ </details>
176
+
177
+ <details>
178
+ <summary><b>1.4.3 修了什么(为什么值得升级)</b>(点开看)</summary>
184
179
 
185
180
  1.4.3 是一次**计数一致性**修复:插件曾同时维护「实时任务状态」和「缓存的统计快照」两份真相,导致面板数字和实际状态对不上(截图里「0 个正在做」但下面有任务正在做,就是它)。
186
181
 
@@ -193,6 +188,8 @@ npm audit --omit=dev
193
188
 
194
189
  修法是**删掉缓存快照,只保留一份状态源**:所有数字在序列化时由同一函数现场派生,并配了 7 条不变量 + 变异测试防止回退。完整报告:[docs/fix-report-derived-counts-1.4.3.md](docs/fix-report-derived-counts-1.4.3.md)。
195
190
 
191
+ </details>
192
+
196
193
  ## 常见问题
197
194
 
198
195
  **装完没反应?**
@@ -0,0 +1,35 @@
1
+ # dsh-workplan v1.8.2 — 首页说人话版 / a clearer front page
2
+
3
+ ## 中文
4
+
5
+ 这一版只改文档,不改代码。
6
+
7
+ **首页第一句现在直接讲两个卖点:**
8
+
9
+ 1. 安全证据按 **ISO/IEC 15408:2026(CC)** 公开,5 条命令自己验 —— 明说没有证书,也绝不宣称"通过认证";
10
+ 2. 安装只要**一条命令**,**零第三方运行时依赖**。
11
+
12
+ 顺手把首屏的铺陈删了:原来要滚过大段标准科普才看到卖点,现在前 5 行讲完;`1.5.0`/`1.4.3` 的历史说明折叠收起,内容没删。
13
+
14
+ 安装:
15
+
16
+ ```bash
17
+ dsh plugin --profile web add dsh-workplan@1.8.2
18
+ ```
19
+
20
+ ## English
21
+
22
+ Documentation only — no code changes.
23
+
24
+ **The first line of the README now states both selling points:**
25
+
26
+ 1. An **ISO/IEC 15408:2026 (CC)** evidence pack you can verify with 5 commands — no certificate is claimed, and we never say "certified";
27
+ 2. A **one-command install** with **zero runtime dependencies**.
28
+
29
+ The front page was also de-bloated: the selling points used to sit below a long standards explainer; now they appear in the first 5 lines, and the 1.5.0/1.4.3 history sections are collapsed (nothing deleted).
30
+
31
+ Install:
32
+
33
+ ```bash
34
+ dsh plugin --profile web add dsh-workplan@1.8.2
35
+ ```
package/lib/host.js CHANGED
@@ -371,7 +371,7 @@ export function apply(ctx, config = {}) {
371
371
  }
372
372
  export const meta = {
373
373
  name,
374
- version: '1.8.1',
374
+ version: '1.8.2',
375
375
  promptOrder: PROMPT_ORDER,
376
376
  routes: ['/dsh-workplan/plans', '/dsh-workplan/vendor/chart.umd.js'],
377
377
  };
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "dsh-workplan",
3
- "version": "1.8.1",
3
+ "version": "1.8.2",
4
4
  "description": "Automatic task decomposition, real department subagents, and a responsive workplan dashboard for DeepSeek Harness.",
5
5
  "type": "module",
6
6
  "license": "MIT",
package/src/host.ts CHANGED
@@ -408,7 +408,7 @@ export function apply(ctx: any, config: WorkplanConfig = {}) {
408
408
 
409
409
  export const meta = {
410
410
  name,
411
- version: '1.8.1',
411
+ version: '1.8.2',
412
412
  promptOrder: PROMPT_ORDER,
413
413
  routes: ['/dsh-workplan/plans', '/dsh-workplan/vendor/chart.umd.js'],
414
414
  }