release-skill 0.4.0 → 0.4.2

package/.claude-plugin/marketplace.json

@@ -9,8 +9,12 @@
     {
       "name": "release-skill",
       "source": "./",
-      "version": "0.4.0",
-      "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification"
+      "version": "0.4.2",
+      "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
+      "author": {
+        "name": "广州市风荷科技有限公司"
+      },
+      "license": "Apache-2.0"
     }
   ]
 }

package/.claude-plugin/plugin.json

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

package/.codebuddy-plugin/plugin.json

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

package/.codex-plugin/plugin.json

@@ -1,17 +1,17 @@
 {
   "name": "release-skill",
-  "version": "0.4.0",
+  "version": "0.4.2",
   "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
   "author": {
     "name": "广州市风荷科技有限公司"
   },
-  "license": "MIT",
+  "license": "Apache-2.0",
   "skills": "./adapters/codex/skills/",
   "interface": {
     "displayName": "Release Skill",
     "shortDescription": "Safe preparation and frozen GitHub/npm publishing",
     "longDescription": "Prepares byte-faithful public snapshots without rewriting project source files and publishes approved frozen GitHub/npm artifacts. Full happy end verification confirms consumer installation from frozen Git ref.",
-    "developerName": "ifoohoo",
+    "developerName": "广州市风荷科技有限公司",
     "category": "DevOps",
     "capabilities": [
       "Write",
@@ -19,7 +19,7 @@
     ],
     "defaultPrompt": [
       "Assess this project for release readiness.",
-      "Prepare a release plan for version 0.4.0.",
+      "Prepare a release plan for version 0.4.2.",
       "Help me understand the release workflow."
     ]
   }

package/.kimi-plugin/plugin.json

@@ -1,11 +1,11 @@
 {
   "name": "release-skill",
-  "version": "0.4.0",
+  "version": "0.4.2",
   "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
   "author": {
     "name": "广州市风荷科技有限公司"
   },
-  "license": "MIT",
+  "license": "Apache-2.0",
   "homepage": "https://github.com/ifoohoo/release-skill#readme",
   "keywords": [
     "release",
@@ -21,7 +21,7 @@
     "displayName": "Release Skill",
     "shortDescription": "Safe preparation and frozen GitHub/npm publishing",
     "longDescription": "Prepares byte-faithful public snapshots without rewriting project source files and publishes approved frozen GitHub/npm artifacts. Full happy end verification confirms consumer installation from frozen Git ref.",
-    "developerName": "ifoohoo",
+    "developerName": "广州市风荷科技有限公司",
     "websiteURL": "https://github.com/ifoohoo/release-skill"
   }
 }

package/CHANGELOG.md

@@ -1,5 +1,33 @@
 # Changelog
 
+<!-- release-skill:changelog:start version=0.4.2 locale=en baseline=sha256:b8676f90eb68c93e40f84ff16de18a8c472e6a06e321bcc25895799e9e6f3896 -->
+## [0.4.2] - 2026-08-12
+
+v0.4.2 makes the CodeBuddy consumer marketplace configurable per distribution instead of hardcoding a single marketplace, so CodeBuddy plugin distributions can target a project-declared marketplace source.
+
+### Changed
+
+- **Plan schema**: production plans carry the resolved codebuddy marketplace coordinates so approval and publish review the exact marketplace target.
+
+### Fixed
+
+- **Configurable CodeBuddy marketplace**: codebuddy-plugin distributions now accept `marketplace` and `marketplaceSource` in project configuration, and prepare threads both values into the consumer install action instead of assuming a fixed marketplace.
+<!-- release-skill:changelog:end version=0.4.2 locale=en -->
+
+
+<!-- release-skill:changelog:start version=0.4.1 locale=en baseline=sha256:e2ccb5ddfef6c5e00b047bbf4fa009f5f5c10b003aa2254756f6f9b73a9b3346 -->
+## [0.4.1] - 2026-08-03
+
+v0.4.1 is the unreleased source candidate that migrates release-skill to Apache License 2.0 and aligns public author metadata while preserving repository ownership and historical attribution.
+
+### Changed
+
+- **Open-source license**: package, plugin manifests, README, LICENSE, and NOTICE now consistently use Apache-2.0.
+- **Identity separation**: project author and developer metadata names 广州市风荷科技有限公司, while the `ifoohoo` repository and Marketplace owner coordinates remain unchanged.
+- **Historical attribution**: existing contributor and company copyright notices remain; metadata and license changes do not assert a copyright transfer.
+<!-- release-skill:changelog:end version=0.4.1 locale=en -->
+
+
 <!-- release-skill:changelog:start version=0.4.0 locale=en baseline=sha256:099d9db24049aeaae78a21d3bd5152582bb20d4efad1ceff085f9609e8e6d52e -->
 ## [0.4.0] - 2026-08-02
 

package/INSTALL.md

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

package/INSTALL.zh-CN.md

@@ -2,7 +2,7 @@
 
 [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.4.0 -->
+<!-- release-skill:release-version: 0.4.2 -->
 ## 前置条件
 
 - 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.4.0
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.4.2
    /plugins reload
    ```
 

package/LICENSE

@@ -1,22 +1,187 @@
-MIT License
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction, and
+distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by the
+copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all other
+entities that control, are controlled by, or are under common control with
+that entity. For the purposes of this definition, "control" means (i) the
+power, direct or indirect, to cause the direction or management of such
+entity, whether by contract or otherwise, or (ii) ownership of fifty percent
+(50%) or more of the outstanding shares, or (iii) beneficial ownership of
+such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity exercising
+permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications,
+including but not limited to software source code, documentation source, and
+configuration files.
+
+"Object" form shall mean any form resulting from mechanical transformation
+or translation of a Source form, including but not limited to compiled object
+code, generated documentation, and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or Object form,
+made available under the License, as indicated by a copyright notice that is
+included in or attached to the work (an example is provided in the Appendix
+below).
+
+"Derivative Works" shall mean any work, whether in Source or Object form,
+that is based on (or derived from) the Work and for which the editorial
+revisions, annotations, elaborations, or other modifications represent, as a
+whole, an original work of authorship. For the purposes of this License,
+Derivative Works shall not include works that remain separable from, or merely
+link (or bind by name) to the interfaces of, the Work and Derivative Works
+thereof.
+
+"Contribution" shall mean any work of authorship, including the original
+version of the Work and any modifications or additions to that Work or
+Derivative Works thereof, that is intentionally submitted to Licensor for
+inclusion in the Work by the copyright owner or by an individual or Legal
+Entity authorized to submit on behalf of the copyright owner. For the purposes
+of this definition, "submitted" means any form of electronic, verbal, or
+written communication sent to the Licensor or its representatives, including
+but not limited to communication on electronic mailing lists, source code
+control systems, and issue tracking systems that are managed by, or on behalf
+of, the Licensor for the purpose of discussing and improving the Work, but
+excluding communication that is conspicuously marked or otherwise designated
+in writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity on
+behalf of whom a Contribution has been received by Licensor and subsequently
+incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of this
+License, each Contributor hereby grants to You a perpetual, worldwide,
+non-exclusive, no-charge, royalty-free, irrevocable copyright license to
+reproduce, prepare Derivative Works of, publicly display, publicly perform,
+sublicense, and distribute the Work and such Derivative Works in Source or
+Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of this
+License, each Contributor hereby grants to You a perpetual, worldwide,
+non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this
+section) patent license to make, have made, use, offer to sell, sell, import,
+and otherwise transfer the Work, where such license applies only to those
+patent claims licensable by such Contributor that are necessarily infringed by
+their Contribution(s) alone or by combination of their Contribution(s) with
+the Work to which such Contribution(s) was submitted. If You institute patent
+litigation against any entity (including a cross-claim or counterclaim in a
+lawsuit) alleging that the Work or a Contribution incorporated within the Work
+constitutes direct or contributory patent infringement, then any patent
+licenses granted to You under this License for that Work shall terminate as of
+the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the Work or
+Derivative Works thereof in any medium, with or without modifications, and in
+Source or Object form, provided that You meet the following conditions:
+
+(a) You must give any other recipients of the Work or Derivative Works a copy
+of this License; and
+
+(b) You must cause any modified files to carry prominent notices stating that
+You changed the files; and
+
+(c) You must retain, in the Source form of any Derivative Works that You
+distribute, all copyright, patent, trademark, and attribution notices from the
+Source form of the Work, excluding those notices that do not pertain to any
+part of the Derivative Works; and
+
+(d) If the Work includes a "NOTICE" text file as part of its distribution,
+then any Derivative Works that You distribute must include a readable copy of
+the attribution notices contained within such NOTICE file, excluding those
+notices that do not pertain to any part of the Derivative Works, in at least
+one of the following places: within a NOTICE text file distributed as part of
+the Derivative Works; within the Source form or documentation, if provided
+along with the Derivative Works; or, within a display generated by the
+Derivative Works, if and wherever such third-party notices normally appear.
+The contents of the NOTICE file are for informational purposes only and do not
+modify the License. You may add Your own attribution notices within Derivative
+Works that You distribute, alongside or as an addendum to the NOTICE text from
+the Work, provided that such additional attribution notices cannot be
+construed as modifying the License.
+
+You may add Your own copyright statement to Your modifications and may provide
+additional or different license terms and conditions for use, reproduction, or
+distribution of Your modifications, or for any such Derivative Works as a
+whole, provided Your use, reproduction, and distribution of the Work otherwise
+complies with the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise, any
+Contribution intentionally submitted for inclusion in the Work by You to the
+Licensor shall be under the terms and conditions of this License, without any
+additional terms or conditions. Notwithstanding the above, nothing herein
+shall supersede or modify the terms of any separate license agreement you may
+have executed with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade names,
+trademarks, service marks, or product names of the Licensor, except as required
+for reasonable and customary use in describing the origin of the Work and
+reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or agreed to in
+writing, Licensor provides the Work (and each Contributor provides its
+Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied, including, without limitation, any warranties
+or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+PARTICULAR PURPOSE. You are solely responsible for determining the
+appropriateness of using or redistributing the Work and assume any risks
+associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory, whether in
+tort (including negligence), contract, or otherwise, unless required by
+applicable law (such as deliberate and grossly negligent acts) or agreed to in
+writing, shall any Contributor be liable to You for damages, including any
+direct, indirect, special, incidental, or consequential damages of any
+character arising as a result of this License or out of the use or inability to
+use the Work (including but not limited to damages for loss of goodwill, work
+stoppage, computer failure or malfunction, or any and all other commercial
+damages or losses), even if such Contributor has been advised of the
+possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing the Work
+or Derivative Works thereof, You may choose to offer, and charge a fee for,
+acceptance of support, warranty, indemnity, or other liability obligations
+and/or rights consistent with this License. However, in accepting such
+obligations, You may act only on Your own behalf and on Your sole
+responsibility, not on behalf of any other Contributor, and only if You agree
+to indemnify, defend, and hold each Contributor harmless for any liability
+incurred by, or claims asserted against, such Contributor by reason of your
+accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+To apply the Apache License to your work, attach the following boilerplate
+notice, with the fields enclosed by brackets "[]" replaced with your own
+identifying information. (Don't include the brackets!) The text should be
+enclosed in the appropriate comment syntax for the file format. We also
+recommend that a file or class name and description of purpose be included on
+the same "printed page" as the copyright notice for easier identification
+within third-party archives.
 
 Copyright (c) 2026 release-skill contributors
 Copyright (c) 2026 广州市风荷科技有限公司
 
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

package/NOTICE

@@ -1,13 +1,15 @@
 # Notice
 
-release-skill is an open-source project released under the MIT License.
+release-skill is an open-source project released under the Apache License,
+Version 2.0.
 
 ## Maintenance
 
 release-skill is maintained by 广州市风荷科技有限公司 (Guangzhou Fenghe
 Technology Co., Ltd.), together with the release-skill contributors. Copyright
 in the project is held by the release-skill contributors and 广州市风荷科技
-有限公司 as stated in the LICENSE file. The transfer of the public GitHub
+有限公司 as stated in the LICENSE file. The 0.4.1 license change does not by
+itself assign or transfer those historical rights. The transfer of the public GitHub
 repository to the `ifoohoo` organization is an administrative change of the
 hosting location and maintenance identity; it does not by itself constitute a
 copyright assignment or transfer.

package/README.md

@@ -2,7 +2,7 @@
 
 [简体中文](README.zh-CN.md) · Installation: [English](INSTALL.md) / [简体中文](INSTALL.zh-CN.md)
 
-<!-- release-skill:release-version: 0.4.0 -->
+<!-- release-skill:release-version: 0.4.2 -->
 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,26 +14,22 @@ 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.4.0** (2026-08-02)
+**0.4.2** (2026-08-12)
 
-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**
-
-- **Manual consumer follow-ups**: when Kimi or CodeBuddy cannot be installed automatically, the release records an installation task after publishing without requiring system attestation.
+v0.4.2 makes the CodeBuddy consumer marketplace configurable per distribution instead of hardcoding a single marketplace, so CodeBuddy plugin distributions can target a project-declared marketplace source.
 
 **Changed**
 
-- **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`.
+- **Plan schema**: production plans carry the resolved codebuddy marketplace coordinates so approval and publish review the exact marketplace target.
 
-**Removed**
+**Fixed**
 
-- **Redundant confirmation flags**: legacy plan-digest repetition, production-confirmation, hook-authorization, and manual-attestation interactions were removed from the normal release path.
+- **Configurable CodeBuddy marketplace**: codebuddy-plugin distributions now accept `marketplace` and `marketplaceSource` in project configuration, and prepare threads both values into the consumer install action instead of assuming a fixed marketplace.
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **Current boundary:** v0.4.0 is the current release (v0.2.2 previously held
+> **Current boundary:** v0.4.2 is the current source candidate; v0.4.1 remains
+> the latest published 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
@@ -51,8 +47,8 @@ v0.4.0 simplifies the production release path to one frozen-plan approval and mo
 > publish global preflight.
 
 <!-- release-skill:capability:safe-first-command -->
-> **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
+> **Production path verified since the v0.1.1 milestone; v0.4.2 is the current
+> source candidate and v0.4.1 is the latest published release.** The npm-installed CLI is the supported user entry. Source checkout
 > is the development/contributor fallback.
 >
 > **Start here:**
@@ -62,7 +58,13 @@ v0.4.0 simplifies the production release path to one frozen-plan approval and mo
 <!-- release-skill:maturity:v0.1-boundary -->
 <!-- release-skill:maturity:boundary -->
 > **Safe defaults:** the recommended path is `help → assess → prepare --offline →
-> human review`. Production publishing uses `ship --target-version <ver> → ship --approve --actor <name>`.
+> human review`. `help` and `assess` are read-only. The release-skill-owned part of
+> `prepare --offline` writes only under `.release-skill/` and does not call remote
+> publish adapters, but configured hooks and gates are unsandboxed processes: they
+> may write outside the project, access credentials, make network calls, or publish.
+> Treat `prepare` as local-only only when those processes are absent or separately
+> audited and explicitly acknowledged. 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).
 
@@ -130,8 +132,11 @@ 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.
+Run these steps in order. Steps 1-3 are read-only. In step 4, release-skill's own
+prepare pipeline is local-only and never invokes remote publish adapters; configured
+hooks and gates remain arbitrary unsandboxed processes and can perform local or remote
+side effects. Step 4 is therefore local-only only when those processes are absent or
+separately audited and explicitly acknowledged. Steps 5-9 require explicit human gates.
 
 ```bash
 CLI=(release-skill)           # or: CLI=(node "$RELEASE_SKILL_HOME/packages/release-skill/bin/release-skill.mjs")
@@ -210,6 +215,9 @@ ACTOR=your-name
      --actor "$ACTOR" --json)
    APPROVAL_PATH=$(printf '%s\n' "$APPROVAL_JSON" | jq -r '.approvalPath')
    ```
+   `--actor` is an unauthenticated local audit string. It is not identity
+   verification, a signature, or proof that a particular human approved the plan;
+   use an external authenticated approval system when that assurance is required.
 8. **publish** — remote writes start here:
    ```bash
    PUBLISH_JSON=$("${CLI[@]}" publish --root "$PROJECT" \
@@ -276,9 +284,12 @@ but blocks a lost or reverted README by path. It never merges, switches
 branches, pushes, or creates a PR.
 
 **Write safety:** `setup` is read-only by default (create-once after digest
-confirmation). `prepare` writes only under `.release-skill/`. `publish` is the
-production write entry, requiring both approval and the current plan digest.
-Project hooks and gates are acknowledged local processes without an OS sandbox.
+confirmation). Release-skill's own `prepare` pipeline writes only under
+`.release-skill/` and does not invoke remote publish adapters. Project hooks and
+gates are acknowledged processes without an OS sandbox; they may write outside the
+project, access credentials, make network calls, or publish. `publish` is the
+release-skill-owned production write entry and requires both approval and the current
+plan digest.
 
 ## Documentation
 
@@ -492,6 +503,11 @@ 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`.
 
+A `codebuddy-plugin` distribution may optionally declare `marketplace` (and
+`marketplaceSource`, the URL consumers use to add the marketplace) to override
+the default unified marketplace `artifact-skill-set`; undeclared distributions
+keep the default and produce byte-identical frozen plans.
+
 For every npm distribution, `prepare` statically checks the exact packed
 tarball against concrete `package.json` entry targets. `publish` and
 `reconcile` repeat the same check on the frozen tarball before any remote
@@ -519,4 +535,4 @@ declaration is narrowed to concrete targets.
 
 ## License
 
-MIT. See [LICENSE](LICENSE).
+Apache License 2.0. See [LICENSE](LICENSE) and [NOTICE](NOTICE).

package/README.zh-CN.md

@@ -2,32 +2,27 @@
 
 [English](README.md) · 安装指南：[中文](INSTALL.zh-CN.md) / [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.4.0 -->
+<!-- release-skill:release-version: 0.4.2 -->
 面向 Claude Code、CodeBuddy、WorkBuddy、Codex 和 Kimi Code 的发布准备工具，完整保留人工维护的文件内容。
 
 release-skill 帮助维护者回答三个问题：准备发布什么、还有哪些检查未通过、最终发布的内容是什么。它不重新生成、也不回写项目源文件。`prepare` 把每个配置的公开文件复制到隔离快照并验证字节——先冻结并供人工审阅，再从同一份冻结产物发布。`setup` 只显示确定性的 `compactSummary` 审阅视图，完整报告保留在临时会话目录中。
 
 <!-- release-skill:managed:start id=latest-release -->
-**0.4.0** (2026-08-02)
+**0.4.2** (2026-08-12)
 
-v0.4.0 将生产发布收敛为一次冻结计划批准，并把无法自动安装的 Kimi 或 CodeBuddy 转为不阻塞发布的人工后续任务。
-
-**新增**
-
-- **人工消费者后续任务**：Kimi 或 CodeBuddy 无法自动安装时，发布完成后记录人工安装待办，系统不再要求安装证明。
+v0.4.2 将 CodeBuddy 消费者市场改为按分发渠道可配置，不再硬编码单一市场，CodeBuddy 插件分发可以指向项目声明的市场来源。
 
 **变更**
 
-- **单次发布批准**：普通生产发布只需批准一次不可变发布计划；调用命令即授权执行其配置的 hook 和 gate。
-- **人工消费者不阻塞发布**：Kimi 和 CodeBuddy 的人工安装待办不再阻止自动发布达到 `VERIFIED`。
+- **计划模式**：生产计划携带解析后的 CodeBuddy 市场坐标，审批与发布时可核对确切的市场目标。
 
-**移除**
+**修复**
 
-- **冗余确认参数**：普通发布路径移除了重复输入 plan digest、production confirmation、hook authorization 和人工证明等交互。
+- **CodeBuddy 市场可配置**：codebuddy-plugin 分发在项目配置中接受 `marketplace` 与 `marketplaceSource`，prepare 将两个值透传进消费者安装动作，不再假定固定市场。
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **当前边界：** v0.4.0 是当前发布版本（v0.2.2 曾处于已发布状态，后因平台验证收敛修复而更新）。
+> **当前边界：** v0.4.2 是当前源码候选，v0.4.1 仍是最新已发布版本（v0.2.2 曾处于已发布状态，后因平台验证收敛修复而更新）。
 > v0.1.1 已完成 GitHub 与 npm 的
 > 真实生产发布，是首次生产验证的历史里程碑，并从冻结 Git ref 完成精确 npm
 > 安装及 Claude/Codex 消费者安装验证；"当前发布版本"与"首次生产验证里程碑"
@@ -40,7 +35,7 @@ v0.4.0 将生产发布收敛为一次冻结计划批准，并把无法自动安
 > 远端唯一性检查在 `publish` 全局预检执行。
 
 <!-- release-skill:capability:safe-first-command -->
-> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.4.0 是当前发布版本。**
+> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.4.2 是当前源码候选，v0.4.1 是最新已发布版本。**
 > npm 安装的 CLI 是受支持的用户入口；源码 checkout 保留为开发/贡献者路径。
 >
 > **第一条命令：**
@@ -49,8 +44,12 @@ v0.4.0 将生产发布收敛为一次冻结计划批准，并把无法自动安
 
 <!-- release-skill:maturity:v0.1-boundary -->
 <!-- release-skill:maturity:boundary -->
-> **安全默认路径：** 推荐 `help → assess → prepare --offline → 人工审阅`；
-> 生产发布使用 `ship --target-version <ver> → ship --approve --actor <name>`。
+> **安全默认路径：** 推荐 `help → assess → prepare --offline → 人工审阅`。
+> `help` 与 `assess` 只读；`prepare --offline` 中由 release-skill 自身控制的部分只写
+> `.release-skill/`，且不调用远端发布适配器。但配置的 hook 和 gate 是无操作系统沙箱的进程，
+> 可以写出项目目录、访问凭据、发起网络请求或执行远端发布。只有未配置这些进程，或已单独审计并
+> 显式确认其副作用时，才可以把 `prepare` 视为“仅本地”。生产发布使用
+> `ship --target-version <ver> → ship --approve --actor <name>`。
 > `ship` 自动执行 hooks 和门禁，唯一的人工门禁是计划批准。
 > Kimi/CodeBuddy 安装是非阻塞的人工后续任务（系统不核验）。
 
@@ -117,7 +116,10 @@ release-skill ship --root "$PROJECT" --approve --actor "$ACTOR" --json
 开发阶段可运行 `release-skill hooks validate`；它会执行声明的 hooks，并写入
 `prepare` 可复用的内容绑定收据。
 
-按以下顺序执行。步骤 1-4 是安全默认（只读或仅本地）；步骤 5-9 需要显式人工门禁。
+按以下顺序执行。步骤 1-3 只读。步骤 4 中，release-skill 自身的 prepare 流水线仅在本地写入，
+且不会调用远端发布适配器；配置的 hook 和 gate 仍是可产生本地或远端副作用的任意无沙箱进程。
+只有这些进程不存在，或已单独审计并显式确认副作用时，步骤 4 才能视为“仅本地”。步骤 5-9
+需要显式人工门禁。
 
 ```bash
 CLI=(release-skill)           # 或：CLI=(node "$RELEASE_SKILL_HOME/packages/release-skill/bin/release-skill.mjs")
@@ -193,6 +195,8 @@ ACTOR=your-name
      --actor "$ACTOR" --json)
    APPROVAL_PATH=$(printf '%s\n' "$APPROVAL_JSON" | jq -r '.approvalPath')
    ```
+   `--actor` 只是未经身份认证的本地审计字符串，不是身份核验、数字签名，也不能证明某位特定人员
+   已批准计划；需要此类保证时，应接入外部已认证的审批系统。
 8. **publish** — 远端写入开始：
    ```bash
    PUBLISH_JSON=$("${CLI[@]}" publish --root "$PROJECT" \
@@ -237,7 +241,10 @@ 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` 默认只读（摘要确认后仅首次创建配置）。release-skill 自身的 `prepare`
+流水线只写 `.release-skill/`，且不调用远端发布适配器。项目 hook 和 gate 在对应命令调用时获得
+授权，但没有操作系统沙箱；它们可以写出项目目录、访问凭据、发起网络请求或执行远端发布。
+`publish` 是 release-skill 自身的生产写入入口，需要有效批准；内部计划摘要由系统自动绑定和校验。
 
 **Workspace 源码权威：** 生产配置使用 `project.sourceRepository` 指定 workspace
 源仓库，并用 `project.defaultBranch` 指定其真实远端默认分支。prepare 冻结所有
@@ -444,6 +451,8 @@ hook 在 `prepare` 调用时运行，命令调用本身即授权执行。gate
 
 每个适配器闭包都自带 CLI、skills 和 schemas 副本，安装后无需外部依赖即可运行。Claude/Codex 验证是自动化的；Kimi Code 和 CodeBuddy/WorkBuddy 以 `manualFollowUps` 返回并标记 `verifiedBySystem: false`，其完成情况不阻塞自动发布进入 `VERIFIED`。
 
+`codebuddy-plugin` 分发可以可选地声明 `marketplace`（以及 `marketplaceSource`，即消费者添加市场所用的 URL）来覆盖默认统一市场 `artifact-skill-set`；未声明的分发保持默认值，冻结计划字节不变。
+
 每个 npm 分发在 `prepare` 时都会针对精确封装的 tarball 静态校验
 `package.json` 声明的具体入口。`publish` 与 `reconcile` 在任何远端动作前对同一
 冻结 tarball 重复校验，`verify` 则在允许进入 `VERIFIED` 前对精确安装目录重复校验。
@@ -463,4 +472,4 @@ hook 在 `prepare` 调用时运行，命令调用本身即授权执行。gate
 
 ## 许可证
 
-MIT，见 [LICENSE](LICENSE)。
+Apache License 2.0，见 [LICENSE](LICENSE) 与 [NOTICE](NOTICE)。