@lmzhen/dsh-evolution-agent-preset 0.1.0-rc.9 → 0.1.0

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/agent.cordis.yml CHANGED
@@ -1,92 +1,14 @@
1
- # The `standard` agent preset: the full coding agent, mounted once per process.
1
+ # Evolution agent layer DELTA ONLY.
2
2
  #
3
- # This file is an AGENT-PLANE composition. The roster mounts it ONCE under a
4
- # standing scope; every session naming it joins by scope parentage, so the
5
- # tools and prompt sections registered here cover each joined agent while a
6
- # session's own state stays keyed per Session/Agent inside the plugins. The
7
- # host composition (`base.cordis.yml` + `web.cordis.yml`) keeps everything a
8
- # preset must not own: the registries themselves, the sandbox and approval
9
- # stack, persistence, and the model route.
3
+ # This file is the incremental part of the Evolution preset, NOT a full
4
+ # composition. `install-layered.mjs` (agent/layered/oneclick modes) generates
5
+ # the installed preset at `$DSH_HOME/.agent-presets/evolution/agent.cordis.yml`
6
+ # by concatenating the RUNTIME platform's `standard` preset composition with
7
+ # this delta (rc.53): the standard rows come from the dsh being installed
8
+ # against, so the preset follows whatever platform version the user actually
9
+ # has — rc, release, or any future line — instead of vendoring one baseline's
10
+ # rows forever.
10
11
  #
11
- # A service row here MUST sit inside a group carrying an `isolate` realm.
12
- # Without one it publishes into the root realm, where it is process-global —
13
- # another preset publishing the same name collides, and a host reader would
14
- # resolve one preset's instance for every session; `dsh-agent-presets` rejects
15
- # that at mount. `true` means an entry-local realm: this standing mount's own
16
- # private instance, apart from every other preset's. (A shared label does NOT
17
- # pool instances — `provide()` throws on the second registration under the
18
- # same realm symbol; labels join REALMS, and are not what this file needs.)
19
-
20
- # ── identity ────────────────────────────────────────────────────────────────
21
-
22
- # The preset's own persona, shadowing the deployment default for this agent.
23
- # `{{model}}` and `{{cwd}}` resolve from the agent's own route and workspace.
24
- - id: persona
25
- name: '@deepseek-ai/dsh-persona'
26
- config:
27
- text: >-
28
- You are a coding agent powered by the {{model}} model. Your working directory is {{cwd}}.
29
-
30
- - id: agent-instructions
31
- name: '@deepseek-ai/dsh-agent-instructions'
32
- config:
33
- maxBytes: 65536
34
-
35
- # ── shell ───────────────────────────────────────────────────────────────────
36
-
37
- # `shell-env` stays in the HOST composition: `apps/cli/src/web.ts` injects it to
38
- # publish `DSH_WEB_URL`/`DSH_WEB_MODE`, and a host row that injects a service is
39
- # the criterion for host-plane ownership — injection resolves before any session
40
- # exists, so there is no agent to key by. Behind a preset realm those variables
41
- # never reached the model's shell at all. Both shell tools consume the host
42
- # registry from here; their executors (`bash-sandbox`/`pwsh-sandbox`) are
43
- # host-plane too.
44
- - id: tool-bash
45
- name: '@deepseek-ai/dsh-tool-bash'
46
- disabled: !!js process.platform === 'win32'
47
-
48
- - id: tool-pwsh
49
- name: '@deepseek-ai/dsh-tool-pwsh'
50
- disabled: !!js process.platform !== 'win32'
51
-
52
- # ── filesystem ──────────────────────────────────────────────────────────────
53
-
54
- # Both register into the host `tools` registry and provide nothing, so
55
- # they need no realm. The `fs` service and its policy stay in the host.
56
- - id: tool-fs
57
- name: '@deepseek-ai/dsh-tool-fs'
58
-
59
- - id: tool-fs-search
60
- name: '@deepseek-ai/dsh-tool-fs-search'
61
- config:
62
- sampleOverCapGlobResults: false
63
-
64
- # ── background jobs ────────────────────────────────────────────────────────
65
-
66
- # Only the model-facing controls. The task REGISTRY stays on the host plane:
67
- # its producers sit outside any realm this file could put it in — `tool-bash`
68
- # above resolves it with `ctx.get`, and an entry-local realm here is invisible
69
- # to every sibling row, so `run_in_background` would answer "background jobs
70
- # unavailable" while these controls sat in the catalog. The registry is keyed by
71
- # owning agent anyway, so one host instance serves every session. What a preset
72
- # chooses is whether its agent can collect and stop background work at all.
73
- - id: tool-jobs
74
- name: '@deepseek-ai/dsh-tool-jobs'
75
-
76
- # ── skills ──────────────────────────────────────────────────────────────────
77
-
78
- # The skill REGISTRY lives in the host composition and is layered per scope:
79
- # these rows register into THIS preset's layer of it, so they need no realm.
80
- # `skill-filesystem` contributes local-root discovery for agents on this preset, and
81
- # `tool-skill` gives them the catalog and loader; the merged catalog also
82
- # carries whatever the deployment registered globally (repository plugins).
83
- - id: skill-filesystem
84
- name: '@deepseek-ai/dsh-skill-filesystem'
85
-
86
- - id: tool-skill
87
- name: '@deepseek-ai/dsh-tool-skill'
88
-
89
- # ── evolution agent layer ───────────────────────────────────────────────────
90
12
  # The host bundle provides memory/skill services; this preset only exposes
