release-skill 0.9.17 → 0.9.19

package/adapters/codex/skills/release-help/SKILL.md

@@ -6,148 +6,92 @@ description: "Discoverable entry point for release-skill: dependency and environ
 > **Codex 安装入口解析协议**：在调用 CLI 前，Agent 必须从宿主当前已加载技能的元数据中取得本 `SKILL.md` 的实际绝对路径，并将该字面量记为 `SKILL_FILE`。
 > `SKILL_FILE` 不是环境变量；禁止从工作目录、可执行搜索路径、源码仓库或 shell 调用上下文猜测。若宿主未提供该绝对路径，立即停止并报告安装定位失败。
 > 对 `SKILL_FILE` 执行 `realpath`，取其目录向上两级得到 `PLUGIN_ROOT`；校验真实技能路径匹配 `PLUGIN_ROOT/skills/*/SKILL.md` 且仍位于插件根内（路径包含检查）。
-> 令 `RELEASE_SKILL_ENTRY=PLUGIN_ROOT/bin/release-skill.mjs`，对入口执行 `realpath` containment、`lstat` 非符号链接且为普通文件校验。
-> 每一次 shell 工具调用都必须在同一个调用中用上述已验证绝对值设置 `RELEASE_SKILL_ENTRY`，然后执行 `node "$RELEASE_SKILL_ENTRY" ...`；不得依赖前一次 shell 的变量。
+> 令 `RELEASE_SKILL_LOCAL_FINISH_ENTRY=PLUGIN_ROOT/bin/release-skill-local-finish.mjs`，对入口执行 `realpath` containment、`lstat` 非符号链接且为普通文件校验。
+> 每一次 shell 工具调用都必须在同一个调用中用上述已验证绝对值设置 `RELEASE_SKILL_LOCAL_FINISH_ENTRY`，然后执行 `node "$RELEASE_SKILL_LOCAL_FINISH_ENTRY" ...`；不得依赖前一次 shell 的变量。
 >
 
 # release-help
 
 ## 触发
 
-用户询问如何使用 release-skill、发布流程是什么、或请求只读诊断和 dry-run 安全检查。
+询问 release-skill 的用法、发布流程、依赖、环境、只读诊断或 dry-run 时使用。本入口只做能力说明和分诊；专用工作流交给对应 Skill。
 
-## 职责
+## 只读边界
 
-- 依赖和环境检查：Node.js >= 22、Git 决定本地准备就绪度；npm/gh 另行决定生产依赖就绪度
-- 能力说明：缺少配置时走 `help → setup → assess`；已有配置的安全默认路径是 `help → assess → prepare --offline`；日常生产发布优先使用可恢复的 `ship`，兼容的分阶段闭环仍是 `prepare --online --production → approve → publish → verify`。冻结计划批准是正常发布级流程的唯一批准门；声明 `requiresApproval: true` 的 postPublish hook 仍须等待独立 checkpoint 批准。若计划声明 `postVerify` hook，可用 `postverify` 直接执行独立收尾 run，也可由 `ship` 编排该阶段；本机收尾必须等待完成的 postVerify run，不能把仅有 `VERIFIED` 的 verify run 当作本机收尾授权。核心发布流程跨平台，WorkBuddy 本机收尾仅支持 macOS
-- 最小示例：展示从 release-help 到 release-assess 的最短路径
-- 只读诊断：运行 dry-run 检查，不修改任何文件
-- 故障引导：根据错误码指向对应的修复 Skill
+`help` 不联网、不检查认证、不改文件、不生成计划，也不执行 Git、宿主安装或外部发布写入。它只根据当前环境报告准备度并给出下一步。优先调用插件自带入口；不可用时才回退到源码入口。
 
-## 0.9.17 候选边界
+核心流程跨平台；WorkBuddy 本机收尾仅支持 macOS。Node.js >= 22 和 Git 决定本地准备度。npm、gh 只影响生产发布依赖；pnpm 缺失只进入建议。
 
-当前源码候选允许多发布单元项目在计划冻结前显式选择本轮范围。`prepare` 和新建的 `ship` 状态支持重复传入 `--unit <id>`；未传时继续选择全部配置单元。成功选择会列出选中与延期单元。延期单元不进入本轮计划，也不获得发布状态。
+本地阶段通过须同时满足 `status: "READY"` 和 exit code 0。读取 `readiness.localPreparation.status` 与 `missingRequired`。生产另读 `readiness.productionPublish`：缺 npm/gh 为 `NOT_READY`，已安装也只是 `AUTH_CHECK_REQUIRED`，不代表认证、权限或发布授权已经成立。
 
-选择只影响按单元绑定的检查与动作。完整配置、生成物新鲜度和顶层 Hook 仍覆盖整个项目。`publicSourceAuthorityReceipt` 涉及的 coordinator 和 subjects 必须作为完整闭包共同选择，系统不会自动扩选。计划冻结后，`plan.units` 是唯一范围权威；publish、reconcile、verify 和 distribute 不接受 `--unit`。
+## 0.9.19 候选边界
 
