dshmarket 1.47.0 → 1.48.0

package/UPDATE-API-V1.md

@@ -33,6 +33,37 @@ supported features, restart owner and endpoint paths. A client must hide its
 restart button when `restart.supported` is false. Desktop and supervised hosts
 normally delegate restart to their owning shell or operator.
 
+## Count what can be updated
+
+```http
+GET /dsh-market/api/v1/updates/summary
+```
+
+```json
+{
+  "schema": "dsh-market/update-api/v1",
+  "checked": 12,
+  "updatable": 3,
+  "packages": [
+    { "name": "dsh-mcp-connector", "source": "npm", "installedVersion": "1.1.0", "latestVersion": "1.2.0" }
+  ]
+}
+```
+
+`checked` is the denominator — how many installed plugins the answer looked
+at. Read it, or a badge cannot tell "nothing to update" from "nothing was
+looked at". The two are different answers and only one of them means the
+profile is up to date.
+
+`packages` carries the same objects the single-package endpoint below
+returns, and lists only plugins that can be updated. A badge needs
+`updatable`; a panel needs the rows; neither should have to filter the whole
+profile itself.
+
+`GET /dsh-market/api/v1/capabilities` reports this endpoint at
+`endpoints.updatesSummary` and sets `features.updatesSummary`. Check that
+rather than probing for the path.
+
 ## Check one installed package
 
 ```http
@@ -123,6 +154,37 @@ same-origin, no forwarding headers, no package mutation in progress, and a Host
 whose lifecycle is not owned by Desktop or a supervisor. Clients must feature
 detect it; they must not invent an alternative process-control path.
 
+## Rendering the market's panel elsewhere (client-side)
+
+A host shell that wants the market inside its own container — rather than in
+the settings page — reads the client service this package publishes:
+
+```ts
+const market = ctx.reflect.get('market')
+const element = market.render({ preferredSubsectionId: 'installed' })
+```
+
+`render()` returns the market's own panel wrapped in its error boundary, as a
+React element. Same page, same React instance: this package's client bundle
+resolves react through the host's module table, so the element mounts
+anywhere in that tree.
+
+| member | |
+|---|---|
+| `version` | `1` |
+| `render(props?)` | the panel element; `preferredSubsectionId` is optional |
+| `setSettingsVisible(visible)` | register or retract the market's own `settings.section` entry |
+| `settingsVisible()` | whether that entry is registered right now |
+
+`ctx.provide(name, value)` and `ctx.reflect.provide(name, value)` are the
+same call — cordis's `Service.provide` delegates to the reflect layer — so
+either idiom reaches this service.
+
+What `render()` is **not**: a way to rearrange the market. It hands over the
+whole panel, chrome included. Cutting the market into host-fillable regions
+is a different design, and one host asking is not yet evidence that it fits
+anyone else.
+
 ## Compatibility policy
 
 - New optional response fields may be added within v1.

package/client/client.js

@@ -10720,6 +10720,86 @@ window.__ModuleLoader__.load({ id: "dshmarket", factory: (require) => {
 			});
 		}
 		//#endregion
+		//#region src/client/market-element.ts
+		/**
+		* The market's panel, as an element, built from explicit dependencies.
+		*
+		* Two callers want the same thing and must not drift apart:
+		*
+		* - the `settings.section` this package registers, whose slot passes down a
+		*   host-chosen `preferredSubsectionId`;
+		* - `market.render()`, for a host shell that renders the market inside its
+		*   own container (#602, from the Tauri desktop).
+		*
+		* A module function taking its dependencies rather than a closure over the
+		* cordis context, so the wiring — which locale, which theme, which log
+		* exporter reaches the panel — is something a test can assert instead of
+		* something only a running host can reveal.
+		*/
+		/**
+		* @param props - see {@link MarketElementProps}.
+		* @returns the panel wrapped in its error boundary.
+		*/
+		function marketElement(props) {
+			return (0, react.createElement)(MarketErrorBoundary, {
+				text: props.crashText,
+				actions: (0, react.createElement)("button", {
+					type: "button",
+					onClick: () => {
+						props.exportLog();
+					}
+				}, props.t("exportLog"))
+			}, (0, react.createElement)(MarketSection, {
+				t: props.t,
+				locale: props.locale,
+				theme: props.theme,
+				themeStore: props.themeStore,
+				preferredSubsectionId: props.preferredSubsectionId
+			}));
+		}
+		//#endregion
+		//#region src/client/section-gate.ts
+		/**
+		* @param register - registers the entry and returns its disposer. Called
+		*   only when the entry should be visible; may be called again after a
+		*   retraction, which is why the disposer is required rather than optional.
+		* @returns the gate.
+		*/
+		function createSectionGate(register) {
+			let ready = false;
+			let wanted = true;
+			let removed = false;
+			let dispose = null;
+			const apply = () => {
+				if (!ready) return;
+				const shouldShow = wanted && !removed;
+				if (shouldShow && dispose === null) {
+					dispose = register();
+					return;
+				}
+				if (!shouldShow && dispose !== null) {
+					const stop = dispose;
+					dispose = null;
+					stop();
+				}
+			};
+			return {
+				available: () => {
+					ready = true;
+					apply();
+				},
+				setVisible: (visible) => {
+					wanted = visible;
+					apply();
+				},
+				visible: () => dispose !== null,
+				retire: () => {
+					removed = true;
+					apply();
+				}
+			};
+		}
+		//#endregion
 		//#region src/client/SettingsCard.tsx
 		/**
 		* The market's card on the plugin configuration page (dsh >= 0.1.0-rc.7).
@@ -11210,8 +11290,32 @@ window.__ModuleLoader__.load({ id: "dshmarket", factory: (require) => {
 				en
 			}), "dsh-market: dictionaries");
 			const t = ctx.locale.bind(NS);
-			let retireSection = null;
-			ctx.slots.inject("settings.section", () => {
+			/**
+			* The market's own panel, as an element — one builder for the settings
+			* section this package registers and for `market.render()` (#602). Built
+			* per call: the props are live (locale, theme, the host's preferred
+			* subsection), and a cached element would freeze the first caller's.
+			*/
+			const buildMarketElement = (ownerProps = {}) => marketElement({
+				t,
+				locale: ctx.locale,
+				theme: ctx.theme,
+				themeStore: {
+					subscribe: (cb) => ctx.on("theme/change", cb),
+					getSnapshot: () => ctx.theme.getTheme()
+				},
+				crashText: {
+					title: t("crashTitle"),
+					hint: t("crashHint"),
+					reload: t("crashReload"),
+					details: t("crashDetails")
+				},
+				exportLog: () => {
+					exportMarketLog().catch(() => {});
+				},
+				preferredSubsectionId: ownerProps.preferredSubsectionId
+			});
+			const sectionGate = createSectionGate(() => {
 				const off = ctx.slots.register({
 					name: "settings.section",
 					id: "market",
@@ -11219,32 +11323,31 @@ window.__ModuleLoader__.load({ id: "dshmarket", factory: (require) => {
 					label: () => t("nav"),
 					locale: NS,
 					inject: () => ({ t })
-				}, (ownerProps = {}) => (0, react.createElement)(MarketErrorBoundary, {
-					text: {
-						title: t("crashTitle"),
-						hint: t("crashHint"),
-						reload: t("crashReload"),
-						details: t("crashDetails")
-					},
-					actions: (0, react.createElement)("button", {
-						type: "button",
-						onClick: () => {
-							exportMarketLog().catch(() => {});
-						}
-					}, t("exportLog"))
-				}, (0, react.createElement)(MarketSection, {
-					t,
-					locale: ctx.locale,
-					theme: ctx.theme,
-					themeStore: {
-						subscribe: (cb) => ctx.on("theme/change", cb),
-						getSnapshot: () => ctx.theme.getTheme()
-					},
-					preferredSubsectionId: ownerProps.preferredSubsectionId
-				})));
-				if (typeof off === "function") retireSection = off;
-				return off;
+				}, (ownerProps = {}) => buildMarketElement(ownerProps));
+				return typeof off === "function" ? off : () => {};
+			});
+			ctx.slots.inject("settings.section", () => {
+				sectionGate.available();
 			});
+			const marketControl = {
+				version: 1,
+				setSettingsVisible: (visible) => {
+					sectionGate.setVisible(visible);
+				},
+				settingsVisible: () => sectionGate.visible(),
+				/**
+				* The market's panel as an element, for a host that renders it inside
+				* its own container. Same page, same React instance — this package's
+				* bundle resolves react through the host's module table, so an element
+				* returned here mounts anywhere in that tree.
+				*
+				* What it is NOT: a way to rearrange the market. It hands over the whole
+				* panel, chrome included. Cutting the market into host-fillable regions
+				* is a different design and has not been asked for by a second host yet.
+				*/
+				render: (props = {}) => buildMarketElement(props)
+			};
+			if (typeof ctx.provide === "function") ctx.provide("market", marketControl);
 			ctx.inject(["settingsScope"], (scoped) => {
 				scoped.slots.inject("settings.plugin.item", () => scoped.slots.register({
 					name: "settings.plugin.item",
@@ -11254,9 +11357,7 @@ window.__ModuleLoader__.load({ id: "dshmarket", factory: (require) => {
 				}, () => (0, react.createElement)(SettingsCard, {
 					t,
 					onRemoved: () => {
-						const off = retireSection;
-						retireSection = null;
-						off?.();
+						sectionGate.retire();
 					}
 				})));
 			});

package/lib/dsh-cli.js

@@ -192,6 +192,44 @@ export function toolSearchDirs(platform = process.platform, env = process.env, h
     // one place a user goes looking for an answer.
     return [...new Set(dirs.filter(dir => dir.trim() !== ''))];
 }
+/**
+ * Stop git asking for credentials down a channel nobody is listening on
+ * (#587).
+ *
+ * `CI=true` below is the same defence one layer up, and pnpm reads it. git
+ * does not — it has its own switch, and it was not set. The gap only opens
+ * when a spec reaches pnpm's git fetcher instead of the codeload tarball
+ * path `accelerate.ts` describes: `github:owner/repo#path:/sub` is one, and
+ * pnpm really does shell out to `git` for it, trying HTTPS first.
+ *
+ * git's credential prompt opens the controlling terminal, not stdin. There
+ * is no terminal here, so the question is never seen and never answered:
+ * the reporter caught `git.exe` alive for eight minutes having burned 0.05s
+ * of CPU, and only the fifteen-minute install timeout ended it. Refusing
+ * the prompt turns that into a fast, readable failure.
+ *
+ * It is a default, not an override: a value the caller set wins, and blank
+ * counts as unset because an empty `GIT_TERMINAL_PROMPT` is not a setting
+ * git can parse either. Credential helpers and `GIT_ASKPASS` are untouched
+ * and still answer first — this closes only the terminal fallback, which is
+ * precisely the branch that cannot work from a spawned child.
+ *
+ * Scope, stated plainly because it is narrower than the issue title
+ * suggests: this is the HTTPS half. pnpm falls back to `git@github.com:`
+ * when HTTPS fails, and the ssh side needs `GIT_SSH_COMMAND`, which
+ * overrides `core.sshCommand` and `GIT_SSH` — the two ordinary ways to
+ * choose an identity — and whose `BatchMode=yes` would disable
+ * `SSH_ASKPASS`, breaking key-passphrase installs that work today. That
+ * half needs a policy decision, so it is not made here. Note also that on
+ * POSIX `runDshPlugin` spawns detached, so the subtree has no controlling
+ * terminal and the prompt already dies instantly; the hang the issue
+ * reports needs Windows, where the spawn is not detached.
+ */
+export function gitEnvForPnpm(env = process.env) {
+    if ((env.GIT_TERMINAL_PROMPT ?? '').trim() !== '')
+        return {};
+    return { GIT_TERMINAL_PROMPT: '0' };
+}
 function spawnEnv() {
     // pnpm v10+ blocks forever on a silent interactive prompt without a TTY;
     // CI mode forces it to act or fail instead of asking.
@@ -201,7 +239,13 @@ function spawnEnv() {
         if (!parts.includes(bin))
             parts.push(bin);
     }
-    return { ...process.env, ...proxyEnvForPnpm(process.env, activeRegion()), CI: 'true', PATH: parts.join(separator) };
+    return {
+        ...process.env,
+        ...proxyEnvForPnpm(process.env, activeRegion()),
+        ...gitEnvForPnpm(process.env),
+        CI: 'true',
+        PATH: parts.join(separator),
+    };
 }
 const INSTALL_TIMEOUT_MS = Number(process.env.DSH_MARKET_INSTALL_TIMEOUT_MS) || 15 * 60 * 1000;
 /**

package/lib/dsh-install.js

@@ -1,6 +1,6 @@
 /** Locate the DSH host package in CLI and packaged Desktop runtimes. */
 import { readFileSync, realpathSync } from 'node:fs';
