release-skill 0.2.6 → 0.2.8

package/.claude-plugin/marketplace.json

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

package/.codebuddy-plugin/plugin.json

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

package/.codex-plugin/plugin.json

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

package/.kimi-plugin/plugin.json

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

package/CHANGELOG.md

@@ -1,5 +1,47 @@
 # Changelog
 
+<!-- release-skill:changelog:start version=0.2.8 locale=en baseline=sha256:ad6e8910f1af206463b5decf134b82590787b77f5a88faca3d8985d3686b111b -->
+## [0.2.8] - 2026-07-30
+
+v0.2.8 adds a project-configurable expected public-surface gate so newly added or omitted release files cannot silently disappear from a frozen snapshot.
+
+### Added
+
+- **Expected public surface**: release units can declare physical scan roots with compact `include` and `exclude` globs instead of maintaining a second per-file checker.
+- **Exhaustive classification diagnostics**: prepare reports missing mappings, unexpected mappings, unclassified files, and files that ambiguously match both include and exclude rules.
+
+### Changed
+
+- **Post-build release gate**: prepare scans the actual workspace after build hooks and blocks before source-authority closure, baseline capture, snapshot construction, or plan creation.
+- **Bounded glob and path safety**: the built-in scanner supports `*`, `?`, and `**`, rejects overlapping or escaping scan roots, and keeps workspace control paths outside the project classification surface.
+
+### Fixed
+
+- **Silent release-file omission**: a file classified for publication can no longer be absent from `publicFiles` while the release still reaches `PREPARED`.
+<!-- release-skill:changelog:end version=0.2.8 locale=en -->
+
+
+<!-- release-skill:changelog:start version=0.2.7 locale=en baseline=sha256:05d12ddcc435b3c4438561dba780481ead1ac7662d946c3c36ddf8123dcaebe3 -->
+## [0.2.7] - 2026-07-29
+
+v0.2.7 prevents npm packages with missing declared runtime entries from being prepared, published, reconciled, or marked as verified.
+
+### Added
+
+- **Static npm entry closure**: release-skill checks `bin`, `main`, `module`, `types`, `typings`, and concrete local `exports` targets against the exact frozen tarball and the freshly installed package.
+- **Setup diagnostics**: setup reports declared npm entry candidates as tracked, untracked, ignored, missing, or non-regular without modifying project configuration.
+
+### Changed
+
+- **Fail-closed unsupported exports**: wildcard exports and fallback arrays remain outside the minimal resolver boundary and now block release instead of being guessed or silently skipped.
+- **Final write-boundary verification**: the npm adapter rechecks the same digest-verified tarball buffer immediately before registry publication.
+
+### Fixed
+
+- **Empty-shell package verification**: a package can no longer reach `PREPARED`, remote publication, reconciliation, or `VERIFIED` when its declared runtime or type entry is absent.
+<!-- release-skill:changelog:end version=0.2.7 locale=en -->
+
+
 <!-- release-skill:changelog:start version=0.2.6 locale=en baseline=sha256:ba7fe1d8cbae8ea3a539016c1231acd066f6dbf30b6e1ebb9db50e7c04e69253 -->
 ## [0.2.6] - 2026-07-29
 

package/INSTALL.md

@@ -2,7 +2,7 @@
 
 [简体中文](INSTALL.zh-CN.md)
 
-<!-- release-skill:release-version: 0.2.6 -->
+<!-- release-skill:release-version: 0.2.8 -->
 ## Prerequisites
 
 - Node.js 22.0.0 or later
@@ -120,7 +120,7 @@ as a version-pinned **manual** install plus trusted observation/attestation:
    permanent writes are consistent. The run record gives the pinned install URL
    and the attestation path.
 2. Read the requirement at
-   `<root>/.release-skill/kimi-attestations/<planDigest>/<plugin>/release-skill-kimi-manual-install.json`.
+   `<root>/.release-skill/kimi-attestations/<plugin>/release-skill-kimi-manual-install.json`.
 3. Launch Kimi Code and install from the release 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. Before writing the
@@ -128,19 +128,19 @@ as a version-pinned **manual** install plus trusted observation/attestation:
    frozen version; otherwise do NOT issue an attestation.
 
    ```
-   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.2.6
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.2.8
    /plugins reload
    ```
 
 4. Write the attestation JSON to
