@yanglaofish/dsh-proxy-pro 1.0.4 → 1.0.5

package/docs/LESSONS.md

@@ -723,4 +723,31 @@ forced-proxy = 新建 ProxyAgent，全部由 `und.fetch` 发起。
 行动；`proxy_test` 工具输出同步中文（模型照读）。教训：给用户看的文案别用英文"图省事"，
 判定结论必须能直接用。
 
-**测试**：断言随中文文案同步翻新（/混用/、/超时/、/上游|超时/、/ECONNREFUSED/）。
+**测试**：断言随中文文案同步翻新（/混用/、/超时/、/上游|超时/、/ECONNREFUSED/）。
+
+---
+
+## 26. 不 import 会被移除的库导出：settings 走服务（2026-09-18）
+
+**症状**：升级 test profile 后，dsh CLI 启动时整棵树崩溃：
+`SyntaxError: The requested module '@deepseek-ai/dsh-settings' does not provide an export named 'installSettingsSection'`，
+插件行加载失败 → 整个启动终止。
+
+**根因**：dsh-settings 同时存在两个版本——桌面版（resources/app/node_modules）**保留**了
+`installSettingsSection`/`settingsNamespace` 兼容导出；全局 dsh CLI（AppData/Roaming/npm 的
+`@deepseek-ai/dsh` 自带依赖树）是**新版，已移除这两个导出**。插件在模块顶层
+`import { installSettingsSection } from '@deepseek-ai/dsh-settings'` → ESM 求值阶段就抛
+SyntaxError，不是运行期错误——profile 插件树加载失败，启动直接终止。
+
+**改法**（1.0.5）：彻底不 import dsh-settings 的任何导出，配置注册改走 **settings 服务**：
+```js
+const scope = ctx.settings.register(PROXY_NS, Config, { base: config })
+source = () => scope.get()                 // update() 重算 registration.resolved，get() 始终新鲜
+scope.watch(() => { void requestSync().catch(() => {}) })
+```
+`register`/`watch`/`update`/`replace` 在两端（旧桌面版 SettingsProvider 与新 CLI 版）都存在；
+命名空间直接写字面量 `'proxy'`（旧 `settingsNamespace()` 也只是 parse + 校验）。
+
+**教训**：① ESM 顶层 import 命中断言是**加载期**错误——一次错误的 import 能杀死整个进程，所以
+对外部包的导出要查运行环境的实际版本，而不是凭记忆；② 能从服务拿到的（settings 是 inject 服务）
+就不要 import 包；③ 「桌面版」与「全局 CLI 版」是两套依赖树，一个功能必须两端都能加载。

package/docs/SPEC.md

@@ -105,7 +105,7 @@ profile 内安装（pnpm nodeLinker: hoisted；本地=file: 软链，发布=regi
 
 ```
 [浏览器 client.js]                    [host index.js (NodeService 链)]
-  │  inject settings.section            │  installSettingsSection(proxy NS)
+  │  inject settings.section            │  ctx.settings.register('proxy') + watch
   │  inject header.utilities            │  sync(): resolve → applyEffective(env+dispatcher)
   │  fetch /dsh-proxy-pro/api/*  ◄──────┤          → installProxyFromEnvironment(policy)
   │                                     │              ↓ 让 web_fetch 的 proxyRouteFor 判 PROXIED
@@ -140,7 +140,9 @@ function apply(ctx, config) { … }   // 导出 { Config, apply, inject, name }
 - **没有 savedEnv / EnvHttpProxyAgent / 手写 dispatcher**：传输完全委托
   `installProxyFromEnvironment`（env + 全局 dispatcher + 模块级策略一体，
   LESSONS §12.4：单一通道，杜绝 undici 错版）。
-- `installSettingsSection(ctx, PROXY_NS, Config, config, { setSource, onChange })`，
+- `ctx.settings.register(PROXY_NS, Config, { base: config })` 拿 owner scope，
+  `source = () => scope.get()`，`scope.watch(onChange)` —— 新版 dsh-settings 已移除
+  `installSettingsSection` 导出（LESSONS §26），必须走 settings 服务；
   onChange → `requestSync()`（合并去重，`syncing` 单飞）。
 - teardown（`ctx.effect`）：清 pollTimer → `await httpProxyPolicy?.()`（卸载=恢复
   env/dispatcher/策略）。

package/lib/index.js

@@ -26,7 +26,6 @@
  */
 import z from '@deepseek-ai/schemastery'
 import { defineTool } from '@deepseek-ai/dsh-tools'
-import { installSettingsSection, settingsNamespace } from '@deepseek-ai/dsh-settings'
 import { installProxyFromEnvironment, proxyRouteFor } from '@deepseek-ai/dsh-http-proxy'
 import { execFile } from 'node:child_process'
 import { promisify } from 'node:util'
@@ -56,8 +55,11 @@ const name = 'dsh-proxy-pro'
 /** Services this plugin must resolve before it applies. */
 const inject = ['tools', 'systemPrompt', 'settings']
 
-/** Settings namespace owning the proxy configuration (shared with stock tooling). */
-const PROXY_NS = settingsNamespace('proxy')
+/** Settings namespace owning the proxy configuration (shared with stock
+ *  tooling). Plain literal: the legacy settingsNamespace() helper was removed
+ *  from newer dsh-settings, and 'proxy' is already a valid lowercase-hyphenated
+ *  namespace identifier. */
+const PROXY_NS = 'proxy'
 
 /** Ordered placement of the proxy status section in the system prompt. */
 const SECTION_ORDER = 55
@@ -442,16 +444,22 @@ function apply(ctx, config) {
   }
 
   // Configuration source: the `proxy` settings namespace layered over the
-  // composition entry; every committed change re-syncs live.
-  installSettingsSection(ctx, PROXY_NS, Config, config, {
-    setSource: (current) => {
-      source = current
+  // composition entry; every committed change re-syncs live. Registration goes
+  // through the settings SERVICE — newer dsh-settings removed the
+  // `installSettingsSection` export entirely, so importing it throws a
+  // SyntaxError at boot and kills the whole profile (LESSONS §26).
+  // register() + scope.get()/watch() exist on every version we target, and
+  // update() recomputes registration.resolved, so scope.get() stays fresh.
+  const settingsService = ctx.get('settings')
+  if (settingsService !== undefined && typeof settingsService.register === 'function') {
+    const proxyScope = settingsService.register(PROXY_NS, Config, { base: config })
+    source = () => proxyScope.get()
+    proxyScope.watch(() => {
       void requestSync().catch(() => {})
-    },
-    onChange: () => {
-      void requestSync().catch(() => {})
-    },
-  })
+    })
+  }
+  // Without a settings service in this composition, `source` keeps the
+  // composition default (initialized above) and the plugin still runs, read-only.
 
   // ---------- Agent tools ----------
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yanglaofish/dsh-proxy-pro",
-  "version": "1.0.4",
+  "version": "1.0.5",
   "description": "DSH proxy manager: route model requests, web fetches and spawned tools through the Windows system proxy or a custom address; per-URL route diagnosis, one-click toggle from the conversation header, a dedicated Settings page, and keepalive-aware 407 hints.",
   "type": "module",
   "main": "./lib/index.js",