release-skill 0.9.17 → 0.9.19

package/.claude-plugin/plugin.json

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

package/.cursor-plugin/plugin.json

@@ -0,0 +1,10 @@
+{
+  "name": "release-skill",
+  "version": "0.9.19",
+  "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
+  "author": {
+    "name": "广州市风荷科技有限公司"
+  },
+  "license": "Apache-2.0",
+  "skills": "./adapters/cursor/skills/"
+}

package/.kimi-plugin/plugin.json

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

package/CHANGELOG.md

@@ -1,9 +1,77 @@
 # Changelog
 
-<!-- release-skill:changelog:start version=0.9.17 locale=en baseline=sha256:83fe967a104a1b324ea1b704cfc6ee67d6a2999f3d6c0e2d92411435fa6986a2 -->
+<!-- release-skill:changelog:start version=0.9.19 locale=en baseline=sha256:e0f2dd2aca0b1ca36bb2a95feded3fb291e176c31357f8ba2d390bed4a10184f -->
+## [0.9.19] - 2026-09-14
+
+0.9.19 is a local source candidate that completes the verified-release workflow with a deterministic local finish orchestrator. After publication and postVerify, maintainers can use one public entry to select the source branch outcome, update supported hosts, confirm that each host loaded the target plugin, run the configured setup Skill, and verify the source workspace without changing the release status. 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
+
+- Finish feedback is bound to the current plugin version, project root, selected host, request identity, and execution environment; changing an update decision invalidates earlier setup evidence.
+- No host is considered loaded from filesystem installation alone, and no configured setup is considered complete until its real result is returned through the bound feedback contract.
+- Hub publication remains a compare-and-swap operation. A partial Hub publication is never rolled back or force-pushed automatically.
+
+### Added
+
+- The local finish entry now accepts `--finish` and emits an ordered plan for branch handling, host updates, load confirmation, configured setup execution, and final source checks.
+- Bound feedback can resume the same finish operation after real host loading and setup execution; JSON and text output expose the same pending, blocked, and complete decisions.
+- The release-finish Skill documents the end-to-end VERIFIED-to-COMPLETE handoff, including the exact request and feedback boundaries used by an agent.
+
+### Changed
+
+- Finish completion is now separate from the release lifecycle: a successful local finish preserves VERIFIED and reports `releaseStatusChanged: false`.
+- The release help entry is shorter and routes specialized publishing, verification, documentation, marketplace, and finish details to their owning Skills.
+- Skill Family Hub remains the central marketplace, and its release entry continues to use the existing GitHub Git Data API after release verification.
+
+### Fixed
+
+- Ambiguous setup-plugin selection, missing host candidates, stale setup feedback, and incomplete next-action lists now fail closed instead of producing a false COMPLETE result.
+- Read-only Git observations disable optional index locking and retain exact argv, exit code, stdout, and stderr when a command fails.
+
+### Upgrade Notes
+
+Upgrade from 0.9.18 to use the new `post-release --finish` orchestration. Remove the old release-skill standalone marketplace; use the ifoohoo/skill-family-hub repository and Hub-qualified plugin id release-skill@skill-family-hub. Complete the normal publish and postVerify stages first, run the finish entry, perform every requested host load and setup action, then pass the bound feedback file to the same entry until it returns COMPLETE.
+<!-- release-skill:changelog:end version=0.9.19 locale=en -->
+
+
+<!-- release-skill:changelog:start version=0.9.18 locale=en baseline=sha256:486d52ac38ecb11f043c79661728004fb1c1593089915741867cdc0f449be275 -->
+## [0.9.18] - 2026-09-11
+
+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
+
+- 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
+
+- 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
+
+- 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
+
+- 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.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:changelog:end version=0.9.18 locale=en -->
+
+
+<!-- release-skill:changelog:start version=0.9.17 locale=en baseline=sha256:b7b382ee18c66d75612df7c83aa80439100237bf7d1ce3e36dc0cf1a038ed051 -->
 ## [0.9.17] - 2026-09-09
 
