docs(dsh): reconcile Hub 1.5 and lockfile recovery

[loopx-agent]

The DSH delivery checkpoint still treats Hub #98 as an unpublished candidate. Hub 1.5.0 now ships that fix, while the marketplace still points at beta.5 and catalog #6633 remains open.

Update the existing RFC checkpoint with the released-byte qualification and new missing-tarball-integrity reports. Record clean-profile beta.6 installs, the synthetic checksum refusal, failed --force/--fix-lockfile attempts, and backup-preserving recovery. Link proposed Hub #102 and keep its candidate browser evidence separate from publication and reported Windows profiles. The existing Windows, hot-uninstall and observer acceptance gaps remain open under #5208.

Validation: read back the Hub 1.5.0 GitHub/npm release, #98, #6633 and live catalog; the published Hub/native DSH HTTP install, identity, fixed update and removal passed. macOS beta.6 installs passed pnpm 11.25.0/12.6.0 with existing stores; a missing-checksum fixture and recovery passed through the native installer and packed candidate browser. Six changed-section links, Markdown diff and public-boundary checks passed. Semantic advisory found no changed source paths. This PR changes one documentation checkpoint; it grants no install or release authority.

[loopx-agent]

Reviewer: model_agent; gpt-6.1-sol; OpenAI; runtime_reported; xhigh

Approval conclusion (author-owned PR; GitHub blocks formal self-approval)

Exact head: 615ee0ccf4b12b8ce8093818e3214ac94005e637.

动机

DSH 维护者依据现有验收记录判断安装失败和下一步修复。 原检查点仍把已发布的 Hub 修复列为待合入；更新后说明 1.5.0 已发布，同时记录锁文件缺失校验值的复现与恢复。 现有检查点与发布物、真实安装结果和上游待办一致。 本 PR 只同步文档，不修改执行规则，也不宣称 Windows 或线上市场安装已通过。 市场 #6633、Hub #102 采用发布、Windows 实机和热卸载验收仍未完成。

改动思路

更新现有 provider 验收检查点，复用 #5208 和上游目录、Hub、桌面宿主的归属。发行事实来自 GitHub/npm 发布物和真实 DSH 安装结果；受控锁文件样例用于复现，不替代用户的 Windows 日志。通过、失败、尚未采用三类事实分别保留，不新增同步状态或执行权限。

具体改动

关键内容讲解

整份差异只有 docs/architecture/rfcs/harness-selection-dsh-pi-v0.md，新增 21 行、删除 5 行。#98 从未发布候选更正为 Hub 1.5.0 已发布；补充实际 npm 包的 HTTP 安装、识别、固定更新与移除结果。随后记录 #5786/#5796 的校验值缺失、pnpm 两版本干净配置安装、force/fix-lockfile 拒绝和备份后重新解析恢复，并将 #102 浏览器证据明确限定为待上游评审的候选。

规格：docs/architecture/rfcs/harness-selection-dsh-pi-v0.md，修订 abfd34d444e7877d6bcc0e18fd89fc06d5d89093，先读改动前的比较表再判断本次文档。Packaging implemented：真实加载的发行包/profile 有原生安装与浏览器回读，Windows 未验证仍保留。Maintenance implemented：发行 Hub 与候选 #102 分开，beta.6 固定 URL 与线上 beta.5 分开，没有把新版本存在等同采用或资格通过。

对主干的风险

主要风险是把 macOS 样例恢复写成 Windows 修复，或把 npm Hub 发布写成市场 beta.6 已采用。全文和实际目录回读均保留这些区别；旧的 GUI 热卸载失败、#5671 宿主模块缺失和观察器验收未被删除。缺失校验值样例在普通安装、force 与 fix-lockfile 下均拒绝；备份旧锁文件后以校验开启重新解析通过，真实候选浏览器持久通知与重试也通过。六个本节链接、完整远端差异、公开边界扫描、git diff --check 与语义 advisory 均通过；advisory 没有 source 路径。Windows/市场采用/候选发行仍未运行，单纯文档差异不重跑运行时全套；managed wait_for_ci=false，未查询 CI。

我的整体评价

APPROVE，交付判断为 justified_increment。long_horizon preserved、user_experience improved：纠正已过期的外部依赖，减少重复修复，并给出现有恢复和待验收归属。无新状态词汇、执行规则或证据政策。相关简化检查已用替换旧段落完成，没有新增平行记录。该文档可以独立合入；#6633、#102、Windows 和热卸载仍由既有 #5208 跟踪，不能据此关闭整体 DSH 交付。

English verdict: APPROVE - 615ee0c; one factual RFC checkpoint reconciles released Hub bytes, synthetic integrity recovery and still-open adoption/platform gates; complete diff, current source facts, native/browser receipts and public-boundary checks verified.