release-skill 0.9.18 → 0.9.20

package/.claude-plugin/plugin.json

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

package/.cursor-plugin/plugin.json

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

package/CHANGELOG.md

@@ -1,5 +1,72 @@
 # Changelog
 
+<!-- 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
+
+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.
+
+### 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.
+
+### 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.
+
+### 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.
+<!-- release-skill:changelog:end version=0.9.19 locale=en -->
+
+
 <!-- release-skill:changelog:start version=0.9.18 locale=en baseline=sha256:486d52ac38ecb11f043c79661728004fb1c1593089915741867cdc0f449be275 -->
 ## [0.9.18] - 2026-09-11
 

package/INSTALL.md

@@ -2,7 +2,7 @@
 
 [简体中文](INSTALL.zh-CN.md)
 
-<!-- release-skill:release-version: 0.9.18 -->
+<!-- release-skill:release-version: 0.9.20 -->
 ## Prerequisites
 
 - Node.js 22.0.0 or later
@@ -125,12 +125,22 @@ 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.18
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.20
    /plugins reload
    ```
 
 After the release has reached `VERIFIED`, the optional `release-finish` workflow
 can perform the same TUI interaction only after explicit user confirmation. It
+starts from the public `release-skill post-release --root <root> --plan <plan> --run
+<postverify-run> --finish` entry. The command reports the fixed merge, host-update,
+host-load, setup, and source-branch steps. A pending load or setup observation
+exits `2`; an operational failure exits `1`; only a fully closed checklist exits
+`0`. Agent-observed host loading and the invoked `release-setup` result return
+through an absolute `--finish-feedback` file bound to the plan digest,
+configuration digest, and project root. An update result alone never proves that
+the host loaded the release.
+
+The workflow
 requires the package name, version, release tag, installed revision, and managed
 root to match the frozen plan. An exact current installation is checked before
 returning `ALREADY_CURRENT`. When an installation or migration occurs, the

package/INSTALL.zh-CN.md

@@ -2,7 +2,7 @@
 
 [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.9.18 -->
+<!-- release-skill:release-version: 0.9.20 -->
 ## 前置条件
 
 - Node.js 22.0.0 或更高版本
@@ -113,12 +113,19 @@ release-skill 当前只采用并验证 Kimi Code 的交互式 TUI 路径，**无
 （切勿使用裸仓库地址，它会安装最新 release 或默认分支），确认信任提示后重新加载：
 
    ```
