release-skill 0.9.13 → 0.9.15

package/.claude-plugin/plugin.json

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

package/.kimi-plugin/plugin.json

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

package/CHANGELOG.md

@@ -1,5 +1,56 @@
 # Changelog
 
+<!-- release-skill:changelog:start version=0.9.15 locale=en baseline=sha256:caaa3680d940673edb3421512224623f618d8bff4ab159be60c797620ea3851f -->
+## [0.9.15] - 2026-09-07
+
+0.9.15 is a local source candidate that makes release preparation use the project's existing assessment, refresh, focused-check, and formal prepare entry points, and makes prepare help return before business execution. The three Foundation dependencies remain pinned to the exact 0.17.0 release. This note is not evidence of publication, real-host acceptance, consumer installation verification, or independent acceptance.
+
+### Security
+
+- The orchestration change adds no execution engine, Hook type, cache key, approval state, or external write. Environment allowlists still forward only values already present in the invoking environment, and invalid lowercase names remain configuration errors.
+- Frozen candidates keep their existing acceptance boundary. A newly generated candidate requires validation against its own bytes; earlier acceptance evidence is not reused for changed output.
+- Skill Family Hub updates continue to use compare-and-swap against the observed branch head through GitHub's Git Data API. A partial Hub publication is never rolled back or force-pushed, and existing remote state is never overwritten.
+
+### Changed
+
+- The release-prepare Skill now reads the current project contract and authorization, resolves required release-document and generated-artifact freshness work through existing project entry points, runs focused checks after repairs, and leaves complete validation to the formal prepare Hook path.
+- After a failure, release-prepare groups directly related fixes before retrying and does not add a same-purpose full test run by default. Explicitly requested independent full acceptance remains part of the workflow, and projects without valid cache evidence still execute their complete Hooks.
+- Existing 0.9.14 production-run retention and Hub-backed post-verification host guidance remain available. The project-private postVerify Hook continues to publish the verified release-skill entry and public snapshot to Skill Family Hub through GitHub's Git Data API.
+
+### Fixed
+
+- `prepare --help` and `prepare -h` now return before project-root resolution, configuration loading, lock acquisition, run cleanup, Hook execution, snapshot construction, or plan writes. JSON help returns `command: prepare` with `status: HELP`; prepare without a help flag keeps its existing business path.
+
+### Upgrade Notes
+
+Upgrade from 0.9.14 to use the consolidated release-prepare workflow and side-effect-free prepare help. No project configuration migration is required. Keep project-specific generation and prerequisite checks in their existing reviewed entry points. Remove any release-skill standalone marketplace registration, add or update `ifoohoo/skill-family-hub`, and use `release-skill@skill-family-hub`. Existing executable `externalActions` targets retain their current update path; Hub-backed targets remain manual in 0.9.15.
+<!-- release-skill:changelog:end version=0.9.15 locale=en -->
+
+
+<!-- release-skill:changelog:start version=0.9.14 locale=en baseline=sha256:48b2f41bd292f3357b3cf7433de1a2191b84d86a5074c9786ac952f62d4279be -->
+## [0.9.14] - 2026-09-05
+
+0.9.14 is a local source candidate that bounds retained production prepare runs and adds explicit Hub-backed host follow-ups after post-verification. The three Foundation dependencies remain pinned to the exact 0.17.0 release. This note is not evidence of publication, real-host acceptance, consumer installation verification, or independent acceptance.
+
+### Security
+
+- Retention reuses Foundation path containment and existing plan and run lineage checks. It deletes whole run directories, preserves uncertain evidence, and never turns a cleanup failure into a prepare failure.
+- Hub-backed guidance does not run Git, GitHub, Hub, or host commands and does not probe local installation state. Plugin identity must match the frozen public manifests, and Hub-backed targets are not passed to `updateLocalHostPlugins()`.
+- Skill Family Hub updates remain compare-and-swap operations against the observed branch head. A partial Hub publication is never rolled back or force-pushed.
+
+### Added
+
+- Production prepare now runs retention under the existing project lock. It keeps the current run, the newest verified complete lineage, and every non-terminal, partial, damaged, ambiguous, or validation-failing run; only superseded complete lineages and sealed failed prepares without external-write evidence are eligible for best-effort removal.
+- A release unit may declare `postPublish.localHostUpdate` with the plugin identity, target hosts, and project-selected Hub repository and ref. Prepare freezes that declaration into the immutable plan and binds it through `planDigest`.
+- After postVerify reaches `DISTRIBUTED`, the CLI and `release-finish` show host-specific manual installation or upgrade guidance for Hub-backed targets. Hub-only targets remain unavailable to the automatic local updater.
+- The project-private postVerify hook continues to publish the verified release-skill entry and public snapshot to Skill Family Hub through GitHub's Git Data API.
+
+### Upgrade Notes
+
+Upgrade from 0.9.13 to bound completed production run history and receive post-verification Hub-backed host guidance. Declare `localHostUpdate` independently for each release unit that needs it. Remove any release-skill standalone marketplace registration, add or update `ifoohoo/skill-family-hub`, and use `release-skill@skill-family-hub`. Existing executable `externalActions` targets retain their current update path; Hub-backed targets remain manual in 0.9.14.
+<!-- release-skill:changelog:end version=0.9.14 locale=en -->
+
+
 <!-- release-skill:changelog:start version=0.9.13 locale=en baseline=sha256:86e8ee0d0aeb161c7fc652f85976b300b649ee6da04d29f9274ebcc69a8eab10 -->
 ## [0.9.13] - 2026-09-05
 

