release-skill 0.3.0 → 0.4.1

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.3.0 -->
+<!-- release-skill:release-version: 0.4.1 -->
 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,27 +14,20 @@ 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.3.0** (2026-07-31)
+**0.4.1** (2026-08-03)
 
-v0.3.0 streamlines production releases into a resumable orchestration with reusable hook receipts, consolidated approvals, and stronger consumer-install evidence.
-
-**Added**
-
-- **Resumable ship orchestration**: the new `ship` command persists the active release state and resumes prepare, approval, publish, reconcile, and verification without rebuilding authority from conversational context.
-- **Reusable hook receipts**: `hooks validate` executes declared hooks through the same content-bound cache used by prepare, so unchanged checks do not need to run again.
-- **Verified manual attestations**: `attest` validates a reported Kimi or CodeBuddy installation against the exact frozen plugin payload before recording consumer evidence.
-- **Git transport preflight**: production publishing selects one repository-consistent HTTPS or SSH transport before any remote write and blocks conflicting remote identities.
+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**
 
-- **Consolidated human decisions**: the normal path requires at most one hook-side-effect authorization and one immutable-plan approval; manual consumer requirements are collected before automatic verification.
-- **Parallel consumer verification**: independent consumer checks run concurrently, drain before failure reporting, and produce deterministically ordered evidence.
-- **Automatic release metadata**: successful verification advances each unit's `previousPublicBaseline` to the frozen public commit, tree, and manifest digest.
-- **Compact prepare output**: JSON output references the immutable plan by path and digest instead of embedding the full plan.
+- **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:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **Current boundary:** v0.3.0 is the current release (v0.2.2 previously held
+> **Current boundary:** v0.4.1 is the current source candidate; v0.4.0 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
@@ -52,8 +45,8 @@ v0.3.0 streamlines production releases into a resumable orchestration with reusa
 > publish global preflight.
 
 <!-- release-skill:capability:safe-first-command -->
-> **Production path verified since the v0.1.1 milestone; v0.3.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.1 is the current
+> source candidate and v0.4.0 is the latest published release.** The npm-installed CLI is the supported user entry. Source checkout
 > is the development/contributor fallback.
 >
 > **Start here:**
@@ -63,10 +56,15 @@ v0.3.0 streamlines production releases into a resumable orchestration with reusa
 <!-- 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`. `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).
 
 ## Table of contents
 
@@ -119,32 +117,24 @@ 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 two authorization
-digests: one for the exact configured hooks and one for the frozen plan. The
-plan approval also authorizes that plan's post-publish verification gates.
+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" --authorize-hooks <hookDigest> --actor "$ACTOR" --json
-release-skill ship --root "$PROJECT" --approve-plan <planDigest> --actor "$ACTOR" --json
-```
-
-If interactive consumers are required, `ship` returns every Kimi/CodeBuddy
-requirement at once. After installing/reloading, record the human fact without
-editing JSON and rerun `ship`:
-
-```bash
-release-skill attest --root "$PROJECT" --platform kimi --plugin my-plugin \
-  --result passed --actor "$ACTOR" --install-path /actual/managed/plugin/path
-release-skill ship --root "$PROJECT" --json
+release-skill ship --root "$PROJECT" --approve --actor "$ACTOR" --json
 ```
 
-During development, `release-skill hooks validate
---acknowledge-hook-side-effects` runs declared hooks and writes the same
-content-bound cache receipts that `prepare` consumes.
+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")
@@ -208,41 +198,35 @@ 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')
    ```
+   `--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" \
-     --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
@@ -257,12 +241,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,
@@ -300,9 +282,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
 
@@ -482,9 +467,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
 
@@ -492,7 +477,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.
 
@@ -506,14 +491,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
@@ -534,12 +520,12 @@ 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.
 
 ## License
 
-MIT. See [LICENSE](LICENSE).
+Apache License 2.0. See [LICENSE](LICENSE) and [NOTICE](NOTICE).