91
13
  # the model-facing entry points and the native skill-catalog bridge.
92
14
  - id: tool-memory
@@ -95,169 +17,12 @@
95
17
  - id: tool-skill-manage
96
18
  name: '@lmzhen/dsh-tool-skill-manage'
97
19
 
20
+ # Cross-session recall. The memory guidance tells the model to use
21
+ # `session_search` instead of saving task progress, so the tool must be
22
+ # mounted for that guidance to be actionable. The backing index is enabled
23
+ # by evolution-host's `session-query-sqlite` row (see its openAt/path config).
24
+ - id: tool-session-query
25
+ name: '@deepseek-ai/dsh-tool-session-query'
26
+
98
27
  - id: evolution-skill-catalog
99
28
  name: '@lmzhen/dsh-evolution-skill-catalog'
100
-
101
- # ── goals ───────────────────────────────────────────────────────────────────
102
-
103
- # Only the model-facing tool. The goal SERVICE, its session driver, and the
104
- # `/goal` command stay on the host plane: the Gateway serves the goal domain as
105
- # Remote endpoints whose receiver comes from a generated descriptor, so it
106
- # resolves `goals` on the host and an entry-local realm here would hide it. The
107
- # registry is keyed by session anyway, so one host instance serves every
108
- # session. What a preset chooses is whether its agent can call the goal tool.
109
- - id: tool-goal
110
- name: '@deepseek-ai/dsh-tool-goal'
111
-
112
- # ── plan mode ───────────────────────────────────────────────────────────────
113
-
114
- # Plan state is per-agent by nature, so an entry-local realm is not a
115
- # workaround here — it is the correct lifetime.
116
- - id: planning
117
- name: cordis:group
118
- group: true
119
- isolate:
120
- planMode: true
121
- config:
122
- - id: plan-mode
123
- name: '@deepseek-ai/dsh-plan-mode'
124
- config:
125
- section: |
126
- You are in plan mode. Stay in plan mode until exit_plan_mode succeeds or the user switches the session mode. Imperative language to implement changes means plan the implementation, not execute it. A user's conversational agreement — including an answer confirming something you asked — approves nothing and does not end plan mode; fold the confirmed decision into the plan and submit it through exit_plan_mode.
127
-
128
- Explore first. Use non-mutating reads, searches, static analysis, and checks to ground the plan in the actual repository. Do not edit or write files, change configuration, run formatters or code generation that rewrites tracked files, commit, or otherwise carry out the plan. Prefer existing functions and patterns over new machinery.
129
-
130
- The tool catalog stays the same across modes for request-cache stability. These plan-mode rules override any later tool description or guidance that suggests using mutation tools; those tools remain listed to keep the tool catalog unchanged. Do not use todo_write to track this planning phase: it tracks implementation after an approved plan, while the plan itself belongs in exit_plan_mode.
131
-
132
- Resolve discoverable facts by inspection. Use ask_user_question only for user-owned choices or material ambiguity that inspection cannot answer. Do not ask the user where code lives or how current behavior works when you can find out.
133
-
134
- Make the plan decision-complete: state the goal and success criteria; group implementation changes by subsystem; identify public API, schema, and data-flow changes; cover edge cases, failure modes, tests, acceptance criteria, and explicit assumptions. Keep it concise enough to review but detailed enough that another engineer can implement it without making design decisions.
135
-
136
- When ready, call exit_plan_mode with the complete plan markdown, starting with a # title. Make exit_plan_mode the only and final tool call in that assistant response: it presents the plan for approval, and implementation begins only in a later step after approval. Do not paste the final plan as a plain reply or ask "should I proceed?" through prose or ask_user_question. If review rejects it, incorporate the feedback and present again. If the review channel is unavailable or aborted, stay in plan mode and ask the user to switch modes manually; do not proceed with implementation.
137
-
138
- # ── compaction ──────────────────────────────────────────────────────────────
139
-
140
- # `compaction-basic` reads `toolResultPrune` through `ctx.get`, so the pruner must
141
- # share this realm rather than sit outside it.
142
- #
143
- # `tokenMeter` is deliberately NOT in this realm: the meter stays on the HOST
144
- # plane, and the rows here resolve that one instance. It takes no configuration,
145
- # keys every fold by Session, and owns the context-meter projection units the
146
- # browser reads for every session — behind a realm those units would come and go
147
- # with whichever presets happen to be mounted. What a preset chooses is whether
148
- # its agent compacts at all, which is `compaction-basic` below.
149
- - id: compaction
150
- name: cordis:group
151
- group: true
152
- isolate:
153
- compaction: true
154
- toolResultPruner: true
155
- config:
156
- - id: compaction-basic
157
- name: '@deepseek-ai/dsh-compaction-basic'
158
-
159
- - id: command-compact
160
- name: '@deepseek-ai/dsh-command-compact'
161
-
162
- - id: tool-result-pruner
163
- name: '@deepseek-ai/dsh-compaction-tool-result-pruner'
164
- config:
165
- thresholdChars: 8192
166
- headChars: 4096
167
- tailChars: 1024
168
-
169
- # ── delegation and workflows ────────────────────────────────────────────────
170
-
171
- # The `subagents` registry and its spawn/fork backends live in the HOST
172
- # composition: the registry is a process singleton whose cross-session queries
173
- # the api-proxy serves to the browser, and a provider name may only be
174
- # registered once. This preset contributes the delegation TOOLS, which resolve
175
- # that host registry.
176
- #
177
- # `workflows` is different — nothing outside an agent reads it — so every row
178
- # that reaches it shares one entry-local realm here, and a consumer left
179
- # outside would resolve a host registry this preset does not populate.
180
- #
181
- # `tool-subagent-report` is host-plane for the same reason as the registry,
182
- # not because a preset may not want it: it registers a CONTINUABLE SETUP on
183
- # that singleton rather than a tool this agent calls, and the setup list is
184
- # not scope-aware — one copy per mounted preset means every child gets
185
- # `report` registered once per live session, which throws on the second.
186
- - id: delegation
187
- name: cordis:group
188
- group: true
189
- isolate:
190
- workflowEngine: true
191
- config:
192
- - id: tool-subagent-control
193
- name: '@deepseek-ai/dsh-tool-subagent-control'
194
-
195
- - id: tool-subagent-list-agents
196
- name: '@deepseek-ai/dsh-tool-subagent-control/list-agents'
197
-
198
- - id: tool-subagent
199
- name: '@deepseek-ai/dsh-tool-subagent'
200
- config:
201
- provider: spawn
202
- toolName: subagent
203
- backgroundMode: continuable
204
-
205
- - id: tool-subagent-fork
206
- name: '@deepseek-ai/dsh-tool-subagent'
207
- config:
208
- provider: fork
209
- toolName: subagent_fork
210
- backgroundMode: continuable
211
-
212
- # Product providers are host-plane singletons. Copy this preset, then
213
- # remove `disabled` from either ordinary tool row to expose that product
214
- # only to agents composed from the copy.
215
- - id: tool-subagent-codex
216
- name: '@deepseek-ai/dsh-tool-subagent'
217
- disabled: true
218
- config:
219
- provider: codex
220
- toolName: subagent_codex
221
- enableRunInBackground: false
222
- maxDepth: provider-managed
223
-
224
- - id: tool-subagent-claude-code
225
- name: '@deepseek-ai/dsh-tool-subagent'
226
- disabled: true
227
- config:
228
- provider: claude-code
229
- toolName: subagent_claude_code
230
- enableRunInBackground: false
231
- maxDepth: provider-managed
232
-
233
- - id: workflow-worker-thread
234
- name: '@deepseek-ai/dsh-workflow-worker-thread'
235
- config:
236
- provider: spawn
237
-
238
- - id: tool-workflow
239
- name: '@deepseek-ai/dsh-tool-workflow'
240
-
241
- - id: tool-ralph
242
- name: '@deepseek-ai/dsh-tool-ralph'
243
- config:
244
- subagentProvider: spawn
245
- maxRounds: 64
246
-
247
- # ── remaining model-facing rows ─────────────────────────────────────────────
248
-
249
- - id: tool-ask-user
250
- name: '@deepseek-ai/dsh-tool-ask-user'
251
-
252
- - id: tool-todo
253
- name: '@deepseek-ai/dsh-tool-todo'
254
- config:
255
- allowParallelInProgress: true
256
-
257
- # The `web` service and its search provider stay in the host composition; only
258
- # the model-facing tool is per-session.
259
- - id: tool-web
260
- name: '@deepseek-ai/dsh-tool-web'
261
- config:
262
- fetch: false
263
- searchTimeoutMs: 60000
@@ -1,8 +1,8 @@
1
1
  /**
2
- * @deepseek-ai/dsh-evolution-agent — composition package.
2
+ * @deepseek-ai/dsh-evolution-agent-preset — composition package.
3
3
  * The package's substance is its YAML composition files declared through the
4
4
  * package manifest; this module carries no runtime API.
5
- * @module @deepseek-ai/dsh-evolution-agent
5
+ * @module @deepseek-ai/dsh-evolution-agent-preset
6
6
  */