package/INSTALL.md

@@ -2,7 +2,7 @@
 
 [简体中文](INSTALL.zh-CN.md)
 
-<!-- release-skill:release-version: 0.9.13 -->
+<!-- release-skill:release-version: 0.9.15 -->
 ## Prerequisites
 
 - Node.js 22.0.0 or later
@@ -110,7 +110,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.13
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.15
    /plugins reload
    ```
 

package/INSTALL.zh-CN.md

@@ -2,7 +2,7 @@
 
 [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.9.13 -->
+<!-- release-skill:release-version: 0.9.15 -->
 ## 前置条件
 
 - Node.js 22.0.0 或更高版本
@@ -101,7 +101,7 @@ release-skill 当前只采用并验证 Kimi Code 的交互式 TUI 路径，**无
 （切勿使用裸仓库地址，它会安装最新 release 或默认分支），确认信任提示后重新加载：
 
    ```
-   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.13
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.15
    /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.13 -->
+<!-- release-skill:release-version: 0.9.15 -->
 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,27 +14,33 @@ 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.13** (2026-09-05)
+**0.9.15** (2026-09-07)
 
-0.9.13 is a local source candidate that prevents new CodeBuddy release configurations from silently inheriting another product family's marketplace. It also brings the README black-box scenario versions under the existing version synchronization command. The three Foundation dependencies remain pinned to the exact 0.17.0 release. This note is not evidence of publication, real-host acceptance, consumer installation verification, or independent acceptance.
+0.9.15 is a local source candidate that makes release preparation use the project's existing assessment, refresh, focused-check, and formal prepare entry points, and makes prepare help return before business execution. The three Foundation dependencies remain pinned to the exact 0.17.0 release. This note is not evidence of publication, real-host acceptance, consumer installation verification, or independent acceptance.
 
 **Security**
 