-0.9.3 引入的四项工作流保护、Hook cache v2 和稳定隔离安装树记录在后续版本继续保留。当前 0.9.17 候选精确消费 Foundation 0.17.0 的公开包根 API。Hook cache 只复用绝对路径或经真实 cwd 校验的 cwd-relative executable identity；裸 PATH、PATHEXT、Windows 和观察不可用时，Hook 仍冷执行，缓存复用失败关闭且不写入 v2 cache。缓存没有 TTL。
+当前 0.9.19 候选精确消费 Foundation 0.21.0 的公开包根 API。0.9.19 仍是源码候选，不能从本说明推断已批准、发布或验证。
 
-稳定隔离安装树记录只在宿主命令退出、目录已隔离且扫描期间没有并发写入时执行；宿主附加链接只记录、不跟随，声明载荷中的 symlink 失败关闭，legacy 全树语义保持不变。0.9.17 仍是源码候选，不能从本说明推断已批准、发布或验证。
+冻结前，`prepare` 或新建 `ship` 状态可重复传入 `--unit <id>`；不传则选择全部单元。延期单元不进入计划，也不获得发布状态。完整配置、生成物新鲜度和顶层 Hook 仍覆盖全项目；`publicSourceAuthorityReceipt` 的 coordinator 与 subjects 必须共同选择。冻结后以 `plan.units` 为唯一范围，publish、reconcile、verify、distribute 不再接受 `--unit`。
 
-**阶段通过规则**: `status` 与 `readiness.localPreparation.status` 只判断本地 help/assess/prepare；其充要条件是 `READY` 且 exit code 为 0。`missingRequired` 列出缺失的 Node/Git。生产发布必须另外读取 `readiness.productionPublish`：缺少 npm/gh 时为 `NOT_READY`，依赖存在时仍是 `AUTH_CHECK_REQUIRED`，因为 help 不访问网络、不验证认证。Agent 无权把本地就绪解释为生产就绪。
+每个单元都要声明 `previousPublicBaseline`：确认没有前序版本才用 `none`，否则使用带 repo/ref/commit 的 `bound`。`none` 不绕过 publish 的唯一性预检。
 
-**边界**: help 不修改文件系统、不执行外部写操作、不生成发布计划。优先探测 PATH 上的全局安装命令 `release-skill`，不可用时回退到源码路径。每个 unit 必须配置 `previousPublicBaseline`：首次发布且确认无前序版本用 none，已有版本用 bound + repo/ref/commit；none 不是绕过 publish 唯一性预检的开关。v0.1.1 已完成 GitHub/npm 真实生产发布、冻结 Git ref 的 Claude/Codex 消费者安装、精确 npm 安装 smoke 与最终 VERIFIED；生产等价本地协议套件继续覆盖 fake gh/npm/Claude/Codex 和本地 bare Git。测试未做 OS 级禁网，且一次成功发布不能证明其他项目的认证、权限、限流或最终一致性行为；每个项目的首次生产发布仍应作为受监控 canary。
+Hook cache v2 只复用绝对路径，或已用真实 cwd 核验的 cwd-relative executable identity；裸 PATH、PATHEXT、Windows 或观察不可用时冷执行，并失败关闭。稳定隔离安装树只在宿主命令退出、目录隔离且扫描期间无并发写入时记录；附加链接只记录、不跟随，声明载荷中的 symlink 失败关闭。
 
-## 正向执行路径
+## 最短路径
 
