relay-dsh-plugin-manager 0.1.0-rc.3 → 0.1.0

package/CHANGELOG.md

@@ -2,6 +2,46 @@
 
 All notable changes to this project are documented here.
 
+## [0.1.0] - 2026-08-31
+
+### Added
+
+- The Settings > Plugins tab now gives each recommended plugin a self-contained
+  card headed by its npm package name, carrying its purpose, prerequisite, the
+  complete Chat message that installs it, and its post-install check.
+
+### Changed
+
+- The Settings > Plugins help tab is now named "Recommended plugins" and sorts
+  ahead of the built-in tabs, so it is the tab Settings > Plugins opens on.
+- The tab's copy is condensed and rescoped. Tab-level text claims nothing about
+  a specific plugin; anything true of one plugin lives on that plugin's card.
+  The former heading, introduction, standalone confirmation notice, and
+  search/remove/list example table are gone.
+- The discovery example no longer names a specific third-party integration.
+
+### Compatibility
+
+- This release retains the verified DSH `0.1.1-rc.2` baseline. It does not include
+  migration to the client APIs introduced in DSH `0.1.2-alpha.2`.
+
+## [0.1.0-rc.4] - 2026-08-28
+
+### Added
+
+- GitHub owner discovery with exact-owner ranking, actionable owner-only inspect
+  errors, and round-trippable repository identities.
+- Plugin-owned DSH choice confirmation that validates the exact plan answer and
+  executes without requiring a duplicate typed confirmation.
+- One-plan, one-confirmation multi-plugin installation with serial child
+  outcomes and required peer-dependency preflight.
+- Explicit restart-required and manual-restart operation terminal states.
+
+### Changed
+
+- Confirmed plugin operations now queue in FIFO order instead of failing while
+  another mutation is active.
+
 ## [0.1.0-rc.3] - 2026-08-26
 
 ### Added
@@ -37,3 +77,5 @@ All notable changes to this project are documented here.
 [0.1.0-rc.1]: https://github.com/yangbobo2021/relay-dsh-plugin-manager/releases/tag/v0.1.0-rc.1
 [0.1.0-rc.2]: https://github.com/yangbobo2021/relay-dsh-plugin-manager/releases/tag/v0.1.0-rc.2
 [0.1.0-rc.3]: https://github.com/yangbobo2021/relay-dsh-plugin-manager/compare/v0.1.0-rc.2...v0.1.0-rc.3
+[0.1.0-rc.4]: https://github.com/yangbobo2021/relay-dsh-plugin-manager/compare/v0.1.0-rc.3...v0.1.0-rc.4
+[0.1.0]: https://github.com/yangbobo2021/relay-dsh-plugin-manager/compare/v0.1.0-rc.4...v0.1.0

package/README.md

