release-skill 0.9.3 → 0.9.5

package/.claude-plugin/marketplace.json

@@ -9,7 +9,7 @@
     {
       "name": "release-skill",
       "source": "./",
-      "version": "0.9.3",
+      "version": "0.9.5",
       "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.9.3",
+  "version": "0.9.5",
   "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.3",
+  "version": "0.9.5",
   "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.3",
+  "version": "0.9.5",
   "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.3.",
+      "Prepare a release plan for version 0.9.5.",
       "Help me understand the release workflow."
     ]
   }

package/.kimi-plugin/plugin.json

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

package/CHANGELOG.md

@@ -1,5 +1,63 @@
 # Changelog
 
+<!-- release-skill:changelog:start version=0.9.5 locale=en baseline=sha256:21c87f71244641b1819ee77ca067f65fd29caa64e42229184cd552b82829d86b -->
+## [0.9.5] - 2026-09-02
+
+0.9.5 is a local source candidate that closes the postVerify-to-local-finish lifecycle, recognizes the supported real host install commands, and tightens standalone-index marketplace identity checks. It consumes the three Foundation packages at the exact 0.16.0 release. This note is not evidence of publication, real-host acceptance, consumer installation verification, or independent acceptance.
+
+### Security
+
+- Local finishing fails closed when the canonical plan or run evidence is missing, mismatched, incomplete, or not linked to the same VERIFIED lineage; host detection and host writes do not start on that path.
+- Any host plan remains a qualified frozen-plan path and requires a VERIFIED-run from the same release lineage before host acceptance; this source candidate does not provide that acceptance.
+
+### Added
+
+- Require completed postVerify evidence, including same-lineage VERIFIED data and every declared checkpoint, before any local host update is probed or executed. Incomplete postVerify evidence returns a bound `ship` continuation when state evidence is available.
+- Add the explicit `manual-index-checkpoint` first-release bootstrap path for Claude and Codex standalone-index distributions. The plan binds the expected plugin identity and leaves the final marketplace index commit pending until verify observes the remote index.
+
+### Changed
+
+- Recognize the supported real host install commands and environment boundaries separately for CodeBuddy and WorkBuddy; unsupported WorkBuddy platforms are reported without invoking a host command.
+- Require first-release bootstrap plans to observe an empty plugin repository without the target tag or GitHub Release, then match the marketplace name and selected entry exactly before continuing.
+- Preserve the complete selected marketplace entry metadata for ordinary non-bootstrap remote distributions while deriving verification identity only from the platform-owned fields.
+- The CodeBuddy plugin declares `marketplace: release-skill`, and both release-finish local-finish examples pass `--root <project-root>`.
+- Keep the narrow R-05 Hook cache v2 consumer path in the current 0.9.5 candidate; this does not add a broader Hook cache or host acceptance surface.
+
+### Upgrade Notes
+
+Prepare a new 0.9.5 plan when adopting these changes. Complete postVerify with `ship` before running post-release when the checklist reports `COMPLETE_POST_VERIFY`. Real-host acceptance can begin only after 0.9.5 is officially published and VERIFIED; the official 0.9.5 entry must be installed or reloaded first. A source candidate, an older installed entry, or the mere existence of plan and run files cannot complete real-host acceptance. Each selected host must complete a first successful update. On the second run, Claude, Kimi, CodeBuddy, and WorkBuddy must report `ALREADY_CURRENT`; Codex may report `UPDATED` only when it reinstalls the same exact 0.9.5 frozen reference, payload validation passes, and `restartRequired=true` is declared. A first-release bootstrap uses `manual-index-checkpoint` only for Claude or Codex standalone-index distributions and requires a manual index checkpoint during verify; it does not add general standalone-index support. This source candidate does not provide real-host acceptance.
+<!-- release-skill:changelog:end version=0.9.5 locale=en -->
+
+
+<!-- release-skill:changelog:start version=0.9.4 locale=en baseline=sha256:bd122e1e4f28539503d3bdd702f73cbabc675dc7006f750cc38ff08544b72dc5 -->
+## [0.9.4] - 2026-09-01
+
+0.9.4 is a local source candidate that lets multi-unit projects freeze and approve an explicit safe release scope while deferring unrelated units. It consumes the three Foundation packages at the exact 0.16.0 release. This note is not evidence of publication, real-host acceptance, consumer installation verification, or independent acceptance.
+
+### Security
+
+- Ship persists an explicit unit request only before plan freeze and rejects attempts to change it while resuming the same state. Once external writes begin, partial success remains `PARTIAL` and recovery stays forward-only within the original plan.
+- Any host plan remains a qualified frozen-plan path and requires a VERIFIED-run before host acceptance; this source candidate does not provide that acceptance.
+
+### Added
+
+- Add repeatable `--unit <id>` selection to prepare and the pre-freeze ship path. Successful explicit selection reports selected and deferred unit IDs plus the exact next prepare command for deferred units.
+- Require an explicitly selected scope to include the complete existing `publicSourceAuthorityReceipt` dependency closure. The command reports missing units and stops before hooks, snapshots, or plan writes instead of expanding the scope automatically.
+
+### Changed
+
+- Run unit-scoped document, version, snapshot, distribution, and verification-gate work only for selected units. Project configuration validation, generated-artifact freshness checks, and top-level hooks still cover the whole project.
+- Keep `plan.units` as the only frozen release-scope authority. Publish, reconcile, verify, and distribute continue to consume the complete frozen plan and do not accept a new unit selector.
+- Consume skill-family-contracts, skill-family-harness-node, and skill-family-engineering-kit at the exact 0.16.0 release through their public package-root APIs. The CodeBuddy plugin declares marketplace: release-skill, and both release-finish local-finish examples pass --root <project-root>.
+- For CodeBuddy, treat only the closed plugin-management command set as eligible to consume complete read-only output when the CLI reports childExitCode 0 but leaves a residual process group; retain the Foundation anomaly and completed SIGTERM cleanup as observable facts, run each write command at most once, and require the final plugin version and commit to match exactly. This handling does not extend to WorkBuddy or change release status.
+- Improve Kimi TUI prompt matching for ANSI boxed prompts and `>` characters in command output, so trust-and-install and reload prompts are recognized without treating ordinary output as an input prompt.
+
+### Upgrade Notes
+
+Existing commands that omit `--unit` keep the full configured release scope. Multi-unit projects may repeat `--unit` on prepare or on a new ship state to defer unrelated units. Review `releaseScope.deferredUnitIds` and the approval summary before approving. A scope that touches `publicSourceAuthorityReceipt` must include its coordinator and every subject. Do not add `--unit` to publish, reconcile, verify, or distribute; those commands must execute the complete frozen plan. Real-host acceptance can begin only after 0.9.4 is officially published and VERIFIED; the official 0.9.4 entry must be installed or reloaded first. A source candidate, an older installed entry, or the mere existence of plan and run files cannot complete real-host acceptance. Each selected host must complete a first successful update. On the second run, Claude, Kimi, CodeBuddy, and WorkBuddy must report `ALREADY_CURRENT`; Codex may report `UPDATED` only when it reinstalls the same exact 0.9.4 frozen reference, payload validation passes, and `restartRequired=true` is declared.
+<!-- release-skill:changelog:end version=0.9.4 locale=en -->
+
+
 <!-- release-skill:changelog:start version=0.9.3 locale=en baseline=sha256:96e5f9167abb13203ba308ebacbb081452f8c23e26ff0b377514556338ebdfff -->
 ## [0.9.3] - 2026-08-31
 

