release-skill 0.2.9 → 0.4.0

package/README.md

@@ -2,7 +2,7 @@
 
 [简体中文](README.zh-CN.md) · Installation: [English](INSTALL.md) / [简体中文](INSTALL.zh-CN.md)
 
-<!-- release-skill:release-version: 0.2.9 -->
+<!-- release-skill:release-version: 0.4.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,21 +14,26 @@ 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.2.9** (2026-07-31)
+**0.4.0** (2026-08-02)
 
-v0.2.9 makes missing expected public-surface configuration visible during assessment and preparation without blocking existing projects.
+v0.4.0 simplifies the production release path to one frozen-plan approval and moves unavailable Kimi or CodeBuddy installations into non-blocking manual follow-up tasks.
 
 **Added**
 
-- **Adoption warning**: assess reports `PUBLIC_SURFACE_CONFIG_MISSING` for every release unit that has not configured `expectedPublicSurface`.
+- **Manual consumer follow-ups**: when Kimi or CodeBuddy cannot be installed automatically, the release records an installation task after publishing without requiring system attestation.
 
 **Changed**
 
-- **Prepare visibility**: prepare records and returns the same non-blocking warning, and the CLI exposes it in both JSON and human-readable output.
+- **Single release approval**: the normal production path now asks only for approval of the immutable release plan; invoking a command authorizes its configured hooks and gates.
+- **Non-blocking human consumers**: Kimi and CodeBuddy manual installation tasks no longer prevent the automated release from reaching `VERIFIED`.
+
+**Removed**
+
+- **Redundant confirmation flags**: legacy plan-digest repetition, production-confirmation, hook-authorization, and manual-attestation interactions were removed from the normal release path.
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **Current boundary:** v0.2.9 is the current release (v0.2.2 previously held
+> **Current boundary:** v0.4.0 is the current release (v0.2.2 previously held
 > published status before the platform verification convergence fix was added).
 > v0.1.1 completed a real production release to GitHub and npm — the first
 > production-verified milestone — followed by
@@ -46,7 +51,7 @@ v0.2.9 makes missing expected public-surface configuration visible during assess
 > publish global preflight.
 
 <!-- release-skill:capability:safe-first-command -->
-> **Production path verified since the v0.1.1 milestone; v0.2.9 is the current
+> **Production path verified since the v0.1.1 milestone; v0.4.0 is the current
 > release.** The npm-installed CLI is the supported user entry. Source checkout
 > is the development/contributor fallback.
 >
@@ -57,10 +62,9 @@ v0.2.9 makes missing expected public-surface configuration visible during assess
 <!-- release-skill:maturity:v0.1-boundary -->
 <!-- release-skill:maturity:boundary -->
 > **Safe defaults:** the recommended path is `help → assess → prepare --offline →
-> human review`. Production publishing adds `prepare --production → approve →
-> publish --confirm-production <planDigest>`; a `bound` previous-public baseline
-> specifically requires `prepare --online --production`. Without digest confirmation,
-> no remote preflight or write starts.
+> human review`. Production publishing uses `ship --target-version <ver> → ship --approve --actor <name>`.
+> The `ship` command runs hooks and gates automatically; the only human gate is plan approval.
+> Kimi/CodeBuddy installations are non-blocking manual follow-up tasks (not verified by system).
 
 ## Table of contents
 
@@ -112,6 +116,20 @@ See [INSTALL.md](INSTALL.md) for CodeBuddy, Codex, and Kimi Code commands.
 
 ### Main workflow
 
+For routine releases, use the durable fast path. It persists authoritative
+paths and resumes safely, so a normal run needs at most one human gate: the
+frozen plan approval. `ship` runs configured hooks and verification gates
+automatically. Kimi/CodeBuddy installations are non-blocking post-release
+manual tasks; the system does not verify their completion.
+
+```bash
+release-skill ship --root "$PROJECT" --target-version 1.2.3 --json
+release-skill ship --root "$PROJECT" --approve --actor "$ACTOR" --json
+```
+
+During development, `release-skill hooks validate` runs declared hooks and
+writes the same content-bound cache receipts that `prepare` consumes.
+
 Run these steps in order. Steps 1-4 are safe (read-only or local-only);
 steps 5-9 require explicit human gates.
 
@@ -177,41 +195,32 @@ ACTOR=your-name
    ```
 4. **prepare** — local snapshot and plan freeze:
    ```bash
-   "${CLI[@]}" prepare --root "$PROJECT" --offline \
-     --acknowledge-hook-side-effects \
-     --acknowledge-gate-side-effects --json
+   "${CLI[@]}" prepare --root "$PROJECT" --offline --json
    ```
-   Omit an acknowledgement only when that project config has no corresponding
-   hook or snapshot gate. Never grant either acknowledgement before reviewing
-   the configured executable, arguments, working directory, and side effects.
 5. **Human review:** inspect `planPath`, `externalActions`, `targetVersion`, and `planDigest`.
 6. **prepare --production** — freeze the production plan:
    ```bash
-   PLAN_JSON=$("${CLI[@]}" prepare --root "$PROJECT" --online --production \
-     --acknowledge-hook-side-effects \
-     --acknowledge-gate-side-effects --json)
+   PLAN_JSON=$("${CLI[@]}" prepare --root "$PROJECT" --online --production --json)
    PLAN_PATH=$(printf '%s\n' "$PLAN_JSON" | jq -r '.planPath')
    PLAN_DIGEST=$(printf '%s\n' "$PLAN_JSON" | jq -r '.planDigest')
    ```
-7. **approve** — human approval bound to the plan digest (24-hour expiry):
+7. **approve** — human approval (digest auto-read from plan, 24-hour expiry):
    ```bash
    APPROVAL_JSON=$("${CLI[@]}" approve --plan "$PLAN_PATH" \
-     --digest "$PLAN_DIGEST" --actor "$ACTOR" --json)
+     --actor "$ACTOR" --json)
    APPROVAL_PATH=$(printf '%s\n' "$APPROVAL_JSON" | jq -r '.approvalPath')
    ```
 8. **publish** — remote writes start here:
    ```bash
    PUBLISH_JSON=$("${CLI[@]}" publish --root "$PROJECT" \
-     --plan "$PLAN_PATH" --approval "$APPROVAL_PATH" \
-     --confirm-production "$PLAN_DIGEST" --json)
+     --plan "$PLAN_PATH" --approval "$APPROVAL_PATH" --json)
    PUBLISH_RUN_PATH=$(printf '%s\n' "$PUBLISH_JSON" | jq -r '.runPath')
    ```
    `PUBLISHED` is **not** the terminal state.
 9. **verify** — consumer install check:
    ```bash
    "${CLI[@]}" verify --root "$PROJECT" \
-     --plan "$PLAN_PATH" --run "$PUBLISH_RUN_PATH" \
-     --acknowledge-gate-side-effects --json
+     --plan "$PLAN_PATH" --run "$PUBLISH_RUN_PATH" --json
    ```
 
 The handoff example requires `jq`. Without it, copy the returned JSON fields
@@ -226,12 +235,10 @@ When `publish` succeeds at some checkpoints but fails at others, the run enters
 RECONCILE_JSON=$("${CLI[@]}" reconcile --root "$PROJECT" \
   --run "$PUBLISH_RUN_PATH" \
   --plan "$PLAN_PATH" \
-  --approval "$APPROVAL_PATH" \
-  --confirm-production "$PLAN_DIGEST" --json)
+  --approval "$APPROVAL_PATH" --json)
 RECONCILE_RUN_PATH=$(printf '%s\n' "$RECONCILE_JSON" | jq -r '.runPath')
 "${CLI[@]}" verify --root "$PROJECT" \
