release-skill 0.9.19 → 0.9.21

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "release-skill",
-  "version": "0.9.19",
+  "version": "0.9.21",
   "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.19",
+  "version": "0.9.21",
   "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.19",
+  "version": "0.9.21",
   "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.19.",
+      "Prepare a release plan for version 0.9.21.",
       "Help me understand the release workflow."
     ]
   }

package/.cursor-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "release-skill",
-  "version": "0.9.19",
+  "version": "0.9.21",
   "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.19",
+  "version": "0.9.21",
   "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.19",
+  "version": "0.9.21",
   "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
   "author": {
     "name": "广州市风荷科技有限公司"

package/CHANGELOG.md

@@ -1,5 +1,66 @@
 # Changelog
 
+<!-- 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
+
+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.
+
+### 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.
+
+### 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.
+
+### 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.
+<!-- release-skill:changelog:end version=0.9.20 locale=en -->
+
+
 <!-- release-skill:changelog:start version=0.9.19 locale=en baseline=sha256:e0f2dd2aca0b1ca36bb2a95feded3fb291e176c31357f8ba2d390bed4a10184f -->
 ## [0.9.19] - 2026-09-14
 

package/INSTALL.md

@@ -2,7 +2,7 @@
 
 [简体中文](INSTALL.zh-CN.md)
 
-<!-- release-skill:release-version: 0.9.19 -->
+<!-- release-skill:release-version: 0.9.21 -->
 ## 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.19
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.21
    /plugins reload
    ```
 

package/INSTALL.zh-CN.md

@@ -2,7 +2,7 @@
 
 [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.9.19 -->
+<!-- release-skill:release-version: 0.9.21 -->
 ## 前置条件
 
 - 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.19
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.21
    /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.19 -->
+<!-- release-skill:release-version: 0.9.21 -->
 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,40 +14,34 @@ 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.19** (2026-09-14)
+**0.9.21** (2026-09-17)
 
-0.9.19 is a local source candidate that completes the verified-release workflow with a deterministic local finish orchestrator. After publication and postVerify, maintainers can use one public entry to select the source branch outcome, update supported hosts, confirm that each host loaded the target plugin, run the configured setup Skill, and verify the source workspace without changing the release status. 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.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**
 
-- Finish feedback is bound to the current plugin version, project root, selected host, request identity, and execution environment; changing an update decision invalidates earlier setup evidence.
-- No host is considered loaded from filesystem installation alone, and no configured setup is considered complete until its real result is returned through the bound feedback contract.
 - Hub publication remains a compare-and-swap operation. A partial Hub publication is never rolled back or force-pushed automatically.
-
-**Added**
-
-- The local finish entry now accepts `--finish` and emits an ordered plan for branch handling, host updates, load confirmation, configured setup execution, and final source checks.
-- Bound feedback can resume the same finish operation after real host loading and setup execution; JSON and text output expose the same pending, blocked, and complete decisions.
-- The release-finish Skill documents the end-to-end VERIFIED-to-COMPLETE handoff, including the exact request and feedback boundaries used by an agent.
+- 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**
 
-- Finish completion is now separate from the release lifecycle: a successful local finish preserves VERIFIED and reports `releaseStatusChanged: false`.
-- The release help entry is shorter and routes specialized publishing, verification, documentation, marketplace, and finish details to their owning Skills.
 - Skill Family Hub remains the central marketplace, and its release entry continues to use the existing GitHub Git Data API after release verification.
 
 **Fixed**
 
-- Ambiguous setup-plugin selection, missing host candidates, stale setup feedback, and incomplete next-action lists now fail closed instead of producing a false COMPLETE result.
-- Read-only Git observations disable optional index locking and retain exact argv, exit code, stdout, and stderr when a command fails.
+- 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.18 to use the new `post-release --finish` orchestration. Remove the old release-skill standalone marketplace; use the ifoohoo/skill-family-hub repository and Hub-qualified plugin id release-skill@skill-family-hub. Complete the normal publish and postVerify stages first, run the finish entry, perform every requested host load and setup action, then pass the bound feedback file to the same entry until it returns COMPLETE.
+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:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **Current boundary:** v0.9.19 is the current source candidate. This README
+> **Current boundary:** v0.9.21 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
@@ -71,7 +65,7 @@ Upgrade from 0.9.18 to use the new `post-release --finish` orchestration. Remove
 > publish global preflight.
 
 <!-- release-skill:capability:safe-first-command -->
-> **Production path verified since the v0.1.1 milestone; v0.9.19 is the current
+> **Production path verified since the v0.1.1 milestone; v0.9.21 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
@@ -100,7 +94,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.19 candidate includes the narrow R-05 Hook cache v2 consumer
+The current 0.9.21 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
@@ -288,6 +282,16 @@ separate checks. See [the Cursor instructions](INSTALL.md#install-as-a-cursor-lo
 
 See [INSTALL.md](INSTALL.md) for CodeBuddy, Codex, Kimi Code, Qoder, and Cursor commands.
 
+### Read-only governance diagnosis
+
+Use the existing Skills and choose only the check the request needs:
+
+- adoption status: `setup --assess-adoption --root <path> --json`;
+- local configuration and release-readiness gaps: `assess --root <path> --offline --json`;
+- explicit historical plan, approval, and run consistency: `verify-records`, using the full input form in the next section.
+
+These entry points run release-skill's read-only analyzers. Governance diagnosis does not run target Skills, hooks, builds, or release actions, and it does not treat `prepare`, `verify`, or `release-finish` as static governance checks. When a maintainer asks to set up or publish instead, continue through the existing product Skill with the authorization and safety contract for that action.
+
 ### Offline historical record verification
 
 Use the public command below when a consumer already has an explicit plan,
@@ -403,7 +407,9 @@ ACTOR=your-name
    not-yet-configured project returns `NOT_CONFIGURED` with a pointer to
    first-time setup. Hook-duration suggestions are derived only from events
    produced by the current version; the tool never guesses or writes
-   `cacheInputs` for a project.
+   `cacheInputs` for a project. `gateSuggestions` contains only actionable,
+   not-yet-configured drafts; other discoveries remain in `gateDiagnostics`
+   without changing adoption status or the routine summary.
 3. **assess** — read-only readiness:
    ```bash
    "${CLI[@]}" assess --root "$PROJECT" --offline --json
@@ -873,15 +879,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.21
+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,46 +2,40 @@
 
 [English](README.md) · 安装指南：[中文](INSTALL.zh-CN.md) / [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.9.19 -->
+<!-- release-skill:release-version: 0.9.21 -->
 面向 Claude Code、CodeBuddy、WorkBuddy、Codex 和 Kimi Code 的发布准备工具，完整保留人工维护的文件内容。
 
 release-skill 帮助维护者回答三个问题：准备发布什么、还有哪些检查未通过、最终发布的内容是什么。它不重新生成、也不回写项目源文件。`prepare` 把每个配置的公开文件复制到隔离快照并验证字节——先冻结并供人工审阅，再从同一份冻结产物发布。`setup` 只显示确定性的 `compactSummary` 审阅视图，完整报告保留在临时会话目录中。
 
 <!-- release-skill:managed:start id=latest-release -->
-**0.9.19** (2026-09-14)
+**0.9.21** (2026-09-17)
 
-0.9.19 是一个本地源码候选。本版本补齐已验证发布后的本机收尾编排。发布和 postVerify 完成后，维护者可以通过同一个公共入口决定源码分支去向、更新受支持宿主、确认各宿主实际加载目标插件、运行项目配置的 setup Skill，并检查源码工作区；整个过程不会改写发布状态。三项 Foundation 依赖继续精确固定在已发布的 0.21.0。本说明不代表已经发布、完成真实宿主验收、完成消费者安装验证或通过独立验收。
+0.9.21 是一个本地源码候选，补齐冻结计划声明 Hub 来源后，Claude、Codex、Kimi、CodeBuddy 和 WorkBuddy 的本机自动更新。Qoder 与 Cursor 保留原有路径。Foundation 依赖继续固定为 0.21.0。本说明不代表已经发布、完成真实宿主验收、完成消费者安装验证或通过独立验收。
 
 **安全**
 
-- 收尾反馈绑定当前插件版本、项目根目录、选定宿主、请求身份和运行环境；宿主更新决定变化后，旧 setup 证据自动失效。
-- 仅完成文件安装不能证明宿主已经加载插件；已配置的 setup 也只有在真实结果通过绑定反馈返回后才算完成。
 - Hub 发布继续绑定已观察的分支头执行比较后写入。部分发布时不回滚、不覆盖已经成功的远端步骤。
-
-**新增**
-
-- 本机收尾入口新增 `--finish`，按固定顺序给出分支处理、宿主更新、加载确认、setup 执行和源码终检计划。
-- 真实完成宿主加载和 setup 后，可以把绑定反馈交回同一入口继续执行；JSON 与文本输出对待处理、阻断和完成状态给出一致裁决。
-- release-finish Skill 补充从 VERIFIED 到 COMPLETE 的完整交接，并明确智能体执行请求与回传反馈的边界。
+- CodeBuddy 与 WorkBuddy 只升级既有安装；插件写入前发现 Hub 分支漂移时停止。
+- Kimi 直接使用冻结 GitHub Release，不把只有仓库 URL 的 Hub 条目作为标签或提交证据。
+- 继续要求完整 postVerify 谱系、用户选择宿主、确认计划摘要和完整载荷验证。单个宿主失败时保留其他已选宿主的实际结果。
 
 **变更**
 
-- 本机收尾完成与发布生命周期分离：成功结果继续保留 VERIFIED，并明确返回 `releaseStatusChanged: false`。
-- release-help 入口缩短，把发布、验证、文档、市场和收尾细节路由到各自负责的 Skill。
-- Skill Family Hub 继续作为中央市场；发布完成验证后，release-skill 仍通过既有 GitHub Git Data API 更新 Hub 条目。
+- Skill Family Hub 继续作为统一市场；发布完成验证后，仍通过既有 GitHub Git Data API 更新 Hub 条目。
 
 **修复**
 
-- setup 插件选择不唯一、没有宿主候选、setup 反馈过期或后续动作缺失时，流程现在会失败关闭，不再错误返回 COMPLETE。
-- 只读 Git 观察关闭可选索引锁；命令失败时保留精确参数、退出码、标准输出和标准错误。
+- 仅声明 Hub 的计划现在可以生成可执行宿主目标，不再需要旧安装动作或旧宿主 distribution。
+- Claude、Codex、CodeBuddy 和 WorkBuddy 按各自 Hub 索引核对冻结发布身份，并比较实际安装载荷。
+- Kimi 终端安装进程保留 http_proxy、https_proxy 和 all_proxy 三个代理变量。
 
 **升级说明**
 
-从 0.9.18 升级后可使用新的 `post-release --finish` 编排。请移除独立的 `release-skill` 市场，改用 ifoohoo/skill-family-hub 仓库与 Hub 限定插件名 release-skill@skill-family-hub。先完成正常发布与 postVerify，再运行收尾入口，实际完成其请求的宿主加载和 setup 动作，并把绑定反馈交回同一入口，直至结果为 COMPLETE。
+从 0.9.20 升级后，原先只能人工处理的五个 Hub 宿主可自动更新，无需迁移配置。请移除独立的 `release-skill` 市场，改用 ifoohoo/skill-family-hub 仓库与 Hub 限定插件名 release-skill@skill-family-hub。Claude 可以离线复验精确当前安装；Codex 列表不提供安装根时继续使用既有卸载再安装流程。安装完成不代表会话已加载新版，仍需重新加载或重启宿主并确认版本。
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **当前边界：** v0.9.19 只是当前源码候选。本 README 记录预期范围与验证边界，
+> **当前边界：** v0.9.21 只是当前源码候选。本 README 记录预期范围与验证边界，
 > 不代表已经发布、完成消费者安装验证或通过独立验收。
 > 版本可用性以对应发布记录及发布后验证结果为准。
 > v0.4.1 是更早的已发布里程碑（v0.2.2 曾处于已发布状态，后因平台验证收敛修复而更新）。
@@ -57,7 +51,7 @@ release-skill 帮助维护者回答三个问题：准备发布什么、还有哪
 > 远端唯一性检查在 `publish` 全局预检执行。
 
 <!-- release-skill:capability:safe-first-command -->
-> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.9.19 是当前源码候选，本 README 不证明该候选已经发布、完成消费者安装验证或通过独立验收。**
+> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.9.21 是当前源码候选，本 README 不证明该候选已经发布、完成消费者安装验证或通过独立验收。**
 > npm 安装的 CLI 是受支持的用户入口；源码 checkout 保留为开发/贡献者路径。
 >
 > **第一条命令：**
@@ -75,7 +69,7 @@ marketplace 委托目标工作区发布的边界不变。
 
 旧 production 计划缺少 `sourceAuthority` 时，在外部写入前拒绝。未发生外部写入的计划必须重新 prepare 并批准新摘要，不能补写旧计划或迁移批准。已有 `PARTIAL` 保留检查点，走匹配版本的恢复路径。evidence v1 只读；v2 顶层封闭，阶段扩展放在 `details`。摘要和恢复建议只作诊断，不构成发布权威。
 
-当前 0.9.19 候选包含窄范围的 R-05 Hook cache v2 消费路径、公开 `postverify`
+当前 0.9.21 候选包含窄范围的 R-05 Hook cache v2 消费路径、公开 `postverify`
 路径和稳定隔离安装树记录路径（A2/A3），并增加只接受显式输入的 `verify-records`
 命令、自包含 Qoder 投影、Cursor 正式打包，以及基于 Foundation 的宿主核验桥。
 Skill Family Hub 仍是唯一市场来源。
@@ -234,6 +228,16 @@ TUI 路径，见 [INSTALL.zh-CN.md](INSTALL.zh-CN.md#安装为-kimi-code-插件)
 
 CodeBuddy、Codex、Kimi Code、Qoder 和 Cursor 的完整命令见 [INSTALL.zh-CN.md](INSTALL.zh-CN.md)。
 
+### 只读治理诊断
+
+沿用现有 Skill，并且只选择请求需要的检查：
+
+- 判断是否接入：`setup --assess-adoption --root <path> --json`；
+- 分析本地配置和发布就绪缺口：`assess --root <path> --offline --json`；
+- 核对显式提供的历史计划、批准和 run：使用 `verify-records`，完整输入见下一节。
+
+这些入口只运行 release-skill 自身的只读分析。治理诊断不运行目标 Skill、hook、构建或发布动作，也不把 `prepare`、`verify` 或 `release-finish` 当作静态治理检查。维护者要求实际接入或发布时，继续使用原有业务 Skill，并沿用该动作的授权与安全合同。
+
 ### 离线核验历史发布记录
 
 消费者已经持有明确的计划、批准、目标 run 和该目标引用的全部前驱 run 时，可以运行：
@@ -335,7 +339,8 @@ ACTOR=your-name
    **接入评估（只读）：** 对已接入项目，`setup --assess-adoption` 报告已满足项、
    必选缺口、可选建议和不适用项，不写入任何文件；未配置项目返回 `NOT_CONFIGURED`
    并指向首次接入。Hook 耗时建议只从当前版本生产者产生的事件推导；工具绝不代猜
-   或代写项目的 `cacheInputs`。
+   或代写项目的 `cacheInputs`。`gateSuggestions` 只列能够形成可执行草案且尚未登记的
+   候选；其余发现保留在 `gateDiagnostics`，不影响接入状态或日常摘要。
 3. **assess** — 只读就绪评估：
    ```bash
    "${CLI[@]}" assess --root "$PROJECT" --offline --json
@@ -730,12 +735,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.21 让 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.19",
+  "version": "0.9.21",
   "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
   "author": {
     "name": "广州市风荷科技有限公司"