-   `<root>/.release-skill/kimi-attestations/<planDigest>/<plugin>/release-skill-kimi-attestation.json`.
+   `<root>/.release-skill/kimi-attestations/<plugin>/release-skill-kimi-attestation.json`.
    `planDigest` MUST be the frozen **plan** digest; `result` accepts only
    `"passed"` or `"failed"`. Example:
 
 ```json
 {
   "platform": "kimi",
-  "version": "0.2.6",
+  "version": "0.2.8",
   "planDigest": "<64-hex frozen plan digest>",
   "result": "passed",
   "actor": "<person who confirmed>",
@@ -150,8 +150,8 @@ as a version-pinned **manual** install plus trusted observation/attestation:
 ```
 
 5. Run `release-skill verify --run <publish-run>` (→
-   `VERIFIED`). The verify command reads the attestation from the same
-   plan-digest-keyed directory, so the fresh run directory does not lose the proof.
+   `VERIFIED`). The verify command reads the attestation from the stable
+   plugin-level directory, so the fresh run directory does not lose the proof.
 
 When a platform has no reliable automated verification, the bound human
 `passed`/`failed` attestation is authoritative. The `verify` command consumes
@@ -191,20 +191,20 @@ attestation (the same capability gap and closed loop as Kimi Code):
    install path fails closed. The run enters `PUBLISHED` after all remote
    permanent writes are consistent. The run record gives the attestation path.
 2. Read the requirement at
-   `<root>/.release-skill/codebuddy-attestations/<planDigest>/<plugin>/release-skill-codebuddy-manual-install.json`.
+   `<root>/.release-skill/codebuddy-attestations/<plugin>/release-skill-codebuddy-manual-install.json`.
 3. Install release-skill from the bundled-family marketplace `ifoohoo/release-skill`
    (https://github.com/ifoohoo/release-skill). Before writing the
    attestation you MUST confirm the installed plugin manifest version equals the
    frozen version; otherwise do NOT issue an attestation.
 4. Write the attestation JSON to
-   `<root>/.release-skill/codebuddy-attestations/<planDigest>/<plugin>/release-skill-codebuddy-attestation.json`.
+   `<root>/.release-skill/codebuddy-attestations/<plugin>/release-skill-codebuddy-attestation.json`.
    `planDigest` MUST be the frozen **plan** digest; `result` accepts only
    `"passed"` or `"failed"`. Example:
 
 ```json
 {
   "platform": "codebuddy",
-  "version": "0.2.6",
+  "version": "0.2.8",
   "planDigest": "<64-hex frozen plan digest>",
   "result": "passed",
   "actor": "<person who confirmed>",
@@ -214,8 +214,8 @@ attestation (the same capability gap and closed loop as Kimi Code):
 ```
 
 5. Run `release-skill verify --run <publish-run>` (→
-   `VERIFIED`). The verify command reads the attestation from the same
-   plan-digest-keyed directory, so the fresh run directory does not lose the proof.
+   `VERIFIED`). The verify command reads the attestation from the stable
+   plugin-level directory, so the fresh run directory does not lose the proof.
 
 When a platform has no reliable automated verification, the bound human
 `passed`/`failed` attestation is authoritative. The `verify` command consumes

package/INSTALL.zh-CN.md