-  --plan "$PLAN_PATH" --run "$RECONCILE_RUN_PATH" \
-  --acknowledge-gate-side-effects --json
+  --plan "$PLAN_PATH" --run "$RECONCILE_RUN_PATH" --json
 ```
 
 `reconcile` queries the actual remote state, skips already-consistent steps,
@@ -451,9 +458,9 @@ hooks:
     envAllowlist: []
 ```
 
-Hooks run only after human review and with
-`prepare --acknowledge-hook-side-effects`. Gates are the controlled extension
-point for release calibration (see `references/02-project-config.md`).
+Hooks run when `prepare` is invoked; the command call itself authorizes
+execution. Gates are the controlled extension point for release calibration
+(see `references/02-project-config.md`).
 
 ## Skills
 
@@ -461,7 +468,7 @@ point for release calibration (see `references/02-project-config.md`).
 - `release-setup`: read-only discovery, human calibration, and create-once configuration.
 - `release-assess`: read-only release readiness report.
 - `release-prepare`: local snapshot and reviewable release plan.
-- `release-publish`: approved, digest-confirmed frozen GitHub+npm publishing.
+- `release-publish`: approved frozen GitHub+npm publishing; the internal digest is checked automatically.
 - `release-reconcile`: evidence-based PARTIAL recovery with human intervention on conflicts.
 - `release-verify`: post-publish verification; only `VERIFIED` is the happy end.
 