-- Already-frozen historical plans without `marketplace` retain the legacy interpretation for deterministic reconcile. New configuration validation changes do not weaken frozen-plan identity, approval, publish, verification, or recovery checks. Skill Family Hub updates remain compare-and-swap operations; a partial Hub publication is never rolled back or force-pushed, and release-skill does not introduce a second Hub registry or state machine.
+- The orchestration change adds no execution engine, Hook type, cache key, approval state, or external write. Environment allowlists still forward only values already present in the invoking environment, and invalid lowercase names remain configuration errors.
+- Frozen candidates keep their existing acceptance boundary. A newly generated candidate requires validation against its own bytes; earlier acceptance evidence is not reused for changed output.
+- Skill Family Hub updates continue to use compare-and-swap against the observed branch head through GitHub's Git Data API. A partial Hub publication is never rolled back or force-pushed, and existing remote state is never overwritten.
+
+**Changed**
+
+- The release-prepare Skill now reads the current project contract and authorization, resolves required release-document and generated-artifact freshness work through existing project entry points, runs focused checks after repairs, and leaves complete validation to the formal prepare Hook path.
+- After a failure, release-prepare groups directly related fixes before retrying and does not add a same-purpose full test run by default. Explicitly requested independent full acceptance remains part of the workflow, and projects without valid cache evidence still execute their complete Hooks.
+- Existing 0.9.14 production-run retention and Hub-backed post-verification host guidance remain available. The project-private postVerify Hook continues to publish the verified release-skill entry and public snapshot to Skill Family Hub through GitHub's Git Data API.
 
 **Fixed**
 
-- New `codebuddy-plugin` distributions must declare `marketplace` explicitly, so each project selects its own Hub instead of inheriting the legacy `artifact-skill-set` default.
-- The first-user and security-reviewer README black-box prompts now receive their candidate version from `sync-version`, preventing their assertions from drifting behind the package version.
-- The project-private postVerify hook continues to publish the verified release-skill entry and public snapshot to Skill Family Hub through GitHub's Git Data API.
+- `prepare --help` and `prepare -h` now return before project-root resolution, configuration loading, lock acquisition, run cleanup, Hook execution, snapshot construction, or plan writes. JSON help returns `command: prepare` with `status: HELP`; prepare without a help flag keeps its existing business path.
 
 **Upgrade Notes**
 
-Upgrade from 0.9.12 before preparing a new CodeBuddy release configuration. Add the intended Hub name to every new `codebuddy-plugin` distribution through its `marketplace` field. Remove any release-skill standalone marketplace registration, add or update `ifoohoo/skill-family-hub`, and use `release-skill@skill-family-hub`. Existing frozen plans remain recoverable, and other distribution types are unaffected.
+Upgrade from 0.9.14 to use the consolidated release-prepare workflow and side-effect-free prepare help. No project configuration migration is required. Keep project-specific generation and prerequisite checks in their existing reviewed entry points. Remove any release-skill standalone marketplace registration, add or update `ifoohoo/skill-family-hub`, and use `release-skill@skill-family-hub`. Existing executable `externalActions` targets retain their current update path; Hub-backed targets remain manual in 0.9.15.
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **Current boundary:** v0.9.13 is the current source candidate. This README
+> **Current boundary:** v0.9.15 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
@@ -58,7 +64,7 @@ Upgrade from 0.9.12 before preparing a new CodeBuddy release configuration. Add
 > publish global preflight.
 
 <!-- release-skill:capability:safe-first-command -->
-> **Production path verified since the v0.1.1 milestone; v0.9.13 is the current
+> **Production path verified since the v0.1.1 milestone; v0.9.15 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
@@ -87,10 +93,13 @@ 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.13 candidate includes the narrow R-05 Hook cache v2 consumer
+The current 0.9.15 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 removes the repository's own marketplace indexes and
-uses Skill Family Hub as the single marketplace source. It still
+path (A2/A3). It keeps Skill Family Hub as the single marketplace source. It
+also makes the `release-prepare` Skill organize existing assessment, refresh,
+focused-check, and prepare entry points without adding another execution
+engine. `prepare --help` and `prepare -h` now return before configuration,
+locks, runs, or hooks can observe the request. This candidate still
 excludes R-02 safe full-tree inventory, R-10 historical-release verification
 implementation, real Kimi/WorkBuddy public-marketplace installation and
 invocation gates, and an Audit public offline release-record verifier.
@@ -740,7 +749,7 @@ append-only incremental flow is described in the setup step above and in
 - `release-help`: environment check and next-step guidance.
 - `release-setup`: read-only discovery, human calibration, create-once configuration, and read-only adoption assessment (`setup --assess-adoption`).
 - `release-assess`: read-only release readiness report.
