dsh-plugin 1.6.11 → 1.6.12

package/lib/services/install/registry-check.js

@@ -3,20 +3,9 @@
  * Website: https://dsh-plugin.org
  * GitHub: https://github.com/dshplugin/dsh-plugin-hub
  *
- * 官方 registry 存在性复核：把「包在 registry 上不存在」这类失败的责任方分开。
- *
- * 背景：安装失败日志出现 `ERR_PNPM_FETCH_404` / `Not Found - 404` 时，光看日志分不清三种情形：
- *   ① 缺的包是 **profile 自己声明的依赖**（历史残留条目，指向一个从未发布的包）—— 用户环境问题：
- *      pnpm 每次解析依赖都会先卡在它上面，任何插件都装不进来（issue #73），提示删掉该条目即可；
- *   ② 缺的包来自**插件的依赖树**，且该包在官方 registry 上也不存在 —— 作者侧问题（漏声明依赖、
- *      依赖被删除或从未发布），应引导用户投插件作者仓库；
- *   ③ 缺的包来自插件依赖树，但官方 registry 上有 —— 用户本机 registry 指向的镜像/私有源未同步
- *      该包，属用户环境问题，提示换源即可。
- * 故本模块先排除 ①（读 profile 的 package.json），再用**官方** registry（registry.npmjs.org，
- * 绕开本机可能配置的镜像）复查存在性，产出 ② / ③ 的标记行。
- *
- * 与 npm-check.ts 同构：本模块只产出「标记行」，由 task-queue 追加到任务输出，前端按标记分类。
- * fetch 与 profile 目录都可注入，便于单测覆盖全部结论而不依赖网络。
+ * 官方 registry 存在性复核：用官方源（绕开本机镜像）复查 404 的包，产出标记行区分
+ * 「profile 残留依赖」「插件依赖在官方源也不存在（作者侧）」「本机镜像未同步」三种情形；
+ * 标记由 task-queue 追加到任务输出，前端按标记归类。fetch 与 profile 目录可注入，便于单测。
  */
 import { readFileSync } from 'node:fs';
 import { join } from 'node:path';

package/lib/services/install/task-queue.js

@@ -132,6 +132,12 @@ function pushLine(task, line) {
         task.progress = Math.max(task.progress, 6 + Math.min(79, task.lines.length * 2));
     }
 }
+/** spawn 的 cwd：profile 目录（asar 路径不能作 cwd）；目录不存在时回退进程工作目录，
+ *  否则 Node 报的是 `spawn <file> ENOENT`，与「可执行文件不存在」无法区分。 */
+function spawnCwdFor(profile) {
+    const dir = profileDirectory(profile);
+    return existsSync(dir) ? dir : process.cwd();
+}
 function cliInvocation(profile) {
     const entry = process.argv[1];
     if (entry !== undefined) {
@@ -145,8 +151,8 @@ function cliInvocation(profile) {
             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' },
@@ -427,15 +433,20 @@ function spawnMutation(options) {
             });
         }
         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,
             });
