release-skill 0.9.1 → 0.9.4

package/.claude-plugin/marketplace.json

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

package/.kimi-plugin/plugin.json

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

package/CHANGELOG.md

@@ -1,5 +1,83 @@
 # Changelog
 
+<!-- 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
+
+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.
+
+### 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.
+
+### 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.
+
+### 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>.
+
+### 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.
+<!-- release-skill:changelog:end version=0.9.3 locale=en -->
+
+
+<!-- release-skill:changelog:start version=0.9.2 locale=en baseline=sha256:748e2f51de3ee9b773ddc2f0f2ffccb3756065c814ec218dffc738364ad25630 -->
+## [0.9.2] - 2026-08-30
+
+0.9.2 is a local source candidate for two release-finish maintenance updates and a route recovery maintenance update. Foundation remains pinned to 0.14.0, whose public temporary-workspace and raw-output APIs pass the default Node.js 22 macOS consumer composition. This note is not evidence of publication, real-host acceptance, consumer installation verification, or independent acceptance.
+
+### Security
+
+- The release-finish maintenance keeps the qualified frozen-plan boundary and the VERIFIED-run requirement; the consumer test combines the public withTemporaryWorkspace and superviseProcess.rawSink APIs under the default Node.js 22 macOS temporary directory.
+
+### Changed
+
+- Self-bootstrap now declares marketplace: release-skill explicitly for the CodeBuddy plugin.
+- Both release-finish local-finish examples now pass --root <project-root> explicitly.
+- Route recovery now skips only failed publish attempts that the current evidence-v2 writer contract proves never acquired release authority; unknown or corrupt history remains blocking DIAGNOSE with an exact path and formal next action.
+
+### Upgrade Notes
+
+Real-host acceptance can begin only after 0.9.2 is officially published and VERIFIED; the official 0.9.2 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.2 frozen reference, payload validation passes, and `restartRequired=true` is declared. In the current workspace, route still reports 63 DIAGNOSE records and 2 VERIFY records; the first UNKNOWN legacy record has no automatic safe recovery entry and requires the formal diagnostic action.
+<!-- release-skill:changelog:end version=0.9.2 locale=en -->
+
+
 <!-- release-skill:changelog:start version=0.9.1 locale=en baseline=sha256:71720f2bbde891ebccda25baf35ef03593d1f6aee1077aeccb3b4af4d2eddfc0 -->
 ## [0.9.1] - 2026-08-28
 

package/INSTALL.md

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

package/INSTALL.zh-CN.md

