dsh-minimal-ptc 0.5.3 → 0.5.4

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
@@ -4,6 +4,10 @@
4
4
 
5
5
  [历史英文记录](docs/CHANGELOG.en.md)
6
6
 
7
+ ## 0.5.4 (2026-10-05)
8
+
9
+ - 修复新版 DSH 并行启动时,定时服务就绪较晚导致整套极简 PTC 预设“加载失败”的问题。现在等待服务激活,再通过宿主加载官方定时工具;旧版宿主不会导入缺失的模块。
10
+
7
11
  ## 0.5.3 (2026-10-05)
8
12
 
9
13
  - 对齐官方 dsh-v0.2.1-alpha.1 PTC 的定时任务工具与子代理禁止调度规则,保留固定一句提示词、Windows Git Bash 和持久 PowerShell。
@@ -4,6 +4,10 @@
4
4
 
5
5
  These English notes preserve the earlier translations. The main changelog contains the consolidated version history.
6
6
 
7
+ ## 0.5.4 (2026-10-05)
8
+
9
+ - Wait for the Host schedule service before importing its official tools. Fixes a parallel startup race that marked the whole preset as failed; hosts without scheduling never import the unavailable module.
10
+
7
11
  ## 0.5.3 (2026-10-05)
8
12
 
9
13
  - Align with dsh-v0.2.1-alpha.1 PTC scheduling tools and subagent scheduling restrictions while preserving the one-line prompt and Windows shells.
package/docs/USAGE.en.md CHANGED
@@ -6,7 +6,7 @@
6
6
 
7
7
  The primary minimal PTC agent can use official scheduling tools. Spawn/fork subagents follow official restrictions against creating, listing, updating or deleting schedules. Minimal mode still omits runtime context, time prompts and AGENTS instructions.
8
8
 
9
- Scheduling tools activate only when the host provides its `schedule` service. Older hosts skip this module and retain their existing PTC capabilities; do not install duplicate DSH core packages.
9
+ Scheduling tools wait for the host's `schedule` service to activate, avoiding preset failures during parallel startup. Older hosts skip the official scheduling module and retain their existing PTC capabilities; do not install duplicate DSH core packages.
10
10
 
11
11
  ## Install and use
12
12
 
package/docs/USAGE.md CHANGED
@@ -6,7 +6,7 @@
6
6
 
7
7
  极简 PTC 的主代理现在可使用官方定时任务;spawn / fork 子代理保持官方限制,不可创建、列举、更新或删除任务。极简模式仍不注入运行时上下文、时间提示或 AGENTS 指令。
8
8
 
9
- 定时工具只在宿主提供 `schedule` 服务时启用。旧版宿主会跳过这个模块,继续使用原有 PTC 能力;无需另外安装 DSH 核心包。
9
+ 定时工具等待宿主的 `schedule` 服务激活后启用,避免启动顺序导致模式加载失败。旧版宿主会跳过官方定时模块,继续使用原有 PTC 能力;无需另外安装 DSH 核心包。
10
10
 
11
11
  ## 安装和使用
12
12
 
@@ -2,6 +2,14 @@
2
2
 
3
3
  本页整理原 README 的历史验证说明,保留当时的版本、日期与范围。自动测试、启动检查、浏览器操作和真实服务验收分别记录,不能相互替代。更详细的版本验收文件仍保留在仓库中。
4
4
 
5
+ ## 2026-10-05:0.5.4 启动与可见操作
6
+
7
+ - Windows 自动测试:22 通过、1 按环境跳过。覆盖旧宿主不导入定时模块、服务延迟到达及模块失败的回报。
8
+ - 官方 npm Harness `0.2.1-alpha.1` 的实际网页中选择「极简 PTC 模式」,通过 `run_code` 调用 SQL,返回 `preset_ok = 1`,并列出 `schedule_create/list/delete/update` 四个官方工具。
9
+ - 工具调用由验证专用脚本选择,未测试模型自主选择工具。全部操作位于隔离配置和合成项目,不涉及用户数据。
10
+ - 本环境「工作区内修改」遇到 `SetNamedSecurityInfoW failed (Win32 5): grantWrite`;上述执行成功发生在隔离会话的「完全权限」模式,之后已恢复原模式。默认权限下的 Windows 沙箱执行仍记为受阻,不建议以降低日常权限来解决。
11
+ - RC2 的完整插件契约验证通过,保留旧宿主兼容;桌面原生窗口未在本轮重新操作。
12
+
5
13
  ## 2026-10-02:0.5.2 与官方 RC2 源码核对