7
7
  export {};
8
8
  //# sourceMappingURL=index.d.ts.map
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@lmzhen/dsh-evolution-agent-preset",
3
3
  "description": "Agent preset exposing memory and skill evolution tools to a session (community build)",
4
- "version": "0.1.0-rc.9",
4
+ "version": "0.1.0",
5
5
  "publishConfig": {
6
6
  "access": "public"
7
7
  },
@@ -22,9 +22,10 @@
22
22
  ],
23
23
  "license": "MIT",
24
24
  "dependencies": {
25
- "@lmzhen/dsh-tool-memory": "^0.1.0-rc.9",
26
- "@lmzhen/dsh-tool-skill-manage": "^0.1.0-rc.9",
27
- "@lmzhen/dsh-evolution-skill-catalog": "^0.1.0-rc.9"
25
+ "@deepseek-ai/dsh-tool-session-query": "^0.1.1-rc.2",
26
+ "@lmzhen/dsh-tool-memory": "^0.1.0",
27
+ "@lmzhen/dsh-tool-skill-manage": "^0.1.0",
28
+ "@lmzhen/dsh-evolution-skill-catalog": "^0.1.0"
28
29
  },
29
30
  "exports": {
30
31
  "./invariant": {
@@ -40,11 +41,11 @@
40
41
  "./package.json": "./package.json"
41
42
  },
42
43
  "peerDependencies": {
43
- "@deepseek-ai/dsh-invariants": "^0.1.0-rc.6",
44
+ "@deepseek-ai/dsh-invariants": "^0.1.1-rc.2",
44
45
  "@deepseek-ai/cordis": "^4.0.1"
45
46
  },
46
47
  "devDependencies": {
47
- "@deepseek-ai/dsh-invariants": "^0.1.0-rc.6",
48
+ "@deepseek-ai/dsh-invariants": "^0.1.1-rc.2",
48
49
  "@deepseek-ai/cordis": "^4.0.1"
49
50
  },
50
51
  "main": "lib/index.js",