@@ -515,12 +526,16 @@ function spawnMutation(options) {
             }, 3_000);
         });
         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) => {
             settleOnce({ exitCode: code, timedOut, error: null, stdout, stderr });
@@ -682,10 +697,8 @@ function annotateNpmTooLow(result, options) {
         pushLine(options.task, line);
     return { ...result, stderr: `${result.stderr}\n${line}`, error: result.error ? `${result.error}\n${line}` : line };
 }
-/** 包在 registry 不存在（404）→ 用官方源复查一次，把「作者依赖缺失/包被删」与「本机镜像源滞后」
- *  分开（两者的提示与去向不同：前者引导投作者、后者只提示换源）。检测逻辑在独立的
- *  registry-check.ts；这里之所以是异步，是因为要联网查官方 registry —— 只在安装失败且日志含 404
- *  时发生，代价可忽略。 */
+/** 安装失败且日志含 404 时，用官方源复查一次并注入标记（逻辑见 registry-check.ts）。
+ *  异步是因为要联网；只在失败路径上发生。 */
 async function annotateRegistryMissing(result, options) {
     if (options.action === 'remove' || result.exitCode === 0 || result.timedOut)
         return result;
@@ -698,6 +711,18 @@ async function annotateRegistryMissing(result, options) {
         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, error) {
+    if (error?.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

package/lib/types/services/install/task-queue.d.ts

@@ -1,4 +1,4 @@
-import type { InstallResult, InstallTask } from './install-types.ts';
+import type { InstallResult, InstallTask, Invocation } from './install-types.ts';
 import type { LoaderHandle } from '../loader.ts';
 /** Snapshot of a task (keeps the live object untouched by consumers). */
 export declare function getTask(id: number): InstallTask | undefined;
@@ -78,6 +78,12 @@ export declare function verifyInstalledEntry(profile: string, target: string): {
     name: string | null;
     missing: string | null;
 };
+/**
+ * 宿主自身 CLI 调不起来时的 ASCII 标记行：spawn 我们解析出的宿主入口报 ENOENT 时返回
+ * `[host-spawn]`，供前端单独归因、不引导提 Issue。PATH 上的 dsh/npm 各有自己的标记，返回 null。
+ * 导出供单测覆盖判据。
+ */
+export declare function hostSpawnMarker(invocation: Invocation, error: unknown): string | null;
 /**
  * Run a plugin mutation with one recovery path: when `add` fails because
  * pnpm's allowBuilds gate blocks a build script — either the git-hosted

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-plugin",
-  "version": "1.6.11",
+  "version": "1.6.12",
   "description": "A community plugin marketplace for DeepSeek Harness, built to the official plugin spec — browse, search and install 10000+ human-curated community plugins without leaving the app. · DeepSeek Harness 社区插件市场（遵循官方开发规范）：10000+ 人工精选社区插件，每日更新。",
   "type": "module",
   "main": "lib/index.js",

package/src/client/components/PluginHubSection.tsx

@@ -27,7 +27,7 @@ import { HubUpdateModal } from './modals/HubUpdateModal.tsx'
 import { InstalledDetailModal } from './modals/InstalledDetailModal.tsx'
 import { NotificationsModal } from './modals/NotificationsModal.tsx'
 import { addFailure, addSuccess, addUpdateNotice, clearNotifications, ignoreUpdate, loadIgnoredUpdates, loadNotifications, removeNotification, removeUpdateNotice } from '../logic/failures.ts'
-import type { NotificationRecord } from '../logic/failures.ts'
+import type { FailureAction, NotificationRecord } from '../logic/failures.ts'
 import { CatalogHeader } from './layout/CatalogHeader.tsx'
 import { MarketView } from './views/MarketView.tsx'
 import { SectionTabs } from './layout/SectionTabs.tsx'
@@ -114,8 +114,8 @@ export function PluginHubSection({ t: _hostT, locale }: SectionProps) {
   const [uninstallNeedsReload, setUninstallNeedsReload] = useState(false)
   /** 结果视图「立即重启」：请求宿主重启后进入等待，服务回来后整页刷新 */
   const [restarting, setRestarting] = useState(false)
-  /** 操作失败完整信息 + 所属插件仓库 + 失败类型（决定弹窗标题「安装失败/卸载失败」）+ 实际执行的安装命令 + 尝试过的安装方式（issue 预填用） */
-  const [errorMsg, setErrorMsg] = useState<{ message: string; repo: string | null; kind: 'install' | 'uninstall'; command?: string; attempts?: string[] } | null>(null)
+  /** 操作失败信息 + 归属仓库 + 动作（决定弹窗标题与上报措辞）+ 命令与尝试记录（issue 预填用） */
+  const [errorMsg, setErrorMsg] = useState<{ message: string; repo: string | null; action: FailureAction; command?: string; attempts?: string[] } | null>(null)
   /** 通知中心记录：localStorage 持久化，每次安装/卸载任务成败都留痕（启动时读回） */
   const [notifications, setNotifications] = useState<NotificationRecord[]>(() => loadNotifications())
   /** 通知中心弹窗：一级导航「设置」tab 后边的铃铛入口按钮打开 */
@@ -173,7 +173,8 @@ export function PluginHubSection({ t: _hostT, locale }: SectionProps) {
       // 提 Issue 目标先反查仓库身份：npm 包名能在已安装表/目录里反查到 owner/repo 才保留，
       // 反查不到置 null —— 错误弹窗据此不显示「一键提 Issue」按钮（防提到错误仓库）
       const issueRepo = issueRepoOf(repo ?? '', catalog.installedItems, catalog.plugins)
-      setErrorMsg({ message, repo: issueRepo, kind, command, attempts })
+      // 动作：更新失败要显示「更新失败」，其余按安装/卸载
+      setErrorMsg({ message, repo: issueRepo, action: update ? 'update' : kind, command, attempts })
       // 失败自动写入通知记录：任务在后台结束时没人盯着也能留痕。
       // 存原始 repo（可能只是裸包名）而非反查结果 —— 反查只服务于提 Issue，
       // 通知中心的展示反查由 NotificationsModal 做、查不到会回退显示原始值，
@@ -793,7 +794,7 @@ export function PluginHubSection({ t: _hostT, locale }: SectionProps) {
     errorMsg && h(ErrorModal, {
       message: errorMsg.message,
       repo: errorMsg.repo,
-      kind: errorMsg.kind,
+      action: errorMsg.action,
       command: errorMsg.command,
       attempts: errorMsg.attempts,
       t,

package/src/client/components/modals/NotificationsModal.tsx

@@ -18,7 +18,7 @@ import type { MouseEvent } from 'react'
 import styles from '../../styles/Modal.module.css'
 import type { EnvInfo, Translate } from '../../types.ts'
 import type { NotificationRecord } from '../../logic/failures.ts'
-import { classifyFailure, missingRegistryPackageOf, npmTooLowVersion, pnpmPolicyHintOf, pnpmPolicyHintParams, registryMissingHintOf, unreachableTargetOf, registryHostOf } from '../../logic/failures.ts'
+import { actionOfRecord, classifyFailure, missingRegistryPackageOf, npmTooLowVersion, pnpmPolicyHintOf, pnpmPolicyHintParams, registryMissingHintOf, unreachableTargetOf, registryHostOf } from '../../logic/failures.ts'
 import type { PendingRestart, QueueTask } from '../../hooks/useTaskQueue.ts'
 import { pluginIssueUrl, pluginSiteUrl, hubIssueUrl } from '../../logic/urls.ts'
 import { CloseIcon } from '../ui/icons.tsx'
@@ -255,6 +255,9 @@ export function NotificationsModal({ records, tasks, pendingRestarts, t, env, on
                   // 卡片不展示错误日志预览，完整日志靠「复制完整日志」按钮带走，避免每条卡片被日志撑高
                   !r.ok && (() => {
                     const kind = classifyFailure(r.message)
+                    // 动作词：该条提示与上报正文按真实动作取词
+                    const action = actionOfRecord(r)
+                    const actionWord = t(action === 'uninstall' ? 'actionUninstall' : action === 'update' ? 'actionUpdate' : 'actionInstall')
                     if (kind === 'npmTooOld') {
                       // npm 内部崩溃（edgesOut）＋ 本机 npm 版本过低：npm 自身已知缺陷，不是插件问题 ——
                       // 直接给升级指引，不引导提 Issue
@@ -324,7 +327,7 @@ export function NotificationsModal({ records, tasks, pendingRestarts, t, env, on
                         h('div', { className: styles.failPrepareHint }, t('failPluginMissingDepHint')),
                         r.repo && shownRepo ? h('a', {
                           className: styles.failBigIssue,
-                          href: pluginIssueUrl(shownRepo, r.message, env, r.command, r.attempts),
+                          href: pluginIssueUrl(shownRepo, r.message, env, r.command, r.attempts, action),
                           target: '_blank',
                           rel: 'noopener noreferrer',
                           title: t('failIssueHint'),
@@ -373,7 +376,7 @@ export function NotificationsModal({ records, tasks, pendingRestarts, t, env, on
                         // registry 被指向内网/自定义源（tarball 从非官方源下载失败）：直接给出换源指引，
                         // 否则用户外网是通的会困惑「为什么连不上」
                         (() => { const host = registryHostOf(r.message); return host ? h('div', { className: styles.failPrepareHint }, t('failNetworkRegistryHint', { host })) : null })(),
-                        h('div', { className: styles.failPrepareHint }, t('failNetworkHint')),
+                        h('div', { className: styles.failPrepareHint }, t('failNetworkHint', { action: actionWord })),
                         onRunDiagnostics ? h('button', {
                           className: styles.failDiagBtn,
                           onClick: onRunDiagnostics,
@@ -387,7 +390,7 @@ export function NotificationsModal({ records, tasks, pendingRestarts, t, env, on
                         h('div', { className: styles.failPrepareHint }, /\[packaging\]/i.test(r.message) ? t('failPackagingHint') : t('failPrepareHint')),
                         r.repo && shownRepo ? h('a', {
                           className: styles.failBigIssue,
-                          href: pluginIssueUrl(shownRepo, r.message, env, r.command, r.attempts),
+                          href: pluginIssueUrl(shownRepo, r.message, env, r.command, r.attempts, action),
                           target: '_blank',
                           rel: 'noopener noreferrer',
                           title: t('failIssueHint'),
@@ -398,7 +401,7 @@ export function NotificationsModal({ records, tasks, pendingRestarts, t, env, on
                           h('div', { className: styles.failPrepareHint }, t('failMisjudgeHint')),
                           h('a', {
                             className: styles.failMisjudgeLink,
-                            href: hubIssueUrl(shownRepo, r.message, env, r.command, r.attempts, 'misjudge'),
+                            href: hubIssueUrl(shownRepo, r.message, env, r.command, r.attempts, 'misjudge', action),
                             target: '_blank',
                             rel: 'noopener noreferrer',
                             title: t('failHubIssueHint'),
@@ -409,7 +412,7 @@ export function NotificationsModal({ records, tasks, pendingRestarts, t, env, on
                     if (kind === 'hubState') {
                       // 插件中心的列表状态已过期（安装器自身守卫消息）：非插件问题、也不是 bug，只给可行动提示，不引导提 Issue
                       return h('div', null, [
-                        h('div', { className: styles.failPrepareHint }, t('failHubStateHint')),
+                        h('div', { className: styles.failPrepareHint }, t('failHubStateHint', { action: actionWord })),
                       ])
                     }
                     if (kind === 'timeout') {
@@ -421,17 +424,23 @@ export function NotificationsModal({ records, tasks, pendingRestarts, t, env, on
                     if (kind === 'profileLock') {
                       // DSH 写 profile 的锁超时（同一 profile 被别的 dsh/安装任务占着）：只给可行动提示，不引导提 Issue
                       return h('div', null, [
-                        h('div', { className: styles.failPrepareHint }, t('failProfileLockHint')),
+                        h('div', { className: styles.failPrepareHint }, t('failProfileLockHint', { action: actionWord })),
+                      ])
+                    }
+                    if (kind === 'hostCliSpawn') {
+                      // 宿主自身入口起不来：环境问题，给提示、不引导提 Issue
+                      return h('div', null, [
+                        h('div', { className: styles.failPrepareHint }, t('failHostCliSpawnHint')),
                       ])
                     }
                     // pnpm allowBuilds 拦截与未知失败：不归到插件作者，改为引导到插件中心仓库排查
                     return h('div', null, [
                       kind === 'pnpmIgnoredBuild'
                         ? h('div', { className: styles.failPrepareHint }, t('failIgnoredBuild'))
-                        : h('div', { className: styles.failPrepareHint }, t('failUnclassifiedHint')),
+                        : h('div', { className: styles.failPrepareHint }, t('failUnclassifiedHint', { action: actionWord })),
                       h('a', {
                         className: styles.failBigIssue,
-                        href: hubIssueUrl(shownRepo || r.repo, r.message, env, r.command, r.attempts),
+                        href: hubIssueUrl(shownRepo || r.repo, r.message, env, r.command, r.attempts, 'triage', action),
                         target: '_blank',
                         rel: 'noopener noreferrer',
                         title: t('failHubIssueHint'),

package/src/client/components/modals/modals.tsx

@@ -18,6 +18,7 @@ import { ProgressView } from './ProgressView.tsx'
 import { installCommandOf } from '../../logic/install-command.ts'
 import { pluginDetailUrl, pluginIssueUrl, pluginSiteUrl, hubIssueUrl } from '../../logic/urls.ts'
 import { classifyFailure, missingRegistryPackageOf, npmTooLowVersion, pnpmPolicyHintOf, pnpmPolicyHintParams, registryMissingHintOf, unreachableTargetOf, registryHostOf } from '../../logic/failures.ts'
+import type { FailureAction } from '../../logic/failures.ts'
 
 /** 完成结果视图：绿色对勾 + 标题/描述；
  *  终态只有两种：
@@ -336,12 +337,11 @@ export function UninstallModal(props: UninstallModalProps) {
   )
 }
 
-/** 预填插件仓库的 GitHub Issue 链接：标题带插件名，正文附完整错误信息，方便用户一键反馈。 */
-/** 安装/卸载失败弹窗：布局与失败记录一致（类型徽标 + 仓库超链接 + 隐蔽复制按钮），报错完整展示，底部一键提交 Issue。 */
-export function ErrorModal({ message, repo, kind, command, attempts, t, env, onCopy, onClose, onRunDiagnostics }: {
+/** 安装/更新/卸载失败弹窗：标题、徽标、提示文案与 issue 正文都按传入的动作取词。 */
+export function ErrorModal({ message, repo, action, command, attempts, t, env, onCopy, onClose, onRunDiagnostics }: {
   message: string
   repo: string | null
-  kind: 'install' | 'uninstall'
+  action: FailureAction
   command?: string
   /** 尝试过的安装方式（npm 反查 + 实际执行命令）：issue 预填一并贴给作者，便于反推正确的 npm 包名 */
   attempts?: string[]
@@ -354,6 +354,8 @@ export function ErrorModal({ message, repo, kind, command, attempts, t, env, onC
 }) {
   // 失败归类：当前安装通道（npm/git）装不上 = 插件分发/依赖的问题，一律引导提 Issue
   const failureKind = classifyFailure(message)
+  // 动作词：标题、徽标与提示里的 {action} 统一取这一个词
+  const actionWord = t(action === 'uninstall' ? 'actionUninstall' : action === 'update' ? 'actionUpdate' : 'actionInstall')
   // 服务端 [npm-too-low] 标记里带的本机 npm 版本（无标记为 null，提示文案降级为「怀疑」）
   const npmVersion = npmTooLowVersion(message)
   // 复制完整错误：实际执行/尝试过的安装命令（如有）+ 完整错误正文。
@@ -372,8 +374,9 @@ export function ErrorModal({ message, repo, kind, command, attempts, t, env, onC
   },
     h('div', { className: styles.errorModal, role: 'dialog', 'aria-modal': 'true' },
       h('div', { className: styles.modalHead },
-        // 标题按操作类型明确区分：安装失败 / 卸载失败
-        h('div', { className: styles.errorTitle }, kind === 'install' ? t('errorTitleInstall') : t('errorTitleUninstall')),
+        // 标题按动作明确区分：安装失败 / 更新失败 / 卸载失败
+        h('div', { className: styles.errorTitle },
+          t(action === 'uninstall' ? 'errorTitleUninstall' : action === 'update' ? 'errorTitleUpdate' : 'errorTitleInstall')),
         h('button', {
           className: styles.modalClose,
           'aria-label': t('errorClose'),
@@ -385,8 +388,8 @@ export function ErrorModal({ message, repo, kind, command, attempts, t, env, onC
         h('div', { className: styles.failRow },
           h('div', { className: styles.failHead },
             h('span', {
-              className: kind === 'install' ? styles.failKindInstall : styles.failKindUninstall,
-            }, kind === 'install' ? t('install') : t('uninstall')),
+              className: action === 'install' ? styles.failKindInstall : styles.failKindUninstall,
+            }, actionWord),
             // 仓库地址（用户名/仓库）统一显示为可点击超链接，跳转到官网详情页（含插件收录信息），而非直接跳 GitHub
             repo ? h('a', {
               className: styles.failRepo,
@@ -458,7 +461,7 @@ export function ErrorModal({ message, repo, kind, command, attempts, t, env, onC
                 h('div', { className: styles.failPrepareHint }, t('failPluginMissingDepHint')),
                 repo ? h('a', {
                   className: styles.failBigIssue,
-                  href: pluginIssueUrl(repo, message, env, command, attempts),
+                  href: pluginIssueUrl(repo, message, env, command, attempts, action),
                   target: '_blank',
                   rel: 'noopener noreferrer',
                   title: t('failIssueHint'),
@@ -498,7 +501,7 @@ export function ErrorModal({ message, repo, kind, command, attempts, t, env, onC
                 // registry 被指向内网/自定义源（tarball 从非官方源下载失败）：直接给出换源指引，
                 // 否则用户外网是通的会困惑「为什么连不上」
                 (() => { const host = registryHostOf(message); return host ? h('div', { className: styles.failPrepareHint }, t('failNetworkRegistryHint', { host })) : null })(),
-                h('div', { className: styles.failPrepareHint }, t('failNetworkHint')),
+                h('div', { className: styles.failPrepareHint }, t('failNetworkHint', { action: actionWord })),
                 onRunDiagnostics ? h('button', {
                   className: styles.failDiagBtn,
                   onClick: onRunDiagnostics,
@@ -511,7 +514,7 @@ export function ErrorModal({ message, repo, kind, command, attempts, t, env, onC
                 h('div', { className: styles.failPrepareHint }, /\[packaging\]/i.test(message) ? t('failPackagingHint') : t('failPrepareHint')),
                 repo ? h('a', {
                   className: styles.failBigIssue,
-                  href: pluginIssueUrl(repo, message, env, command, attempts),
+                  href: pluginIssueUrl(repo, message, env, command, attempts, action),
                   target: '_blank',
                   rel: 'noopener noreferrer',
                   title: t('failIssueHint'),
@@ -523,7 +526,7 @@ export function ErrorModal({ message, repo, kind, command, attempts, t, env, onC
                   h('div', { className: styles.failPrepareHint }, t('failMisjudgeHint')),
                   h('a', {
                     className: styles.failMisjudgeLink,
-                    href: hubIssueUrl(repo, message, env, command, attempts, 'misjudge'),
+                    href: hubIssueUrl(repo, message, env, command, attempts, 'misjudge', action),
                     target: '_blank',
                     rel: 'noopener noreferrer',
                     title: t('failHubIssueHint'),
@@ -533,7 +536,7 @@ export function ErrorModal({ message, repo, kind, command, attempts, t, env, onC
               : failureKind === 'hubState'
               ? h('div', null, [
                 // 插件中心的列表状态已过期（安装器自身守卫消息）：不是插件问题、也不是 bug，只给可行动提示，不引导提 Issue
-                h('div', { className: styles.failPrepareHint }, t('failHubStateHint')),
+                h('div', { className: styles.failPrepareHint }, t('failHubStateHint', { action: actionWord })),
               ])
               : failureKind === 'timeout'
               ? h('div', null, [
@@ -543,16 +546,21 @@ export function ErrorModal({ message, repo, kind, command, attempts, t, env, onC
               : failureKind === 'profileLock'
               ? h('div', null, [
                 // DSH 写 profile 的锁超时（同一 profile 被别的 dsh/安装任务占着）：给可行动提示，不引导提 Issue
-                h('div', { className: styles.failPrepareHint }, t('failProfileLockHint')),
+                h('div', { className: styles.failPrepareHint }, t('failProfileLockHint', { action: actionWord })),
+              ])
+              : failureKind === 'hostCliSpawn'
+              ? h('div', null, [
+                // 宿主自身入口起不来：环境问题，给提示、不引导提 Issue
+                h('div', { className: styles.failPrepareHint }, t('failHostCliSpawnHint')),
               ])
               : h('div', null, [
                 // pnpm allowBuilds 拦截与未知失败：不归到插件作者，改为引导到插件中心仓库排查
                 failureKind === 'pnpmIgnoredBuild'
                   ? h('div', { className: styles.failPrepareHint }, t('failIgnoredBuild'))
-                  : h('div', { className: styles.failPrepareHint }, t('failUnclassifiedHint')),
+                  : h('div', { className: styles.failPrepareHint }, t('failUnclassifiedHint', { action: actionWord })),
                 h('a', {
                   className: styles.failBigIssue,
-                  href: hubIssueUrl(repo, message, env, command, attempts),
+                  href: hubIssueUrl(repo, message, env, command, attempts, 'triage', action),
                   target: '_blank',
                   rel: 'noopener noreferrer',
                   title: t('failHubIssueHint'),

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} —— 你的网络连接不通',
@@ -722,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',
@@ -733,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
@@ -749,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',

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' | 'pluginMissingDep' | '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,10 +249,7 @@ export function classifyFailure(message: string): FailureKind {
   // 装后校验发现入口文件缺失（[packaging]）= git 分发缺构建产物
   if (/\[packaging\]|entry file missing/i.test(message)) return 'pluginPrepare'
   // registry 上不存在的依赖（404），profile 任何安装都会卡在这条。必须在 pluginPrepare 之前判
-  // 官方源复核结论：缺的包在官方 registry 上也不存在，且不是本机 profile 声明的残留依赖 →
-  // 该包来自插件的依赖树，属**作者侧**问题（依赖没发布/已被删除）。标记由服务端联网复查后注入。
-  // 必须排在 pnpmMissingDep 之前 —— 日志里同样含 ERR_PNPM_FETCH_404，靠标记区分「作者的锅」
-  // 与「本机 profile 残留依赖（#73）/ 镜像源滞后」。
+  // [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 之前判
@@ -257,12 +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'
-  // 宿主 DSH 自己的 allowBuilds 摘要行（#210）：新版宿主把 pnpm 报错只写进 diagnostics 日志文件，
-  // 终端里只留这一句「git-hosted plugins build … add the exact key … then re-run」，日志里因此
-  // 一条原始 ERR_PNPM_* 码都没有 —— 只能靠这句话识别为「构建脚本被白名单拦截」。
-  // 摆放位置在一切错误码分支之后：日志里真有 ERR_PNPM_PREPARE_PACKAGE / ERR_PNPM_IGNORED_BUILDS
-  // 时（构建确实跑挂、或不带摘要的旧宿主），仍以原始报错为准，不会被这句摘要改写。
+  // 宿主自己的 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'
 }