@@ -1,4 +1,4 @@
-# Plugin Manager for DeepSeek Harness
+# Manage DeepSeek Harness Plugins from Chat
 
 [![npm version](https://img.shields.io/npm/v/relay-dsh-plugin-manager?label=npm)](https://www.npmjs.com/package/relay-dsh-plugin-manager)
 [![CI](https://github.com/yangbobo2021/relay-dsh-plugin-manager/actions/workflows/ci.yml/badge.svg)](https://github.com/yangbobo2021/relay-dsh-plugin-manager/actions/workflows/ci.yml)
@@ -13,10 +13,24 @@ English | [中文](README.zh.md)
 **npm package:** [`relay-dsh-plugin-manager`](https://www.npmjs.com/package/relay-dsh-plugin-manager)
 · [Relay DSH plugin catalog](https://github.com/yangbobo2021/Relay/blob/codex/relay-foundation/docs/dsh-plugins.md)
 
-`relay-dsh-plugin-manager` lets you discover and manage DSH plugins directly
-from a DeepSeek Harness Chat conversation. Ask for the capability you need, or
-ask DSH to install, update, enable, disable, or remove a plugin. DSH shows a plan
-and waits for confirmation before changing your Profile.
+**Find and manage DSH plugins by describing what you need, without leaving the
+conversation or editing Profile files by hand.**
+
+`relay-dsh-plugin-manager` lets DeepSeek Harness Chat discover, install, update,
+enable, disable, and remove plugins. Search and inspection are read-only. Before
+any change, DSH shows the plan and waits for a separate confirmation.
+
+[![Plugin Manager installs relay-dsh-plugin-codex successfully in DSH](https://raw.githubusercontent.com/yangbobo2021/Relay/codex/relay-foundation/docs/media/dsh-plugin-manager-codex-install-success.png)](https://github.com/yangbobo2021/Relay/blob/codex/relay-foundation/docs/media/dsh-plugin-manager-codex-install-demo.en.mp4?raw=1)
+
+*Watch the [40-second real DSH run](https://github.com/yangbobo2021/Relay/blob/codex/relay-foundation/docs/media/dsh-plugin-manager-codex-install-demo.en.mp4?raw=1):
+search, review a no-change plan, confirm separately, and finish with the Codex
+plugin installed. Recorded on official DSH commit
+[`b150a551`](https://github.com/deepseek-ai/deepseek-harness/commit/b150a551b8d465e31e418e1b2eaf5e79bbb7d28e)
+with Plugin Manager `0.1.0-rc.3` and Codex plugin `0.1.2`.*
+
+If conversation-first plugin management is useful to you,
+[star this plugin](https://github.com/yangbobo2021/relay-dsh-plugin-manager) and
+[share your install result or missing plugin use case](https://github.com/yangbobo2021/relay-dsh-plugin-manager/issues).
 
 ## Install
 
@@ -33,8 +47,12 @@ Then start or restart DSH Web:
 dsh web
 ```
 
-The plugin appears under **Settings > Plugins > Plugin marketplace**. This page
-is a short help view; plugin management itself happens in Chat.
+If `dsh` is not on `PATH`, replace it with
+`pnpm dlx @deepseek-ai/dsh@0.1.1-rc.2` in both commands.
+
+The plugin appears under **Settings > Plugins > Recommended plugins**, the tab
+that Settings > Plugins opens on. It presents the recommended conversation-backend
+plugins and a short help view; plugin management itself happens in Chat.
 
 ### Installed by KeySync
 
@@ -49,7 +67,9 @@ Describe what you want in ordinary language:
 
 ```text
 Find a plugin that connects to Lark
+Find DSH plugins owned by GitHub user yangbobo2021
 Install relay-dsh-plugin-codex
+Install relay-dsh-plugin-codex, relay-dsh-plugin-files, and relay-dsh-plugin-terminal together
 List my installed plugins and their status
 Disable example-dsh-plugin
 Remove example-dsh-plugin
@@ -59,22 +79,17 @@ You can also use the single `/plugins` command:
 
 ```text
 /plugins find a workspace file browser
+/plugins search owner:yangbobo2021
 /plugins install relay-dsh-plugin-files
 ```
 
 Search and inspection are read-only. Installation, update, removal, enablement,
-disablement, and restart always show a plan and require a later confirmation.
-
-## Real Install Demo
-
-[![Plugin Manager installs relay-dsh-plugin-codex successfully in DSH](https://raw.githubusercontent.com/yangbobo2021/Relay/codex/relay-foundation/docs/media/dsh-plugin-manager-codex-install-success.png)](https://github.com/yangbobo2021/Relay/blob/codex/relay-foundation/docs/media/dsh-plugin-manager-codex-install-demo.en.mp4?raw=1)
-
-Watch the [38-second real DSH run](https://github.com/yangbobo2021/Relay/blob/codex/relay-foundation/docs/media/dsh-plugin-manager-codex-install-demo.en.mp4?raw=1):
-search, planning without changes, separate confirmation, installation, and the
-final `succeeded` status. It was recorded against official DSH commit
-[`b150a551`](https://github.com/deepseek-ai/deepseek-harness/commit/b150a551b8d465e31e418e1b2eaf5e79bbb7d28e)
-with Plugin Manager `0.1.0-rc.2` and Codex plugin `0.1.2`. DSH reports when a
-restart is required after installation.
+disablement, and restart always show a plan. You can confirm with DSH's choice
+UI, or explicitly approve in a later Chat message.
+When you request multiple installs together, DSH shows one ordered plan and any
+missing companion peers, waits for one confirmation, and runs the installs in
+sequence. Completed changes that still need restart are reported explicitly as
+restart-required or waiting for a manual restart.
 
 ## Part of Relay
 

package/README.zh.md

@@ -1,4 +1,4 @@
-# DeepSeek Harness 插件管理器
+# 在 DeepSeek Harness 对话中管理插件
 
 [![npm 版本](https://img.shields.io/npm/v/relay-dsh-plugin-manager?label=npm)](https://www.npmjs.com/package/relay-dsh-plugin-manager)
 [![CI](https://github.com/yangbobo2021/relay-dsh-plugin-manager/actions/workflows/ci.yml/badge.svg)](https://github.com/yangbobo2021/relay-dsh-plugin-manager/actions/workflows/ci.yml)
@@ -13,9 +13,24 @@
 **npm 包名：** [`relay-dsh-plugin-manager`](https://www.npmjs.com/package/relay-dsh-plugin-manager)
 · [Relay DSH 插件目录](https://github.com/yangbobo2021/Relay/blob/codex/relay-foundation/docs/dsh-plugins.zh.md)
 
-`relay-dsh-plugin-manager` 让你直接在 DeepSeek Harness 的 Chat 对话中寻找和
-管理 DSH 插件。你可以描述需要的能力，也可以让 DSH 安装、更新、启用、停用
-或卸载插件。修改 Profile 前，DSH 会先展示操作计划并等待确认。
+**只需描述需要的能力，就能查找和管理 DSH 插件；不必离开对话，也不必手工
+编辑 Profile 文件。**
+
+`relay-dsh-plugin-manager` 让 DeepSeek Harness Chat 可以查找、安装、更新、
+启用、停用和卸载插件。搜索和查看只读；任何变更执行前，DSH 都会先展示计划，
+并等待单独确认。
+
+[![插件管理器在 DSH 中成功安装 relay-dsh-plugin-codex](https://raw.githubusercontent.com/yangbobo2021/Relay/codex/relay-foundation/docs/media/dsh-plugin-manager-codex-install-success.png)](https://github.com/yangbobo2021/Relay/blob/codex/relay-foundation/docs/media/dsh-plugin-manager-codex-install-demo.zh.mp4?raw=1)
+
+*查看 [38 秒真实 DSH 运行录像](https://github.com/yangbobo2021/Relay/blob/codex/relay-foundation/docs/media/dsh-plugin-manager-codex-install-demo.zh.mp4?raw=1)：
+从搜索、查看不产生变更的计划、单独确认，到 Codex 插件安装完成。录像基于官方
+DSH 提交
+[`b150a551`](https://github.com/deepseek-ai/deepseek-harness/commit/b150a551b8d465e31e418e1b2eaf5e79bbb7d28e)，
+使用 Plugin Manager `0.1.0-rc.2` 和 Codex 插件 `0.1.2`。*
+
+如果这种对话式插件管理对你有用，欢迎
+[Star 本插件](https://github.com/yangbobo2021/relay-dsh-plugin-manager)，并
+[反馈安装结果或缺少的插件场景](https://github.com/yangbobo2021/relay-dsh-plugin-manager/issues)。
 
 ## 安装
 
@@ -31,8 +46,11 @@ dsh plugin --profile web add relay-dsh-plugin-manager@latest
 dsh web
 ```
 
-安装后可以在 **设置 > 插件 > 插件市场** 看到简短帮助。实际的插件管理仍在
-Chat 对话中完成。
+如果 `PATH` 中没有 `dsh`，请在两条命令中将它替换为
+`pnpm dlx @deepseek-ai/dsh@0.1.1-rc.2`。
+
+安装后，**设置 > 插件** 会默认打开 **推荐插件** 标签页，在这里介绍推荐的
+对话后端插件，并附一份简短帮助。实际的插件管理仍在 Chat 对话中完成。
 
 ### KeySync 已内置安装
 
@@ -46,7 +64,9 @@ Chat 对话中完成。
 
 ```text
 找一个能连接飞书的插件
+查找 GitHub 用户 yangbobo2021 发布的 DSH 插件
 安装 relay-dsh-plugin-codex
+一起安装 relay-dsh-plugin-codex、relay-dsh-plugin-files 和 relay-dsh-plugin-terminal
 列出已安装插件及其状态
 停用 example-dsh-plugin
 卸载 example-dsh-plugin
@@ -56,21 +76,15 @@ Chat 对话中完成。
 
 ```text
 /plugins 找一个工作区文件浏览插件
+/plugins 搜索 owner:yangbobo2021
 /plugins 安装 relay-dsh-plugin-files
 ```
 
-搜索和查看不会修改配置。安装、更新、卸载、启用、停用和重启都会先展示计划，
-并要求用户在后续消息中明确确认。
-
-## 真实安装演示
-
-[![插件管理器在 DSH 中成功安装 relay-dsh-plugin-codex](https://raw.githubusercontent.com/yangbobo2021/Relay/codex/relay-foundation/docs/media/dsh-plugin-manager-codex-install-success.png)](https://github.com/yangbobo2021/Relay/blob/codex/relay-foundation/docs/media/dsh-plugin-manager-codex-install-demo.mp4?raw=1)
-
-查看 [38 秒真实 DSH 运行录像](https://github.com/yangbobo2021/Relay/blob/codex/relay-foundation/docs/media/dsh-plugin-manager-codex-install-demo.mp4?raw=1)：
-从搜索、只生成计划、单独确认，到安装完成并显示 `succeeded`。录像基于官方 DSH
-提交 [`b150a551`](https://github.com/deepseek-ai/deepseek-harness/commit/b150a551b8d465e31e418e1b2eaf5e79bbb7d28e)，
-使用 Plugin Manager `0.1.0-rc.2` 和 Codex 插件 `0.1.2`；安装后如需重启，
-DSH 会明确提示。
+搜索和查看不会修改配置。安装、更新、卸载、启用、停用和重启都会先展示计划。
+你可以直接在 DSH 的选项界面中确认，也可以在后续 Chat 消息中明确批准。
+一次请求安装多个插件时，DSH 会展示一份有序计划和缺失的配套 peer 插件，等待
+一次确认后依次安装。修改完成但仍需重启时，状态会明确区分“需要另行重启”和
+“等待人工重启”。
 
 ## 与 Relay 的关系
 

package/SPEC.md

@@ -10,9 +10,12 @@ Relay DSH Plugin Manager is a conversation-first, independently installable
 DeepSeek Harness bundle. It discovers and manages DSH profile plugins through
 conversation, without management controls or public management HTTP routes.
 
-The package contributes a read-only Plugin Marketplace help tab under
-Settings > Plugins. That tab explains how to search, install, remove, and list
-plugins from Chat; it does not call the Host or mutate plugin state.
+The package contributes a read-only recommended-plugins tab under
+Settings > Plugins. That tab gives each recommended plugin one self-contained
+card headed by its npm package name, carrying its purpose, prerequisite, the
+complete Chat message that installs it, and the check that confirms it worked.
+It then points at Chat for installing, reviewing, or removing any other plugin;
+it does not call the Host or mutate plugin state.
 
 The user may enter `/plugins <request>` or describe the same request in ordinary
 conversation. Both paths use the same model-facing tools and Host management
@@ -26,23 +29,26 @@ service.
 | PM-002 | Keep the model surface compact: one discovery tool and one management tool. Natural-language and slash-command requests use these tools. |
 | PM-003 | List profile dependencies with installed source, bundle membership, package-level enablement, runtime phase, and pending-restart state. |
 | PM-004 | Provide a versioned `ctx.pluginSearch` registry. Other installed plugins may register abortable search providers. Providers discover candidates only and cannot install or mutate the profile. |
-| PM-005 | Search all registered providers concurrently with bounded results, timeout/cancellation, provenance, provider-error isolation, and repository/package-identity deduplication. |
-| PM-006 | Ship npm and GitHub search providers. Preserve a syntactically valid exact npm package-name query even when npm search ranking omits it. Search results are inspected before being reported as installable DSH plugins. |
-| PM-007 | Accept only core-owned npm and GitHub install-source types. Resolve npm to an exact semantic version with registry integrity and GitHub to a full 40-character commit. |
+| PM-005 | Search all registered providers concurrently with bounded results, timeout/cancellation, provenance, provider-error isolation, and repository/package-identity deduplication. Exact typed intent matches sort before unrelated provider-local ranks. Results expose repository owner, aggregate providers, and bounded match reasons. |
+| PM-006 | Ship npm and GitHub search providers. Preserve a syntactically valid exact npm package-name query even when npm search ranking omits it. Support explicit GitHub owner queries and conservative inferred bare-owner hints; inferred hints with no owned DSH repositories fall back to ordinary GitHub keyword search. Search results are inspected before being reported as installable DSH plugins. |
+| PM-007 | Accept only core-owned npm and GitHub install-source types. GitHub repositories accept `github:owner/repo`, `https://github.com/owner/repo`, and the emitted identity `github.com/owner/repo`. Resolve npm to an exact semantic version with registry integrity and GitHub to a full 40-character commit. |
 | PM-008 | Inspect the resolved package manifest and require a valid package name plus a DSH surface (`dsh.bundle.patch` or `dsh.client`). Search providers cannot bypass this validation. |
-| PM-009 | Every install, remove, update, enable, disable, or restart starts with an immutable plan. A later execute call requires the unexpired, one-use confirmation token returned by that plan. The token is bound to the planning DSH Session and cannot execute until that Session contains a newer user message; the original request is mechanically not confirmation. Execution also refuses a stale plan when the target profile dependency changed after planning. |
+| PM-009 | Every install, multi-install, remove, update, enable, disable, or restart starts with an immutable plan and an unexpired, one-use confirmation token bound to the planning DSH Session. A plain `execute` call requires a newer user message in that Session, so the original request is mechanically not confirmation. A `confirm` call may instead ask the user through the controlled UI flow defined by PM-023. Execution also refuses a stale plan when any target profile dependency changed after planning. |
 | PM-010 | Install and update through argv-only invocation of the currently running DSH CLI: `dsh plugin --profile web add --save-exact <immutable-source>`. Never build a shell command string. |
 | PM-011 | Remove through argv-only `dsh plugin --profile web remove <package>`. Verify dependency and bundle postconditions and reconcile a half-removed profile conservatively. |
 | PM-012 | Enable and disable are package-level projections over owned Cordis Loader entries. Persist manager-owned `disabled` overrides in the profile patch, report `mixed` or `unknown` when ownership is not safely reducible, and never disable the manager itself or protected DSH infrastructure. A disable plan warns that conversations using the target plugin may be interrupted. |
 | PM-013 | Attempt restart-free activation for newly installed client-only packages and bundles whose patches contain only plain insert rows. Attempt live disposal for removals. Otherwise report `restartRequired` with a concrete reason. |
 | PM-014 | Enable/disable changes use Loader HMR and normally require no restart. A failed or unverifiable live transition reports pending restart rather than claiming success. |
-| PM-015 | Mutations run as tracked operations with stable ids, progress snapshots, terminal exit state, cooperative cancellation, and one active mutation at a time. |
+| PM-015 | Mutations run as tracked FIFO operations with stable ids, progress snapshots, explicit terminal exit state, cooperative cancellation, and one active top-level mutation at a time; additional confirmed operations remain queued rather than failing busy. A multi-install is one top-level operation whose child installs run serially, stop on the first failure, and retain succeeded, failed, skipped, or cancelled child outcomes. Successful mutations that still need restart terminate as `succeeded_restart_required` when a separately confirmed automatic restart is available, or `waiting_for_manual_restart` when it is not. |
 | PM-016 | Restart is a separately planned operation. When allowed, relaunch the exact current DSH entry/argv/environment through a detached helper, then stop the old process. Refuse automatic restart under a detected service supervisor or explicit disable setting. |
 | PM-017 | Snapshot the profile manifest before package mutations. Restore failed install/update manifest residue; detect and reconcile a remove that deleted package files before pnpm failed. Never report success before dependency source, installed package identity/version, DSH surface, and bundle-membership postconditions pass. |
 | PM-018 | Reject unsafe source tokens, flags, whitespace/control characters, shell metacharacters, unsupported URL hosts, ambiguous package names, and mutable execution sources. Build scripts remain governed by pnpm/DSH and are never silently authorized. |
 | PM-019 | Expose no public plugin-management HTTP routes and impose no client-address, Origin, CORS, or loopback policy. The callable surface is the in-process DSH command/tool plane. |
 | PM-020 | Remain independently installable. Do not import Relay parent implementation code or KeySync implementation code. Runtime interactions use DSH/Cordis public services and the official CLI. |
-| PM-021 | Contribute one localized, read-only `marketplace` tab to `settings.plugins.tab`. It briefly explains conversation-based discovery and lifecycle management, includes representative search/install/remove/list prompts, and states that mutations wait for confirmation. It exposes no management control, Remote call, or additional Host service. |
+| PM-021 | Contribute one localized, read-only `marketplace` tab to `settings.plugins.tab`, sorted ahead of the Host's own tabs so Settings > Plugins opens on it. Each recommended plugin owns one self-contained card: its exact npm package name as the heading, its purpose, its prerequisite, one complete Chat message that installs it by that exact package name, and its post-install check. Tab-level copy claims nothing about a specific plugin and points at Chat for installing, reviewing, or removing any other plugin. It exposes no management control, Remote call, or additional Host service. |
+| PM-022 | Preserve required manifest peer-dependency metadata during source inspection while respecting `peerDependenciesMeta.optional`. A multi-install plan reports required peers absent from both the current profile and the requested set, deduplicated with their ranges, dependents, and suggested npm source. Planning never silently adds an unrequested companion plugin. |
+| PM-023 | `plugin_manage confirm` owns its DSH question: it validates the token, expiry, and exact Session before asking; supplies a stable plan-specific id, visible plan detail, exact approve/decline options, and `plan-review` intent; and executes in that same tool call only for the exact single approve answer. Declines, malformed or unrelated answers, provider failure/cancellation, and cross-session attempts do not execute or consume a still-valid plan. Generic model-authored question results are never mutation authority. |
+| PM-024 | GitHub owner discovery recognizes `owner:<name>`, owner-only GitHub identities, `<name> DSH plugins`, and conservative bare identifiers containing digits. It sends a typed owner intent to providers, uses GitHub's exact owner qualifier, case-insensitively verifies returned ownership, and ranks verified owner matches first. Owner-only `inspect` fails with an actionable error directing callers to search. Every emitted repository identity is accepted by `inspect`; every recommended immutable source is accepted by `plan`. |
 
 ## Command Grammar
 
@@ -62,11 +68,20 @@ behavior drift between direct commands and conversation.
 
 Read-only actions: `list`, `search`, `inspect`, `status`.
 
+`search` accepts capability text or GitHub owner forms such as
+`owner:yangbobo2021`. `inspect` accepts npm sources and all three GitHub
+repository forms from PM-007. An owner without a repository belongs to
+`search`, not `inspect`.
+
 ### `plugin_manage`
 
-State-changing workflow actions: `plan`, `execute`, `status`, `cancel`.
+State-changing workflow actions: `plan`, `confirm`, `execute`, `status`, `cancel`.
 `plan` carries one operation from `install`, `remove`, `update`, `enable`,
-`disable`, or `restart`. `execute` accepts only a confirmation token.
+`disable`, `restart`, or `install_many`. `install_many` accepts a bounded,
+non-empty `sources` array and returns one ordered aggregate plan. `confirm`
+accepts the token and owns the DSH choice UI plus exact-answer validation.
+`execute` accepts the token after a later explicit chat message. The Agent must
+not wrap a plugin plan in the generic `ask_user_question` tool.
 
 ## Search Extension Contract
 
@@ -81,11 +96,12 @@ one provider before deterministic cross-provider ordering.
 ## Explicit Non-Goals
 
 - Settings controls, dashboard, or any other second management workflow. The
-  read-only Plugin Marketplace help tab is explicitly in scope.
+  read-only recommended-plugins help tab is explicitly in scope.
 - Public management REST/HTTP endpoints.
 - Provider-defined installers, shell commands, or arbitrary pnpm arguments.
 - Arbitrary tarball, filesystem, SSH Git, or non-GitHub Git installation in the
   first release.
 - Automatic mutation based only on a search query.
+- Silent installation of peer or companion plugins that the user did not request.
 - Automatic restart as part of install/update/remove.
 - Managing profiles other than the running `web` profile in the first release.

package/docs/acceptance/live-owner-discovery-2026-08-28.md

@@ -0,0 +1,64 @@
+# Live GitHub Owner Discovery Acceptance - 2026-08-28
+
+## Scope
+
+This record validates Issue #3 against the real npm and GitHub services and a
+published DSH runtime. It covers GitHub-owner discovery, schemeless repository
+inspection, immutable-source planning, the complete Codex plugin lifecycle, and
+the existing three-plugin batch flow.
+
+## Environment
+
+- Date: 2026-08-28 (Asia/Shanghai)
+- Node.js: v25.5.0
+- npm: 11.8.0
+- pnpm: 11.19.0
+- DSH: `@deepseek-ai/dsh@0.1.1-rc.2`
+- Plugin manager base commit: `8d78cd267bd12cea246c97d36a233098d5ceb5ed`
+
+The test used an isolated temporary DSH home. It did not make an LLM request,
+require an LLM credential, or persist credentials in repository artifacts.
+
+## Command
+
+```sh
+DSH_CLI_PATH=test/fixtures/dsh-runtime/node_modules/@deepseek-ai/dsh/lib/bin.js \
+  npm run acceptance:live:codex
+```
+
+## Observed Results
+
+The live suite passed both tests in 27.8 seconds.
+
+The explicit owner query `owner:yangbobo2021` returned and prioritized all six
+owner-matching DSH repositories before unrelated results:
+
+1. `yangbobo2021/relay-dsh-plugin-codex`
+2. `yangbobo2021/relay-dsh-plugin-claude`
+3. `yangbobo2021/relay-dsh-plugin-files`
+4. `yangbobo2021/relay-dsh-plugin-workbench`
+5. `yangbobo2021/relay-dsh-plugin-manager`
+6. `yangbobo2021/relay-dsh-plugin-terminal`
+
+Each prioritized result exposed its repository owner, contributing provider,
+and exact-owner match reason. Core inspection independently verified the owner
+before the result received exact-match priority.
+
+The schemeless identity
+`github.com/yangbobo2021/relay-dsh-plugin-codex` inspected successfully and
+resolved to immutable commit
+`ef65b29dd52c92278a2717f19d2a8f056cefdfaa`. The emitted repository identity
+and immutable recommended source were accepted directly by the next inspect and
+plan actions.
+
+The existing live lifecycle also passed for Codex from npm and GitHub,
+including install, enable, disable, update, uninstall, operation polling, Loader
+state, and web boot with HTTP 200. The live batch flow passed for Codex, Files,
+and Terminal. The npm Codex fixture resolved to version `0.1.2`.
+
+## Acceptance Conclusion
+
+The live evidence satisfies the network-dependent portions of A-028 and A-029;
+the automated negative suite covers A-030. Owner-oriented discovery works
+without shell or direct-API workflow repair, result identities round-trip
+through the plugin tools, and the pre-existing lifecycle remains operational.

package/docs/acceptance/release-candidate-0.1.0-rc.4.md

@@ -0,0 +1,63 @@
+# Release Candidate Acceptance - 0.1.0-rc.4
+
+## Scope
+
+This record validates the cumulative delivery of PRs #4, #5, and #6 plus the
+A-031 cross-feature release flow. The candidate starts from main commit
+`aa0330c6d7e9ddd5f4d579481e9e14b52b4e6ea7` and changes the package version to
+`0.1.0-rc.4`.
+
+## Environment
+
+- Date: 2026-08-28 (Asia/Shanghai)
+- Node.js: v25.5.0 locally; Node.js 22 and 24 in CI
+- npm: 11.8.0
+- pnpm: 11.19.0 locally; 11.7.0 in release CI
+- DSH acceptance fixture: `@deepseek-ai/dsh@0.1.1-rc.2`
+- npm dist-tag target: `next`
+
+No LLM request or LLM credential was required. The repository secret scan had
+no matches.
+
+## Cross-Feature Acceptance
+
+A-031 runs one scenario through the real DSH `ToolRuntime`, `AgentRegistry`,
+`PluginSearchRuntime`, and `UserQuestionService`, with the production
+`PluginManager` and a controlled official-CLI runner boundary.
+
+The scenario passed all of these assertions:
+
+1. Discovery emitted three immutable recommended sources in provider rank.
+2. Those exact values entered one `install_many` plan without profile mutation.
+3. The plan exposed the missing Workbench peer and its requesting plugin.
+4. The plugin-owned question displayed all sources and peer preflight detail.
+5. No runner call or profile mutation occurred while the UI answer was pending.
+6. One exact approval started one parent operation.
+7. Three exact `add --save-exact` calls ran serially with maximum concurrency one.
+8. Parent and child operations completed successfully and the profile contained
+   the three exact versions.
+9. Approval replay did not reopen the question or start another runner call.
+
+## Verification Results
+
+- Typecheck: passed
+- Vitest: 90 passed; 2 opt-in live tests skipped in the default suite
+- Release metadata tests: 4 passed
+- Build: passed
+- Packed-package install through the official DSH CLI: passed
+- npm production dependency audit: 0 vulnerabilities
+- Credential scan: passed
+- Simulated tag metadata: `v0.1.0-rc.4` -> `0.1.0-rc.4` on `next`
+- Registry preflight: `0.1.0-rc.4` was not already published
+- `npm publish --dry-run --tag next`: passed; 25 files, approximately 89.7 kB
+
+The opt-in real-network suite also passed both tests. It discovered the six
+owner repositories, resolved the Codex GitHub source to commit
+`ef65b29dd52c92278a2717f19d2a8f056cefdfaa`, completed the npm/GitHub Codex
+lifecycle, booted Web with HTTP 200, and batch-installed Codex, Files, and
+Terminal through the published DSH CLI fixture.
+
+## Release Decision
+
+The candidate satisfies A-001 through A-031 and is approved for publication as
+`0.1.0-rc.4` after its release PR and tag workflow pass on the final commit.

package/docs/acceptance.md

@@ -22,13 +22,21 @@ This matrix is the release contract. Tests name the relevant `PM-*` ids.
 | A-014 disable warns about active-conversation interruption, writes only manager-owned patch rows, HMR-verifies state, survives reload, and enable removes only owned rows | PM-012, PM-014 | plan + profile/loader integration + real DSH walkthrough |
 | A-015 mixed, unknown, user-patch conflict, self-disable, and protected-infrastructure disable are refused or reported accurately | PM-012, PM-014 | enablement unit/integration |
 | A-016 simple insert bundle hot-mounts; complex/config patch, unavailable Include, timeout, and thrown activation require restart | PM-013 | hot-runtime unit/integration |
-| A-017 operation progress is bounded, a concurrent mutation is refused, cancellation reaches the runner, and terminal status is retained | PM-015 | operation integration |
+| A-017 operation progress is bounded, concurrently confirmed mutations run in FIFO order with one active runner, queued cancellation never starts its runner, active cancellation reaches the runner, and terminal status is retained | PM-015 | operation unit + manager integration |
 | A-018 restart requires a separate plan, is refused under supervisor/disabled config, and schedules exact invocation otherwise | PM-016 | restart unit |
 | A-019 package exposes only a read-only help client entry, no management HTTP route, and registers exactly one command/two tools | PM-001, PM-002, PM-019, PM-021 | package/loader integration |
 | A-020 packed tarball installs through official DSH CLI into a clean profile and contributes both Host rows without modifying DSH | PM-020 | local checkout E2E + CI against the locked published DSH runtime fixture |
 | A-021 optional live-network acceptance discovers the real Codex plugin through npm/GitHub, installs npm and immutable GitHub sources in isolated DSH homes, boots the npm-installed Web profile, exercises enable/disable/update, and removes both | PM-003-PM-017 | `npm run acceptance:live:codex` |
 | A-022 a real DSH Web Session exposes both tools, serves slash-command and natural-language search, rejects same-turn confirmation, executes later confirmation, and observes Loader HMR without restarting DSH | PM-001, PM-002, PM-009, PM-012, PM-014 | release-candidate walkthrough with real Codex backend |
-| A-023 Settings > Plugins contains one localized Plugin Marketplace tab with search/install/remove/list Chat examples and confirmation guidance; the page has no action control, Host call, or Remote dependency | PM-019, PM-021 | client registration + server-rendered component unit tests + packed client-bundle E2E |
+| A-023 Settings > Plugins opens on one localized recommended-plugins tab that gives each recommended plugin a self-contained card headed by its exact npm package name, carrying its purpose, prerequisite, a complete install message repeating that package name, and its post-install check, with tab-level copy claiming nothing about a specific plugin; the page has no action control, Host call, or Remote dependency | PM-019, PM-021 | client registration + server-rendered component unit tests + packed client-bundle E2E |
+| A-024 three immutable plugin sources produce one deeply immutable plan and token, execute serially after one confirmation, expose per-child outcomes, stop/skip after failure, cancel without starting later children, and reject duplicates, invalid bounds, or aggregate stale state before mutation | PM-009, PM-010, PM-015, PM-017, PM-018 | plan/operation unit + conversation tool + fake-CLI manager integration |
+| A-025 multi-install planning deduplicates missing peer dependencies, excludes optional peers and peers already installed or requested, suggests but never silently installs companions, and successful operations terminate as `succeeded`, `succeeded_restart_required`, or `waiting_for_manual_restart` according to activation and restart availability | PM-013, PM-015, PM-016, PM-022 | source/plan unit + manager integration + opt-in real Codex/Files/Terminal DSH CLI lifecycle |
+| A-026 a valid Session-bound plan opens one plugin-owned DSH `plan-review` question; no mutation starts before an answer, and the exact single approve answer executes once without a typed chat message | PM-009, PM-023 | conversation state-machine unit + real UserQuestionService integration |
+| A-027 decline, malformed/unrelated/custom answers, provider failure/cancellation, cross-session use, pre-prompt expiry, expiry while waiting, and approval replay never cause an unauthorized mutation; a still-valid rejected plan remains retriable, while later-message `execute` remains supported | PM-009, PM-023 | negative confirmation matrix + manager expiry/replay integration |
+| A-028 explicit, natural-language, and conservative bare GitHub owner queries issue an exact owner-qualified search, verify ownership, rank inspected owner plugins ahead of unrelated rows, expose owner/provider/reason metadata, and fall back from an empty inferred hint to keyword search | PM-005, PM-006, PM-024 | query/provider unit + mixed-provider search integration + opt-in live owner search |
+| A-029 `github.com/owner/repo`, canonical HTTPS, and `github:owner/repo` inspect to the same immutable plugin; emitted repository identities round-trip into inspect and recommended sources round-trip into install planning | PM-007, PM-008, PM-024 | source unit + manager integration + opt-in live schemeless inspection |
+| A-030 owner-only inspect forms return actionable search guidance while malformed, unsafe, and non-GitHub inputs remain rejected without weakening source validation | PM-018, PM-024 | source/manager negative unit |
+| A-031 search results feed one immutable multi-install plan through the real DSH tool and user-question registries; no mutation starts before one exact UI approval, then child installs execute serially and approval replay is rejected | PM-002, PM-005, PM-009, PM-010, PM-015, PM-023, PM-024 | combined host/tool/search/question/manager integration |
 
 ## Test Layers
 
@@ -45,7 +53,8 @@ injected fakes.
 Use temporary profiles and an in-process fake official CLI runner that performs
 the same manifest/bundle changes DSH owns. Exercise real manager orchestration,
 postconditions, rollback, operation polling, cancellation, Loader state, actual
-DSH command/tool registries, and model-tool execution.
+DSH command/tool/user-question registries, controlled confirmation, and
+model-tool execution.
 
 ### E2E
 
@@ -68,7 +77,11 @@ commit, and sanitized output.
 The current evidence record is
 [`live-codex-2026-08-26.md`](./live-codex-2026-08-26.md). The real
 conversation and Loader record is
-[`release-candidate-2026-08-26.md`](./release-candidate-2026-08-26.md).
+[`release-candidate-2026-08-26.md`](./release-candidate-2026-08-26.md). GitHub
+owner discovery and schemeless repository round-trip evidence is recorded in
+[`live-owner-discovery-2026-08-28.md`](./acceptance/live-owner-discovery-2026-08-28.md).
+The cumulative `0.1.0-rc.4` release decision and A-031 evidence are recorded in
+[`release-candidate-0.1.0-rc.4.md`](./acceptance/release-candidate-0.1.0-rc.4.md).
 
 ## Review Gates
 

package/docs/technical-design.md

@@ -9,7 +9,7 @@ The bundle mounts two Host entries:
    model tools, and `/plugins`.
 
 It also ships one browser client entry that registers a static, read-only
-Plugin Marketplace help tab in `settings.plugins.tab`. The client has no Remote
+recommended-plugins help tab in `settings.plugins.tab`. The client has no Remote
 dependency and exposes no management action. There is no management HTTP route.
 
 ## Request Flow
@@ -31,8 +31,10 @@ natural language --------------------------+
                                                                |
                                                      restart fallback
 
-Settings > Plugins > Plugin Marketplace
+Settings > Plugins > Recommended plugins  (first tab, opened by default)
         |
+        +-- one card per recommended plugin: package name + purpose
+        |                                  + requires / install message / check
         +-- localized Chat examples only (no Host call or mutation control)
 ```
 
@@ -48,12 +50,24 @@ Two model tools are sufficient:
 - management separates planning from execution and also owns operation status
   and cancellation.
 
-The tool descriptions instruct the model to show a plan and wait for a later
-affirmative user message before calling `execute`. The conversation adapter
-also binds each token to the Agent Session and its latest `user/message` seq at
-planning time. Same-turn and cross-session execution fail before the manager
+The tool descriptions instruct the model to show a plan and then use one of two
+confirmation paths. `confirm` asks through the plugin-owned DSH choice UI and,
+on an exact approval, executes in the same tool call. `execute` remains the
+plain-chat path and requires a later affirmative user message. The conversation
+adapter binds each token to the Agent Session and its latest `user/message` seq
+at planning time. Same-turn and cross-session execution fail before the manager
 can consume the token.
 
+The plugin-owned question has a plan-derived stable id, visible plan detail,
+fixed approve and decline labels, single-selection semantics, and DSH's
+`plan-review` intent. The adapter accepts only one answer with that exact id,
+the exact approve label, and no custom text. It never interprets results from a
+generic, model-authored `ask_user_question` call as mutation authority.
+Declines, malformed answers, provider errors, and cancellation leave a valid
+token retriable. Expiry is checked both before opening UI and atomically by the
+manager when approval returns, covering a plan that expires while the UI is
+open.
+
 ## Source Resolution
 
 The core recognizes only this closed union:
@@ -87,11 +101,25 @@ candidate when the registry search ranking omits it. This is not trusted as an
 installation result: the same core registry metadata, integrity, manifest, and
 DSH-surface inspection still runs before it can be returned.
 
+The query parser also recognizes explicit GitHub owner forms and conservative
+bare-owner hints. A typed owner intent reaches the GitHub provider, which uses
+`user:<owner> topic:dsh-plugin`, verifies every returned `full_name` owner, and
+marks exact matches structurally. Inferred bare hints fall back to the ordinary
+keyword query when the owner search returns no repositories. Exact typed
+matches sort before provider-local rank; local scores remain incomparable.
+
+Search results expose the canonical repository owner, aggregate provider ids,
+and bounded match reasons in addition to per-source provenance. The emitted
+`github.com/owner/repo` identity is itself an accepted source, so it can flow
+directly into `inspect`; `recommendedSource` is immutable and can flow directly
+into `plan`. Owner-only identities fail inspection with guidance to use owner
+search instead of falling through to npm validation.
+
 No provider callback participates after discovery.
 
 ## Confirmation Plans
 
-Plans live in memory for ten minutes. Each carries:
+Plans live in memory for ten minutes. A single-mutation plan carries:
 
 - operation and profile;
 - package/source and immutable target where applicable;
@@ -105,6 +133,15 @@ compares the planned dependency source with the current profile and refuses a
 stale plan. This prevents confirmation replay, plan substitution, and mutation
 after an out-of-band profile change.
 
+An `install_many` plan contains an ordered, bounded list of the same immutable
+install items under one digest and confirmation token. Nested plan data is
+deeply frozen. Planning resolves every source before creating the plan, rejects
+duplicate package identities, and reports required peer dependencies that are
+absent from both the profile and the requested list. Peers marked optional in
+`peerDependenciesMeta` are excluded. Missing peers are advisory: the manager
+suggests their npm source but does not silently expand the confirmed mutation
+scope.
+
 ## Package Mutations
 
 The runner reuses the current DSH installation. When the current Node entry is
@@ -112,14 +149,28 @@ an existing file, it invokes `process.execPath <current-entry> plugin ...`;
 otherwise it uses explicit `DSH_EXECUTABLE` or the `dsh` command. Arguments are
 always an array. Windows shell fallback is limited to a bare `.cmd` executable.
 
-Only one mutation runs at once. Output is bounded and exposed as progress.
-Cancellation sends SIGTERM and later SIGKILL if needed.
+Only one top-level mutation runs at once. Additional confirmed operations enter
+a FIFO and retain `queued` status instead of failing busy. Plans are checked
+again when they leave the queue so an intervening mutation cannot execute a
+stale target. An `install_many` operation owns one queue slot and invokes child
+installs serially, so child work never competes for the tracker. The batch stops
+on the first child failure, retains earlier successes, and marks later children
+skipped. Output is bounded and exposed as progress. Cancellation removes queued
+work without starting it, or reaches the active child and prevents later
+children from starting.
 
 After add succeeds, the manager verifies the saved immutable dependency, the
 installed package name and exact npm version, a declared DSH surface, and exact
 bundle membership before reporting success. A failed check restores the saved
 profile manifest and reports a failed operation.
 
+Tracked operations have explicit restart-aware terminal states. A successful
+mutation that needs a separately confirmed restart finishes as
+`succeeded_restart_required` when the restarter is available, or
+`waiting_for_manual_restart` when the deployment requires an operator action.
+The mutation itself is complete in both cases; it is never left `running` while
+waiting for restart.
+
 ## Enablement
 
 DSH has Loader-entry enablement, not a native package-level boolean. The manager