@@ -2,7 +2,7 @@
 
 [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.2.6 -->
+<!-- release-skill:release-version: 0.2.8 -->
 ## 前置条件
 
 - Node.js 22.0.0 或更高版本
@@ -106,25 +106,25 @@ release-skill 把 Kimi 安装建模为“版本钉死的手动安装 + 可信观
 1. `publish` 先完成自动化远端写入（Git branch/tag、npm、GitHub Release）。
    `kimi-marketplace-install` 动作在 publish 阶段记录为 `DEFERRED`，不调用市场适配器，自动化安装路径失败关闭。全部远端永久写入一致后运行进入 `PUBLISHED`。运行记录会给出钉死的安装 URL 与证明写入路径。
 2. 读取 requirement：
-   `<root>/.release-skill/kimi-attestations/<planDigest>/<plugin>/release-skill-kimi-manual-install.json`。
+   `<root>/.release-skill/kimi-attestations/<plugin>/release-skill-kimi-manual-install.json`。
 3. 启动 Kimi Code，从钉死到精确版本的 release tag 安装（切勿使用裸仓库地址，
    它会安装最新 release 或默认分支），确认信任提示后重新加载。写出证明之前，
    必须核实已安装插件清单版本等于冻结版本；否则**不得**出具证明。
 
    ```
-   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.2.6
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.2.8
    /plugins reload
    ```
 
 4. 把人工结果 JSON 写入
-   `<root>/.release-skill/kimi-attestations/<planDigest>/<plugin>/release-skill-kimi-attestation.json`。
+   `<root>/.release-skill/kimi-attestations/<plugin>/release-skill-kimi-attestation.json`。
    `planDigest` 必须是冻结**计划**摘要；`result` 只接受 `"passed"` 或 `"failed"`。
    示例：
 
 ```json
 {
   "platform": "kimi",
-  "version": "0.2.6",
+  "version": "0.2.8",
   "planDigest": "<64 位十六进制冻结计划摘要>",
   "result": "passed",
   "actor": "<确认人>",
@@ -134,7 +134,7 @@ release-skill 把 Kimi 安装建模为“版本钉死的手动安装 + 可信观
 ```
 
 5. 运行 `release-skill verify --run <publish-run>`（→
-   `VERIFIED`）。verify 命令从同一个按计划摘要命名的目录读取证明，因此新的
+   `VERIFIED`）。verify 命令从稳定的插件级目录读取证明，因此新的
    run 目录不会丢失该证明。
 
 当平台没有可靠的自动化验证时，绑定后的人工 `passed`/`failed` 结果即为权威判定。
@@ -166,19 +166,19 @@ codebuddy CLI 可以添加市场并安装插件，但 **`plugin marketplace add`
    `codebuddy-marketplace-install` 动作在 publish 阶段记录为 `DEFERRED`，不调用
    市场适配器，自动化安装路径失败关闭。全部远端永久写入一致后运行进入 `PUBLISHED`。运行记录会给出证明写入路径。
 2. 读取 requirement：
-   `<root>/.release-skill/codebuddy-attestations/<planDigest>/<plugin>/release-skill-codebuddy-manual-install.json`。
+   `<root>/.release-skill/codebuddy-attestations/<plugin>/release-skill-codebuddy-manual-install.json`。
 3. 从 bundled-family 市场 `ifoohoo/release-skill`
    （https://github.com/ifoohoo/release-skill）安装 release-skill。
    写出证明之前，必须核实已安装插件清单版本等于冻结版本；否则**不得**出具证明。
 4. 把人工结果 JSON 写入
-   `<root>/.release-skill/codebuddy-attestations/<planDigest>/<plugin>/release-skill-codebuddy-attestation.json`。
+   `<root>/.release-skill/codebuddy-attestations/<plugin>/release-skill-codebuddy-attestation.json`。
    `planDigest` 必须是冻结**计划**摘要；`result` 只接受 `"passed"` 或 `"failed"`。
    示例：
 
 ```json
 {
   "platform": "codebuddy",
-  "version": "0.2.6",
+  "version": "0.2.8",
   "planDigest": "<64 位十六进制冻结计划摘要>",
   "result": "passed",
   "actor": "<确认人>",
@@ -188,7 +188,7 @@ codebuddy CLI 可以添加市场并安装插件，但 **`plugin marketplace add`
 ```
 
 5. 运行 `release-skill verify --run <publish-run>`（→
-   `VERIFIED`）。verify 命令从同一个按计划摘要命名的目录读取证明，因此新的
+   `VERIFIED`）。verify 命令从稳定的插件级目录读取证明，因此新的
    run 目录不会丢失该证明。
 
 当平台没有可靠的自动化验证时，绑定后的人工 `passed`/`failed` 结果即为权威判定。

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.6 -->
+<!-- release-skill:release-version: 0.2.8 -->
 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,27 @@ 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.6** (2026-07-29)
+**0.2.8** (2026-07-30)
 
-v0.2.6 adds a source-authority content gate so a production release cannot succeed while the project workspace's real default branch still exposes stale public files.
+v0.2.8 adds a project-configurable expected public-surface gate so newly added or omitted release files cannot silently disappear from a frozen snapshot.
 
 **Added**
 
-- **Source-authority content closure**: prepare freezes the exact public input paths and executable modes that must exist on the configured source repository's actual default branch.
-- **Pre-publish remote proof**: publish compares the frozen closure with the remote default branch before any external write and records a digest-bound receipt that verify requires.
+- **Expected public surface**: release units can declare physical scan roots with compact `include` and `exclude` globs instead of maintaining a second per-file checker.
+- **Exhaustive classification diagnostics**: prepare reports missing mappings, unexpected mappings, unclassified files, and files that ambiguously match both include and exclude rules.
 
 **Changed**
 
-- **Branch topology tolerance**: projects may develop directly on the default branch or use release branches; compliance is based on final content, not merge ancestry or a hard-coded branch name.
-- **Minimal conflict policy**: divergent or conflicting source state fails closed with diagnostics; Release Skill does not auto-merge, rebase, force-push, or create a replacement branch workflow.
+- **Post-build release gate**: prepare scans the actual workspace after build hooks and blocks before source-authority closure, baseline capture, snapshot construction, or plan creation.
+- **Bounded glob and path safety**: the built-in scanner supports `*`, `?`, and `**`, rejects overlapping or escaping scan roots, and keeps workspace control paths outside the project classification surface.
 
 **Fixed**
 
-- **Stale workspace README after release**: production publishing now blocks when the source workspace's real default branch does not contain the frozen public README and other declared source inputs.
+- **Silent release-file omission**: a file classified for publication can no longer be absent from `publicFiles` while the release still reaches `PREPARED`.
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **Current boundary:** v0.2.6 is the current release (v0.2.2 previously held
+> **Current boundary:** v0.2.8 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
@@ -52,7 +52,7 @@ v0.2.6 adds a source-authority content gate so a production release cannot succe
 > publish global preflight.
 
 <!-- release-skill:capability:safe-first-command -->
-> **Production path verified since the v0.1.1 milestone; v0.2.6 is the current
+> **Production path verified since the v0.1.1 milestone; v0.2.8 is the current
 > release.** The npm-installed CLI is the supported user entry. Source checkout
 > is the development/contributor fallback.
 >
@@ -167,7 +167,12 @@ ACTOR=your-name
    ```
    The write must return `CONFIG_CREATED`; the next setup must return
    `ALREADY_CONFIGURED`. Existing configuration is never regenerated — make only
-   reviewed incremental edits. Discovered scripts are `SIDE_EFFECTS_UNPROVEN`.
+   reviewed incremental edits. For npm units, setup also reports each concrete
+   `bin`/`main`/`module`/`types`/`typings`/`exports` target and legacy
+   `npmRequiredPackagePaths` as tracked, untracked, ignored, missing, or
+   non-regular. These are review candidates only: setup never copies them into
+   `publicFiles` or `requiredPublicFiles`. Discovered scripts are
+   `SIDE_EFFECTS_UNPROVEN`.
    Add a project-specific hook or gate only after human review: edit
    `projectConfig.hooks`, or edit `verificationGates` and add the same id to
    `selectedGateIds`, then rerun the bound dry-run.
@@ -485,6 +490,16 @@ 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.
 
+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
+action, and `verify` repeats it against the exact installed package before
+allowing `VERIFIED`. `smokeBin` remains optional: when configured it adds an
+authorized runtime smoke test; when absent, the static entry-closure check is
+still mandatory. Wildcard exports and fallback arrays are deliberately outside
+the first minimal semantic boundary, so the static gate fails closed until the
+declaration is narrowed to concrete targets.
+
 <!-- release-skill:capability:unsupported-scope -->
 - no automatic README generation or source-file overwrite;
 - no automatic conflict merge or rollback workflow;

package/README.zh-CN.md

@@ -2,33 +2,33 @@
 
 [English](README.md) · 安装指南：[中文](INSTALL.zh-CN.md) / [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.2.6 -->
+<!-- release-skill:release-version: 0.2.8 -->
 面向 Claude Code、CodeBuddy、WorkBuddy、Codex 和 Kimi Code 的发布准备工具，完整保留人工维护的文件内容。
 
 release-skill 帮助维护者回答三个问题：准备发布什么、还有哪些检查未通过、最终发布的内容是什么。它不重新生成、也不回写项目源文件。`prepare` 把每个配置的公开文件复制到隔离快照并验证字节——先冻结并供人工审阅，再从同一份冻结产物发布。`setup` 只显示确定性的 `compactSummary` 审阅视图，完整报告保留在临时会话目录中。
 
 <!-- release-skill:managed:start id=latest-release -->
-**0.2.6** (2026-07-29)
+**0.2.8** (2026-07-30)
 
-v0.2.6 新增源码权威内容门，避免生产发布完成后，项目工作区的真实默认分支仍对外展示旧 README 等公开文件。
+v0.2.8 新增项目可配置的期望发布面门禁，防止新增或漏声明的发布文件静默消失在冻结快照之外。
 
 **新增**
 
-- **源码权威内容闭包**：prepare 冻结必须出现在所配置源码仓真实默认分支上的公开输入路径、内容与可执行位。
-- **发布前远端证明**：publish 在任何外部写入前对比冻结闭包与远端默认分支，并生成摘要绑定的收据；verify 必须消费该收据。
+- **期望发布面**：发布单元可以通过精简的 `include`、`exclude` glob 声明物理扫描根，无需再维护第二份逐文件检查器。
+- **穷举分类诊断**：prepare 会报告缺失映射、多余映射、未分类文件，以及同时命中包含和排除规则的歧义文件。
 
 **变更**
 
-- **兼容不同分支拓扑**：项目既可直接在默认分支迭代，也可使用发布分支；是否合规只看最终内容，不依赖合并祖先关系或写死的分支名。
-- **最小冲突策略**：分叉或冲突状态失败关闭并给出诊断；Release Skill 不自动 merge、rebase、force-push，也不引入替代性的分支工作流。
+- **构建后发布门禁**：prepare 在 build hook 后扫描真实工作区，并在源码权威闭集、基线捕获、快照构建和计划写入前阻断失败。
+- **有界 glob 与路径安全**：内建扫描器支持 `*`、`?`、`**`，拒绝重叠或逃逸的扫描根，并将工作区控制面排除在项目分类范围之外。
 
 **修复**
 
-- **修复发布后工作区 README 陈旧**：当源码工作区真实默认分支缺少冻结后的 README 或其他声明输入时，生产发布会在外部写入前阻断。
+- **发布文件静默漏项**：已归类为应发布的文件如果缺少 `publicFiles` 映射，发布将无法再进入 `PREPARED`。
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **当前边界：** v0.2.6 是当前发布版本（v0.2.2 曾处于已发布状态，后因平台验证收敛修复而更新）。
+> **当前边界：** v0.2.8 是当前发布版本（v0.2.2 曾处于已发布状态，后因平台验证收敛修复而更新）。
 > v0.1.1 已完成 GitHub 与 npm 的
 > 真实生产发布，是首次生产验证的历史里程碑，并从冻结 Git ref 完成精确 npm
 > 安装及 Claude/Codex 消费者安装验证；"当前发布版本"与"首次生产验证里程碑"
@@ -41,7 +41,7 @@ v0.2.6 新增源码权威内容门，避免生产发布完成后，项目工作
 > 远端唯一性检查在 `publish` 全局预检执行。
 
 <!-- release-skill:capability:safe-first-command -->
-> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.2.6 是当前发布版本。**
+> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.2.8 是当前发布版本。**
 > npm 安装的 CLI 是受支持的用户入口；源码 checkout 保留为开发/贡献者路径。
 >
 > **第一条命令：**
@@ -152,7 +152,11 @@ ACTOR=your-name
    ```
    写入必须返回 `CONFIG_CREATED`，下一次 setup 必须返回 `ALREADY_CONFIGURED`。
    已有配置永不重新生成，后续只做经审阅的增量编辑。发现的脚本标记为
-   `SIDE_EFFECTS_UNPROVEN`。只有在人工审阅之后才添加项目专属 hook 或 gate：
+   `SIDE_EFFECTS_UNPROVEN`。对于 npm 单元，setup 还会把具体
+   `bin`/`main`/`module`/`types`/`typings`/`exports` 目标和旧
+   `npmRequiredPackagePaths` 标成已跟踪、未跟踪、已忽略、缺失或非普通文件。
+   这些只是假设候选：setup 不会自动写入 `publicFiles` 或
+   `requiredPublicFiles`。只有在人工审阅之后才添加项目专属 hook 或 gate：
    编辑 `projectConfig.hooks`，或编辑 `verificationGates` 并把同一个 id 加入
    `selectedGateIds`，然后重新运行绑定 dry-run。配置已存在时跳过。
    完整多步流程见 [INSTALL.zh-CN.md](INSTALL.zh-CN.md#首次接入)。
@@ -437,6 +441,13 @@ hook 仅在人工审阅后、以 `--acknowledge-hook-side-effects` 显式授权
 
 每个适配器闭包都自带 CLI、skills 和 schemas 副本，安装后无需外部依赖即可运行。Claude/Codex 验证是自动化的；Kimi Code 和 CodeBuddy/WorkBuddy 需要绑定冻结计划摘要的可信证明。
 
+每个 npm 分发在 `prepare` 时都会针对精确封装的 tarball 静态校验
+`package.json` 声明的具体入口。`publish` 与 `reconcile` 在任何远端动作前对同一
+冻结 tarball 重复校验，`verify` 则在允许进入 `VERIFIED` 前对精确安装目录重复校验。
+`smokeBin` 仍是可选的：配置后增加需授权的运行时烟雾测试；未配置时，静态入口闭包
+检查仍然是强制门禁。通配符 exports 与 fallback array 刻意不纳入首版最小语义边界，
+静态门禁会阻断，直到入口声明收窄为具体目标。
+
 <!-- release-skill:capability:unsupported-scope -->
 - 不自动生成 README，不覆盖项目源文件；
 - 不自动合并冲突，也不要求回滚工作流；

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

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