dsh-deep-ptc-mode 1.2.0 → 1.3.1
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 +16 -0
- package/LICENSE +0 -0
- package/README.md +58 -77
- package/README.zh.md +66 -79
- package/assets/icon.png +0 -0
- package/compatibility.json +5 -0
- package/cordis.patch.yml +5 -224
- package/lib/client.js +111 -0
- package/lib/environment.mjs +14 -0
- package/lib/executor.mjs +34 -0
- package/lib/index.mjs +29 -0
- package/lib/lifecycle.mjs +30 -0
- package/lib/model.mjs +77 -0
- package/lib/preset.json +209 -0
- package/lib/terminal.mjs +41 -0
- package/package.json +75 -4
package/lib/preset.json
ADDED
|
@@ -0,0 +1,209 @@
|
|
|
1
|
+
{
|
|
2
|
+
"id": "deep-ptc",
|
|
3
|
+
"order": 5,
|
|
4
|
+
"plugins": [
|
|
5
|
+
{
|
|
6
|
+
"id": "persona",
|
|
7
|
+
"name": "@deepseek-ai/dsh-persona",
|
|
8
|
+
"config": {
|
|
9
|
+
"prefix": "You are a coding agent powered by the {{model}} model, working in Deep PTC mode. Use the available tools to complete the user's task carefully, keep progress visible, and verify the result.",
|
|
10
|
+
"suffix": "## Work visibly\n\n- Use the user's language. Before the first inspection, say what you will check. Report findings, decisions, direction changes, delegation and verification at real milestones. During active work, aim for a useful update about every 30–60 seconds at a tool boundary. Combine trivial repeated reads; do not narrate every call. One short sentence is usually enough; a one-step task needs only an introduction and its result.\n- Give run_code programs clear human descriptions. Batch independent inspections, keep dependent actions sequential, and bound output. A long foreground call prevents timely steering; prefer short calls and managed background jobs. Handle new user messages at the next available step boundary.\n\n## Clarify meaning and preserve scope\n\n- Establish inspectable facts yourself: file locations, installed names, versions and current behavior. An unfamiliar name can first receive one focused, read-only lookup in the relevant installation or workspace. Stop that lookup when it identifies the referent or reveals ambiguity; do not turn it into broad exploration or use search results to invent the user's intent.\n- Ask early when multiple plausible referents remain, a private term cannot be resolved, a consequential preference changes the solution, or acceptance criteria materially affect the work. Ask one to three self-contained questions with concrete choices when useful. Otherwise state a reasonable, reversible assumption and proceed. Do not ask about facts that a cheap inspection establishes.\n- Use the available question tool through run_code. A program whose only job is a question should only ask. Give that program enough time within the runtime's actual cap; do not copy a fixed timeout blindly. Pending or timed-out questions remain unanswered, and silence is not approval. Continue independent work while a required answer is pending; do not perform dependent actions.\n- A user's answer or explicit delegation of a choice wins over your assumptions and these defaults. Keep it across turns and compaction. Do the smallest complete piece of work that satisfies the request; avoid unrelated features, refactors and abstractions. Ask before a material expansion, not before ordinary edits already authorized by the request.\n\n## Plan and respect existing authorization\n\n- For small linear tasks, plan internally and act. For work spanning several steps or subsystems, show a concise plan with the goal, changes and verification, then continue. Explain consequential assumptions and boundaries when they matter.\n- Estimated time determines how much planning to show, not whether authorization expires. A slower investigation or a task crossing twenty minutes does not by itself require approval. Update the plan when new evidence changes the work; do not repeatedly ask for permission already granted.\n- Pause only for an unresolved decision that materially changes the outcome, a new action outside the authorized scope, or an applicable approval requirement. Complete independent preparation so any approval concerns a concrete result. Explicit plan mode always wins: stay read-only and use its prescribed exit_plan_mode approval process before implementation.\n\n## Use evidence and finish verification\n\n- Use your full capability within the task's requirements. Do not sacrifice a necessary read, search, command or check merely to shorten the answer or reduce tool use. This preset does not grant extra tokens, change billing or remove runtime limits.\n- Inspect current evidence instead of relying on memory. Reproduce relevant failures when practical, check the changed behavior and touched edge cases, and inspect your own changes. Distinguish a passed check from an assumption and static inspection from an end-to-end test.\n- Verification has a stopping point: once acceptance criteria are met, relevant checks pass and material uncertainty is resolved, finish. Reopen a check only for a new change, failure or conflicting evidence. Do not repeat successful checks to appear thorough or expand the project to test it.\n- Keep context and output bounded; use the provided compaction and pruning mechanisms. Spend effort on correctness and relevant uncertainty, not repetition or lengthy narration. Final answers state the outcome, meaningful verification and remaining limitations concisely.\n\n## Wait according to the task's lifecycle\n\n- Track every managed background job id. A build or test that will finish can run in the background while you continue independent work. If no useful step remains, say what is pending and end the turn; resume on its completion notice, read its output and complete dependent work. Never report pending verification as passed.\n- A server or watcher is a long-lived service: start it as a managed job, check readiness with a bounded health/port probe, then continue the actual test or browser validation. Do not wait for the service to exit before doing the work it enables. Stop services you created when no longer needed, unless keeping them is part of the task.\n- An external task id is not automatically a Harness job. Use that service's real completion notification, bounded status checks or a supported reminder. Identify failure, timeout and missing-notification behavior before relying on an automatic wakeup. Use schedule_create only when the user requested later work or a reminder is necessary to complete the current task; avoid duplicate recurring reminders.\n- Do not busy-poll or sleep inside run_code to wait out long work. Prefer bounded waits at step boundaries. Cancel obsolete work; collect all still-relevant results before declaring completion.\n\n## Delegate deliberately\n\n- Keep small sequential work with one agent. Delegate genuinely independent pieces, broad inspection that would overwhelm one context, or a useful independent review. Use only delegation tools actually listed; an explicit user preference about delegation takes precedence.\n- Give each worker a clear goal, necessary context, constraints, acceptance criteria and a disjoint write scope. Record team responsibilities and dependencies when team tools exist. Do not duplicate running work; send corrections to its current owner.\n- Collect results through the channel that tool actually provides: team waiting, a child completion message, a synchronous return or a managed job. Do not require wait_agent or list_agents when absent, and do not infer that a one-shot child is missing because it is not discoverable. Review the evidence and final state yourself.\n\n## Honor the selected execution environment\n\n- Follow this preset's execution-environment section and the live tool contract for shell syntax, paths and working directory. Windows hosting WSL still uses host-side paths for file tools and workdir; command source runs in the selected Linux distribution. Native PowerShell and macOS/Linux shells have their own syntax. Never silently substitute another shell after a failure or bypass the active sandbox policy."
|
|
11
|
+
}
|
|
12
|
+
},
|
|
13
|
+
{
|
|
14
|
+
"id": "agent-instructions",
|
|
15
|
+
"name": "@deepseek-ai/dsh-agent-instructions",
|
|
16
|
+
"config": {
|
|
17
|
+
"maxBytes": 65536
|
|
18
|
+
}
|
|
19
|
+
},
|
|
20
|
+
{
|
|
21
|
+
"id": "time-context",
|
|
22
|
+
"name": "@deepseek-ai/dsh-time-context"
|
|
23
|
+
},
|
|
24
|
+
{
|
|
25
|
+
"id": "tool-bash",
|
|
26
|
+
"name": "@deepseek-ai/dsh-tool-bash",
|
|
27
|
+
"disabled": {
|
|
28
|
+
"__jsExpr": "process.platform === 'win32'"
|
|
29
|
+
}
|
|
30
|
+
},
|
|
31
|
+
{
|
|
32
|
+
"id": "tool-pwsh",
|
|
33
|
+
"name": "@deepseek-ai/dsh-tool-pwsh",
|
|
34
|
+
"disabled": {
|
|
35
|
+
"__jsExpr": "process.platform !== 'win32'"
|
|
36
|
+
}
|
|
37
|
+
},
|
|
38
|
+
{
|
|
39
|
+
"id": "tool-fs",
|
|
40
|
+
"name": "@deepseek-ai/dsh-tool-fs"
|
|
41
|
+
},
|
|
42
|
+
{
|
|
43
|
+
"id": "tool-fs-search",
|
|
44
|
+
"name": "@deepseek-ai/dsh-tool-fs-search",
|
|
45
|
+
"config": {
|
|
46
|
+
"sampleOverCapGlobResults": false
|
|
47
|
+
}
|
|
48
|
+
},
|
|
49
|
+
{
|
|
50
|
+
"id": "tool-jobs",
|
|
51
|
+
"name": "@deepseek-ai/dsh-tool-jobs"
|
|
52
|
+
},
|
|
53
|
+
{
|
|
54
|
+
"id": "tool-schedule",
|
|
55
|
+
"name": "@deepseek-ai/dsh-tool-schedule"
|
|
56
|
+
},
|
|
57
|
+
{
|
|
58
|
+
"id": "skill-filesystem",
|
|
59
|
+
"name": "@deepseek-ai/dsh-skill-filesystem"
|
|
60
|
+
},
|
|
61
|
+
{
|
|
62
|
+
"id": "tool-skill",
|
|
63
|
+
"name": "@deepseek-ai/dsh-tool-skill"
|
|
64
|
+
},
|
|
65
|
+
{
|
|
66
|
+
"id": "command-goal",
|
|
67
|
+
"name": "@deepseek-ai/dsh-command-goal"
|
|
68
|
+
},
|
|
69
|
+
{
|
|
70
|
+
"id": "tool-goal",
|
|
71
|
+
"name": "@deepseek-ai/dsh-tool-goal"
|
|
72
|
+
},
|
|
73
|
+
{
|
|
74
|
+
"id": "planning",
|
|
75
|
+
"name": "cordis:group",
|
|
76
|
+
"group": true,
|
|
77
|
+
"isolate": {
|
|
78
|
+
"planMode": true
|
|
79
|
+
},
|
|
80
|
+
"config": [
|
|
81
|
+
{
|
|
82
|
+
"id": "plan-mode",
|
|
83
|
+
"name": "@deepseek-ai/dsh-plan-mode",
|
|
84
|
+
"config": {
|
|
85
|
+
"section": "You are in plan mode. Stay in plan mode until the user approves your plan through exit_plan_mode or 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.\n\nExplore 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.\n\nThe 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.\n\nResolve 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.\n\nMake 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.\n\nWhen 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.\n"
|
|
86
|
+
}
|
|
87
|
+
}
|
|
88
|
+
]
|
|
89
|
+
},
|
|
90
|
+
{
|
|
91
|
+
"id": "compaction",
|
|
92
|
+
"name": "cordis:group",
|
|
93
|
+
"group": true,
|
|
94
|
+
"isolate": {
|
|
95
|
+
"compaction": true,
|
|
96
|
+
"toolResultPruner": true
|
|
97
|
+
},
|
|
98
|
+
"config": [
|
|
99
|
+
{
|
|
100
|
+
"id": "compaction-basic",
|
|
101
|
+
"name": "@deepseek-ai/dsh-compaction-basic"
|
|
102
|
+
},
|
|
103
|
+
{
|
|
104
|
+
"id": "command-compact",
|
|
105
|
+
"name": "@deepseek-ai/dsh-command-compact"
|
|
106
|
+
},
|
|
107
|
+
{
|
|
108
|
+
"id": "tool-result-pruner",
|
|
109
|
+
"name": "@deepseek-ai/dsh-compaction-tool-result-pruner",
|
|
110
|
+
"config": {
|
|
111
|
+
"thresholdChars": 8192,
|
|
112
|
+
"headChars": 4096,
|
|
113
|
+
"tailChars": 1024
|
|
114
|
+
}
|
|
115
|
+
}
|
|
116
|
+
]
|
|
117
|
+
},
|
|
118
|
+
{
|
|
119
|
+
"id": "delegation",
|
|
120
|
+
"name": "cordis:group",
|
|
121
|
+
"group": true,
|
|
122
|
+
"isolate": {
|
|
123
|
+
"workflowEngine": true
|
|
124
|
+
},
|
|
125
|
+
"config": [
|
|
126
|
+
{
|
|
127
|
+
"id": "tool-subagent-control",
|
|
128
|
+
"name": "@deepseek-ai/dsh-tool-subagent-control"
|
|
129
|
+
},
|
|
130
|
+
{
|
|
131
|
+
"id": "tool-subagent-list-agents",
|
|
132
|
+
"name": "@deepseek-ai/dsh-tool-subagent-control/list-agents"
|
|
133
|
+
},
|
|
134
|
+
{
|
|
135
|
+
"id": "tool-subagent",
|
|
136
|
+
"name": "@deepseek-ai/dsh-tool-subagent",
|
|
137
|
+
"config": {
|
|
138
|
+
"provider": "spawn",
|
|
139
|
+
"toolName": "subagent",
|
|
140
|
+
"modelSelectionSettings": true
|
|
141
|
+
}
|
|
142
|
+
},
|
|
143
|
+
{
|
|
144
|
+
"id": "tool-subagent-fork",
|
|
145
|
+
"name": "@deepseek-ai/dsh-tool-subagent",
|
|
146
|
+
"config": {
|
|
147
|
+
"provider": "fork",
|
|
148
|
+
"toolName": "subagent_fork"
|
|
149
|
+
}
|
|
150
|
+
},
|
|
151
|
+
{
|
|
152
|
+
"id": "workflow-ptc",
|
|
153
|
+
"name": "@deepseek-ai/dsh-workflow-ptc",
|
|
154
|
+
"disabled": true,
|
|
155
|
+
"config": {
|
|
156
|
+
"provider": "spawn"
|
|
157
|
+
}
|
|
158
|
+
},
|
|
159
|
+
{
|
|
160
|
+
"id": "tool-workflow",
|
|
161
|
+
"name": "@deepseek-ai/dsh-tool-workflow",
|
|
162
|
+
"disabled": true
|
|
163
|
+
}
|
|
164
|
+
]
|
|
165
|
+
},
|
|
166
|
+
{
|
|
167
|
+
"id": "tool-ask-user",
|
|
168
|
+
"name": "@deepseek-ai/dsh-tool-ask-user"
|
|
169
|
+
},
|
|
170
|
+
{
|
|
171
|
+
"id": "tool-todo",
|
|
172
|
+
"name": "@deepseek-ai/dsh-tool-todo",
|
|
173
|
+
"config": {
|
|
174
|
+
"allowParallelInProgress": true
|
|
175
|
+
}
|
|
176
|
+
},
|
|
177
|
+
{
|
|
178
|
+
"id": "tool-web",
|
|
179
|
+
"name": "@deepseek-ai/dsh-tool-web",
|
|
180
|
+
"config": {
|
|
181
|
+
"fetch": true,
|
|
182
|
+
"searchTimeoutMs": 60000
|
|
183
|
+
}
|
|
184
|
+
},
|
|
185
|
+
{
|
|
186
|
+
"id": "tool-presentation",
|
|
187
|
+
"name": "@deepseek-ai/dsh-agent-tool-presentation",
|
|
188
|
+
"config": {
|
|
189
|
+
"mode": "ptc"
|
|
190
|
+
}
|
|
191
|
+
},
|
|
192
|
+
{
|
|
193
|
+
"id": "present",
|
|
194
|
+
"name": "@deepseek-ai/dsh-tool-present"
|
|
195
|
+
},
|
|
196
|
+
{
|
|
197
|
+
"id": "tool-plugin-manager",
|
|
198
|
+
"name": "@deepseek-ai/dsh-plugin-manager/tools",
|
|
199
|
+
"disabled": true
|
|
200
|
+
},
|
|
201
|
+
{
|
|
202
|
+
"id": "tool-plugin-market",
|
|
203
|
+
"name": "@deepseek-ai/dsh-plugin-market/tools",
|
|
204
|
+
"disabled": true
|
|
205
|
+
}
|
|
206
|
+
],
|
|
207
|
+
"name": "深度PTC模式",
|
|
208
|
+
"description": "持续汇报、先查证再澄清、充分验证并及时收尾;可选择 WSL、PowerShell、macOS Zsh 或原生 Bash。"
|
|
209
|
+
}
|
package/lib/terminal.mjs
ADDED
|
@@ -0,0 +1,41 @@
|
|
|
1
|
+
import { apply as applyBash } from '@deepseek-ai/dsh-tool-bash';
|
|
2
|
+
|
|
3
|
+
export const name = 'deep-ptc-zsh-tool';
|
|
4
|
+
export const inject = ['tools', 'shell', 'systemPrompt', 'shellEnv', 'workingDirectory'];
|
|
5
|
+
|
|
6
|
+
// Keep the official execution, jobs and approval implementation; adapt its public dialect.
|
|
7
|
+
export function apply(ctx) {
|
|
8
|
+
const dialect = text => text.replace(/\bbash\b/gu, 'zsh').replace(/\bBash\b/gu, 'Zsh');
|
|
9
|
+
const tools = new Proxy(ctx.tools, {
|
|
10
|
+
get(target, key) {
|
|
11
|
+
if (key === 'register') return definition => target.register({
|
|
12
|
+
...definition, name: definition.name === 'bash' ? 'zsh' : definition.name,
|
|
13
|
+
description: dialect(definition.description),
|
|
14
|
+
});
|
|
15
|
+
const value = Reflect.get(target, key, target);
|
|
16
|
+
return typeof value === 'function' ? value.bind(target) : value;
|
|
17
|
+
},
|
|
18
|
+
});
|
|
19
|
+
const systemPrompt = new Proxy(ctx.systemPrompt, {
|
|
20
|
+
get(target, key) {
|
|
21
|
+
if (key === 'section') return section => target.section({ ...section,
|
|
22
|
+
name: section.name === 'tool:bash' ? 'tool:zsh' : section.name, text: dialect(section.text) });
|
|
23
|
+
const value = Reflect.get(target, key, target);
|
|
24
|
+
return typeof value === 'function' ? value.bind(target) : value;
|
|
25
|
+
},
|
|
26
|
+
});
|
|
27
|
+
// A proxy preserves the real Cordis context for inject/effects, changing only the registry face.
|
|
28
|
+
const adapted = new Proxy(ctx, {
|
|
29
|
+
get(target, key) {
|
|
30
|
+
if (key === 'tools') return tools;
|
|
31
|
+
if (key === 'systemPrompt') return systemPrompt;
|
|
32
|
+
const value = Reflect.get(target, key, target);
|
|
33
|
+
if (key === 'inject') return (dependencies, callback) => target.inject(dependencies, child => {
|
|
34
|
+
const wrapped = new Proxy(child, { get(c, k) { return k === 'tools' ? tools : Reflect.get(c, k, c); } });
|
|
35
|
+
return callback(wrapped);
|
|
36
|
+
});
|
|
37
|
+
return typeof value === 'function' ? value.bind(target) : value;
|
|
38
|
+
},
|
|
39
|
+
});
|
|
40
|
+
applyBash(adapted);
|
|
41
|
+
}
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "dsh-deep-ptc-mode",
|
|
3
|
-
"version": "1.
|
|
4
|
-
"description": "Deep PTC
|
|
3
|
+
"version": "1.3.1",
|
|
4
|
+
"description": "Deep PTC with visible progress, scoped verification, lifecycle-aware background work and selectable WSL, PowerShell, Bash or Zsh execution.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"keywords": [
|
|
7
7
|
"dsh-plugin",
|
|
@@ -13,7 +13,11 @@
|
|
|
13
13
|
"clarification"
|
|
14
14
|
],
|
|
15
15
|
"license": "MIT",
|
|
16
|
-
"author":
|
|
16
|
+
"author": {
|
|
17
|
+
"name": "lishize20040802-rgb",
|
|
18
|
+
"email": "lishize20040802@gmail.com",
|
|
19
|
+
"url": "https://github.com/lishize20040802-rgb"
|
|
20
|
+
},
|
|
17
21
|
"repository": {
|
|
18
22
|
"type": "git",
|
|
19
23
|
"url": "git+https://github.com/lishize20040802-rgb/dsh-deep-ptc-mode.git"
|
|
@@ -24,18 +28,85 @@
|
|
|
24
28
|
},
|
|
25
29
|
"files": [
|
|
26
30
|
"cordis.patch.yml",
|
|
31
|
+
"lib",
|
|
32
|
+
"compatibility.json",
|
|
27
33
|
"README.md",
|
|
28
34
|
"README.zh.md",
|
|
35
|
+
"CHANGELOG.md",
|
|
29
36
|
"assets/icon.png"
|
|
30
37
|
],
|
|
31
38
|
"engines": {
|
|
32
39
|
"node": ">=24",
|
|
33
|
-
"dsh": ">=0.2.1-rc.
|
|
40
|
+
"dsh": ">=0.2.1-rc.5"
|
|
34
41
|
},
|
|
35
42
|
"dsh": {
|
|
36
43
|
"manifestVersion": 1,
|
|
37
44
|
"bundle": {
|
|
38
45
|
"patch": "./cordis.patch.yml"
|
|
46
|
+
},
|
|
47
|
+
"client": {
|
|
48
|
+
"platform": "web",
|
|
49
|
+
"inject": [
|
|
50
|
+
"@deepseek-ai/dsh-client-locale",
|
|
51
|
+
"@deepseek-ai/dsh-client-ui-settings",
|
|
52
|
+
"@deepseek-ai/dsh-client-ui-plugin-manager"
|
|
53
|
+
]
|
|
54
|
+
}
|
|
55
|
+
},
|
|
56
|
+
"main": "lib/index.mjs",
|
|
57
|
+
"exports": {
|
|
58
|
+
".": "./lib/index.mjs",
|
|
59
|
+
"./executor": "./lib/executor.mjs",
|
|
60
|
+
"./terminal": "./lib/terminal.mjs",
|
|
61
|
+
"./environment": "./lib/environment.mjs",
|
|
62
|
+
"./client": "./lib/client.js",
|
|
63
|
+
"./package.json": "./package.json"
|
|
64
|
+
},
|
|
65
|
+
"scripts": {
|
|
66
|
+
"test": "node --test",
|
|
67
|
+
"check": "node scripts/check.mjs",
|
|
68
|
+
"check:upstream": "node scripts/check.mjs --upstream",
|
|
69
|
+
"prepack": "npm run check && npm test"
|
|
70
|
+
},
|
|
71
|
+
"devDependencies": {
|
|
72
|
+
"js-yaml": "4.3.2",
|
|
73
|
+
"react": "18.3.1",
|
|
74
|
+
"react-test-renderer": "18.3.1"
|
|
75
|
+
},
|
|
76
|
+
"peerDependencies": {
|
|
77
|
+
"@deepseek-ai/schemastery": "^3.18.4",
|
|
78
|
+
"@deepseek-ai/dsh-bash-local": ">=0.2.1-rc.5",
|
|
79
|
+
"@deepseek-ai/dsh-bash-sandbox": ">=0.2.1-rc.5",
|
|
80
|
+
"@deepseek-ai/dsh-tool-bash": ">=0.2.1-rc.5",
|
|
81
|
+
"@deepseek-ai/dsh-client-ui-renderer": ">=0.2.1-rc.5",
|
|
82
|
+
"@deepseek-ai/dsh-client-ui-settings": ">=0.2.1-rc.5",
|
|
83
|
+
"@deepseek-ai/dsh-client-ui-slots": ">=0.2.1-rc.5",
|
|
84
|
+
"@deepseek-ai/dsh-client-locale": ">=0.2.1-rc.5"
|
|
85
|
+
},
|
|
86
|
+
"peerDependenciesMeta": {
|
|
87
|
+
"@deepseek-ai/schemastery": {
|
|
88
|
+
"optional": true
|
|
89
|
+
},
|
|
90
|
+
"@deepseek-ai/dsh-bash-local": {
|
|
91
|
+
"optional": true
|
|
92
|
+
},
|
|
93
|
+
"@deepseek-ai/dsh-bash-sandbox": {
|
|
94
|
+
"optional": true
|
|
95
|
+
},
|
|
96
|
+
"@deepseek-ai/dsh-tool-bash": {
|
|
97
|
+
"optional": true
|
|
98
|
+
},
|
|
99
|
+
"@deepseek-ai/dsh-client-ui-renderer": {
|
|
100
|
+
"optional": true
|
|
101
|
+
},
|
|
102
|
+
"@deepseek-ai/dsh-client-ui-settings": {
|
|
103
|
+
"optional": true
|
|
104
|
+
},
|
|
105
|
+
"@deepseek-ai/dsh-client-ui-slots": {
|
|
106
|
+
"optional": true
|
|
107
|
+
},
|
|
108
|
+
"@deepseek-ai/dsh-client-locale": {
|
|
109
|
+
"optional": true
|
|
39
110
|
}
|
|
40
111
|
}
|
|
41
112
|
}
|