release-skill 0.9.16 → 0.9.18

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.16 -->
+<!-- release-skill:release-version: 0.9.18 -->
 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,37 +14,40 @@ 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.16** (2026-09-09)
+**0.9.18** (2026-09-11)
 
-0.9.16 is a local source candidate that connects verified releases to explicit source-branch checks, host-aware setup continuation, and postVerify finish guidance. The three Foundation dependencies remain pinned to the exact 0.17.0 release. This note is not evidence of publication, real-host acceptance, consumer installation verification, or independent acceptance.
+0.9.18 is a local source candidate that adds first-class Cursor packaging, Foundation-backed host verification, and a final local distribution path for Claude, Codex, Kimi, CodeBuddy, WorkBuddy, Qoder, and Cursor. The three Foundation dependencies remain pinned to the exact 0.21.0 release. This note is not evidence of publication, real-host acceptance, consumer installation verification, or independent acceptance.
 
 **Security**
 
-- The source-branch reminder runs only `git branch --show-current` and `git status --short --branch`; it never fetches, switches, merges, rebases, stashes, resets, cleans, or pushes. Setup names are matched as skill metadata and are never executed as shell text.
-- Skill Family Hub updates bind the observed branch head with compare-and-swap semantics. Partial Hub publication is never rolled back or force-pushed, and remote state is never overwritten.
+- Cursor must be closed before its plugin tree is scanned or replaced. Failed upgrades preserve or restore a complete old or new directory instead of publishing a mixed tree.
+- Host verification receives only caller-declared roots and records mechanism observations separately from release-domain publication and verification state.
+- Hub publication remains a compare-and-swap operation. A partial Hub publication is never rolled back or force-pushed automatically.
 
 **Added**
 
-- Projects may configure `releaseFinish.sourceBranchCheck` as `remind` or `skip` and may name a loaded setup entry through `releaseFinish.setupSkill`. The release-finish workflow keeps the publishing workspace separate from an explicitly selected consumer project and reports setup as pending when the target directory, loaded plugin version, or callable host is not established.
-- Source checks use read-only Git commands and report the current branch, worktree changes, upstream summary, and any decision that still belongs to the maintainer. A project can select `release-setup` when it wants the release-finish workflow to continue into release-skill setup.
+- The npm package now includes `.cursor-plugin/plugin.json` and a self-contained `adapters/cursor/` projection with all release-skill Skills and runtime resources.
+- Release verification can invoke Foundation 0.21.0 host verification with explicit executable and user-state roots, including Cursor project-level plugin verification.
+- The final local updater can distribute the verified release to the declared Claude, Codex, Kimi, CodeBuddy, WorkBuddy, Qoder, and Cursor installations.
+- Skill Family Hub remains the central marketplace. Its release entry is published through the existing Git Data API after release verification.
 
 **Changed**
 
-- After a successful postVerify run reaches `DISTRIBUTED`, both JSON and text CLI output now expose the same Hub-backed local-host finish guidance used by the release-finish workflow. The guidance remains diagnostic and never invokes a host command on its own.
-- Host updates and setup checks remain local follow-up work and do not change the immutable release plan or the `VERIFIED` publication result. Shared project readiness may be checked once only when the plugin version, consumer directory, and runtime environment are the same; host-specific installation and loading remain separate checks.
-- Skill Family Hub publication continues through the project-private postVerify hook and GitHub Git Data API. The Hub update remains a separately approved compare-and-swap write against the observed branch head.
+- Local host updates verify the frozen snapshot and manifest identity before installation, and Cursor updates use Foundation fixed-set publication for first install and atomic full-directory replacement for upgrades.
+- Platform generation, public-file projection, package allowlists, schemas, and release-finish guidance now treat Cursor as a declared host and adapter.
 
 **Fixed**
 
-- A completed postVerify delivery now keeps `DISTRIBUTED` even when the optional finish checklist cannot reread its plan. The CLI returns an explicit unavailable diagnostic without rewriting the successful delivery checkpoint.
+- Cursor plugin names reject underscores so generated local plugin directories remain compatible with Cursor's manifest requirements.
+- The package's native prebuild allowlist and fixed resource-closure checks now include every generated adapter, including Cursor.
 
 **Upgrade Notes**
 
-Upgrade from 0.9.15 to receive postVerify finish guidance and optional source-branch and setup continuation. Add a top-level `releaseFinish` block only when the project wants to select a setup entry or change the default reminder policy. Remove any release-skill standalone marketplace registration, add or update `ifoohoo/skill-family-hub`, and use `release-skill@skill-family-hub`. Restart an updated host before treating the new plugin version or setup entry as loaded.
+Upgrade from 0.9.17 to obtain Cursor packaging and local installation, the Foundation-backed host verification bridge, and the unified seven-host local finish path. Remove the old release-skill standalone marketplace; use the ifoohoo/skill-family-hub repository and Hub-qualified plugin id release-skill@skill-family-hub. Reload each host after updating; an `UPDATED` filesystem result alone does not prove that the running host loaded the new version.
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **Current boundary:** v0.9.16 is the current source candidate. This README
+> **Current boundary:** v0.9.18 is the current source candidate. This README
 > records intended scope 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