@@ -475,14 +482,15 @@ closures. A release unit declares what reaches users via `distributions`:
 | `npm` | npm package with CLI entry | `npm install -g release-skill` |
 | `claude-plugin` | self-contained closure under `adapters/claude/` | automated marketplace checkpoint |
 | `codex-plugin` | self-contained closure under `adapters/codex/` | automated marketplace checkpoint |
-| `kimi-plugin` | self-contained closure (no scriptable install API) | manual, attestation-bound |
-| `codebuddy-plugin` | generated `adapters/workbuddy/` with `.codebuddy-plugin/plugin.json` | manual, attestation-bound |
+| `kimi-plugin` | self-contained closure (no scriptable install API) | non-blocking post-release manual task |
+| `codebuddy-plugin` | generated `adapters/workbuddy/` with `.codebuddy-plugin/plugin.json` | non-blocking post-release manual task |
 
 Each adapter closure bundles its own CLI, skills, and schemas for zero external
 dependency after installation. `publish` only publishes frozen Git objects and
 npm tarballs, then checks remote commit/tree/tag integrity. Claude/Codex
-verification is automated; Kimi Code and CodeBuddy/WorkBuddy require a trusted
-attestation bound to the frozen plan digest.
+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`.
 
 For every npm distribution, `prepare` statically checks the exact packed
 tarball against concrete `package.json` entry targets. `publish` and
@@ -503,9 +511,9 @@ 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 CodeBuddy/WorkBuddy marketplace install checkpoint — the
-  codebuddy CLI cannot pin a frozen ref, so installation is a manual step proven
-  by the same attestation closed loop as Kimi Code;
+- 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 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,27 +2,32 @@
 
 [English](README.md) · 安装指南：[中文](INSTALL.zh-CN.md) / [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.2.9 -->
+<!-- release-skill:release-version: 0.4.0 -->
 面向 Claude Code、CodeBuddy、WorkBuddy、Codex 和 Kimi Code 的发布准备工具，完整保留人工维护的文件内容。
 
 release-skill 帮助维护者回答三个问题：准备发布什么、还有哪些检查未通过、最终发布的内容是什么。它不重新生成、也不回写项目源文件。`prepare` 把每个配置的公开文件复制到隔离快照并验证字节——先冻结并供人工审阅，再从同一份冻结产物发布。`setup` 只显示确定性的 `compactSummary` 审阅视图，完整报告保留在临时会话目录中。
 
 <!-- release-skill:managed:start id=latest-release -->
-**0.2.9** (2026-07-31)
+**0.4.0** (2026-08-02)
 
-v0.2.9 会在评估和准备阶段提示缺少期望发布面配置，同时保持现有项目兼容，不立即阻断发布。
+v0.4.0 将生产发布收敛为一次冻结计划批准，并把无法自动安装的 Kimi 或 CodeBuddy 转为不阻塞发布的人工后续任务。
 
 **新增**
 
-- **采用提醒**：assess 会为每个尚未配置 `expectedPublicSurface` 的发布单元报告 `PUBLIC_SURFACE_CONFIG_MISSING`。
+- **人工消费者后续任务**：Kimi 或 CodeBuddy 无法自动安装时，发布完成后记录人工安装待办，系统不再要求安装证明。
 
 **变更**
 
-- **prepare 可见性**：prepare 会记录并返回同一条非阻断警告，CLI 的 JSON 与人类可读输出都会显示该提醒。
+- **单次发布批准**：普通生产发布只需批准一次不可变发布计划；调用命令即授权执行其配置的 hook 和 gate。
+- **人工消费者不阻塞发布**：Kimi 和 CodeBuddy 的人工安装待办不再阻止自动发布达到 `VERIFIED`。
+
+**移除**
+
+- **冗余确认参数**：普通发布路径移除了重复输入 plan digest、production confirmation、hook authorization 和人工证明等交互。
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **当前边界：** v0.2.9 是当前发布版本（v0.2.2 曾处于已发布状态，后因平台验证收敛修复而更新）。
+> **当前边界：** v0.4.0 是当前发布版本（v0.2.2 曾处于已发布状态，后因平台验证收敛修复而更新）。
 > v0.1.1 已完成 GitHub 与 npm 的
 > 真实生产发布，是首次生产验证的历史里程碑，并从冻结 Git ref 完成精确 npm
 > 安装及 Claude/Codex 消费者安装验证；"当前发布版本"与"首次生产验证里程碑"
@@ -35,7 +40,7 @@ v0.2.9 会在评估和准备阶段提示缺少期望发布面配置，同时保
 > 远端唯一性检查在 `publish` 全局预检执行。
 
 <!-- release-skill:capability:safe-first-command -->
-> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.2.9 是当前发布版本。**
+> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.4.0 是当前发布版本。**
 > npm 安装的 CLI 是受支持的用户入口；源码 checkout 保留为开发/贡献者路径。
 >
 > **第一条命令：**
@@ -45,9 +50,9 @@ v0.2.9 会在评估和准备阶段提示缺少期望发布面配置，同时保
 <!-- release-skill:maturity:v0.1-boundary -->
 <!-- release-skill:maturity:boundary -->
 > **安全默认路径：** 推荐 `help → assess → prepare --offline → 人工审阅`；
-> 生产发布在此基础上显式增加 `prepare --production → approve → publish
-> --confirm-production <planDigest>`；`bound` 前序公开基线必须使用
-> `prepare --online --production`。没有摘要确认就不会预检或写远端。
+> 生产发布使用 `ship --target-version <ver> → ship --approve --actor <name>`。
+> `ship` 自动执行 hooks 和门禁，唯一的人工门禁是计划批准。
+> Kimi/CodeBuddy 安装是非阻塞的人工后续任务（系统不核验）。
 
 ## 目录
 
@@ -99,6 +104,19 @@ CodeBuddy、Codex 和 Kimi Code 的完整命令见 [INSTALL.zh-CN.md](INSTALL.zh
 
 ### 主流程
 
+日常发布优先使用可恢复的快速路径。它会持久化所有权威文件路径，正常流程只需
+一次可读的冻结计划批准。`ship` 自动执行配置中的 hooks 和验证门禁，不进入
+hook 授权等待态。Kimi/CodeBuddy 安装是发布完成后的非阻塞人工后续任务，
+系统不核验其完成结果。
+
+```bash
+release-skill ship --root "$PROJECT" --target-version 1.2.3 --json
+release-skill ship --root "$PROJECT" --approve --actor "$ACTOR" --json
+```
+
+开发阶段可运行 `release-skill hooks validate`；它会执行声明的 hooks，并写入
+`prepare` 可复用的内容绑定收据。
+
 按以下顺序执行。步骤 1-4 是安全默认（只读或仅本地）；步骤 5-9 需要显式人工门禁。
 
 ```bash