-1. 使用插件根相对路径运行 CLI：`node "$RELEASE_SKILL_ENTRY" help --json`
-2. 检查 `readiness.localPreparation`；需要生产发布时再检查 `readiness.productionPublish`
-3. 若环境就绪且缺少 `.release-skill/project.yaml`，先路由 `release-setup`；配置已存在才运行 `release-assess`
-4. 默认在审阅本地计划和快照后停止；只有用户明确要求且完成摘要审批时才进入 `release-publish`。已持有合法批准的 production plan 时，publish 自行完成权威校验，不把 route 当作授权门
-
-## 确定性脚本调用
+1. 从插件根运行 `help --json`，检查本地准备度；生产发布再检查生产准备度。
+2. 缺少 `.release-skill/project.yaml` 时进入 `release-setup`；已有配置时进入 `release-assess`。
+3. 本地评估使用 `release-assess` 和 `prepare --offline`。默认在审阅计划与快照后停止。
+4. 生产发布优先使用可恢复的 `ship`；也可走 `prepare --online --production → approve → publish → verify`。
 
 ```bash
-# 从插件根运行（自包含 bundle，无需 node_modules）
 node "$RELEASE_SKILL_ENTRY" help --json
 node "$RELEASE_SKILL_ENTRY" setup --root <path> --json
 node "$RELEASE_SKILL_ENTRY" assess --root <path> --offline --json
-# 日常发布快速路径：发布前确认可读计划摘要，状态文件可恢复。
-# 受限 postPublish hook 的 checkpoint 批准与计划批准分开。
-node "$RELEASE_SKILL_ENTRY" ship --root <path> --target-version <version> --json
-# 多发布单元项目显式选择本轮范围；未传 --unit 时仍为全部单元
-node "$RELEASE_SKILL_ENTRY" ship --root <path> \
-  --target-version <version> --unit <unit-a> --unit <unit-b> --json
-# 对已经 VERIFIED 的计划独立执行 postVerify hook；不读取或写入 ship state
-node "$RELEASE_SKILL_ENTRY" postverify --root <path> \
-  --plan <plan-path> --approval <approval-path> --run <verified-run-path> \
-  --hook-approval <immutable-hook-approval-path> --json
-# 开发阶段执行声明 hooks 并生成 prepare 可复用的内容绑定收据
-# 配置时刻即授权（FM-16 处置 A）：hook 是任意本地进程、无隔离、触发前无确认点，
-# 命令调用本身即授权执行配置中的 hooks
-node "$RELEASE_SKILL_ENTRY" hooks validate --root <path> --json
-# 仅旧冻结计划兼容：记录历史 Kimi/CodeBuddy 人工证明
-# （本地自声明收据，证明力弱：--actor 仅非空字符串校验、无外部签名核验；新计划不适用）
-node "$RELEASE_SKILL_ENTRY" attest --root <path> \
-  --platform <kimi|codebuddy> --plugin <id> --result <passed|failed> --actor <person> --json
-# 发布文档刷新：默认只读演练
-node "$RELEASE_SKILL_ENTRY" docs refresh --unit <id> --json
-# 摘要确认后的本地写入（三项绑定缺一不可）
-node "$RELEASE_SKILL_ENTRY" docs refresh --unit <id> \
-  --write --confirm-refresh <refreshDigest> --ack-local-document-write --json
+node "$RELEASE_SKILL_ENTRY" route --root <path> --target-version <version> --json
 ```
 
-## 发布文档刷新（docs refresh）
+`route` 只做分类和推荐，不是授权门。分类为 docs、config、marketplace、code 或 mixed；存在 `PARTIAL` 时先进入 reconcile，不能确定时按更安全的完整路径处理。
 
-发布单元配置 `releaseDocuments` 后，一份结构化双语说明源可确定性刷新 README 受管区域、唯一版本标记的机器值和 CHANGELOG 当前版本受管条目。核心 CLI 不联网、不调用大模型、不自动翻译；只改写声明过的受管区域、版本标记机器值和当前受管条目，区域外字节逐字保留。`prepare` 只检查新鲜度，不写工作树。
+## 生产发布与恢复边界
 
-- **配置**：`releaseDocuments.notesSource`（说明源路径，只允许 `{version}` 占位符与 `.yaml`/`.yml`/`.json` 后缀）、`locales`（如 `[en, zh-CN]`）、`changelogs`（path + locale）、`readmes`（path + locale + `regions` 受管区域 id + `versionMarkers` 版本标记模式）。版本标记模式必须与 README 现有唯一标记精确匹配，`{version}` 代表机器版本值，刷新只替换该值；零次或多次匹配失败关闭。
-- **说明源**：`version` 必须与单元版本精确一致，`date` 为 `YYYY-MM-DD`，每个配置语种恰好出现一次且 `summary`、变更项非空，`security`/`breaking`/`added`/`changed`/`deprecated`/`removed`/`fixed` 至少一个类别含条目。YAML alias、重复键、未知字段和语种回退都失败关闭。
-- **只读演练**：`docs refresh --unit <id> --json` 输出逐文件相对路径、locale、新旧摘要、`version`、`locales`、`inputDigest`、`refreshDigest` 和 `nextCommand.argv`；候选无变化时 `status: "clean"`。
-- **确认写入**：必须同时提供 `--write`、精确 `--confirm-refresh <refreshDigest>` 和 `--ack-local-document-write`，全部目标作为一个事务提交；成功后立即复演必须为 `clean`。
+只有用户明确要求生产发布，且冻结计划摘要已经人工审阅，才进入 `release-publish`。冻结计划批准是发布级唯一批准门；publish 会自行核对 plan、approval、digest、目标版本、远端冲突和允许动作。route、help、`READY`、历史成功或 `VERIFIED` 都不能替代批准。
 
-**授权边界**：本地发布文档写入授权只覆盖声明的本地文档目标，不是 Git 提交、push、publish 或安装的授权。hook/gate 由对应命令调用直接授权——在 project.yaml 配置 hook 即完成授权（配置时刻即授权契约，FM-16 处置 A）：hook 是任意本地进程、无文件系统/网络隔离、触发前无确认点，配置者须对其内容负责；恢复触发前强制确认门为后续加固项。写入后必须审阅、提交，再重新 prepare。
+`requiresApproval: true` 的 postPublish hook 还需要独立 checkpoint 批准。项目配置中的其他 hook 是任意本地进程，没有文件系统或网络隔离；执行相应命令即授权运行，help 不替用户作出该授权。
 
