dsh-root-planner-preset 1.0.0 → 1.0.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/INSTALL.md +19 -9
- package/README.md +66 -45
- package/README.zh.md +103 -0
- package/docs/DEVELOPMENT.md +25 -2
- package/package.json +2 -2
package/INSTALL.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
面向**接收方**。本包是一个 DSH agent 预设（bundle），不改动 DSH 本体。
|
|
4
4
|
|
|
5
|
-
[
|
|
5
|
+
[English README](README.md) | [中文说明](README.zh.md) | [维护者文档](docs/DEVELOPMENT.md)
|
|
6
6
|
|
|
7
7
|
## 一、前置条件
|
|
8
8
|
|
|
@@ -32,27 +32,35 @@ web_search web_fetch
|
|
|
32
32
|
|
|
33
33
|
## 二、安装
|
|
34
34
|
|
|
35
|
-
|
|
35
|
+
四种方式任选，推荐第 1 种。
|
|
36
36
|
|
|
37
|
-
### 方式 1
|
|
37
|
+
### 方式 1：npm（推荐）
|
|
38
38
|
|
|
39
39
|
```sh
|
|
40
|
-
dsh plugin --profile web add
|
|
40
|
+
dsh plugin --profile web add dsh-root-planner-preset
|
|
41
41
|
```
|
|
42
42
|
|
|
43
|
-
|
|
43
|
+
已发布在 npm：<https://www.npmjs.com/package/dsh-root-planner-preset>。这是**预构建安装**，跳过 pnpm 的构建授权步骤，最省事。
|
|
44
|
+
|
|
45
|
+
> 也可以钉版本：`dsh plugin --profile web add dsh-root-planner-preset@1.0.0`
|
|
46
|
+
|
|
47
|
+
### 方式 2：GitHub 源码
|
|
48
|
+
|
|
49
|
+
```sh
|
|
50
|
+
dsh plugin --profile web add github:XiaoOu2024/dsh-root-planner-preset
|
|
51
|
+
```
|
|
44
52
|
|
|
45
|
-
>
|
|
53
|
+
> 也可以指定分支或 tag：`github:XiaoOu2024/dsh-root-planner-preset#v1.0.0`
|
|
46
54
|
|
|
47
|
-
### 方式
|
|
55
|
+
### 方式 3：让 DSH 里的 agent 装
|
|
48
56
|
|
|
49
57
|
对 agent 说：
|
|
50
58
|
|
|
51
|
-
> 用 `plugin_manager` 的 `install_bundle`，target 填 `github:XiaoOu2024/dsh-root-planner-preset
|
|
59
|
+
> 用 `plugin_manager` 的 `install_bundle`，target 填 `dsh-root-planner-preset`（或 `github:XiaoOu2024/dsh-root-planner-preset`）
|
|
52
60
|
|
|
53
61
|
注意：这个工具调用需要 **Full access** 权限或当次授权。
|
|
54
62
|
|
|
55
|
-
### 方式
|
|
63
|
+
### 方式 4：先克隆再按路径装
|
|
56
64
|
|
|
57
65
|
```sh
|
|
58
66
|
git clone https://github.com/XiaoOu2024/dsh-root-planner-preset
|
|
@@ -60,6 +68,8 @@ git clone https://github.com/XiaoOu2024/dsh-root-planner-preset
|
|
|
60
68
|
|
|
61
69
|
然后让 agent 用 `install_bundle`，target 填**克隆下来的绝对路径**。
|
|
62
70
|
|
|
71
|
+
装完重启 `dsh web`。
|
|
72
|
+
|
|
63
73
|
### ❌ 不适用：插件市场界面
|
|
64
74
|
|
|
65
75
|
**「设置 → 插件市场」搜不到本包，属正常。** dsh-market 只允许安装 `awesome-dsh-plugin` 精选列表内的来源，本包不在其中。请用上面三种方式。
|
package/README.md
CHANGED
|
@@ -1,82 +1,103 @@
|
|
|
1
1
|
# dsh-root-planner-preset
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
An agent preset for [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) (DSH) that **separates reading from deciding**.
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
The root agent's context holds task analysis, planning and decisions; file reading and information queries go to subagents that return summaries only. Creating, modifying and deleting files stays with the root agent — subagents do not even have the tools.
|
|
6
6
|
|
|
7
|
-
>
|
|
7
|
+
> One agent in the tree has hands. Every other agent has only eyes.
|
|
8
8
|
|
|
9
|
-
[
|
|
9
|
+
[中文说明](README.zh.md) | [Install](INSTALL.md) | [Maintainer notes](docs/DEVELOPMENT.md)
|
|
10
10
|
|
|
11
|
-
##
|
|
11
|
+
## The problem it solves
|
|
12
12
|
|
|
13
|
-
|
|
13
|
+
On a long task a coding agent's context fills up with raw file contents, and it forgets the goal, loses the plan, and starts repeating work. The usual answer — "delegate more to subagents" — does not hold on its own: a subagent will still edit files on its way past, and work gets passed further down without limit.
|
|
14
14
|
|
|
15
|
-
|
|
15
|
+
This preset turns both of those into structural constraints rather than good intentions:
|
|
16
16
|
|
|
17
|
-
|
|
|
17
|
+
| Requirement | Mechanism | Strength |
|
|
18
18
|
|---|---|---|
|
|
19
|
-
|
|
|
20
|
-
|
|
|
21
|
-
|
|
|
22
|
-
|
|
|
23
|
-
|
|
|
19
|
+
| Subagents **cannot** create, modify or delete files | A `toolFilter.allow` list on both delegation tools, without `write`, `edit`, `ops_replace` | **Structural**: an absent tool cannot be called |
|
|
20
|
+
| Subagents **have no shell** to work around it | The same list, without `ops_bash`, `pwsh` | **Structural** |
|
|
21
|
+
| Work cannot be passed down without limit | The runtime delegation depth limit (`subagent.maxDepth`) | **Structural**: past the cap it throws `SubagentDepthError` |
|
|
22
|
+
| The root agent owns every mutation | Persona rules (the mask applies to children only) | Prompt-level |
|
|
23
|
+
| The root agent delegates reading by default | Persona rules | Prompt-level |
|
|
24
24
|
|
|
25
|
-
|
|
25
|
+
The mask is an **allow** list, not a deny list: a tool added by a future plugin is invisible to subagents until it is added here.
|
|
26
26
|
|
|
27
|
-
##
|
|
27
|
+
## How it works
|
|
28
28
|
|
|
29
29
|
```
|
|
30
|
-
|
|
31
|
-
├──
|
|
32
|
-
│ └──
|
|
33
|
-
└──
|
|
30
|
+
root agent (depth 0) <- the only one with write / edit / shell
|
|
31
|
+
├── subagent (depth 1) <- read-only; may delegate one more level
|
|
32
|
+
│ └── grandchild (depth 2) <- read-only; a leaf
|
|
33
|
+
└── subagent (depth 1)
|
|
34
34
|
```
|
|
35
35
|
|
|
36
|
-
-
|
|
37
|
-
-
|
|
38
|
-
-
|
|
36
|
+
- **Root agent**: plans first (goal, success criteria, constraints, ordered task list), delegates reading, searching and locating by default, and reads directly only for one known file, a short targeted range, or to check a claim a subagent made.
|
|
37
|
+
- **Subagent**: reads, locates and summarizes. On finding that a file **needs changing** it does not act; it reports the exact change — target path, location (`file:line`), current content, proposed replacement, and why.
|
|
38
|
+
- **The root agent decides** on that proposal and then makes the change itself.
|
|
39
39
|
|
|
40
|
-
|
|
40
|
+
How does a subagent know it is a subagent? DSH force-inserts the sentence `You are a delegated subagent: …` into every subagent's prompt, injected by the runtime and impossible to remove — while a preset persona has **no** `{{role}}`-style variable available. So the persona states a **test** instead: read your own prompt for that sentence. One persona then serves both roles, and parent and child read the same text, which is what prevents the drift where a parent believes a child is constrained and the child never saw it.
|
|
41
41
|
|
|
42
|
-
##
|
|
42
|
+
## Quick start
|
|
43
|
+
|
|
44
|
+
Install from npm (prebuilt, no build-approval step):
|
|
45
|
+
|
|
46
|
+
```sh
|
|
47
|
+
dsh plugin --profile web add dsh-root-planner-preset
|
|
48
|
+
```
|
|
49
|
+
|
|
50
|
+
Or straight from GitHub source:
|
|
43
51
|
|
|
44
52
|
```sh
|
|
45
53
|
dsh plugin --profile web add github:XiaoOu2024/dsh-root-planner-preset
|
|
46
54
|
```
|
|
47
55
|
|
|
48
|
-
|
|
56
|
+
Then **one required step**: set **Settings → Subagents → depth limit** to **`2`**. (This is the Host's `subagent` settings section — global, and **not** part of the bundle. Setting it to `0` disables all delegation and breaks the design.)
|
|
49
57
|
|
|
50
|
-
|
|
58
|
+
Then **start a new session** and pick **Root Planner** in the preset selector. Full steps and troubleshooting are in [INSTALL.md](INSTALL.md).
|
|
51
59
|
|
|
52
|
-
##
|
|
60
|
+
## When it fits, and when it does not
|
|
53
61
|
|
|
54
|
-
|
|
62
|
+
**Fits**: long research-heavy tasks across many files, reverse engineering, code review — anything read-heavy, or where a change must be carefully decided.
|
|
55
63
|
|
|
56
|
-
|
|
64
|
+
**Does not fit**:
|
|
57
65
|
|
|
58
|
-
-
|
|
59
|
-
-
|
|
60
|
-
-
|
|
66
|
+
- changing one file quickly — the extra delegation layer is pure overhead;
|
|
67
|
+
- wanting subagents to **write code in parallel** — this preset forbids that on purpose; use the `standard` preset instead;
|
|
68
|
+
- an environment missing the DSH tooling listed in [INSTALL.md](INSTALL.md).
|
|
61
69
|
|
|
62
|
-
##
|
|
70
|
+
## Repository contents
|
|
63
71
|
|
|
64
|
-
|
|
|
72
|
+
| File | Purpose |
|
|
65
73
|
|---|---|
|
|
66
|
-
| `cordis.patch.yml` |
|
|
67
|
-
| `persona.txt` |
|
|
68
|
-
| `build-patch.mjs` |
|
|
69
|
-
| `verify-patch.mjs` |
|
|
70
|
-
| `verify-depth-override.mjs` |
|
|
71
|
-
| `lib-yaml.mjs` |
|
|
72
|
-
| `docs/DEVELOPMENT.md` |
|
|
74
|
+
| `cordis.patch.yml` | The preset declaration (**generated — do not hand-edit**) |
|
|
75
|
+
| `persona.txt` | The persona prose; **edit this one** |
|
|
76
|
+
| `build-patch.mjs` | Generates `cordis.patch.yml` from `persona.txt` |
|
|
77
|
+
| `verify-patch.mjs` | Checks patch structure and the tool mask, and asserts byte identity of the persona |
|
|
78
|
+
| `verify-depth-override.mjs` | Checks that the depth override reached the composed profile |
|
|
79
|
+
| `lib-yaml.mjs` | Resolves a YAML parser from the local DSH install, so this package has **no dependencies** |
|
|
80
|
+
| `docs/DEVELOPMENT.md` | Maintainer notes: design trade-offs, mechanics, verified/unverified boundaries |
|
|
81
|
+
|
|
82
|
+
## Verified / not verified
|
|
83
|
+
|
|
84
|
+
**Verified**: the patch parses as loader YAML; the parsed persona is **byte-identical** to `persona.txt`; both delegation masks exclude every mutation entry point and name only tools this profile actually registers; a clean checkout passes verification (`.gitattributes` pins LF, without which a Windows clone breaks the byte-identity check); the depth override reached the composed profile.
|
|
85
|
+
|
|
86
|
+
**Not verified**: **no subagent has actually been spawned under the `root-planner` preset yet.** The tool names in the mask were cross-checked against the author's environment, not exercised at runtime. If your environment lacks one of those global tool names, child creation fails with `tools.restrict() names unknown global tool …`. See the troubleshooting section of [INSTALL.md](INSTALL.md).
|
|
87
|
+
|
|
88
|
+
## Contributing
|
|
89
|
+
|
|
90
|
+
Issues and pull requests are welcome — this repository is meant to be maintained by more than its author. The license is [MIT](LICENSE), so forking, modifying and redistributing are all permitted.
|
|
73
91
|
|
|
74
|
-
|
|
92
|
+
Useful contributions, roughly in order of value:
|
|
75
93
|
|
|
76
|
-
|
|
94
|
+
- **Report what broke**, with the error text and your DSH version. The unverified area above is exactly where real reports matter most.
|
|
95
|
+
- **Report a mask mismatch** on your platform: which global tools your profile registers and which name the mask got wrong.
|
|
96
|
+
- **Improve the persona** (`persona.txt`) — but run `node build-patch.mjs && node verify-patch.mjs` and include the result, since `cordis.patch.yml` is generated and a hand-edited one will be rejected.
|
|
97
|
+
- **Translate or fix the docs** — [README.zh.md](README.zh.md) and [INSTALL.md](INSTALL.md).
|
|
77
98
|
|
|
78
|
-
|
|
99
|
+
Please keep a change to one concern per pull request, and say which preset it was tested with.
|
|
79
100
|
|
|
80
|
-
##
|
|
101
|
+
## License
|
|
81
102
|
|
|
82
103
|
[MIT](LICENSE)
|
package/README.zh.md
ADDED
|
@@ -0,0 +1,103 @@
|
|
|
1
|
+
# dsh-root-planner-preset
|
|
2
|
+
|
|
3
|
+
一个面向 [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness)（DSH）的 agent 预设：**把「读书」和「决策」分开**。
|
|
4
|
+
|
|
5
|
+
根 agent 的上下文只装任务分析、规划与决策；文件阅读、信息查询交给子代理，子代理只回摘要。而**创建、修改、删除文件只能由根 agent 执行**——子代理连工具都没有。
|
|
6
|
+
|
|
7
|
+
> 一句话：让整棵树里只有一个 agent 有手，其余都只有眼睛。
|
|
8
|
+
|
|
9
|
+
[English](README.md) | [安装步骤](INSTALL.md) | [维护者文档](docs/DEVELOPMENT.md)
|
|
10
|
+
|
|
11
|
+
## 它解决什么问题
|
|
12
|
+
|
|
13
|
+
用 coding agent 干长任务，上下文很快被原始文件内容塞满，于是忘了目标、丢了计划、开始重复劳动。常见对策是「让 agent 多派子代理」，但光靠提示词约束不住——子代理照样会顺手改文件，任务也会被无限往下转派。
|
|
14
|
+
|
|
15
|
+
这个预设把两件事做成了结构约束，而不是靠自觉：
|
|
16
|
+
|
|
17
|
+
| 要求 | 机制 | 强度 |
|
|
18
|
+
|---|---|---|
|
|
19
|
+
| 子代理**不能**创建/修改/删除文件 | 两个委派工具上的 `toolFilter.allow` 白名单，不含 `write`、`edit`、`ops_replace` | **结构性**：工具不存在，调不到 |
|
|
20
|
+
| 子代理**没有** shell 可绕过 | 同一白名单，不含 `ops_bash`、`pwsh` | **结构性** |
|
|
21
|
+
| 任务不会被无限转派 | 运行时深度上限（`subagent.maxDepth`） | **结构性**：超过上限直接抛 `SubagentDepthError` |
|
|
22
|
+
| 根 agent 独揽所有修改 | 人设规则（白名单只作用于子级） | 提示词级 |
|
|
23
|
+
| 根 agent 默认委派阅读 | 人设规则 | 提示词级 |
|
|
24
|
+
|
|
25
|
+
白名单是 **allow 而非 deny**：将来某个插件新增的工具，对子代理默认不可见。
|
|
26
|
+
|
|
27
|
+
## 工作方式
|
|
28
|
+
|
|
29
|
+
```
|
|
30
|
+
根 agent (depth 0) ← 只有它有 write / edit / shell
|
|
31
|
+
├── 子代理 (depth 1) ← 只读；可以再派一层
|
|
32
|
+
│ └── 孙代理 (depth 2) ← 只读；叶子
|
|
33
|
+
└── 子代理 (depth 1)
|
|
34
|
+
```
|
|
35
|
+
|
|
36
|
+
- **根 agent**：先立计划（目标、成功判据、约束、任务清单），把阅读/搜索/定位默认派出去，自己只在「单个已知文件、一小段范围、或核实子代理的某个断言」时才亲自读。
|
|
37
|
+
- **子代理**：只读、只定位、只总结。发现**需要改文件**时不动手，而是回报精确的改动方案——目标路径、位置（file:line）、当前内容、建议替换、理由。
|
|
38
|
+
- **根 agent 收到方案后决策**，然后亲自落盘。
|
|
39
|
+
|
|
40
|
+
子代理怎么知道自己是子代理？DSH 会在每个子代理的提示词里强制插入一句 `You are a delegated subagent: …`，运行时注入、无法移除，而预设人设**没有** `{{role}}` 这类变量可用。所以人设里写的是一条**判定指令**：读自己的提示词里有没有那句话。这让人设只需要一份，父与子读到的是同一份文本，因此不会出现「父以为子被这么约束、子其实没读到」的漂移。
|
|
41
|
+
|
|
42
|
+
## 快速开始
|
|
43
|
+
|
|
44
|
+
推荐从 npm 安装（预构建，免构建授权步骤）：
|
|
45
|
+
|
|
46
|
+
```sh
|
|
47
|
+
dsh plugin --profile web add dsh-root-planner-preset
|
|
48
|
+
```
|
|
49
|
+
|
|
50
|
+
或直接从 GitHub 源码安装：
|
|
51
|
+
|
|
52
|
+
```sh
|
|
53
|
+
dsh plugin --profile web add github:XiaoOu2024/dsh-root-planner-preset
|
|
54
|
+
```
|
|
55
|
+
|
|
56
|
+
装完**必须**再做一步：**设置 → 子智能体 → 深度上限 = `2`**。（这是 Host 的 `subagent` 设置节，**全局生效、不属于** bundle；设成 `0` 会禁掉全部委派，设计就废了。）
|
|
57
|
+
|
|
58
|
+
然后**开新会话**，在预设选择器里选 **Root Planner**。完整步骤与故障排查见 [INSTALL.md](INSTALL.md)。
|
|
59
|
+
|
|
60
|
+
## 适合 / 不适合
|
|
61
|
+
|
|
62
|
+
**适合**：需要跨很多文件调研的长任务、逆向分析、代码审查，以及任何「读得多、改得少」或「改动必须被仔细决策」的工作。
|
|
63
|
+
|
|
64
|
+
**不适合**：
|
|
65
|
+
|
|
66
|
+
- 只想快速改一个文件——多一层委派是纯粹的开销；
|
|
67
|
+
- 需要子代理**并行写代码**——这是本预设**故意**禁止的，请改用 `standard` 预设；
|
|
68
|
+
- 环境缺少 DSH 的工具基础（见 [INSTALL.md](INSTALL.md) 的前置条件）。
|
|
69
|
+
|
|
70
|
+
## 仓库内容
|
|
71
|
+
|
|
72
|
+
| 文件 | 说明 |
|
|
73
|
+
|---|---|
|
|
74
|
+
| `cordis.patch.yml` | 预设声明（**由脚本生成，不要手改**） |
|
|
75
|
+
| `persona.txt` | 人设正文，**要改就改这个** |
|
|
76
|
+
| `build-patch.mjs` | 从 `persona.txt` 生成 `cordis.patch.yml` |
|
|
77
|
+
| `verify-patch.mjs` | 校验补丁结构、工具白名单，并断言人设逐字节一致 |
|
|
78
|
+
| `verify-depth-override.mjs` | 校验深度覆盖是否落到合成配置 |
|
|
79
|
+
| `lib-yaml.mjs` | 从本地 DSH 安装里解析 YAML，因此本包**零依赖** |
|
|
80
|
+
| `docs/DEVELOPMENT.md` | 维护者文档：设计取舍、机制细节、已验证/未验证边界 |
|
|
81
|
+
|
|
82
|
+
## 已验证 / 未验证
|
|
83
|
+
|
|
84
|
+
**已验证**：补丁可被 loader 解析；解析出的人设与 `persona.txt` **逐字节相同**；两个委派工具的白名单排除了所有写入入口、且只包含本机实际注册的工具名；干净检出后校验通过（`.gitattributes` 已钉死 LF，否则 Windows 克隆会破坏逐字节校验）；深度覆盖已落到合成配置。
|
|
85
|
+
|
|
86
|
+
**未验证**：**尚未在 `root-planner` 预设下真正派出过一个子代理。** 白名单里的工具名是按作者环境的实际工具清单交叉核对出来的，不是运行时实测。若你的环境缺少其中某个全局工具名，子代理创建会失败并报 `tools.restrict() names unknown global tool …`。详见 [INSTALL.md](INSTALL.md) 的故障排查。
|
|
87
|
+
|
|
88
|
+
## 参与维护
|
|
89
|
+
|
|
90
|
+
**欢迎提 issue 和 PR——这个仓库本来就打算由作者之外的人一起维护。** 许可证是 [MIT](LICENSE)，fork、修改、再分发都是允许的。
|
|
91
|
+
|
|
92
|
+
按价值排序，有用的贡献大概是这样：
|
|
93
|
+
|
|
94
|
+
- **报告你遇到的故障**，带上完整报错和你使用的 DSH 版本。上面「未验证」那段正是最需要真实反馈的地方。
|
|
95
|
+
- **报告工具白名单在你的环境里不匹配**：你的 profile 注册了哪些全局工具、白名单里哪个名字报错了。
|
|
96
|
+
- **改进人设**（`persona.txt`）——但请跑一次 `node build-patch.mjs && node verify-patch.mjs` 并把结果一并附上，因为 `cordis.patch.yml` 是生成文件，手工改过的会被拒。
|
|
97
|
+
- **翻译或修订文档**——[README.md](README.md) 与 [INSTALL.md](INSTALL.md)。
|
|
98
|
+
|
|
99
|
+
请一个 PR 只做一件事，并说明你在哪个预设下验证过。
|
|
100
|
+
|
|
101
|
+
## 许可
|
|
102
|
+
|
|
103
|
+
[MIT](LICENSE)
|
package/docs/DEVELOPMENT.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# root-planner preset bundle — maintainer notes
|
|
2
2
|
|
|
3
|
-
[中文说明](../README.md) | [
|
|
3
|
+
[English README](../README.md) | [中文说明](../README.zh.md) | [Install](../INSTALL.md)
|
|
4
4
|
|
|
5
5
|
An agent preset for DSH Web that splits **reading** from **planning and mutating**:
|
|
6
6
|
the root agent keeps its context for analysis, planning, and decisions, delegates
|
|
@@ -29,6 +29,8 @@ Paths below are relative to the repository root; this file lives in `docs/`.
|
|
|
29
29
|
| `verify-depth-override.mjs` | Checks that the profile patch layer still parses and that the `subagent` depth override landed in the composed profile. |
|
|
30
30
|
| `package.json` | Bundle manifest (`dsh.bundle.patch`). |
|
|
31
31
|
| `.gitattributes` | Pins LF; without it a Windows checkout breaks the byte-identity check. |
|
|
32
|
+
| `README.md` / `README.zh.md` | The English and Chinese front pages, cross-linked. npm renders the repository root `README.md`, which is why the English one holds that name. |
|
|
33
|
+
| `INSTALL.md` | Recipient-facing setup steps and troubleshooting (Chinese). |
|
|
32
34
|
|
|
33
35
|
```sh
|
|
34
36
|
node build-patch.mjs # after every persona.txt edit
|
|
@@ -54,9 +56,30 @@ targets:
|
|
|
54
56
|
|---|---|---|
|
|
55
57
|
| Absolute path | `C:\path\to\root-planner-preset` | Works from a checkout, a share, or a USB drive. Already-installed bundles must be addressed by package name, not path. |
|
|
56
58
|
| Git repository | `github:you/root-planner-preset` | Also `https://…`, `git+…`, `gitlab:`/`gist:` forms. The manager pre-checks GitHub reachability with `git ls-remote`. |
|
|
57
|
-
| npm registry | `dsh-root-planner-preset`
|
|
59
|
+
| npm registry | `dsh-root-planner-preset` (`@1.0.0` to pin) | **Published.** Preferred: a prebuilt install skips pnpm's build-approval step. |
|
|
58
60
|
| Tarball URL | `https://…/dsh-root-planner-preset-1.0.0.tgz` | For a file server or release asset. |
|
|
59
61
|
|
|
62
|
+
### Publishing to npm
|
|
63
|
+
|
|
64
|
+
The package is live at <https://www.npmjs.com/package/dsh-root-planner-preset>.
|
|
65
|
+
Two things about this machine and account cost real time to discover; both are
|
|
66
|
+
permanent conditions, not accidents:
|
|
67
|
+
|
|
68
|
+
- **The configured registry is `registry.npmmirror.com`**, a read-only mirror.
|
|
69
|
+
Every publish must name the official registry explicitly:
|
|
70
|
+
`npm publish --registry https://registry.npmjs.org/ --access public`.
|
|
71
|
+
- **The publishing account uses npm's staged publishing.** A `npm publish` can
|
|
72
|
+
report success and still leave the version off the registry, because it went to
|
|
73
|
+
the stage instead; `npm stage list` may show nothing while the registry refuses
|
|
74
|
+
that version with `E409 Cannot publish over previously staged version`. The
|
|
75
|
+
reliable check is never the command's exit code — it is
|
|
76
|
+
`https://registry.npmjs.org/<name>/<version>` returning 200. Version `1.0.0`
|
|
77
|
+
reached the registry only after approval on npmjs.com, not from the CLI.
|
|
78
|
+
|
|
79
|
+
The `0.0.0-stage` version on the registry is an automatic placeholder from that
|
|
80
|
+
workflow. It is harmless but pointless; deprecate it rather than treat it as a
|
|
81
|
+
release. Never publish a real version below it.
|
|
82
|
+
|
|
60
83
|
### What the recipient's environment must provide
|
|
61
84
|
|
|
62
85
|
1. **A DSH version whose presets carry the same tool row ids.** The patch mirrors
|
package/package.json
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "dsh-root-planner-preset",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.2",
|
|
4
4
|
"type": "module",
|
|
5
|
-
"description": "DSH agent preset
|
|
5
|
+
"description": "DSH agent preset that outsources file reading to strictly read-only subagents, while the root agent keeps the plan and owns every file mutation.",
|
|
6
6
|
"license": "MIT",
|
|
7
7
|
"author": "XiaoOu2024",
|
|
8
8
|
"homepage": "https://github.com/XiaoOu2024/dsh-root-planner-preset#readme",
|