dsh-instruction-memory 1.4.3 → 1.4.4

package/CHANGELOG.md

@@ -7,6 +7,29 @@
 > 1.0.13 起由 CI 经 OIDC Trusted Publishing 发布（首个带 provenance 的版本）。
 > 这些历史 tag **不应回填**——npm 上的版本号已被占用。
 
+## [1.4.4] — 2026-10-29
+
+最新版审计（桌面端 0.2.1-rc.3、网页端同一宿主，并对照 npm `next` 上的 0.2.1-rc.4）发现的缺陷修复。
+
+### 修复
+
+- **注入字数上限真的会越界**：形象区块与条目区块各自预留"另有 N …"尾注空间，但都按 `footerFor(omitted + 1)` 预留、按 `footerFor(omitted)` 渲染——被省略的数量跨过一位数时就少留字符。实测 1.4.3：12 个形象 × 292 字符、上限 800，渲染出 **801** 字符。现在两侧都按"最坏情况（全部省略）"预留，形象区块还会先让出条目尾注所需的字符。
+- **条目被形象挤空时尾注消失**：形象占满预算后条目区块文本为空，于是"另有 N 条指令未包含"永远不会出现，模型在毫无提示的情况下丢掉用户指令。现在会显式追加该尾注。
+- **`injection.available` 恒为 `true`**：现在反映提示词区块是否真的注册成功，失败（`sectionError`）时为 `false`，与 `injection.error` 一致。
+- **快照泄露绝对路径**：`storage.backupPath` / `storage.historyDir` / `storage.schemaFile` 之前直接给绝对路径，现在与 `storage.path` 一样经 `displayPath()` 把家目录折叠成 `~`（真实路径只用于读写，不对外暴露账号名）。
+- **`install.mjs` 不在 npm 包里**：`files` 白名单缺它，而 README 让用户跑 `node install.mjs`。已加入。
+
+### 兼容区间
+
+- 尾部 `|| >=0.2.0-0` **没有上界**：`0.3.0`、`1.0.0`、`9.9.9` 都被判兼容。现收窄为 `>=0.2.0-0 <0.4.0-0`。
+- 新增 `>=0.2.2-alpha.0 <0.3.0-0`：semver 只在同一 tuple 上匹配预发布号，`0.2.0` 那段够不到 `0.2.2-alpha.N`（npm `alpha` 标签当前即 `0.2.2-alpha.5`）。该线**只做过契约比对，尚未实机启动**。
+- 三处声明（`peerDependencies` / `dsh.engines.dsh` / `dsh.compatibility.dsh`）仍由 `host-range-test.mjs` 生成并校验一致。
+
+### 说明（未改动，但需要知道）
+
+- 设置页依赖宿主的 `slots` 服务；`@deepseek-ai/cordis` 没有"可选注入"，只能声明硬依赖。宿主不提供该服务时插件不装载设置页，只打印一行说明——平台要求，已写入 README。
+- 插件 HTTP 路由在宿主网页端**没有鉴权**（README 早已写明）。桌面端同端口下 `/` 返回 401 而插件路由 200，这一层插件自己修不了，只能靠宿主或反向代理。
+
 ## [1.4.3] — 2026-10-27
 
 技术方案评审团（3 名专家独立评审 + 逐条复现）列出的缺陷**全部修复**，并补上对应的回归断言。
@@ -63,10 +86,14 @@
 
 ### 测试
 
-- 新增 12 项 `install.mjs` 断言（真实子进程跑安装/卸载/幂等/拒绝半卸载）。
-- 新增 4 项跨进程与备份保护断言（真实双 handler 实例 + 三种不可用主文件）。
-- 新增 4 项静音断言与 2 项用量条断言；`npm test` 全套通过（`lint` 在本机沙箱内因禁止管道子进程
-  而误报，改用逐文件 `node --check` 等价校验）。
+- `install.mjs` 补断言：真实子进程跑安装 / 卸载 / 幂等 / **拒绝半卸载**（链接是真实目录时不得
+  改 `package.json`）。
+- 跨进程与备份保护补断言：真实两个 handler 实例模拟"另一个进程刚保存"，以及三种不可用主文件
+  （缺失 / 空 / 非空但不可解析）下 `.bak` 的处置。
+- 请求门禁（端口 / `same-site` / 尾点 / 重复 `Host` / MIME 精确匹配）、静音解析、用量条与预算
+  上限均补断言；预算不变量另用 3000 组随机存储形状做模糊验证（0 违例）。
+- `npm test` 全套通过：**928 项断言，0 失败**。`lint.mjs` 增加管道子进程不可用时的
+  `stdio: inherit` 回退，使语法门禁在受限沙箱内也能给出真实结论（此前会被误报为全部解析失败）。
 
 ## [1.4.2] — 2026-10-24
 

package/README.md

