dsh-plugin 1.6.8 → 1.6.9

package/lib/http/diagnostics.js

@@ -42,16 +42,34 @@ function hostDshVersion() {
     }
     return null;
 }
+/** 从命令输出里抽出版本号本体：pnpm/npm 直接打印 `11.7.0`，而 `git --version` 打印
+ *  `git version 2.55.0.windows.5` —— 原样取首行会让 issue 正文（统一再加 `v` 前缀）拼成
+ *  `vgit version 2.55.0.windows.5`。只取版本号，顺带兼容 `v1.2.3` 这类自带前缀的输出。 */
+function versionOf(output) {
+    const first = output.trim().split(/\r?\n/)[0]?.trim() ?? '';
+    if (!first)
+        return null;
+    const match = /\d+\.\d+[0-9A-Za-z.\-+]*/.exec(first);
+    return match === null ? null : match[0];
+}
 /** 探测命令行工具的版本号（pnpm --version / npm --version / git --version）：
  *  未安装 / 不在 PATH / 超时一律返回 null —— issue 环境快照如实写 unknown，绝不挂起。
- *  （同步探测仅用于启动期/请求期的低频率 /env 快照，安装通道不经过这里。） */
+ *  （同步探测仅用于启动期/请求期的低频率 /env 快照，安装通道不经过这里。）
+ *
+ *  Windows 上 pnpm/npm 是 .cmd shim，不带 shell 的 spawnSync 起不来 —— 上报的 issue 里
+ *  因此长期是 `pnpm: unknown` / `npm: unknown`，而 pnpm 版本恰恰是 allowBuilds 那类问题的
+ *  关键信息（门禁行为随版本变）。故 win32 走 shell 让 cmd 解析 shim；参数是固定的
+ *  `--version`，没有注入面。 */
 function toolVersion(cmd, args) {
     try {
-        const r = spawnSync(cmd, args, { timeout: 1500, encoding: 'utf8' });
+        const r = spawnSync(cmd, args, {
+            timeout: 1500,
+            encoding: 'utf8',
+            shell: process.platform === 'win32',
+        });
         if (r.error || r.status !== 0)
             return null;
-        const v = (r.stdout ?? '').trim().split(/\r?\n/)[0];
-        return v || null;
+        return versionOf(r.stdout ?? '');
     }
     catch {
         return null;

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

@@ -526,6 +526,9 @@ function spawnMutation(options) {
         });
     });
     return (async () => {
+        // 超时复核用基线：本次任务开始前目标是否已在 profile 里。已安装的话，超时后核对无法区分
+        // 「旧版本还在」与「刚装上」，那种情形（更新超时）不冒认成功。
+        const wasInstalled = action !== 'remove' && !isGlobalNpm && verifyInstalledEntry(profile, target).name !== null;
         let result = await spawnOnce(args);
         // npm 11 的 arborist peer-set bug（`Cannot read properties of null (reading 'children')`）
         // 会让 `npm install -g` 在解析阶段直接崩溃。首次失败后自动带 `--legacy-peer-deps` 重试一次：
@@ -539,6 +542,17 @@ function spawnMutation(options) {
                 pushLine(task, '[npm] peer-set resolution crashed npm (known npm bug) — retrying with --legacy-peer-deps');
             result = await spawnOnce(retryArgs);
         }
+        // 超时被强杀 ≠ 没装上：命中的安装可能已经落盘（日志里 pnpm 已打印 Done，只是 dsh 进程迟迟不退出
+        // 而被我们超时掐掉）。判失败之前先复核 profile —— 目标已在依赖里、且声明分发的入口文件都在，
+        // 就按成功收尾，避免「其实装好了却报安装失败」并被自动归档成未知失败。
+        if (result.timedOut && !wasInstalled && action !== 'remove' && !isGlobalNpm && task?.status !== 'cancelled') {
+            const verified = verifyInstalledEntry(profile, target);
+            if (verified.name !== null && verified.missing === null) {
+                result = { ...result, timedOut: false, exitCode: 0, error: null };
+                if (task)
+                    pushLine(task, '[timeout] the install had already completed — treating it as a success');
+            }
+        }
         // 统一终态后处理：exitCode/status/needsRestart 以最后一次尝试为准
         if (task) {
             task.exitCode = result.exitCode;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-plugin",
-  "version": "1.6.8",
+  "version": "1.6.9",
   "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

@@ -651,8 +651,8 @@ export function PluginHubSection({ t: _hostT, locale }: SectionProps) {
       langPath,
       restarting,
       update: confirmIsUpdate,
-      // 仅命令行插件（webInstallable=false）：弹窗只展示命令供复制，不提供一键安装
-      cliOnly: confirmPlugin.install?.webInstallable === false,
+      // 仅命令行插件（webInstallable=false / 人工干预 manualInstall）：弹窗只展示命令供复制，不提供一键安装
+      cliOnly: confirmPlugin.install?.webInstallable === false || confirmPlugin.install?.manualInstall === true,
       submitting: queue.submitting,
       needsRestart: installNeedsRestart,
       needsReload: installNeedsReload,

package/src/client/components/catalog/PluginCard.tsx

@@ -89,9 +89,9 @@ export function PluginCard({ plugin: p, copied, installedName, installedVersion,
                 disabled: true,
                 title: t('installed'),
               }, t('installed')))
-            // 未安装：按钮恒为「安装」，点击先弹信任确认；AI 识别为「可能需要命令行辅助」
-            // 的插件（webInstallable=false）不拦截，允许尝试一键安装，弹窗内会给出提示与
-            // 复制命令通道，安装失败时引导去 dsh 终端手动执行
+            // 未安装：按钮恒为「安装」，点击先弹信任确认；需在终端手动安装的插件
+            //（webInstallable=false）按钮不额外变形，但弹窗内只给提示与复制命令通道，
+            // 不提供一键安装按钮
             : h('button', {
               className: isCopied ? styles.installBtnCopied : styles.installBtn,
               // 文字恒定避免按钮宽度变化导致卡片跳动；点击先弹信任确认，

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

@@ -375,6 +375,18 @@ export function NotificationsModal({ records, tasks, pendingRestarts, t, env, on
                           rel: 'noopener noreferrer',
                           title: t('failIssueHint'),
                         }, t('failIssueBig')) : null,
+                        // 次要入口：这条分支的判据（[packaging] 预检/装后校验、prepare 摘要）是插件中心
+                        // 自己产出的，不是 pnpm 原文 —— 判错时用户会被送去作者仓库、我们永远收不到反馈
+                        r.repo && shownRepo ? h('div', null, [
+                          h('div', { className: styles.failPrepareHint }, t('failMisjudgeHint')),
+                          h('a', {
+                            className: styles.failMisjudgeLink,
+                            href: hubIssueUrl(shownRepo, r.message, env, r.command, r.attempts, 'misjudge'),
+                            target: '_blank',
+                            rel: 'noopener noreferrer',
+                            title: t('failHubIssueHint'),
+                          }, t('failMisjudgeLink')),
+                        ]) : null,
                       ])
                     }
                     if (kind === 'hubState') {
@@ -383,6 +395,12 @@ export function NotificationsModal({ records, tasks, pendingRestarts, t, env, on
                         h('div', { className: styles.failPrepareHint }, t('failHubStateHint')),
                       ])
                     }
+                    if (kind === 'timeout') {
+                      // 安装命令超时被强杀（日志里 pnpm 可能已 Done）：可能其实已装成功 —— 只给可行动提示，不引导提 Issue
+                      return h('div', null, [
+                        h('div', { className: styles.failPrepareHint }, t('failTimeoutHint')),
+                      ])
+                    }
                     // pnpm allowBuilds 拦截与未知失败：不归到插件作者，改为引导到插件中心仓库排查
                     return h('div', null, [
                       kind === 'pnpmIgnoredBuild'

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

@@ -193,8 +193,10 @@ export function InstallModal(props: InstallModalProps) {
           globalNpm !== undefined && globalNpm.length > 0
             ? h('div', { className: styles.cliOnlyHint }, t('globalNpmHint'))
             : null,
-          // AI 识别可能需要命令行辅助的插件（webInstallable=false）：提示但不拦截，仍允许尝试一键安装
-          cliOnly ? h('div', { className: styles.cliOnlyHint }, t('cliOnlyHint')) : null,
+          // 需在终端手动安装的插件（webInstallable=false）：按钮位只给提示与复制通道，不提供一键安装；
+          // 人工干预标记（manualInstall）另给一条更明确的终端引导
+          cliOnly ? h('div', { className: styles.cliOnlyHint },
+            t(plugin?.install?.manualInstall === true ? 'manualInstallOnlyHint' : 'cliOnlyHint')) : null,
           task && task.status === 'pending' ? h('div', { className: styles.queuedHint }, t('queuedHint')) : null,
           task ? h(ProgressView, { task }) : null,
           // 安装失败：引导用户复制上方命令到 dsh 终端手动安装（如 node-pty 等原生依赖构建脚本需人工放行）
@@ -496,12 +498,30 @@ export function ErrorModal({ message, repo, kind, command, attempts, t, env, onC
                   rel: 'noopener noreferrer',
                   title: t('failIssueHint'),
                 }, t('failIssueBig')) : null,
+                // 次要入口：这条分支的判据（[packaging] 预检/装后校验、prepare 摘要）是插件中心
+                // 自己产出的，不是 pnpm 原文 —— 判错时用户会被送去作者仓库、我们永远收不到反馈，
+                // 故另给一条「可能是市场误判」的反馈通道（正文自我说明它来自哪条分支）
+                repo ? h('div', null, [
+                  h('div', { className: styles.failPrepareHint }, t('failMisjudgeHint')),
+                  h('a', {
+                    className: styles.failMisjudgeLink,
+                    href: hubIssueUrl(repo, message, env, command, attempts, 'misjudge'),
+                    target: '_blank',
+                    rel: 'noopener noreferrer',
+                    title: t('failHubIssueHint'),
+                  }, t('failMisjudgeLink')),
+                ]) : null,
               ])
               : failureKind === 'hubState'
               ? h('div', null, [
                 // 插件中心的列表状态已过期（安装器自身守卫消息）：不是插件问题、也不是 bug，只给可行动提示，不引导提 Issue
                 h('div', { className: styles.failPrepareHint }, t('failHubStateHint')),
               ])
+              : failureKind === 'timeout'
+              ? h('div', null, [
+                // 安装命令超时被强杀（日志里 pnpm 可能已 Done）：可能其实已装成功 —— 给可行动提示，不引导提 Issue
+                h('div', { className: styles.failPrepareHint }, t('failTimeoutHint')),
+              ])
               : h('div', null, [
                 // pnpm allowBuilds 拦截与未知失败：不归到插件作者，改为引导到插件中心仓库排查
                 failureKind === 'pnpmIgnoredBuild'

package/src/client/locales.ts

@@ -30,8 +30,13 @@ export const zh = {
   failedDescProxy: '你的网络似乎不通，或设置里的 HTTP 代理地址不可达，无法获取插件目录数据。请检查代理设置与网络连接后重试；或点击右上角按钮在浏览器中打开插件市场。',
   retry: '重试',
   install: '安装',
-  // AI 识别可能需要命令行辅助的插件（webInstallable=false）：仍可尝试一键安装，失败时复制命令去 dsh 终端
-  cliOnlyHint: '此插件需在命令行安装（网页端无法代执行），请复制上方命令到终端运行',
+  // 需在终端手动安装的插件（webInstallable=false）：两种情形共用一句 —— 命令网页端代执行不了
+  //（npx 安装器 / 本地 link），或命令能跑但装机过程要在终端完成（仓库带 prepare 构建钩子、
+  // 需要装配子目录等）。措辞覆盖两者，不承诺"网页端一定能装"。
+  cliOnlyHint: '此插件的安装需要在 dsh 终端里完成（网页端无法代跑它所需的构建或装配步骤），请复制上方命令到终端执行',
+  // 人工干预标记（manualInstall）：安装要在终端里跑构建/分步装配，网页一键安装替不了终端。
+  // 注意 key 不能叫 manualInstallHint —— 那个是「已安装」页来源筛选的文案（目录插件 / 手动安装）
+  manualInstallOnlyHint: '此插件需要你在 dsh 终端手动安装：网页端的一键安装替代不了终端里的构建与装配步骤。请复制上方命令到终端执行（Windows 用 Git Bash 或 PowerShell，macOS/Linux 用终端），完整步骤见作者仓库的安装说明。',
   failedCopyHint: '安装失败。请复制上方安装命令到 dsh 终端手动执行（原生依赖构建脚本可能需要人工放行，如 pnpm approve-builds）',
   toastCopied: '安装命令已复制，去 dsh 终端粘贴即可安装',
   installed: '已安装',
@@ -317,12 +322,18 @@ export const zh = {
   failUnclassifiedHint: '安装失败，原因未能自动识别。这通常不是插件自身的问题（可能与本机环境或插件中心有关），请将错误信息反馈给插件中心，由维护者排查。',
   // 插件中心自身状态类消息（插件未安装 / 不在此处卸载 / 已在队列中）：已安装列表与实读快照不同步，非插件问题，不引导提 Issue
   failHubStateHint: '插件列表状态已过期或与本地不一致：该插件可能已经装过了（无需重复安装，要升级请点「更新」），也可能已不在已安装列表中，或已在队列中。这不是插件本身的问题 —— 请刷新页面后重试。',
+  // 安装命令超时被强杀：可能其实已装成功（安装器超时后会先核对已安装列表），给可行动提示，不引导提 Issue
+  failTimeoutHint: '安装耗时超过本地上限、已被中断 —— 但很可能其实已经装上了（安装器在超时后会先核对本地已安装列表）。请刷新页面确认该插件是否已装上；若确实没装上，可在终端手动执行一次安装命令查看完整输出。这不是插件本身的问题。',
   // prepare 构建脚本实际执行失败（git 分发缺子模块/构建产物）：插件打包分发问题，应提 Issue
   failPrepareHint: '该插件安装时的构建脚本执行失败（git 分发常缺失子模块或构建产物），属插件打包分发问题。请向作者仓库提交 Issue 反馈。',
+  // 「插件打包问题」分支的次要入口：该判据由插件中心自己的预检/装后校验产出（不是 pnpm 原文），
+  // 一旦误报，用户会被引导去作者仓库、插件中心永远收不到反馈 —— 故留一条反馈路径
+  failMisjudgeHint: '如果这个插件其实能正常安装（上面这个判定是插件中心误报的），请反馈给插件中心：文字提示里的判据由市场自身产出，误报只有靠你的反馈才能被发现。',
+  failMisjudgeLink: '插件能装却被拦下？反馈给插件中心',
   // 安装前预检 / 装后校验拦截（[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 脚本）。这不一定是插件自身的问题（也可能是插件中心反查失败后回退到 git 安装所致），请先反馈给插件中心排查；若确认为插件依赖问题，可建议作者改用预编译版本（如 node-pty-prebuilt-multiarch）或移除安装期构建。',
+  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',
@@ -428,9 +439,13 @@ export const en = {
   failedDescProxy: 'Your network seems unreachable, or the HTTP proxy in Settings is unreachable, so the plugin catalog could not be loaded. Please check the proxy address and your connection, then retry; or open the hub in your browser with the button above.',
   retry: 'Retry',
   install: 'Install',
-  // AI-flagged plugins that may need command-line help (webInstallable=false): one-click install still allowed,
-  // on failure the user is guided to copy the command into the dsh terminal
-  cliOnlyHint: 'This plugin must be installed from the command line (it cannot be run from the web UI) — copy the command above and run it in your terminal',
+  // Plugins that must be installed by hand (webInstallable=false): one wording for both cases —
+  // the web UI cannot run the command at all (npx installers, local links), or it can run it but
+  // the install needs terminal-side work (repos with a prepare build hook, sub-directory assembly).
+  cliOnlyHint: 'This plugin has to be installed in your dsh terminal (the web UI cannot run the build or assembly steps it needs) — copy the command above and run it there',
+  // Manual-intervention flag (manualInstall): the install needs a build / step-by-step assembly in the terminal.
+  // The key cannot be manualInstallHint — that one is the source filter on the Installed page.
+  manualInstallOnlyHint: 'This plugin has to be installed by hand in your dsh terminal — one-click install from the web UI cannot run the build and assembly steps it needs. Copy the command above and run it there (Git Bash or PowerShell on Windows, Terminal on macOS/Linux); the author\'s repo has the full steps.',
   failedCopyHint: 'Install failed. Copy the command above and run it manually in your dsh terminal (native build scripts may need manual approval, e.g. pnpm approve-builds)',
   toastCopied: 'Install command copied — paste it in your dsh terminal',
   installed: 'Installed',
@@ -717,12 +732,19 @@ export const en = {
   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.',
   // 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.',
   // 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
+  // pre/post-install check, not from pnpm output — a false positive sends users to the author
+  // repo and the hub never hears about it, so keep a feedback path here.
+  failMisjudgeHint: 'If this plugin actually installs fine (the verdict above is the Plugin Hub misjudging it), please report it to the Hub: that verdict is produced by the marketplace itself, so a false positive can only be found through your feedback.',
+  failMisjudgeLink: 'Plugin installs fine but got blocked? Report to the Plugin Hub',
   // 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 its dependencies) needs to run build scripts, 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). This is not necessarily the plugin itself (it may be caused by the hub falling back to a git install after npm lookup failed). Please report it to the Plugin Hub first; if it turns out to be a plugin dependency issue, the author can ship a prebuilt variant (e.g. node-pty-prebuilt-multiarch) or drop install-time builds.',
+  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.',
   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

package/src/client/logic/failures.ts

@@ -151,7 +151,7 @@ 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' | 'hub'
+export type FailureKind = 'npmTooOld' | 'dshMissing' | 'gitMissing' | 'pnpmMissing' | 'npmMissing' | 'pnpmStore' | 'pnpmWorkspace' | 'originRejected' | 'pnpmPolicy' | 'pnpmUnusedPatch' | 'pnpmMissingDep' | 'registryVersionStale' | 'pnpmLinkedDirMissing' | 'fileLocked' | 'accessDenied' | 'fsUnavailable' | 'pnpmIgnoredBuild' | 'pluginPrepare' | 'network' | 'hubState' | 'timeout' | 'hub'
 
 /** Match the pnpm error code, not a generic mention of checksum or integrity. */
 function missingTarballIntegrity(message: string): boolean {
@@ -244,6 +244,10 @@ export function classifyFailure(message: string): FailureKind {
   // already installed 只认「整行就是它」的短形态（旧版本守卫留下的历史记录）；带「——」说明的
   // 包名冲突另有处置，不能按状态不同步提示。
   if (/plugin is not installed|plugin cannot be uninstalled here|already queued:|^already installed: \S+$/im.test(message)) return 'hubState'
+  // 安装器自己的超时标记（命令跑满上限被强杀）：既不是插件问题、也不是用户环境问题，而且很可能是
+  // 「其实已经装上了」——摆放位置在一切错误码分支之后，日志里真有 pnpm 报错时仍以真实报错为准。
+  // 单独归类，给「刷新确认是否已安装」这类可行动提示，不引导提 Issue。
+  if (/^\[timed out\]$/m.test(message)) return 'timeout'
   // 其余未知失败：引导到插件中心仓库排查
   return 'hub'
 }

package/src/client/logic/normalize.ts

@@ -29,10 +29,12 @@ export function normalize(raw: Record<string, unknown>): HubPlugin {
           }
           : undefined,
       // 安装信息：wi 仅在 false 时下发（缺省视为 true 可一键安装）；
+      // mi 仅在 true 时下发（人工干预：网页端替不了终端，只引导用户自己去终端装）；
       // ic/igc = 目录下发的权威安装命令（npm/git 通道各一条，CLI-only 插件如 dsh-tui 必须用）
-      install: raw.wi === false || typeof raw.ic === 'string' || typeof raw.igc === 'string'
+      install: raw.wi === false || raw.mi === true || typeof raw.ic === 'string' || typeof raw.igc === 'string'
         ? {
           webInstallable: raw.wi === false ? false : undefined,
+          manualInstall: raw.mi === true ? true : undefined,
           command: typeof raw.ic === 'string' ? raw.ic : undefined,
           githubCommand: typeof raw.igc === 'string' ? raw.igc : undefined,
         }

package/src/client/logic/urls.ts

@@ -64,6 +64,7 @@ function reasonTitleOf(kind: FailureKind): string {
     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 'hub': return 'install failed (cause unclassified)'
     default: return 'plugin install failed'
   }
@@ -190,11 +191,28 @@ export function pluginIssueUrl(repo: string, message: string, env?: EnvInfo | nu
  * 以及 pnpm allowBuilds 拦截这类不再归到插件作者的情形）。正文带上目标插件与完整
  * 错误摘要，供插件中心维护者分诊 —— 不再把环境问题/插件中心自身问题误投给插件作者。
  */
-export function hubIssueUrl(pluginRepo: string | null, message: string, env?: EnvInfo | null, command?: string, attempts?: string[]): string {
+export type HubIssueVariant =
+  /** 缺省：安装器主动把失败送到插件中心分诊（未分类兜底 / allowBuilds 门禁） */
+  | 'triage'
+  /** 从「插件打包问题」分支的次要入口提交：该判定由插件中心自己产出，用户怀疑是误报 */
+  | 'misjudge'
+
+export function hubIssueUrl(
+  pluginRepo: string | null,
+  message: string,
+  env?: EnvInfo | null,
+  command?: string,
+  attempts?: string[],
+  /** 见 HubIssueVariant；缺省 'triage'，既有正文保持不变 */
+  variant: HubIssueVariant = 'triage',
+): string {
   const kind = classifyFailure(message)
   const executed = executedCommandOf(command, attempts)
   const repo = pluginRepo && pluginRepo.trim() !== '' ? pluginRepo.trim() : 'unknown'
-  const title = `[dsh-plugin-hub] ${reasonTitleOf(kind)}: ${repo}`
+  const title = variant === 'misjudge'
+    // 标题就点明「可能是误判」，维护者一眼能区分它和未分类兜底
+    ? `[dsh-plugin-hub] possible misjudgment: ${repo}`
+    : `[dsh-plugin-hub] ${reasonTitleOf(kind)}: ${repo}`
   const code = coreErrorCode(message)
   const build = (coreChars: number): string => {
     const body = [
@@ -203,7 +221,15 @@ export function hubIssueUrl(pluginRepo: string | null, message: string, env?: En
       `- Target plugin: \`${repo}\``,
       ...(code ? [`- Key error: \`${code}\``] : []),
       // 为什么投递到这里而非插件仓库：只有确有证据是插件自身构建失败（pluginPrepare）才投插件仓库
-      '- 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.',
+      ...(variant === 'misjudge'
+        // 这条入口的判据（[packaging] 预检/装后校验、prepare 摘要）是插件中心自己产出的，
+        // 不是 pnpm 原文 —— 一旦我们自己误报，用户就被送去作者仓库、我们永远收不到反馈。
+        // 正文写清它来自哪条分支、判据是谁给的，维护者才不会把它当成未分类兜底。
+        ? [
+          '- Filed from: the plugin-prepare path (which normally routes to the plugin repo) — filed here because that verdict may be our own misjudgment.',
+          '- Source of that verdict: produced by dsh-plugin-hub\'s own pre/post-install check, not by pnpm output.',
+        ]
+        : ['- 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}) 插件市场的安装程序自动生成，随本次安装失败一并提交。`,

package/src/client/styles/Modal.module.css

@@ -1264,6 +1264,22 @@
   box-shadow: 0 3px 10px rgba(0, 0, 0, 0.12);
 }
 
+/* 「插件打包问题」分支的次要入口（可能是市场误判）：主按钮是去作者仓库，这条只在用户
+   怀疑我们判定有误时才用 —— 做成弱化的文字链接，不与主按钮抢注意力 */
+.failMisjudgeLink {
+  display: inline-block;
+  margin-top: 6px;
+  font-size: 12px;
+  line-height: 18px;
+  color: var(--hub-text-tertiary);
+  text-decoration: underline;
+  cursor: pointer;
+}
+
+.failMisjudgeLink:hover {
+  color: var(--hub-text-secondary);
+}
+
 /* 网络类失败弹窗的「无法访问 …」醒目行：红色加粗，直接告诉用户具体哪个地址连不上
    （URL 较长允许换行断词），与下方琥珀色说明区分主次 */
 .failNetworkTarget {

package/src/client/types.ts

@@ -59,10 +59,11 @@ export interface HubPlugin {
   description?: string
   source?: { repo?: string; npmPackage?: string }
   /** 安装信息：能否网页一键安装（false = 仅支持命令行/专属 profile，缺省视为 true）；
+   *  manualInstall = 人工干预标记（网页端一键安装替代不了终端的构建/装配，必须用户自己去终端装）；
    *  command/githubCommand = 目录下发的权威安装命令（npm/git 通道各一条），
    *  仅供展示/复制 —— CLI-only 插件（如 dsh-tui）需专属 profile（--profile dsh-tui），
    *  无法从 repo/npm 包名推断，必须用目录命令。 */
-  install?: { webInstallable?: boolean; command?: string; githubCommand?: string }
+  install?: { webInstallable?: boolean; manualInstall?: boolean; command?: string; githubCommand?: string }
   compatibility?: { status?: string }
   dates?: { repoUpdatedAt?: string; addedAt?: string }
   stats?: { stargazers_count?: number; forks_count?: number }

package/src/server/http/diagnostics.ts

@@ -40,15 +40,33 @@ function hostDshVersion(): string | null {
   return null
 }
 
+/** 从命令输出里抽出版本号本体：pnpm/npm 直接打印 `11.7.0`，而 `git --version` 打印
+ *  `git version 2.55.0.windows.5` —— 原样取首行会让 issue 正文（统一再加 `v` 前缀）拼成
+ *  `vgit version 2.55.0.windows.5`。只取版本号，顺带兼容 `v1.2.3` 这类自带前缀的输出。 */
+function versionOf(output: string): string | null {
+  const first = output.trim().split(/\r?\n/)[0]?.trim() ?? ''
+  if (!first) return null
+  const match = /\d+\.\d+[0-9A-Za-z.\-+]*/.exec(first)
+  return match === null ? null : match[0]
+}
+
 /** 探测命令行工具的版本号（pnpm --version / npm --version / git --version）：
  *  未安装 / 不在 PATH / 超时一律返回 null —— issue 环境快照如实写 unknown，绝不挂起。
- *  （同步探测仅用于启动期/请求期的低频率 /env 快照，安装通道不经过这里。） */
+ *  （同步探测仅用于启动期/请求期的低频率 /env 快照，安装通道不经过这里。）
+ *
+ *  Windows 上 pnpm/npm 是 .cmd shim，不带 shell 的 spawnSync 起不来 —— 上报的 issue 里
+ *  因此长期是 `pnpm: unknown` / `npm: unknown`，而 pnpm 版本恰恰是 allowBuilds 那类问题的
+ *  关键信息（门禁行为随版本变）。故 win32 走 shell 让 cmd 解析 shim；参数是固定的
+ *  `--version`，没有注入面。 */
 function toolVersion(cmd: string, args: string[]): string | null {
   try {
-    const r = spawnSync(cmd, args, { timeout: 1500, encoding: 'utf8' })
+    const r = spawnSync(cmd, args, {
+      timeout: 1500,
+      encoding: 'utf8',
+      shell: process.platform === 'win32',
+    })
     if (r.error || r.status !== 0) return null
-    const v = (r.stdout ?? '').trim().split(/\r?\n/)[0]
-    return v || null
+    return versionOf(r.stdout ?? '')
   } catch {
     return null
   }

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

@@ -567,6 +567,9 @@ function spawnMutation(options: {
   })
 
   return (async () => {
+    // 超时复核用基线：本次任务开始前目标是否已在 profile 里。已安装的话，超时后核对无法区分
+    // 「旧版本还在」与「刚装上」，那种情形（更新超时）不冒认成功。
+    const wasInstalled = action !== 'remove' && !isGlobalNpm && verifyInstalledEntry(profile, target).name !== null
     let result = await spawnOnce(args)
     // npm 11 的 arborist peer-set bug（`Cannot read properties of null (reading 'children')`）
     // 会让 `npm install -g` 在解析阶段直接崩溃。首次失败后自动带 `--legacy-peer-deps` 重试一次：
@@ -578,6 +581,16 @@ function spawnMutation(options: {
       if (task) pushLine(task, '[npm] peer-set resolution crashed npm (known npm bug) — retrying with --legacy-peer-deps')
       result = await spawnOnce(retryArgs)
     }
+    // 超时被强杀 ≠ 没装上：命中的安装可能已经落盘（日志里 pnpm 已打印 Done，只是 dsh 进程迟迟不退出
+    // 而被我们超时掐掉）。判失败之前先复核 profile —— 目标已在依赖里、且声明分发的入口文件都在，
+    // 就按成功收尾，避免「其实装好了却报安装失败」并被自动归档成未知失败。
+    if (result.timedOut && !wasInstalled && action !== 'remove' && !isGlobalNpm && task?.status !== 'cancelled') {
+      const verified = verifyInstalledEntry(profile, target)
+      if (verified.name !== null && verified.missing === null) {
+        result = { ...result, timedOut: false, exitCode: 0, error: null }
+        if (task) pushLine(task, '[timeout] the install had already completed — treating it as a success')
+      }
+    }
     // 统一终态后处理：exitCode/status/needsRestart 以最后一次尝试为准
     if (task) {
       task.exitCode = result.exitCode