-0.9.17 is a local source candidate that adds explicit offline verification of historical release records and a self-contained Qoder projection, while preserving the setup-root and Kimi initial-directory trust fixes. 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; it also does not establish Hub acceptance.
+0.9.17 is a local source candidate that adds explicit offline verification of historical release records and a self-contained Qoder projection, while preserving the setup-root and Kimi initial-directory trust fixes. The three Foundation dependencies are pinned to the exact 0.21.0 release. This note is not evidence of publication, real-host acceptance, consumer installation verification, or independent acceptance; it also does not establish Hub acceptance.
 
 ### Security
 

package/INSTALL.md

@@ -2,7 +2,7 @@
 
 [简体中文](INSTALL.zh-CN.md)
 
-<!-- release-skill:release-version: 0.9.17 -->
+<!-- release-skill:release-version: 0.9.19 -->
 ## Prerequisites
 
 - Node.js 22.0.0 or later
@@ -125,12 +125,22 @@ 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.17
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.19
    /plugins reload
    ```
 
 After the release has reached `VERIFIED`, the optional `release-finish` workflow
 can perform the same TUI interaction only after explicit user confirmation. It
+starts from the public `release-skill post-release --root <root> --plan <plan> --run
+<postverify-run> --finish` entry. The command reports the fixed merge, host-update,
+host-load, setup, and source-branch steps. A pending load or setup observation
+exits `2`; an operational failure exits `1`; only a fully closed checklist exits
+`0`. Agent-observed host loading and the invoked `release-setup` result return
+through an absolute `--finish-feedback` file bound to the plan digest,
+configuration digest, and project root. An update result alone never proves that
+the host loaded the release.
+
+The workflow
 requires the package name, version, release tag, installed revision, and managed
 root to match the frozen plan. An exact current installation is checked before
 returning `ALREADY_CURRENT`. When an installation or migration occurs, the
@@ -146,13 +156,22 @@ The effective configuration root is explicit `kimiHome`, then
 `KIMI_CODE_HOME`, then `~/.kimi-code`. The TUI process and post-operation
 observation use that same root. The TUI working directory is the resolved release
 project root passed through `--root`. After explicit confirmation of the frozen
-plan and selection of 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 row, verifies the new selection,
-confirms it, and waits for the known command prompt. Unknown rows or selections,
-a failed move, timeout, early exit, or a folder-trust dialog after the plugin
-command fails closed. release-finish still strips ANSI/OSC control sequences and
-soft wrapping before it checks the frozen repository, tag, and selected
+plan and selection of Kimi for update, release-finish reads the complete initial
+`Trust this folder?` dialog and requires exactly one positive
+`Trust this folder` action and exactly one selected action. If the positive action
+is already selected, it confirms without sending a direction key. If a known
+rejection action is selected, it moves once according to the action's position,
+reads the complete dialog again, and verifies the positive selection before
+confirming. Unknown or duplicate actions, a missing or duplicate positive action,
+an unverifiable selection, a failed move, timeout, early exit, or a folder-trust
+dialog after the plugin command fails closed. When a later Kimi version presents
+a new reproducible blocking layout, capture the Kimi version, visible actions,
+selected action, and their relationship first. Add the nearest regression and
+continue compatibility work when those facts uniquely identify the current
+directory, positive trust action, and selection result; stop and escalate when
+directory identity or action semantics remain ambiguous. release-finish still
+strips ANSI/OSC control sequences and soft wrapping before it checks the frozen
+repository, tag, and selected
 `Trust and install` action inside the plugin trust dialog. This local check is
 not part of `verify` and does not alter the `VERIFIED` release state.
 
@@ -198,6 +217,44 @@ For a single session from a source checkout you can also point CodeBuddy at the
 generated plugin directory with `--plugin-dir <path>/adapters/workbuddy`; the
 adapter never references files outside its own directory.
 
+## Install as a Cursor Local plugin
+
+`adapters/cursor/` contains `.cursor-plugin/plugin.json`, all public Skills and a
+self-contained runtime. Skills resolve the plugin from the absolute `SKILL.md`
+path supplied by Cursor and validate the root manifest; no plugin-root environment
+variable is required.
+
+Declare `cursor` in `postPublish.localHostUpdate.hosts` and set
+`cursor.sourcePath: adapters/cursor`. The directory and manifest identity are
+frozen with the public snapshot. Optional `cursor.dependencyInstall:
+npm-ci-ignore-scripts` installs lockfile dependencies in a candidate outside the
+scanner root.
+
+On macOS, quit Cursor and run the installed finishing entry. Supply the real
+absolute plugins root, commonly `.cursor/plugins` inside the user directory:
+
+```bash
+node <installed-plugin-root>/bin/release-skill-local-finish.mjs \
+  --root <release-project-root> --plan <frozen-plan-path> --run <completed-run-path> \
+  --update-local-hosts --hosts cursor --confirm-plan <planDigest> \
+  --cursor-plugins-root <absolute-cursor-plugins-root> --json
+```
+
+The command verifies the plan, run lineage and frozen snapshot before installing
+the complete plugin at `<cursor-plugins-root>/local/<plugin>`. First installation
+never overwrites an existing directory. Upgrades atomically exchange whole
+directories and retain the old version at `backups/<plugin>/release-*/plugin`.
+An identical version and full closure returns `ALREADY_CURRENT`; a completed
+write returns `UPDATED` with restart instructions. Indeterminate exchanges retain
+both sides for manual inspection; do not retry blindly. If backup relocation
+fails while the exchanged mapping remains provable, the script restores the old
+directory and reports failure.
+
+Restart Cursor or run Reload Window, then verify the Local source, version,
+public Skills and a real business invocation separately. Installation does not
+prove loading and never changes `VERIFIED`. Other operating systems, a running
+Cursor process or unavailable process observation return `MANUAL_REQUIRED`.
+
 ## Install as a Qoder plugin
 
 The npm package ships `.qoder-plugin/plugin.json` and a generated,

package/INSTALL.zh-CN.md

@@ -2,7 +2,7 @@
 
 [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.9.17 -->
+<!-- release-skill:release-version: 0.9.19 -->
 ## 前置条件
 
 - Node.js 22.0.0 或更高版本
@@ -113,12 +113,19 @@ release-skill 当前只采用并验证 Kimi Code 的交互式 TUI 路径，**无
 （切勿使用裸仓库地址，它会安装最新 release 或默认分支），确认信任提示后重新加载：
 
    ```