@@ -2,7 +2,7 @@
 
 [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.9.1 -->
+<!-- release-skill:release-version: 0.9.4 -->
 ## 前置条件
 
 - 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.1
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.4
    /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.1 -->
+<!-- release-skill:release-version: 0.9.4 -->
 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,38 +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.1** (2026-08-28)
+**0.9.4** (2026-09-01)
 
-0.9.1 is a local source candidate for safer post-release host finishing. It now pins Foundation 0.14.0, whose public temporary-workspace and raw-output APIs pass the default Node.js 22 macOS consumer composition. This note is not evidence of publication, real-host acceptance, consumer installation verification, or independent acceptance.
+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**
 
-- Real-host acceptance requires a qualified frozen release plan and a VERIFIED run from the same release lineage. The workflow confirms the exact plan digest and selected hosts before any host write. release-skill's optional local finishing never changes the terminal release state.
+- 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.
 
-**Changed**
+**Added**
 
-- Pin skill-family-contracts, skill-family-harness-node, and skill-family-engineering-kit together at 0.14.0. A consumer test now combines the public withTemporaryWorkspace and superviseProcess.rawSink APIs under the default Node.js 22 macOS temporary directory.
-- Derive platform-manifest.json version ownership from package.json.version and check manifest freshness before prepare runs hooks, including docs-only and config-only workflows.
-- Expand ship's plan-approval summary from the frozen plan so reviewers can see public repositories, branch strategies, tags, npm targets, GitHub Releases, external action targets, waivers, and separately gated postPublish hooks.
-- Claude now re-observes the installed plugin after marketplace rebinding before deciding whether a plugin update is still required. Codex keeps the formal frozen-marketplace reinstall path.
-- Kimi accepts a managed installation without a .git directory when the package name, version, release tag, installed revision, managed root, and real payload all match. Legacy local-path entries are removed and reinstalled from the pinned release tag in one controlled TUI session.
-- CodeBuddy/WorkBuddy can update an existing bundled-family entry only when one remote query proves that the frozen tag and mutable marketplace branch both resolve to the frozen commit. The final installed list must contain exactly one entry with the expected marketplace, version, and revision.
+- 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.
 
-**Fixed**
+**Changed**
 
-- Prevent prepare from freezing a stale platform manifest into the public snapshot or npm tarball.
-- Remove the misleading claim that plan approval includes a requiresApproval postPublish checkpoint. Plan approval remains the single normal release-level approval; each gated postPublish hook needs its own approval record, bound to the plan digest and hook id for at most 24 hours.
-- Avoid a redundant Claude plugin update after marketplace rebinding has already removed or replaced the old installed entry.
-- Classify legacy Kimi local-path installations before managed-root checks so they can follow the explicit migration path.
-- Keep CodeBuddy/WorkBuddy host state unchanged when the target is absent, standalone, inaccessible, ambiguous, or inconsistent with the frozen release identity.
+- 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**
 
-Real-host acceptance can begin only after 0.9.1 is officially published and VERIFIED; the official 0.9.1 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 and a second run that reports `ALREADY_CURRENT`.
+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:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **Current boundary:** v0.9.1 is the current source candidate. This README
+> **Current boundary:** v0.9.4 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
@@ -69,7 +66,7 @@ Real-host acceptance can begin only after 0.9.1 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.1 is the current
+> **Production path verified since the v0.1.1 milestone; v0.9.4 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
@@ -98,11 +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.
 
-This version excludes R-02 safe full-tree inventory, R-05 Hook cache v2,
-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.14.0 packages.
+The current 0.9.4 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.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
@@ -194,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.
@@ -370,6 +399,7 @@ ACTOR=your-name
      --plan "$PLAN_PATH" --approval "$APPROVAL_PATH" --json)
    PUBLISH_RUN_PATH=$(printf '%s\n' "$PUBLISH_JSON" | jq -r '.runPath')
    ```
+   A valid approved production plan may enter `publish` directly; `route` is only a workflow suggestion. `publish` still requires the plan, approval, frozen digest and artifact identity, remote preflight, and fail-closed `PARTIAL` checkpoint rules.
    `PUBLISHED` is **not** the terminal state.
 9. **verify** — consumer install check:
    ```bash
@@ -758,7 +788,7 @@ the first minimal semantic boundary, so the static gate fails closed until the
 declaration is narrowed to concrete targets.
 
 <!-- release-skill:capability:unsupported-scope -->
-- **not in the current version:** Hook cache v2 (executor-identity receipts, R-05) — the current version keeps the v1 content-bound hook cache and never imports old run evidence; full consumer install-tree scanning (R-02) — only declared files are verified byte-for-byte; and a real-host (Kimi/WorkBuddy) verification gate — host verification stays a design and can never produce `PASS`/`VERIFIED` in this version;
+- **not in the current version:** full consumer install-tree scanning (R-02) — the current implementation handles only the declared public surface and the stable isolated install-tree record; and a real-host (Kimi/WorkBuddy) verification gate — host verification stays a non-blocking manual follow-up and does not produce `PASS`/`VERIFIED` evidence;
 - no automatic README generation or source-file overwrite;
 - no automatic conflict merge or rollback workflow;
 - no claim that a real production canary has run for marketplace verification;

package/README.zh-CN.md

