release-skill 0.9.36 → 0.9.37

package/.claude-plugin/plugin.json

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

package/.cursor-plugin/plugin.json

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

package/.kimi-plugin/plugin.json

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

package/.qoder-plugin/plugin.json

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

package/CHANGELOG.md

@@ -1,5 +1,29 @@
 # Changelog
 
+<!-- release-skill:changelog:start version=0.9.37 locale=en baseline=sha256:11b436a4b3d6a642189df7126078f2fa2a2d3cf0922d8031d0c33cb12d9680d3 -->
+## [0.9.37] - 2026-10-23
+
+0.9.37 fixes a false verification failure caused by write-bit changes to installed files in the single-plugin path where the frozen plugin root is the project root. It also adds a TEST intake choice before a Skill starts a new production preparation. The three Foundation dependencies remain pinned to 0.25.0. This note is not evidence of publication, real-host acceptance, consumer installation verification, or independent acceptance.
+
+### Security
+
+- Remote-write authorization and release approval remain unchanged. Consent to skip TEST intake is not release approval.
+- Skill Family Hub is the unified marketplace. Updates use GitHub Git Data API and compare-and-swap against the observed branch head; partial Hub publication is never rolled back or force-pushed, and completed steps are not overwritten.
+
+### Added
+
+- Before a Skill starts a new production preparation, it checks `testIntake`. When wiring is missing, the Skill directs the project through the existing `skill-family-test:skill-family-test-plan` and `skill-family-test:skill-family-test-run` entries to organize the plan and checks and return the actual result. The original business owner judges the result; invoking TEST or skipping intake does not mean the tests passed. Skipping requires an explicit prompt followed by consent that applies to the current run and matches the project, version, and scope. Silence, refusal, general release preauthorization, and stale or mismatched consent do not qualify. A matching response for the current run may be reused.
+
+### Fixed
+
+- Only in the single-plugin path where the frozen plugin root is the project root, `verify` ignores changes to all write permission bits (`mode & ~0o222`) when comparing installed files with the frozen snapshot. The frozen snapshot retains its original modes. File content, type, size, non-write mode bits, missing or extra paths, and frozen bindings remain strictly checked.
+
+### Upgrade Notes
+
+This applies only to new Skill-led production preparation. Read-only and non-production paths, and approval, publish, reconcile, and formal verify for plans that are already frozen, gain no new TEST intake obligation. The direct non-interactive CLI continues to accept optional `testIntake`; no CLI argument, consent format, authentication, or state machine was added. Test results remain bound to the existing candidate and requirements contract. The release-skill standalone marketplace is deprecated; use `ifoohoo/skill-family-hub` and `release-skill@skill-family-hub`.
+<!-- release-skill:changelog:end version=0.9.37 locale=en -->
+
+
 <!-- release-skill:changelog:start version=0.9.36 locale=en baseline=sha256:704d09597e835404867409d99c9b8d674751ef145a9e0855d6e2182d768bb3a2 -->
 ## [0.9.36] - 2026-10-22
 

package/INSTALL.md

@@ -2,7 +2,7 @@
 
 [简体中文](INSTALL.zh-CN.md)
 
-<!-- release-skill:release-version: 0.9.36 -->
+<!-- release-skill:release-version: 0.9.37 -->
 ## Prerequisites
 
 - Node.js `>=22.22.2 <23` (22.22.2 or newer, and below 23)
@@ -125,7 +125,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.9.36
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.37
    /plugins reload
    ```
 

package/INSTALL.zh-CN.md

@@ -2,7 +2,7 @@
 
 [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.9.36 -->
+<!-- release-skill:release-version: 0.9.37 -->
 ## 前置条件
 
 - Node.js `>=22.22.2 <23`（22.22.2 及以上，且低于 23）
@@ -113,7 +113,7 @@ release-skill 当前只采用并验证 Kimi Code 的交互式 TUI 路径，**无
 （切勿使用裸仓库地址，它会安装最新 release 或默认分支），确认信任提示后重新加载：
 
    ```
