TAOxxx7/dsh-plugin-manager

## Core Features
- The plugin adds a categorized plugin manager to Settings → Plugins as an independently publishable DSH bundle.
- It lists installed profile packages by category and searches GitHub repositories under the dsh-plugin topic while detecting duplicate installations.
- Installation uses npm first when a market repository publishes a DSH bundle and falls back to GitHub for unpublished repositories.
- Package operations include uninstall, single-package update, update checking, startup checks, GitHub Release checks for semver-tagged source installs, and commit-head fallback for unpinned sources.
- Build and restart handling includes explicit pnpm build approval or retry with captured diagnostics and an install-complete restart prompt for Desktop and native Web.

## Use Cases
- Users can manage installed DSH profile packages from a categorized Settings tab in Desktop or native Web.
- Users can discover plugins through GitHub dsh-plugin topic search and install repositories that publish DSH bundles.
- Users can maintain existing packages by uninstalling, updating, checking releases, and responding to pnpm build diagnostics.
- Users can complete installation flows that require restarting DSH Desktop or the native Web process.

## Technical Details
- The repository is shaped as a DSH community plugin with an installable root package.json, a dsh.bundle.patch Host gateway mount, a dsh.client browser Settings loader, and built artifacts in lib/.
- The dsh.client.platform: "web" declaration describes the browser face while a remote browser controls the Host profile running the DSH process, so package operations occur on that machine.
- On Windows native Web, pnpm resolution follows DSH_PNPM_BIN, the active profile or shared DSH pnpm package, PNPM_HOME or npm global directories, PATH, and Node.js Corepack.
- Command execution avoids shell splitting for direct .exe or pnpm-script launches, quotes .cmd shims when needed, and reads output as UTF-8 with GB18030 fallback.

## Notes
- A newer package version requires restarting the current DSH process so the new bundle layer is loaded, and the Settings tab prompts after a successful market install.
- Native Web restart replaces the running Node process, so the triggering HTTP request may show Failed to fetch while lib/client.js treats the Web-only disconnect as an expected restart.
- If Windows native Web cannot locate pnpm, install Node.js or Corepack, or set DSH_PNPM_BIN to the full pnpm.cmd path, then restart the Web process.