@@ -2,44 +2,41 @@
 
 [English](README.md) · 安装指南：[中文](INSTALL.zh-CN.md) / [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.9.1 -->
+<!-- release-skill:release-version: 0.9.4 -->
 面向 Claude Code、CodeBuddy、WorkBuddy、Codex 和 Kimi Code 的发布准备工具，完整保留人工维护的文件内容。
 
 release-skill 帮助维护者回答三个问题：准备发布什么、还有哪些检查未通过、最终发布的内容是什么。它不重新生成、也不回写项目源文件。`prepare` 把每个配置的公开文件复制到隔离快照并验证字节——先冻结并供人工审阅，再从同一份冻结产物发布。`setup` 只显示确定性的 `compactSummary` 审阅视图，完整报告保留在临时会话目录中。
 
 <!-- release-skill:managed:start id=latest-release -->
-**0.9.1** (2026-08-28)
+**0.9.4** (2026-09-01)
 
-0.9.1 是发布后本机宿主安全收尾的本地源码候选。三项 Foundation 依赖已精确锁定到 0.14.0；其正式临时工作区与原始输出接口已通过默认 Node.js 22 和 macOS 消费者组合。本说明不代表已经发布、完成真实宿主验收、完成消费者安装验证或通过独立验收。
+0.9.4 是支持多发布单元项目显式冻结安全发布范围、延期无关单元的本地源码候选。三项 Foundation 依赖均精确消费已发布的 0.16.0。本说明不代表已经发布、完成真实宿主验收、完成消费者安装验证或通过独立验收。
 
 **安全**
 
-- 真实宿主验收须使用合格的冻结发布计划与同一发布血缘的 VERIFIED run。工作流须在宿主写入前确认精确的计划摘要和选定宿主。release-skill 的可选本机收尾不会改变发布终态。
+- ship 只在计划冻结前保存显式单元请求；沿用同一状态恢复时不能改变范围。外部写入开始后若出现部分成功，状态仍为 `PARTIAL`，只能在原计划内向前恢复。
+- 任何宿主计划都必须是合格冻结计划，且宿主验收要求 VERIFIED run；本源码候选不提供该验收。
 
-**变更**
+**新增**
 
-- skill-family-contracts、skill-family-harness-node 和 skill-family-engineering-kit 已一起精确锁定到 0.14.0。新增消费者测试，在默认 Node.js 22 与 macOS 临时目录下组合正式 withTemporaryWorkspace 与 superviseProcess.rawSink 接口。
-- platform-manifest.json 的版本归属改为从 package.json.version 派生。prepare 在运行 hook 前检查 manifest 新鲜度，docs-only 和 config-only 工作流同样执行该检查。
-- ship 现在从冻结计划展开批准摘要。审阅者可直接查看公开仓库、分支策略、标签、npm 目标、GitHub Release、外部动作目标、豁免以及需要单独批准的 postPublish hook。
-- Claude 重新绑定市场后，会再次观察本机安装状态，再判断是否仍需更新插件。Codex 继续使用正式的冻结市场重装路径。
-- Kimi 的受管安装只要包名、版本、发布标签、已安装修订号、受管根和真实载荷都匹配，即使没有 .git 目录也可通过。旧的本地路径条目会在同一个受控 TUI 会话中先移除，再从钉死的发布标签安装。
-- CodeBuddy/WorkBuddy 只在一次远端查询证明冻结标签和可变市场分支都解析到冻结提交后，更新已有的 bundled-family 条目。最终安装列表必须只有一个条目，且市场、版本和修订号都符合预期。
+- prepare 和冻结前的 ship 支持重复传入 `--unit <id>`。显式选择成功后，命令会列出选中单元、延期单元，以及下一次准备延期单元的精确命令。
+- 显式范围命中现有 `publicSourceAuthorityReceipt` 依赖闭包时，必须同时包含 coordinator 和全部 subjects。范围不完整会在 Hook、快照和计划写入前停止，并列出缺少的单元；命令不会自动扩大范围。
 
-**修复**
+**变更**
 
-- 防止 prepare 把陈旧的 platform manifest 冻结进公开快照或 npm tarball。
-- 移除“计划批准已包含 requiresApproval postPublish checkpoint”的误导性说明。冻结计划批准仍是正常发布级流程的唯一批准门；每个受限的 postPublish hook 仍需独立批准记录，记录绑定计划摘要与 hook id，有效期最长 24 小时。
-- 避免 Claude 重新绑定市场后，旧安装已经移除或替换却仍重复执行插件更新。
-- 在检查受管根之前识别 Kimi 的旧本地路径安装，使其进入明确的迁移流程。
-- CodeBuddy/WorkBuddy 目标缺失、使用 standalone 来源、远端不可访问、身份含糊或与冻结身份不一致时，保持宿主不变。
+- 版本、发布文档、快照、分发和按单元绑定的验证门只处理选中单元。完整项目配置校验、生成物新鲜度检查和顶层 Hook 仍覆盖整个项目。
+- `plan.units` 继续作为冻结后的唯一发布范围权威。publish、reconcile、verify 和 distribute 仍消费完整冻结计划，不增加单元选择参数。
+- 通过公开包根 API 精确消费 skill-family-contracts、skill-family-harness-node 和 skill-family-engineering-kit 0.16.0。CodeBuddy plugin 显式声明 marketplace: release-skill，两个 release-finish local-finish 示例都显式传入 --root <project-root>。
+- CodeBuddy 只对封闭的插件管理命令集合采用完整只读输出：即使命令报告 childExitCode 0 但残留进程组，仍保留 Foundation 异常和已完成的 SIGTERM 清理事实；每个写命令最多执行一次，并要求最终插件版本和提交精确一致。该处理不扩展到 WorkBuddy，也不改变发布状态。
+- 修正 Kimi TUI 对 ANSI 框线提示以及命令输出中 `>` 字符的识别，使信任安装和重新加载提示能够被识别，同时避免把普通输出误判为输入提示。
 
 **升级说明**
 
-只有 0.9.1 正式发布并达到 VERIFIED，且先安装或重载正式的 0.9.1 入口，才能开始真实宿主验收。源码候选、旧的已安装入口或仅存在计划和运行文件都不能完成真实宿主验收。每个选定宿主都须首次成功更新，第二次运行返回 `ALREADY_CURRENT`。
+未传 `--unit` 的现有命令继续选择配置中的全部发布单元。多发布单元项目可以在 prepare 或新的 ship 状态上重复传入 `--unit`，延期无关单元。批准前应审阅 `releaseScope.deferredUnitIds` 和批准摘要。范围只要命中 `publicSourceAuthorityReceipt`，就必须包含 coordinator 和全部 subjects。publish、reconcile、verify、distribute 不接受 `--unit`，这些命令必须完整执行冻结计划。只有 0.9.4 正式发布并达到 VERIFIED，且先安装或重载正式的 0.9.4 入口，才能开始真实宿主验收。源码候选、旧的已安装入口或仅存在计划和运行文件都不能完成真实宿主验收。每个选定宿主都须首次成功更新。第二次运行时，Claude、Kimi、CodeBuddy 和 WorkBuddy 必须返回 `ALREADY_CURRENT`；Codex 可以返回 `UPDATED`，但仅当再次安装同一精确 0.9.4 冻结引用、载荷验证通过且声明 `restartRequired=true`。
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **当前边界：** v0.9.1 只是当前源码候选。本 README 记录预期范围与验证边界，
+> **当前边界：** v0.9.4 只是当前源码候选。本 README 记录预期范围与验证边界，
 > 不代表已经发布、完成消费者安装验证或通过独立验收。
 > 版本可用性以对应发布记录及发布后验证结果为准。
 > v0.4.1 是更早的已发布里程碑（v0.2.2 曾处于已发布状态，后因平台验证收敛修复而更新）。
@@ -55,7 +52,7 @@ release-skill 帮助维护者回答三个问题：准备发布什么、还有哪
 > 远端唯一性检查在 `publish` 全局预检执行。
 
 <!-- release-skill:capability:safe-first-command -->
-> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.9.1 是当前源码候选，本 README 不证明该候选已经发布、完成消费者安装验证或通过独立验收。**
+> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.9.4 是当前源码候选，本 README 不证明该候选已经发布、完成消费者安装验证或通过独立验收。**
 > npm 安装的 CLI 是受支持的用户入口；源码 checkout 保留为开发/贡献者路径。
 >
 > **第一条命令：**
@@ -73,9 +70,9 @@ marketplace 委托目标工作区发布的边界不变。
 
 旧 production 计划缺少 `sourceAuthority` 时，在外部写入前拒绝。未发生外部写入的计划必须重新 prepare 并批准新摘要，不能补写旧计划或迁移批准。已有 `PARTIAL` 保留检查点，走匹配版本的恢复路径。evidence v1 只读；v2 顶层封闭，阶段扩展放在 `details`。摘要和恢复建议只作诊断，不构成发布权威。
 
-本版不包含 R-02 安全整树盘点、R-05 Hook cache v2、R-10 历史发布验证的产品实现、真实 Kimi/WorkBuddy 公开市场安装与调用门禁或 Audit 公开离线发布记录验证器。本范围说明不构成远端发布记录或消费者升级指引。
+当前 0.9.4 候选包含窄范围的 R-05 Hook cache v2 消费路径和稳定隔离安装树记录路径（A2/A3）。当前仍不包含 R-02 安全整树盘点、R-10 历史发布验证的产品实现、真实 Kimi/WorkBuddy 公开市场安装与调用门禁或 Audit 公开离线发布记录验证器。本范围说明不构成远端发布记录或消费者升级指引。
 
-Foundation 三包精确依赖已发布的 0.14.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 -->
@@ -149,6 +146,32 @@ Foundation 三包精确依赖已发布的 0.14.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 仓库。
@@ -310,6 +333,7 @@ ACTOR=your-name
      --plan "$PLAN_PATH" --approval "$APPROVAL_PATH" --json)
    PUBLISH_RUN_PATH=$(printf '%s\n' "$PUBLISH_JSON" | jq -r '.runPath')
    ```
+   持有合法批准的 production plan 时可以直接进入 `publish`；`route` 只是工作流建议。`publish` 仍要求计划、批准、冻结摘要与制品身份、远端预检，并在检查点失败时保持 fail-closed 的 `PARTIAL` 规则。
    `PUBLISHED` **不是**终态。
 9. **verify** — 消费者安装检查：
    ```bash
