@deepseek-ai/dsh-tool-jobs 0.2.0-rc.2 → 0.2.1-alpha.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.
Files changed (4) hide show
  1. package/README.i18n.yaml +5 -5
  2. package/README.md +2 -3
  3. package/README.zh.md +1 -2
  4. package/package.json +18 -18
package/README.i18n.yaml CHANGED
@@ -9,7 +9,7 @@
9
9
  en: 256894de7b318e7e
10
10
  zh: a6f3cb0060fe2c4d
11
11
  /deepseek-ai-dsh-tool-jobs/summary:
12
- en: 945e3cec059e1a89
12
+ en: b32de88c29a3c2e0
13
13
  zh: 63142a605332b4b7
14
14
  /deepseek-ai-dsh-tool-jobs/table-of-contents:
15
15
  en: d152484eb41ac6b4
@@ -33,11 +33,11 @@
33
33
  en: 32a36a3fe388e2c1
34
34
  zh: f4bd2866fff6fa8d
35
35
  /deepseek-ai-dsh-tool-jobs/understand-the-implementation/design-philosophy:
36
- en: 5b69ae2716a52951
37
- zh: fec78d84af7192b1
36
+ en: e1d89b73fdcc5b24
37
+ zh: 38dd176ae111561f
38
38
  /deepseek-ai-dsh-tool-jobs/understand-the-implementation/source-map:
39
- en: 354782dee6840110
40
- zh: dfd46a4eee6b937d
39
+ en: 6f006ff2d901bc92
40
+ zh: 779d18ba7bec4202
41
41
  /deepseek-ai-dsh-tool-jobs/understand-the-implementation/output-capping:
42
42
  en: b47638fb0e80287a
43
43
  zh: c47fa4b99b6df4c3
package/README.md CHANGED
@@ -9,7 +9,7 @@ English | [中文](README.zh.md)
9
9
 
10
10
  ## Summary
11
11
 
12
- Use `dsh-tool-jobs` to inspect and control background commands, PTY work, and subagents through `job_output`, `job_list`, and `job_kill`. Reads can wait within a configured timeout, list results identify each job's kind and status, and cancellation settles only after the work stops. When owned work finishes, the agent receives an in-session notice: busy agents receive it in their next step, while idle agents are woken by a follow-up turn. Configuration controls wait limits, completion delivery, and an optional cap on consecutive wakeups. Stream output is consumed by one reader, and pending notices do not survive owner disposal.
12
+ Use `dsh-tool-jobs` to inspect and control background commands and PTY work through `job_output`, `job_list`, and `job_kill`. Reads can wait within a configured timeout, list results identify each job's kind and status, and cancellation settles only after the work stops. When owned work finishes, the agent receives an in-session notice: busy agents receive it in their next step, while idle agents are woken by a follow-up turn. Configuration controls wait limits, completion delivery, and an optional cap on consecutive wakeups. Stream output is consumed by one reader, and pending notices do not survive owner disposal.
13
13
 
14
14
  ## Table of Contents
15
15
 
@@ -74,7 +74,7 @@ This section explains the design decisions behind the tools and points at the co
74
74
 
75
75
  ### Design philosophy
76
76
 
77
- - **Kind-independent controls.** The same three tools read, list, and cancel jobs of every producer kind — bash, subagent, PTY — because all of them register through the generic `ctx.jobs` runtime.
77
+ - **Kind-independent controls.** The same three tools read, list, and cancel jobs of every producer kind — bash, PTY — because all of them register through the generic `ctx.jobs` runtime.
78
78
  - **Delivery is owned here; recipients are the registry's.** The plugin decides how an unreported completion reaches the owner — injected into a busy step, or a woken turn on an idle owner — while the registry routes each settlement to the listeners its owner's scope chain reaches, so a mount under one preset never sees another preset's agents, and an agent reads exactly one notice per completion however many presets are mounted.
79
79
  - **Producer-owned output bounds.** When a producer supplies `outputLimitBytes`, the complete model-facing result — output read, terminal kill snapshot, or completion notice — is capped after status and notice metadata are added; producers that omit it keep unbounded behavior.
80
80
 
@@ -84,7 +84,6 @@ This section explains the design decisions behind the tools and points at the co
84
84
  |---|---|
85
85
  | [`src/index.ts`](src/index.ts) | Plugin entry: tool registrations, the settlement subscription and model-kill set, prompt section, output capping |
86
86
  | [`src/render.ts`](src/render.ts) | Model-facing rendering: the public projection, status lines, and the consuming delta (stdout, `[stderr]` section, dropped-output notice) |
87
- | — | No runtime invariant companion is published; this model-facing adapter has no independent lifecycle stream; execution relations are owned by the capability seam it calls. |
88
87
 
89
88
  ### Output capping
90
89
 
package/README.zh.md CHANGED
@@ -74,7 +74,7 @@ kind: "package-reference"
74
74
 
75
75
  ### 设计理念
76
76
 