@@ -160,39 +178,32 @@ ACTOR=your-name
    ```
 4. **prepare** — 本地快照与计划冻结：
    ```bash
-   "${CLI[@]}" prepare --root "$PROJECT" --offline \
-     --acknowledge-hook-side-effects \
-     --acknowledge-gate-side-effects --json
+   "${CLI[@]}" prepare --root "$PROJECT" --offline --json
    ```
-   只有项目配置没有对应 hook 或 snapshot gate 时，才省略相应授权参数。授权前必须审阅可执行文件、参数、工作目录和副作用，不能把授权参数当固定样板。
 5. **人工审阅：** 检查 `planPath`、`externalActions`、`targetVersion` 和 `planDigest`。
 6. **prepare --production** — 冻结生产计划：
    ```bash
-   PLAN_JSON=$("${CLI[@]}" prepare --root "$PROJECT" --online --production \
-     --acknowledge-hook-side-effects \
-     --acknowledge-gate-side-effects --json)
+   PLAN_JSON=$("${CLI[@]}" prepare --root "$PROJECT" --online --production --json)
    PLAN_PATH=$(printf '%s\n' "$PLAN_JSON" | jq -r '.planPath')
    PLAN_DIGEST=$(printf '%s\n' "$PLAN_JSON" | jq -r '.planDigest')
    ```
-7. **approve** — 人工批准（24 小时有效期）：
+7. **approve** — 人工批准（24 小时有效期，摘要从计划自动读取）：
    ```bash
    APPROVAL_JSON=$("${CLI[@]}" approve --plan "$PLAN_PATH" \
-     --digest "$PLAN_DIGEST" --actor "$ACTOR" --json)
+     --actor "$ACTOR" --json)
    APPROVAL_PATH=$(printf '%s\n' "$APPROVAL_JSON" | jq -r '.approvalPath')
    ```
 8. **publish** — 远端写入开始：
    ```bash
    PUBLISH_JSON=$("${CLI[@]}" publish --root "$PROJECT" \
-     --plan "$PLAN_PATH" --approval "$APPROVAL_PATH" \
-     --confirm-production "$PLAN_DIGEST" --json)
+     --plan "$PLAN_PATH" --approval "$APPROVAL_PATH" --json)
    PUBLISH_RUN_PATH=$(printf '%s\n' "$PUBLISH_JSON" | jq -r '.runPath')
    ```
    `PUBLISHED` **不是**终态。
 9. **verify** — 消费者安装检查：
    ```bash
    "${CLI[@]}" verify --root "$PROJECT" \