@@ -68,7 +71,7 @@ Upgrade from 0.9.15 to receive postVerify finish guidance and optional source-br
 > publish global preflight.
 
 <!-- release-skill:capability:safe-first-command -->
-> **Production path verified since the v0.1.1 milestone; v0.9.16 is the current
+> **Production path verified since the v0.1.1 milestone; v0.9.18 is the current
 > source candidate. Its README does not establish publication,
 > consumer-installation verification, or independent acceptance.**
 > The npm-installed CLI is the supported user entry. Source checkout
@@ -97,19 +100,22 @@ checkpoints remain intact and use matching-version recovery. Evidence v1 stays
 read-only; v2 uses a closed top level with phase extensions in `details`.
 Summaries and recovery suggestions are diagnostic, never publication authority.
 
-The current 0.9.16 candidate includes the narrow R-05 Hook cache v2 consumer
+The current 0.9.18 candidate includes the narrow R-05 Hook cache v2 consumer
 path, the public `postverify` path, and the stable isolated install-tree record
-path (A2/A3). It keeps Skill Family Hub as the single marketplace source. It
+path (A2/A3). It also adds the explicit-input `verify-records` command and a
+self-contained Qoder projection, first-class Cursor packaging, and the
+Foundation-backed host verification bridge. Skill Family Hub remains the single
+marketplace source. The candidate
 also makes the `release-prepare` Skill organize existing assessment, refresh,
 focused-check, and prepare entry points without adding another execution
 engine. `prepare --help` and `prepare -h` now return before configuration,
 locks, runs, or hooks can observe the request. The `release-finish` Skill can
 also report the source branch and continue into a configured setup entry after
-the selected host has loaded the released plugin. This candidate still
-excludes R-02 safe full-tree inventory, R-10 historical-release verification
-implementation, real Kimi/WorkBuddy public-marketplace installation and
-invocation gates, and an Audit public offline release-record verifier.
-Foundation dependencies are pinned to the three released 0.17.0 packages.
+the selected host has loaded the released plugin. This candidate still excludes
+R-02 safe full-tree inventory. Marketplace installation and live invocation
+remain host-level post-release checks; Cursor is distributed through its
+supported local-plugin directory rather than a Hub marketplace entry.
+Foundation dependencies are pinned to the three released 0.21.0 packages.
 For Kimi/CodeBuddy plans that still use the bundled-family distribution form,
 verify calls the released
 `runPluginVerification` entry with the complete frozen payload and records a