-- `release-prepare`: local snapshot and reviewable release plan.
+- `release-prepare`: organizes existing project prerequisites and focused repairs, then freezes a local snapshot and reviewable release plan through the formal prepare entry.
 - `release-publish`: approved frozen GitHub+npm publishing; the internal digest is checked automatically.
 - `release-reconcile`: evidence-based PARTIAL recovery with human intervention on conflicts.
 - `release-verify`: post-publish verification; only `VERIFIED` is the happy end.
@@ -784,6 +793,25 @@ unsupported. When a plan declares postVerify hooks, release-finish must receive
 the completed postVerify run produced by `ship`, rather than the earlier verify
 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 are manual in 0.9.14 (`promptRequired: true`, `available: false`): the
+prompt does 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.
+
+Production `prepare` also performs one best-effort retention pass after its new
+run evidence exists and before expensive snapshot and hook work. It removes
+only superseded complete run lineages and sealed failed prepare directories
+that have no valid plan or external-write trace. The current plan, the newest
+complete lineage, and every non-terminal, partial, corrupt, ambiguous, or
+out-of-bounds lineage remain protected. Retention failures never change the
+prepare result.
+
 New `codebuddy-plugin` project configurations must declare `marketplace`
 explicitly so product families cannot silently inherit another family's Hub.
 `marketplaceSource`, the URL consumers use to add that marketplace, remains

package/README.zh-CN.md

