release-skill 0.2.5 → 0.2.7

package/.claude-plugin/marketplace.json

@@ -9,7 +9,7 @@
     {
       "name": "release-skill",
       "source": "./",
-      "version": "0.2.5",
+      "version": "0.2.7",
       "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.5",
+  "version": "0.2.7",
   "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.5",
+  "version": "0.2.7",
   "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.5",
+  "version": "0.2.7",
   "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.5.",
+      "Prepare a release plan for version 0.2.7.",
       "Help me understand the release workflow."
     ]
   }

package/.kimi-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "release-skill",
-  "version": "0.2.5",
+  "version": "0.2.7",
   "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.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
+
+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.
+
+### 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.
+
+### 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.
+
+### 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.
+<!-- release-skill:changelog:end version=0.2.6 locale=en -->
+
+
 <!-- release-skill:changelog:start version=0.2.5 locale=en baseline=sha256:8bd4c268f65c72efeb3866ef4bcae7d1fa902e02833e622ca66670b633b124b1 -->
 ## [0.2.5] - 2026-07-28
 

package/INSTALL.md

@@ -2,7 +2,7 @@
 
 [简体中文](INSTALL.zh-CN.md)
 
-<!-- release-skill:release-version: 0.2.5 -->
+<!-- release-skill:release-version: 0.2.7 -->
 ## 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.5
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.2.7
    /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.5",
+  "version": "0.2.7",
   "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.5",
+  "version": "0.2.7",
   "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
