release-skill 0.8.1 → 0.9.0

package/.claude-plugin/marketplace.json

@@ -9,7 +9,7 @@
     {
       "name": "release-skill",
       "source": "./",
-      "version": "0.8.1",
+      "version": "0.9.0",
       "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
       "author": {
         "name": "广州市风荷科技有限公司"

package/.claude-plugin/plugin.json

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

package/.kimi-plugin/plugin.json

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

package/CHANGELOG.md

@@ -1,5 +1,36 @@
 # Changelog
 
+<!-- release-skill:changelog:start version=0.9.0 locale=en baseline=sha256:80f51046ce63386f75ed1a2b869cf3245732e9a1b040e11eb8942dba5f7c8fed -->
+## [0.9.0] - 2026-08-28
+
+0.9.0 is a local source candidate for multi-unit postPublish plans and optional post-release local finishing. This note records the 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 and post-publish verification results.
+
+### Security
+
+- release-finish requires a plan-digest confirmation and a VERIFIED run from the same release lineage before any host command. Host updates use a restricted environment; Claude/Codex exact results are bound to the real installed payload, and every host fails closed when the identity evidence its protocol can provide is insufficient.
+
+### Added
+
+- Plan version 3 freezes postPublish declarations per release unit as an ordered array. Each declaration carries its own targets, hooks, approval binding, execution bundle, checkpoints, and postVerify continuation while explicit plan versions 1 and 2 retain their established single-declaration behavior.
+- A new release-finish workflow derives a read-only local checklist from the frozen plan and VERIFIED run. After explicit user confirmation it can update Claude and Codex, drive the Kimi TUI and verify the resulting installation, or confirm that CodeBuddy/WorkBuddy already matches the frozen identity; CodeBuddy/WorkBuddy updates that cannot pin the frozen ref remain manual. None of these local actions changes the published release terminal state.
+
+### Changed
+
+- The distribute and postVerify phases preflight every declaration before the first external write, then re-observe mutable remote proposal state during execution. Checkpoint identifiers are namespaced by release unit, and an earlier hook failure skips all later-unit work.
+- PostPublish hook identifiers are unique across the complete plan. Prepare, setup, approval, distribute, and postVerify consume the same validation rule before side effects.
+
+### Fixed
+
+- Prevent a later unit's missing bundle or deterministic proposal conflict from being discovered only after an earlier unit has already written remotely.
+- Preserve PARTIAL when a checkpoint has succeeded before a later failure, and preserve BLOCKED when no external checkpoint succeeded.
+- Prevent duplicate target names and duplicate hook identifiers from collapsing evidence or approval identity across release units.
+
+### Upgrade Notes
+
+Prepare a new 0.9.0 plan to use plan version 3; do not edit or upgrade frozen older plans. Plan versions 1 and 2 remain readable only through their explicit compatibility path. release-finish is optional local follow-up, not publication evidence: branch merges, Kimi trust prompts, and local host changes still require explicit user consent, and unsupported exact-ref updates remain manual. Hook cache v2, safe full-tree inventory, the Audit offline release-record verifier, and mandatory public-marketplace host invocation gates remain outside this version.
+<!-- release-skill:changelog:end version=0.9.0 locale=en -->
+
+
 <!-- release-skill:changelog:start version=0.8.1 locale=en baseline=sha256:c1dcef984b85d6da26cba7f15225d03f1cbaedc510a7c63149306d49a2c5532e -->
 ## [0.8.1] - 2026-08-27
 

package/INSTALL.md

@@ -2,7 +2,7 @@
 
 [简体中文](INSTALL.zh-CN.md)
 
-<!-- release-skill:release-version: 0.8.1 -->
+<!-- release-skill:release-version: 0.9.0 -->
 ## Prerequisites
 
 - Node.js 22.0.0 or later
@@ -114,10 +114,16 @@ 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.8.1
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.0
    /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
+then re-reads Kimi's managed installation root and requires the version, tag,
+revision, and Git commit to match the frozen plan. This local check is not part
+of `verify` and does not alter the `VERIFIED` release state.
+
 No receipt or attestation is required. The `attest` command remains available
 only for frozen plans created by older versions that lack the
 `humanConsumersStrategy: manualFollowUps` marker.
@@ -145,6 +151,12 @@ reports `verifiedBySystem: false`. Install from the bundled-family marketplace
 `ifoohoo/release-skill` after publishing. No receipt or attestation is required
 for new plans; `attest` exists only for old frozen-plan compatibility.
 
+The optional `release-finish` workflow can inspect the CodeBuddy/WorkBuddy list
+after explicit confirmation. It reports `ALREADY_CURRENT` only when the listed
+marketplace, version, and frozen commit all match. Because the CLI cannot pin a
+ref, a mismatch remains `MANUAL_REQUIRED`; release-finish does not update to an
+unbound latest version.
+
 For a single session from a source checkout you can also point CodeBuddy at the
 generated plugin directory with `--plugin-dir <path>/adapters/workbuddy`; the
 adapter never references files outside its own directory.

package/INSTALL.zh-CN.md

@@ -2,7 +2,7 @@
 
 [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.8.1 -->
+<!-- release-skill:release-version: 0.9.0 -->
 ## 前置条件
 
 - Node.js 22.0.0 或更高版本
@@ -104,10 +104,15 @@ Kimi Code 有交互式插件市场，但**没有可脚本化的非交互安装
 （切勿使用裸仓库地址，它会安装最新 release 或默认分支），确认信任提示后重新加载：
 
    ```
-   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.8.1
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.0
    /plugins reload
    ```
 
+发布达到 `VERIFIED` 后，可选的 `release-finish` 工作流可以在用户明确同意后执行
+同一套 TUI 操作。随后它会重新读取 Kimi 的受管安装根，并要求版本、标签、修订号和
+Git 提交与冻结计划一致。这个本机检查不属于 `verify`，也不会改变已经完成的
+`VERIFIED` 发布状态。
+
 新计划无需收据或人工证明。`attest` 命令仅兼容缺少
 `humanConsumersStrategy: manualFollowUps` 标记的旧冻结计划。
 
@@ -129,6 +134,11 @@ codebuddy CLI 可以添加市场并安装插件，但 **`plugin marketplace add`
 不检查安装并返回 `verifiedBySystem: false`。发布后从 bundled-family 市场
 `ifoohoo/release-skill` 安装即可。新计划无需收据或人工证明；`attest` 只兼容旧冻结计划。
 
+可选的 `release-finish` 工作流会在用户明确同意后读取 CodeBuddy/WorkBuddy 的安装
+列表。只有市场、版本和冻结提交全部一致时才报告 `ALREADY_CURRENT`。由于 CLI 无法
+钉死 ref，不匹配时仍返回 `MANUAL_REQUIRED`；release-finish 不会改装到一个未绑定的
+latest 版本。
+
 源码检出后也可以用 `--plugin-dir <path>/adapters/workbuddy` 把 CodeBuddy 指向
 生成的插件目录做单会话使用；适配器不引用自身目录之外的任何文件。
 

package/README.md

@@ -2,7 +2,7 @@
 
 [简体中文](README.zh-CN.md) · Installation: [English](INSTALL.md) / [简体中文](INSTALL.zh-CN.md)
 
-<!-- release-skill:release-version: 0.8.1 -->
+<!-- release-skill:release-version: 0.9.0 -->
 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,33 +14,37 @@ 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.8.1** (2026-08-27)
+**0.9.0** (2026-08-28)
 
-0.8.1 is a local source candidate. This note records its 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 and post-publish verification results. The fresh 0.8.1 coordinate avoids overwriting the different public bytes already published as v0.8.0.
+0.9.0 is a local source candidate for multi-unit postPublish plans and optional post-release local finishing. This note records the 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 and post-publish verification results.
 
 **Security**
 
-- The occupied v0.8.0 tag and npm coordinate are not overwritten or reused. v0.8.1 receives a newly frozen plan, approval, tag, package, release, and post-publish verification lineage.
+- release-finish requires a plan-digest confirmation and a VERIFIED run from the same release lineage before any host command. Host updates use a restricted environment; Claude/Codex exact results are bound to the real installed payload, and every host fails closed when the identity evidence its protocol can provide is insufficient.
+
+**Added**
+
+- Plan version 3 freezes postPublish declarations per release unit as an ordered array. Each declaration carries its own targets, hooks, approval binding, execution bundle, checkpoints, and postVerify continuation while explicit plan versions 1 and 2 retain their established single-declaration behavior.
+- A new release-finish workflow derives a read-only local checklist from the frozen plan and VERIFIED run. After explicit user confirmation it can update Claude and Codex, drive the Kimi TUI and verify the resulting installation, or confirm that CodeBuddy/WorkBuddy already matches the frozen identity; CodeBuddy/WorkBuddy updates that cannot pin the frozen ref remain manual. None of these local actions changes the published release terminal state.
 
 **Changed**
 
-- Pin all three Foundation dependencies to released 0.13.0 packages. Packaging uses the existing generators for runtime resources, native files, legal materials, host profiles, and plugin-verification contracts.
-- Reuse Foundation runPluginVerification for complete local payload observation of frozen Kimi and CodeBuddy bundled-family plugins. CodeBuddy maps to Foundation's compatible workbuddy host. Marketplace installation and host invocation remain explicit manual follow-ups; Foundation observations do not replace release-domain gates or three-role README acceptance.
-- Evidence v2 closes the top level and stores phase extensions in typed details. Evidence v1 remains read-only. Summaries, producer versions, and recovery suggestions are diagnostic, never publication authority.
+- The distribute and postVerify phases preflight every declaration before the first external write, then re-observe mutable remote proposal state during execution. Checkpoint identifiers are namespaced by release unit, and an earlier hook failure skips all later-unit work.
+- PostPublish hook identifiers are unique across the complete plan. Prepare, setup, approval, distribute, and postVerify consume the same validation rule before side effects.
 
 **Fixed**
 
-- Config branch A keeps zero external actions and no sourceAuthority, even with a configured public source receipt. Production branch B and docs production freeze plan.sourceAuthority and retain remote consistency checks. Marketplace delegation is unchanged.
-- Fixes cover installed host surfaces, release-run lineage, Git hooks in frozen checkouts, pure configuration checks before long hooks, and adoption assessment. Focused self-tests verify their stated cases but do not establish publication, consumer installation, or independent candidate acceptance.
-- FAILED summaries, compatibility details, and returned errors now project the same domain recovery result when current-run evidence is available. Existing fallbacks, unknown without evidence, and successful verify null suggestions remain unchanged.
+- Prevent a later unit's missing bundle or deterministic proposal conflict from being discovered only after an earlier unit has already written remotely.
+- Preserve PARTIAL when a checkpoint has succeeded before a later failure, and preserve BLOCKED when no external checkpoint succeeded.
+- Prevent duplicate target names and duplicate hook identifiers from collapsing evidence or approval identity across release units.
 
 **Upgrade Notes**
 
-Old production plans missing sourceAuthority and checker v4 plans must not be silently upgraded; when no external writes occurred, prepare again and approve the new digest. Do not migrate old approvals or evidence. Preserve existing PARTIAL checkpoints and use matching-version recovery. Hook cache v1 is unchanged; old full-test evidence is not imported. R-02 safe full-tree inventory, R-05 Hook cache v2, R-10 implementation, real Kimi/WorkBuddy public-marketplace installation and invocation gates, and the Audit public offline release-record verifier are excluded.
+Prepare a new 0.9.0 plan to use plan version 3; do not edit or upgrade frozen older plans. Plan versions 1 and 2 remain readable only through their explicit compatibility path. release-finish is optional local follow-up, not publication evidence: branch merges, Kimi trust prompts, and local host changes still require explicit user consent, and unsupported exact-ref updates remain manual. Hook cache v2, safe full-tree inventory, the Audit offline release-record verifier, and mandatory public-marketplace host invocation gates remain outside this version.
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **Current boundary:** v0.8.1 is the current source candidate. This README
+> **Current boundary:** v0.9.0 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
@@ -64,7 +68,7 @@ Old production plans missing sourceAuthority and checker v4 plans must not be si
 > publish global preflight.
 
 <!-- release-skill:capability:safe-first-command -->
-> **Production path verified since the v0.1.1 milestone; v0.8.1 is the current
+> **Production path verified since the v0.1.1 milestone; v0.9.0 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
@@ -724,6 +728,13 @@ verification is automated. Kimi Code and CodeBuddy/WorkBuddy are returned as
 `manualFollowUps` with `verifiedBySystem: false`; their completion is not a
 condition for the automated release to reach `VERIFIED`.
 
+After `VERIFIED`, the optional `release-finish` workflow can update Claude and
+Codex from the frozen marketplace identity, drive Kimi's TUI and re-check its
+managed installation, or confirm an already exact CodeBuddy/WorkBuddy entry.
+It requires explicit user confirmation, does not change release status, and
+leaves CodeBuddy/WorkBuddy mismatches for manual handling because that CLI
+cannot pin the frozen ref.
+
 A `codebuddy-plugin` distribution may optionally declare `marketplace` (and
 `marketplaceSource`, the URL consumers use to add the marketplace) to override
 the default unified marketplace `artifact-skill-set`; undeclared distributions
@@ -749,9 +760,10 @@ declaration is narrowed to concrete targets.
 - no overwrite of branches/tags/releases or npm unpublish; create-only refs use
   `--force-with-lease=<ref>:` solely as an atomic compare-and-set assertion that
   the ref is absent, while existing branches use an ordinary non-force push;
-- no automated Kimi or CodeBuddy/WorkBuddy marketplace install checkpoint —
-  these installations remain explicit post-release team tasks and the system
-  does not verify their completion;
+- no Kimi or CodeBuddy/WorkBuddy marketplace install checkpoint in the release
+  state machine — optional release-finish can drive and re-check Kimi locally,
+  or confirm an already exact CodeBuddy/WorkBuddy entry, but those results do
+  not become publication evidence;
 - no promise of Windows or broad multi-platform native write support;
 - no hidden commit, push, tag, release, or package publication.
 

package/README.zh-CN.md

@@ -2,39 +2,43 @@
 
 [English](README.md) · 安装指南：[中文](INSTALL.zh-CN.md) / [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.8.1 -->
+<!-- release-skill:release-version: 0.9.0 -->
 面向 Claude Code、CodeBuddy、WorkBuddy、Codex 和 Kimi Code 的发布准备工具，完整保留人工维护的文件内容。
 
 release-skill 帮助维护者回答三个问题：准备发布什么、还有哪些检查未通过、最终发布的内容是什么。它不重新生成、也不回写项目源文件。`prepare` 把每个配置的公开文件复制到隔离快照并验证字节——先冻结并供人工审阅，再从同一份冻结产物发布。`setup` 只显示确定性的 `compactSummary` 审阅视图，完整报告保留在临时会话目录中。
 
 <!-- release-skill:managed:start id=latest-release -->
-**0.8.1** (2026-08-27)
+**0.9.0** (2026-08-28)
 
-0.8.1 当前只是本地源码候选。本说明记录预期范围与验证边界，不代表已经发布、完成消费者安装验证或通过独立验收。版本是否可用，须以对应发布记录及发布后验证结果为准。使用新的 0.8.1 坐标，是为了避免覆盖已经以 v0.8.0 发布的另一份公开制品。
+0.9.0 是多发布单元 postPublish 计划和可选发布后本机收尾能力的本地源码候选。本说明记录预期范围与验证边界，不代表已经发布、完成消费者安装验证或通过独立验收。版本是否可用，须以对应的生产发布记录和发布后验证结果为准。
 
 **安全**
 
-- 不会覆盖或复用已被占用的 v0.8.0 标签和 npm 坐标。v0.8.1 将重新冻结计划，并建立新的批准、标签、软件包、GitHub Release 与发布后验证血缘。
+- release-finish 在执行宿主命令前，要求确认计划摘要，并核对同一发布血缘的 VERIFIED run。宿主更新只传入受限环境；Claude/Codex 的精确结果绑定真实安装载荷，各宿主在自身协议能够提供的身份依据不足时都会失败关闭。
+
+**新增**
+
+- 计划版本 3 按发布单元冻结有序的 postPublish 声明数组。每项声明分别绑定目标、Hook、批准、执行包、检查点和 postVerify 后续动作；显式的计划版本 1、2 继续保持既有单声明语义。
+- 新增 release-finish 工作流。它从冻结计划和同一血缘的 VERIFIED run 派生只读本机收尾清单；用户明确同意后，可更新 Claude 和 Codex、驱动 Kimi TUI 并复验安装结果，或确认 CodeBuddy/WorkBuddy 已经精确匹配冻结身份。CodeBuddy/WorkBuddy 无法钉死冻结 ref 时仍转人工处理；这些本机动作都不改变已经完成的发布终态。
 
 **变更**
 
-- Foundation 三包精确依赖已发布的 0.13.0。打包继续通过既有生成器携带运行资源、原生文件、法律材料、宿主 Profile 和插件验证合同。
-- Kimi、CodeBuddy 的同仓冻结插件载荷改用 Foundation runPluginVerification 做完整本地安装观察。CodeBuddy 映射到 Foundation 中兼容的 workbuddy 宿主。真实市场安装和宿主调用仍作为人工后续任务；Foundation 观察不能替代发布领域门禁或 README 三角色验收。
-- evidence v2 顶层封闭，阶段扩展进入受类型约束的 details；evidence v1 保持只读。摘要、生产者版本和恢复建议只作诊断，不构成发布权威。
+- distribute 和 postVerify 在首次外部写入前预检全部声明，执行时重新观察可能变化的远端 proposal 状态。检查点 ID 按发布单元区分；前一项 Hook 失败后，后续单元全部跳过。
+- 整份计划中的 postPublish Hook ID 必须唯一。prepare、setup、批准、distribute 和 postVerify 在副作用发生前复用同一条校验规则。
 
 **修复**
 
-- config 场景 A 保持零外部动作、不生成 sourceAuthority，即使配置了公开来源收据也不例外。production 场景 B 与 docs production 冻结 plan.sourceAuthority，保留远端一致性检查。marketplace 委托发布的边界不变。
-- 修复覆盖实际安装宿主表面、发布运行血缘、冻结副本中的 Git Hook、长 Hook 前纯配置检查和接入评估。聚焦自测只证明对应场景，不代表已经发布、完成消费者安装验证或通过独立验收。
-- 有本次证据时，FAILED 摘要、兼容 details 与返回错误已接齐同一次领域恢复计算结果。既有回退、无证据时的 unknown 和成功 verify 的 null 建议保持不变。
+- 修复后续单元缺执行包或存在确定性 proposal 冲突时，前序单元已经写入远端的问题。
+- 任一检查点成功后发生后续失败时保留 PARTIAL；没有外部检查点成功时保持 BLOCKED。
+- 避免不同发布单元使用同名 target 或重复 Hook ID 时，证据与批准身份发生碰撞。
 
 **升级说明**
 
-缺 sourceAuthority 的旧 production 计划和 checker v4 计划不得静默升级；未发生外部写入时须重新 prepare 并批准新摘要，不迁移旧批准或证据。已有 PARTIAL 保留检查点，走匹配版本的恢复路径。Hook cache v1 不变，不导入旧 full-test 证据。本版不包含 R-02 安全整树盘点、R-05 Hook cache v2、R-10 产品实现、真实 Kimi/WorkBuddy 公开市场安装与调用门禁或 Audit 公开离线发布记录验证器。
+使用计划版本 3 时须重新生成 0.9.0 计划，禁止修改或升级已经冻结的旧计划。计划版本 1、2 只通过显式兼容路径读取。release-finish 是可选的本机后续动作，不构成发布证据：分支合并、Kimi 信任提示和本机宿主修改仍须用户明确同意；宿主不支持精确 ref 更新时继续转人工处理。本版不包含 Hook cache v2、安全整树盘点、Audit 离线发布记录验证器或强制的公开市场宿主调用门禁。
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **当前边界：** v0.8.1 只是当前源码候选。本 README 记录预期范围与验证边界，
+> **当前边界：** v0.9.0 只是当前源码候选。本 README 记录预期范围与验证边界，
 > 不代表已经发布、完成消费者安装验证或通过独立验收。
 > 版本可用性以对应发布记录及发布后验证结果为准。
 > v0.4.1 是更早的已发布里程碑（v0.2.2 曾处于已发布状态，后因平台验证收敛修复而更新）。
@@ -50,7 +54,7 @@ release-skill 帮助维护者回答三个问题：准备发布什么、还有哪
 > 远端唯一性检查在 `publish` 全局预检执行。
 
 <!-- release-skill:capability:safe-first-command -->
-> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.8.1 是当前源码候选，本 README 不证明该候选已经发布、完成消费者安装验证或通过独立验收。**
+> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.9.0 是当前源码候选，本 README 不证明该候选已经发布、完成消费者安装验证或通过独立验收。**
 > npm 安装的 CLI 是受支持的用户入口；源码 checkout 保留为开发/贡献者路径。
 >
 > **第一条命令：**
@@ -616,6 +620,11 @@ release-skill ship --root "$PROJECT" --hook-approval "$HOOK_APPROVAL_PATH" --jso
 
 每个适配器闭包都自带 CLI、skills 和 schemas 副本，安装后无需外部依赖即可运行。Claude/Codex 验证是自动化的；Kimi Code 和 CodeBuddy/WorkBuddy 以 `manualFollowUps` 返回并标记 `verifiedBySystem: false`，其完成情况不阻塞自动发布进入 `VERIFIED`。
 
+发布达到 `VERIFIED` 后，可选的 `release-finish` 工作流可以按冻结市场身份更新 Claude
+和 Codex、驱动 Kimi TUI 并复查受管安装，或确认 CodeBuddy/WorkBuddy 已经精确匹配。
+它要求用户明确同意，不改变发布状态；由于 CodeBuddy/WorkBuddy CLI 无法钉死冻结
+ref，不匹配时仍转人工处理。
+
 `codebuddy-plugin` 分发可以可选地声明 `marketplace`（以及 `marketplaceSource`，即消费者添加市场所用的 URL）来覆盖默认统一市场 `artifact-skill-set`；未声明的分发保持默认值，冻结计划字节不变。
 
 每个 npm 分发在 `prepare` 时都会针对精确封装的 tarball 静态校验
@@ -632,7 +641,7 @@ release-skill ship --root "$PROJECT" --hook-approval "$HOOK_APPROVAL_PATH" --jso
 - 不声称已经替项目完成真实生产 canary，不声称已完成真实插件市场验证；
 - `prepare --online` 只观察 bound 前序基线；目标唯一性由 publish 全局预检完成；
 - 不覆盖已有 branch/tag/Release，不 unpublish npm；
-- 不提供 Kimi 或 CodeBuddy/WorkBuddy marketplace 自动安装检查点——这些安装是发布后明确的团队待办，系统不核验其完成结果；
+- 发布状态机不提供 Kimi 或 CodeBuddy/WorkBuddy marketplace 安装检查点——可选的 release-finish 可以在本机驱动并复查 Kimi，或确认 CodeBuddy/WorkBuddy 已经精确匹配，但这些结果不构成发布证据；
 - 不承诺 Windows 或广泛的跨平台原生写入；
 - 不会隐藏地 commit、push、打 tag、创建 Release 或发布包。
 

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

@@ -9,7 +9,7 @@
     {
       "name": "release-skill",
       "source": "./",
-      "version": "0.8.1",
+      "version": "0.9.0",
       "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
       "author": {
         "name": "广州市风荷科技有限公司"

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

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

package/adapters/claude/bin/release-skill-local-finish.mjs

@@ -0,0 +1,4 @@
+#!/usr/bin/env node
+
+if (process.argv[2] !== 'post-release') process.argv.splice(2, 0, 'post-release');
+await import('./release-skill.mjs');