@@ -2,33 +2,39 @@
 
 [English](README.md) · 安装指南：[中文](INSTALL.zh-CN.md) / [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.9.13 -->
+<!-- release-skill:release-version: 0.9.15 -->
 面向 Claude Code、CodeBuddy、WorkBuddy、Codex 和 Kimi Code 的发布准备工具，完整保留人工维护的文件内容。
 
 release-skill 帮助维护者回答三个问题：准备发布什么、还有哪些检查未通过、最终发布的内容是什么。它不重新生成、也不回写项目源文件。`prepare` 把每个配置的公开文件复制到隔离快照并验证字节——先冻结并供人工审阅，再从同一份冻结产物发布。`setup` 只显示确定性的 `compactSummary` 审阅视图，完整报告保留在临时会话目录中。
 
 <!-- release-skill:managed:start id=latest-release -->
-**0.9.13** (2026-09-05)
+**0.9.15** (2026-09-07)
 
-0.9.13 是阻止新的 CodeBuddy 发布配置静默继承其他产品线市场的本地源码候选，并把 README 黑盒场景中的候选版本交给现有版本同步命令统一维护。三项 Foundation 依赖仍精确固定在已发布的 0.17.0。本说明不代表已经发布、完成真实宿主验收、完成消费者安装验证或通过独立验收。
+0.9.15 是一个本地源码候选。本版本让发布准备复用项目已有评估、刷新、聚焦检查和正式 prepare 入口，并让 prepare 帮助在业务执行前返回。三项 Foundation 依赖仍精确固定在已发布的 0.17.0。本说明不代表已经发布、完成真实宿主验收、完成消费者安装验证或通过独立验收。
 
 **安全**
 
-- 已经冻结且未携带 `marketplace` 的历史计划仍按旧语义执行，以便确定性地恢复发布。新的配置校验不放宽冻结计划身份、批准、发布、验证或恢复检查。Skill Family Hub 更新继续采用比较后写入；Hub 局部发布不回滚、不覆盖，也不强推，release-skill 中没有增加第二套 Hub Registry 或状态机。
+- 本次编排调整不新增执行引擎、Hook 类型、缓存键、批准状态或外部写入。环境变量白名单仍只转发调用环境中已存在的同名值，非法的小写名称继续按配置错误处理。
+- 已冻结候选保留原有验收边界。新生成的候选必须针对自身字节验证，不得复用变更前的验收证据。
+- Skill Family Hub 更新继续通过 GitHub Git Data API，根据已观察的分支头比较后写入。Hub 局部发布不回滚、不覆盖，也不强推。
+
+**变更**
+
+- release-prepare Skill 现在先读取项目合同和授权，通过项目已有入口处理发布文档与生成物新鲜度，修复后运行聚焦检查，并把完整验证交给正式 prepare Hook 路径。
+- 一次失败后，release-prepare 会集中处理直接相关的修复再重试，默认不增加同目的的完整测试。用户明确要求的独立完整验收仍保留；项目没有有效缓存证据时，完整 Hook 仍会执行。
+- 0.9.14 的 production run 保留策略和 Hub-backed 发布后验证宿主提示继续可用。项目私有的 postVerify Hook 继续通过 GitHub Git Data API，把已验证的 release-skill 条目和公开快照发布到 Skill Family Hub。
 
 **修复**
 
-- 新的 `codebuddy-plugin` 分发必须显式声明 `marketplace`。每个项目据此选择自己的 Hub，不再继承旧的 `artifact-skill-set` 默认值。
-- 首次使用者与安全审阅者的 README 黑盒提示词现在通过 `sync-version` 接收候选版本，避免其中的断言落后于包版本。
-- 项目私有的 postVerify hook 继续通过 GitHub Git Data API，把已验证的 release-skill 条目和公开快照发布到 Skill Family Hub。
+- `prepare --help` 和 `prepare -h` 现在会在项目根目录解析、配置读取、锁获取、run 清理、Hook 执行、快照构建或计划写入前返回。JSON 帮助返回 `command: prepare` 和 `status: HELP`；没有帮助参数的 prepare 保留原有业务路径。
 
 **升级说明**
 
-准备新的 CodeBuddy 发布配置前，应从 0.9.12 升级到本版本，并在每个 `codebuddy-plugin` 分发的 `marketplace` 字段中填写目标 Hub。删除各宿主中独立的 `release-skill` 市场登记，添加或更新 `ifoohoo/skill-family-hub`，并使用 `release-skill@skill-family-hub`。已经冻结的历史计划仍可恢复，其他分发类型不受影响。
+从 0.9.14 升级后，可使用收敛后的 release-prepare 流程和无业务副作用的 prepare 帮助。项目配置无需迁移；项目专属的生成和前提检查仍通过已审阅入口执行。删除各宿主中独立的 `release-skill` 市场登记，添加或更新 `ifoohoo/skill-family-hub`，并使用 `release-skill@skill-family-hub`。现有 `externalActions` 可执行目标继续使用原更新路径；0.9.15 的 Hub-backed 目标仍由维护者人工处理。
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **当前边界：** v0.9.13 只是当前源码候选。本 README 记录预期范围与验证边界，
+> **当前边界：** v0.9.15 只是当前源码候选。本 README 记录预期范围与验证边界，
 > 不代表已经发布、完成消费者安装验证或通过独立验收。
 > 版本可用性以对应发布记录及发布后验证结果为准。
 > v0.4.1 是更早的已发布里程碑（v0.2.2 曾处于已发布状态，后因平台验证收敛修复而更新）。
@@ -44,7 +50,7 @@ release-skill 帮助维护者回答三个问题：准备发布什么、还有哪
 > 远端唯一性检查在 `publish` 全局预检执行。
 
 <!-- release-skill:capability:safe-first-command -->
-> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.9.13 是当前源码候选，本 README 不证明该候选已经发布、完成消费者安装验证或通过独立验收。**
+> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.9.15 是当前源码候选，本 README 不证明该候选已经发布、完成消费者安装验证或通过独立验收。**
 > npm 安装的 CLI 是受支持的用户入口；源码 checkout 保留为开发/贡献者路径。
 >
 > **第一条命令：**
@@ -62,9 +68,11 @@ marketplace 委托目标工作区发布的边界不变。
 
 旧 production 计划缺少 `sourceAuthority` 时，在外部写入前拒绝。未发生外部写入的计划必须重新 prepare 并批准新摘要，不能补写旧计划或迁移批准。已有 `PARTIAL` 保留检查点，走匹配版本的恢复路径。evidence v1 只读；v2 顶层封闭，阶段扩展放在 `details`。摘要和恢复建议只作诊断，不构成发布权威。
 
-当前 0.9.13 候选包含窄范围的 R-05 Hook cache v2 消费路径、公开 `postverify`
-路径和稳定隔离安装树记录路径（A2/A3），并删除仓库自有市场索引，统一以
-Skill Family Hub 为市场来源。当前仍不包含 R-02 安全整树盘点、R-10 历史发布验证
+当前 0.9.15 候选包含窄范围的 R-05 Hook cache v2 消费路径、公开 `postverify`
+路径和稳定隔离安装树记录路径（A2/A3），继续以 Skill Family Hub 为唯一市场来源。
+`release-prepare` Skill 现在会组织项目已有的评估、刷新、聚焦检查和 prepare 入口，不新增执行引擎。
+`prepare --help` 和 `prepare -h` 会在配置、锁、run 或 Hook 观察请求之前返回。当前仍不包含
+R-02 安全整树盘点、R-10 历史发布验证
 的产品实现、真实 Kimi/WorkBuddy 公开市场安装与调用门禁或 Audit 公开离线发布记录
 验证器。本范围说明不构成远端发布记录或消费者升级指引。
 
@@ -633,7 +641,7 @@ release-skill ship --root "$PROJECT" --hook-approval "$HOOK_APPROVAL_PATH" --jso
 - `release-help`：环境检查和下一步引导。
 - `release-setup`：首次接入的只读发现、人工校准、create-once 配置创建和只读接入评估（`setup --assess-adoption`）。
 - `release-assess`：只读发布就绪度报告。
-- `release-prepare`：本地快照和可审阅发布计划。
+- `release-prepare`：组织项目已有前提和聚焦修复，再通过正式 prepare 入口冻结本地快照和可审阅发布计划。
 - `release-publish`：经批准的冻结 GitHub+npm 发布；内部摘要由系统自动校验。
 - `release-reconcile`：基于证据恢复 PARTIAL；冲突时人工介入。
 - `release-verify`：发布后验证；只有 `VERIFIED` 才是 happy end。
@@ -666,6 +674,19 @@ WorkBuddy 本机更新仅支持 macOS；其他平台返回不支持并跳过。
 release-finish 必须接收 `ship` 产出的已完成 postVerify run，不能直接使用较早的
 verify run；核心 prepare、publish、verify 流程仍跨平台。
 
+如果插件由项目选定的 Hub 通过 `postVerify` Hook 交付，发布单元还可以声明
+`postPublish.localHostUpdate`。Hook 达到 `DISTRIBUTED` 后，`ship`、`verify`、
+`post-release` 和 `release-finish` 会显示声明中的 Hub、插件和宿主。0.9.14 对这类
+目标只提供人工入口（`promptRequired: true`、`available: false`）：提示不会访问 Hub、
+探测宿主或运行宿主命令。Claude 和 Codex 使用各自已有的 marketplace 管理入口；Kimi
+使用冻结 GitHub Release 和现有人工确认路径；CodeBuddy 与 WorkBuddy 因无法固定 Hub
+ref 而继续人工处理。由冻结插件安装动作派生的原有可执行目标不受影响。
+
+生产 prepare 还会在本轮运行证据建立后、高成本快照和 Hook 之前执行一次尽力清理。
+它只删除已被更新完整谱系取代的终态运行目录，以及没有有效计划或外部写入迹象的封口
+失败 prepare。当前计划、最近完整谱系，以及所有非终态、部分成功、损坏、含糊或越界
+谱系都受保护。清理失败不会改变 prepare 结果。
+
 新的 `codebuddy-plugin` 项目配置必须显式声明 `marketplace`，避免不同产品线误用同一市场；`marketplaceSource`（消费者添加市场所用的 URL）仍可按需声明。只有已经冻结、且未携带该字段的历史计划会继续按旧规则解释为 `artifact-skill-set`，以保证 reconcile 可以重放原计划。
 
 每个 npm 分发在 `prepare` 时都会针对精确封装的 tarball 静态校验

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

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