dsh-plugin 1.6.10 → 1.6.12

package/src/client/locales.ts

@@ -308,6 +308,10 @@ export const zh = {
   errorTitleUninstall: '卸载失败',
   // 更新失败（通知中心区分安装/更新）：更新目标覆盖重装失败，与首次安装失败不同语义
   errorTitleUpdate: '更新失败',
+  // 动作词：失败提示与上报正文统一取词，不写死「安装」
+  actionInstall: '安装',
+  actionUpdate: '更新',
+  actionUninstall: '卸载',
   errorPlugin: '插件',
   errorClose: '知道了',
   errorCopy: '复制错误信息',
@@ -319,12 +323,14 @@ export const zh = {
   failHubIssueHint: '此失败已被判定为环境或插件中心自身问题（非插件作者问题），带着错误日志到插件中心仓库一键提交 Issue',
   failHubIssueBig: '反馈给插件中心排查',
   // 未知失败兜底：不归到插件作者，引导到插件中心仓库排查
-  failUnclassifiedHint: '安装失败，原因未能自动识别。这通常不是插件自身的问题（可能与本机环境或插件中心有关），请将错误信息反馈给插件中心，由维护者排查。',
+  failUnclassifiedHint: '{action}失败，原因未能自动识别。这通常不是插件自身的问题（可能与本机环境或插件中心有关），请将错误信息反馈给插件中心，由维护者排查。',
   // 插件中心自身状态类消息（插件未安装 / 不在此处卸载 / 已在队列中）：已安装列表与实读快照不同步，非插件问题，不引导提 Issue
-  failHubStateHint: '插件列表状态已过期或与本地不一致：该插件可能已经装过了（无需重复安装，要升级请点「更新」），也可能已不在已安装列表中，或已在队列中。这不是插件本身的问题 —— 请刷新页面后重试。',
-  // 安装命令超时被强杀：可能其实已装成功（安装器超时后会先核对已安装列表），给可行动提示，不引导提 Issue
-  failTimeoutHint: '安装耗时超过本地上限、已被中断 —— 但很可能其实已经装上了（安装器在超时后会先核对本地已安装列表）。请刷新页面确认该插件是否已装上；若确实没装上，可在终端手动执行一次安装命令查看完整输出。这不是插件本身的问题。',
-  failProfileLockHint: 'DSH 在写入插件清单时等不到文件锁、超时中止 —— 通常是同时有另一个 DSH 进程或安装任务在写同一个 profile（也可能是上一次的进程没退干净留下的锁）。请先关掉其他 dsh 窗口或正在跑的命令，再重试一次；若反复出现，重启一次 DSH。这不是插件本身的问题，也不需要重复安装。',
+  failHubStateHint: '插件列表状态已过期或与本地不一致：这次{action}的目标可能已经在列表里了（要升级请点「更新」），也可能已经不在已安装列表中，或已在队列中。这不是插件本身的问题 —— 请刷新页面后重试。',
+  // 超时被强杀，可能其实已生效：给提示，不引导提 Issue。措辞动作中性（卸载场景说「已经装上了」不通）
+  failTimeoutHint: '本次操作耗时超过本地上限、已被中断 —— 但很可能其实已经生效了（安装器在超时后会先核对本地已安装列表）。请刷新页面确认当前状态；若确实没生效，可在终端手动执行一次对应命令查看完整输出。这不是插件本身的问题。',
+  failProfileLockHint: 'DSH 在写入插件清单时等不到文件锁、超时中止 —— 通常是同时有另一个 DSH 进程或安装任务在写同一个 profile（也可能是上一次的进程没退干净留下的锁）。请先关掉其他 dsh 窗口或正在跑的命令，再重试一次；若反复出现，重启一次 DSH。这不是插件本身的问题，也不需要重复{action}。',
+  // 宿主自身入口起不来：环境问题，给提示、不引导提 Issue
+  failHostCliSpawnHint: 'DSH 没能启动自身来完成这次操作（系统报「找不到可执行文件」）：通常是因为 DSH 的安装目录被移动或正在更新，或该 profile 目录还不存在。请重启一次 DSH 后重试；若反复出现，重新安装 DSH。这不是插件本身的问题，换别的插件也一样。',
   // prepare 构建脚本实际执行失败（git 分发缺子模块/构建产物）：插件打包分发问题，应提 Issue
   failPrepareHint: '该插件安装时的构建脚本执行失败（git 分发常缺失子模块或构建产物），属插件打包分发问题。请向作者仓库提交 Issue 反馈。',
   // 「插件打包问题」分支的次要入口：该判据由插件中心自己的预检/装后校验产出（不是 pnpm 原文），
@@ -334,12 +340,12 @@ export const zh = {
   // 安装前预检 / 装后校验拦截（[packaging]）：git 分发缺插件需要的文件（入口 / 补丁 mount 的入口 / bundle 补丁）= 插件未适配官方默认安装方式
   failPackagingHint: '该插件不支持官方默认安装方式：其 git 分发缺少它需要的文件（`main` / `exports` 声明的入口、补丁按本包名 mount 的入口，或 `dsh.bundle.patch` 声明的补丁），说明作者未适配官方安装流程。请到作者仓库提交 Issue 反馈，请其提交构建产物、改用预构建 release `.tgz` 直链（`releases/download/<tag>/<asset>.tgz`），或发布完整的 npm 版。',
   // 原生依赖构建脚本被 pnpm 默认拦截（如 node-pty 的 ERR_PNPM_IGNORED_BUILDS）：不单独算插件问题，引导到插件中心仓库排查
-  failIgnoredBuild: '该插件（或其依赖）需要在安装时执行构建脚本，被 pnpm 的安全白名单（allowBuilds）默认拦截，安装因此失败（如原生模块 node-pty，或 git 安装时插件自己的 prepare 脚本）。安装器已自动放行该 key 并重试过一次；仍失败通常说明构建本身没通过。可先在终端手动执行一次安装命令查看完整构建错误；若确属插件的构建/分发问题，建议作者预置构建产物、发布 npm 包或预构建 .tgz。需要协助排查时也可反馈给插件中心。',
+  failIgnoredBuild: '该插件（或其依赖）需要在安装时执行构建脚本，被 pnpm 的安全白名单（allowBuilds）默认拦截，本次操作因此失败（如原生模块 node-pty，或 git 安装时插件自己的 prepare 脚本）。安装器已自动放行该 key 并重试过一次；仍失败通常说明构建本身没通过。可先在终端手动执行一次安装命令查看完整构建错误；若确属插件的构建/分发问题，建议作者预置构建产物、发布 npm 包或预构建 .tgz。需要协助排查时也可反馈给插件中心。',
   // npm arborist 内部崩溃（edgesOut）＋ 本机 npm 版本过低：npm 自身已知缺陷，不是插件问题，升级 npm 即可
   failNpmTooLow: '怀疑本机 npm 版本过低：npm 解析插件依赖时内部崩溃（这是 npm 自身的已知缺陷，不是插件问题）。请升级 npm 后重试：npm install -g npm@latest',
   failNpmTooLowV: '本机 npm 版本过低（当前 v{v}）：npm 解析插件依赖时内部崩溃（这是 npm 自身的已知缺陷，不是插件问题）。请升级 npm 后重试：npm install -g npm@latest',
   // 安装前连通性预检 / 安装日志里的连接失败（[network] / git fetch 超时 / DNS / TLS）：本机网络或代理问题，不是插件问题，不引导提 Issue
-  failNetworkHint: '安装前检测到网络不通：无法连接到安装源（可能是断网、DNS 解析失败、被防火墙拦截，或代理配置有问题）。这不是插件本身的问题 —— 请检查网络连接，或到「设置」里确认 HTTP 代理配置，再到「系统诊断」运行一次连通性检测，然后重试。',
+  failNetworkHint: '{action}前检测到网络不通：无法连接到安装源（可能是断网、DNS 解析失败、被防火墙拦截，或代理配置有问题）。这不是插件本身的问题 —— 请检查网络连接，或到「设置」里确认 HTTP 代理配置，再到「系统诊断」运行一次连通性检测，然后重试。',
   // 网络失败弹窗里的「无法访问 …」醒目行：直接告诉用户具体哪个地址连不上（{url} 为提取的不可达地址）
   failNetworkRegistryHint: '你的 npm/pnpm 源（registry）被配置为 {host}，插件包需从该源下载但失败了。这通常是内网/自定义源没有同步该包（或需要内网认证）—— 请把 npm/pnpm 的 registry 指回官方源 https://registry.npmjs.org（或确认此源可访问该包）后重试。',
   failNetworkTarget: '无法访问 {url} —— 你的网络连接不通',
@@ -357,6 +363,9 @@ export const zh = {
   // 404 依赖：点名 registry 上不存在的那个包（取不到包名时跳过这行），再给删除条目的指引
   failPnpmMissingDepTarget: '{pkg} 在 npm registry 上不存在（404）',
   failPnpmMissingDepHint: '安装器调用 pnpm 时报「包不存在」（ERR_PNPM_FETCH_404）：你的 profile 里留着一条指向 registry 上未发布包的依赖，pnpm 每次解析依赖都会先卡在它上面，因此任何插件都装不进来。这不是插件本身的问题——请在 profile 目录（~/.dsh/profiles/<profile>）的 package.json 里删除该依赖条目（同时删掉对应的 pnpm-lock.yaml 条目或整个锁文件）后重试。',
+  failRegistryMirrorLagHint: '安装器调用 pnpm 时报「包不存在」（ERR_PNPM_FETCH_404）：该包在官方 npm 源上是有的，但你本机配置的 npm/pnpm 源（registry 或镜像）没有同步到它。请把 npm/pnpm 的 registry 指回官方源 https://registry.npmjs.org（或换一个已同步该包的镜像）后重试。这不是插件本身的问题。',
+  failPluginMissingDepTarget: '{pkg} 在官方 npm 源上不存在',
+  failPluginMissingDepHint: '该插件依赖的包在官方 npm 源上并不存在（已删除或从未发布）：这是插件作者侧的依赖问题，不是你环境的问题。请向插件作者仓库反馈，请作者补上或修正该依赖，或改为随插件一起分发。',
   failRegistryVersionStaleHint: '安装器调用 pnpm 时报「找不到匹配的版本」（ERR_PNPM_NO_MATCHING_VERSION）：要装的这个版本在实际执行安装的 npm 源里查不到。常见原因是你设置的 npmRegistry 与本机 ~/.npmrc 用的不是同一个源——官方源刚发布、镜像还没同步上来（快则几分钟、慢则几小时），也可能只是版本号写错了。这不是插件本身的问题。可在插件市场设置里把 npmRegistry 改成与本机 ~/.npmrc 一致（或反过来），或那一次显式走官方源（https://registry.npmjs.org）、改用离线包后重试；若该版本刚发布不久，等镜像同步后重试即可。',
   failPnpmLinkedDirMissingHint: '安装器调用 pnpm 时报「要安装的目录不存在」（ERR_PNPM_LINKED_PKG_DIR_NOT_FOUND）：你的 profile 里留着一条指向本机不存在目录的本地依赖（link: / file: 形式，例如用 dsh plugin add <本地路径> 装过开发中的插件，之后那个目录被删除或移动了）。pnpm 每次解析 profile 依赖都会先卡在它上面，因此任何插件都装不进来。这不是插件本身的问题——请在 profile 目录（~/.dsh/profiles/<profile>）的 package.json 里删除该本地依赖条目（同时删掉对应的 pnpm-lock.yaml 条目或整个锁文件），或把该目录恢复回原路径后重试。',
   failFileLockedHint: '安装过程中 pnpm 无法替换 profile 里的文件：有程序正占用着它（Windows 常见报错 os error 32「另一个程序正在使用此文件」）。通常是 DeepSeek Harness 自身或杀毒软件的实时扫描持有文件句柄。这不是插件本身的问题——请完全退出 DeepSeek Harness（Windows 可在任务管理器确认进程已结束，必要时临时关闭杀毒软件实时防护）后重试。',
@@ -719,6 +728,10 @@ export const en = {
   errorTitleUninstall: 'Removal failed',
   // Update failed (notification center distinguishes install/update): update target reinstall failed
   errorTitleUpdate: 'Update failed',
+  // Action words: failure hints and filed reports take their wording from here
+  actionInstall: 'install',
+  actionUpdate: 'update',
+  actionUninstall: 'removal',
   errorPlugin: 'Plugin',
   errorClose: 'Got it',
   errorCopy: 'Copy error',
@@ -730,12 +743,14 @@ export const en = {
   failHubIssueHint: 'This failure was classified as an environment or Plugin Hub issue (not a plugin-author issue). Open a pre-filled issue on the Plugin Hub repo with this error log.',
   failHubIssueBig: 'Report to the Plugin Hub for triage',
   // Unknown-failure fallback: not routed to the plugin author, but to the hub repo for triage
-  failUnclassifiedHint: 'The install failed and the cause could not be identified automatically. This is usually not the plugin itself (it may relate to your local environment or the Plugin Hub). Please report the error to the Plugin Hub so the maintainers can triage it.',
+  failUnclassifiedHint: 'The {action} failed and the cause could not be identified automatically. This is usually not the plugin itself (it may relate to your local environment or the Plugin Hub). Please report the error to the Plugin Hub so the maintainers can triage it.',
   // The hub's own state-guard messages (plugin not installed / cannot be uninstalled here / already queued / already installed): the installed list is out of sync with the live snapshot — not a plugin issue, no issue prompt
-  failHubStateHint: 'The plugin list is out of date or out of sync: this plugin may already be installed (no need to reinstall — use "Update" to upgrade), or may no longer be in the installed list, or may already be queued. This is not a plugin problem — refresh the page and retry.',
-  // The install command hit the local time limit and was killed: it may well have installed successfully (the installer re-checks the installed list after a timeout) — actionable hint, no issue prompt
-  failTimeoutHint: 'The install exceeded the local time limit and was interrupted — but it may well have completed already (the installer re-checks your installed list after a timeout). Refresh the page to see whether the plugin is installed; if it is not, run the install command in a terminal to see the full output. This is not a plugin problem.',
-  failProfileLockHint: 'DSH timed out waiting for the file lock while writing the plugin list — usually because another DSH process or install task is writing the same profile (sometimes a previous run left the lock behind). Close other dsh windows or running commands, then retry; if it keeps happening, restart DSH once. This is not a plugin problem, and the plugin does not need to be reinstalled.',
+  failHubStateHint: 'The plugin list is out of date or out of sync: the target of this {action} may already be in the list (use "Update" to upgrade), may no longer be in the installed list, or may already be queued. This is not a plugin problem — refresh the page and retry.',
+  // The command hit the local time limit and was killed: it may well have taken effect already (the installer re-checks the installed list after a timeout) — actionable hint, no issue prompt
+  failTimeoutHint: 'This operation exceeded the local time limit and was interrupted — but it may well have taken effect already (the installer re-checks the installed list after a timeout). Refresh the page to confirm the current state; if it did not take effect, run the corresponding command in a terminal to see the full output. This is not a plugin problem.',
+  failProfileLockHint: 'DSH timed out waiting for the file lock while writing the plugin list — usually because another DSH process or install task is writing the same profile (sometimes a previous run left the lock behind). Close other dsh windows or running commands, then retry; if it keeps happening, restart DSH once. This is not a plugin problem, and there is no need to repeat the {action}.',
+  // The host could not launch itself to run the operation: not a plugin issue — hint only, no issue prompt
+  failHostCliSpawnHint: 'DSH could not start itself to perform this operation (the system reported that the executable was not found). This usually means the DSH installation folder has been moved or is being updated, or that the profile directory does not exist yet. Restart DSH and retry; if it keeps happening, reinstall DSH. This is not a plugin problem — other plugins would fail the same way.',
   // prepare script actually failed (git tarball misses submodules/build output): a packaging issue of the plugin itself — file an issue
   failPrepareHint: 'This plugin failed while running its build scripts during install (git tarballs often miss submodules or build output). This is a packaging issue of the plugin itself — please report it to the author repository.',
   // Secondary entry on the "plugin packaging" branch: that verdict comes from the hub's own
@@ -746,11 +761,11 @@ export const en = {
   // Pre-install / post-install guard hit ([packaging]): git distribution lacks a file the package needs (entry / entry a patch mounts / bundle patch) = not adapted to the official default install method
   failPackagingHint: 'This plugin does not support the official default install method: its git distribution lacks a file the package needs (the entry from `main` / `exports`, an entry its own patch mounts by name, or the patch declared by `dsh.bundle.patch`), so it has not been adapted to the official install flow. Please file an Issue on the author\'s repo asking for committed build output, a prebuilt release `.tgz` (`releases/download/<tag>/<asset>.tgz`), or a complete npm release.',
   // native-module build scripts ignored by pnpm by default (e.g. node-pty, ERR_PNPM_IGNORED_BUILDS): not a plugin-side issue on its own, route to the hub repo for triage
-  failIgnoredBuild: 'This plugin (or one of its dependencies) needs to run build scripts at install time, which pnpm blocks by default via its allowBuilds allowlist — so the install fails (e.g. native modules like node-pty, or the plugin\'s own prepare script on git installs). The installer already auto-allows that key and retries once; if it still fails, the build itself is usually the problem. Run the install command in a terminal to see the full build error; if it is indeed the plugin\'s build or distribution, the author can ship prebuilt output, an npm release, or a prebuilt .tgz. You can also report it to the Plugin Hub for triage.',
+  failIgnoredBuild: 'This plugin (or one of its dependencies) needs to run build scripts at install time, which pnpm blocks by default via its allowBuilds allowlist — so this operation fails (e.g. native modules like node-pty, or the plugin\'s own prepare script on git installs). The installer already auto-allows that key and retries once; if it still fails, the build itself is usually the problem. Run the install command in a terminal to see the full build error; if it is indeed the plugin\'s build or distribution, the author can ship prebuilt output, an npm release, or a prebuilt .tgz. You can also report it to the Plugin Hub for triage.',
   failNpmTooLow: 'Your local npm may be too old: npm crashed internally while resolving the plugin\'s dependencies (a known npm bug — not a plugin issue). Please upgrade npm and retry: npm install -g npm@latest',
   failNpmTooLowV: 'Your local npm is too old (v{v}): npm crashed internally while resolving the plugin\'s dependencies (a known npm bug — not a plugin issue). Please upgrade npm and retry: npm install -g npm@latest',
   // Pre-install connectivity probe / connection failure in the install log ([network] / git fetch timeout / DNS / TLS): a local network or proxy issue, not a plugin issue — no issue link
-  failNetworkHint: 'The network could not be reached before install: the install source is unreachable (offline, DNS failure, firewall block, or a misconfigured proxy). This is not a problem with the plugin itself — please check your connection, confirm the HTTP proxy in Settings, run a connectivity check under System Diagnostics, then retry.',
+  failNetworkHint: 'The network could not be reached before the {action}: the install source is unreachable (offline, DNS failure, firewall block, or a misconfigured proxy). This is not a problem with the plugin itself — please check your connection, confirm the HTTP proxy in Settings, run a connectivity check under System Diagnostics, then retry.',
   // Prominent "cannot reach …" line in the network-failure dialog: shows the exact unreachable address ({url})
   failNetworkRegistryHint: 'Your npm/pnpm registry is set to {host}, and the package tarball could not be downloaded from it. This usually means a private/internal mirror that has not synced the package (or requires intranet auth) — point the registry back to https://registry.npmjs.org (or make sure this source can serve the package), then retry.',
   failNetworkTarget: 'Cannot reach {url} — your network connection is down',
@@ -770,6 +785,9 @@ export const en = {
   // then give the removal instructions
   failPnpmMissingDepTarget: '{pkg} was not found on the npm registry (404)',
   failPnpmMissingDepHint: 'pnpm reported that a package does not exist on the npm registry (ERR_PNPM_FETCH_404): your profile keeps a dependency on a package that was never published, and pnpm hits it every time it resolves dependencies — no plugin can be installed into that profile. This is not a problem with the plugin itself. Remove that dependency from package.json inside the profile directory (~/.dsh/profiles/<profile>) — along with its entry in pnpm-lock.yaml, or the lockfile itself — then retry.',
+  failRegistryMirrorLagHint: 'pnpm reported that a package does not exist on the npm registry (ERR_PNPM_FETCH_404): that package does exist on the official npm registry, but the npm/pnpm registry (or mirror) configured on your machine has not synced it. Point the npm/pnpm registry back at the official one (https://registry.npmjs.org), or switch to a mirror that has the package, then retry. This is not a problem with the plugin itself.',
+  failPluginMissingDepTarget: '{pkg} does not exist on the official npm registry',
+  failPluginMissingDepHint: 'A package this plugin depends on does not exist on the official npm registry (removed, or never published). This is a dependency problem on the plugin author side, not a problem with your environment. Please report it to the plugin repository so the author can fix that dependency or ship it together with the plugin.',
   failRegistryVersionStaleHint: 'pnpm reported that no matching version was found (ERR_PNPM_NO_MATCHING_VERSION): the version being installed does not exist in the npm registry that actually performs the install. This usually means the npmRegistry configured in the hub differs from the source in your local ~/.npmrc — the official registry has published it but the mirror has not synced yet (it can take minutes to hours) — or the version number was simply mistyped. This is not a problem with the plugin itself. Align the hub\'s npmRegistry with your local ~/.npmrc (or the other way round), or explicitly use the official registry (https://registry.npmjs.org) for that one install, or use an offline package, then retry; if the version was published only recently, waiting for the mirror to sync is enough.',
   failPnpmLinkedDirMissingHint: 'pnpm reported that a directory it needs to install from does not exist (ERR_PNPM_LINKED_PKG_DIR_NOT_FOUND): your profile keeps a local dependency (a link: / file: entry, e.g. from `dsh plugin add <local path>`) whose target directory has since been deleted or moved. pnpm hits it every time it resolves profile dependencies, so no plugin can be installed into that profile. This is not a problem with the plugin itself. Remove that local dependency from package.json inside the profile directory (~/.dsh/profiles/<profile>) — along with its entry in pnpm-lock.yaml, or the lockfile itself — or restore the directory to its original path, then retry.',
   failFileLockedHint: 'During install, pnpm could not replace a file inside the profile because another program is holding it (on Windows this shows as os error 32, "the process cannot access the file because it is being used by another process"). Usually DeepSeek Harness itself or a real-time antivirus scan holds the handle. This is not a problem with the plugin itself — fully quit DeepSeek Harness (on Windows, confirm in Task Manager that the process has ended, and temporarily disable real-time antivirus protection if needed), then retry.',

package/src/client/logic/failures.ts

@@ -151,7 +151,26 @@ export function removeNotification(id: number): NotificationRecord[] {
   return next
 }
 
-export type FailureKind = 'npmTooOld' | 'dshMissing' | 'gitMissing' | 'pnpmMissing' | 'npmMissing' | 'pnpmStore' | 'pnpmWorkspace' | 'originRejected' | 'pnpmPolicy' | 'pnpmUnusedPatch' | 'pnpmMissingDep' | 'registryVersionStale' | 'pnpmLinkedDirMissing' | 'fileLocked' | 'accessDenied' | 'fsUnavailable' | 'pnpmIgnoredBuild' | 'pluginPrepare' | 'network' | 'hubState' | 'timeout' | 'profileLock' | 'hub'
+export type FailureKind = 'npmTooOld' | 'dshMissing' | 'gitMissing' | 'pnpmMissing' | 'npmMissing' | 'pnpmStore' | 'pnpmWorkspace' | 'originRejected' | 'pnpmPolicy' | 'pnpmUnusedPatch' | 'pnpmMissingDep' | 'pluginMissingDep' | 'registryVersionStale' | 'pnpmLinkedDirMissing' | 'fileLocked' | 'accessDenied' | 'fsUnavailable' | 'pnpmIgnoredBuild' | 'pluginPrepare' | 'network' | 'hostCliSpawn' | 'hubState' | 'timeout' | 'profileLock' | 'hub'
+
+/** 失败动作口径：标题、上报正文与提示文案按安装/更新/卸载取词，不写死「安装」。 */
+export type FailureAction = 'install' | 'update' | 'uninstall'
+
+/** 动作词（英文）：名词短语，标题与句子里都成立。 */
+export function actionWordEn(action: FailureAction): string {
+  return action === 'uninstall' ? 'removal' : action === 'update' ? 'update' : 'install'
+}
+
+/** 动作词（中文）：安装 / 更新 / 卸载。 */
+export function actionWordZh(action: FailureAction): string {
+  return action === 'uninstall' ? '卸载' : action === 'update' ? '更新' : '安装'
+}
+
+/** 记录的动作：老记录只有 kind，按 kind 兜底。 */
+export function actionOfRecord(rec: { kind: NotificationRecord['kind']; action?: FailureAction }): FailureAction {
+  if (rec.action !== undefined) return rec.action
+  return rec.kind === 'uninstall' ? 'uninstall' : rec.kind === 'update' ? 'update' : 'install'
+}
 
 /** Match the pnpm error code, not a generic mention of checksum or integrity. */
 function missingTarballIntegrity(message: string): boolean {
@@ -230,6 +249,8 @@ export function classifyFailure(message: string): FailureKind {
   // 装后校验发现入口文件缺失（[packaging]）= git 分发缺构建产物
   if (/\[packaging\]|entry file missing/i.test(message)) return 'pluginPrepare'
   // registry 上不存在的依赖（404），profile 任何安装都会卡在这条。必须在 pluginPrepare 之前判
+  // [registry-missing]（服务端官方源复核后注入）= 作者侧缺依赖，须先于 pnpmMissingDep（同样含 404 文本）
+  if (/\[registry-missing\]/i.test(message)) return 'pluginMissingDep'
   if (/ERR_PNPM_FETCH_404|404 Not Found|Not Found - 404/i.test(message)) return 'pnpmMissingDep'
   // 要装的版本在实际安装源里没有（镜像滞后或版本写错）。必须在 pluginPrepare 之前判
   if (/\bERR_PNPM_NO_MATCHING_VERSION\b|\bETARGET\b|No matching version found/i.test(message)) return 'registryVersionStale'
@@ -252,6 +273,11 @@ export function classifyFailure(message: string): FailureKind {
   // dsh 进程或安装任务在写，锁一直没释放。既不是插件问题、也不是用户环境坏了 —— 把并发收掉重试即可。
   // 摆放位置同样在一切错误码分支之后：日志里真有 pnpm 报错时仍以真实报错为准。
   if (/atomic-write: timed out waiting for the writer lock|timed out waiting for the writer lock/i.test(message)) return 'profileLock'
+  // 宿主自己的 allowBuilds 摘要行（pnpm 原文只写进 diagnostics 日志文件，终端只剩这一句）
+  if (/git-hosted plugins build on install via their prepare script|add the exact key pnpm printed above under allowBuilds/i.test(message)) return 'pnpmIgnoredBuild'
+  // 宿主自身入口起不来（服务端 [host-spawn] 标记）：环境问题，给提示、不引导提 Issue。
+  // 不匹配 `spawn … ENOENT` 文本 —— 那个形态任何 spawn（curl/git/taskkill…）都会产出
+  if (/\[host-spawn\]/i.test(message)) return 'hostCliSpawn'
   // 其余未知失败：引导到插件中心仓库排查
   return 'hub'
 }
@@ -318,13 +344,21 @@ export function coreErrorCode(message: string): string | null {
   return m ? m[0].replace(/^\[|\]$/g, '') : null
 }
 
+/** 「包在 registry 不存在」失败的提示变体：服务端用官方源复核过（会注入 `[registry-mirror-lag]`）
+ *  时，说明包在官方源上存在、是本机镜像源未同步 → 提示换源；否则沿用既有的「profile 残留依赖」
+ *  提示（#73：指向从未发布包的残留条目，任何插件都装不进来）。 */
+export function registryMissingHintOf(message: string): 'failPnpmMissingDepHint' | 'failRegistryMirrorLagHint' {
+  return /\[registry-mirror-lag\]/i.test(message) ? 'failRegistryMirrorLagHint' : 'failPnpmMissingDepHint'
+}
+
 /** 提取「registry 上不存在的包名」：从 404 行（`ERR_PNPM_FETCH_404 GET <registry>/<pkg>: Not Found - 404`）
  *  里取请求路径中的包名（含 scope，如 `@scope/name`）；非 404 或提取不到返回 null。 */
 export function missingRegistryPackageOf(message: string): string | null {
   for (const line of message.split(/\r?\n/)) {
     if (!/ERR_PNPM_FETCH_404|404/.test(line)) continue
     const m = line.match(/GET\s+https?:\/\/[^\s/]+\/((?:@[^/\s:]+\/)?[^/\s:]+)/)
-    if (m) return m[1]
+    // pnpm 输出里 scope 包是 URL 编码形态（`@scope%2Fname`）：还原成 `@scope/name` 再展示
+    if (m) return m[1].replace(/%40/gi, '@').replace(/%2f/gi, '/')
   }
   return null
 }

package/src/client/logic/urls.ts

@@ -9,9 +9,9 @@
  */
 import type { EnvInfo, HubPlugin, LocaleId } from '../types.ts'
 import { GITHUB_URL, HUB_REPO, PLUGIN_VERSION, SITE_URL } from './constants.ts'
-import { MAX_CORE_CHARS, classifyFailure, coreErrorCode, pnpmPolicyHintOf, summarizeError } from './failures.ts'
+import { MAX_CORE_CHARS, actionWordEn, actionWordZh, classifyFailure, coreErrorCode, pnpmPolicyHintOf, summarizeError } from './failures.ts'
 import { executedCommandOf } from './install-command.ts'
-import type { FailureKind } from './failures.ts'
+import type { FailureAction, FailureKind } from './failures.ts'
 
 /** dsh-plugin.org 中文页挂在 /zh/ 前缀下，英文在根路径。 */
 export function langPathOf(lang: LocaleId): string {
@@ -41,18 +41,18 @@ export function pluginSiteUrl(repo: string): string {
   return siteUrl(`plugins/${repo}`)
 }
 
-/** 按失败类型给出简洁的错误原因标题（对外用英文）：
- *  标题直接点明问题出在哪一侧（构建白名单/分发物/本机 npm/网络/插件侧），
- *  让作者与用户扫一眼列表就能分流，而不是笼统的 Install/Remove 动作词。 */
-function reasonTitleOf(kind: FailureKind): string {
+/** 错误原因标题（对外英文）：点明问题出在哪一侧，便于 issue 列表分流；
+ *  动作级原因（未分类/超时…）带动作词，卸载失败不写成 install failed。 */
+function reasonTitleOf(kind: FailureKind, action: FailureAction): string {
+  const word = actionWordEn(action)
   switch (kind) {
-    case 'npmTooOld': return 'npm too old to install'
+    case 'npmTooOld': return `npm too old for this ${word}`
     case 'dshMissing': return 'dsh command not found on the user machine'
     case 'pnpmMissing': return 'pnpm command not found on the user machine'
     case 'pnpmStore': return 'pnpm store version mismatch on the user machine'
-    case 'pnpmWorkspace': return 'pnpm workspace-root check blocked the install on the user machine'
+    case 'pnpmWorkspace': return `pnpm workspace-root check blocked the ${word} on the user machine`
     case 'originRejected': return 'request origin rejected by the local service on the user machine'
-    case 'pnpmPolicy': return 'pnpm supply-chain policy blocked the install on the user machine'
+    case 'pnpmPolicy': return `pnpm supply-chain policy blocked the ${word} on the user machine`
     case 'pnpmUnusedPatch': return 'stale pnpm patch entry on the user machine'
     case 'pnpmMissingDep': return 'dependency not found on the npm registry on the user machine'
     case 'registryVersionStale': return 'requested version not available on the npm registry in use on the user machine'
@@ -63,11 +63,13 @@ function reasonTitleOf(kind: FailureKind): string {
     case 'pnpmIgnoredBuild': return 'build scripts blocked by pnpm allowlist'
     case 'pluginPrepare': return 'plugin distribution incomplete'
     case 'network': return 'network failure on the user side'
-    case 'hubState': return 'stale install state in the plugin hub'
-    case 'timeout': return 'install timed out'
+    case 'hostCliSpawn': return 'the DSH host could not be launched on the user machine'
+    case 'hubState': return `stale ${word} state in the plugin hub`
+    case 'timeout': return `${word} timed out`
     case 'profileLock': return 'DSH profile is locked by another process'
-    case 'hub': return 'install failed (cause unclassified)'
-    default: return 'plugin install failed'
+    case 'pluginMissingDep': return 'a dependency of the plugin is not published on npm'
+    case 'hub': return `${word} failed (cause unclassified)`
+    default: return `plugin ${word} failed`
   }
 }
 
@@ -80,16 +82,21 @@ function reasonTitleOf(kind: FailureKind): string {
  * attempts（尝试过的安装方式，npm 反查 + 实际执行命令）：作者看到我们查过/试过的命令，
  * 组织 scope 与 GitHub 用户名不一致时也能直接指认正确的 npm 包名。
  */
-export function pluginIssueUrl(repo: string, message: string, env?: EnvInfo | null, command?: string, attempts?: string[]): string {
+export function pluginIssueUrl(repo: string, message: string, env?: EnvInfo | null, command?: string, attempts?: string[], action: FailureAction = 'install'): string {
   // 原因判定：按失败类型归类，便于作者判断问题是否出在插件侧。
   // [packaging]（预检/装后校验拦截）单独列：无论走 npm 还是 git 通道，都是分发物不完整
   // （package.json 声明的文件在发布物里缺失），作者照此补齐即可。
   const kind = classifyFailure(message)
   const executed = executedCommandOf(command, attempts)
+  // 动作词：标题与正文的「安装/更新/卸载」统一取自这里
+  const zhWord = actionWordZh(action)
   // 标题 = 错误原因（非动作词），让 issue 列表一眼可分流
-  const title = `[dsh-plugin.org | dsh-plugin-hub] ${reasonTitleOf(kind)}: ${repo}`
+  const title = `[dsh-plugin.org | dsh-plugin-hub] ${reasonTitleOf(kind, action)}: ${repo}`
   const reason = /\[packaging\]/i.test(message)
     ? 'plugin distribution is incomplete — a file the package needs (its entry from main / exports, an entry a bundled patch mounts, or the patch declared by dsh.bundle.patch) is missing from the published package (github tarball or npm package); please commit build output or publish a complete package'
+      : /\[registry-missing\]/i.test(message)
+        // 服务端用官方 registry 复核过：缺的包在官方源上也不存在，且不是用户 profile 的残留依赖
+        ? 'a dependency declared by the plugin is not published on the public npm registry (missing, removed, or never released); please publish or correct that dependency, or ship it with the plugin'
       : kind === 'network'
         ? 'network connectivity issue on the user side (DNS, proxy, firewall, or a blocked connection)'
         : kind === 'pluginPrepare'
@@ -119,16 +126,15 @@ export function pluginIssueUrl(repo: string, message: string, env?: EnvInfo | nu
       `- Cause: ${reason}`,
       ...(code ? [`- Key error: \`${code}\``] : []),
       '',
-      // 来源说明：标题（链官网）+ 一句来源（链仓库）+ 实际执行的安装命令（含 --profile）与执行结果，链接由常量动态拼接
-      `## [DSH Plugin 插件市场](${SITE_URL}) · 安装 Plugin 失败错误信息`,
-      `本错误信息由 [dsh-plugin-hub](${GITHUB_URL}) 插件市场的安装程序自动生成，随本次安装失败一并提交。`,
-      `- 实际执行的安装命令：${executed ? `\`${executed}\`` : 'unknown (no executed command recorded)'}`,
-      `- 执行结果：安装失败，未能安装该插件。`,
-      // 尝试过的安装方式（npm 反查 + 实际执行命令，按先后顺序）：作者据此反推正确的
-      // npm 包名 —— 组织 scope 与 GitHub 用户名不一致时仅凭仓库名猜不到，作者看到我们
-      // 查过/试过的命令就能直接指认
+      // 来源说明：标题（链官网）+ 一句来源（链仓库）+ 实际执行的命令（含 --profile）与执行结果，链接由常量动态拼接
+      `## [DSH Plugin 插件市场](${SITE_URL}) · ${zhWord} Plugin 失败错误信息`,
+      `本错误信息由 [dsh-plugin-hub](${GITHUB_URL}) 插件市场的安装程序自动生成，随本次${zhWord}失败一并提交。`,
+      `- 实际执行的${zhWord}命令：${executed ? `\`${executed}\`` : 'unknown (no executed command recorded)'}`,
+      `- 执行结果：${zhWord}失败，未能${zhWord}该插件。`,
+      // 尝试过的通道（npm 反查 + 实际执行命令，按先后顺序）：作者据此指认正确的 npm 包名。
+      // 不写「安装」：卸载失败也走这条正文。
       ...(attempts && attempts.length > 0
-        ? ['', '## Attempted install channels（已尝试的安装方式）', ...attempts.map((a) => `- ${a}`)]
+        ? ['', '## Attempted channels（已尝试的方式）', ...attempts.map((a) => `- ${a}`)]
         : []),
       // [packaging] 场景：说明三种官方安装通道（npm 包 / git 直装 / 预构建 release .tgz），当前插件在对应通道下分发不完整
       ...(/\[packaging\]/i.test(message)
@@ -206,19 +212,22 @@ export function hubIssueUrl(
   attempts?: string[],
   /** 见 HubIssueVariant；缺省 'triage'，既有正文保持不变 */
   variant: HubIssueVariant = 'triage',
+  /** 上报动作：标题与正文按它取词 */
+  action: FailureAction = 'install',
 ): string {
   const kind = classifyFailure(message)
   const executed = executedCommandOf(command, attempts)
+  const zhWord = actionWordZh(action)
   const repo = pluginRepo && pluginRepo.trim() !== '' ? pluginRepo.trim() : 'unknown'
   const title = variant === 'misjudge'
     // 标题就点明「可能是误判」，维护者一眼能区分它和未分类兜底
     ? `[dsh-plugin-hub] possible misjudgment: ${repo}`
-    : `[dsh-plugin-hub] ${reasonTitleOf(kind)}: ${repo}`
+    : `[dsh-plugin-hub] ${reasonTitleOf(kind, action)}: ${repo}`
   const code = coreErrorCode(message)
   const build = (coreChars: number): string => {
     const body = [
       '## Summary',
-      `- Auto-classified cause: ${reasonTitleOf(kind)}`,
+      `- Auto-classified cause: ${reasonTitleOf(kind, action)}`,
       `- Target plugin: \`${repo}\``,
       ...(code ? [`- Key error: \`${code}\``] : []),
       // 为什么投递到这里而非插件仓库：只有确有证据是插件自身构建失败（pluginPrepare）才投插件仓库
@@ -232,12 +241,12 @@ export function hubIssueUrl(
         ]
         : ['- Why filed here: the installer only routes a failure to the plugin repo when there is positive evidence the plugin build itself failed (pluginPrepare). This failure does not match that, so it is routed here for triage.']),
       '',
-      `## [DSH Plugin 插件市场](${SITE_URL}) · 安装 Plugin 失败错误信息`,
-      `本错误信息由 [dsh-plugin-hub](${GITHUB_URL}) 插件市场的安装程序自动生成，随本次安装失败一并提交。`,
-      `- 实际执行的安装命令：${executed ? `\`${executed}\`` : 'unknown (no executed command recorded)'}`,
-      `- 执行结果：安装失败，未能安装该插件。`,
+      `## [DSH Plugin 插件市场](${SITE_URL}) · ${zhWord} Plugin 失败错误信息`,
+      `本错误信息由 [dsh-plugin-hub](${GITHUB_URL}) 插件市场的安装程序自动生成，随本次${zhWord}失败一并提交。`,
+      `- 实际执行的${zhWord}命令：${executed ? `\`${executed}\`` : 'unknown (no executed command recorded)'}`,
+      `- 执行结果：${zhWord}失败，未能${zhWord}该插件。`,
       ...(attempts && attempts.length > 0
-        ? ['', '## Attempted install channels（已尝试的安装方式）', ...attempts.map((a) => `- ${a}`)]
+        ? ['', '## Attempted channels（已尝试的方式）', ...attempts.map((a) => `- ${a}`)]
         : []),
       '',
       '## Environment',

package/src/server/services/install/registry-check.ts

@@ -0,0 +1,83 @@
+/**
+ * DSH Plugin Hub — the community plugin marketplace for DeepSeek Harness.
+ * Website: https://dsh-plugin.org
+ * GitHub: https://github.com/dshplugin/dsh-plugin-hub
+ *
+ * 官方 registry 存在性复核：用官方源（绕开本机镜像）复查 404 的包，产出标记行区分
+ * 「profile 残留依赖」「插件依赖在官方源也不存在（作者侧）」「本机镜像未同步」三种情形；
+ * 标记由 task-queue 追加到任务输出，前端按标记归类。fetch 与 profile 目录可注入，便于单测。
+ */
+import { readFileSync } from 'node:fs'
+import { join } from 'node:path'
+
+/** pnpm 输出里 scope 包是 URL 编码形态（`@scope%2Fname`）：比较依赖名、拼查询 URL 前先还原成
+ *  `@scope/name`。 */
+function decodePackageName(raw: string): string {
+  return raw.replace(/%40/gi, '@').replace(/%2f/gi, '/')
+}
+
+/** 从失败输出里提取「registry 上不存在的包名」（含 scope，如 `@scope/name`）：读 404 行的请求路径。
+ *  提取不到返回 null。 */
+export function missingPackageOf(output: string): string | null {
+  for (const line of output.split(/\r?\n/)) {
+    if (!/ERR_PNPM_FETCH_404|404/.test(line)) continue
+    const m = line.match(/GET\s+https?:\/\/[^\s/]+\/((?:@[^/\s:]+\/)?[^/\s:]+)/)
+    if (m) return decodePackageName(m[1])
+  }
+  return null
+}
+
+/** 读 profile 自己声明的依赖名（profile 目录下 package.json 的 dependencies 键）。读不到返回空数组。 */
+export function profileDependencyNames(profileDir: string): string[] {
+  try {
+    const raw = JSON.parse(readFileSync(join(profileDir, 'package.json'), 'utf8')) as { dependencies?: Record<string, unknown> }
+    return Object.keys(raw.dependencies ?? {})
+  } catch {
+    return []
+  }
+}
+
+/** 官方 registry 上是否存在该包：明确 404 → false（不存在），2xx → true，其余（限流/网络异常）→ null
+ *  —— 判不了就不判，绝不妄下结论。 */
+async function existsOnOfficialRegistry(
+  name: string,
+  fetchImpl: typeof fetch,
+  timeoutMs: number,
+): Promise<boolean | null> {
+  // scope 包的路径要编码：`@scope/name` → `%40scope%2Fname`
+  const url = `https://registry.npmjs.org/${name.replace('@', '%40').replace('/', '%2F')}`
+  try {
+    const res = await fetchImpl(url, {
+      headers: { accept: 'application/vnd.npm.install-v1+json' },
+      signal: AbortSignal.timeout(timeoutMs),
+    })
+    if (res.status === 404) return false
+    return res.ok ? true : null
+  } catch {
+    return null
+  }
+}
+
+/**
+ * 产出「包不存在」失败的责任方标记行；判不了返回 null（前端维持既有提示）。
+ * - `[registry-missing]`     缺的包在官方源上也不存在 → 作者侧问题（前端引导投作者）
+ * - `[registry-mirror-lag]`  官方源上有 → 本机镜像源未同步（前端提示换源，不投任何一方）
+ */
+export async function registryMissingMarker(
+  output: string,
+  opts: { profileDir: string; fetchImpl?: typeof fetch; timeoutMs?: number },
+): Promise<string | null> {
+  const name = missingPackageOf(output)
+  if (name === null) return null
+  // ① profile 自己声明的残留依赖（#73）：用户环境问题，交给既有的 pnpmMissingDep 提示（该提示就是
+  // 教用户删 profile 里那条依赖），这里不再产出标记、不改归属
+  if (profileDependencyNames(opts.profileDir).some((dep) => dep.toLowerCase() === name.toLowerCase())) return null
+  const exists = await existsOnOfficialRegistry(name, opts.fetchImpl ?? fetch, opts.timeoutMs ?? 8000)
+  if (exists === false) {
+    return `[registry-missing] ${name} is not published on the official npm registry (registry.npmjs.org) — a dependency of this plugin is missing or was removed; author-side issue`
+  }
+  if (exists === true) {
+    return `[registry-mirror-lag] ${name} exists on the official npm registry — the configured registry or mirror has not synced it; local environment issue`
+  }
+  return null
+}

package/src/server/services/install/task-queue.ts

@@ -14,6 +14,7 @@ import { dirname, join, resolve } from 'node:path'
 import type { InstallResult, InstallTask, Invocation, QueueItem } from './install-types.ts'
 import { CAPTURE_LIMIT_BYTES, MAX_TASKS, MAX_TASK_LINES } from './install-types.ts'
 import { npmTooLowMarker } from './npm-check.ts'
+import { registryMissingMarker } from './registry-check.ts'
 import { backfillOperationLog } from './operation-log.ts'
 import { cleanLine, estimateProgress } from '../profile/progress.ts'
 import type { LoaderHandle } from '../loader.ts'
@@ -148,6 +149,13 @@ function pushLine(task: InstallTask, line: string): void {
   }
 }
 
+/** spawn 的 cwd：profile 目录（asar 路径不能作 cwd）；目录不存在时回退进程工作目录，
+ *  否则 Node 报的是 `spawn <file> ENOENT`，与「可执行文件不存在」无法区分。 */
+function spawnCwdFor(profile: string): string {
+  const dir = profileDirectory(profile)
+  return existsSync(dir) ? dir : process.cwd()
+}
+
 function cliInvocation(profile: string): Invocation {
   const entry = process.argv[1]
   if (entry !== undefined) {
@@ -161,8 +169,8 @@ function cliInvocation(profile: string): Invocation {
       return {
         file: process.execPath,
         prefixArgs: ['--expose-internals', bootstrap],
-        // 工作目录用 profile 目录（真实存在的目录）：asar 内的路径不能作为 spawn 的 cwd
-        cwd: profileDirectory(profile),
+        // cwd 用 profile 目录（asar 路径不能作 cwd），不存在时由 spawnCwdFor 回退
+        cwd: spawnCwdFor(profile),
         useShell: false,
         // Electron 可执行文件只有带这个变量才按 Node 运行引导脚本
         env: { ELECTRON_RUN_AS_NODE: '1' },
@@ -474,15 +482,19 @@ function spawnMutation(options: {
         stdio: ['ignore', 'pipe', 'pipe'],
       })
     } catch (error) {
+      const detail = error instanceof Error ? error.message : String(error)
+      // 宿主自身入口起不来 → 补标记，前端据此归因
+      const marker = hostSpawnMarker(invocation, error)
       if (task) {
         task.status = 'failed'
         task.exitCode = null
-        pushLine(task, `[error] ${error instanceof Error ? error.message : String(error)}`)
+        pushLine(task, `[error] ${detail}`)
+        if (marker !== null) pushLine(task, marker)
       }
       resolveOnce({
         exitCode: null,
         timedOut: false,
-        error: error instanceof Error ? error.message : String(error),
+        error: marker === null ? detail : `${detail}\n${marker}`,
         stdout,
         stderr,
       })
@@ -553,12 +565,15 @@ function spawnMutation(options: {
     })
 
     child.once('error', (error) => {
+      // 同同步抛出那条路径：宿主自身入口起不来 → 补标记
+      const marker = hostSpawnMarker(invocation, error)
       if (task && task.status !== 'cancelled') {
         task.status = 'failed'
         task.exitCode = null
         pushLine(task, `[error] ${error.message}`)
+        if (marker !== null) pushLine(task, marker)
       }
-      settleOnce({ exitCode: null, timedOut: false, error: error.message, stdout, stderr })
+      settleOnce({ exitCode: null, timedOut: false, error: marker === null ? error.message : `${error.message}\n${marker}`, stdout, stderr })
     })
 
     child.once('close', (code) => {
@@ -711,6 +726,33 @@ function annotateNpmTooLow(result: InstallResult, options: {
   return { ...result, stderr: `${result.stderr}\n${line}`, error: result.error ? `${result.error}\n${line}` : line }
 }
 
+/** 安装失败且日志含 404 时，用官方源复查一次并注入标记（逻辑见 registry-check.ts）。
+ *  异步是因为要联网；只在失败路径上发生。 */
+async function annotateRegistryMissing(result: InstallResult, options: {
+  action: 'add' | 'remove' | 'update'
+  profile: string
+  task?: InstallTask
+}): Promise<InstallResult> {
+  if (options.action === 'remove' || result.exitCode === 0 || result.timedOut) return result
+  const line = await registryMissingMarker(`${result.stderr}\n${result.stdout}`, {
+    profileDir: profileDirectory(options.profile),
+  })
+  if (line === null) return result
+  if (options.task && options.task.status !== 'cancelled') pushLine(options.task, line)
+  return { ...result, stderr: `${result.stderr}\n${line}`, error: result.error ? `${result.error}\n${line}` : line }
+}
+
+/**
+ * 宿主自身 CLI 调不起来时的 ASCII 标记行：spawn 我们解析出的宿主入口报 ENOENT 时返回
+ * `[host-spawn]`，供前端单独归因、不引导提 Issue。PATH 上的 dsh/npm 各有自己的标记，返回 null。
+ * 导出供单测覆盖判据。
+ */
+export function hostSpawnMarker(invocation: Invocation, error: unknown): string | null {
+  if ((error as NodeJS.ErrnoException | null)?.code !== 'ENOENT') return null
+  if (invocation.file === 'dsh' || invocation.file === 'npm') return null
+  return `[host-spawn] the DSH host could not be launched (${invocation.file}: ENOENT)`
+}
+
 /**
  * Run a plugin mutation with one recovery path: when `add` fails because
  * pnpm's allowBuilds gate blocks a build script — either the git-hosted
@@ -804,6 +846,8 @@ export async function runPluginMutation(options: {
       result = { ...result, stderr: `${result.stderr}\n${backfilled}` }
     }
   }
+  // 包在 registry 不存在（404）→ 官方源复查，区分「作者的依赖缺失/包被删」与「本机镜像源滞后」
+  result = await annotateRegistryMissing(result, options)
   // npm arborist edgesOut 崩溃 + 本机 npm 版本过低 → 追加 [npm-too-low] 标记，前端据此给准确原因
   return annotateNpmTooLow(result, options)
 }