dsh-client-auto-continue 0.6.2 → 0.6.3

package/README.md

@@ -75,6 +75,8 @@ All knobs live in the plugin's settings card — see [Configuration](#configurat
 
 DSH plugins install into a **profile** (`dsh web` → `web` profile). Install, restart `dsh web`, done.
 
+> **Requires DSH ≥ 0.1.0-rc.7** — newer versions register the settings card through the keyed `settings.plugin.item` slot; on rc.6 and earlier the plugin fails to load (`list slot ... requires options.id`). Upgrade dsh first.
+
 ### From npm (recommended)
 
 Published as [`dsh-client-auto-continue`](https://www.npmjs.com/package/dsh-client-auto-continue):
@@ -125,27 +127,7 @@ dsh web
 
 > Switching from a manual install to `dsh plugin add`? Remove the manual `insert` entry first — the bundle patch registers the row and a duplicate would conflict.
 
-> **Note (DSH ≥ 0.1.0-rc.7):** upstream made settings exposure **registry-driven**
-> — every namespace a plugin registers is served to the web settings surface,
-> so the settings card just works, no vendor patch needed. Only DSH 0.1.0-rc.6
-> and earlier gate exposure behind a hardcoded allowlist in
-> `@deepseek-ai/dsh-host-apiproxy`; on those versions, run the idempotent
-> vendor patch once (and re-run after reinstalling dsh):
->
-> ```sh
-> npx --yes --package dsh-client-auto-continue patch-expose
-> dsh web
-> ```
->
-> The patch script ships inside the npm package as a `bin` (works from any
-> directory in a fresh environment — no repo clone, no profile-path guessing)
-> and covers every reachable dsh installation: the profile-linked copy, a
-> global `npm i -g @deepseek-ai/dsh` install, and the invoking directory's
-> own. If you installed from this repository instead, the same script is
-> `node scripts/patch-expose.mjs` at the repo root. The auto-continue engine
-> itself works without this patch — it only gates the GUI settings section;
-> on rc.6 and earlier, configure everything directly in `~/.dsh/settings.yaml`
-> (see [Configuration](#configuration)).
+> **Settings exposure:** since DSH 0.1.0-rc.7 the web settings surface is **registry-driven** — every namespace a plugin registers is served, so the settings card works out of the box, no vendor patch needed (the plugin requires rc.7+, see Quick Start).
 
 ### Verify & uninstall
 

package/README.zh.md

@@ -75,6 +75,8 @@
 
 DSH 插件安装进 **profile**(`dsh web` 对应 `web` profile)。安装后重启 `dsh web` 即可。
 
+> **要求 DSH ≥ 0.1.0-rc.7** — 新版本通过 keyed 的 `settings.plugin.item` 槽位注册设置卡片; 在 rc.6 及更早版本上插件会加载失败(`list slot ... requires options.id`), 请先升级 dsh。
+
 ### 从 npm 安装(推荐)
 
 已发布为 [`dsh-client-auto-continue`](https://www.npmjs.com/package/dsh-client-auto-continue):
@@ -125,22 +127,7 @@ dsh web
 
 > 从手动安装切换到 `dsh plugin add` 时, 请先删掉手动加的 `insert` 条目——包自带的 bundle patch 会注册插件行, 重复注册会冲突。
 
-> **说明(DSH ≥ 0.1.0-rc.7):** 上游已把设置暴露改成**注册表驱动**——插件注册的
-> 任何命名空间都会直接出现在 webui 设置区, 设置卡片开箱即用, 无需任何供应商补丁。
-> 仅 DSH 0.1.0-rc.6 及更早版本仍在 `@deepseek-ai/dsh-host-apiproxy` 里用硬编码白名单
-> 门禁暴露; 这些版本需要执行一次幂等的供应商补丁(重新安装 dsh 后重跑):
->
-> ```sh
-> npx --yes --package dsh-client-auto-continue patch-expose
-> dsh web
-> ```
->
-> 补丁脚本随 npm 包以 `bin` 形式发布(全新环境下任意目录都能直接执行, 无需克隆仓库、
-> 无需猜测 profile 路径), 并覆盖所有可达的 dsh 安装: profile 链接副本、全局
-> `npm i -g @deepseek-ai/dsh` 安装、以及当前目录的安装。若是从本仓库安装,
-> 同一脚本在仓库根目录执行 `node scripts/patch-expose.mjs` 即可。自动续跑引擎
-> 本身不依赖这个补丁——它只影响 GUI 设置区是否可见; 在 rc.6 及更早版本上,
-> 可以直接在 `~/.dsh/settings.yaml` 里配置全部参数(见 [配置](#配置))。
+> **设置暴露:** DSH 0.1.0-rc.7 起 webui 设置区是**注册表驱动**的——插件注册的命名空间直接可见, 设置卡片开箱即用, 无需任何供应商补丁(插件要求 rc.7+, 见快速开始)。
 
 ### 验证与卸载
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "dsh-client-auto-continue",
   "description": "DSH Web UI plugin: automatically sends \"继续\" (continue) when a request is interrupted by network errors or other non-human causes",
-  "version": "0.6.2",
+  "version": "0.6.3",
   "type": "module",
   "main": "lib/index.js",
   "types": "lib/types/index.d.ts",
@@ -84,8 +84,5 @@
     "@deepseek-ai/dsh-settings": "^0.1.0-rc.7",
     "@deepseek-ai/schemastery": "^3.18.1",
     "@deepseek-ai/cordis": "^4.0.1"
-  },
-  "bin": {
-    "patch-expose": "./scripts/patch-expose.mjs"
   }
 }

package/scripts/patch-expose.mjs

@@ -1,133 +0,0 @@
-#!/usr/bin/env node
-/**
- * Vendor patch for a known DSH limitation (0.1.0-rc.6 and earlier):
- *
- * The web settings surface only exposes namespaces listed in the hardcoded
- * `WEB_SETTINGS_NAMESPACES` / `PRODUCT_SETTINGS_NAMESPACES` allowlists inside
- * the installed `@deepseek-ai/dsh-host-apiproxy` bundle. Any other registered
- * namespace answers `settings-not-exposed`, so a third-party plugin's settings
- * section renders nothing even though its namespace registered fine (the
- * proxy's own comment calls moving exposure into `settings.register()` "deferred
- * work").
- *
- * Since DSH 0.1.0-rc.7 upstream made exposure REGISTRY-DRIVEN, so this script
- * is a no-op there (it detects the missing function and reports accordingly).
- * On rc.6 and earlier it patches `exposedNamespaces()` to also expose every
- * namespace currently registered with the settings provider. The patch
- * contains NO plugin-specific string, so the settings of ANY plugin that
- * registers a namespace (and mounts its own settings section) appear
- * automatically — this plugin included.
- *
- * It is applied to every reachable dsh installation: the profile-linked copy
- * (pnpm store / npx cache), a global `npm i -g @deepseek-ai/dsh` install under
- * the active Node version, and the invoking directory's own install. Re-run it
- * after any dsh reinstall; it is idempotent and also removes the previous
- * per-plugin allowlist entry (pre-0.4.0 installs).
- *
- * Usage: node scripts/patch-expose.mjs
- */
-import { createRequire } from 'node:module';
-import { readFileSync, writeFileSync, realpathSync } from 'node:fs';
-import { dirname, join } from 'node:path';
-import { homedir } from 'node:os';
-
-/** The registry-driven patch: expose every namespace the provider knows. */
-const GENERIC_ADD = `\t\tconst settings = ctx.get("settings");
-\t\tif (settings !== void 0) for (const descriptor of settings.describe()) exposed.add(String(descriptor.ns));`;
-
-/** Marker proving the generic patch is already applied. */
-const GENERIC_MARKER = 'for (const descriptor of settings.describe()) exposed.add(String(descriptor.ns))';
-
-/** The hardcoded allowlist tail, as shipped (and as the old patch rewrote it). */
-const ARRAY_TAIL_PLAIN = `\t"web-search-deepseek"\n];`;
-const ARRAY_TAIL_OLD_PATCH = `\t"web-search-deepseek",\n\t"auto-continue"\n];`;
-
-/**
- * Collect candidate dsh-host-apiproxy package.json paths: the profile-linked
- * copy, a global install under the active Node version's nvm layout
- * (`<nvm>/<version>/lib/node_modules/@deepseek-ai/dsh`), and the invoking
- * directory's own install. Deduplicated by real path.
- */
-function candidatePackageJsons() {
-  const found = new Set();
-  const add = (pkgJson) => {
-    try {
-      found.add(realpathSync(pkgJson));
-    } catch {
-      /* candidate not present */
-    }
-  };
-  const tryResolve = (requireFn) => {
-    try {
-      add(requireFn.resolve('@deepseek-ai/dsh-host-apiproxy/package.json'));
-    } catch {
-      /* not resolvable from this anchor */
-    }
-  };
-
-  // 1. The copy the profile's node_modules links to.
-  tryResolve(createRequire(join(homedir(), '.dsh', 'profiles', 'web', 'package.json')));
-  // 2. A global install under the active Node version's nvm layout.
-  try {
-    const globalRoot = realpathSync(join(process.execPath, '..', '..', 'lib', 'node_modules'));
-    tryResolve(createRequire(join(globalRoot, '@deepseek-ai', 'dsh', 'package.json')));
-  } catch {
-    /* not an nvm-style global root */
-  }
-  // 3. The invoking directory's own install.
-  tryResolve(createRequire(join(process.cwd(), 'package.json')));
-  return [...found];
-}
-
-const candidates = candidatePackageJsons();
-if (candidates.length === 0) {
-  console.error('[patch-expose] could not resolve any @deepseek-ai/dsh-host-apiproxy installation');
-  process.exit(1);
-}
-
-let changedAny = false;
-for (const packageJson of candidates) {
-  const bundlePath = join(dirname(packageJson), 'lib', 'index.js');
-  let source = readFileSync(bundlePath, 'utf8');
-  let changed = false;
-
-  // 1. Remove the previous per-plugin allowlist entry (pre-0.4.0 installs).
-  if (source.includes(ARRAY_TAIL_OLD_PATCH)) {
-    source = source.replace(ARRAY_TAIL_OLD_PATCH, ARRAY_TAIL_PLAIN);
-    changed = true;
-    console.log(`[patch-expose] removed per-plugin allowlist entry in ${bundlePath}`);
-  }
-
-  // 2. Make exposure registry-driven (idempotent).
-  if (!source.includes(GENERIC_MARKER)) {
-    const fnStart = source.indexOf('\tfunction exposedNamespaces() {');
-    if (fnStart === -1) {
-      // DSH ≥ 0.1.0-rc.7 已把设置暴露改为注册表驱动, 没有这个函数也不需要补丁。
-      console.log(
-        `[patch-expose] ${bundlePath}: DSH ≥ 0.1.0-rc.7 已原生支持 registry-driven 设置暴露, 无需补丁 — skipped.`,
-      );
-      continue;
-    }
-    const fnEnd = source.indexOf('\t}', fnStart);
-    if (fnEnd === -1) {
-      console.error(`[patch-expose] could not locate the end of exposedNamespaces() in ${bundlePath}`);
-      continue;
-    }
-    const body = source.slice(fnStart, fnEnd);
-    if (!body.includes('return exposed;')) {
-      console.error(`[patch-expose] unexpected exposedNamespaces() body in ${bundlePath}`);
-      continue;
-    }
-    const patchedBody = body.replace('\t\treturn exposed;', `${GENERIC_ADD}\n\t\treturn exposed;`);
-    source = source.slice(0, fnStart) + patchedBody + source.slice(fnEnd);
-    changed = true;
-    console.log(`[patch-expose] made exposure registry-driven in ${bundlePath}`);
-  } else {
-    console.log(`[patch-expose] registry-driven exposure already present in ${bundlePath} — skipped.`);
-  }
-
-  if (changed) writeFileSync(bundlePath, source);
-  changedAny = changedAny || changed;
-}
-
-if (changedAny) console.log('[patch-expose] restart `dsh web` for the change to take effect.');