-import { dirname, join, resolve } from 'node:path';
+import { dirname, isAbsolute, join, relative, resolve, sep } from 'node:path';
 /** The entry with symlinks resolved, or unchanged when it cannot be read. */
 function realpathOf(entry) {
     try {
@@ -14,27 +14,77 @@ function realpathOf(entry) {
     }
 }
 const DSH_PACKAGE = '@deepseek-ai/dsh';
+const DESKTOP_PACKAGE = '@deepseek-ai/dsh-desktop';
+const APPLICATION_ROOTS = ['app.asar.unpacked', 'app.asar', 'app'];
+// The split runtime reported in #553. Only these local, identity-checked
+// packages corroborate the shell; never resolve witnesses from a profile.
+const DESKTOP_RUNTIME_PACKAGES = ['dsh-base', 'dsh-web-app', 'dsh-web', 'dsh-settings'];
 /**
- * The host package's own manifest, or null when `directory` is not it.
- * @returns the parsed manifest of `@deepseek-ai/dsh`, or null.
+ * A package's own manifest, or null when its identity cannot be confirmed.
  */
-function readDshManifest(directory) {
+function readDshManifest(directory, name = DSH_PACKAGE) {
     try {
         const manifest = JSON.parse(readFileSync(join(directory, 'package.json'), 'utf8'));
-        return manifest.name === DSH_PACKAGE ? { name: DSH_PACKAGE, version: manifest.version } : null;
+        return manifest.name === name ? { name, version: manifest.version } : null;
     }
     catch {
         return null;
     }
 }
-function isDshPackage(directory) {
-    return readDshManifest(directory) !== null;
+function entryDirectories(entry) {
+    if (entry === undefined)
+        return [];
+    const directories = [];
+    let directory = resolve(dirname(realpathOf(entry)));
+    for (let depth = 0; depth < 10; depth += 1) {
+        directories.push(directory);
+        const parent = dirname(directory);
+        if (parent === directory)
+            break;
+        directory = parent;
+    }
+    return directories;
+}
+function desktopDirectories() {
+    const { resourcesPath } = process;
+    if (typeof resourcesPath !== 'string' || resourcesPath.length === 0)
+        return [];
+    return APPLICATION_ROOTS.map(root => join(resourcesPath, root));
+}
+function declaredVersion(manifest) {
+    return typeof manifest?.version === 'string' && manifest.version !== '' ? manifest.version : 'unknown';
+}
+function flatDesktopHost(directory) {
+    const shell = readDshManifest(directory, DESKTOP_PACKAGE);
+    if (shell === null)
+        return null;
+    const runtime = DESKTOP_RUNTIME_PACKAGES.map(name => {
+        const candidate = join(directory, 'node_modules', '@deepseek-ai', name);
+        // Bundled pnpm links are fine; a link to a mutable profile/global package
+        // is not evidence about the version of the embedded runtime.
+        const path = relative(realpathOf(directory), realpathOf(join(candidate, 'package.json')));
+        if (isAbsolute(path) || path === '..' || path.startsWith(`..${sep}`))
+            return null;
+        return readDshManifest(candidate, `@deepseek-ai/${name}`);
+    });
+    // A shell alone is not a dependency anchor. Either in-box bundle can
+    // establish the directory even if the other version witnesses are broken.
+    if (runtime[0] === null && runtime[1] === null)
+        return null;
+    const version = declaredVersion(shell);
+    // DSH split packages share a release line, but a desktop shell need not.
+    // Require agreement from every witness; missing/conflicting evidence is
+    // unknown, not the shell version or a majority vote among split packages.
+    const parsed = /^(?:0|[1-9]\d*)\.(?:0|[1-9]\d*)\.(?:0|[1-9]\d*)(?:-([0-9A-Za-z-]+(?:\.[0-9A-Za-z-]+)*))?(?:\+[0-9A-Za-z-]+(?:\.[0-9A-Za-z-]+)*)?$/.exec(version);
+    const corroborated = parsed !== null && !(parsed[1]?.split('.').some(part => /^0\d+$/.test(part)) ?? false)
+        && runtime.every(manifest => manifest?.version === version);
+    return { directory, version: corroborated ? version : 'unknown' };
 }
 /**
  * The version of the DSH host this market is running inside.
  *
- * Read from the same manifest `findDshInstallDir` already parses to identify
- * the package — the version was sitting in that object and being discarded.
+ * CLI versions come from the host manifest. Flat Desktop shells additionally
+ * require agreement with their bundled split runtime, never profile packages.
  *
  * Worth reporting because the host version has repeatedly been the thing
  * neither side could see. #293 turned on it (the reporter was on
@@ -51,17 +101,20 @@ function isDshPackage(directory) {
  * legitimately land here).
  */
 export function dshHostInfo(entry = process.argv[1]) {
-    const directory = findDshInstallDir(entry);
-    if (directory === null)
-        return null;
-    const manifest = readDshManifest(directory);
-    // Located but unversioned: report the directory anyway. "The host is here
-    // and declares no version" is a fact worth carrying, and it is not the
-    // same fact as "no host found".
-    const version = typeof manifest?.version === 'string' && manifest.version !== ''
-        ? manifest.version
-        : 'unknown';
-    return { version, directory };
+    const ancestors = entryDirectories(entry);
+    const applications = desktopDirectories();
+    // Keep the entire legacy search order ahead of newly supported shells.
+    for (const directory of [...ancestors, ...applications.map(root => join(root, 'node_modules', '@deepseek-ai', 'dsh'))]) {
+        const manifest = readDshManifest(directory);
+        if (manifest !== null)
+            return { directory, version: declaredVersion(manifest) };
+    }
+    for (const directory of [...ancestors, ...applications]) {
+        const host = flatDesktopHost(directory);
+        if (host !== null)
+            return host;
+    }
+    return null;
 }
 /**
  * Walk up from the CLI entry first, then inspect Electron's authoritative
@@ -84,25 +137,5 @@ export function dshHostInfo(entry = process.argv[1]) {
  * why this survived: the case that worked is the one that gets tested.
  */
 export function findDshInstallDir(entry = process.argv[1]) {
-    if (entry !== undefined) {
-        let directory = resolve(dirname(realpathOf(entry)));
-        for (let depth = 0; depth < 10; depth += 1) {
-            if (isDshPackage(directory))
-                return directory;
-            const parent = dirname(directory);
-            if (parent === directory)
-                break;
-            directory = parent;
-        }
-    }
-    const electronProcess = process;
-    if (typeof electronProcess.resourcesPath !== 'string'
-        || electronProcess.resourcesPath.length === 0)
-        return null;
-    for (const applicationRoot of ['app.asar.unpacked', 'app.asar', 'app']) {
-        const candidate = join(electronProcess.resourcesPath, applicationRoot, 'node_modules', '@deepseek-ai', 'dsh');
-        if (isDshPackage(candidate))
-            return candidate;
-    }
-    return null;
+    return dshHostInfo(entry)?.directory ?? null;
 }

package/lib/install.js

@@ -10,8 +10,19 @@ import { classifyPnpmFailure, HOST_NAMESPACE_RE } from './pnpm-compat.js';
 import { conflictingEntryIds, dropFromManifest, hasDshManifest, hasLoadableEntry, pluginSubdirs, profileDir, readInstalled, readManifestDeps, readProfileBundles } from './profile.js';
 import { logEvent } from './log.js';
 import { cleanOrphanedStore } from './store.js';
-/** One-shot bypass for pnpm's fresh-release hold; scoped to a single command. */
-export const RELEASE_AGE_OVERRIDE = '--config.minimumReleaseAge=0';
+/**
+ * One-shot bypass for pnpm's fresh-release hold; scoped to a single command.
+ *
+ * Spelled like the .npmrc key, not the camelCase pnpm-workspace.yaml one:
+ * from pnpm 12.3.0 (the native CLI) `--config.minimumReleaseAge=0` is
+ * silently ignored — no unknown-option error — so the retry ran without the
+ * bypass and failed exactly like the first attempt (#600).
+ * `--config.minimum-release-age=0` is honoured by pnpm 10, 11 and 12 alike.
+ * That is specific to this key, not a rule for `--config.*`: the native CLI
+ * ignores `--config.fetch-timeout` in both spellings, which is why
+ * FETCH_TIMEOUT_OVERRIDE below is not respelled here (#615).
+ */
+export const RELEASE_AGE_OVERRIDE = '--config.minimum-release-age=0';
 /**
  * Longer per-request fetch timeout for one retried command. pnpm's default
  * 60-second limit aborts large tarball downloads (github: sources fetch the
@@ -77,8 +88,15 @@ export function isUnpublishedHostPeer(pkg, profile, explicitDir) {
  * Any recognized failure that survives gets its bilingual explanation
  * appended to stderr so the UI shows an actionable message instead of a
  * wall of text (#20 bug 3). Cancelled runs are never recovered.
+ *
+ * The release-age bypass can be declined (`releaseAgeBypass: false`). Its
+ * safety argument above assumes the young package is already installed; a
+ * fresh install pinned to the registry's latest (#594) is the one case
+ * where it is not — there the bypass would be what installs the young
+ * version, over a minimumReleaseAge the profile set on purpose — so the
+ * install route declines it and falls back to the bare name instead.
  */
-export async function withHoistRecovery(run, profile, pluginArgs, profileDirectory) {
+export async function withHoistRecovery(run, profile, pluginArgs, profileDirectory, options = {}) {
     let result = await run(profile, pluginArgs);
     const ok = (r) => r.exitCode === 0 && !r.timedOut && !r.cancelled;
     if (!ok(result) && !result.cancelled) {
@@ -92,6 +110,7 @@ export async function withHoistRecovery(run, profile, pluginArgs, profileDirecto
                 result = await run(profile, pluginArgs);
         }
         else if (failure?.code === 'release-age-violation'
+            && options.releaseAgeBypass !== false
             && (pluginArgs[0] === 'add' || pluginArgs[0] === 'remove')
             && !pluginArgs.includes(RELEASE_AGE_OVERRIDE)) {
             logEvent('warn', 'install', `a too-young release blocks pnpm's lockfile verification (#39) — retrying once with ${RELEASE_AGE_OVERRIDE}`);
@@ -172,6 +191,23 @@ export async function withHoistRecovery(run, profile, pluginArgs, profileDirecto
 export function pnpmNeverStarted(result) {
     return classifyPnpmFailure(`${result.stderr}\n${result.stdout}`, result.exitCode)?.code === 'pnpm-unusable';
 }
+/**
+ * Whether pnpm failed because the running host holds the package's files
+ * open, so nothing pnpm runs from inside that host can replace them.
+ *
+ * Worth asking for the same reason as pnpmNeverStarted: the update route
+ * answers a failed run by reinstalling the previous build, and that reinstall
+ * performs the very rename that just failed, against the same open handles
+ * (#608 by @Euezb). It cannot win — pnpm retries the rename for about three
+ * minutes before giving up — and the route then told the user their profile
+ * might be broken and to inspect it before restarting, when nothing had been
+ * reinstalled and the previous build was still there to be checked.
+ * @param result - the failed run.
+ * @returns true when pnpm was stopped by files the host holds open.
+ */
+export function pnpmBlockedByOpenFiles(result) {
+    return classifyPnpmFailure(`${result.stderr}\n${result.stdout}`, result.exitCode)?.code === 'windows-file-locked';
+}
 /**
  * The most specific description of a failed run available, for logs.
  *

package/lib/pnpm-compat.js

@@ -271,7 +271,7 @@ export function classifyPnpmFailure(output, exitCode) {
     // before ANY later mutation — uninstalling even an unrelated plugin fails
     // (MINIMUM_RELEASE_AGE_VIOLATION), and a later add can fail re-resolving
     // the young dep (NO_MATURE_MATCHING_VERSION). Recovery is a one-shot
-    // --config.minimumReleaseAge=0 retry, automated in withHoistRecovery.
+    // --config.minimum-release-age=0 retry, automated in withHoistRecovery.
     if (output.includes('ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION')
         || output.includes('ERR_PNPM_NO_MATURE_MATCHING_VERSION')) {
         return {
@@ -389,7 +389,10 @@ export function classifyPnpmFailure(output, exitCode) {
     // win, because that process is the thing holding the handles; retrying
     // would only turn one clear failure into several slow ones. So this names
     // the cause and the ways out instead of guessing.
-    if (/ERR_PNPM_EPERM|EPERM: operation not permitted, rename/i.test(output)) {
+    // pnpm 12 (the native CLI) says it differently and carries no ERR_PNPM_
+    // code: `failed to remove existing directory "…" prior to swap: …` — same
+    // refused swap over the open directory, so the same answer.
+    if (/ERR_PNPM_EPERM|EPERM: operation not permitted, rename|failed to remove existing directory .* prior to swap/i.test(output)) {
         // Read through the NDJSON reporter like the integrity classifier does:
         // in production this arrives JSON-escaped, so every separator is doubled
         // and a single-character class silently matches nothing.
@@ -402,7 +405,7 @@ export function classifyPnpmFailure(output, exitCode) {
             code: 'windows-file-locked',
             recoverable: false,
             ...(pkg === undefined ? {} : { pkg }),
-            message: `Windows 不允许替换正在被打开的文件。pnpm 要用新目录替换${zh === '' ? '一个已装好的包' : ` ${pkg}`}，而它的文件正被运行中的 DeepSeek Harness 打开着，改名因此失败，这一步没有生效——已经装好的内容没有被破坏。\n如果这个包带原生模块（.node 文件，例如 node-hid 这类），那么停用插件、甚至卸载插件都不够：原生模块一旦被加载，在进程退出前都不会释放。刚卸载完立刻重装同一个插件在 Windows 上失败，通常就是这个原因。\n可行的做法：完全退出 DeepSeek Harness（不是刷新页面），重新启动后再操作一次；或退出后在命令行执行。杀毒软件或文件索引临时占用目录也会报同样的错，若都不适用可稍后重试。 / Windows will not replace a file that is open. pnpm tried to swap a new directory over${en === '' ? ' an installed package' : en}, whose files the running DeepSeek Harness holds open, so the rename failed and this step did not apply — what was already installed is intact. If that package ships a native module (a .node file, node-hid and friends), disabling the plugin — even uninstalling it — is not enough: once a native module is loaded it is not released until the process exits, which is the usual reason reinstalling a plugin right after uninstalling it fails on Windows. What works: quit DeepSeek Harness completely (not a page refresh), start it again, and repeat the operation; or run it from the command line with the app closed. Antivirus or a file indexer holding the directory produces the same error, so a later retry is worth trying if neither applies.`,
+            message: `Windows 不允许替换正在被打开的文件。pnpm 要用新目录替换${zh === '' ? '一个已装好的包' : ` ${pkg}`}，而它的文件正被运行中的 DeepSeek Harness 打开着，改名因此失败，这一步没有生效。\n要注意的是：pnpm 在重试改名之前会尽量把目标目录清掉，所以**被占用文件旁边的内容可能已经被删**——不一定只是「没换成」而已。市场遇到这种失败时不再尝试回滚（同一个改名会撞同一批句柄），而是把 package.json 与 pnpm-lock.yaml 恢复成操作前的样子，并检查原构建的入口是否还在——结论以那次检查为准。\n如果这个包带原生模块（.node 文件，例如 node-hid 这类），那么停用插件、甚至卸载插件都不够：原生模块一旦被加载，在进程退出前都不会释放。刚卸载完立刻重装同一个插件在 Windows 上失败，通常就是这个原因。\n可行的做法：完全退出 DeepSeek Harness（不是刷新页面），重新启动后再操作一次；或退出后在命令行执行。杀毒软件或文件索引临时占用目录也会报同样的错，若都不适用可稍后重试。 / Windows will not replace a file that is open. pnpm tried to swap a new directory over${en === '' ? ' an installed package' : en}, whose files the running DeepSeek Harness holds open, so the rename failed and this step did not apply. Note that pnpm clears as much of the target directory as it can before retrying the rename, so content BESIDE the file it could not remove may already be gone — this is not always only "the swap did not happen". On this failure the market no longer attempts a rollback (the same rename would meet the same open handles); it restores package.json and pnpm-lock.yaml to how they were and then checks whether the previous build still has a loadable entry — that check is the answer. If that package ships a native module (a .node file, node-hid and friends), disabling the plugin — even uninstalling it — is not enough: once a native module is loaded it is not released until the process exits, which is the usual reason reinstalling a plugin right after uninstalling it fails on Windows. What works: quit DeepSeek Harness completely (not a page refresh), start it again, and repeat the operation; or run it from the command line with the app closed. Antivirus or a file indexer holding the directory produces the same error, so a later retry is worth trying if neither applies.`,
         };
     }
     // #83: pnpm replays the WHOLE dependency tree on every add/remove, so a