77
- - **与 kind 无关的控制。** 同一套三个工具读取、列出和取消每种生产方 kind 的任务——bash、subagent、PTY——因为它们都通过通用的 `ctx.jobs` 运行时注册。
77
+ - **与 kind 无关的控制。** 同一套三个工具读取、列出和取消每种生产方 kind 的任务——bash、PTY——因为它们都通过通用的 `ctx.jobs` 运行时注册。
78
78
  - **投递归本插件，收件人归注册表。** 插件决定未报告的完成如何到达所有者——注入繁忙的一步，或唤醒空闲所有者的一轮——而注册表把每次结算路由给其所有者 scope 链所能抵达的监听器，因此某个 preset 下的挂载永远看不到另一个 preset 的 agent，无论挂载了多少 preset，一个 agent 每次完成都只读到一条通知。
79
79
  - **生产方自有的输出上限。** 生产方提供 `outputLimitBytes` 时，完整的模型侧结果——输出读取、终止 kill 快照或完成通知——会在添加状态与通知元数据之后被施加上限；省略该字段的生产方保持无界行为。
80
80
 
@@ -84,7 +84,6 @@ kind: "package-reference"
84
84
  |---|---|
85
85
  | [`src/index.ts`](src/index.ts) | 插件入口：工具注册、结算订阅与模型杀停集合、提示词区段、输出上限 |
86
86
  | [`src/render.ts`](src/render.ts) | 面向模型的渲染：公共投影、状态行与消耗式增量（stdout、`[stderr]` 段、丢失输出提示） |
87
- | — | 不发布运行时不变式伴生入口；执行关系归能力 seam 所有。 |
88
87
 
89
88
  ### 输出上限
90
89
 
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@deepseek-ai/dsh-tool-jobs",
3
3
  "description": "Model-facing background job control tools (job_output, job_list, job_kill) over the ctx.jobs registry",
4
- "version": "0.2.0-rc.2",
4
+ "version": "0.2.1-alpha.2",
5
5
  "publishConfig": {
6
6
  "access": "public"
7
7
  },
@@ -27,26 +27,26 @@
27
27
  ],
28
28
  "license": "MIT",
29
29
  "dependencies": {
30
- "@deepseek-ai/schemastery": "~3.18.4"
30
+ "@deepseek-ai/schemastery": "~3.18.5-alpha.1"
31
31
  },
32
32
  "peerDependencies": {
33
- "@deepseek-ai/dsh-llm": "0.2.0-rc.2",
34
- "@deepseek-ai/dsh-output-retention": "0.2.0-rc.2",
35
- "@deepseek-ai/dsh-agent": "0.2.0-rc.2",
36
- "@deepseek-ai/dsh-jobs": "0.2.0-rc.2",
37
- "@deepseek-ai/dsh-tools": "0.2.0-rc.2",
38
- "@deepseek-ai/cordis": "~4.0.4",
39
- "@deepseek-ai/dsh-system-prompt": "0.2.0-rc.2"
33
+ "@deepseek-ai/dsh-agent": "0.2.1-alpha.2",
34
+ "@deepseek-ai/dsh-llm": "0.2.1-alpha.2",
35
+ "@deepseek-ai/dsh-output-retention": "0.2.1-alpha.2",
36
+ "@deepseek-ai/dsh-system-prompt": "0.2.1-alpha.2",
37
+ "@deepseek-ai/dsh-jobs": "0.2.1-alpha.2",
38
+ "@deepseek-ai/dsh-tools": "0.2.1-alpha.2",
39
+ "@deepseek-ai/cordis": "~4.0.5-alpha.1"
40
40
  },
41
41
  "devDependencies": {
42
- "@deepseek-ai/dsh-agent": "0.2.0-rc.2",
43
- "@deepseek-ai/dsh-llm": "0.2.0-rc.2",
44
- "@deepseek-ai/dsh-output-retention": "0.2.0-rc.2",
45
- "@deepseek-ai/dsh-system-prompt": "0.2.0-rc.2",
46
- "@deepseek-ai/dsh-jobs": "0.2.0-rc.2",
47
- "@deepseek-ai/dsh-jobs-local": "0.2.0-rc.2",
48
- "@deepseek-ai/dsh-tools": "0.2.0-rc.2",
49
- "@deepseek-ai/cordis": "~4.0.4",
50
- "@deepseek-ai/dsh-session": "0.2.0-rc.2"
42
+ "@deepseek-ai/dsh-agent": "0.2.1-alpha.2",
43
+ "@deepseek-ai/dsh-llm": "0.2.1-alpha.2",
44
+ "@deepseek-ai/dsh-output-retention": "0.2.1-alpha.2",
45
+ "@deepseek-ai/dsh-session": "0.2.1-alpha.2",
46
+ "@deepseek-ai/dsh-system-prompt": "0.2.1-alpha.2",
47
+ "@deepseek-ai/dsh-jobs": "0.2.1-alpha.2",
48
+ "@deepseek-ai/dsh-jobs-local": "0.2.1-alpha.2",
49
+ "@deepseek-ai/dsh-tools": "0.2.1-alpha.2",
50
+ "@deepseek-ai/cordis": "~4.0.5-alpha.1"
51
51
  }
52
52
  }