-   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.36
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.37
    /plugins reload
    ```
 

package/README.md

@@ -2,7 +2,7 @@
 
 [简体中文](README.zh-CN.md) · Installation: [English](INSTALL.md) / [简体中文](INSTALL.zh-CN.md)
 
-<!-- release-skill:release-version: 0.9.36 -->
+<!-- release-skill:release-version: 0.9.37 -->
 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,30 @@ 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.9.36** (2026-10-22)
+**0.9.37** (2026-10-23)
 
-0.9.36 fixes incorrect rejection of valid dual-projection plugin directories in Qoder, ensures correct validation of market sources via both URL and GitHub-based manifests, and corrects Codex entry root detection to respect manifest-declared paths instead of hardcoding `skills/`. This release note is not evidence of publication, real-host acceptance, consumer installation verification, or independent acceptance. Foundation dependencies remain pinned to 0.25.0.
+0.9.37 fixes a false verification failure caused by write-bit changes to installed files in the single-plugin path where the frozen plugin root is the project root. It also adds a TEST intake choice before a Skill starts a new production preparation. The three Foundation dependencies remain pinned to 0.25.0. This note is not evidence of publication, real-host acceptance, consumer installation verification, or independent acceptance.
 
 **Security**
 
-- Foundation 0.25.0 remains unchanged; the source, scope, commit/digest, and full payload are preserved. The frozen snapshot is re-verified before writing, and the full payload is compared after installation. No new market, first-install, host strategy, framework, dependency, or tier has been introduced. 0.9.35 is immutable. Skill Family Hub remains the unified marketplace, using GitHub Git Data API and compare-and-swap bound to the observed branch head. Partial Hub publication is never rolled back or force-pushed; completed steps are not overwritten.
+- Remote-write authorization and release approval remain unchanged. Consent to skip TEST intake is not release approval.
+- Skill Family Hub is the unified marketplace. Updates use GitHub Git Data API and compare-and-swap against the observed branch head; partial Hub publication is never rolled back or force-pushed, and completed steps are not overwritten.
+
+**Added**
+
+- Before a Skill starts a new production preparation, it checks `testIntake`. When wiring is missing, the Skill directs the project through the existing `skill-family-test:skill-family-test-plan` and `skill-family-test:skill-family-test-run` entries to organize the plan and checks and return the actual result. The original business owner judges the result; invoking TEST or skipping intake does not mean the tests passed. Skipping requires an explicit prompt followed by consent that applies to the current run and matches the project, version, and scope. Silence, refusal, general release preauthorization, and stale or mismatched consent do not qualify. A matching response for the current run may be reused.
 
 **Fixed**
 
-- In 0.9.35, Qoder plugins incorrectly rejected valid dual-projection directories. The `name` and `version` in `.qoder-plugin/plugin.json` and `.claude-plugin/plugin.json` must bind to the same frozen target, though individual `skills` can differ. Each present candidate must be a valid JSON object, match the target identity, have non-empty `skills`, and resolve to a real directory within the plugin root. Native takes precedence; compatibility is only used when native is missing. If any candidate is invalid, installation fails immediately without fallback. After installation, the selected path and `skills` must exactly match the frozen choice, and full payload validation is retained.
-- Qoder now also accepts existing markets that provide `.claude-plugin/marketplace.json` instead of a root `marketplace.json`. The system supports two existing locations: a URL-based `marketplace.json` at the root, and a GitHub-based `marketplace.json` in `.claude-plugin/`. At least one must exist. Each present index must be valid and contain exactly one entry for the target plugin, bound to the same frozen identity; other plugin entries remain allowed. A bad source is not ignored just because another is valid. URL sources require exact repository and SHA verification, and any explicit `version` or `ref` must match. GitHub sources require exact verification of `repo`, `ref`, `sha`, and `entry.version`. Only confirmed missing files are considered absent. Validation occurs after market refresh and before plugin update. `ALREADY_CURRENT` remains read-only with zero update commands.
-- The Codex entry root check previously hardcoded `skills/`, rejecting valid paths like `.agents/skills/` declared in the manifest. Installation pre-check and post-install observation now respect the `skills` directory declared in the plugin manifest. When the field is missing, the default `skills/` path is retained, and existing prefix behavior is preserved. Explicitly invalid, out-of-bounds, or non-directory paths are rejected without fallback. Post-install observation and full payload verification must bind to the same frozen installation contract.
+- Only in the single-plugin path where the frozen plugin root is the project root, `verify` ignores changes to all write permission bits (`mode & ~0o222`) when comparing installed files with the frozen snapshot. The frozen snapshot retains its original modes. File content, type, size, non-write mode bits, missing or extra paths, and frozen bindings remain strictly checked.
 
 **Upgrade Notes**
 
-The release-skill standalone marketplace is deprecated; use `ifoohoo/skill-family-hub` and the updated `release-skill@skill-family-hub`, `release-finish`, and public CLI. Unmodified plugins need not be republished. Byte changes require a new frozen plan and matching approval. Installation does not imply loading — if actual loading is not observed, the state remains `reload-pending`. Local completion failure does not alter the remote `VERIFIED` status.
+This applies only to new Skill-led production preparation. Read-only and non-production paths, and approval, publish, reconcile, and formal verify for plans that are already frozen, gain no new TEST intake obligation. The direct non-interactive CLI continues to accept optional `testIntake`; no CLI argument, consent format, authentication, or state machine was added. Test results remain bound to the existing candidate and requirements contract. The release-skill standalone marketplace is deprecated; use `ifoohoo/skill-family-hub` and `release-skill@skill-family-hub`.
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **Current boundary:** v0.9.36: this README records capabilities and verification boundaries;
+> **Current boundary:** v0.9.37: this README records capabilities and verification boundaries;
 > it is not evidence of
 > publication, consumer-installation verification, or independent acceptance.
 > Release availability must be established from the corresponding release records
@@ -58,7 +61,7 @@ The release-skill standalone marketplace is deprecated; use `ifoohoo/skill-famil
 > publish global preflight.
 
 <!-- release-skill:capability:safe-first-command -->
-> **Production path verified since the v0.1.1 milestone; for v0.9.36,
+> **Production path verified since the v0.1.1 milestone; for v0.9.37,
 > publication, consumer-installation verification, and independent acceptance
 > require version-specific release records and verification results.**
 > The npm-installed CLI is the supported user entry. Source checkout
@@ -615,6 +618,17 @@ of the current plan digest. Replacing the result, criterion, scope, or allowed
 limitation invalidates the previous approval. Approve, publish, and reconcile
 re-check those originals before acting.
 