-## 故障路由
+外部写入按 checkpoint 停止；部分成功进入 `PARTIAL`。不得自动删除远端标签、覆盖 Release、unpublish npm 或从头重跑。使用 `release-reconcile` 查询远端实际状态，只重试安全且未完成的动作；冲突交回人工决定。
 
-| 场景 | 处理 |
-|---|---|
-| Node.js 版本不足 | `status: "NOT_READY"`, `missingRequired` 含 `"node>=22"`；提示升级至 >= 22 |
-| Git 未安装 | `status: "NOT_READY"`, `missingRequired` 含 `"git"`；提示安装 Git |
-| pnpm 未安装 | 不影响本地准备；仅出现在 recommendations 中 |
-| npm/gh 未安装 | 本地准备仍可就绪，但 `readiness.productionPublish.status` 为 `NOT_READY` |
-| npm/gh 已安装 | 生产状态仍为 `AUTH_CHECK_REQUIRED`；发布前验证 `gh auth`、Git HTTPS credential 和 npm auth |
-| CLI 入口不存在 | 确认 `$RELEASE_SKILL_ENTRY` 存在；不存在时重新安装插件 |
-| 项目配置不存在 | 路由 `release-setup`，默认只读；不得直接生成或覆盖 README/配置 |
-| assess 失败 | 运行 `node "$RELEASE_SKILL_ENTRY" assess --offline --json` 获取详情 |
-| 请求生产发布 | 已有公开版本先调用 `release-prepare --online --production` 观察 bound 基线；人工审阅后直接调用 `release-publish`，由 publish 自行完成计划、approval、digest、远端冲突和 `PARTIAL` 校验 |
-| RELEASE_DOCS_INVALID | 配置或说明源语义非法（重复键、alias、未知字段、版本漂移等）；修正配置或说明源后重新演练 |
-| RELEASE_DOCS_TRANSLATION_MISSING | 配置语种缺失或多余；补齐说明源语种，与 `releaseDocuments.locales` 完全一致，不得回退 |
+## VERIFIED 后收尾
 
-## Routing Suggestions (§4.3 Quickstart Routing)
+声明的 `postVerify` hook 可由 `postverify` 独立执行或由 `ship` 编排。计划声明该 hook 时，本机收尾必须等待完成的 postVerify run；没有声明时使用同一计划的 `VERIFIED` verify run。
 
-对于不清楚如何开始的用户，推荐使用 `release-skill route` 命令进行自动化工作流选择：
+随后进入 `release-finish`，通过公共入口编排宿主更新、加载确认、已配置 setup 和源码分支检查：
 
 ```bash
-# 快速分类变更并推荐工作流；已知目标版本时显式传入，未知时省略
-node "$RELEASE_SKILL_ENTRY" route --root <path> --json
-node "$RELEASE_SKILL_ENTRY" route --root <path> \
-  --target-version <version> --json
-
-# JSON 输出包含 classification 和 recommendation 字段
-{
-  "classification": {
-    "code": [],
-    "docs": ["README.md"],
-    "config": [],
-    "marketplace": [],
-    "mixed": false
-  },
-  "recommendation": {
-    "workflowKind": "docs-only",
-    "reason": "Pure documentation changes detected...",
-    "firstCommand": "release-docs"
-  }
-}
+node "$RELEASE_SKILL_LOCAL_FINISH_ENTRY" \
+  --root <project-root> --plan <plan-path> --run <verify-or-postverify-run-path> \
+  --finish --json
 ```
 
-**可用工作流**:
-- `docs-only`: 纯文档变更（跳过代码类门限）
-- `config-only`: 纯配置变更（schema 验证 + 决策分支）
-- `marketplace-only`: 纯 marketplace 索引变更（条目更新 + snapshot 同步）
-- `full-happy-end`: 混合变更或无法确定（fail-closed 到最安全路径）
-- `reconcile`: 存在 PARTIAL 运行时需先恢复
-- `help`: 无变更且未指定目标版本
+首次结果可能请求用户选择分支和本机宿主，或返回需要智能体实际加载并调用 setup 的请求。将绑定反馈写入文件后，以同一入口增加 `--finish-feedback <feedback-path>` 再次汇总。完整参数、反馈合同、宿主限制和 macOS Cursor 安装见 `release-finish`。仅有 `VERIFIED` 不构成本机写入、插件更新、分支合并或 setup 写入授权；收尾结果也不改写发布状态。
+
+## 专用工作流路由
+
+- 消费项目的 Cursor 场景配置、受控可执行目录、用户状态目录、结果不确定时的现场保留与复验，见 `release-verify`。
+- README、CHANGELOG 和双语说明的 `docs refresh` 演练、摘要确认与受管写入，见 `release-docs`。
+- VERIFIED 后的分支决定、宿主更新、加载反馈、setup 和源码检查，见 `release-finish`。
+- 纯配置变更，见 `release-config`。
+- 纯 marketplace 索引与快照变更，见 `release-marketplace`。
+
+这些入口保留各自的参数、确认和失败关闭规则；help 不复制或放宽它们。
 