6
14
 
7
15
  - 官方基线:Harness `0.2.0-rc.2`,提交 `639ed015397290b3745d163aafe02ffee4aa3f84`。
package/lib/index.js CHANGED
@@ -60,7 +60,7 @@ function materialize(logger, modernRuntime) {
60
60
  return
61
61
  }
62
62
 
63
- for (const file of ['agent.cordis.yml', 'preset.yml', 'gitbash-executor.mjs']) {
63
+ for (const file of ['agent.cordis.yml', 'preset.yml', 'gitbash-executor.mjs', 'schedule-tools.mjs']) {
64
64
  let content = readFileSync(join(presetSourceDir, file), 'utf8')
65
65
  if (modernRuntime && file === 'agent.cordis.yml') {
66
66
  content = content.replaceAll('workflow-worker-thread', 'workflow-ptc')
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "dsh-minimal-ptc",
3
- "version": "0.5.3",
3
+ "version": "0.5.4",
4
4
  "description": "把官方极简提示词与 PTC 编排组合起来,提供完整插件工具和 Windows 终端适配。",
5
5
  "type": "module",
6
6
  "main": "lib/index.js",
@@ -10,7 +10,8 @@
10
10
  },
11
11
  "./cordis.patch.yml": "./cordis.patch.yml",
12
12
  "./package.json": "./package.json",
13
- "./gitbash-executor": "./presets/ptc-minimal/gitbash-executor.mjs"
13
+ "./gitbash-executor": "./presets/ptc-minimal/gitbash-executor.mjs",
14
+ "./schedule-tools": "./presets/ptc-minimal/schedule-tools.mjs"
14
15
  },
15
16
  "files": [
16
17
  "lib",
@@ -120,8 +120,7 @@
120
120
  name: '@deepseek-ai/dsh-tool-jobs'
121
121
 
122
122
  - id: tool-schedule
123
- name: '@deepseek-ai/dsh-tool-schedule'
124
- disabled: !!js "!ctx.get('schedule')"
123
+ name: ./schedule-tools.mjs
125
124
 
126
125
  # ── skills ──────────────────────────────────────────────────────────────────
127
126
 
@@ -0,0 +1,12 @@
1
+ // Optional Host capability: wait for the service instead of evaluating its
2
+ // current readiness in a Loader `disabled` expression. The official module
3
+ // is resolved by the Host so this preset never bundles a second core copy.
4
+ export const name = 'ptc-minimal-schedule-tools'
5
+ export const inject = ['tools']
6
+
7
+ export function apply(ctx) {
8
+ ctx.inject(['schedule'], async (scheduleCtx) => {
9
+ const exports = await scheduleCtx.loader.import('@deepseek-ai/dsh-tool-schedule')
10
+ scheduleCtx.plugin(scheduleCtx.loader.unwrapExports(exports))
11
+ })
12
+ }
@@ -130,10 +130,9 @@
130
130
  name: '@deepseek-ai/dsh-tool-jobs'
131
131
 
132
132
  - id: tool-schedule
133
- name: '@deepseek-ai/dsh-tool-schedule'
134
- # Older hosts have no schedule service or module. Disabled rows
135
- # are never imported; enable only when the host supplies it.
136
- disabled: !!js "!ctx.get('schedule')"
133
+ # Wait for service activation; do not freeze an early readiness
134
+ # check into a disabled row while the Host is still booting.
135
+ name: dsh-minimal-ptc/schedule-tools
137
136
 
138
137
  # ── skills ──────────────────────────────────────────────────────────────────
139
138