release-skill 0.1.10 → 0.2.1

package/.claude-plugin/marketplace.json

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

package/.claude-plugin/plugin.json

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

package/.codebuddy-plugin/plugin.json

@@ -0,0 +1,10 @@
+{
+  "name": "release-skill",
+  "version": "0.2.1",
+  "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
+  "author": {
+    "name": "广州市风荷科技有限公司"
+  },
+  "license": "MIT",
+  "skills": "./adapters/workbuddy/skills/"
+}

package/.codex-plugin/plugin.json

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

package/.kimi-plugin/plugin.json

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

package/CHANGELOG.md

@@ -1,5 +1,38 @@
 # Changelog
 
+<!-- release-skill:changelog:start version=0.2.1 locale=en baseline=sha256:7d616df824b1d28f9939ef181d6a5d5928d3e0f0455974bebb356c742992ac81 -->
+## [0.2.1] - 2026-07-25
+
+v0.2.1 adds a fourth platform adapter — workbuddy (CodeBuddy/WorkBuddy plugin) — using a build-only distribution model. The build-adapters generator and platform registry now register workbuddy alongside claude, codex, and kimi, producing a self-contained adapter directory at `adapters/workbuddy/` with a `.codebuddy-plugin/plugin.json` manifest, bundled CLI entry, native prebuilds, schemas, and skills. The sync-public-files and sync-version scripts cover the new manifest, and the adapter-contract standard documents build-only distribution. README and INSTALL (en + zh-CN) register the CodeBuddy installation entry. Installation is manual — the automated marketplace install checkpoint does not cover CodeBuddy yet.
+
+### Added
+
+- **WorkBuddy/CodeBuddy build-only distribution adapter**: new fourth platform adapter `workbuddy` registered in the platform registry and build-adapters generator. The generated self-contained adapter directory (`adapters/workbuddy/`) ships a `.codebuddy-plugin/plugin.json` manifest, a bundled CLI entry (`bin/release-skill.bundle.mjs`), native safe-write prebuilds, JSON schemas, and the full skill set. Skills resolve the CLI entry via `${CODEBUDDY_PLUGIN_ROOT}`, which CodeBuddy expands inline.
+- **Build-only distribution model in adapter-contract standard**: both the parent `standards/06-adapter-contract.md` and the public `references/06-adapter-contract.md` now document the build-only distribution scope — the adapter is generated and self-contained, installation is manual, and the automated preflight/execute/observe/verify marketplace checkpoint is not yet wired for CodeBuddy.
+- **sync-public-files and sync-version coverage for `.codebuddy-plugin`**: the `sync-public-files.mjs` script now validates the `.codebuddy-plugin/plugin.json` manifest as a public asset, and `sync-version.mjs` propagates the package version into it. The build-adapters generator produces workbuddy artifacts alongside the existing three platforms.
+- **README and INSTALL registration (en + zh-CN)**: all four public documents (README.md, README.zh-CN.md, INSTALL.md, INSTALL.zh-CN.md) now list the CodeBuddy/WorkBuddy adapter, its manual installation path, and the scope limitation that the automated marketplace install checkpoint does not yet cover CodeBuddy.
+<!-- release-skill:changelog:end version=0.2.1 locale=en -->
+
+
+<!-- release-skill:changelog:start version=0.2.0 locale=en baseline=sha256:cc9236e620cdb2d9eef6fede00c54095bf0cc0ccdfeb9c1e584f063ff3af7e23 -->
+## [0.2.0] - 2026-07-25
+
+v0.2.0 is a hardening release that improves publish reliability, digest reproducibility, version management, and platform registry data-driven architecture. Nine hardening tasks are completed: observe retry backoff, digest decoupling with planVersion 2, declared-manifest payload contract, single-source versioning, real CLI contract tests, incremental hook caching, tiered parallel checkpoint execution, observe-before-execute idempotent skip, and platform registry data-driven architecture. The npm package name (`release-skill`), publishing identity (`publisher: mzdbxqh`), public repository (`ifoohoo/release-skill`), and corporate maintainer remain unchanged.
+
+### Added
+
+- **Observe retry backoff (`observeWithRetry`)**: post-execute observe in publish/reconcile now uses bounded exponential backoff for transient failures. Transient classification is propagating — retries only on transient errors (network timeouts, 5xx); CONFLICTING errors are never retried. Marketplace retry window is clamped to action `timeoutMs`. This resolves intermittent PARTIAL failures caused by transient observe timeouts on real networks.
+- **Digest decoupling with planVersion 2**: plan fields split into binding layer (frozen artifacts, actions, versions, config) vs record layer (baseline, createdAt, status). Frozen commit timestamp derived from `headCommit` for reproducible digests. Approval no longer invalidated by tree/workspace digest drift (v2 plans); baseline check demoted to evidence warning. v1 legacy behavior preserved byte-for-byte (golden-value tested).
+- **Declared-manifest payload contract for marketplace installs**: replace whole-tree byte equality with declared-manifest comparison. Authority entries must exist and match byte-for-byte in the install dir; host-added files are recorded (`extraInstalledPaths`, capped) instead of failing. Legacy plans without `payloadContract` keep exact whole-tree semantics. `consumerTransportExclusions` deprecated (legacy path only).
+- **Single-source versioning with `sync-version` script**: `package.json` version is now the sole handwritten source. New `sync-version.mjs` propagates it to plugin manifests, marketplace.json, README boundary lines, and INSTALL docs (idempotent, `--check` mode, defensive whitelist). `smokeExpectedJson.version` is injected at runtime from `targetVersion`, ending the bump-invalidates-plan loop. docs hook now runs `check-docs-drift.mjs` (render check + sync-version check). Hardcoded version literals in tests replaced with dynamic reads.
+- **Real CLI contract tests for claude/codex/kimi adapters**: isolated-HOME contract tests asserting adapter assumptions against real CLI protocol shapes (`list --json` output forms, subcommand existence), gated by `RELEASE_SKILL_LIVE_CLI=1` with skip-not-fail semantics. Static contract locks in 'kimi has no scriptable install' to prevent fabricated CLI commands from regressing silently.
+- **Incremental hook caching for prepare**: hooks can declare `cacheable`+`cacheInputs`; results cached under `.release-skill/cache/hooks/<name>/<key>.json` keyed by hook config and input content hashes. Failures never cached; hits skip execution but not authorization gates; `--no-hook-cache` escape hatch. Cache dir registered in baseline control-plane exclusions and gitignore. test/typecheck hooks cached in this project: second prepare drops to ~2s with test hook served from cache.
+- **Tiered parallel checkpoint execution for publish**: publish checkpoints grouped into hard-coded `TIER_TABLE` layers. Layers run sequentially, actions within a layer run concurrently with `allSettled` semantics (no fail-fast, successes preserved). State persistence moves to per-layer snapshots keeping the appendRunState hash chain intact; crash recovery verified via SIGKILL-mid-tier integration test. Evidence appends serialized through a mutex chain with sequence starting at 1 and tier info in `details.tier`.
+- **Observe-before-execute idempotent skip**: publish each checkpoint execute now has a single read-only pre-observe. Four-way classification: CONSISTENT→SKIPPED / MISSING→execute / CONFLICTING→FAILED / not observable→execute. Two-layer preflight shares `classifyPreObservation` single source (global Safety Gate 10 arbitration). SKIPPED downstream adaptation: layer folding recognizes success, three `every` checks expanded to SUCCEEDED||SKIPPED, `buildPersistedState` maps skipped, TOCTOU as usual.
+- **Platform registry data-driven architecture**: new `src/platforms/registry.mjs` with `PLATFORMS`/`getPlatform`/`assertRegistry` module self-validation. Three platforms complete description (§3.4 matrix full dimensions) + pure strategy functions. Golden tests 12 cases solidify three platforms execute/observe/list current behavior. `src/producers/build-adapters.mjs` PLATFORMS now derived from registry; `scripts/build-adapters.mjs` duplicate platform table removed for single-source. `build:adapters:check` byte-zero diff (zero behavior change strong evidence).
+<!-- release-skill:changelog:end version=0.2.0 locale=en -->
+
+
 <!-- release-skill:changelog:start version=0.1.10 locale=en baseline=sha256:ec4dbf3f44f1295d9af20e0fbf1ced4341d9b65d0c93598104e228244e33fa2b -->
 ## [0.1.10] - 2026-07-24
 