-     --plan "$PLAN_PATH" --run "$PUBLISH_RUN_PATH" \
-     --acknowledge-gate-side-effects --json
+     --plan "$PLAN_PATH" --run "$PUBLISH_RUN_PATH" --json
    ```
 
 示例需要 `jq`。没有 jq 时，直接复制返回的 JSON 字段；不要把尖括号占位符当作 shell 语法。
@@ -205,12 +216,10 @@ ACTOR=your-name
 RECONCILE_JSON=$("${CLI[@]}" reconcile --root "$PROJECT" \
   --run "$PUBLISH_RUN_PATH" \
   --plan "$PLAN_PATH" \
-  --approval "$APPROVAL_PATH" \
-  --confirm-production "$PLAN_DIGEST" --json)
+  --approval "$APPROVAL_PATH" --json)
 RECONCILE_RUN_PATH=$(printf '%s\n' "$RECONCILE_JSON" | jq -r '.runPath')
 "${CLI[@]}" verify --root "$PROJECT" \
-  --plan "$PLAN_PATH" --run "$RECONCILE_RUN_PATH" \
-  --acknowledge-gate-side-effects --json
+  --plan "$PLAN_PATH" --run "$RECONCILE_RUN_PATH" --json
 ```
 
 `reconcile` 查询实际远端状态，跳过已一致步骤，只重试安全未完成的动作。远端冲突需人工决策。reconcile 成功只返回 `PUBLISHED`，不返回 `VERIFIED`。
@@ -228,7 +237,7 @@ DISCOVERED -> ASSESSED -> PREPARED -> APPROVED -> PUBLISHING -> PUBLISHED -> VER
 
 **保存契约：** release-skill 不重新生成或回写项目源文件。`prepare` 把每个配置的公开文件复制到隔离快照并验证字节。后续 prepare 重新读取当前文件，不会从模板重建。只有 `publicFiles` 列出的文件会被复制。`prepare` 不会刷新或重写人工文档——维护者先更新 README、INSTALL 和 CHANGELOG，再 prepare、审阅和批准。
 
-**写入安全：** `setup` 默认只读（摘要确认后仅首次创建配置）。`prepare` 只写 `.release-skill/`。`publish` 是生产写入入口，需要同时提供批准和当前计划摘要。项目 hook 和 gate 是已确认的本地进程，没有操作系统沙箱。
+**写入安全：** `setup` 默认只读（摘要确认后仅首次创建配置）。`prepare` 只写 `.release-skill/`。`publish` 是生产写入入口，需要有效批准；内部计划摘要由系统自动绑定和校验。项目 hook 和 gate 在对应命令调用时获得授权，没有操作系统沙箱。
 
 **Workspace 源码权威：** 生产配置使用 `project.sourceRepository` 指定 workspace
 源仓库，并用 `project.defaultBranch` 指定其真实远端默认分支。prepare 冻结所有
