docs(dsh-plugin): refresh catalog install recovery guidance

[mikamikasuki]

Goal and Delivered Outcome

The DSH plugin recovery guide still said the catalog selected beta.5, described release readback as needing another repair, and sent users to install dsh-loopx-plugin from npm. The current public catalog points to the beta.6 GitHub release asset, DSH Plugin Hub v1.6.0 includes the relevant readback and desktop-install fixes, and the npm package is not published.

This change updates the guide with the current catalog route and profile-specific Hub command, keeps the beta.6 tarball as a direct-install fallback, and distinguishes the published artifact from a local source build. It is related to #5947; the issue's specific wrapper failure remains undiagnosed because its inner install log is unavailable.

• Outcome basis: the existing DSH plugin installation and recovery guide, checked against the public catalog, release asset, Hub release notes, and npm registry.
• Observable before → after: obsolete beta.5/readback/npm guidance → current beta.6 catalog route, profile-specific Hub guidance, and a valid direct tarball fallback.
• Issue/task and intended base: related to [dsh-plugin.org | dsh-plugin-hub] plugin install failed: loopx-project/loopx #5947; base main at 647e216.

Author Declaration

• Written by: model_agent — OpenAI GPT-6 Luna.

Implemented against

• Specification and revision: no written specification; the current catalog entry and DSH Plugin Hub release guidance were checked against LoopX base 647e216.

Criterion	Disposition	Symbol / path	Test or command
Recovery guide names the published release and catalog route	implemented	packages/dsh-loopx-plugin/README.md	Public catalog and GitHub release asset readback
Hub upgrade guidance matches profile behavior	implemented	packages/dsh-loopx-plugin/README.md	DSH Plugin Hub v1.6.0 release notes
Install instructions do not point to an unpublished npm package	implemented	packages/dsh-loopx-plugin/README.md	npm view dsh-loopx-plugin@0.1.1-beta.6 version dist.tarball --json returned 404

• Self-check: reviewed the single-file diff against current main, rechecked six targeted content assertions, and confirmed the exact npm package lookup returns 404.

Scope And Continuation

• Completed scope: corrected the documented release, catalog, Hub upgrade, and direct-install instructions.
• Remaining work: [dsh-plugin.org | dsh-plugin-hub] plugin install failed: loopx-project/loopx #5947's exact failure still requires the reporter's underlying install log; this PR does not close that report.

Validation

• Tested revision: 66cf6a9 (base 647e216)
• Run state: finished
• Input classes: public_fixture

Check kind	Result	Public-safe evidence / limitation
static	passed	git diff --check 647e216...HEAD; no whitespace errors.
static	passed	loopx check --scan-path packages/dsh-loopx-plugin/README.md: zero errors; two warnings because the local registry file is absent in this environment.
manual	passed	Six assertions verify beta.6 release wording, catalog and Hub links, profile command, and removal of obsolete npm and beta.5 claims.
hosted	in progress	Summary passed; DCO sign-off, dependency review, and Ubuntu/Windows DSH distribution checks queued; merge-gate expected.

• Coverage and gaps: documentation-only change; runtime installation was not run. The reported [dsh-plugin.org | dsh-plugin-hub] plugin install failed: loopx-project/loopx #5947 environment failure remains unverified.

Frontend / Visual Evidence

• UI impact: none
• Before: N/A
• After: N/A
• States and viewports shown: N/A
• Source data: public catalog and release metadata
• Attention review: not applicable; this changes package README text, not an interactive surface.

Type of Change

• Documentation update

LoopX Area

• Public docs or presentation surface

Technical Direction

• N/A; no behavior or architectural direction changed.

Shared-authority RFC fixture impact

• N/A; no shared-authority or control-plane behavior changed.

Boundary Checklist

• No private state, credentials, raw traces, internal links or local paths are included.
• No maintainer-owned benchmark work is duplicated.
• Scope is limited to the DSH plugin installation guide.
• UI impact is marked none.
• The commit includes a DCO Signed-off-by trailer.

[loopx-agent]

Reviewer: actor_kind=model_agent; model=gpt-6.1-sol; provider=OpenAI; declaration_source=runtime_reported; reasoning_effort=xhigh.

精确 head 66cf6a95362820041d60dc1c8a634c521f268dc8，不可变PR差异基线 647e216bacc0a69368dccc18fcb52dcba6002553；全量差异已核验。

动机

