release-skill 0.9.20 → 0.9.22

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "release-skill",
-  "version": "0.9.20",
+  "version": "0.9.22",
   "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
   "author": {
     "name": "广州市风荷科技有限公司"

package/.codebuddy-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "release-skill",
-  "version": "0.9.20",
+  "version": "0.9.22",
   "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
   "author": {
     "name": "广州市风荷科技有限公司"

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "release-skill",
-  "version": "0.9.20",
+  "version": "0.9.22",
   "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
   "author": {
     "name": "广州市风荷科技有限公司"
@@ -19,7 +19,7 @@
     ],
     "defaultPrompt": [
       "Assess this project for release readiness.",
-      "Prepare a release plan for version 0.9.20.",
+      "Prepare a release plan for version 0.9.22.",
       "Help me understand the release workflow."
     ]
   }

package/.cursor-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "release-skill",
-  "version": "0.9.20",
+  "version": "0.9.22",
   "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
   "author": {
     "name": "广州市风荷科技有限公司"

package/.kimi-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "release-skill",
-  "version": "0.9.20",
+  "version": "0.9.22",
   "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
   "author": {
     "name": "广州市风荷科技有限公司"

package/.qoder-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "release-skill",
-  "version": "0.9.20",
+  "version": "0.9.22",
   "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
   "author": {
     "name": "广州市风荷科技有限公司"

package/CHANGELOG.md

@@ -1,5 +1,59 @@
 # Changelog
 
+<!-- release-skill:changelog:start version=0.9.22 locale=en baseline=sha256:5b9ca7ff99b3d072831f4f114ff4830f6d76540f7c5262fd1deb97eaec9d0a57 -->
+## [0.9.22] - 2026-09-17
+
+0.9.22 is a local source candidate that fixes two failures found during the real-host rollout of 0.9.21. CodeBuddy and WorkBuddy keep the same frozen Hub identity and installed-payload checks. Foundation dependencies remain pinned to 0.21.0. This note is not evidence of publication, real-host acceptance, consumer installation verification, or independent acceptance.
+
+### Security
+
+- Hub publication remains a compare-and-swap operation. A partial Hub publication is never rolled back or force-pushed automatically.
+- A Hub marketplace reported as github is accepted only on the Hub-backed CodeBuddy/WorkBuddy path. The updater still verifies the checkout origin, branch, HEAD, host-specific index, installed revision, and complete frozen payload.
+- WorkBuddy reuses the existing strict residual_process_group envelope only when the child exited successfully and Foundation reports the exact cleanup evidence. Any field mismatch fails closed before later writes.
+
+### Changed
+
+- Skill Family Hub remains the central marketplace, and its release entry continues to use the existing GitHub Git Data API after release verification.
+
+### Fixed
+
+- CodeBuddy 2.148.0 can now update an existing Hub plugin when its official marketplace list reports type github instead of type git.
+- WorkBuddy can complete the same existing-plugin update when its embedded CodeBuddy CLI exits successfully but leaves a process group that Foundation has already terminated and verified.
+
+### Upgrade Notes
+
+Upgrade from 0.9.21 before running local host finishing for CodeBuddy or WorkBuddy. No configuration migration is required. Remove the old release-skill standalone marketplace; use the ifoohoo/skill-family-hub repository and Hub-qualified plugin id release-skill@skill-family-hub. Reload or restart each updated host before claiming that 0.9.22 is loaded.
+<!-- release-skill:changelog:end version=0.9.22 locale=en -->
+
+
+<!-- release-skill:changelog:start version=0.9.21 locale=en baseline=sha256:90f61122ebbbe5f53bc95be7049aaaab4401e19cc805e76be525e9a74bf0a360 -->
+## [0.9.21] - 2026-09-17
+
+0.9.21 is a local source candidate that enables automatic local updates for Claude, Codex, Kimi, CodeBuddy, and WorkBuddy when the frozen plan declares a Hub source. Qoder and Cursor retain their existing paths. Foundation dependencies remain pinned to 0.21.0. This note is not evidence of publication, real-host acceptance, consumer installation verification, or independent acceptance.
+
+### Security
+
+- Hub publication remains a compare-and-swap operation. A partial Hub publication is never rolled back or force-pushed automatically.
+- CodeBuddy and WorkBuddy only upgrade existing installations and reject a Hub branch that moves before plugin update.
+- Kimi uses the frozen GitHub Release; its repository-only Hub entry is not treated as tag or commit evidence.
+- Completed postVerify lineage, host selection, plan-digest confirmation, and full installed-payload verification remain required. Host failures preserve the results of other selected hosts.
+
+### Changed
+
+- Skill Family Hub remains the central marketplace, and its release entry continues to use the existing GitHub Git Data API after release verification.
+
+### Fixed
+
+- Hub-only plans now produce executable local host targets without recreating legacy installation actions or distributions.
+- Claude, Codex, CodeBuddy, and WorkBuddy verify their host-specific Hub entries and installed payloads against the frozen release identity.
+- Kimi retains http_proxy, https_proxy, and all_proxy in the process that performs its controlled terminal installation.
+
+### Upgrade Notes
+
+Upgrade from 0.9.20 to automate the five previously manual Hub-backed hosts. No configuration migration is required. Remove the old release-skill standalone marketplace; use the ifoohoo/skill-family-hub repository and Hub-qualified plugin id release-skill@skill-family-hub. Claude can verify an exact current installation offline. Codex performs its existing remove/install flow when its list does not provide an installation root. Installed does not mean loaded: reload or restart the host and confirm the loaded version.
+<!-- release-skill:changelog:end version=0.9.21 locale=en -->
+
+
 <!-- release-skill:changelog:start version=0.9.20 locale=en baseline=sha256:b1fff0e015af8eb8c97c5a466bcd4f9aa879b1e9fe0622ed3281e55747ff9e1e -->
 ## [0.9.20] - 2026-09-17
 

package/INSTALL.md

@@ -2,7 +2,7 @@
 
 [简体中文](INSTALL.zh-CN.md)
 
-<!-- release-skill:release-version: 0.9.20 -->
+<!-- release-skill:release-version: 0.9.22 -->
 ## Prerequisites
 
 - Node.js 22.0.0 or later
@@ -125,7 +125,7 @@ tag pinned to the exact version (never the bare repository URL, which installs
 the latest release or default branch), confirm the trust prompt, then reload:
 
    ```
-   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.20
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.22
    /plugins reload
    ```
 

package/INSTALL.zh-CN.md

@@ -2,7 +2,7 @@
 
 [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.9.20 -->
+<!-- release-skill:release-version: 0.9.22 -->
 ## 前置条件
 
 - Node.js 22.0.0 或更高版本
@@ -113,7 +113,7 @@ release-skill 当前只采用并验证 Kimi Code 的交互式 TUI 路径，**无
 （切勿使用裸仓库地址，它会安装最新 release 或默认分支），确认信任提示后重新加载：
 
    ```
-   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.20
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.22
    /plugins reload
    ```
 

package/README.md

@@ -2,7 +2,7 @@
 
 [简体中文](README.zh-CN.md) · Installation: [English](INSTALL.md) / [简体中文](INSTALL.zh-CN.md)
 
-<!-- release-skill:release-version: 0.9.20 -->
+<!-- release-skill:release-version: 0.9.22 -->
 Release preparation for Claude Code, CodeBuddy, WorkBuddy, Codex, and Kimi Code, with human-edited files kept intact.
 
 release-skill helps a maintainer answer three questions: what will be released,
@@ -14,39 +14,32 @@ Setup surfaces only the deterministic `compactSummary` review view; the full
 report stays in a temporary session directory.
 
 <!-- release-skill:managed:start id=latest-release -->
-**0.9.20** (2026-09-17)
+**0.9.22** (2026-09-17)
 
-0.9.20 is a local source candidate that makes release governance diagnosis easier to select and safer to interpret. Existing public Skills now distinguish adoption assessment, offline release-readiness assessment, and explicit historical-record verification without running target Skills, hooks, builds, or release actions. This release also separates actionable verification-gate drafts from non-actionable diagnostics and corrects Cursor automation capability derivation. The three Foundation dependencies remain pinned to the exact 0.21.0 release. This note is not evidence of publication, real-host acceptance, consumer installation verification, or independent acceptance.
+0.9.22 is a local source candidate that fixes two failures found during the real-host rollout of 0.9.21. CodeBuddy and WorkBuddy keep the same frozen Hub identity and installed-payload checks. Foundation dependencies remain pinned to 0.21.0. This note is not evidence of publication, real-host acceptance, consumer installation verification, or independent acceptance.
 
 **Security**
 
-- Read-only governance diagnosis does not execute target Skills, business scripts, builds, hooks, prepare, verify, or release-finish.
-- Historical verification remains limited to files supplied explicitly by the maintainer and does not claim author identity, target execution, current artifact identity, or current remote state.
 - Hub publication remains a compare-and-swap operation. A partial Hub publication is never rolled back or force-pushed automatically.
-
-**Added**
-
-- Public help and assessment guidance now routes read-only governance requests to the one check that matches the maintainer's intent: adoption status, offline readiness gaps, or explicit historical-record consistency.
-- Adoption reports expose non-actionable discovered scripts in `gateDiagnostics`, while `gateSuggestions` remains limited to actionable, not-yet-configured drafts.
+- A Hub marketplace reported as github is accepted only on the Hub-backed CodeBuddy/WorkBuddy path. The updater still verifies the checkout origin, branch, HEAD, host-specific index, installed revision, and complete frozen payload.
+- WorkBuddy reuses the existing strict residual_process_group envelope only when the child exited successfully and Foundation reports the exact cleanup evidence. Any field mismatch fails closed before later writes.
 
 **Changed**
 
-- English and Chinese README guidance now documents the read-only governance boundary and preserves the existing authorization contract for setup and release work.
-- Release assessment guidance states what each historical-record result proves and avoids treating a historical terminal status as evidence about current artifact bytes or remote state.
 - Skill Family Hub remains the central marketplace, and its release entry continues to use the existing GitHub Git Data API after release verification.
 
 **Fixed**
 
-- Cursor's `foundation-host-verification` installation method now derives `automatable: true`, matching the published host descriptor instead of being treated as manual-only.
-- Derived-artifact verification now exercises write mode in an isolated replica, so the real workspace remains read-only during the check.
+- CodeBuddy 2.148.0 can now update an existing Hub plugin when its official marketplace list reports type github instead of type git.
+- WorkBuddy can complete the same existing-plugin update when its embedded CodeBuddy CLI exits successfully but leaves a process group that Foundation has already terminated and verified.
 
 **Upgrade Notes**
 
-Upgrade from 0.9.19 to use the clearer governance entry guidance, actionable-only `gateSuggestions`, the new `gateDiagnostics` field, and corrected Cursor automation derivation. No configuration migration is required. Remove the old release-skill standalone marketplace; use the ifoohoo/skill-family-hub repository and Hub-qualified plugin id release-skill@skill-family-hub. This release does not add the deferred public conclusion-file output or engineering dependency-fact interface.
+Upgrade from 0.9.21 before running local host finishing for CodeBuddy or WorkBuddy. No configuration migration is required. Remove the old release-skill standalone marketplace; use the ifoohoo/skill-family-hub repository and Hub-qualified plugin id release-skill@skill-family-hub. Reload or restart each updated host before claiming that 0.9.22 is loaded.
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **Current boundary:** v0.9.20 is the current source candidate. This README
+> **Current boundary:** v0.9.22 is the current source candidate. This README
 > records intended scope and verification boundaries; it is not evidence of
 > publication, consumer-installation verification, or independent acceptance.
 > Release availability must be established from the corresponding release records
@@ -70,7 +63,7 @@ Upgrade from 0.9.19 to use the clearer governance entry guidance, actionable-onl
 > publish global preflight.
 
 <!-- release-skill:capability:safe-first-command -->
-> **Production path verified since the v0.1.1 milestone; v0.9.20 is the current
+> **Production path verified since the v0.1.1 milestone; v0.9.22 is the current
 > source candidate. Its README does not establish publication,
 > consumer-installation verification, or independent acceptance.**
 > The npm-installed CLI is the supported user entry. Source checkout
@@ -99,7 +92,7 @@ checkpoints remain intact and use matching-version recovery. Evidence v1 stays
 read-only; v2 uses a closed top level with phase extensions in `details`.
 Summaries and recovery suggestions are diagnostic, never publication authority.
 
-The current 0.9.20 candidate includes the narrow R-05 Hook cache v2 consumer
+The current 0.9.22 candidate includes the narrow R-05 Hook cache v2 consumer
 path, the public `postverify` path, and the stable isolated install-tree record
 path (A2/A3). It also adds the explicit-input `verify-records` command and a
 self-contained Qoder projection, first-class Cursor packaging, and the
@@ -884,15 +877,18 @@ run. The core prepare, publish, and verify workflow remains cross-platform.
 A release unit may also declare `postPublish.localHostUpdate` for a plugin that
 is delivered through a project-selected Hub by a `postVerify` hook. After that
 hook reaches `DISTRIBUTED`, `ship`, `verify`, `post-release`, and
-`release-finish` display the declared Hub, plugin, and hosts. These Hub-backed
-targets retain their declared execution mode. Qoder is executable only when it
-was selected and all frozen-plan, Hub-source, existing user-scope installation,
-and payload checks pass; other Hub-backed targets remain manual. Manual prompts
-do not query the Hub, inspect the host, or run host commands. Claude
-and Codex use their existing marketplace management entry; Kimi uses the
-frozen GitHub Release and its existing confirmation path; CodeBuddy and
-WorkBuddy remain manual because this flow cannot pin a Hub ref. Existing
-executable targets derived from frozen plugin-install actions remain available.
+`release-finish` display the declared Hub, plugin, and hosts. Version 0.9.22
+makes Claude, Codex, Kimi, CodeBuddy, WorkBuddy, and Qoder executable after
+explicit host selection and plan-digest confirmation. Claude and Codex require
+an existing matching Hub marketplace and verify its host-specific entry before
+plugin writes. CodeBuddy and WorkBuddy only upgrade existing installations,
+checking the Hub branch again after refresh. Kimi uses the frozen GitHub Release
+and controlled terminal interaction, preserving all three proxy variables;
+its repository-only Hub file is not tag or commit evidence. Every successful
+update verifies the installed payload against the frozen snapshot. Claude can
+verify an exact current installation offline; Codex reinstalls when its list
+does not expose an installation root. Existing frozen installation actions
+and the Qoder and Cursor paths remain supported without duplicate execution.
 
 Production `prepare` also performs one best-effort retention pass after its new
 run evidence exists and before expensive snapshot and hook work. It removes

package/README.zh-CN.md

@@ -2,45 +2,38 @@
 
 [English](README.md) · 安装指南：[中文](INSTALL.zh-CN.md) / [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.9.20 -->
+<!-- release-skill:release-version: 0.9.22 -->
 面向 Claude Code、CodeBuddy、WorkBuddy、Codex 和 Kimi Code 的发布准备工具，完整保留人工维护的文件内容。
 
 release-skill 帮助维护者回答三个问题：准备发布什么、还有哪些检查未通过、最终发布的内容是什么。它不重新生成、也不回写项目源文件。`prepare` 把每个配置的公开文件复制到隔离快照并验证字节——先冻结并供人工审阅，再从同一份冻结产物发布。`setup` 只显示确定性的 `compactSummary` 审阅视图，完整报告保留在临时会话目录中。
 
 <!-- release-skill:managed:start id=latest-release -->
-**0.9.20** (2026-09-17)
+**0.9.22** (2026-09-17)
 
-0.9.20 是一个本地源码候选。本版本让维护者更容易选择发布治理检查，也更容易判断结果的效力。既有公共 Skill 现在会区分接入评估、离线发布就绪评估和显式历史记录核对；这些只读检查不会运行目标 Skill、hook、构建或发布动作。本版本还把可执行的验证门草案与不可执行的诊断事实分开，并修正 Cursor 自动化能力的派生结果。三项 Foundation 依赖继续精确固定在已发布的 0.21.0。本说明不代表已经发布、完成真实宿主验收、完成消费者安装验证或通过独立验收。
+0.9.22 是一个本地源码候选，修复 0.9.21 真实宿主收尾暴露的两处问题。CodeBuddy 与 WorkBuddy 继续使用同一份冻结 Hub 身份和安装载荷检查。Foundation 依赖保持固定为 0.21.0。本说明不代表已经发布、完成真实宿主验收、完成消费者安装验证或通过独立验收。
 
 **安全**
 
-- 只读治理诊断不会执行目标 Skill、业务脚本、构建、hook、prepare、verify 或 release-finish。
-- 历史核对只读取维护者显式提供的文件，不鉴定作者，也不证明目标实际执行、当前发行物身份或当前远端状态。
 - Hub 发布继续绑定已观察的分支头执行比较后写入。部分发布时不回滚、不覆盖已经成功的远端步骤。
-
-**新增**
-
-- 公共帮助与评估入口现在按维护者的意图区分三类只读请求：判断是否接入、分析离线就绪缺口、核对显式提供的历史记录。
-- 接入报告新增 `gateDiagnostics`，用于保留不能形成执行草案的脚本发现；`gateSuggestions` 只保留尚未配置且能够执行的草案。
+- 只有 Hub-backed CodeBuddy/WorkBuddy 路径接受 github 市场类型。更新器仍核对 checkout 的 origin、分支、HEAD、宿主专用索引、安装修订号和完整冻结载荷。
+- WorkBuddy 只复用现有的严格 residual_process_group 信封。子进程必须成功退出，Foundation 也必须返回精确的清理证据；任一字段不符时，在后续写入前失败关闭。
 
 **变更**
 
-- 中英文 README 补充只读治理边界；实际 setup 和发布工作继续沿用既有授权合同。
-- 发布评估说明明确历史记录核对结果的效力，避免把历史终态误写成当前发行物字节或远端状态的证据。
-- Skill Family Hub 继续作为统一市场；发布完成验证后，release-skill 仍通过既有 GitHub Git Data API 更新 Hub 条目。
+- Skill Family Hub 继续作为统一市场；发布完成验证后，仍通过既有 GitHub Git Data API 更新 Hub 条目。
 
 **修复**
 
-- Cursor 的 `foundation-host-verification` 安装方式现在正确派生为 `automatable: true`，与已发布的宿主描述符保持一致。
-- 派生制品校验把写模式放到隔离副本执行，检查期间不再改写真实工作区。
+- CodeBuddy 2.148.0 的官方市场列表返回 github 类型时，现在可以继续更新既有 Hub 插件。
+- WorkBuddy 的内嵌 CodeBuddy CLI 成功退出，且 Foundation 已清理并验证残留进程组时，现在可以完成同一条既有插件更新路径。
 
 **升级说明**
 
-从 0.9.19 升级后，可以使用更清晰的治理入口说明、只含可执行草案的 `gateSuggestions`、新的 `gateDiagnostics` 字段，以及修正后的 Cursor 自动化能力派生。无需迁移配置。请移除独立的 `release-skill` 市场，改用 ifoohoo/skill-family-hub 仓库与 Hub 限定插件名 release-skill@skill-family-hub。本版本不包含仍在延期的公共结论文件输出和工程依赖事实接口。
+执行 CodeBuddy 或 WorkBuddy 本机宿主收尾前，请从 0.9.21 升级到 0.9.22，无需迁移配置。请移除独立的 `release-skill` 市场，改用 ifoohoo/skill-family-hub 仓库与 Hub 限定插件名 release-skill@skill-family-hub。更新后必须重新加载或重启宿主，确认实际加载 0.9.22 后再报告完成。
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **当前边界：** v0.9.20 只是当前源码候选。本 README 记录预期范围与验证边界，
+> **当前边界：** v0.9.22 只是当前源码候选。本 README 记录预期范围与验证边界，
 > 不代表已经发布、完成消费者安装验证或通过独立验收。
 > 版本可用性以对应发布记录及发布后验证结果为准。
 > v0.4.1 是更早的已发布里程碑（v0.2.2 曾处于已发布状态，后因平台验证收敛修复而更新）。
@@ -56,7 +49,7 @@ release-skill 帮助维护者回答三个问题：准备发布什么、还有哪
 > 远端唯一性检查在 `publish` 全局预检执行。
 
 <!-- release-skill:capability:safe-first-command -->
-> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.9.20 是当前源码候选，本 README 不证明该候选已经发布、完成消费者安装验证或通过独立验收。**
+> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.9.22 是当前源码候选，本 README 不证明该候选已经发布、完成消费者安装验证或通过独立验收。**
 > npm 安装的 CLI 是受支持的用户入口；源码 checkout 保留为开发/贡献者路径。
 >
 > **第一条命令：**
@@ -74,7 +67,7 @@ marketplace 委托目标工作区发布的边界不变。
 
 旧 production 计划缺少 `sourceAuthority` 时，在外部写入前拒绝。未发生外部写入的计划必须重新 prepare 并批准新摘要，不能补写旧计划或迁移批准。已有 `PARTIAL` 保留检查点，走匹配版本的恢复路径。evidence v1 只读；v2 顶层封闭，阶段扩展放在 `details`。摘要和恢复建议只作诊断，不构成发布权威。
 
-当前 0.9.20 候选包含窄范围的 R-05 Hook cache v2 消费路径、公开 `postverify`
+当前 0.9.22 候选包含窄范围的 R-05 Hook cache v2 消费路径、公开 `postverify`
 路径和稳定隔离安装树记录路径（A2/A3），并增加只接受显式输入的 `verify-records`
 命令、自包含 Qoder 投影、Cursor 正式打包，以及基于 Foundation 的宿主核验桥。
 Skill Family Hub 仍是唯一市场来源。
@@ -740,12 +733,14 @@ verify run；核心 prepare、publish、verify 流程仍跨平台。
 
 如果插件由项目选定的 Hub 通过 `postVerify` Hook 交付，发布单元还可以声明
 `postPublish.localHostUpdate`。Hook 达到 `DISTRIBUTED` 后，`ship`、`verify`、
-`post-release` 和 `release-finish` 会显示声明中的 Hub、插件和宿主。0.9.14 对这类
-目标保留各自声明的执行模式。只有用户已选择 Qoder，且冻结计划、Hub 来源、既有用户
-范围安装和载荷核对全部通过时，Qoder 才进入可执行分支；其他 Hub-backed 目标仍为人工
-入口。人工提示不会访问 Hub、探测宿主或运行宿主命令。Claude 和 Codex 使用各自已有的 marketplace 管理入口；Kimi
-使用冻结 GitHub Release 和现有人工确认路径；CodeBuddy 与 WorkBuddy 因无法固定 Hub
-ref 而继续人工处理。由冻结插件安装动作派生的原有可执行目标不受影响。
+`post-release` 和 `release-finish` 会显示声明中的 Hub、插件和宿主。0.9.22 让 Claude、
+Codex、Kimi、CodeBuddy、WorkBuddy 和 Qoder 在用户选择宿主并确认计划摘要后进入执行。
+Claude 和 Codex 要求已有同源 Hub 市场，并在插件写入前核对宿主专用条目。CodeBuddy
+与 WorkBuddy 只升级既有安装，刷新市场后再次检查 Hub 分支是否漂移。Kimi 使用冻结
+GitHub Release 和受控终端交互，保留三个代理变量；只有仓库 URL 的 Hub 文件不作为
+标签或提交证据。更新成功前必须把实际安装载荷与冻结快照比较。Claude 可离线复验
+精确当前安装；Codex 列表没有安装根时仍须正式重装。旧安装动作与 Qoder、Cursor
+路径继续可用，身份一致的重复目标只执行一次。
 
 生产 prepare 还会在本轮运行证据建立后、高成本快照和 Hook 之前执行一次尽力清理。
 它只删除已被更新完整谱系取代的终态运行目录，以及没有有效计划或外部写入迹象的封口

package/adapters/claude/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "release-skill",
-  "version": "0.9.20",
+  "version": "0.9.22",
   "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
   "author": {
     "name": "广州市风荷科技有限公司"