+When a Skill starts a new production prepare, it checks intake first. If
+intake is missing, it names the gap and default-pushes the existing wiring.
+Skip is allowed only after this-round matching explicit consent. Silence,
+refuse, generic publish preauthorization, and stale, other-project, version,
+or scope-mismatched consent do not skip. A matching this-round reply is
+reused. Skip is never described as tests already passed. Already-frozen
+approve, publish, reconcile, and verify do not gain a new intake obligation.
+Read-only, non-production, and delegated marketplace-only paths do not add
+one. Direct non-interactive CLI still accepts optional `testIntake` with no
+new choice flag.
+
 Use `release-skill post-release --finish` for the complete local finish. It
 always reports merge, host update, actual host loading, setup, and source-branch
 steps. Exit 0 means every applicable step completed or was explicitly skipped;

package/README.zh-CN.md

@@ -2,33 +2,36 @@
 
 [English](README.md) · 安装指南：[中文](INSTALL.zh-CN.md) / [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.9.36 -->
+<!-- release-skill:release-version: 0.9.37 -->
 面向 Claude Code、CodeBuddy、WorkBuddy、Codex 和 Kimi Code 的发布准备工具，完整保留人工维护的文件内容。
 
 release-skill 帮助维护者回答三个问题：准备发布什么、还有哪些检查未通过、最终发布的内容是什么。它不重新生成、也不回写项目源文件。`prepare` 把每个配置的公开文件复制到隔离快照并验证字节——先冻结并供人工审阅，再从同一份冻结产物发布。`setup` 只显示确定性的 `compactSummary` 审阅视图，完整报告保留在临时会话目录中。
 
 <!-- release-skill:managed:start id=latest-release -->
-**0.9.36** (2026-10-22)
+**0.9.37** (2026-10-23)
 
-0.9.36 修复 Qoder 插件清单对合法双投影目录的误拒，确保市场来源在 URL 与 GitHub 两种路径下均正确校验，修正 Codex 入口目录检测逻辑以尊重 manifest 声明路径而非硬编码 skills/。本发布说明不代表已经发布、完成真实宿主验收、完成消费者安装验证或通过独立验收。Foundation 依赖保持精确锁定为 0.25.0。
+0.9.37 修复单插件发布单元在冻结插件根为项目根目录时，安装文件写权限变化造成的验证误报，并在 Skill 发起新一轮生产准备前加入 TEST 接入选择。三个 Foundation 依赖均精确锁定为 0.25.0。本发布说明不代表已经发布、完成真实宿主验收、完成消费者安装验证或通过独立验收。
 
 **安全**
 
-- Foundation 0.25.0 保持不变；Hub 来源、user-scope、冻结 commit/digest 与完整载荷校验机制保留。写入宿主前复验冻结快照摘要，安装后比较完整载荷。无新增市场、首装、新宿主策略、新框架、新依赖或 tier 变化。0.9.35 不可变。Skill Family Hub 仍为统一市场，沿用 GitHub Git Data API，以比较后写入绑定已观察的分支头；部分发布不回滚、不覆盖已完成步骤。
+- 远端写入授权和发布批准保持不变。同意跳过 TEST 接入不等于发布批准。
+- Skill Family Hub 是统一市场，更新采用 GitHub Git Data API，并以比较后写入绑定已观察的分支头；部分发布不回滚、不覆盖已完成步骤，也不 force-push。
+
+**新增**
+
+- Skill 启动新一轮生产准备前会核对 `testIntake`。缺少接线时，Skill 会引导项目通过现有的 `skill-family-test:skill-family-test-plan` 和 `skill-family-test:skill-family-test-run` 入口组织方案与检查，并交回实际结果。结果仍由原业务职责方判读；调用 TEST 或跳过接入都不表示测试已通过。跳过前必须明确征询，并取得适用于本轮且与项目、版本、范围匹配的同意。沉默、拒绝、一般发布预授权及过期或不匹配的同意都不能作为跳过依据；本轮匹配的答复可以复用。
 
 **修复**
 
-- 0.9.35 版本中，Qoder 插件误拒自身合法的双投影目录。`.qoder-plugin/plugin.json` 与 `.claude-plugin/plugin.json` 中的 name/version 必须绑定同一冻结目标，各自 skills 可不同。每个已存在候选必须是合法 JSON 对象、目标身份匹配、skills 非空且解析为插件根内真实目录。原生优先，仅原生缺失时才选兼容；任一候选无效即失败，不回退。安装后路径与 skills 必须精确匹配冻结选择，完整载荷检查保留。
-- Qoder 现可接受只提供 `.claude-plugin/marketplace.json`、未提供根 marketplace.json 的既有市场。支持两种既有位置：根 marketplace.json 的 URL 来源，以及 `.claude-plugin/marketplace.json` 的 GitHub 来源。至少一份存在，每份已存在清单均须合法，且目标插件恰有一条、绑定同一冻结身份；市场仍可包含其他插件。不因另一份有效而忽略坏清单。URL 来源保留仓库与 sha 精确校验，显式 version/ref 必须匹配；兼容 GitHub 来源校验 repo/ref/sha/entry.version。仅确定缺文件视为缺席。市场刷新后、插件更新前校验；ALREADY_CURRENT 保持只读且零更新命令。
-- Codex 入口目录原检查写死为 skills/，误拒 `.agents/skills/` 等合法 manifest 声明路径。安装前检查与安装后观察均采用 manifest 声明的 skills 目录。字段缺省时继续使用既有 skills/ 默认路径，入口名前缀行为保留。显式无效、越界或非目录路径拒绝，不回退。已安装入口观察与完整载荷验证须绑定同一冻结安装合同。
+- 仅在单插件发布单元且冻结插件根为项目根目录的验证路径中，`verify` 比较已安装文件与冻结快照时忽略所有写权限位（`mode & ~0o222`）。冻结快照保留原始权限；文件内容、类型、大小、非写权限位、缺失或新增路径及冻结绑定仍严格检查。
 
 **升级说明**
 
-原独立的 `release-skill` 市场已弃用。使用更新后的 `release-skill@skill-family-hub` 入口、`release-finish` 与公共 CLI。未改插件无需重发，改字节须新冻结计划与匹配批准。安装 ≠ 加载，未观察实际加载则保留 reload-pending 状态。本机收尾失败不改变远端 VERIFIED 状态。统一使用 `ifoohoo/skill-family-hub` 和 `release-skill@skill-family-hub`。
+本项只适用于由 Skill 开始的新一轮生产准备。只读、非生产路径，以及已有冻结计划的批准、发布、对账和正式验证不新增 TEST 接入义务。直接非交互 CLI 仍接受可选 `testIntake`；本版本未增加 CLI 参数、同意格式、认证或状态机。测试结果继续按既有合同绑定候选与要求。原独立的 `release-skill` 市场已弃用，请使用 `ifoohoo/skill-family-hub` 和 `release-skill@skill-family-hub`。
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **当前边界：** v0.9.36 的能力范围与验证边界见本 README，
+> **当前边界：** v0.9.37 的能力范围与验证边界见本 README，
 > 不代表已经发布、完成消费者安装验证或通过独立验收。
 > 版本可用性以对应发布记录及发布后验证结果为准。
 > v0.4.1 是更早的已发布里程碑（v0.2.2 曾处于已发布状态，后因平台验证收敛修复而更新）。
@@ -44,7 +47,7 @@ release-skill 帮助维护者回答三个问题：准备发布什么、还有哪
 > 远端唯一性检查在 `publish` 全局预检执行。
 
 <!-- release-skill:capability:safe-first-command -->
-> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.9.36 的发布、消费者安装验证和独立验收状态须由该版本的发布记录及验证结果确认。**
+> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.9.37 的发布、消费者安装验证和独立验收状态须由该版本的发布记录及验证结果确认。**
 > npm 安装的 CLI 是受支持的用户入口；源码 checkout 保留为开发/贡献者路径。
 >
 > **第一条命令：**
@@ -504,6 +507,8 @@ release-finish 在 `--root` 指定的当前发布项目根目录调用该入口
 
 可选的 `testIntake` 只声明要求文件和结果文件，并且只在生产 prepare 中生效。首次生产 prepare 保存一份非正式候选，返回 `NEEDS_INPUT`（`GATE_FAILED`，退出码 13），并给出 `candidatePath`、`candidateSha256` 和 `subjectDigest`，此时不写正式计划。用 `prepare --candidate <path>` 续接同一候选；适用的冻结前要求通过后才写入正式计划和 `PREPARED`。候选不能用于批准或发布，也不能清除 `PARTIAL`、`PUBLISHED` 或 `VERIFIED`。未声明 `testIntake` 的项目保持原有 hook、完整门和发布路径。docs、config、marketplace 工作流、单元选择和无需发布的配置都不免除项目级要求。非生产 prepare 拒绝 `testIntake`，错误码为 `CONFIG_INVALID`。可选的 `testAcceptance` 进入当前计划摘要。替换结果、准则、范围或允许的限制会使原批准失效。approve、publish 和 reconcile 在动作前复核这些原件。
 
+由 Skill 发起的新一轮生产准备先核对接入。缺失则说明缺项并默认推动现有接线；仅本轮适用且范围匹配的明确同意可跳过。沉默、拒绝、仅普通发布预授权、旧轮次、其他项目、版本或范围不匹配均不可跳过；本轮匹配答复可复用。不得把跳过写成测试已达标。已冻结计划的批准、发布、对账与正式验证不回头追加接入义务。只读、非生产及 marketplace-only 委托发布不新增接入义务。直接非交互 CLI 仍接受可选 `testIntake`，不新增选择参数。
+
 完整的本地收尾使用 `release-skill post-release --finish`。命令固定报告分支决定、宿主更新、实际加载、setup 和源码分支检查：全部适用步骤完成或明确跳过时退出 0，仍有待办时退出 2，确定失败时退出 1。智能体通过绝对路径的 `--finish-feedback` JSON 文件回传观察，文件必须绑定当前计划摘要、配置摘要和规范项目根目录。反馈只作为数据：脚本不执行其中字符串，也不把反馈当成新的写入授权。`--skip-local-hosts` 显示跳过宿主更新、加载和 setup，不得与 `--hosts` 或 `--update-local-hosts` 同时使用。
 
 `distributions` 是必填字段，但可以显式设为空数组。使用

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

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

package/adapters/claude/bin/release-skill.bundle.mjs

@@ -9,9 +9,9 @@ const __bundlePkgRoot = __bundleResolve(__bundleDirname(__bundleFileURLToPath(im
 // Provide a real require() for CJS packages bundled into ESM (e.g. yaml, ajv).
 const __bundleRealRequire = __bundleCreateRequire(import.meta.url);
 // Package identity injected at build time — closure-independent --version probe.
-const __bundlePkg = Object.freeze({"name":"release-skill","version":"0.9.36"});
+const __bundlePkg = Object.freeze({"name":"release-skill","version":"0.9.37"});
 // Build-time source digest for the BUNDLE_STALE freshness gate (see above).
-const __bundleSourceDigest = "bc9386087a5bffe2f92c12f687ec75582a9e853164020e99618a4bdf5cd13a68";
+const __bundleSourceDigest = "6eb7b6560da84252426dc5cfc81297a3d5d6d6101aecb1a8fbf3f35402892715";
 
 var __create = Object.create;
 var __defProp = Object.defineProperty;
@@ -116683,6 +116683,49 @@ import { dirname as dirname11, join as join20, relative as relative18, isAbsolut
 import { tmpdir as tmpdir3 } from "node:os";
 import { execFile as execFileCb7 } from "node:child_process";
 import { promisify as promisify7 } from "node:util";
+function transportIdentityEntries(entries) {
+  return entries.map(({ path: path43, type, mode, size, contentDigest }) => ({
+    path: path43,
+    type,
+    mode: mode & ~WRITE_BITS,
+    size,
+    contentDigest
+  }));
+}
+function compareInstallToFrozenTransport(frozenEntries, installedEntries) {
+  const frozen = transportIdentityEntries(frozenEntries);
+  const installed = transportIdentityEntries(installedEntries);
+  const installedByPath = new Map(installed.map((entry) => [entry.path, entry]));
+  const conflicts = [];
+  for (const frozenEntry of frozen) {
+    const installedEntry = installedByPath.get(frozenEntry.path);
+    if (!installedEntry) {
+      conflicts.push(`missing: ${frozenEntry.path}`);
+      continue;
+    }
+    if (installedEntry.type !== frozenEntry.type) {
+      conflicts.push(`type mismatch: ${frozenEntry.path}`);
+    } else if (installedEntry.size !== frozenEntry.size || installedEntry.contentDigest !== frozenEntry.contentDigest) {
+      conflicts.push(`content mismatch: ${frozenEntry.path}`);
+    } else if (installedEntry.mode !== frozenEntry.mode) {
+      conflicts.push(`mode mismatch: ${frozenEntry.path}`);
+    }
+  }
+  const frozenPaths = new Set(frozen.map((entry) => entry.path));
+  for (const installedEntry of installed) {
+    if (!frozenPaths.has(installedEntry.path)) {
+      conflicts.push(`extra: ${installedEntry.path}`);
+    }
+  }
+  return conflicts;
+}
+function frozenSnapshotRelativePath(unit, actions, unitId) {
+  if (typeof unit?.frozenSnapshot?.path === "string" && unit.frozenSnapshot.path.length > 0) {
+    return unit.frozenSnapshot.path;
+  }
+  const action = (actions ?? []).find((item) => item.unitId === unitId && typeof item.parameters?.snapshotPath === "string" && item.parameters.snapshotPath.length > 0);
+  return action?.parameters?.snapshotPath ?? null;
+}
 async function verifyCursorHostDistributions({
   plan,
   root,
@@ -118258,16 +118301,65 @@ async function verifyRelease(options) {
           }
           const pluginDistCount = (surface.unit?.distributions ?? []).filter((d) => d.type !== "npm").length;
           if (pluginDistCount === 1 && surface.frozenPluginRoot === ".") {
-            const observedReceipt = createSkillResourceClosureReceipt(closureResult, {
-              unitId: surface.unitId,
-              preparedAt: expectedUnitReceipt.preparedAt ?? null,
-              exitCode: expectedUnitReceipt.exitCode ?? 0
-            });
-            assertSkillResourceClosureReceipt(
-              expectedUnitReceipt,
-              observedReceipt,
-              `unit "${surface.unitId}"`
-            );
+            const frozenRel = frozenSnapshotRelativePath(surface.unit, actions, surface.unitId);
+            if (frozenRel) {
+              const frozenDir = await resolveFrozenPath(root, frozenRel, "frozen snapshot path");
+              const frozenClosure = await checkSkillResourceClosure({
+                snapshotDir: frozenDir,
+                host: surface.host,
+                surfaceHostBindings: [{ surfaceId: surface.surfaceId, host: surface.host }]
+              });
+              const frozenReceipt = createSkillResourceClosureReceipt(frozenClosure, {
+                unitId: surface.unitId,
+                preparedAt: expectedUnitReceipt.preparedAt ?? null,
+                exitCode: expectedUnitReceipt.exitCode ?? 0
+              });
+              assertSkillResourceClosureReceipt(
+                expectedUnitReceipt,
+                frozenReceipt,
+                `unit "${surface.unitId}"`
+              );
+              const frozenSnap = await computeFrozenSnapshot(frozenDir, {
+                excludeRootEntries: TRANSPORT_EXCLUSIONS
+              });
+              const installedSnap = await computeFrozenSnapshot(surface.installPath, {
+                excludeRootEntries: TRANSPORT_EXCLUSIONS
+              });
+              const conflicts = compareInstallToFrozenTransport(
+                frozenSnap.entries,
+                installedSnap.entries
+              );
+              await evidence.append({
+                phase: "verify",
+                step: "skill-resource-closure",
+                status: "install-comparison",
+                unitId: surface.unitId,
+                frozenInputDigest: frozenSnap.digest,
+                installedInputDigest: installedSnap.digest,
+                frozenModes: frozenSnap.entries.map((entry) => ({ path: entry.path, mode: entry.mode })),
+                installedModes: installedSnap.entries.map((entry) => ({ path: entry.path, mode: entry.mode }))
+              });
+              if (conflicts.length > 0) {
+                const listed = conflicts.slice(0, PAYLOAD_CONFLICT_REPORT_CAP2).join("; ");
+                const overflow = conflicts.length > PAYLOAD_CONFLICT_REPORT_CAP2 ? `; and ${conflicts.length - PAYLOAD_CONFLICT_REPORT_CAP2} more conflicting path(s)` : "";
+                throw new ReleaseError(
+                  POST_PUBLISH_VERIFY_FAILED,
+                  `installed plugin root differs in path, bytes, size, or non-write mode bits for unit "${surface.unitId}": ${listed}${overflow}`,
+                  { unitId: surface.unitId, conflicts }
+                );
+              }
+            } else {
+              const observedReceipt = createSkillResourceClosureReceipt(closureResult, {
+                unitId: surface.unitId,
+                preparedAt: expectedUnitReceipt.preparedAt ?? null,
+                exitCode: expectedUnitReceipt.exitCode ?? 0
+              });
+              assertSkillResourceClosureReceipt(
+                expectedUnitReceipt,
+                observedReceipt,
+                `unit "${surface.unitId}"`
+              );
+            }
           }
         }
         skillResourceClosureReceipts.push(createSkillResourceClosureReceipt(
@@ -118478,7 +118570,7 @@ async function verifyRelease(options) {
     throw err;
   }
 }
-var execFile6, VERIFICATION_RESOLVED_TYPES, ADAPTER_ACTION_TYPE_MAP2, FIRST_RELEASE_BOOTSTRAP_MODE, EXTERNAL_MARKETPLACE_SHA_RE2, defaultNpmExecutor;
+var execFile6, VERIFICATION_RESOLVED_TYPES, WRITE_BITS, PAYLOAD_CONFLICT_REPORT_CAP2, ADAPTER_ACTION_TYPE_MAP2, FIRST_RELEASE_BOOTSTRAP_MODE, EXTERNAL_MARKETPLACE_SHA_RE2, defaultNpmExecutor;
 var init_verify = __esm({
   async "src/commands/verify.mjs"() {
     init_src2();
@@ -118516,6 +118608,11 @@ var init_verify = __esm({
       PASSED_MANUAL: "PASSED_MANUAL",
       NOT_REQUIRED_UNCHANGED: "NOT_REQUIRED_UNCHANGED"
     });
+    WRITE_BITS = 146;
+    PAYLOAD_CONFLICT_REPORT_CAP2 = 10;
+    __name(transportIdentityEntries, "transportIdentityEntries");
+    __name(compareInstallToFrozenTransport, "compareInstallToFrozenTransport");
+    __name(frozenSnapshotRelativePath, "frozenSnapshotRelativePath");
     __name(verifyCursorHostDistributions, "verifyCursorHostDistributions");
     __name(verifyPublicSourceAuthorityReceiptOffline, "verifyPublicSourceAuthorityReceiptOffline");
     ADAPTER_ACTION_TYPE_MAP2 = {

package/adapters/claude/skills/release-config/SKILL.md

@@ -7,36 +7,29 @@ description: "Config-only workflow profile: route confirms config-only diff, ass
 
 ## 触发
 
-用户询问或执行纯配置变更的发布流程。包含 `.release-skill/project.yaml`、配置 schema 等配置文件的修改，且无代码、文档或 marketplace 变更。
+用户发起仅配置变更的发布流程，涉及 `.release-skill/project.yaml`、配置 schema、`releaseUnits` 映射、`policy` 策略定义等配置文件的修改，且无代码、文档或 marketplace 变更。
 
 ## 当前状态
 
-`release-config` 是工作流配置文件 (§4) 定义的独立工作流之一，专门处理仅配置变更的场景。它遵循简化生命周期，专注于配置验证和发布路径决策分支。
+`release-config` 是工作流配置文件（§4）定义的独立工作流之一，专门处理仅配置变更场景。其遵循简化生命周期，专注于配置验证与发布路径决策分支。
 
-**机械实现**: `prepare --workflow config` 确定性地裁剪代码类门禁（H5），并比较当前
-per-unit `snapshotDigest` 与最新冻结 plan——公开字节未变 → `publishPath:
-'no-publish-needed'`（externalActions 被移除，无 publish 路径）；字节变化或无对比
-plan → `publishPath: 'publish-needed'`（fail-safe）。决策以 `workflowDecision` 绑定
-进 plan digest，不可篡改。**不存在** `NO_PUBLISH_NEEDED`/`REPORTED` 虚构状态：
-prepare 的真实输出是 plan 内的 `workflowDecision`。
+**机械实现**：`prepare --workflow config` 确定性地裁剪代码类门禁（H5），并比较当前 per-unit `snapshotDigest` 与最新冻结 plan——公开字节未变 → `publishPath: 'no-publish-needed'`（`externalActions` 被移除，无 publish 路径）；字节变化或无对比 plan → `publishPath: 'publish-needed'`（fail-safe）。决策以 `workflowDecision` 绑定进 plan digest，不可篡改。**不存在** `NO_PUBLISH_NEEDED`/`REPORTED` 虚构状态：prepare 的真实输出是 plan 内的 `workflowDecision`。
 
 **边界**：裁剪代码类检查（declared hooks、snapshot-verify gates、skill-resource-closure），保留基线、快照、计划冻结和文档新鲜度检查。来源权威检查按发布分支决定，不能一并裁掉：
 
-- 场景 A：公开字节未变，`externalActions=[]`，不生成 `plan.sourceAuthority`（冻结的源码来源权威），也不进入 approve/publish/verify。即使配置了公开来源收据，这一边界也不变。
-- 场景 B：公开字节变化或不可判定，需要发布。production prepare 必须通过现有来源权威检查并冻结 `plan.sourceAuthority`；publish、reconcile、verify 继续校验冻结绑定和远端一致性，consumer-verify 保留。
+- **场景 A**：公开字节未变，`externalActions=[]`，不生成 `plan.sourceAuthority`（冻结的源码来源权威），也不进入 approve/publish/verify。即使配置了公开来源收据，这一边界也不变。
+- **场景 B**：公开字节变化或不可判定，需要发布。production prepare 必须通过现有来源权威检查并冻结 `plan.sourceAuthority`；publish、reconcile、verify 继续校验冻结绑定和远端一致性，consumer-verify 保留。
 
 旧 production 计划缺少 `sourceAuthority` 时，仍在外部写入前拒绝。未发生外部写入的旧计划必须重新 prepare 并批准新摘要，不补字段、不迁移旧批准。已有 `PARTIAL` 保留检查点，走匹配版本的恢复路径。docs production 同样要求来源权威；marketplace 委托目标工作区发布的边界不变。
 
 ## 职责与边界
 
-- **步骤① diff 确认 config-only**: 调用 `release-skill route` command 确认仅有配置变更
-- **步骤② assess with schema validation**: 执行配置结构验证、schema 检查、contract 一致性
-- **步骤③ prepare --workflow config**: 本地 freeze 检查，生成只读计划；输出 `workflowDecision`
-- **步骤④ decision branch**（来自 plan.workflowDecision）:
-  - 场景 A：`publishPath === 'no-publish-needed'`（公开字节未变化）→ 记录决策并结束，
-    无 publish 路径，不运行 approve/publish/verify
-  - 场景 B：`publishPath === 'publish-needed'`（公开 surface 变化或不可判定）→ 运行
-    轻链 (approve→publish→verify)
+- **步骤① diff 确认 config-only**：调用 `release-skill route` 命令确认仅有配置变更
+- **步骤② assess with schema validation**：执行配置结构验证、schema 检查、contract 一致性
+- **步骤③ prepare --workflow config**：本地 freeze 检查，生成只读计划；输出 `workflowDecision`
+- **步骤④ decision branch**（来自 plan.workflowDecision）：
+  - **场景 A**：`publishPath === 'no-publish-needed'`（公开字节未变化）→ 记录决策并结束，无 publish 路径，不运行 approve/publish/verify
+  - **场景 B**：`publishPath === 'publish-needed'`（公开 surface 变化或不可判定）→ 运行轻链（approve→publish→verify）
 
 存量增量只改本轮目标映射。已有合法字段、历史发行记录与精确授权保持不变，不要重建 `.release-skill/project.yaml`。
 
@@ -44,25 +37,27 @@ prepare 的真实输出是 plan 内的 `workflowDecision`。
 
 `delivery.include/exclude` 不是文件包含或排除。排除不得覆盖 `requiredPublicFiles`。互相冲突的配置必须失败关闭。Foundation 建议不能作为发布批准。未经精确批准不产生远端动作。分类文字不会机械识别全部私有内容。接入评估缺失码 `REQUIRED_PUBLIC_FILE_MISSING` 不属于本技能的 prepare 路径；config-only prepare 仍走 `release-prepare` 原生错误。
 
-**授权边界**: 命令调用本身即授权执行配置的 hooks/gates。config-only 工作流的远程写操作受标准 approval 机制约束，不 bypass 安全 gate。
+**授权边界**：命令调用本身即授权执行配置的 hooks/gates。config-only 工作流的远程写操作受标准 approval 机制约束，不 bypass 安全 gate。
 
-**阶段通过规则**:
-- 场景 A: prepare 输出 `workflowDecision.decision === 'public-bytes-unchanged'`（无 publish 路径）
-- 场景 B: `status === 'VERIFIED'` + CLI exit code 0
+**接入选择**：进入本入口的新一轮生产准备前，必须按 `release-prepare` 同一完整流程核对 `testIntake`。若缺失，须说明缺项并默认推动 `skill-family-test:skill-family-test-plan`，再在授权范围内调用 `skill-family-test:skill-family-test-run`，由 TEST 组织检查并交回结果。跳过须先明确征询，再依据本轮适用且范围匹配的明确同意决定。**沉默、拒绝、仅普通发布预授权、旧轮次、其他项目、版本或范围不匹配均不可跳过**。本轮匹配答复可复用。**不得把跳过写成测试已达标，也不得用跳过清除已声明的适用要求**。已冻结计划的批准、发布、对账与正式验证不回头追加接入义务。只读和非生产准备不新增接入义务。直接非交互 CLI 仍接受可选 `testIntake`，不新增选择参数。答复与适用范围记入既有任务或执行计划。
+
+**阶段通过规则**：
+- **场景 A**：prepare 输出 `workflowDecision.decision === 'public-bytes-unchanged'`（无 publish 路径）
+- **场景 B**：`status === 'VERIFIED'` + CLI exit code 0
 
 ## 正向执行路径
 
-1. 运行 `release-skill route --root <path> [--target-version <ver>] --json` 获取 diff 分类；已知目标版本时显式传入，route 只是工作流建议
+1. 运行 `release-skill route --root <path> [--target-version <ver>] --json` 获取 diff 分类；已知目标版本时显式传入，`route` 只是工作流建议
 2. 若推荐 `workflowKind === 'config-only'`，则使用本技能
 3. 执行步骤②：运行 `release-skill assess --root <path> --offline --json` 进行 schema validation
-4. 执行步骤③：运行 `release-skill prepare --offline --workflow config --target-version <ver> --json`
-5. 读取输出中的 `workflowDecision`：
-   - **A**: `publishPath === 'no-publish-needed'` → 记录决策（plan 已冻结，无
-     externalActions），结束。无需 approve/publish/verify
-   - **B**: `publishPath === 'publish-needed'` → 继续 approve → publish → verify 链条
-6. (场景 B 续) 执行步骤⑥：运行 `release-skill approve --plan <path> --actor <name>`
-7. (场景 B 续) 执行步骤⑦：运行 `release-skill publish --plan <path> --approval <path>`
-8. (场景 B 续) 执行步骤⑧：运行 `release-skill verify --plan <path> --run <path>`
+4. 进入本入口新一轮生产准备前完成接入选择：按 `release-prepare` 同一完整流程核对 `testIntake`，默认推动 `skill-family-test:skill-family-test-plan` 与授权范围内的 `skill-family-test-run`。跳过须先明确征询再依据本轮匹配答复决定。未完成接入且无有效跳过时，不进入下一步 `prepare`。该分支只决定后续是否进入发布链，不改变生产 prepare 前的测试接入要求。
+5. 执行步骤③：运行 `release-skill prepare --offline --workflow config --target-version <ver> --json`
+6. 读取输出中的 `workflowDecision`：
+   - **A**：`publishPath === 'no-publish-needed'` → 记录决策（plan 已冻结，无 `externalActions`），结束。无需 approve/publish/verify
+   - **B**：`publishPath === 'publish-needed'` → 继续 approve → publish → verify 链条
+7. （场景 B 续）执行步骤⑥：运行 `release-skill approve --plan <path> --actor <name>`
+8. （场景 B 续）执行步骤⑦：运行 `release-skill publish --plan <path> --approval <path>`
+9. （场景 B 续）执行步骤⑧：运行 `release-skill verify --plan <path> --run <path> --json`
 
 ## 确定性脚本调用
 
@@ -135,21 +130,21 @@ node "${CLAUDE_PLUGIN_ROOT}/bin/release-skill.mjs" verify \
 
 ## 与其他工作流的关系
 
-- **docs-only**: 纯文档变更时使用 `release-docs`
-- **marketplace-only**: 仅 marketplace 变更时使用独立工作流
-- **full-happy-end**: 混合变更（code+config+docs）时降级到此完整路径
+- **docs-only**：纯文档变更时使用 `release-docs`
+- **marketplace-only**：仅 marketplace 变更时使用独立工作流
+- **full-happy-end**：混合变更（code+config+docs）时降级到此完整路径
 
 ## 关联技能
 
-- `release-skill route`: 快速入门决策路由（§4.3）
-- `release-assess`: 配置 schema/contract 验证入口
-- `release-prepare`: 离线冻结检查（`--workflow config` 输出 publish-path 决策）
-- `release-approve`: Plan approval（仅场景 B）
-- `release-publish`: 制品发布（仅在 public surface 变化时执行）
-- `release-verify`: 消费者验证（场景 B 的最终验证门）
+- `release-skill route`：快速入门决策路由（§4.3）
+- `release-assess`：配置 schema/contract 验证入口
+- `release-prepare`：离线冻结检查（`--workflow config` 输出 publish-path 决策）
+- `release-approve`：Plan approval（仅场景 B）
+- `release-publish`：制品发布（仅在 public surface 变化时执行）
+- `release-verify`：消费者验证（场景 B 的最终验证门）
 
 ## 人类最终回复
 
 纯问询或转交时短答：写明实际回答、适用范围或理由、必要限制和下一步。建议保持为建议。
 
-执行路径说明实际分支、已完成步骤、未执行步骤，以及既有计划、`workflowDecision` 产物和限制。`publishPath` 为 `no-publish-needed` 时按原合同结束，无发布路径。场景 B 只写入已经执行的 approve、publish、verify 结果。已有文件输出按原合同呈现。栏目只收录当前命令或分支已经返回的事实。
+执行路径说明实际分支、已完成步骤、未执行步骤，以及既有计划、`workflowDecision` 产物和限制。`publishPath` 为 `no-publish-needed` 时按原合同结束，无发布路径。场景 B 只写入已经执行的 approve、publish、verify 结果。已有文件输出按原合同呈现。栏目只收录当前命令或分支已经返回的事实。