@@ -215,6 +215,11 @@ DSH 就会得到第二份空记忆，看起来像"记忆消失"。相对的 `$DS
 > "没活干还在动"的副作用。现在文件由**第一个真正需要它的动作**创建：一次保存、一次导入，
 > 或设置页读取 `state`（面板打开时就会读）。
 
+> **快照里的路径是折叠过的**（1.4.4 起）：`storage.path` / `backupPath` / `historyDir` / `schemaFile` 都把家目录折成 `~`，只用于显示；读写、备份、监听仍用绝对路径。
+> `injection.available` 也不再恒为 `true`——提示词区块注册失败时它是 `false`。
+> 设置页依赖宿主的 `slots` 服务：`@deepseek-ai/cordis` 没有"可选注入"，所以这是硬依赖，
+> 宿主不提供时插件不装载设置页（只打印一行说明）。
+
 在这之前：`storage.path` 仍会显示路径，但 `storage.onDisk` 为 `false`，设置页显示
 「尚未写入磁盘」（该文案本就存在），`state.injection.registered === false`，`pulls === 0`。
 挂载日志相应为 `from=first run (no store on disk yet) onDisk=no`。
@@ -593,7 +598,7 @@ DNS 重绑定恰好推翻了它**：`evil.com` 解析到 `127.0.0.1` 之后，
 同一串范围（三处逐字节一致，由测试锁定）：
 
 ```