@@ -409,7 +418,7 @@ hooks:
     envAllowlist: []
 ```
 
-hook 仅在人工审阅后、以 `--acknowledge-hook-side-effects` 显式授权后运行。gate 是发布校准的受控扩展点（见 `references/02-project-config.md`）。
+hook 在 `prepare` 调用时运行，命令调用本身即授权执行。gate 是发布校准的受控扩展点（见 `references/02-project-config.md`）。
 
 ## Skills
 
@@ -417,7 +426,7 @@ hook 仅在人工审阅后、以 `--acknowledge-hook-side-effects` 显式授权
 - `release-setup`：首次接入的只读发现、人工校准和 create-once 配置创建。
 - `release-assess`：只读发布就绪度报告。
 - `release-prepare`：本地快照和可审阅发布计划。
-- `release-publish`：经批准、摘要确认的冻结 GitHub+npm 发布。
+- `release-publish`：经批准的冻结 GitHub+npm 发布；内部摘要由系统自动校验。
 - `release-reconcile`：基于证据恢复 PARTIAL；冲突时人工介入。
 - `release-verify`：发布后验证；只有 `VERIFIED` 才是 happy end。
 
@@ -430,10 +439,10 @@ hook 仅在人工审阅后、以 `--acknowledge-hook-side-effects` 显式授权
 | `npm` | 带 CLI 入口的 npm 包 | `npm install -g release-skill` |
 | `claude-plugin` | `adapters/claude/` 下的自包含闭包 | 自动化 marketplace 检查点 |
 | `codex-plugin` | `adapters/codex/` 下的自包含闭包 | 自动化 marketplace 检查点 |
-| `kimi-plugin` | 自包含闭包（无可脚本化安装接口） | 手动，需可信证明 |
-| `codebuddy-plugin` | 生成的 `adapters/workbuddy/`，带 `.codebuddy-plugin/plugin.json` | 手动，需可信证明 |
+| `kimi-plugin` | 自包含闭包（无可脚本化安装接口） | 发布后非阻塞人工任务 |
+| `codebuddy-plugin` | 生成的 `adapters/workbuddy/`，带 `.codebuddy-plugin/plugin.json` | 发布后非阻塞人工任务 |
 
-每个适配器闭包都自带 CLI、skills 和 schemas 副本，安装后无需外部依赖即可运行。Claude/Codex 验证是自动化的；Kimi Code 和 CodeBuddy/WorkBuddy 需要绑定冻结计划摘要的可信证明。
+每个适配器闭包都自带 CLI、skills 和 schemas 副本，安装后无需外部依赖即可运行。Claude/Codex 验证是自动化的；Kimi Code 和 CodeBuddy/WorkBuddy 以 `manualFollowUps` 返回并标记 `verifiedBySystem: false`，其完成情况不阻塞自动发布进入 `VERIFIED`。
 
 每个 npm 分发在 `prepare` 时都会针对精确封装的 tarball 静态校验
 `package.json` 声明的具体入口。`publish` 与 `reconcile` 在任何远端动作前对同一
@@ -448,7 +457,7 @@ hook 仅在人工审阅后、以 `--acknowledge-hook-side-effects` 显式授权
 - 不声称已经替项目完成真实生产 canary，不声称已完成真实插件市场验证；
 - `prepare --online` 只观察 bound 前序基线；目标唯一性由 publish 全局预检完成；
 - 不覆盖已有 branch/tag/Release，不 unpublish npm；
-- 不提供自动化 CodeBuddy/WorkBuddy marketplace 安装检查点——codebuddy CLI 无法钉死冻结 ref，安装为手动步骤，经与 Kimi Code 相同的可信证明闭环确认；
+- 不提供 Kimi 或 CodeBuddy/WorkBuddy marketplace 自动安装检查点——这些安装是发布后明确的团队待办，系统不核验其完成结果；
 - 不承诺 Windows 或广泛的跨平台原生写入；
 - 不会隐藏地 commit、push、打 tag、创建 Release 或发布包。
 

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

@@ -9,7 +9,7 @@
     {
       "name": "release-skill",
       "source": "./",
-      "version": "0.2.9",
+      "version": "0.4.0",
       "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification"
     }
   ]

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

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