-参考文档：
-- [`release-docs`](../release-docs/SKILL.md) - 文档工作流详解
-- [`release-config`](../release-config/SKILL.md) - 配置工作流详解
-- [`release-marketplace`](../release-marketplace/SKILL.md) - Marketplace 工作流详解
+## 故障分诊
 
-| RELEASE_DOCS_CONFLICT | 目标含非受管同版本条目、受管标记损坏或人工冲突；人工修复目标并保留人工修改后重新演练 |
-| RELEASE_DOCS_REFRESH_STALE | 确认绑定后候选已变化；重新演练取得新 `refreshDigest` 再确认写入 |
-| RELEASE_DOCS_STALE | prepare 检测到文档未刷新；按 `docs refresh` → 审阅 → 提交 → 重新 prepare 恢复 |
+- Node.js 或 Git 缺失：读取 `missingRequired`，补齐依赖后重跑 help。
+- npm/gh 缺失或未认证：本地准备仍可继续；生产发布前另行完成 gh、Git HTTPS credential 与 npm auth 检查。
+- CLI 入口缺失：确认 `$RELEASE_SKILL_ENTRY` 存在；缺失时重新安装插件。
+- 项目配置缺失：进入 `release-setup` 的只读发现，不直接生成或覆盖 README/配置。
+- assess 失败：运行 `release-assess` 的离线诊断并按错误码处理。
+- `PARTIAL` 或远端冲突：进入 `release-reconcile`，保留已经成功的 checkpoint。
+- 文档、Cursor、宿主更新或本机收尾失败：转到上节对应专用 Skill，不在 help 中猜测恢复步骤。
 
 ## 后续引导
 
-本地准备就绪后下一步运行 `release-assess`：`node "$RELEASE_SKILL_ENTRY" assess`。生产发布还要求 npm、gh 可用，并在发布前另行完成认证检查。
+本地就绪后运行 `release-assess`；需要生产发布时，再确认 npm、gh、认证、冻结计划和有效批准。

package/adapters/codex/skills/release-verify/SKILL.md

@@ -57,7 +57,7 @@ ship state；hook approval 缺失、错误或过期时，在 hook 执行前失
 2. 使用插件根相对路径运行 CLI；命令调用本身即授权执行已配置的 verification gate 和 smoke process
 3. 检查 exit code 和结构化状态：`VERIFIED`（全部通过）/ 失败（具体错误）
 4. 只有 `VERIFIED` 才是发布 happy end
-5. 达到 `VERIFIED` 后先检查计划是否声明 `postVerify` hook：直接收尾使用独立的 `postverify --plan --approval --run --hook-approval`，由该命令产生 `DISTRIBUTED` postVerify run；若仍由持久化 ship state 承担编排，则使用 `ship --hook-approval` 完成同一阶段，再把最终 run 路径交给 `release-finish`。没有 postVerify hook 时，把当前 verify run 路径交给 `release-finish`。随后按清单主动询问分支合并和本机宿主插件更新；发布策略已包含分支动作时略过合并询问
+5. 达到 `VERIFIED` 后先检查计划是否声明 `postVerify` hook：直接收尾使用独立的 `postverify --plan --approval --run --hook-approval`，由该命令产生 `DISTRIBUTED` postVerify run；若仍由持久化 ship state 承担编排，则使用 `ship --hook-approval` 完成同一阶段，再把最终 run 路径交给 `release-finish`。没有 postVerify hook 时，把当前 verify run 路径交给 `release-finish`。随后执行返回的 `post-release --finish` 命令，按 `nextActions` 补齐分支决定、宿主加载与真实 setup 结果；发布策略已包含分支动作时略过合并询问
 
 ## 确定性脚本调用
 
@@ -84,7 +84,7 @@ node "$RELEASE_SKILL_ENTRY" postverify --root <path> \
 
 ## 发布后收尾
 
-`VERIFIED` 不代表要自动修改开发分支或本机宿主。进入 `release-finish` 后，只有用户明确同意，才执行对应的本地动作。本机插件更新失败不会改变发布终态。
+`VERIFIED` 不代表要自动修改开发分支或本机宿主。进入 `release-finish` 后，只有用户明确同意，才执行对应的本地动作。`post-release --finish` 退出 0 需要所有适用步骤完成或明确跳过；单纯的宿主 `UPDATED` 不代表新入口已加载，也不代表 setup 已执行。本机插件更新失败不会改变发布终态。
 核心 prepare、publish、verify 流程跨平台；WorkBuddy 的本机收尾探测和更新仅支持 macOS。
 
 ## 烟雾测试

package/adapters/codex/src/schemas/host-descriptor.schema.json