package/INSTALL.md

@@ -2,7 +2,7 @@
 
 [简体中文](INSTALL.zh-CN.md)
 
-<!-- release-skill:release-version: 0.1.10 -->
+<!-- release-skill:release-version: 0.2.1 -->
 ## Prerequisites
 
 - Node.js 22.0.0 or later
@@ -68,7 +68,7 @@ as a version-pinned **manual** install plus trusted observation/attestation:
    default branch), confirm the trust prompt, then reload:
 
    ```
-   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.1.10
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.2.1
    /plugins reload
    ```
 
@@ -83,10 +83,10 @@ as a version-pinned **manual** install plus trusted observation/attestation:
 {
   "consumer": "kimi",
   "plugin": "release-skill",
-  "version": "0.1.10",
+  "version": "0.2.1",
   "entrySkill": "release-help",
   "repo": "ifoohoo/release-skill",
-  "ref": "release-skill-v0.1.10",
+  "ref": "release-skill-v0.2.1",
   "installPath": "<kimiCodeHome>/plugins/managed/release-skill",
   "planDigest": "<64-hex frozen plan digest>",
   "payloadDigest": "<64-hex frozen snapshot payload digest>",
@@ -106,6 +106,26 @@ attested `installPath` must resolve inside the requirement's isolated
 `KIMI_CODE_HOME` managed root, otherwise verification fails closed and the Kimi
 unit never reaches `VERIFIED`.
 
+## Install as a CodeBuddy/WorkBuddy plugin
+
+The package also ships a generated, self-contained CodeBuddy/WorkBuddy adapter
+at `adapters/workbuddy/`, next to `adapters/claude/`, `adapters/codex/`, and
+`adapters/kimi/`. Its manifest lives at `.codebuddy-plugin/plugin.json` (the
+components — `skills/`, `bin/`, `schemas/`, `native/` — sit at the plugin
+root, per the CodeBuddy plugin reference), and its skills resolve the CLI
+entry via `${CODEBUDDY_PLUGIN_ROOT}`, which CodeBuddy expands inline like
+Claude Code expands `${CLAUDE_PLUGIN_ROOT}`.
+
+CodeBuddy/WorkBuddy installation is a **manual** step today: the automated
+marketplace install checkpoint (`publish`/`verify`) does not cover CodeBuddy
+yet. To use the adapter, point CodeBuddy at the generated plugin directory —
+for a single session run CodeBuddy with `--plugin-dir <path>/adapters/workbuddy`,
+or add the directory as a marketplace source you control
+(`codebuddy plugin marketplace add <source>`) and install from it
+(`codebuddy plugin install release-skill@<marketplace>`, or the interactive
+`/plugin` manager). The installed copy lands in CodeBuddy's versioned plugin
+cache; the adapter never references files outside its own directory.
+
 ## Development Install (Local Checkout)
 
 For development or when working from source:

package/INSTALL.zh-CN.md

@@ -2,7 +2,7 @@
 
 [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.1.10 -->
+<!-- release-skill:release-version: 0.2.1 -->
 ## 前置条件
 
 - Node.js 22.0.0 或更高版本
@@ -62,7 +62,7 @@ release-skill 把 Kimi 安装建模为“版本钉死的手动安装 + 可信观
    它会安装最新 release 或默认分支），确认信任提示后重新加载：
 
    ```
-   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.1.10
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.2.1
    /plugins reload
    ```
 
@@ -76,10 +76,10 @@ release-skill 把 Kimi 安装建模为“版本钉死的手动安装 + 可信观
 {
   "consumer": "kimi",
   "plugin": "release-skill",
-  "version": "0.1.10",
+  "version": "0.2.1",
   "entrySkill": "release-help",
   "repo": "ifoohoo/release-skill",
-  "ref": "release-skill-v0.1.10",
+  "ref": "release-skill-v0.2.1",
   "installPath": "<kimiCodeHome>/plugins/managed/release-skill",
   "planDigest": "<64 位十六进制冻结计划摘要>",
   "payloadDigest": "<64 位十六进制冻结快照载荷摘要>",
@@ -98,6 +98,24 @@ release-skill 把 Kimi 安装建模为“版本钉死的手动安装 + 可信观
 必须解析到 requirement 给出的隔离 `KIMI_CODE_HOME` managed 根之内，否则验证
 失败关闭，Kimi 单元绝不进入 `VERIFIED`。
 
+## 安装为 CodeBuddy/WorkBuddy 插件
+
+本包还随 `adapters/claude/`、`adapters/codex/`、`adapters/kimi/` 一并提供生成的
+自包含 CodeBuddy/WorkBuddy 适配器 `adapters/workbuddy/`。其清单位于
+`.codebuddy-plugin/plugin.json`（组件——`skills/`、`bin/`、`schemas/`、
+`native/`——按 CodeBuddy 插件规范位于插件根目录），技能通过
+`${CODEBUDDY_PLUGIN_ROOT}` 解析 CLI 入口；CodeBuddy 会像 Claude Code 展开
+`${CLAUDE_PLUGIN_ROOT}` 一样内联展开该变量。
+
+CodeBuddy/WorkBuddy 安装目前是**手动**步骤：自动化 marketplace 安装检查点
+（`publish`/`verify`）尚未覆盖 CodeBuddy。使用该适配器时，把 CodeBuddy 指向
+生成的插件目录——单会话可用 `--plugin-dir <path>/adapters/workbuddy` 启动
+CodeBuddy；或把该目录作为你控制的 marketplace 源
+（`codebuddy plugin marketplace add <source>`）再从中安装
+（`codebuddy plugin install release-skill@<marketplace>`，或交互式 `/plugin`
+管理器）。安装后的副本落在 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.1.10 -->
+<!-- release-skill:release-version: 0.2.1 -->
 Release preparation for Claude Code, Codex, and Kimi Code, with human-edited files kept intact.
 
 release-skill helps a maintainer answer three questions: what will be released,
@@ -11,40 +11,20 @@ reviewed artifacts first and publishes those same artifacts later; it does not
 regenerate a README or re-pack the live workspace at the last step.
 
 <!-- release-skill:managed:start id=latest-release -->
-**0.1.10** (2026-07-24)
-
-v0.1.10 fixes the codex marketplace install verification failure caused by the codex CLI materializing a `.codex-plugin/migrated-command-skills/` subtree (commands migrated to skill format) in the plugin install root at install time. That consumer-owned transport metadata is now exempted alongside the root `.git` checkout, and the frozen snapshot exclusion list supports multi-segment relative path prefixes while single-segment root-only behavior is unchanged. The sealed snapshot digest, release plan schema, and prepare-side freezing are unchanged, so already-frozen plans reconcile without re-approval. The npm package name (`release-skill`), publishing identity (`publisher: mzdbxqh`), public repository (`ifoohoo/release-skill`), and corporate maintainer remain unchanged.
-
-**Fixed**
-
-- **Codex `migrated-command-skills` transport exemption**: the codex CLI
-  converts plugin `commands/` into skill format at install time and writes the
-  result under `.codex-plugin/migrated-command-skills/` in the install root.
-  That consumer-owned subtree is not part of the published payload, so the
-  whole-tree comparison failed every real codex marketplace install; the
-  codex consumer transport exemptions widen from `['.git']` to
-  `['.git', '.codex-plugin/migrated-command-skills']`. Claude (`.in_use`) and
-  Kimi (`.git`) exemptions are unchanged, and the exemption deliberately
-  never widens to `.codex-plugin/*` or arbitrary extra files. Verified
-  against a real flow-architect install: the installed tree is byte-identical
-  to the frozen snapshot except for the migrated-command-skills directory.
-  Already-frozen plans reconcile unchanged because the sealed digest, plan
-  schema, and prepare-side freezing are untouched.
-- **Multi-segment snapshot exclusions, fail-closed**:
-  `computeFrozenSnapshot`'s `excludeRootEntries` now accepts multi-segment
-  relative path prefixes naming an exact excluded subtree (required for the
-  `.codex-plugin/migrated-command-skills` exemption); single-segment entries
-  keep the historical root-only matching. Malformed entries (non-string,
-  absolute, `..`, backslash) fail closed: a bad exclusion list is a caller
-  bug, not transport metadata.
-- **Regression coverage**: new protocol-level tests cover the root-layout
-  codex execute→observe→verify cycle with the CLI-generated
-  migrated-command-skills tree present, including byte-tamper and extra-file
-  negatives that must still fail closed.
+**0.2.1** (2026-07-25)
+
+v0.2.1 adds a fourth platform adapter — workbuddy (CodeBuddy/WorkBuddy plugin) — using a build-only distribution model. The build-adapters generator and platform registry now register workbuddy alongside claude, codex, and kimi, producing a self-contained adapter directory at `adapters/workbuddy/` with a `.codebuddy-plugin/plugin.json` manifest, bundled CLI entry, native prebuilds, schemas, and skills. The sync-public-files and sync-version scripts cover the new manifest, and the adapter-contract standard documents build-only distribution. README and INSTALL (en + zh-CN) register the CodeBuddy installation entry. Installation is manual — the automated marketplace install checkpoint does not cover CodeBuddy yet.
+
+**Added**
+
+- **WorkBuddy/CodeBuddy build-only distribution adapter**: new fourth platform adapter `workbuddy` registered in the platform registry and build-adapters generator. The generated self-contained adapter directory (`adapters/workbuddy/`) ships a `.codebuddy-plugin/plugin.json` manifest, a bundled CLI entry (`bin/release-skill.bundle.mjs`), native safe-write prebuilds, JSON schemas, and the full skill set. Skills resolve the CLI entry via `${CODEBUDDY_PLUGIN_ROOT}`, which CodeBuddy expands inline.
+- **Build-only distribution model in adapter-contract standard**: both the parent `standards/06-adapter-contract.md` and the public `references/06-adapter-contract.md` now document the build-only distribution scope — the adapter is generated and self-contained, installation is manual, and the automated preflight/execute/observe/verify marketplace checkpoint is not yet wired for CodeBuddy.
+- **sync-public-files and sync-version coverage for `.codebuddy-plugin`**: the `sync-public-files.mjs` script now validates the `.codebuddy-plugin/plugin.json` manifest as a public asset, and `sync-version.mjs` propagates the package version into it. The build-adapters generator produces workbuddy artifacts alongside the existing three platforms.
+- **README and INSTALL registration (en + zh-CN)**: all four public documents (README.md, README.zh-CN.md, INSTALL.md, INSTALL.zh-CN.md) now list the CodeBuddy/WorkBuddy adapter, its manual installation path, and the scope limitation that the automated marketplace install checkpoint does not yet cover CodeBuddy.
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **Current boundary:** v0.1.10 is the current release (v0.1.9 previously held
+> **Current boundary:** v0.2.1 is the current release (v0.1.9 previously held
 > published status before the codex migrated-command-skills fix was added).
 > v0.1.1 completed a real production release to GitHub and npm — the first
 > production-verified milestone — followed by
@@ -914,6 +894,11 @@ Successful reconcile returns `PUBLISHED`, not `VERIFIED`; only the fresh
   Code (no scriptable install API) it emits a version-pinned manual install
   requirement and proves the entry Skill and payload digest only from a trusted
   attestation bound to the frozen plan digest;
+- ships a generated, self-contained CodeBuddy/WorkBuddy adapter
+  (`adapters/workbuddy/`, manifest `.codebuddy-plugin/plugin.json`, skills
+  rendered with `${CODEBUDDY_PLUGIN_ROOT}`) alongside the Claude/Codex/Kimi
+  adapters; CodeBuddy installation is manual — the automated marketplace
+  install checkpoint does not cover CodeBuddy yet;
 - distinguishes `PUBLISHED` (writes completed) from `VERIFIED` (remote and
   consumer installation evidence completed);
 - stops subsequent checkpoints on failure and writes a separate run record
@@ -999,6 +984,8 @@ npm publish may never be hooks/gates; they remain controlled plan actions.
 - 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
+  generated `adapters/workbuddy/` distribution adapter is installed manually;
 - 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,26 @@
 
 [English](README.md) · 安装指南：[中文](INSTALL.zh-CN.md) / [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.1.10 -->
+<!-- release-skill:release-version: 0.2.1 -->
 面向 Claude Code、Codex 和 Kimi Code 的发布准备工具，完整保留人工维护的文件内容。
 
 release-skill 帮助维护者回答三个问题：准备发布什么、还有哪些检查未通过、最终发布的内容是什么。它先冻结并供人工审阅，再从同一份冻结产物发布，不会在最后一步重新生成 README、重新打包当前工作区或覆盖人工内容。
 
 <!-- release-skill:managed:start id=latest-release -->
-**0.1.10** (2026-07-24)
-
-v0.1.10 修复 codex marketplace 安装校验失败：codex CLI 安装时会在插件安装根目录生成 `.codex-plugin/migrated-command-skills/` 子树（commands 迁移为 skill 格式的产物）。这部分消费者所有的传输元数据现在与根目录 `.git` 检出一样获得豁免；冻结快照排除清单扩展支持多段相对路径前缀，单段行为保持不变。密封快照摘要、发布计划 schema 与 prepare 冻结均未改动，已冻结计划无需重新审批即可 reconcile。npm 包名（`release-skill`）、发布身份（`publisher: mzdbxqh`）、公开仓库（`ifoohoo/release-skill`）与公司维护主体保持不变。
-
-**修复**
-
-- **Codex `migrated-command-skills` 传输豁免**：codex CLI 安装时会把插件
-  `commands/` 转换为 skill 格式并写入安装根目录的
-  `.codex-plugin/migrated-command-skills/`。该消费者所有的子树不属于已发布
-  载荷，导致整树比较在每次真实 codex marketplace 安装中失败；codex 消费者
-  传输豁免从 `['.git']` 扩为 `['.git', '.codex-plugin/migrated-command-skills']`。
-  Claude（`.in_use`）与 Kimi（`.git`）豁免不变，且豁免刻意不扩大为
-  `.codex-plugin/*` 或任意多余文件。flow-architect 真实安装实测验证：除
-  migrated-command-skills 目录外，安装内容与冻结快照逐字节一致。密封摘要、
-  计划 schema 与 prepare 冻结均未改动，已冻结计划可以不变地 reconcile 收口。
-- **多段快照排除，失败关闭**：`computeFrozenSnapshot` 的
-  `excludeRootEntries` 现在接受多段相对路径前缀，命名一个精确排除的子树
-  （`.codex-plugin/migrated-command-skills` 豁免所必需）；单段条目保持历史
-  的根直接子项匹配。畸形条目（非字符串、绝对路径、`..`、反斜杠）失败关闭：
-  错误的排除清单是调用方 bug，不是传输元数据。
-- **回归覆盖**：新增协议级测试覆盖带 CLI 生成 migrated-command-skills 树的
-  根布局 codex execute→observe→verify 完整链路，包含必须仍然失败关闭的字节
-  篡改与多余文件负例。
+**0.2.1** (2026-07-25)
+
+v0.2.1 新增第四个平台适配器 workbuddy（CodeBuddy/WorkBuddy 插件），采用 build-only 分发模式。build-adapters 生成器与平台注册表现在将 workbuddy 与 claude、codex、kimi 并列登记，在 `adapters/workbuddy/` 产出包含 `.codebuddy-plugin/plugin.json` 清单、打包 CLI 入口、native 预编译、JSON schemas 与全套技能的自包含适配器目录。sync-public-files 与 sync-version 脚本覆盖新清单，适配器契约标准补充 build-only 分发说明。README 与 INSTALL（中英四份）登记 CodeBuddy 安装入口。安装为手动步骤——自动化 marketplace 安装检查点尚未覆盖 CodeBuddy。
+
+**新增**
+
+- **WorkBuddy/CodeBuddy build-only 分发适配器**：新增第四个平台适配器 `workbuddy`，在平台注册表和 build-adapters 生成器中登记。生成的自包含适配器目录（`adapters/workbuddy/`）附带 `.codebuddy-plugin/plugin.json` 清单、打包 CLI 入口（`bin/release-skill.bundle.mjs`）、native safe-write 预编译、JSON schemas 与全套技能。技能通过 `${CODEBUDDY_PLUGIN_ROOT}` 解析 CLI 入口，CodeBuddy 会内联展开该变量。
+- **适配器契约标准补充 build-only 分发模型**：父级 `standards/06-adapter-contract.md` 与公开 `references/06-adapter-contract.md` 均补充 build-only 分发范围说明——适配器由生成器产出且自包含，安装为手动步骤，CodeBuddy 的自动化 preflight/execute/observe/verify marketplace 检查点尚未接入。
+- **sync-public-files 与 sync-version 覆盖 `.codebuddy-plugin`**：`sync-public-files.mjs` 脚本现在将 `.codebuddy-plugin/plugin.json` 清单作为公开资产校验，`sync-version.mjs` 将包版本同步到该清单。build-adapters 生成器将 workbuddy 产物与既有三平台并列生成。
+- **README 与 INSTALL 登记（中英四份）**：四份公开文档（README.md、README.zh-CN.md、INSTALL.md、INSTALL.zh-CN.md）均列出 CodeBuddy/WorkBuddy 适配器、其手动安装路径以及自动化 marketplace 安装检查点尚未覆盖 CodeBuddy 的范围限制。
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **当前边界：** v0.1.10 是当前发布版本（v0.1.9 曾处于已发布、待独立验证状态）。
+> **当前边界：** v0.2.1 是当前发布版本（v0.1.9 曾处于已发布、待独立验证状态）。
 > v0.1.1 已完成 GitHub 与 npm 的
 > 真实生产发布，是首次生产验证的历史里程碑，并从冻结 Git ref 完成精确 npm
 > 安装及 Claude/Codex 消费者安装验证；“当前发布版本”与“首次生产验证里程碑”
@@ -608,6 +595,7 @@ reconcile 成功只返回 `PUBLISHED`，不会返回 `VERIFIED`；只有全新
 - 用计划摘要、有效期和显式 action allowlist 绑定人工批准；
 - 从冻结 Git object 和 npm tarball 发布，并核对远端 commit/tree/tag/integrity；
 - 从冻结 Git ref 安装配置的 Claude/Codex 插件，证明入口 Skill 和安装载荷摘要；对 Kimi Code（无可脚本化安装接口）产出版本钉死的手动安装要求，仅依据绑定到冻结计划摘要的可信证明来确认入口 Skill 和载荷摘要；
+- 随 Claude/Codex/Kimi 适配器一并提供生成的自包含 CodeBuddy/WorkBuddy 适配器（`adapters/workbuddy/`，清单 `.codebuddy-plugin/plugin.json`，技能以 `${CODEBUDDY_PLUGIN_ROOT}` 渲染）；CodeBuddy 安装为手动步骤——自动化 marketplace 安装检查点尚未覆盖 CodeBuddy；
 - 明确区分 `PUBLISHED`（外写完成）与 `VERIFIED`（远端和消费者安装证据完成）；
 - 中途失败停止后续动作，记录独立 run；不修改冻结 plan，不自动撤销已成功动作。
 
@@ -659,6 +647,7 @@ push、tag、默认分支修改、GitHub Release 和 npm publish 不能放进 ho
 - 不声称已经替项目完成真实生产 canary；
 - `prepare --online` 只观察 bound 前序基线；目标唯一性由 publish 全局预检完成；
 - 不覆盖已有 branch/tag/Release，不 unpublish npm；
+- 不提供自动化 CodeBuddy/WorkBuddy marketplace 安装检查点——生成的 `adapters/workbuddy/` 分发适配器需手动安装；
 - 不承诺 Windows 或广泛的跨平台原生写入；
 - 不会隐藏地 commit、push、打 tag、创建 Release 或发布包。
 

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

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