@@ -267,7 +273,35 @@ Skill Family Hub marketplace:
 Kimi Code. It uses the version-pinned interactive TUI path described in
 [INSTALL.md](INSTALL.md#install-as-a-kimi-code-plugin).
 
-See [INSTALL.md](INSTALL.md) for CodeBuddy, Codex, and Kimi Code commands.
+**Qoder:** the package ships `.qoder-plugin/plugin.json` and the self-contained
+`adapters/qoder/` projection. A user-scope marketplace install is available only
+after the central Hub's root `marketplace.json` has accepted the release-skill
+Qoder entry; the generated adapter alone does not prove Hub consumption. See
+[INSTALL.md](INSTALL.md#install-as-a-qoder-plugin) for the bounded install and
+post-release update contract.
+
+**Cursor:** `adapters/cursor/` is a complete Local plugin. After release verification,
+`release-finish` can install or atomically upgrade its frozen tree on macOS while
+Cursor is closed. It requires an explicit `--cursor-plugins-root` and preserves
+the displaced version outside `local/`. Restart and real Skill invocation remain
+separate checks. See [the Cursor instructions](INSTALL.md#install-as-a-cursor-local-plugin).
+
+See [INSTALL.md](INSTALL.md) for CodeBuddy, Codex, Kimi Code, Qoder, and Cursor commands.
+
+### Offline historical record verification
+
+Use the public command below when a consumer already has an explicit plan,
+approval, target run, and every predecessor run referenced by that target:
+
+```text
+release-skill verify-records --plan <path> --approval <path> --target-run <path> --source-run <path>... --unit <id> --target-version <version> --json
+```
+
+The command reads only those paths and emits one JSON object. `CONSISTENT`
+exits 0, `CONTRADICTED` exits 1, and `INSUFFICIENT` exits 2. It does not scan
+`.release-skill`, follow paths embedded in a record, contact a remote, write a
+file, or advance release state. A consistent historical chain does not prove
+that its records are globally latest or that remote objects still exist.
 
 ### Main workflow
 
@@ -539,7 +573,9 @@ releaseUnits:
 defaults to `remind`; set it to `skip` to suppress the read-only source-branch
 reminder. `setupSkill` is optional and names an already installed and loaded
 setup entry such as `release-setup` or `plugin:skill`; it is never executed as
-a shell command. The two settings are independent.
+a shell command. After host updates, release-finish runs that setup entry
+against the current release project root passed through `--root`; it does not
+request a separate project directory. The two settings are independent.
 
 `distributions` is required but may be an explicit empty array. Use
 `distributions: []` when release-skill should publish only the unit's GitHub
@@ -782,6 +818,11 @@ closures. A release unit declares what reaches users via `distributions`:
 | `kimi-plugin` | self-contained closure (release-skill invokes 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 |
 
+Qoder is intentionally outside this `distributions` table: it is a build-only
+public projection at `adapters/qoder/`, with root manifest
+`.qoder-plugin/plugin.json`. It does not add a `qoder-plugin` plan type or an
+automated publish, reconcile, or verify checkpoint.
+
 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
@@ -796,12 +837,23 @@ commit before that host's first write; a failed check leaves that host unchanged
 without stopping other selected hosts. The workflow can also migrate or update
 Kimi through one controlled TUI session and verify its real managed payload, or update an existing
 bundled-family CodeBuddy/WorkBuddy entry when the frozen tag and mutable branch
-both resolve to the frozen commit. It requires explicit user confirmation and
+both resolve to the frozen commit. For an explicitly selected Qoder host, it can
+update only an existing user-scope installation after proving the configured Hub
+source and frozen payload; it never adds a marketplace or performs first install.
+An `UPDATED` installation is not treated as loaded: reload or start a new Qoder
+session, then complete one read-only release-skill business call before claiming
+the new version is active. It requires explicit user confirmation and
 does not change release status. Kimi uses one effective configuration root:
 explicit `kimiHome`, then `KIMI_CODE_HOME`, then `~/.kimi-code`. The TUI and
-post-operation observation share that root. A `Trust this folder?` prompt,
-unknown interface, timeout, early exit, or unprovable plugin identity returns a
-manual or failed result without confirming folder trust. Missing, standalone, inaccessible, or ambiguous
+post-operation observation share that root, and the TUI working directory is the
+resolved release project root passed through `--root`. After the user confirms
+the frozen plan and explicitly selects Kimi for update, release-finish accepts
+only the initial standard `Trust this folder?` dialog with `No, exit` selected
+and `Trust this folder` available. It moves to that target, verifies the new
+selection, confirms it, and waits for the known command prompt before sending
+the plugin command. An unknown row or selection, a failed move, timeout, early
+exit, or any folder-trust dialog after the plugin command fails closed. The
+frozen plugin identity and `Trust and install` checks remain unchanged. Missing, standalone, inaccessible, or ambiguous
 CodeBuddy/WorkBuddy targets remain manual and receive no host mutation.
 WorkBuddy local updates are macOS-only; on other platforms they are skipped as
 unsupported. When a plan declares postVerify hooks, release-finish must receive
@@ -812,8 +864,10 @@ A release unit may also declare `postPublish.localHostUpdate` for a plugin that
 is delivered through a project-selected Hub by a `postVerify` hook. After that
 hook reaches `DISTRIBUTED`, `ship`, `verify`, `post-release`, and
 `release-finish` display the declared Hub, plugin, and hosts. These Hub-backed
-targets are manual in 0.9.16 (`promptRequired: true`, `available: false`): the
-prompt does not query the Hub, inspect the host, or run host commands. Claude
+targets retain their declared execution mode. Qoder is executable only when it
+was selected and all frozen-plan, Hub-source, existing user-scope installation,
+and payload checks pass; other Hub-backed targets remain manual. Manual prompts
+do not query the Hub, inspect the host, or run host commands. Claude
 and Codex use their existing marketplace management entry; Kimi uses the
 frozen GitHub Release and its existing confirmation path; CodeBuddy and
 WorkBuddy remain manual because this flow cannot pin a Hub ref. Existing
@@ -844,7 +898,7 @@ the first minimal semantic boundary, so the static gate fails closed until the
 declaration is narrowed to concrete targets.
 
 <!-- release-skill:capability:unsupported-scope -->
-- **not in the current version:** full consumer install-tree scanning (R-02) — the current implementation handles only the declared public surface and the stable isolated install-tree record; and a real-host (Kimi/WorkBuddy) verification gate — host verification stays a non-blocking manual follow-up and does not produce `PASS`/`VERIFIED` evidence;
+- **not in the current version:** full consumer install-tree scanning (R-02) — the current implementation handles only the declared public surface and the stable isolated install-tree record; and a real-host (Kimi/WorkBuddy/Qoder) verification gate — host verification and Qoder activation stay outside release `PASS`/`VERIFIED` evidence;
 - no automatic README generation or source-file overwrite;
 - no automatic conflict merge or rollback workflow;
 - no claim that a real production canary has run for marketplace verification;
@@ -853,10 +907,11 @@ 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 Kimi or CodeBuddy/WorkBuddy marketplace install checkpoint in the release
+- no Kimi, CodeBuddy/WorkBuddy, or Qoder marketplace install checkpoint in the release
   state machine — optional release-finish can drive and re-check Kimi locally,
   or update an existing CodeBuddy/WorkBuddy entry under strict frozen-identity
-  checks, but those results do not become publication evidence;
+  checks, or update an existing user-scope Qoder entry after equivalent source
+  and payload checks, but those results do not become publication evidence;
 - no promise of Windows or broad multi-platform native write support;
 - no hidden commit, push, tag, release, or package publication.
 

package/README.zh-CN.md

@@ -2,43 +2,46 @@
 
 [English](README.md) · 安装指南：[中文](INSTALL.zh-CN.md) / [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.9.16 -->
+<!-- release-skill:release-version: 0.9.18 -->
 面向 Claude Code、CodeBuddy、WorkBuddy、Codex 和 Kimi Code 的发布准备工具，完整保留人工维护的文件内容。
 
 release-skill 帮助维护者回答三个问题：准备发布什么、还有哪些检查未通过、最终发布的内容是什么。它不重新生成、也不回写项目源文件。`prepare` 把每个配置的公开文件复制到隔离快照并验证字节——先冻结并供人工审阅，再从同一份冻结产物发布。`setup` 只显示确定性的 `compactSummary` 审阅视图，完整报告保留在临时会话目录中。
 
 <!-- release-skill:managed:start id=latest-release -->
-**0.9.16** (2026-09-09)
+**0.9.18** (2026-09-11)
 
-0.9.16 是把已验证发布衔接到显式源码分支检查、宿主感知 setup 续接和 postVerify 收尾提示的本地源码候选。三项 Foundation 依赖仍精确固定在已发布的 0.17.0。本说明不代表已经发布、完成真实宿主验收、完成消费者安装验证或通过独立验收。
+0.9.18 是一个本地源码候选。本版本增加 Cursor 的正式打包与分发、基于 Foundation 的宿主核验，以及覆盖 Claude、Codex、Kimi、CodeBuddy、WorkBuddy、Qoder 和 Cursor 的最终本机分发路径。三项 Foundation 依赖继续精确固定在已发布的 0.21.0。本说明不代表已经发布、完成真实宿主验收、完成消费者安装验证或通过独立验收。
 
 **安全**
 
-- 源码分支提醒只运行 `git branch --show-current` 和 `git status --short --branch`，不会 fetch、切换、合并、rebase、stash、reset、clean 或 push。setup 名只作为技能元数据匹配，不会按 shell 文本执行。
-- Skill Family Hub 更新以已观察的分支头为基础比较后写入。Hub 局部发布不回滚、不覆盖，也不强推。
+- 扫描或替换 Cursor 插件树前必须关闭 Cursor。升级失败时保留或恢复完整的旧目录或新目录，不会发布混合目录。
+- 宿主核验只接收调用方声明的根目录，并把机制观察结果与 release-skill 的发布、验证状态分别记录。
+- Hub 发布继续绑定已观察的分支头执行比较后写入。部分发布时不回滚、不覆盖已经成功的远端步骤。
 
 **新增**
 
-- 项目可以把 `releaseFinish.sourceBranchCheck` 配置为 `remind` 或 `skip`，并通过 `releaseFinish.setupSkill` 指定已加载的 setup 入口。release-finish 会区分发布工作区和用户明确选择的消费项目；目标目录、新版插件加载状态或可调用宿主不能确认时，只报告 setup 待执行。
-- 源码检查只运行只读 Git 命令，报告当前分支、工作区改动、上游摘要，以及仍需维护者决定的事项。项目需要让 release-finish 继续进入 release-skill setup 时，可以选择 `release-setup`。
+- npm 包新增 `.cursor-plugin/plugin.json` 和自包含的 `adapters/cursor/` 投影，包含 release-skill 的全部 Skill 与运行资源。
+- 发布验证可通过显式的可执行文件根目录和用户状态根目录调用 Foundation 0.21.0 宿主核验，其中包括 Cursor 项目级插件核验。
+- 最终本机更新入口可以把已验证版本分发到声明的 Claude、Codex、Kimi、CodeBuddy、WorkBuddy、Qoder 和 Cursor 安装位置。
+- Skill Family Hub 继续作为中央市场。发布完成验证后，release-skill 通过既有 GitHub Git Data API 更新 Hub 条目。
 
 **变更**
 
-- postVerify 成功进入 `DISTRIBUTED` 后，JSON 和文本 CLI 输出都会显示与 release-finish 一致的 Hub-backed 本机宿主收尾提示。提示只用于诊断，不会自行调用宿主命令。
-- 宿主更新和 setup 检查仍属于本地后续工作，不改写不可变发布计划，也不改变 `VERIFIED` 发布结果。只有插件版本、消费目录和运行环境都相同时，才可复用一次项目就绪检查；各宿主仍分别检查安装与加载状态。
-- Skill Family Hub 继续通过项目私有的 postVerify hook 和 GitHub Git Data API 发布。Hub 更新仍需单独批准，并根据已观察的分支头比较后写入。
+- 本机宿主更新会先核对冻结快照、manifest 身份和版本。Cursor 首次安装使用 Foundation 固定集合发布，升级使用整个目录的原子替换。
+- 平台生成、公开文件投影、包内容许可清单、Schema 与 release-finish 指引现在统一把 Cursor 视为正式宿主和适配器。
 
 **修复**
 
-- postVerify 已完成分发后，即使可选收尾清单无法重新读取计划，也会保留 `DISTRIBUTED`。CLI 会返回明确的不可用诊断，不会改写已成功的分发检查点。
+- Cursor 插件名不再接受下划线，生成的本机插件目录符合 Cursor manifest 的名称约束。
+- npm 包原生预构建许可清单和固定资源闭包检查现已覆盖包括 Cursor 在内的全部生成适配器。
 
 **升级说明**
 
-从 0.9.15 升级后，可获得 postVerify 收尾提示，以及可选的源码分支与 setup 续接。只有需要指定 setup 入口或修改默认提醒策略时，才增加顶层 `releaseFinish` 配置。删除各宿主中独立的 `release-skill` 市场登记，添加或更新 `ifoohoo/skill-family-hub`，并使用 `release-skill@skill-family-hub`。宿主更新后需先重启，才能把新版插件或 setup 入口视为已加载。
+从 0.9.17 升级后，可获得 Cursor 打包与本机安装、基于 Foundation 的宿主核验桥，以及统一的七宿主本机收尾路径。请移除独立的 `release-skill` 市场，改用 ifoohoo/skill-family-hub 仓库与 Hub 限定插件名 release-skill@skill-family-hub。更新后仍需重新加载各宿主；文件系统返回 `UPDATED` 并不单独证明运行中的宿主已经加载新版。
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **当前边界：** v0.9.16 只是当前源码候选。本 README 记录预期范围与验证边界，
+> **当前边界：** v0.9.18 只是当前源码候选。本 README 记录预期范围与验证边界，
 > 不代表已经发布、完成消费者安装验证或通过独立验收。
 > 版本可用性以对应发布记录及发布后验证结果为准。
 > v0.4.1 是更早的已发布里程碑（v0.2.2 曾处于已发布状态，后因平台验证收敛修复而更新）。
@@ -54,7 +57,7 @@ release-skill 帮助维护者回答三个问题：准备发布什么、还有哪
 > 远端唯一性检查在 `publish` 全局预检执行。
 
 <!-- release-skill:capability:safe-first-command -->
-> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.9.16 是当前源码候选，本 README 不证明该候选已经发布、完成消费者安装验证或通过独立验收。**
+> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.9.18 是当前源码候选，本 README 不证明该候选已经发布、完成消费者安装验证或通过独立验收。**
 > npm 安装的 CLI 是受支持的用户入口；源码 checkout 保留为开发/贡献者路径。
 >
 > **第一条命令：**
@@ -72,16 +75,17 @@ marketplace 委托目标工作区发布的边界不变。
 
 旧 production 计划缺少 `sourceAuthority` 时，在外部写入前拒绝。未发生外部写入的计划必须重新 prepare 并批准新摘要，不能补写旧计划或迁移批准。已有 `PARTIAL` 保留检查点，走匹配版本的恢复路径。evidence v1 只读；v2 顶层封闭，阶段扩展放在 `details`。摘要和恢复建议只作诊断，不构成发布权威。
 
-当前 0.9.16 候选包含窄范围的 R-05 Hook cache v2 消费路径、公开 `postverify`
-路径和稳定隔离安装树记录路径（A2/A3），继续以 Skill Family Hub 为唯一市场来源。
+当前 0.9.18 候选包含窄范围的 R-05 Hook cache v2 消费路径、公开 `postverify`
+路径和稳定隔离安装树记录路径（A2/A3），并增加只接受显式输入的 `verify-records`
+命令、自包含 Qoder 投影、Cursor 正式打包，以及基于 Foundation 的宿主核验桥。
+Skill Family Hub 仍是唯一市场来源。
 `release-prepare` Skill 现在会组织项目已有的评估、刷新、聚焦检查和 prepare 入口，不新增执行引擎。
 `prepare --help` 和 `prepare -h` 会在配置、锁、run 或 Hook 观察请求之前返回。
-所选宿主加载已发布插件后，`release-finish` Skill 还可以报告源码分支，并继续执行已配置的 setup 入口。当前仍不包含
-R-02 安全整树盘点、R-10 历史发布验证
-的产品实现、真实 Kimi/WorkBuddy 公开市场安装与调用门禁或 Audit 公开离线发布记录
-验证器。本范围说明不构成远端发布记录或消费者升级指引。
+所选宿主加载已发布插件后，`release-finish` Skill 还可以报告源码分支，并继续执行已配置的 setup 入口。
+当前仍不包含 R-02 安全整树盘点。市场安装与真实调用继续作为各宿主的发布后检查；Cursor
+通过其支持的本机插件目录分发，不进入 Hub 市场条目。本范围说明不构成远端发布记录或消费者升级指引。
 
-Foundation 三包精确依赖已发布的 0.17.0。仍采用 bundled-family 分发形态的
+Foundation 三包精确依赖已发布的 0.21.0。仍采用 bundled-family 分发形态的
 Kimi/CodeBuddy 计划会在 verify 阶段调用正式 `runPluginVerification`，把完整冻结载荷
 交给 Foundation，并记录最小的 `install-only` 观察收据。Kimi 映射为 `kimi-code`，
 CodeBuddy 映射为兼容的 `workbuddy`。`observed` 与 `payloadMatches` 只表示机制观察结果，
@@ -218,7 +222,30 @@ Claude Code、CodeBuddy、WorkBuddy 和 Codex 从统一的 Skill Family Hub 市
 **Kimi Code：** release-skill 当前无可脚本化安装接口接入，只采用钉死版本的交互式
 TUI 路径，见 [INSTALL.zh-CN.md](INSTALL.zh-CN.md#安装为-kimi-code-插件)。
 
-CodeBuddy、Codex 和 Kimi Code 的完整命令见 [INSTALL.zh-CN.md](INSTALL.zh-CN.md)。
+**Qoder：** 包内提供 `.qoder-plugin/plugin.json` 和自包含的 `adapters/qoder/` 投影。
+只有中央 Hub 的根 `marketplace.json` 已接纳 release-skill 的 Qoder 条目后，才能执行
+用户范围的市场安装；生成适配器本身不能证明 Hub 消费成立。安装与发布后更新边界见
+[INSTALL.zh-CN.md](INSTALL.zh-CN.md#安装为-qoder-插件)。
+
+**Cursor：** `adapters/cursor/` 是完整的 Local（本地）插件。发布验证完成后，
+`release-finish` 可在 macOS 上安装或整体原子升级冻结插件，操作前必须退出 Cursor，
+并显式传入 `--cursor-plugins-root`。旧版保存在 `local/` 外；重启后的加载和技能调用
+另行验证。操作说明见[Cursor 本地插件安装](INSTALL.zh-CN.md#安装为-cursor-本地插件)。
+
+CodeBuddy、Codex、Kimi Code、Qoder 和 Cursor 的完整命令见 [INSTALL.zh-CN.md](INSTALL.zh-CN.md)。
+
+### 离线核验历史发布记录
+
+消费者已经持有明确的计划、批准、目标 run 和该目标引用的全部前驱 run 时，可以运行：
+
+```text
+release-skill verify-records --plan <path> --approval <path> --target-run <path> --source-run <path>... --unit <id> --target-version <version> --json
+```
+
+该命令只读取这些路径，并输出一个 JSON 对象。`CONSISTENT` 的退出码是 0，
+`CONTRADICTED` 的退出码是 1，`INSUFFICIENT` 的退出码是 2。它不会扫描
+`.release-skill`、跟随记录内嵌路径、访问远端、写文件或推进发布状态。历史链一致也不能
+证明这些记录是全局最新，或远端对象仍然存在。
 
 ### 主流程
 
@@ -455,7 +482,9 @@ releaseUnits:
 
 `releaseFinish` 只控制本地发布收尾。`sourceBranchCheck` 缺省为 `remind`；设为
 `skip` 时关闭只读源码分支提醒。`setupSkill` 可省略，填写时指定已经安装并加载的 setup
-入口，例如 `release-setup` 或 `plugin:skill`；它不会作为 shell 命令执行。两个配置彼此独立。
+入口，例如 `release-setup` 或 `plugin:skill`；它不会作为 shell 命令执行。宿主更新后，
+release-finish 在 `--root` 指定的当前发布项目根目录调用该入口，不再要求另行提供项目目录。
+两个配置彼此独立。
 
 `distributions` 是必填字段，但可以显式设为空数组。使用
 `distributions: []` 时，release-skill 只发布该单元的 GitHub 快照、标签和
@@ -670,6 +699,10 @@ release-skill ship --root "$PROJECT" --hook-approval "$HOOK_APPROVAL_PATH" --jso
 | `kimi-plugin` | 自包含闭包（release-skill 无可脚本化安装接口接入） | 发布后非阻塞人工任务 |
 | `codebuddy-plugin` | 生成的 `adapters/workbuddy/`，带 `.codebuddy-plugin/plugin.json` | 发布后非阻塞人工任务 |
 
+Qoder 不属于上表的 `distributions` 类型。它是 `adapters/qoder/` 下的 build-only
+公开投影，根清单为 `.qoder-plugin/plugin.json`；发布计划不会因此新增 `qoder-plugin`
+类型，也不会新增自动 publish、reconcile 或 verify 检查点。
+
 每个适配器闭包都自带 CLI、skills 和 schemas 副本，安装后无需外部依赖即可运行。Claude/Codex 验证是自动化的；Kimi Code 和 CodeBuddy/WorkBuddy 以 `manualFollowUps` 返回并标记 `verifiedBySystem: false`，其完成情况不阻塞自动发布进入 `VERIFIED`。
 
 发布达到 `VERIFIED` 后，可选的 `release-finish` 工作流可以按冻结市场身份更新 Claude
@@ -677,11 +710,18 @@ release-skill ship --root "$PROJECT" --hook-approval "$HOOK_APPROVAL_PATH" --jso
 提交；预检失败时不修改该宿主，也不阻止其他已选宿主继续。流程也可以在同一个受控
 TUI 会话中迁移或更新 Kimi，并核对真实受管载荷。
 对于已有的 bundled-family CodeBuddy/WorkBuddy 条目，只有冻结标签与可变分支都解析到
-冻结提交时才允许更新。该流程要求用户明确同意，且不改变发布状态。目标缺失、使用
+冻结提交时才允许更新。用户显式选择 Qoder 后，流程只有在确认 Hub 来源、冻结载荷和
+既有用户范围安装后才更新；它不会添加市场，也不会执行首次安装。安装结果为 `UPDATED`
+不等于新版已加载：必须重新加载或新开 Qoder 会话，再完成一次只读 release-skill 业务
+调用，才能宣称新版已生效。该流程要求用户明确同意，且不改变发布状态。目标缺失、使用
 standalone 来源、远端不可访问或身份含糊时仍转人工处理，不修改宿主。
 Kimi 的有效配置根依次取显式 `kimiHome`、`KIMI_CODE_HOME`、`~/.kimi-code`，TUI 与
-操作后观察使用同一根。出现 `Trust this folder?`、未知界面、超时、提前退出，或无法
-证明插件身份时，流程返回人工处理或失败结果，不确认目录信任。
+操作后观察使用同一根，TUI 工作目录固定为 `--root` 指定的当前发布项目。用户确认冻结
+计划并显式选择更新 Kimi 后，release-finish 只接受初始标准 `Trust this folder?` 界面：
+当前必须选中 `No, exit`，且存在 `Trust this folder` 目标行。流程移动到目标行，重新确认
+选中项，再提交并等待已知命令提示符。出现未知行或选中项、移动后无法确认、超时、提前
+退出，或者插件命令发出后再次出现目录信任时，该宿主失败并停止。冻结插件身份和
+`Trust and install` 的核对保持不变。
 WorkBuddy 本机更新仅支持 macOS；其他平台返回不支持并跳过。计划声明 postVerify hook 时，
 release-finish 必须接收 `ship` 产出的已完成 postVerify run，不能直接使用较早的
 verify run；核心 prepare、publish、verify 流程仍跨平台。
@@ -689,8 +729,9 @@ verify run；核心 prepare、publish、verify 流程仍跨平台。
 如果插件由项目选定的 Hub 通过 `postVerify` Hook 交付，发布单元还可以声明
 `postPublish.localHostUpdate`。Hook 达到 `DISTRIBUTED` 后，`ship`、`verify`、
 `post-release` 和 `release-finish` 会显示声明中的 Hub、插件和宿主。0.9.14 对这类
-目标只提供人工入口（`promptRequired: true`、`available: false`）：提示不会访问 Hub、
-探测宿主或运行宿主命令。Claude 和 Codex 使用各自已有的 marketplace 管理入口；Kimi
+目标保留各自声明的执行模式。只有用户已选择 Qoder，且冻结计划、Hub 来源、既有用户
+范围安装和载荷核对全部通过时，Qoder 才进入可执行分支；其他 Hub-backed 目标仍为人工
+入口。人工提示不会访问 Hub、探测宿主或运行宿主命令。Claude 和 Codex 使用各自已有的 marketplace 管理入口；Kimi
 使用冻结 GitHub Release 和现有人工确认路径；CodeBuddy 与 WorkBuddy 因无法固定 Hub
 ref 而继续人工处理。由冻结插件安装动作派生的原有可执行目标不受影响。
 
@@ -709,13 +750,13 @@ ref 而继续人工处理。由冻结插件安装动作派生的原有可执行
 静态门禁会阻断，直到入口声明收窄为具体目标。
 
 <!-- release-skill:capability:unsupported-scope -->
-- **当前版本不含：** 消费者安装整树盘点（R-02）——当前版本只处理声明的公开表面和稳定隔离安装树记录；真实宿主（Kimi/WorkBuddy）验证门禁——宿主验证仍是非阻断的人工后续任务，不产生 `PASS` 或 `VERIFIED` 证据；
+- **当前版本不含：** 消费者安装整树盘点（R-02）——当前版本只处理声明的公开表面和稳定隔离安装树记录；真实宿主（Kimi/WorkBuddy/Qoder）验证门禁——宿主验证和 Qoder 加载确认均不产生发布 `PASS` 或 `VERIFIED` 证据；
 - 不自动生成 README，不覆盖项目源文件；
 - 不自动合并冲突，也不要求回滚工作流；
 - 不声称已经替项目完成真实生产 canary，不声称已完成真实插件市场验证；
 - `prepare --online` 只观察 bound 前序基线；目标唯一性由 publish 全局预检完成；
 - 不覆盖已有 branch/tag/Release，不 unpublish npm；
-- 发布状态机不提供 Kimi 或 CodeBuddy/WorkBuddy marketplace 安装检查点——可选的 release-finish 可以在本机驱动并复查 Kimi，也可以在严格核对冻结身份后更新已有 CodeBuddy/WorkBuddy 条目，但这些结果不构成发布证据；
+- 发布状态机不提供 Kimi、CodeBuddy/WorkBuddy 或 Qoder marketplace 安装检查点——可选的 release-finish 可以在本机驱动并复查 Kimi，也可以在严格核对冻结身份后更新已有 CodeBuddy/WorkBuddy 条目，或在核对同等来源和载荷后更新已有的用户范围 Qoder 条目，但这些结果不构成发布证据；
 - 不承诺 Windows 或广泛的跨平台原生写入；
 - 不会隐藏地 commit、push、打 tag、创建 Release 或发布包。
 

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

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

package/adapters/claude/bin/consumer-contract-vectors.json

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 1,
   "kind": "skill-family.contracts.consumer-contract-vectors",
-  "foundationVersion": "0.17.0",
+  "foundationVersion": "0.21.0",
   "sets": [
     {
       "capabilityId": "foundation.contracts.object-validation",
@@ -15,7 +15,7 @@
           "vectorId": "foundation.contracts.object-validation.consumer-v1.indeterminate",
           "vectorSetId": "foundation.contracts.object-validation.consumer-v1",
           "capabilityId": "foundation.contracts.object-validation",
-          "foundationVersion": "0.17.0",
+          "foundationVersion": "0.21.0",
           "contractId": "skill-family-contracts:validateDocument",
           "caseClass": "indeterminate",
           "strategy": "real-pure",
@@ -31,7 +31,7 @@
           "vectorId": "foundation.contracts.object-validation.consumer-v1.negative",
           "vectorSetId": "foundation.contracts.object-validation.consumer-v1",
           "capabilityId": "foundation.contracts.object-validation",
-          "foundationVersion": "0.17.0",
+          "foundationVersion": "0.21.0",
           "contractId": "skill-family-contracts:validateDocument",
           "caseClass": "negative",
           "strategy": "real-pure",
@@ -47,7 +47,7 @@
           "vectorId": "foundation.contracts.object-validation.consumer-v1.positive",
           "vectorSetId": "foundation.contracts.object-validation.consumer-v1",
           "capabilityId": "foundation.contracts.object-validation",
-          "foundationVersion": "0.17.0",
+          "foundationVersion": "0.21.0",
           "contractId": "skill-family-contracts:validateDocument",
           "caseClass": "positive",
           "strategy": "real-pure",
@@ -71,7 +71,7 @@
           "vectorId": "foundation.harness.atomic-write.consumer-v1.indeterminate",
           "vectorSetId": "foundation.harness.atomic-write.consumer-v1",
           "capabilityId": "foundation.harness.atomic-write",
-          "foundationVersion": "0.17.0",
+          "foundationVersion": "0.21.0",
           "contractId": "skill-family-harness-node:writeFileAtomic",
           "caseClass": "indeterminate",
           "strategy": "official-fake",
@@ -84,7 +84,7 @@
           "vectorId": "foundation.harness.atomic-write.consumer-v1.negative",
           "vectorSetId": "foundation.harness.atomic-write.consumer-v1",
           "capabilityId": "foundation.harness.atomic-write",
-          "foundationVersion": "0.17.0",
+          "foundationVersion": "0.21.0",
           "contractId": "skill-family-harness-node:writeFileAtomic",
           "caseClass": "negative",
           "strategy": "official-fake",
@@ -97,7 +97,7 @@
           "vectorId": "foundation.harness.atomic-write.consumer-v1.positive",
           "vectorSetId": "foundation.harness.atomic-write.consumer-v1",
           "capabilityId": "foundation.harness.atomic-write",
-          "foundationVersion": "0.17.0",
+          "foundationVersion": "0.21.0",
           "contractId": "skill-family-harness-node:writeFileAtomic",
           "caseClass": "positive",
           "strategy": "official-fake",

package/adapters/claude/bin/error-codes.json

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 1,
   "kind": "skill-family.contracts.error-codes",
-  "contractsVersion": "1.16.0",
+  "contractsVersion": "1.18.0",
   "policy": {
     "format": "^SFC[0-9]{4}$",
     "ranges": [