@@ -25,7 +25,7 @@
       "additionalProperties": false,
       "required": ["driverId", "authStrategy", "credentialMutation"],
       "properties": {
-        "driverId": { "enum": ["kimi-code-print-v1", "workbuddy-codebuddy-print-v1", "codebuddy-print-v1", "claude-code-print-v1", "codex-exec-v1", "qodercli-print-v1"] },
+        "driverId": { "enum": ["kimi-code-print-v1", "workbuddy-codebuddy-print-v1", "codebuddy-print-v1", "claude-code-print-v1", "codex-exec-v1", "qodercli-print-v1", "cursor-agent-print-v1"] },
         "authStrategy": { "const": "existing-user-state" },
         "credentialMutation": { "const": "host-managed" }
       }
@@ -109,7 +109,14 @@
       }
     },
     {
-      "if": { "properties": { "hostId": { "enum": ["kimi-code", "workbuddy", "codebuddy", "claude", "codex", "qoder"] } }, "required": ["hostId"] },
+      "if": { "properties": { "hostId": { "const": "cursor" } }, "required": ["hostId"] },
+      "then": {
+        "required": ["verification"],
+        "properties": { "verification": { "type": "object", "properties": { "driverId": { "const": "cursor-agent-print-v1" } } } }
+      }
+    },
+    {
+      "if": { "properties": { "hostId": { "enum": ["kimi-code", "workbuddy", "codebuddy", "claude", "codex", "qoder", "cursor"] } }, "required": ["hostId"] },
       "else": { "properties": { "verification": false } }
     },
     {

package/adapters/cursor/.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": "./skills/"
+}

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

@@ -0,0 +1,110 @@
+{
+  "schemaVersion": 1,
+  "kind": "skill-family.contracts.consumer-contract-vectors",
+  "foundationVersion": "0.21.0",
+  "sets": [
+    {
+      "capabilityId": "foundation.contracts.object-validation",
+      "vectorSetId": "foundation.contracts.object-validation.consumer-v1",
+      "contractId": "skill-family-contracts:validateDocument",
+      "strategy": "real-pure",
+      "vectors": [
+        {
+          "schemaVersion": 1,
+          "kind": "skill-family.consumer-contract-vector",
+          "vectorId": "foundation.contracts.object-validation.consumer-v1.indeterminate",
+          "vectorSetId": "foundation.contracts.object-validation.consumer-v1",
+          "capabilityId": "foundation.contracts.object-validation",
+          "foundationVersion": "0.21.0",
+          "contractId": "skill-family-contracts:validateDocument",
+          "caseClass": "indeterminate",
+          "strategy": "real-pure",
+          "request": {
+            "document": { "schemaVersion": 1, "kind": "skill-family.project-manifest" },
+            "options": { "schemaId": "https://contracts.skill-family.example/v1/project-manifest.json", "dialect": "2020-12", "policy": "strict" }
+          },
+          "expected": { "outcome": "indeterminate", "allowedStates": ["return", "throw"], "failClosed": true }
+        },
+        {
+          "schemaVersion": 1,
+          "kind": "skill-family.consumer-contract-vector",
+          "vectorId": "foundation.contracts.object-validation.consumer-v1.negative",
+          "vectorSetId": "foundation.contracts.object-validation.consumer-v1",
+          "capabilityId": "foundation.contracts.object-validation",
+          "foundationVersion": "0.21.0",
+          "contractId": "skill-family-contracts:validateDocument",
+          "caseClass": "negative",
+          "strategy": "real-pure",
+          "request": {
+            "document": { "schemaVersion": 1, "kind": "skill-family.project-manifest", "project": { "id": "demo-project", "name": "Demo Project" }, "contracts": { "version": "not-a-version", "profile": "generic" } },
+            "options": { "schemaId": "https://contracts.skill-family.example/v1/project-manifest.json", "dialect": "2020-12", "policy": "strict" }
+          },
+          "expected": { "outcome": "return", "value": { "valid": false, "errorCode": "SFC1001", "errors": [{ "keyword": "pattern", "instancePath": "/contracts/version", "schemaPath": "#/properties/contracts/properties/version/pattern", "message": "must match pattern \"^[0-9]+\\.[0-9]+\\.[0-9]+$\"", "params": { "pattern": "^[0-9]+\\.[0-9]+\\.[0-9]+$" } }], "data": { "schemaVersion": 1, "kind": "skill-family.project-manifest", "project": { "id": "demo-project", "name": "Demo Project" }, "contracts": { "version": "not-a-version", "profile": "generic" } } } }
+        },
+        {
+          "schemaVersion": 1,
+          "kind": "skill-family.consumer-contract-vector",
+          "vectorId": "foundation.contracts.object-validation.consumer-v1.positive",
+          "vectorSetId": "foundation.contracts.object-validation.consumer-v1",
+          "capabilityId": "foundation.contracts.object-validation",
+          "foundationVersion": "0.21.0",
+          "contractId": "skill-family-contracts:validateDocument",
+          "caseClass": "positive",
+          "strategy": "real-pure",
+          "request": {
+            "document": { "schemaVersion": 1, "kind": "skill-family.project-manifest", "project": { "id": "demo-project", "name": "Demo Project" }, "contracts": { "version": "1.0.0", "profile": "generic" } },
+            "options": { "schemaId": "https://contracts.skill-family.example/v1/project-manifest.json", "dialect": "2020-12", "policy": "strict" }
+          },
+          "expected": { "outcome": "return", "value": { "valid": true, "errorCode": null, "errors": [], "data": { "schemaVersion": 1, "kind": "skill-family.project-manifest", "project": { "id": "demo-project", "name": "Demo Project" }, "contracts": { "version": "1.0.0", "profile": "generic" } } } }
+        }
+      ]
+    },
+    {
+      "capabilityId": "foundation.harness.atomic-write",
+      "vectorSetId": "foundation.harness.atomic-write.consumer-v1",
+      "contractId": "skill-family-harness-node:writeFileAtomic",
+      "strategy": "official-fake",
+      "vectors": [
+        {
+          "schemaVersion": 1,
+          "kind": "skill-family.consumer-contract-vector",
+          "vectorId": "foundation.harness.atomic-write.consumer-v1.indeterminate",
+          "vectorSetId": "foundation.harness.atomic-write.consumer-v1",
+          "capabilityId": "foundation.harness.atomic-write",
+          "foundationVersion": "0.21.0",
+          "contractId": "skill-family-harness-node:writeFileAtomic",
+          "caseClass": "indeterminate",
+          "strategy": "official-fake",
+          "request": { "root": { "runtimeBinding": "atomic-write-canonical-root" }, "relPath": "records/item.json", "data": "fixture-data", "options": { "mode": 420 } },
+          "expected": { "outcome": "indeterminate", "allowedStates": ["return", "throw"], "failClosed": true }
+        },
+        {
+          "schemaVersion": 1,
+          "kind": "skill-family.consumer-contract-vector",
+          "vectorId": "foundation.harness.atomic-write.consumer-v1.negative",
+          "vectorSetId": "foundation.harness.atomic-write.consumer-v1",
+          "capabilityId": "foundation.harness.atomic-write",
+          "foundationVersion": "0.21.0",
+          "contractId": "skill-family-harness-node:writeFileAtomic",
+          "caseClass": "negative",
+          "strategy": "official-fake",
+          "request": { "root": { "runtimeBinding": "atomic-write-canonical-root" }, "relPath": "../outside.json", "data": "fixture-data", "options": { "mode": 420 } },
+          "expected": { "outcome": "throw", "errorCode": "SFC2004", "errorKind": "path-traversal" }
+        },
+        {
+          "schemaVersion": 1,
+          "kind": "skill-family.consumer-contract-vector",
+          "vectorId": "foundation.harness.atomic-write.consumer-v1.positive",
+          "vectorSetId": "foundation.harness.atomic-write.consumer-v1",
+          "capabilityId": "foundation.harness.atomic-write",
+          "foundationVersion": "0.21.0",
+          "contractId": "skill-family-harness-node:writeFileAtomic",
+          "caseClass": "positive",
+          "strategy": "official-fake",
+          "request": { "root": { "runtimeBinding": "atomic-write-canonical-root" }, "relPath": "records/item.json", "data": "fixture-data", "options": { "mode": 420 } },
+          "expected": { "outcome": "return", "valueRelation": "atomic-write-contained-absolute-target" }
+        }
+      ]
+    }
+  ]
+}

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