-   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.18
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.20
    /plugins reload
    ```
 
 发布达到 `VERIFIED` 后，可选的 `release-finish` 工作流可以在用户明确同意后执行
-同一套 TUI 操作。包名、版本、发布标签、已安装修订号和受管安装根都必须与冻结计划
+同一套 TUI 操作。其公共入口是 `release-skill post-release --root <root> --plan <plan>
+--run <postverify-run> --finish`，固定汇总合并、本机宿主更新、宿主加载、setup 和源码
+分支五步。仍缺加载或 setup 观察时退出码为 `2`，操作失败时为 `1`，只有全部收尾才为
+`0`。智能体观察到的宿主加载结果和实际调用 `release-setup` 的结果，必须通过绝对路径的
+`--finish-feedback` 文件回传，并绑定计划摘要、配置摘要和项目根；更新成功本身不证明新版
+已经加载。
+
+包名、版本、发布标签、已安装修订号和受管安装根都必须与冻结计划
 一致。精确当前安装会在返回 `ALREADY_CURRENT` 前核对；发生安装或迁移时，只在操作
 完成后核对结果。`.git` 目录只提供附加诊断，不是通过条件。发生安装或迁移后，
 release-finish 会重新读取 Kimi 的受管安装根，不复用操作前的观察；随后核对最终身份与

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.18 -->
+<!-- release-skill:release-version: 0.9.20 -->
 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,39 @@ 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.18** (2026-09-11)
+**0.9.20** (2026-09-17)
 
-0.9.18 is a local source candidate that adds first-class Cursor packaging, Foundation-backed host verification, and a final local distribution path for Claude, Codex, Kimi, CodeBuddy, WorkBuddy, Qoder, and Cursor. 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.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**
 
-- Cursor must be closed before its plugin tree is scanned or replaced. Failed upgrades preserve or restore a complete old or new directory instead of publishing a mixed tree.
-- Host verification receives only caller-declared roots and records mechanism observations separately from release-domain publication and verification state.
+- 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**
 
-- The npm package now includes `.cursor-plugin/plugin.json` and a self-contained `adapters/cursor/` projection with all release-skill Skills and runtime resources.
-- Release verification can invoke Foundation 0.21.0 host verification with explicit executable and user-state roots, including Cursor project-level plugin verification.
-- The final local updater can distribute the verified release to the declared Claude, Codex, Kimi, CodeBuddy, WorkBuddy, Qoder, and Cursor installations.
-- Skill Family Hub remains the central marketplace. Its release entry is published through the existing Git Data API after release verification.
+- 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**
 
-- Local host updates verify the frozen snapshot and manifest identity before installation, and Cursor updates use Foundation fixed-set publication for first install and atomic full-directory replacement for upgrades.
-- Platform generation, public-file projection, package allowlists, schemas, and release-finish guidance now treat Cursor as a declared host and adapter.
+- 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 plugin names reject underscores so generated local plugin directories remain compatible with Cursor's manifest requirements.
-- The package's native prebuild allowlist and fixed resource-closure checks now include every generated adapter, including Cursor.
+- 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.17 to obtain Cursor packaging and local installation, the Foundation-backed host verification bridge, and the unified seven-host local finish path. 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 each host after updating; an `UPDATED` filesystem result alone does not prove that the running host loaded the new version.
+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:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **Current boundary:** v0.9.18 is the current source candidate. This README
+> **Current boundary:** v0.9.20 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 +70,7 @@ Upgrade from 0.9.17 to obtain Cursor packaging and local installation, the Found
 > publish global preflight.
 
 <!-- release-skill:capability:safe-first-command -->
-> **Production path verified since the v0.1.1 milestone; v0.9.18 is the current
+> **Production path verified since the v0.1.1 milestone; v0.9.20 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 +99,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.18 candidate includes the narrow R-05 Hook cache v2 consumer
+The current 0.9.20 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 +287,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 +412,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
@@ -577,6 +588,16 @@ a shell command. After host updates, release-finish runs that setup entry
 against the current release project root passed through `--root`; it does not
 request a separate project directory. The two settings are independent.
 
+Use `release-skill post-release --finish` for the complete local finish. It
+always reports merge, host update, actual host loading, setup, and source-branch
+steps. Exit 0 means every applicable step completed or was explicitly skipped;
+exit 2 means caller work remains; exit 1 means a deterministic failure. Pass
+agent observations back through an absolute `--finish-feedback` JSON file bound
+to the reported plan digest, config digest, and canonical project root. Feedback
+is data only: the command does not execute its strings or treat it as new write
+authority. `--skip-local-hosts` explicitly skips host update, loading, and setup
+and cannot be combined with `--hosts` or `--update-local-hosts`.
+
 `distributions` is required but may be an explicit empty array. Use
 `distributions: []` when release-skill should publish only the unit's GitHub
 snapshot, tag, and GitHub Release, with no npm publish or marketplace consumer

package/README.zh-CN.md

@@ -2,46 +2,45 @@
 
 [English](README.md) · 安装指南：[中文](INSTALL.zh-CN.md) / [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.9.18 -->
+<!-- release-skill:release-version: 0.9.20 -->
 面向 Claude Code、CodeBuddy、WorkBuddy、Codex 和 Kimi Code 的发布准备工具，完整保留人工维护的文件内容。
 
 release-skill 帮助维护者回答三个问题：准备发布什么、还有哪些检查未通过、最终发布的内容是什么。它不重新生成、也不回写项目源文件。`prepare` 把每个配置的公开文件复制到隔离快照并验证字节——先冻结并供人工审阅，再从同一份冻结产物发布。`setup` 只显示确定性的 `compactSummary` 审阅视图，完整报告保留在临时会话目录中。
 
 <!-- release-skill:managed:start id=latest-release -->
-**0.9.18** (2026-09-11)
+**0.9.20** (2026-09-17)
 
-0.9.18 是一个本地源码候选。本版本增加 Cursor 的正式打包与分发、基于 Foundation 的宿主核验，以及覆盖 Claude、Codex、Kimi、CodeBuddy、WorkBuddy、Qoder 和 Cursor 的最终本机分发路径。三项 Foundation 依赖继续精确固定在已发布的 0.21.0。本说明不代表已经发布、完成真实宿主验收、完成消费者安装验证或通过独立验收。
+0.9.20 是一个本地源码候选。本版本让维护者更容易选择发布治理检查，也更容易判断结果的效力。既有公共 Skill 现在会区分接入评估、离线发布就绪评估和显式历史记录核对；这些只读检查不会运行目标 Skill、hook、构建或发布动作。本版本还把可执行的验证门草案与不可执行的诊断事实分开，并修正 Cursor 自动化能力的派生结果。三项 Foundation 依赖继续精确固定在已发布的 0.21.0。本说明不代表已经发布、完成真实宿主验收、完成消费者安装验证或通过独立验收。
 
 **安全**
 
-- 扫描或替换 Cursor 插件树前必须关闭 Cursor。升级失败时保留或恢复完整的旧目录或新目录，不会发布混合目录。
-- 宿主核验只接收调用方声明的根目录，并把机制观察结果与 release-skill 的发布、验证状态分别记录。
+- 只读治理诊断不会执行目标 Skill、业务脚本、构建、hook、prepare、verify 或 release-finish。
+- 历史核对只读取维护者显式提供的文件，不鉴定作者，也不证明目标实际执行、当前发行物身份或当前远端状态。
 - Hub 发布继续绑定已观察的分支头执行比较后写入。部分发布时不回滚、不覆盖已经成功的远端步骤。
 
 **新增**
 
-- npm 包新增 `.cursor-plugin/plugin.json` 和自包含的 `adapters/cursor/` 投影，包含 release-skill 的全部 Skill 与运行资源。
-- 发布验证可通过显式的可执行文件根目录和用户状态根目录调用 Foundation 0.21.0 宿主核验，其中包括 Cursor 项目级插件核验。
-- 最终本机更新入口可以把已验证版本分发到声明的 Claude、Codex、Kimi、CodeBuddy、WorkBuddy、Qoder 和 Cursor 安装位置。
-- Skill Family Hub 继续作为中央市场。发布完成验证后，release-skill 通过既有 GitHub Git Data API 更新 Hub 条目。
+- 公共帮助与评估入口现在按维护者的意图区分三类只读请求：判断是否接入、分析离线就绪缺口、核对显式提供的历史记录。
+- 接入报告新增 `gateDiagnostics`，用于保留不能形成执行草案的脚本发现；`gateSuggestions` 只保留尚未配置且能够执行的草案。
 
 **变更**
 
-- 本机宿主更新会先核对冻结快照、manifest 身份和版本。Cursor 首次安装使用 Foundation 固定集合发布，升级使用整个目录的原子替换。
-- 平台生成、公开文件投影、包内容许可清单、Schema 与 release-finish 指引现在统一把 Cursor 视为正式宿主和适配器。
+- 中英文 README 补充只读治理边界；实际 setup 和发布工作继续沿用既有授权合同。
+- 发布评估说明明确历史记录核对结果的效力，避免把历史终态误写成当前发行物字节或远端状态的证据。
+- Skill Family Hub 继续作为统一市场；发布完成验证后，release-skill 仍通过既有 GitHub Git Data API 更新 Hub 条目。
 
 **修复**
 
-- Cursor 插件名不再接受下划线，生成的本机插件目录符合 Cursor manifest 的名称约束。
-- npm 包原生预构建许可清单和固定资源闭包检查现已覆盖包括 Cursor 在内的全部生成适配器。
+- Cursor 的 `foundation-host-verification` 安装方式现在正确派生为 `automatable: true`，与已发布的宿主描述符保持一致。
+- 派生制品校验把写模式放到隔离副本执行，检查期间不再改写真实工作区。
 
 **升级说明**
 
-从 0.9.17 升级后，可获得 Cursor 打包与本机安装、基于 Foundation 的宿主核验桥，以及统一的七宿主本机收尾路径。请移除独立的 `release-skill` 市场，改用 ifoohoo/skill-family-hub 仓库与 Hub 限定插件名 release-skill@skill-family-hub。更新后仍需重新加载各宿主；文件系统返回 `UPDATED` 并不单独证明运行中的宿主已经加载新版。
+从 0.9.19 升级后，可以使用更清晰的治理入口说明、只含可执行草案的 `gateSuggestions`、新的 `gateDiagnostics` 字段，以及修正后的 Cursor 自动化能力派生。无需迁移配置。请移除独立的 `release-skill` 市场，改用 ifoohoo/skill-family-hub 仓库与 Hub 限定插件名 release-skill@skill-family-hub。本版本不包含仍在延期的公共结论文件输出和工程依赖事实接口。
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **当前边界：** v0.9.18 只是当前源码候选。本 README 记录预期范围与验证边界，
+> **当前边界：** v0.9.20 只是当前源码候选。本 README 记录预期范围与验证边界，
 > 不代表已经发布、完成消费者安装验证或通过独立验收。
 > 版本可用性以对应发布记录及发布后验证结果为准。
 > v0.4.1 是更早的已发布里程碑（v0.2.2 曾处于已发布状态，后因平台验证收敛修复而更新）。
@@ -57,7 +56,7 @@ release-skill 帮助维护者回答三个问题：准备发布什么、还有哪
 > 远端唯一性检查在 `publish` 全局预检执行。
 
 <!-- release-skill:capability:safe-first-command -->
-> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.9.18 是当前源码候选，本 README 不证明该候选已经发布、完成消费者安装验证或通过独立验收。**
+> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.9.20 是当前源码候选，本 README 不证明该候选已经发布、完成消费者安装验证或通过独立验收。**
 > npm 安装的 CLI 是受支持的用户入口；源码 checkout 保留为开发/贡献者路径。
 >
 > **第一条命令：**
@@ -75,7 +74,7 @@ marketplace 委托目标工作区发布的边界不变。
 
 旧 production 计划缺少 `sourceAuthority` 时，在外部写入前拒绝。未发生外部写入的计划必须重新 prepare 并批准新摘要，不能补写旧计划或迁移批准。已有 `PARTIAL` 保留检查点，走匹配版本的恢复路径。evidence v1 只读；v2 顶层封闭，阶段扩展放在 `details`。摘要和恢复建议只作诊断，不构成发布权威。
 
-当前 0.9.18 候选包含窄范围的 R-05 Hook cache v2 消费路径、公开 `postverify`
+当前 0.9.20 候选包含窄范围的 R-05 Hook cache v2 消费路径、公开 `postverify`
 路径和稳定隔离安装树记录路径（A2/A3），并增加只接受显式输入的 `verify-records`
 命令、自包含 Qoder 投影、Cursor 正式打包，以及基于 Foundation 的宿主核验桥。
 Skill Family Hub 仍是唯一市场来源。
@@ -234,6 +233,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 +344,8 @@ ACTOR=your-name
    **接入评估（只读）：** 对已接入项目，`setup --assess-adoption` 报告已满足项、
    必选缺口、可选建议和不适用项，不写入任何文件；未配置项目返回 `NOT_CONFIGURED`
    并指向首次接入。Hook 耗时建议只从当前版本生产者产生的事件推导；工具绝不代猜
-   或代写项目的 `cacheInputs`。
+   或代写项目的 `cacheInputs`。`gateSuggestions` 只列能够形成可执行草案且尚未登记的
+   候选；其余发现保留在 `gateDiagnostics`，不影响接入状态或日常摘要。
 3. **assess** — 只读就绪评估：
    ```bash
    "${CLI[@]}" assess --root "$PROJECT" --offline --json
@@ -486,6 +496,8 @@ releaseUnits:
 release-finish 在 `--root` 指定的当前发布项目根目录调用该入口，不再要求另行提供项目目录。
 两个配置彼此独立。
 
+完整的本地收尾使用 `release-skill post-release --finish`。命令固定报告分支决定、宿主更新、实际加载、setup 和源码分支检查：全部适用步骤完成或明确跳过时退出 0，仍有待办时退出 2，确定失败时退出 1。智能体通过绝对路径的 `--finish-feedback` JSON 文件回传观察，文件必须绑定当前计划摘要、配置摘要和规范项目根目录。反馈只作为数据：脚本不执行其中字符串，也不把反馈当成新的写入授权。`--skip-local-hosts` 显示跳过宿主更新、加载和 setup，不得与 `--hosts` 或 `--update-local-hosts` 同时使用。
+
 `distributions` 是必填字段，但可以显式设为空数组。使用
 `distributions: []` 时，release-skill 只发布该单元的 GitHub 快照、标签和
 GitHub Release，不生成 npm 发布或市场消费者动作。单元的 `postPublish` 声明仍会

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

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