->=0.1.3-alpha.2 <0.1.4 || >=0.1.4-0 <0.1.5-0 || >=0.1.5-alpha.1 <0.1.6-0 || >=0.1.6-alpha.0 <0.1.7-0 || >=0.1.7-alpha.0 <0.2.0-0 || >=0.2.1-alpha.0 <0.3.0-0 || >=0.2.0-0
+>=0.1.3-alpha.2 <0.1.4 || >=0.1.4-0 <0.1.5-0 || >=0.1.5-alpha.1 <0.1.6-0 || >=0.1.6-alpha.0 <0.1.7-0 || >=0.1.7-alpha.0 <0.2.0-0 || >=0.2.1-alpha.0 <0.3.0-0 || >=0.2.2-alpha.0 <0.3.0-0 || >=0.2.0-0 <0.4.0-0
 ```
 
 **验证范围与证据等级**——三者不可混为一谈，下面每一行都标了它到底证明了什么：

package/install.mjs

@@ -0,0 +1,186 @@
+/**
+ * Install / uninstall dsh-instruction-memory into the web profile.
+ *
+ *   node install.mjs           # install
+ *   node install.mjs --remove  # roll back completely
+ *
+ * Three idempotent steps:
+ *   1. make the package resolvable from the profile's node_modules (junction)
+ *   2. register it in `dsh.profile.bundles`, so the boot composes its
+ *      cordis.patch.yml host row
+ *   3. declare it in the profile's `dependencies` as `link:<this checkout>`.
+ *      A junction plus a bundle entry is enough for the HOST to load the
+ *      plugin, but NOT enough to be seen by the market: dshmarket's installed
+ *      list is built from the profile's `dependencies` only
+ *      (`readInstalled` in dshmarket/src/profile.ts), so a plugin installed
+ *      by steps 1-2 alone runs while showing up nowhere under 「已安装」.
+ *
+ * The profile package.json is backed up before the first modification.
+ */
+import { existsSync, readFileSync, writeFileSync, symlinkSync, lstatSync, unlinkSync, copyFileSync } from 'node:fs'
+import { homedir } from 'node:os'
+import { dirname, join, resolve } from 'node:path'
+import { fileURLToPath } from 'node:url'
+
+// Profile location follows the same precedence as @deepseek-ai/dsh-home-paths
+// (and this plugin's own store resolution): explicit $DSH_HOME, else ~/.dsh.
+// A relative override is resolved ONCE, for the same reason the plugin does it:
+// every path this script prints and writes must be absolute.
+const DSH_HOME = typeof process.env.DSH_HOME === 'string' && process.env.DSH_HOME.trim() !== ''
+  ? resolve(process.env.DSH_HOME.trim())
+  : join(homedir(), '.dsh')
+const PROF = join(DSH_HOME, 'profiles', 'web')
+// This script lives in the package root, so the source is wherever it runs from.
+const SRC = dirname(fileURLToPath(import.meta.url))
+const NAME = 'dsh-instruction-memory'
+
+const remove = process.argv.includes('--remove')
+const link = join(PROF, 'node_modules', NAME)
+const pkgPath = join(PROF, 'package.json')
+const backupPath = pkgPath + '.dsh-instruction-memory.bak'
+
+function readPkg() {
+  return JSON.parse(readFileSync(pkgPath, 'utf8'))
+}
+
+function writePkg(pkg) {
+  writeFileSync(pkgPath, JSON.stringify(pkg, null, 2) + '\n', 'utf8')
+}
+
+function bundlesOf(pkg) {
+  pkg.dsh = pkg.dsh || {}
+  pkg.dsh.profile = pkg.dsh.profile || {}
+  pkg.dsh.profile.bundles = pkg.dsh.profile.bundles || []
+  return pkg.dsh.profile.bundles
+}
+
+if (remove) {
+  let touched = false
+  // `link` is normally a junction, and unlinking one removes only the link —
+  // the real package stays where it is. It can also be a REAL directory (pnpm
+  // materialises `link:` dependencies into node_modules as a copy), and there
+  // the old `rmSync(link, {recursive: true})` fallback deleted the installed
+  // copy itself: an uninstall that silently destroys the thing it was told to
+  // detach. Refuse that case and say what to do instead.
+  let linkKind = null
+  try {
+    linkKind = lstatSync(link).isSymbolicLink() ? 'link' : 'directory'
+  } catch {
+    linkKind = null
+  }
+  if (linkKind === 'link') {
+    // A junction can still refuse to go away (EBUSY/EPERM while DSH holds it
+    // open). The old call let that throw as an unhandled rejection, which read
+    // as a crash rather than "nothing was removed".
+    try {
+      unlinkSync(link)
+      console.log('removed junction: ' + link)
+      touched = true
+    } catch (err) {
+      console.error('could not remove ' + link + ': ' + (err && err.code ? err.code : String(err)))
+      console.error('  close DSH (or any process using the plugin) and run this again.')
+      process.exitCode = 1
+    }
+  } else if (linkKind === 'directory') {
+    console.error('refusing to delete ' + link)
+    console.error('  it is a real directory (a pnpm-materialised copy), not a junction;')
+    console.error('  recursive deletion would remove the installed plugin itself.')
+    console.error('  delete it yourself once you have confirmed that is what you want.')
+    // Stop HERE: continuing would strip the dependency and the bundle entry
+    // while the plugin is still on disk, leaving a profile that reports the
+    // plugin as absent and an install that cannot find it either.
+    console.log('\nNOT UNINSTALLED — see the refusal above.')
+    process.exit(1)
+  }
+  if (process.exitCode) {
+    // The junction could not be removed; do not report the plugin as detached.
+    console.log('\nNOT UNINSTALLED — see the refusal above.')
+    process.exit(process.exitCode)
+  }
+  const pkg = readPkg()
+  let changed = false
+  if (pkg.dependencies !== undefined && Object.hasOwn(pkg.dependencies, NAME)) {
+    delete pkg.dependencies[NAME]
+    changed = true
+    console.log('removed from dependencies')
+  }
+  const bundles = pkg.dsh?.profile?.bundles
+  const index = Array.isArray(bundles) ? bundles.indexOf(NAME) : -1
+  if (index >= 0) {
+    bundles.splice(index, 1)
+    changed = true
+    console.log('removed from dsh.profile.bundles')
+  }
+  if (changed) {
+    writePkg(pkg)
+    touched = true
+  }
+  if (existsSync(backupPath)) console.log('backup kept at: ' + backupPath)
+  if (process.exitCode) {
+    console.log('\nNOT UNINSTALLED — see the refusal above.')
+  } else {
+    console.log(touched ? '\nUNINSTALLED — restart DSH to unload the plugin.' : '\nnothing to remove')
+  }
+  // Honour the failure flag the refused-deletion branch may have set: a bare
+  // process.exit(0) would report success for an uninstall that did nothing.
+  process.exit(process.exitCode ?? 0)
+}
+
+// ---- install ----
+if (!existsSync(SRC)) {
+  console.error('source package not found: ' + SRC)
+  process.exit(1)
+}
+
+if (!existsSync(join(PROF, 'package.json'))) {
+  console.error('web profile not found at ' + PROF + '（DSH 尚未初始化该 profile？）')
+  process.exit(1)
+}
+
+if (existsSync(link)) {
+  console.log('junction already present: ' + link)
+} else {
+  symlinkSync(SRC, link, 'junction')
+  console.log('junction created: ' + link)
+}
+
+// Roll the previous backup forward instead of keeping the first one forever:
+// a profile package.json broken by a later run is exactly what the user needs
+// the backup for, and a backup frozen at the first install cannot restore it.
+const lastBackupPath = backupPath + '.last'
+if (existsSync(backupPath)) {
+  copyFileSync(backupPath, lastBackupPath)
+  console.log('rotated previous backup -> ' + lastBackupPath)
+}
+copyFileSync(pkgPath, backupPath)
+console.log('backed up profile package.json -> ' + backupPath)
+
+const pkg = readPkg()
+let changed = false
+
+// Step 3: a link: dependency, so the market lists it under 「已安装」.
+// package.json only — the target is the junction from step 1, so no
+// reinstall of the package itself is needed.
+const spec = 'link:' + SRC.replaceAll('\\', '/')
+pkg.dependencies = pkg.dependencies || {}
+if (pkg.dependencies[NAME] === spec) {
+  console.log('already a profile dependency: ' + spec)
+} else {
+  pkg.dependencies[NAME] = spec
+  changed = true
+  console.log('declared as a profile dependency: ' + spec)
+}
+
+const bundles = bundlesOf(pkg)
+if (bundles.includes(NAME)) {
+  console.log('already in dsh.profile.bundles')
+} else {
+  bundles.push(NAME)
+  changed = true
+  console.log('added to dsh.profile.bundles (position ' + bundles.length + ')')
+}
+
+if (changed) writePkg(pkg)
+
+console.log('\nINSTALLED. Restart DSH to mount the plugin.')
+console.log('Roll back with:  node install.mjs --remove')