@@ -0,0 +1,161 @@
+{
+  "schemaVersion": 1,
+  "kind": "skill-family.contracts.error-codes",
+  "contractsVersion": "1.18.0",
+  "policy": {
+    "format": "^SFC[0-9]{4}$",
+    "ranges": [
+      {
+        "prefix": "SFC1",
+        "category": "contract",
+        "note": "Contracts authority errors: schemas, registry, dialects, rules, fixtures."
+      },
+      {
+        "prefix": "SFC2",
+        "category": "kernel",
+        "note": "Kernel protocol operation errors."
+      },
+      {
+        "prefix": "SFC3",
+        "category": "report",
+        "note": "Report contract errors: digest binding, mandatory elements, fact drift. Style findings are never coded here; they are advisory output of the report check, not errors."
+      }
+    ],
+    "stability": "Codes are append-only. A frozen code is never reused for a different meaning; a deprecated code stays reserved. New codes require a contracts change."
+  },
+  "codes": [
+    {
+      "code": "SFC1001",
+      "name": "SCHEMA_VALIDATION_FAILED",
+      "category": "contract",
+      "stableSince": "1.0.0",
+      "meaning": "A document failed validation against its registered schema under the declared dialect and policy."
+    },
+    {
+      "code": "SFC1002",
+      "name": "UNKNOWN_SCHEMA_ID",
+      "category": "contract",
+      "stableSince": "1.0.0",
+      "meaning": "The referenced $id is not present in the schema registry."
+    },
+    {
+      "code": "SFC1003",
+      "name": "DUPLICATE_SCHEMA_ID",
+      "category": "contract",
+      "stableSince": "1.0.0",
+      "meaning": "Two schema registrations share the same $id; the registration is mechanically rejected."
+    },
+    {
+      "code": "SFC1004",
+      "name": "DUPLICATE_PROTOCOL_NAME",
+      "category": "contract",
+      "stableSince": "1.0.0",
+      "meaning": "Two protocol registrations share the same name and version; the registration is mechanically rejected."
+    },
+    {
+      "code": "SFC1005",
+      "name": "UNRESOLVED_REF",
+      "category": "contract",
+      "stableSince": "1.0.0",
+      "meaning": "A $ref target cannot be resolved within the registered schema set."
+    },
+    {
+      "code": "SFC1006",
+      "name": "UNSUPPORTED_DIALECT",
+      "category": "contract",
+      "stableSince": "1.0.0",
+      "meaning": "The declared JSON Schema dialect is not in the frozen supported dialect set."
+    },
+    {
+      "code": "SFC1007",
+      "name": "UNKNOWN_CHECK_TYPE",
+      "category": "contract",
+      "stableSince": "1.0.0",
+      "meaning": "A rule uses a check type outside the finite set of nine."
+    },
+    {
+      "code": "SFC1008",
+      "name": "RULE_BUDGET_EXCEEDED",
+      "category": "contract",
+      "stableSince": "1.0.0",
+      "meaning": "The mandatory rule count exceeds the first-version budget or the absolute cap."
+    },
+    {
+      "code": "SFC1009",
+      "name": "UNKNOWN_ERROR_CODE",
+      "category": "contract",
+      "stableSince": "1.0.0",
+      "meaning": "A fixture expectation references an error code that is not in this frozen registry."
+    },
+    {
+      "code": "SFC1010",
+      "name": "FIXTURE_EXPECTATION_MISMATCH",
+      "category": "contract",
+      "stableSince": "1.0.0",
+      "meaning": "A fixture did not behave as declared: a valid-expecting fixture failed, or an invalid-expecting fixture did not fail with the declared stable code."
+    },
+    {
+      "code": "SFC1011",
+      "name": "UNKNOWN_PROTOCOL",
+      "category": "contract",
+      "stableSince": "1.0.0",
+      "meaning": "A request references a protocol name/version that is not registered."
+    },
+    {
+      "code": "SFC1012",
+      "name": "SCHEMA_COMPILE_FAILED",
+      "category": "contract",
+      "stableSince": "1.0.0",
+      "meaning": "A registered schema does not compile under its declared dialect (the schema document itself is invalid)."
+    },
+    {
+      "code": "SFC1013",
+      "name": "CONSUMER_CONTRACT_VERSION_MISMATCH",
+      "category": "contract",
+      "stableSince": "1.14.0",
+      "meaning": "A consumer contract vector, capability identity, vector set, or Foundation package version does not match the installed Contracts package."
+    },
+    {
+      "code": "SFC2002",
+      "name": "UNKNOWN_OPERATION",
+      "category": "kernel",
+      "stableSince": "1.0.0",
+      "meaning": "The requested operation name is not in the frozen operation vocabulary of the referenced protocol version."
+    },
+    {
+      "code": "SFC2003",
+      "name": "INVALID_PARAMS",
+      "category": "kernel",
+      "stableSince": "1.0.0",
+      "meaning": "Operation params do not satisfy the frozen params contract of the requested operation."
+    },
+    {
+      "code": "SFC2004",
+      "name": "EXECUTION_FAILED",
+      "category": "kernel",
+      "stableSince": "1.0.0",
+      "meaning": "The mechanism runtime failed while executing a well-formed operation; details carry the mechanism evidence. Demonstrable only by a mechanism runtime, not by static contracts checks."
+    },
+    {
+      "code": "SFC3001",
+      "name": "REPORT_DIGEST_MISMATCH",
+      "category": "report",
+      "stableSince": "1.2.0",
+      "meaning": "A report binding digest (model, result, or report digest) does not match the recomputed sha256 digest, or the report is not the canonical render of its model; the binding is stale or tampered and is never trusted."
+    },
+    {
+      "code": "SFC3002",
+      "name": "REPORT_ELEMENT_MISSING",
+      "category": "report",
+      "stableSince": "1.2.0",
+      "meaning": "A mandatory report element is absent, empty where it must not be, or declared in an unsupported form: the conclusion, non-empty evidence, risks/next-action sections, a supported locale, or a coded outcome for failed/blocked runs. No half report is issued for a missing element."
+    },
+    {
+      "code": "SFC3003",
+      "name": "REPORT_FACT_DRIFT",
+      "category": "report",
+      "stableSince": "1.2.0",
+      "meaning": "A report model misstates the bound operation result's terminal state/errors, or rendered report bytes diverge from the deterministic re-render of the bound report model: fact fields rewritten, sections deleted, duplicated, or injected."
+    }
+  ]
+}