@@ -345,7 +345,11 @@ setup; use the mechanically extracted `recommendedAnswers`.
   "projectConfig": {
     "apiVersion": "release-skill/v1",
     "kind": "ReleaseProject",
-    "project": { "name": "my-project", "defaultBranch": "main" },
+    "project": {
+      "name": "my-project",
+      "defaultBranch": "main",
+      "sourceRepository": "owner/my-workspace"
+    },
     "releaseUnits": [{
       "id": "my-project",
       "source": ".",
@@ -428,6 +432,7 @@ kind: ReleaseProject
 project:
   name: my-project
   defaultBranch: main
+  sourceRepository: owner/my-workspace
 
 releaseUnits:
   - id: my-project
@@ -643,6 +648,23 @@ The last two strategies require online production prepare. Any mismatch stops
 for review; update the human-owned config only after inspecting real remote
 state, and never force-push or weaken the baseline.
 
+### Workspace source authority
+
+`project.sourceRepository` is the GitHub `owner/repo` of the workspace that
+owns the human source files; it may differ from every release unit's
+`publicRepo`. `project.defaultBranch` is that repository's actual remote
+default branch and is not assumed to be `main`.
+
+Production prepare freezes a content-and-mode closure of every expanded
+`publicFiles.from` input and each unit's `version.source`. It rejects only
+uncommitted changes inside that closure. Before any publish adapter executes,
+release-skill verifies the same closure on the remote default branch. Commit
+ancestry is intentionally irrelevant: merge, squash, and rebase are accepted
+when the bytes still match, while a reverted or conflict-lost README is
+blocked by path. Resolve differences manually and put the accepted content on
+the default branch; release-skill never merges, switches branches, pushes, or
+creates a PR.
+
 ## Protect Human-Owned Content
 
 README text, slogans, examples, layout, and other manually curated source files
@@ -673,10 +695,12 @@ When an existing public copy has drifted, choose explicitly:
   a release plan.
 - Before production, configure every unit's `previousPublicBaseline`. Use
   `mode: bound` with the exact `repo`, `ref`, and `commit` for an existing
-  public version, then run `"${CLI[@]}" prepare --root <your-project> --online --production`.
+  public version. Also configure the workspace `project.sourceRepository` and
+  its real `project.defaultBranch`, then run
+  `"${CLI[@]}" prepare --root <your-project> --online --production`.
   The default observer proves only the ref-to-commit mapping; remote content is
-  not downloaded. Target branch/tag/Release/npm uniqueness is checked by the
-  publish global preflight before any execute.
+  not downloaded during prepare. Source content authority and target
+  branch/tag/Release/npm uniqueness are checked by publish before any execute.
 - For production commands, use only the immutable `planPath` returned by
   `prepare --json` and immutable `approvalPath` returned by `approve --json`.
   Mutable latest aliases are for convenience and are not production authority.

package/INSTALL.zh-CN.md

@@ -2,7 +2,7 @@
 
 [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.2.5 -->
+<!-- release-skill:release-version: 0.2.7 -->
 ## 前置条件
 
 - 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.5
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.2.7
    /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.5",
+  "version": "0.2.7",
   "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.5",
+  "version": "0.2.7",
   "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` 结果即为权威判定。
@@ -297,7 +297,11 @@ node -e 'require("node:fs").rmSync(process.argv[1],{recursive:true,force:false})
   "projectConfig": {
     "apiVersion": "release-skill/v1",
     "kind": "ReleaseProject",
-    "project": { "name": "my-project", "defaultBranch": "main" },
+    "project": {
+      "name": "my-project",
+      "defaultBranch": "main",
+      "sourceRepository": "owner/my-workspace"
+    },
     "releaseUnits": [{
       "id": "my-project",
       "source": ".",
@@ -362,6 +366,7 @@ kind: ReleaseProject
 project:
   name: my-project
   defaultBranch: main
+  sourceRepository: owner/my-workspace
 
 releaseUnits:
   - id: my-project
@@ -512,6 +517,19 @@ production:
 
 后两种策略必须在线执行 production prepare。任何不一致都应停止并审阅；只有检查真实远端状态后才能人工更新权威配置，禁止 force push 或弱化基线。
 
+### Workspace 源码权威
+
+`project.sourceRepository` 是承载人工源文件的 workspace GitHub
+`owner/repo`，可以与各 release unit 的 `publicRepo` 不同。
+`project.defaultBranch` 是该仓库真实的远端默认分支，不假设一定为 `main`。
+
+生产 prepare 冻结所有 `publicFiles.from` 展开输入和各 unit
+`version.source` 的内容与 Git mode，只拒绝这个闭包内的未提交变化。publish 在任何
+adapter execute 前从远端默认分支比较同一闭包。判定不依赖 commit ancestry，因此
+merge、squash、rebase 后字节仍一致即可通过；README 被 revert 或冲突解决丢失时按路径
+阻断。差异必须由人工处理并把接受内容放入默认分支；release-skill 不自动 merge、切分支、
+push 或创建 PR。
+
 ## 保护人工维护内容
 
 README 文案、slogan、示例、排版及其他人工源文件始终是权威。release-skill 只按 `publicFiles` 映射做快照，不重新生成或覆盖源 README。每次人工编辑后重新 prepare，并批准新的不可变计划；不得编辑冻结快照或复用旧批准绕过变化。
@@ -528,5 +546,9 @@ README 文案、slogan、示例、排版及其他人工源文件始终是权威
 - 缺少配置时运行 `"${CLI[@]}" setup --root <your-project> --json`，在人工决策完成前保持默认 dry-run。
 - 运行 `"${CLI[@]}" assess --root <your-project> --offline` 检查发布就绪度。
 - 运行 `"${CLI[@]}" prepare --root <your-project> --offline` 生成发布计划；release-skill 自身只做本地写入，但项目 hook 可能执行远端操作。
-- 生产前为每个 unit 配置 `previousPublicBaseline`。已有公开版本必须使用 `mode: bound`，绑定精确 `repo`、`ref` 和 `commit`，再运行 `"${CLI[@]}" prepare --root <your-project> --online --production`。
+- 生产前为每个 unit 配置 `previousPublicBaseline`。已有公开版本必须使用 `mode: bound`，
+  绑定精确 `repo`、`ref` 和 `commit`；同时配置 workspace 的
+  `project.sourceRepository` 与真实 `project.defaultBranch`，再运行
+  `"${CLI[@]}" prepare --root <your-project> --online --production`。prepare 不下载源码
+  内容；publish 会在任何 execute 前检查源码权威闭包与目标唯一性。
 - 生产命令只使用 `prepare --json` 返回的不可变 `planPath`，以及 `approve --json` 返回的不可变 `approvalPath`。

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.5 -->
+<!-- release-skill:release-version: 0.2.7 -->
 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,30 +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.5** (2026-07-28)
+**0.2.7** (2026-07-29)
 
-v0.2.5 adds a built-in skill resource-closure release gate. Release Skill now validates the actual frozen and installed plugin projections instead of treating repository-level file presence as proof that every skill can resolve its resources.
+v0.2.7 prevents npm packages with missing declared runtime entries from being prepared, published, reconciled, or marked as verified.
 
 **Added**
 
-- **Skill resource-closure gate**: recursively discovers nested skills and validates skill-local references, assets, schemas, examples, and private scripts from each skill root.
-- **Frozen and installed receipts**: prepare records closure receipts for every distribution surface, publish rechecks the frozen artifact before external writes, and verify requires matching receipts from real npm and plugin installation roots.
-- **Adversarial path checks**: rejects current-working-directory fallbacks, source-tree backjumps, absolute machine paths, path escape, symbolic links, and non-regular resource targets.
+- **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**
 
-- **Shared runtime resolution is explicit**: plugin-level scripts and cross-skill resources must resolve from a validated plugin root; bounded source-only build tools remain auditable exceptions.
-- **Kimi Code and CodeBuddy verification tightened**: consumer verification plans now bind to actual isolated or managed plugin installation paths.
-- **Legacy plan compatibility preserved**: existing frozen plans remain readable, while newly prepared plans require resource-closure evidence.
+- **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**
 
-- **Nested skill blind spot removed**: author, review, repair, and other nested skills are no longer skipped by resource validation.
-- **Public baseline tests synchronized**: migration invariants now track the configured v0.2.4 public baseline commit.
+- **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:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **Current boundary:** v0.2.5 is the current release (v0.2.2 previously held
+> **Current boundary:** v0.2.7 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
@@ -55,7 +52,7 @@ v0.2.5 adds a built-in skill resource-closure release gate. Release Skill now va
 > publish global preflight.
 
 <!-- release-skill:capability:safe-first-command -->
-> **Production path verified since the v0.1.1 milestone; v0.2.5 is the current
+> **Production path verified since the v0.1.1 milestone; v0.2.7 is the current
 > release.** The npm-installed CLI is the supported user entry. Source checkout
 > is the development/contributor fallback.
 >
@@ -170,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.
@@ -263,6 +265,15 @@ again; it never rebuilds from a template. Only files listed in `publicFiles` are
 copied. `prepare` never refreshes or rewrites human docs — maintainers update
 README, INSTALL, and CHANGELOG first, then prepare, review, and approve.
 
+**Workspace source authority:** production config names the workspace source
+repository with `project.sourceRepository` and its real remote default branch
+with `project.defaultBranch`. Prepare binds the content and Git mode of every
+expanded `publicFiles.from` input plus each `version.source`; publish compares
+that frozen closure with the remote default branch before the first adapter
+write. The check accepts merge, squash, and rebase when the bytes still match,
+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.
@@ -293,6 +304,7 @@ kind: ReleaseProject
 project:
   name: my-project
   defaultBranch: main
+  sourceRepository: owner/my-workspace
 releaseUnits:
   - id: my-project
     source: .
@@ -333,6 +345,7 @@ kind: ReleaseProject
 project:
   name: my-workspace
   defaultBranch: main
+  sourceRepository: owner/my-workspace
 releaseUnits:
   - id: my-app
     source: packages/app
@@ -390,7 +403,11 @@ and binding the same id in `selectedGateIds`:
   "projectConfig": {
     "apiVersion": "release-skill/v1",
     "kind": "ReleaseProject",
-    "project": { "name": "my-project", "defaultBranch": "main" },
+    "project": {
+      "name": "my-project",
+      "defaultBranch": "main",
+      "sourceRepository": "owner/my-workspace"
+    },
     "releaseUnits": [{
       "id": "my-project",
       "source": ".",
@@ -473,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,36 +2,33 @@
 
 [English](README.md) · 安装指南：[中文](INSTALL.zh-CN.md) / [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.2.5 -->
+<!-- release-skill:release-version: 0.2.7 -->
 面向 Claude Code、CodeBuddy、WorkBuddy、Codex 和 Kimi Code 的发布准备工具，完整保留人工维护的文件内容。
 
 release-skill 帮助维护者回答三个问题：准备发布什么、还有哪些检查未通过、最终发布的内容是什么。它不重新生成、也不回写项目源文件。`prepare` 把每个配置的公开文件复制到隔离快照并验证字节——先冻结并供人工审阅，再从同一份冻结产物发布。`setup` 只显示确定性的 `compactSummary` 审阅视图，完整报告保留在临时会话目录中。
 
 <!-- release-skill:managed:start id=latest-release -->
-**0.2.5** (2026-07-28)
+**0.2.7** (2026-07-29)
 
-v0.2.5 新增内置的技能资源闭包发布门禁。Release Skill 现在检查真实冻结产物与安装投影，不再把“仓库根目录存在文件”误当成“每个技能都能解析资源”的证据。
+v0.2.7 阻止缺少已声明运行入口的 npm 包进入准备、发布、协调或已验证终态。
 
 **新增**
 
-- **技能资源闭包门禁**：递归发现嵌套技能，并从每个技能根验证技能私有的 references、assets、schemas、examples 与 scripts。
-- **冻结态与安装态收据**：prepare 为每个分发面记录闭包收据，publish 在外部写入前复核冻结制品，verify 要求真实 npm 与插件安装根产生匹配收据。
-- **对抗性路径检查**：拒绝依赖当前工作目录、回跳源码树、机器绝对路径、路径逃逸、符号链接和非普通文件资源。
+- **npm 静态入口闭包**：release-skill 针对精确冻结 tarball 和全新安装包检查 `bin`、`main`、`module`、`types`、`typings` 及具体本地 `exports` 目标。
+- **setup 诊断**：setup 将声明的 npm 入口报告为已跟踪、未跟踪、已忽略、缺失或非普通文件，但不会修改项目配置。
 
 **变更**
 
-- **共享运行时显式解析**：插件级脚本和跨技能资源必须从已校验的插件根解析；有限的仅源码构建工具作为可审计例外保留。
-- **Kimi Code 与 CodeBuddy 验证收紧**：消费者验证计划现在绑定真实的隔离或受管插件安装路径。
-- **保留旧计划兼容性**：既有冻结计划仍可读取，新生成计划必须包含资源闭包证据。
+- **不支持的 exports 失败关闭**：通配符 exports 和 fallback array 仍处于最小解析边界之外，并改为阻断发布，不猜测展开或静默跳过。
+- **最终写入边界复检**：npm 适配器在提交注册表前，对同一份已通过摘要校验的 tarball Buffer 再次检查入口闭包。
 
 **修复**
 
-- **消除嵌套技能盲区**：author、review、repair 等嵌套技能不再被资源验证遗漏。
-- **同步公开基线测试**：迁移不变量现与配置中的 v0.2.4 公开基线提交一致。
+- **空壳包验证漏洞**：当已声明的运行入口或类型入口缺失时，包不再能够进入 `PREPARED`、远端发布、协调或 `VERIFIED`。
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **当前边界：** v0.2.5 是当前发布版本（v0.2.2 曾处于已发布状态，后因平台验证收敛修复而更新）。
+> **当前边界：** v0.2.7 是当前发布版本（v0.2.2 曾处于已发布状态，后因平台验证收敛修复而更新）。
 > v0.1.1 已完成 GitHub 与 npm 的
 > 真实生产发布，是首次生产验证的历史里程碑，并从冻结 Git ref 完成精确 npm
 > 安装及 Claude/Codex 消费者安装验证；"当前发布版本"与"首次生产验证里程碑"
@@ -44,7 +41,7 @@ v0.2.5 新增内置的技能资源闭包发布门禁。Release Skill 现在检
 > 远端唯一性检查在 `publish` 全局预检执行。
 
 <!-- release-skill:capability:safe-first-command -->
-> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.2.5 是当前发布版本。**
+> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.2.7 是当前发布版本。**
 > npm 安装的 CLI 是受支持的用户入口；源码 checkout 保留为开发/贡献者路径。
 >
 > **第一条命令：**
@@ -155,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#首次接入)。
@@ -235,6 +236,13 @@ DISCOVERED -> ASSESSED -> PREPARED -> APPROVED -> PUBLISHING -> PUBLISHED -> VER
 
 **写入安全：** `setup` 默认只读（摘要确认后仅首次创建配置）。`prepare` 只写 `.release-skill/`。`publish` 是生产写入入口，需要同时提供批准和当前计划摘要。项目 hook 和 gate 是已确认的本地进程，没有操作系统沙箱。
 
+**Workspace 源码权威：** 生产配置使用 `project.sourceRepository` 指定 workspace
+源仓库，并用 `project.defaultBranch` 指定其真实远端默认分支。prepare 冻结所有
+`publicFiles.from` 展开文件及各 `version.source` 的内容与 Git mode；publish 在第一个
+adapter 写入前与远端默认分支比较。普通 merge、squash、rebase 后内容仍一致即可通过；
+README 被冲突解决或 revert 丢失时会精确到路径阻断。系统不会自动合并、切分支、push
+或创建 PR。
+
 ## 文档导航
 
 | 文档 | 说明 |
@@ -259,6 +267,7 @@ kind: ReleaseProject
 project:
   name: my-project
   defaultBranch: main
+  sourceRepository: owner/my-workspace
 releaseUnits:
   - id: my-project
     source: .
@@ -297,6 +306,7 @@ kind: ReleaseProject
 project:
   name: my-workspace
   defaultBranch: main
+  sourceRepository: owner/my-workspace
 releaseUnits:
   - id: my-app
     source: packages/app
@@ -353,7 +363,11 @@ releaseUnits:
   "projectConfig": {
     "apiVersion": "release-skill/v1",
     "kind": "ReleaseProject",
-    "project": { "name": "my-project", "defaultBranch": "main" },
+    "project": {
+      "name": "my-project",
+      "defaultBranch": "main",
+      "sourceRepository": "owner/my-workspace"
+    },
     "releaseUnits": [{
       "id": "my-project",
       "source": ".",
@@ -427,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，不覆盖项目源文件；
 - 不自动合并冲突，也不要求回滚工作流；