@@ -640,7 +664,7 @@ standalone 来源、远端不可访问或身份含糊时仍转人工处理，不
 静态门禁会阻断，直到入口声明收窄为具体目标。
 
 <!-- release-skill:capability:unsupported-scope -->
-- **当前版本不含：** Hook cache v2（执行器身份收据，R-05）——当前版本保持 v1 内容绑定缓存，且从不导入旧运行证据；消费者安装整树盘点（R-02）——只对声明文件做逐字节核对；真实宿主（Kimi/WorkBuddy）验证门禁——宿主验证仍是设计，本版本中不能产生 `PASS` 或 `VERIFIED`；
+- **当前版本不含：** 消费者安装整树盘点（R-02）——当前版本只处理声明的公开表面和稳定隔离安装树记录；真实宿主（Kimi/WorkBuddy）验证门禁——宿主验证仍是非阻断的人工后续任务，不产生 `PASS` 或 `VERIFIED` 证据；
 - 不自动生成 README，不覆盖项目源文件；
 - 不自动合并冲突，也不要求回滚工作流；
 - 不声称已经替项目完成真实生产 canary，不声称已完成真实插件市场验证；

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

@@ -9,7 +9,7 @@
     {
       "name": "release-skill",
       "source": "./",
-      "version": "0.9.1",
+      "version": "0.9.4",
       "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.1",
+  "version": "0.9.4",
   "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.14.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.14.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.14.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.14.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.14.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.14.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.14.0",
+          "foundationVersion": "0.16.0",
           "contractId": "skill-family-harness-node:writeFileAtomic",
           "caseClass": "positive",
           "strategy": "official-fake",

package/adapters/claude/bin/error-codes.json

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 1,
   "kind": "skill-family.contracts.error-codes",
-  "contractsVersion": "1.14.0",
+  "contractsVersion": "1.15.0",
   "policy": {
     "format": "^SFC[0-9]{4}$",
     "ranges": [