package/INSTALL.md

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

package/INSTALL.zh-CN.md

@@ -2,7 +2,7 @@
 
 [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.9.3 -->
+<!-- release-skill:release-version: 0.9.5 -->
 ## 前置条件
 
 - Node.js 22.0.0 或更高版本
@@ -104,7 +104,7 @@ Kimi Code 有交互式插件市场，但**没有可脚本化的非交互安装
 （切勿使用裸仓库地址，它会安装最新 release 或默认分支），确认信任提示后重新加载：
 
    ```
-   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.3
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.5
    /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.3 -->
+<!-- release-skill:release-version: 0.9.5 -->
 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,34 +14,35 @@ 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.3** (2026-08-31)
+**0.9.5** (2026-09-02)
 
-0.9.3 is a local source candidate for the four workflow safeguards and the narrow Hook cache v2 and isolated-install-tree integrations. It consumes the three Foundation packages at the exact 0.15.0 release. This note is not evidence of publication, real-host acceptance, consumer installation verification, or independent acceptance.
+0.9.5 is a local source candidate that closes the postVerify-to-local-finish lifecycle, recognizes the supported real host install commands, and tightens standalone-index marketplace identity checks. It consumes the three Foundation packages at the exact 0.16.0 release. This note is not evidence of publication, real-host acceptance, consumer installation verification, or independent acceptance.
 
 **Security**
 
-- Unknown, corrupt, non-stable, or unsupported observations remain fail-closed. A cache hit never replaces a Hook execution when the authority or identity evidence is unavailable, and no TTL or ambient PATH inference is used.
-- Any host plan remains a qualified frozen-plan path and requires a VERIFIED-run before host acceptance; this source candidate does not provide that acceptance.
+- Local finishing fails closed when the canonical plan or run evidence is missing, mismatched, incomplete, or not linked to the same VERIFIED lineage; host detection and host writes do not start on that path.
+- Any host plan remains a qualified frozen-plan path and requires a VERIFIED-run from the same release lineage before host acceptance; this source candidate does not provide that acceptance.
 
 **Added**
 
-- Add the opt-in pre-hook public-surface check, ship help and target-version conflict guard, verify lineage guidance, and evidence-based adoption suggestions without adding a new command, state, or approval authority.
-- Add the narrow Hook cache v2 consumer path: absolute-path and validated cwd-relative executable identity, closed input and environment binding, no TTL, and fail-closed cache reuse for bare PATH, PATHEXT, Windows, and unavailable observations while Hooks still execute cold.
-- Add the narrow isolated install-tree record path after a completed host command, recording host-added links without following them and rejecting declared-payload symlinks while preserving legacy full-tree semantics.
+- Require completed postVerify evidence, including same-lineage VERIFIED data and every declared checkpoint, before any local host update is probed or executed. Incomplete postVerify evidence returns a bound `ship` continuation when state evidence is available.
+- Add the explicit `manual-index-checkpoint` first-release bootstrap path for Claude and Codex standalone-index distributions. The plan binds the expected plugin identity and leaves the final marketplace index commit pending until verify observes the remote index.
 
 **Changed**
 
-- Consume skill-family-contracts, skill-family-harness-node, and skill-family-engineering-kit at the exact 0.15.0 release through their public package-root APIs.
-- Keep the 0.9.2 production plan PREPARED and immutable as an unpublished historical record now replaced by the 0.9.3 candidate; with an explicit target, only unfinished records that pass complete run, plan, digest/binding, and lineage validation and whose plan target matches participate in current recovery, while all other history remains diagnostics. Without a target, route still shows full-history diagnostics, but workflow selection remains based on the current diff and baseline.
-- The CodeBuddy plugin explicitly declares marketplace: release-skill, and both release-finish local-finish examples pass --root <project-root>.
+- Recognize the supported real host install commands and environment boundaries separately for CodeBuddy and WorkBuddy; unsupported WorkBuddy platforms are reported without invoking a host command.
+- Require first-release bootstrap plans to observe an empty plugin repository without the target tag or GitHub Release, then match the marketplace name and selected entry exactly before continuing.
+- Preserve the complete selected marketplace entry metadata for ordinary non-bootstrap remote distributions while deriving verification identity only from the platform-owned fields.
+- The CodeBuddy plugin declares `marketplace: release-skill`, and both release-finish local-finish examples pass `--root <project-root>`.
+- Keep the narrow R-05 Hook cache v2 consumer path in the current 0.9.5 candidate; this does not add a broader Hook cache or host acceptance surface.
 
 **Upgrade Notes**
 
-Real-host acceptance can begin only after 0.9.3 is officially published and VERIFIED; the official 0.9.3 entry must be installed or reloaded first. A source candidate, an older installed entry, or the mere existence of plan and run files cannot complete real-host acceptance. Each selected host must complete a first successful update. On the second run, Claude, Kimi, CodeBuddy, and WorkBuddy must report `ALREADY_CURRENT`; Codex may report `UPDATED` only when it reinstalls the same exact 0.9.3 frozen reference, payload validation passes, and `restartRequired=true` is declared. The 0.9.2 plan was never published and remains an immutable historical record. With an explicit target, only unfinished records that pass complete run, plan, digest/binding, and lineage validation and whose plan target matches participate in current recovery; all other history remains diagnostics. Without a target, route still shows full-history diagnostics, but workflow selection remains based on the current diff and baseline.
+Prepare a new 0.9.5 plan when adopting these changes. Complete postVerify with `ship` before running post-release when the checklist reports `COMPLETE_POST_VERIFY`. Real-host acceptance can begin only after 0.9.5 is officially published and VERIFIED; the official 0.9.5 entry must be installed or reloaded first. A source candidate, an older installed entry, or the mere existence of plan and run files cannot complete real-host acceptance. Each selected host must complete a first successful update. On the second run, Claude, Kimi, CodeBuddy, and WorkBuddy must report `ALREADY_CURRENT`; Codex may report `UPDATED` only when it reinstalls the same exact 0.9.5 frozen reference, payload validation passes, and `restartRequired=true` is declared. A first-release bootstrap uses `manual-index-checkpoint` only for Claude or Codex standalone-index distributions and requires a manual index checkpoint during verify; it does not add general standalone-index support. This source candidate does not provide real-host acceptance.
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **Current boundary:** v0.9.3 is the current source candidate. This README
+> **Current boundary:** v0.9.5 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
@@ -65,7 +66,7 @@ Real-host acceptance can begin only after 0.9.3 is officially published and VERI
 > publish global preflight.
 
 <!-- release-skill:capability:safe-first-command -->
-> **Production path verified since the v0.1.1 milestone; v0.9.3 is the current
+> **Production path verified since the v0.1.1 milestone; v0.9.5 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
@@ -94,12 +95,12 @@ 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.3 candidate includes the narrow R-05 Hook cache v2 consumer
+The current 0.9.5 candidate includes the narrow R-05 Hook cache v2 consumer
 path and the stable isolated install-tree record path (A2/A3). It 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.
-Foundation dependencies are pinned to the three released 0.15.0 packages.
+Foundation dependencies are pinned to the three released 0.16.0 packages.
 For new bundled-family Kimi/CodeBuddy plans, verify calls the released
 `runPluginVerification` entry with the complete frozen payload and records a
 minimal `install-only` observation receipt. Kimi maps to `kimi-code`; CodeBuddy
@@ -191,6 +192,37 @@ This scope summary is not a remote publication record or a consumer upgrade inst
 
 A release unit is a release object with independently configured version, public files, and distribution targets.
 
+### Selecting a release scope
+
+Multi-unit projects can repeat `--unit <id>` before the plan is frozen. Omitting
+the option keeps the existing full-scope behavior:
+
+```bash
+release-skill prepare --root "$PROJECT" --offline \
+  --unit runtime --unit plugin --json
+release-skill ship --root "$PROJECT" --target-version 1.2.3 \
+  --unit runtime --unit plugin --json
+```
+
+The selected IDs are normalized to project configuration order. Unit-scoped
+version, documentation, snapshot, distribution, and verification-gate work runs
+only for that scope. Full configuration validation, generated-artifact freshness
+checks, and top-level hooks still cover the whole project.
+
+An explicit scope that includes any unit named by
+`publicSourceAuthorityReceipt` must include its coordinator and every subject.
+release-skill reports the missing units and stops before hooks or plan writes; it
+does not expand the scope automatically. A successful explicit selection reports
+`releaseScope.selectedUnitIds`, `releaseScope.deferredUnitIds`, and the exact next
+prepare command for the deferred units.
+
+After freeze, `plan.units` is the only release-scope authority. Approval covers
+every action in that plan. `publish`, `reconcile`, `verify`, and `distribute` do
+not accept `--unit`; a partial external write remains `PARTIAL` and resumes
+forward within the same frozen plan. A resumed ship state may omit `--unit` and
+reuse its saved request, but cannot change that request or add it to a legacy
+full-scope state.
+
 ### Install
 
 - Node.js 22+, Git 2.30+, a target Git repository with at least one commit.
@@ -739,6 +771,10 @@ bundled-family CodeBuddy/WorkBuddy entry when the frozen tag and mutable branch
 both resolve to the frozen commit. It requires explicit user confirmation and
 does not change release status. Missing, standalone, inaccessible, or ambiguous
 CodeBuddy/WorkBuddy targets remain manual and receive no host mutation.
+WorkBuddy local updates are macOS-only; on other platforms they are skipped as
+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 `codebuddy-plugin` distribution may optionally declare `marketplace` (and
 `marketplaceSource`, the URL consumers use to add the marketplace) to override

package/README.zh-CN.md

@@ -2,40 +2,41 @@
 
 [English](README.md) · 安装指南：[中文](INSTALL.zh-CN.md) / [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.9.3 -->
+<!-- release-skill:release-version: 0.9.5 -->
 面向 Claude Code、CodeBuddy、WorkBuddy、Codex 和 Kimi Code 的发布准备工具，完整保留人工维护的文件内容。
 
 release-skill 帮助维护者回答三个问题：准备发布什么、还有哪些检查未通过、最终发布的内容是什么。它不重新生成、也不回写项目源文件。`prepare` 把每个配置的公开文件复制到隔离快照并验证字节——先冻结并供人工审阅，再从同一份冻结产物发布。`setup` 只显示确定性的 `compactSummary` 审阅视图，完整报告保留在临时会话目录中。
 
 <!-- release-skill:managed:start id=latest-release -->
-**0.9.3** (2026-08-31)
+**0.9.5** (2026-09-02)
 
-0.9.3 是四项工作流安全修补、Hook cache v2 窄接线和稳定隔离安装树记录接线的本地源码候选。三项 Foundation 依赖均精确消费已发布的 0.15.0。本说明不代表已经发布、完成真实宿主验收、完成消费者安装验证或通过独立验收。
+0.9.5 是当前本地源码候选，收口 postVerify 到本机收尾的生命周期，识别受支持的真实宿主安装命令，并收紧 standalone-index 市场索引的身份校验。三项 Foundation 依赖均精确消费已发布的 0.16.0。本说明不代表已经发布、完成真实宿主验收、完成消费者安装验证或通过独立验收。
 
 **安全**
 
-- 未知、损坏、非稳定或不支持的观察结果继续失败关闭。权威或身份证据不足时，缓存命中不能替代 Hook 执行；不使用 TTL，也不从环境 PATH 推断可执行文件身份。
-- 任何宿主计划都必须是合格冻结计划，且宿主验收要求 VERIFIED run；本源码候选不提供该验收。
+- canonical plan 或 run 证据缺失、摘要不一致、内容不完整或未连接到同一 VERIFIED 谱系时，本机收尾会失败关闭；该路径不会开始宿主探测或写入。
+- 任何宿主计划都必须是合格冻结计划，并要求同一发布谱系的 VERIFIED run 才能开始宿主验收；本源码候选不提供该验收。
 
 **新增**
 
-- 新增可选的 Hook 前公开表面检查、ship 帮助与目标版本冲突保护、verify 血缘提示和基于证据的接入建议，不增加新命令、状态或批准权威。
-- 新增窄范围 Hook cache v2 消费路径：支持绝对路径和经真实 cwd 校验的 cwd-relative executable identity，绑定封闭输入与环境，无 TTL；裸 PATH、PATHEXT、Windows 或观察不可用时仅禁止缓存复用，Hook 仍正常冷执行。
-- 新增宿主命令完成后的稳定隔离安装树记录路径：记录宿主附加链接但不跟随；声明载荷中的 symlink 仍失败关闭，同时保留 legacy 全树语义。
+- 本机更新前必须先取得同一发布谱系的 VERIFIED 证据，并逐项完成所有已声明 checkpoint；postVerify 尚未完成时不会探测或执行宿主。本机状态证据可用时，待处理路径会返回带绑定信息的 `ship` 续接命令。
+- 为 Claude 和 Codex 的 standalone-index 分发新增显式 `manual-index-checkpoint` 首发引导路径。计划会绑定预期插件身份，并把最终市场索引提交留到 verify 观察远端索引后确定。
 
 **变更**
 
-- 通过公开包根 API 精确消费 skill-family-contracts、skill-family-harness-node 和 skill-family-engineering-kit 0.15.0。
-- 保留从未发布的 0.9.2 production plan 作为不可变历史记录；它已由 0.9.3 候选取代。显式传入目标时，只有完整通过 run、plan、digest/binding 和 lineage 校验且计划目标匹配的未完成记录，才参与当前恢复；其他历史仅保留为 diagnostics。未传目标时仍展示全历史 diagnostics，但 workflow 始终按当前 diff 和 baseline 选择，历史不能覆盖工作流。
-- CodeBuddy plugin 显式声明 marketplace: release-skill，两个 release-finish local-finish 示例都显式传入 --root <project-root>。
+- 分别识别 CodeBuddy 与 WorkBuddy 支持的真实宿主安装命令和环境边界；在不支持 WorkBuddy 的平台上只报告跳过状态，不调用宿主命令。
+- 首发引导计划必须确认插件仓库为空、目标 tag 和 GitHub Release 均不存在，再严格匹配市场名称与选定条目后继续。
+- 普通非 bootstrap 远端分发保留完整的市场条目元数据；身份校验只取平台自有字段生成。
+- CodeBuddy 插件显式声明 `marketplace: release-skill`；两个 release-finish 本机收尾示例都传入 `--root <project-root>`。
+- 当前 0.9.5 候选保留窄范围的 R-05 Hook cache v2 消费路径；本版不扩大 Hook cache 或宿主验收范围。
 
 **升级说明**
 
-只有 0.9.3 正式发布并达到 VERIFIED，且先安装或重载正式的 0.9.3 入口，才能开始真实宿主验收。源码候选、旧的已安装入口或仅存在计划和运行文件都不能完成真实宿主验收。每个选定宿主都须首次成功更新。第二次运行时，Claude、Kimi、CodeBuddy 和 WorkBuddy 必须返回 `ALREADY_CURRENT`；Codex 可以返回 `UPDATED`，但仅当再次安装同一精确 0.9.3 冻结引用、载荷验证通过且声明 `restartRequired=true`。0.9.2 计划从未发布，作为不可变历史记录保留并已由 0.9.3 候选取代。显式传入目标时，只有完整通过 run、plan、digest/binding 和 lineage 校验且计划目标匹配的未完成记录，才参与当前恢复；其他历史仅保留为 diagnostics。未传目标时仍展示全历史 diagnostics，但 workflow 始终按当前 diff 和 baseline 选择，历史不能覆盖工作流。
+采用这些改动时请重新准备 0.9.5 计划。清单返回 `COMPLETE_POST_VERIFY` 时，先用 `ship` 完成 postVerify，再运行 post-release。只有 0.9.5 正式发布并达到 VERIFIED，才能开始真实宿主验收；必须先安装或重载正式的 0.9.5 入口。源码候选、旧的已安装入口，或仅存在计划和运行文件，都不能完成真实宿主验收。每个选定宿主都必须先完成首次成功更新。第二次运行时，Claude、Kimi、CodeBuddy 和 WorkBuddy 必须返回 `ALREADY_CURRENT`；Codex 可以使用 `UPDATED`，但只有在重新安装同一精确 0.9.5 冻结引用、载荷验证通过并声明 `restartRequired=true` 时才允许这样返回。首发引导只适用于 Claude 或 Codex 的 standalone-index 分发，并使用 `manual-index-checkpoint`；verify 期间必须完成一次人工索引检查，当前版本不扩展 standalone-index 的通用支持。本源码候选不提供真实宿主验收。
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **当前边界：** v0.9.3 只是当前源码候选。本 README 记录预期范围与验证边界，
+> **当前边界：** v0.9.5 只是当前源码候选。本 README 记录预期范围与验证边界，
 > 不代表已经发布、完成消费者安装验证或通过独立验收。
 > 版本可用性以对应发布记录及发布后验证结果为准。
 > v0.4.1 是更早的已发布里程碑（v0.2.2 曾处于已发布状态，后因平台验证收敛修复而更新）。
@@ -51,7 +52,7 @@ release-skill 帮助维护者回答三个问题：准备发布什么、还有哪
 > 远端唯一性检查在 `publish` 全局预检执行。
 
 <!-- release-skill:capability:safe-first-command -->
-> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.9.3 是当前源码候选，本 README 不证明该候选已经发布、完成消费者安装验证或通过独立验收。**
+> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.9.5 是当前源码候选，本 README 不证明该候选已经发布、完成消费者安装验证或通过独立验收。**
 > npm 安装的 CLI 是受支持的用户入口；源码 checkout 保留为开发/贡献者路径。
 >
 > **第一条命令：**
@@ -69,9 +70,9 @@ marketplace 委托目标工作区发布的边界不变。
 
 旧 production 计划缺少 `sourceAuthority` 时，在外部写入前拒绝。未发生外部写入的计划必须重新 prepare 并批准新摘要，不能补写旧计划或迁移批准。已有 `PARTIAL` 保留检查点，走匹配版本的恢复路径。evidence v1 只读；v2 顶层封闭，阶段扩展放在 `details`。摘要和恢复建议只作诊断，不构成发布权威。
 
-当前 0.9.3 候选包含窄范围的 R-05 Hook cache v2 消费路径和稳定隔离安装树记录路径（A2/A3）。当前仍不包含 R-02 安全整树盘点、R-10 历史发布验证的产品实现、真实 Kimi/WorkBuddy 公开市场安装与调用门禁或 Audit 公开离线发布记录验证器。本范围说明不构成远端发布记录或消费者升级指引。
+当前 0.9.5 候选包含窄范围的 R-05 Hook cache v2 消费路径和稳定隔离安装树记录路径（A2/A3）。当前仍不包含 R-02 安全整树盘点、R-10 历史发布验证的产品实现、真实 Kimi/WorkBuddy 公开市场安装与调用门禁或 Audit 公开离线发布记录验证器。本范围说明不构成远端发布记录或消费者升级指引。
 
-Foundation 三包精确依赖已发布的 0.15.0。新生成的 Kimi/CodeBuddy 同仓计划在 verify 阶段调用正式 `runPluginVerification`，把完整冻结载荷交给 Foundation，并记录最小的 `install-only` 观察收据。Kimi 映射为 `kimi-code`，CodeBuddy 映射为兼容的 `workbuddy`。`observed` 与 `payloadMatches` 只表示机制观察结果，不代表远端已发布或 release-skill 已完成领域验证。独立市场来源、真实市场安装和宿主调用仍是人工后续任务。
+Foundation 三包精确依赖已发布的 0.16.0。新生成的 Kimi/CodeBuddy 同仓计划在 verify 阶段调用正式 `runPluginVerification`，把完整冻结载荷交给 Foundation，并记录最小的 `install-only` 观察收据。Kimi 映射为 `kimi-code`，CodeBuddy 映射为兼容的 `workbuddy`。`observed` 与 `payloadMatches` 只表示机制观察结果，不代表远端已发布或 release-skill 已完成领域验证。独立市场来源、真实市场安装和宿主调用仍是人工后续任务。
 
 <!-- release-skill:maturity:distribute-v1 -->
 <!-- release-skill:capability:distribute -->
@@ -145,6 +146,32 @@ Foundation 三包精确依赖已发布的 0.15.0。新生成的 Kimi/CodeBuddy
 
 发布单元是独立配置版本、公开文件和分发目标的发布对象。
 
+### 选择本轮发布范围
+
+多发布单元项目可以在计划冻结前重复传入 `--unit <id>`。不传该参数时，继续选择
+配置中的全部单元：
+
+```bash
+release-skill prepare --root "$PROJECT" --offline \
+  --unit runtime --unit plugin --json
+release-skill ship --root "$PROJECT" --target-version 1.2.3 \
+  --unit runtime --unit plugin --json
+```
+
+命令会按项目配置顺序整理单元 ID。版本、发布文档、快照、分发和按单元绑定的验证门
+只处理选中范围；完整配置校验、生成物新鲜度检查和顶层 Hook 仍覆盖整个项目。
+
+显式范围只要包含 `publicSourceAuthorityReceipt` 声明的任一单元，就必须同时包含
+coordinator 和全部 subjects。release-skill 会列出缺少的单元，并在 Hook 或计划写入前
+停止，不会自动扩大范围。选择成功后，`releaseScope.selectedUnitIds` 和
+`releaseScope.deferredUnitIds` 分别列出本轮单元与延期单元；返回结果还会给出下一次
+准备延期单元的精确命令。
+
+计划冻结后，`plan.units` 是唯一发布范围权威，批准覆盖计划内的全部动作。
+`publish`、`reconcile`、`verify` 和 `distribute` 不接受 `--unit`。外部写入部分成功时
+仍进入 `PARTIAL`，只能在同一冻结计划内向前恢复。恢复已有 ship 状态时可以省略
+`--unit` 并沿用首次请求，但不能改变该请求，也不能给旧的全范围状态追加该参数。
+
 ### 安装
 
 - Node.js 22+、Git 2.30+、至少已有一个提交的目标 Git 仓库。
@@ -626,6 +653,9 @@ release-skill ship --root "$PROJECT" --hook-approval "$HOOK_APPROVAL_PATH" --jso
 对于已有的 bundled-family CodeBuddy/WorkBuddy 条目，只有冻结标签与可变分支都解析到
 冻结提交时才允许更新。该流程要求用户明确同意，且不改变发布状态。目标缺失、使用
 standalone 来源、远端不可访问或身份含糊时仍转人工处理，不修改宿主。
+WorkBuddy 本机更新仅支持 macOS；其他平台返回不支持并跳过。计划声明 postVerify hook 时，
+release-finish 必须接收 `ship` 产出的已完成 postVerify run，不能直接使用较早的
+verify run；核心 prepare、publish、verify 流程仍跨平台。
 
 `codebuddy-plugin` 分发可以可选地声明 `marketplace`（以及 `marketplaceSource`，即消费者添加市场所用的 URL）来覆盖默认统一市场 `artifact-skill-set`；未声明的分发保持默认值，冻结计划字节不变。
 

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

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

package/adapters/claude/bin/consumer-contract-vectors.json

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 1,
   "kind": "skill-family.contracts.consumer-contract-vectors",
-  "foundationVersion": "0.15.0",
+  "foundationVersion": "0.16.0",
   "sets": [
     {
       "capabilityId": "foundation.contracts.object-validation",
@@ -15,7 +15,7 @@
           "vectorId": "foundation.contracts.object-validation.consumer-v1.indeterminate",
           "vectorSetId": "foundation.contracts.object-validation.consumer-v1",
           "capabilityId": "foundation.contracts.object-validation",
-          "foundationVersion": "0.15.0",
+          "foundationVersion": "0.16.0",
           "contractId": "skill-family-contracts:validateDocument",
           "caseClass": "indeterminate",
           "strategy": "real-pure",
@@ -31,7 +31,7 @@
           "vectorId": "foundation.contracts.object-validation.consumer-v1.negative",
           "vectorSetId": "foundation.contracts.object-validation.consumer-v1",
           "capabilityId": "foundation.contracts.object-validation",
-          "foundationVersion": "0.15.0",
+          "foundationVersion": "0.16.0",
           "contractId": "skill-family-contracts:validateDocument",
           "caseClass": "negative",
           "strategy": "real-pure",
@@ -47,7 +47,7 @@
           "vectorId": "foundation.contracts.object-validation.consumer-v1.positive",
           "vectorSetId": "foundation.contracts.object-validation.consumer-v1",
           "capabilityId": "foundation.contracts.object-validation",
-          "foundationVersion": "0.15.0",
+          "foundationVersion": "0.16.0",
           "contractId": "skill-family-contracts:validateDocument",
           "caseClass": "positive",
           "strategy": "real-pure",
@@ -71,7 +71,7 @@
           "vectorId": "foundation.harness.atomic-write.consumer-v1.indeterminate",
           "vectorSetId": "foundation.harness.atomic-write.consumer-v1",
           "capabilityId": "foundation.harness.atomic-write",
-          "foundationVersion": "0.15.0",
+          "foundationVersion": "0.16.0",
           "contractId": "skill-family-harness-node:writeFileAtomic",
           "caseClass": "indeterminate",
           "strategy": "official-fake",
@@ -84,7 +84,7 @@
           "vectorId": "foundation.harness.atomic-write.consumer-v1.negative",
           "vectorSetId": "foundation.harness.atomic-write.consumer-v1",
           "capabilityId": "foundation.harness.atomic-write",
-          "foundationVersion": "0.15.0",
+          "foundationVersion": "0.16.0",
           "contractId": "skill-family-harness-node:writeFileAtomic",
           "caseClass": "negative",
           "strategy": "official-fake",
@@ -97,7 +97,7 @@
           "vectorId": "foundation.harness.atomic-write.consumer-v1.positive",
           "vectorSetId": "foundation.harness.atomic-write.consumer-v1",
           "capabilityId": "foundation.harness.atomic-write",
-          "foundationVersion": "0.15.0",
+          "foundationVersion": "0.16.0",
           "contractId": "skill-family-harness-node:writeFileAtomic",
           "caseClass": "positive",
           "strategy": "official-fake",