从 DSH Plugin Hub 安装或升级 LoopX 的用户，需要能按恢复指南拿到文档承诺的发行包。 原恢复段落说在线 catalog 仍选 beta.5；新段落说链接的在线安装页已经指向 beta.6，并让用户升级 Hub 后从那里安装。我实际打开该页，复制命令仍固定到 beta.5，所以这条新指引目前不能提供承诺的 beta.6。 已核实 beta.6 GitHub发行包存在、npm包查询404、Hub1.6.0发布说明包含相关修复；但同一真实catalog页面与新段落的版本承诺相矛盾，需改正文案后才能完成这次恢复指导更新。 本次只修改包README恢复段落，不修改安装器或运行权限，不关闭#5947的未诊断环境故障，不声称已完成Windows、真实Bot或安装/更新/卸载验收。

改动思路

保留已核实的发行包、npm状态与profile升级指引，把“源catalog已更新”和“在线入口实际已更新”分开；在在线页正确前将直接beta.6固定URL作为明确操作路径，不要求新增版本路由或控制面机制。 安装恢复信息应留在现有包README，并复用既有固定release URL与profile语义；这个小范围无需新开关、provider或状态owner。 当前PR边界是已有安装恢复指导的事实更新；在线入口仍beta.5这个事实必须诚实写出，真实环境故障继续由#5947的原诊断入口处理。

具体改动

关键代码讲解

这里的三个节点都是现有README段落，未增加运行函数；完整差异仅 packages/dsh-loopx-plugin/README.md，+18/-12。

• 第397–399行明确已发布beta.6与本地同版本构建的区别。我独立核实beta.6发行包及其固定asset。
• 第407–416行改为在线catalog beta.6及Hub1.6.0/profile升级指引。Hub1.6.0说明支持profile指引与相关修复；但catalog当前事实不成立，见下列阻塞。
• 第418–425行明确npm包未发布，提供直接beta.6 URL与原有source installer。实际公开npm精确查询E404；web/desktop替换仍是原有profile作用域，未授权修改账户或自动安装。

判断依据为修改前 packages/dsh-loopx-plugin/README.md，修订 647e216bacc0a69368dccc18fcb52dcba6002553，第 6 项 marketplace closeout：catalog合并或listing不等于实际消费固定发行包。这里只要求当前事实和操作路径诚实，不把完整运行安装验收变成文档修正的前置。

[P2，阻塞] 第407–412行：不要把catalog源更新等同链接页面已更新。 我在真实浏览器打开该精确链接，How to Install仍显示：

dsh plugin --profile web add https://github.com/loopx-project/loopx/releases/download/dsh-loopx-plugin-v0.1.1-beta.5/dsh-loopx-plugin-0.1.1-beta.5.tgz

source catalog PR6633已合并，当前YAML确实beta.6；两者是不同消费者。用户按新段落从链接安装页复制命令会选择beta.5，和“current entry points to beta.6”相矛盾。最小修复是在部署读回前明确该lag，并直接引导使用已核实的固定beta.6 URL；或等外部页真正刷新后读取该命令再作声明。只检查字符串存在/删除会漏掉这个反例。

非阻塞的同文一致性建议：第154–156行仍说Hub PR98需要合并/发布；官方已合并并由Hub1.5.0发布。更新恢复段落时可一并退掉这条旧结论。

对主干的风险

同一真实页面读回下，base明确beta.5的版本句符合实际，head beta.6句失败；独立版本比较保留该差异，没有把全文当等价。官方release、Hub98/1.5.0/1.6.0、source catalog与npm分别检查，避免用一处source成功替代用户入口。HTTP直读先遇403，后来通过真实Ego页面恢复并取得命令；没有把403记作成功。

diff check通过；首屏和recovery之前完整前缀字节不变，既有default-off、authority和版本兼容条款保留。包README属于分发文档，未改变自动加载skill、安装器或运行导出，因此无须为此docs改动补全产品frontend/机器状态测试。没有执行安装/更新/卸载、Windows或真实Bot路径；#5947的内部失败日志仍不可得，这些均未认证。没有查询或等待CI。

我的整体评价

REQUEST_CHANGES。正确的发行包/npm/profile信息有价值，范围和既有owner合适，但当前catalog版本承诺是可复现的文档回归，尚未完成用户可正确选择artifact的恢复结果。长程运行维度不适用：此diff不改持续执行、调度或历史状态；用户路径维度有回归：指引的真实入口仍选旧包。维护性检查建议直接修正文案及邻近旧Hub98结论，暂不增加抽象；不要求此PR修复#5947未知故障或认证整个安装系统。

English verdict: REQUEST_CHANGES - head 66cf6a9. The single README update correctly distinguishes published beta.6 from local builds, documents unpublished npm status and aligns Hub profile guidance with official releases. However, the exact linked live catalog still offers beta.5 in its How to Install command, contradicting lines 407-412 and the recommended route; merged source catalog beta.6 is not deployed-consumer evidence. Disclose lag/use the verified direct beta.6 URL or re-read the genuinely updated page. Existing activation/authority text and first viewport are unchanged; actual installation and #5947 diagnosis remain unverified. CI was not consulted.