-   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.17
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.19
    /plugins reload
    ```
 
 发布达到 `VERIFIED` 后，可选的 `release-finish` 工作流可以在用户明确同意后执行
-同一套 TUI 操作。包名、版本、发布标签、已安装修订号和受管安装根都必须与冻结计划
+同一套 TUI 操作。其公共入口是 `release-skill post-release --root <root> --plan <plan>
+--run <postverify-run> --finish`，固定汇总合并、本机宿主更新、宿主加载、setup 和源码
+分支五步。仍缺加载或 setup 观察时退出码为 `2`，操作失败时为 `1`，只有全部收尾才为
+`0`。智能体观察到的宿主加载结果和实际调用 `release-setup` 的结果，必须通过绝对路径的
+`--finish-feedback` 文件回传，并绑定计划摘要、配置摘要和项目根；更新成功本身不证明新版
+已经加载。
+
+包名、版本、发布标签、已安装修订号和受管安装根都必须与冻结计划
 一致。精确当前安装会在返回 `ALREADY_CURRENT` 前核对；发生安装或迁移时，只在操作
 完成后核对结果。`.git` 目录只提供附加诊断，不是通过条件。发生安装或迁移后，
 release-finish 会重新读取 Kimi 的受管安装根，不复用操作前的观察；随后核对最终身份与
@@ -127,11 +134,16 @@ release-finish 会重新读取 Kimi 的受管安装根，不复用操作前的
 
 有效配置根依次取显式 `kimiHome`、`KIMI_CODE_HOME`、`~/.kimi-code`，TUI 进程和
 操作后观察使用同一根，TUI 工作目录固定为 `--root` 指定的当前发布项目。用户确认冻结
-计划并显式选择更新 Kimi 后，release-finish 只接受初始标准 `Trust this folder?` 界面：
-当前必须选中 `No, exit`，且存在 `Trust this folder` 目标行。流程移动到目标行，重新确认
-选中项，再提交并等待已知命令提示符。出现未知行或选中项、移动后无法确认、超时、提前
-退出，或者插件命令发出后再次出现目录信任时，该宿主失败并停止。release-finish 仍会先
-清理 ANSI/OSC 控制序列和软换行，再在插件信任对话框内核对冻结仓库、标签和当前选中的
+计划并显式选择更新 Kimi 后，release-finish 会读取完整的初始 `Trust this folder?`
+对话框，并要求其中只有一个正向项 `Trust this folder` 和一个选中项。正向项已经选中时，
+流程不发送方向键，直接确认；已知拒绝项选中时，流程按它与正向项的相对位置移动一次，
+重新读取完整对话框并确认正向项已选中，然后才提交。出现未知或重复选项、正向项缺失或
+重复、选中状态无法核验、移动后无法确认、超时、提前退出，或者插件命令发出后再次出现
+目录信任时，该宿主失败并停止。若后续 Kimi 版本出现新的可复现阻断界面，先记录 Kimi
+版本、可见选项、选中项及其相对关系；这些事实足以唯一确认当前目录、正向信任项和选择
+结果时，在最近测试补回归与兼容并继续，目录身份或选项语义仍有歧义时停止并交回主会话。
+release-finish 仍会先清理 ANSI/OSC 控制序列和软换行，再在插件信任对话框内核对冻结
+仓库、标签和当前选中的
 `Trust and install`。这个本机检查不属于 `verify`，也不会改变
 已经完成的 `VERIFIED` 发布状态。
 
@@ -189,6 +201,35 @@ qoder plugins install release-skill@skill-family-hub --scope user --json
 或新开会话，再由真实发现的 release-skill 完成一次只读发布业务调用，才能宣称新版已
 生效。这些本机结果不会改变 `VERIFIED`。
 
+## 安装为 Cursor 本地插件
+
+包内 `adapters/cursor/` 包含 `.cursor-plugin/plugin.json`、全部公开 Skill 和自足运行资源。
+Skill 根据宿主实际加载的 `SKILL.md` 绝对路径定位插件根，并检查根清单；不依赖插件根环境变量。
+
+发布项目在 `postPublish.localHostUpdate.hosts` 中声明 `cursor`，并设置
+`cursor.sourcePath: adapters/cursor`。该相对目录与清单身份随公开快照冻结；需要锁文件依赖时，
+可设置 `cursor.dependencyInstall: npm-ci-ignore-scripts`，脚本只在扫描根外的候选中安装依赖。
+
+macOS 上先退出 Cursor，再运行已安装版本的收尾入口。插件根必须使用真实绝对路径；
+常见位置是用户目录下的 `.cursor/plugins`，命令不会自动推断它。
+
+```bash
+node <installed-plugin-root>/bin/release-skill-local-finish.mjs \
+  --root <release-project-root> --plan <frozen-plan-path> --run <completed-run-path> \
+  --update-local-hosts --hosts cursor --confirm-plan <planDigest> \
+  --cursor-plugins-root <absolute-cursor-plugins-root> --json
+```
+
+命令先复验计划、运行谱系和冻结快照，再把完整插件放到 `<cursor-plugins-root>/local/<plugin>`。
+首次安装不覆盖已有目录；升级整体交换目录，并把旧版保存到 `backups/<plugin>/release-*/plugin`。
+相同版本和完整闭包一致时返回 `ALREADY_CURRENT`；写入成功返回 `UPDATED` 和重启提示。
+交换结果不确定时保留现场并要求人工检查，禁止原样重试。备份迁移失败且交换映射可确认时，
+脚本恢复原目录并报告失败。
+
+重启 Cursor 或执行 Reload Window 后，分别核对 Local 来源、版本、公开 Skill 和一次实际业务调用。
+安装成功不等于新版已加载；本机结果不改变 `VERIFIED`。其他操作系统、Cursor 仍运行或进程状态
+无法判断时，自动安装返回 `MANUAL_REQUIRED`。
+
 ## 消费端安装验证边界
 
 **何时执行验证。** 消费端安装验证仅在安装契约关键文件相对已确认公开基线发生变化时执行；

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.17 -->
+<!-- release-skill:release-version: 0.9.19 -->
 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,36 +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.17** (2026-09-09)
+**0.9.19** (2026-09-14)
 
-0.9.17 is a local source candidate that adds explicit offline verification of historical release records and a self-contained Qoder projection, while preserving the setup-root and Kimi initial-directory trust fixes. 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; it also does not establish Hub acceptance.
+0.9.19 is a local source candidate that completes the verified-release workflow with a deterministic local finish orchestrator. After publication and postVerify, maintainers can use one public entry to select the source branch outcome, update supported hosts, confirm that each host loaded the target plugin, run the configured setup Skill, and verify the source workspace without changing the release status. 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**
 
-- Offline verification reads only paths explicitly supplied on the command line and redacts local path details from its JSON result. Historical consistency does not prove that records are globally latest or that remote objects still exist.
-- Qoder remains outside release distributions and publication checkpoints. The updater does not add a marketplace, perform a first install, uninstall, or reload the current session; `UPDATED` does not mean the new plugin has been loaded.
-- Any later central Skill Family Hub publication uses the existing Git Data API with compare-and-swap. A partial Hub publication remains recoverable and is never rolled back or force-pushed automatically.
+- Finish feedback is bound to the current plugin version, project root, selected host, request identity, and execution environment; changing an update decision invalidates earlier setup evidence.
+- No host is considered loaded from filesystem installation alone, and no configured setup is considered complete until its real result is returned through the bound feedback contract.
+- Hub publication remains a compare-and-swap operation. A partial Hub publication is never rolled back or force-pushed automatically.
 
 **Added**
 
-- The public `release-skill verify-records` CLI checks caller-supplied plan, approval, target-run, and predecessor-run bytes. It reports `CONSISTENT`, `CONTRADICTED`, or `INSUFFICIENT` without scanning `.release-skill`, following paths from records, contacting remotes, writing files, or changing release state.
-- The npm package now includes `.qoder-plugin/plugin.json` and a self-contained `adapters/qoder/` projection. The existing post-release updater can update an already installed user-scope Qoder plugin only after the selected Hub source and frozen payload match.
+- The local finish entry now accepts `--finish` and emits an ordered plan for branch handling, host updates, load confirmation, configured setup execution, and final source checks.
+- Bound feedback can resume the same finish operation after real host loading and setup execution; JSON and text output expose the same pending, blocked, and complete decisions.
+- The release-finish Skill documents the end-to-end VERIFIED-to-COMPLETE handoff, including the exact request and feedback boundaries used by an agent.
 
 **Changed**
 
-- The release-finish setup continuation uses the current `--root` release project directly. It no longer asks for a second project path, while project-level readiness and host-specific loading checks remain distinct.
+- Finish completion is now separate from the release lifecycle: a successful local finish preserves VERIFIED and reports `releaseStatusChanged: false`.
+- The release help entry is shorter and routes specialized publishing, verification, documentation, marketplace, and finish details to their owning Skills.
+- Skill Family Hub remains the central marketplace, and its release entry continues to use the existing GitHub Git Data API after release verification.
 
 **Fixed**
 
-- An authorized Kimi update can confirm the standard initial `Trust this folder?` dialog for the current release project before continuing. Unknown rows, selections, repeated trust dialogs, timeout, or early exit still stop that host.
+- Ambiguous setup-plugin selection, missing host candidates, stale setup feedback, and incomplete next-action lists now fail closed instead of producing a false COMPLETE result.
+- Read-only Git observations disable optional index locking and retain exact argv, exit code, stdout, and stderr when a command fails.
 
 **Upgrade Notes**
 
-Upgrade from 0.9.16 to use `release-skill verify-records`, the Qoder package projection, and the setup/Kimi fixes. Remove the old release-skill standalone marketplace; use the ifoohoo/skill-family-hub repository and Hub-qualified plugin id release-skill@skill-family-hub. The central Skill Family Hub must accept the Qoder entry before marketplace installation can begin. Real Qoder and Kimi installation, reload, and business invocation remain separate authorized follow-up work.
+Upgrade from 0.9.18 to use the new `post-release --finish` orchestration. Remove the old release-skill standalone marketplace; use the ifoohoo/skill-family-hub repository and Hub-qualified plugin id release-skill@skill-family-hub. Complete the normal publish and postVerify stages first, run the finish entry, perform every requested host load and setup action, then pass the bound feedback file to the same entry until it returns COMPLETE.
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **Current boundary:** v0.9.17 is the current source candidate. This README
+> **Current boundary:** v0.9.19 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
@@ -67,7 +71,7 @@ Upgrade from 0.9.16 to use `release-skill verify-records`, the Qoder package pro
 > publish global preflight.
 
 <!-- release-skill:capability:safe-first-command -->
-> **Production path verified since the v0.1.1 milestone; v0.9.17 is the current
+> **Production path verified since the v0.1.1 milestone; v0.9.19 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
@@ -96,10 +100,11 @@ 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.17 candidate includes the narrow R-05 Hook cache v2 consumer
+The current 0.9.19 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 also adds the explicit-input `verify-records` command and a
-self-contained Qoder projection. Skill Family Hub remains the single
+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
@@ -107,10 +112,10 @@ 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 and real Kimi/WorkBuddy/Qoder marketplace
-installation and invocation gates. The central Hub has not yet accepted the
-release-skill Qoder entry.
-Foundation dependencies are pinned to the three released 0.17.0 packages.
+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
@@ -275,7 +280,13 @@ 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.
 
-See [INSTALL.md](INSTALL.md) for CodeBuddy, Codex, Kimi Code, and Qoder commands.
+**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
 
@@ -566,6 +577,16 @@ 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.
 
+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;
+exit 2 means caller work remains; exit 1 means a deterministic failure. Pass
+agent observations back through an absolute `--finish-feedback` JSON file bound
+to the reported plan digest, config digest, and canonical project root. Feedback
+is data only: the command does not execute its strings or treat it as new write
+authority. `--skip-local-hosts` explicitly skips host update, loading, and setup
+and cannot be combined with `--hosts` or `--update-local-hosts`.
+
 `distributions` is required but may be an explicit empty array. Use
 `distributions: []` when release-skill should publish only the unit's GitHub
 snapshot, tag, and GitHub Release, with no npm publish or marketplace consumer

package/README.zh-CN.md

@@ -2,42 +2,46 @@
 
 [English](README.md) · 安装指南：[中文](INSTALL.zh-CN.md) / [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.9.17 -->
+<!-- release-skill:release-version: 0.9.19 -->
 面向 Claude Code、CodeBuddy、WorkBuddy、Codex 和 Kimi Code 的发布准备工具，完整保留人工维护的文件内容。
 
 release-skill 帮助维护者回答三个问题：准备发布什么、还有哪些检查未通过、最终发布的内容是什么。它不重新生成、也不回写项目源文件。`prepare` 把每个配置的公开文件复制到隔离快照并验证字节——先冻结并供人工审阅，再从同一份冻结产物发布。`setup` 只显示确定性的 `compactSummary` 审阅视图，完整报告保留在临时会话目录中。
 
 <!-- release-skill:managed:start id=latest-release -->
-**0.9.17** (2026-09-09)
+**0.9.19** (2026-09-14)
 
-0.9.17 是一个本地源码候选。本版本增加显式的历史发布记录离线核验入口和自包含 Qoder 投影，并保留 setup 根目录与 Kimi 初始目录信任修复。三项 Foundation 依赖仍精确固定在已发布的 0.17.0。本说明不代表已经发布、完成真实宿主验收、完成消费者安装验证或通过独立验收，也不代表 Hub 已接纳。
+0.9.19 是一个本地源码候选。本版本补齐已验证发布后的本机收尾编排。发布和 postVerify 完成后，维护者可以通过同一个公共入口决定源码分支去向、更新受支持宿主、确认各宿主实际加载目标插件、运行项目配置的 setup Skill，并检查源码工作区；整个过程不会改写发布状态。三项 Foundation 依赖继续精确固定在已发布的 0.21.0。本说明不代表已经发布、完成真实宿主验收、完成消费者安装验证或通过独立验收。
 
 **安全**
 
-- 离线核验只读取命令行显式提供的路径，并从 JSON 结果中隐去本机路径细节。历史材料一致不代表记录是全局最新，也不证明远端对象仍然存在。
-- Qoder 不进入 release distribution 和发布检查点。更新入口不会添加市场、首次安装、卸载或重新加载当前会话；`UPDATED` 也不代表新版插件已经加载。
-- 后续如需发布到中央 Skill Family Hub，仍通过既有 GitHub Git Data API 执行比较后写入。Hub 部分发布保持可恢复，系统不会自动回滚；即不回滚、不覆盖已经成功的远端步骤。
+- 收尾反馈绑定当前插件版本、项目根目录、选定宿主、请求身份和运行环境；宿主更新决定变化后，旧 setup 证据自动失效。
+- 仅完成文件安装不能证明宿主已经加载插件；已配置的 setup 也只有在真实结果通过绑定反馈返回后才算完成。
+- Hub 发布继续绑定已观察的分支头执行比较后写入。部分发布时不回滚、不覆盖已经成功的远端步骤。
 
 **新增**
 
-- 新增公共命令 `release-skill verify-records`，核验调用者显式提供的计划、批准、目标 run 和前驱 run 字节。命令返回 `CONSISTENT`、`CONTRADICTED` 或 `INSUFFICIENT`，不会扫描 `.release-skill`、跟随记录中的路径、访问远端、写文件或改变发布状态。
-- npm 包增加 `.qoder-plugin/plugin.json` 和自包含的 `adapters/qoder/` 投影。现有发布后更新入口只在所选 Hub 来源与冻结载荷一致时，更新已经存在的用户范围 Qoder 插件。
+- 本机收尾入口新增 `--finish`，按固定顺序给出分支处理、宿主更新、加载确认、setup 执行和源码终检计划。
+- 真实完成宿主加载和 setup 后，可以把绑定反馈交回同一入口继续执行；JSON 与文本输出对待处理、阻断和完成状态给出一致裁决。
+- release-finish Skill 补充从 VERIFIED 到 COMPLETE 的完整交接，并明确智能体执行请求与回传反馈的边界。
 
 **变更**
 
-- release-finish 的 setup 续接直接使用当前 `--root` 发布项目，不再询问第二个项目路径。项目级就绪检查与各宿主的加载检查仍分别判断。
+- 本机收尾完成与发布生命周期分离：成功结果继续保留 VERIFIED，并明确返回 `releaseStatusChanged: false`。
+- release-help 入口缩短，把发布、验证、文档、市场和收尾细节路由到各自负责的 Skill。
+- Skill Family Hub 继续作为中央市场；发布完成验证后，release-skill 仍通过既有 GitHub Git Data API 更新 Hub 条目。
 
 **修复**
 
-- 已授权的 Kimi 更新可以先确认当前发布项目的标准初始 `Trust this folder?` 界面，再继续插件操作。未知行、未知选中项、重复信任界面、超时或提前退出仍会停止该宿主。
+- setup 插件选择不唯一、没有宿主候选、setup 反馈过期或后续动作缺失时，流程现在会失败关闭，不再错误返回 COMPLETE。
+- 只读 Git 观察关闭可选索引锁；命令失败时保留精确参数、退出码、标准输出和标准错误。
 
 **升级说明**
 
-从 0.9.16 升级后，可使用 `release-skill verify-records`、Qoder 包投影及 setup/Kimi 修复。请移除独立的 `release-skill` 市场，改用 ifoohoo/skill-family-hub 仓库与 Hub 限定插件名 release-skill@skill-family-hub。中央 Skill Family Hub 必须先接纳 Qoder 条目，才能开始市场安装。真实 Qoder 与 Kimi 的安装、重载和业务调用仍是需要单独授权的后续工作。
+从 0.9.18 升级后可使用新的 `post-release --finish` 编排。请移除独立的 `release-skill` 市场，改用 ifoohoo/skill-family-hub 仓库与 Hub 限定插件名 release-skill@skill-family-hub。先完成正常发布与 postVerify，再运行收尾入口，实际完成其请求的宿主加载和 setup 动作，并把绑定反馈交回同一入口，直至结果为 COMPLETE。
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **当前边界：** v0.9.17 只是当前源码候选。本 README 记录预期范围与验证边界，
+> **当前边界：** v0.9.19 只是当前源码候选。本 README 记录预期范围与验证边界，
 > 不代表已经发布、完成消费者安装验证或通过独立验收。
 > 版本可用性以对应发布记录及发布后验证结果为准。
 > v0.4.1 是更早的已发布里程碑（v0.2.2 曾处于已发布状态，后因平台验证收敛修复而更新）。
@@ -53,7 +57,7 @@ release-skill 帮助维护者回答三个问题：准备发布什么、还有哪
 > 远端唯一性检查在 `publish` 全局预检执行。
 
 <!-- release-skill:capability:safe-first-command -->
-> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.9.17 是当前源码候选，本 README 不证明该候选已经发布、完成消费者安装验证或通过独立验收。**
+> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.9.19 是当前源码候选，本 README 不证明该候选已经发布、完成消费者安装验证或通过独立验收。**
 > npm 安装的 CLI 是受支持的用户入口；源码 checkout 保留为开发/贡献者路径。
 >
 > **第一条命令：**
@@ -71,16 +75,17 @@ marketplace 委托目标工作区发布的边界不变。
 
 旧 production 计划缺少 `sourceAuthority` 时，在外部写入前拒绝。未发生外部写入的计划必须重新 prepare 并批准新摘要，不能补写旧计划或迁移批准。已有 `PARTIAL` 保留检查点，走匹配版本的恢复路径。evidence v1 只读；v2 顶层封闭，阶段扩展放在 `details`。摘要和恢复建议只作诊断，不构成发布权威。
 
-当前 0.9.17 候选包含窄范围的 R-05 Hook cache v2 消费路径、公开 `postverify`
+当前 0.9.19 候选包含窄范围的 R-05 Hook cache v2 消费路径、公开 `postverify`
 路径和稳定隔离安装树记录路径（A2/A3），并增加只接受显式输入的 `verify-records`
-命令和自包含 Qoder 投影。Skill Family Hub 仍是唯一市场来源。
+命令、自包含 Qoder 投影、Cursor 正式打包，以及基于 Foundation 的宿主核验桥。
+Skill Family Hub 仍是唯一市场来源。
 `release-prepare` Skill 现在会组织项目已有的评估、刷新、聚焦检查和 prepare 入口，不新增执行引擎。
 `prepare --help` 和 `prepare -h` 会在配置、锁、run 或 Hook 观察请求之前返回。
 所选宿主加载已发布插件后，`release-finish` Skill 还可以报告源码分支，并继续执行已配置的 setup 入口。
-当前仍不包含 R-02 安全整树盘点和真实 Kimi/WorkBuddy/Qoder 市场安装与调用门禁；中央 Hub
-尚未接纳 release-skill 的 Qoder 条目。本范围说明不构成远端发布记录或消费者升级指引。
+当前仍不包含 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` 只表示机制观察结果，
@@ -222,7 +227,12 @@ TUI 路径，见 [INSTALL.zh-CN.md](INSTALL.zh-CN.md#安装为-kimi-code-插件)
 用户范围的市场安装；生成适配器本身不能证明 Hub 消费成立。安装与发布后更新边界见
 [INSTALL.zh-CN.md](INSTALL.zh-CN.md#安装为-qoder-插件)。
 
-CodeBuddy、Codex、Kimi Code 和 Qoder 的完整命令见 [INSTALL.zh-CN.md](INSTALL.zh-CN.md)。
+**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)。
 
 ### 离线核验历史发布记录
 
@@ -476,6 +486,8 @@ releaseUnits:
 release-finish 在 `--root` 指定的当前发布项目根目录调用该入口，不再要求另行提供项目目录。
 两个配置彼此独立。
 
+完整的本地收尾使用 `release-skill post-release --finish`。命令固定报告分支决定、宿主更新、实际加载、setup 和源码分支检查：全部适用步骤完成或明确跳过时退出 0，仍有待办时退出 2，确定失败时退出 1。智能体通过绝对路径的 `--finish-feedback` JSON 文件回传观察，文件必须绑定当前计划摘要、配置摘要和规范项目根目录。反馈只作为数据：脚本不执行其中字符串，也不把反馈当成新的写入授权。`--skip-local-hosts` 显示跳过宿主更新、加载和 setup，不得与 `--hosts` 或 `--update-local-hosts` 同时使用。
+
 `distributions` 是必填字段，但可以显式设为空数组。使用
 `distributions: []` 时，release-skill 只发布该单元的 GitHub 快照、标签和
 GitHub Release，不生成 npm 发布或市场消费者动作。单元的 `postPublish` 声明仍会

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

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