skill-family-engineering-kit 0.16.0 → 0.17.0

package/CHANGELOG.md

@@ -1,5 +1,27 @@
 # Changelog
 
+<!-- release-skill:changelog:start version=0.17.0 locale=en baseline=sha256:c09a3edaeab4e9f29527900bff5baaa7f7be185a9270ce81f450fab8ec9fb16f -->
+## [0.17.0] - 2026-09-01
+
+Engineering Kit 0.17.0 separates CodeBuddy from WorkBuddy host verification and adds an opt-in structural comparison against a provider-owned engineering baseline.
+
+### Added
+
+- Adds the codebuddy-print-v1 driver for CodeBuddy project discovery under .codebuddy/skills while preserving the existing workbuddy-codebuddy-print-v1 driver and WorkBuddy layout.
+- Adds describeSkeletonReferenceImplementation and returns its identity from scaffoldTarget.
+- Adds the paired adopt-plan options --engineering-baseline and --compare-skeleton. The result reports reference-only, target-only, entry-type, and file-class differences without declaring compliance, equivalence, severity, or waivers.
+
+### Changed
+
+- Adds skill-family-kit check entries --root . to the generated public-plugin check script; other profiles keep their existing check command.
+- Keeps host-managed login state, domain acceptance, and real-host qualification under consumer ownership.
+
+### Upgrade Notes
+
+Pin all three Foundation packages to exactly 0.17.0. CodeBuddy and WorkBuddy are separate host routes even when they consume the same plugin payload. Baseline comparison is read-only and opt-in; the baseline provider still owns rule semantics and publication.
+<!-- release-skill:changelog:end version=0.17.0 locale=en -->
+
+
 <!-- release-skill:changelog:start version=0.16.0 locale=en baseline=sha256:47c81698bf9458edc28ec1e198e43ad6f961db4249f606426a4b83664872a5d8 -->
 ## [0.16.0] - 2026-08-31
 

package/CHANGELOG.zh-CN.md

@@ -1,5 +1,27 @@
 # 变更日志
 
+<!-- release-skill:changelog:start version=0.17.0 locale=zh-CN baseline=sha256:7c413da3ad02837bdd63a1b49a5dc78cefe15a9779a05ce070876f817d09ae65 -->
+## [0.17.0] - 2026-09-01
+
+Engineering Kit 0.17.0 将 CodeBuddy 与 WorkBuddy 的宿主验证分开，并新增按需启用的提供方工程基线结构比较。
+
+### 新增
+
+- 新增 codebuddy-print-v1 driver，按 CodeBuddy 的 .codebuddy/skills 项目目录发现技能；既有 workbuddy-codebuddy-print-v1 driver 与 WorkBuddy 布局保持不变。
+- 新增 describeSkeletonReferenceImplementation，并由 scaffoldTarget 返回该参考骨架身份。
+- adopt-plan 新增须成对使用的 --engineering-baseline 与 --compare-skeleton。结果只报告参考侧独有、目标侧独有、条目类型和文件类别差异，不裁定合规、等价、严重程度或豁免。
+
+### 变更
+
+- public-plugin 骨架生成的 check 脚本新增 skill-family-kit check entries --root .；其他 Profile 的检查命令保持不变。
+- 宿主管理的登录态、领域验收和真实宿主资格继续归消费者负责。
+
+### 升级说明
+
+三个 Foundation 包须一起精确锁定到 0.17.0。CodeBuddy 与 WorkBuddy 即使消费同一插件载荷，也必须走独立宿主路由。基线比较只读且按需启用；规则语义与基线发布仍由基线提供方负责。
+<!-- release-skill:changelog:end version=0.17.0 locale=zh-CN -->
+
+
 <!-- release-skill:changelog:start version=0.16.0 locale=zh-CN baseline=sha256:1db170e8f4ae8ca25301b4e5893d86a0f486218fa75f9bcc0ced2a5eba7d26d6 -->
 ## [0.16.0] - 2026-08-31
 

package/README.md

@@ -4,23 +4,29 @@
 
 # skill-family-engineering-kit
 
-<!-- release-skill:release-version: 0.16.0 -->
+<!-- release-skill:release-version: 0.17.0 -->
 
 An engineering toolkit used in development and CI. There are **exactly four** top-level commands, and no fifth:
 
 <!-- release-skill:managed:start id=latest-release -->
-**0.16.0** (2026-08-31)
+**0.17.0** (2026-09-01)
 
-Engineering Kit 0.16.0 tightens the candidate host-verification regression around one common workload and consumer answer across five fixed drivers.
+Engineering Kit 0.17.0 separates CodeBuddy from WorkBuddy host verification and adds an opt-in structural comparison against a provider-owned engineering baseline.
+
+**Added**
+
+- Adds the codebuddy-print-v1 driver for CodeBuddy project discovery under .codebuddy/skills while preserving the existing workbuddy-codebuddy-print-v1 driver and WorkBuddy layout.
+- Adds describeSkeletonReferenceImplementation and returns its identity from scaffoldTarget.
+- Adds the paired adopt-plan options --engineering-baseline and --compare-skeleton. The result reports reference-only, target-only, entry-type, and file-class differences without declaring compliance, equivalence, severity, or waivers.
 
 **Changed**
 
-- Verifies that all five fixed host drivers consume the same candidate bindings and expose the caller's business answer through the existing runHostVerification path.
-- Keeps host-managed state, domain acceptance, and real-host qualification outside Foundation; no new Kit command or lifecycle capability is added.
+- Adds skill-family-kit check entries --root . to the generated public-plugin check script; other profiles keep their existing check command.
+- Keeps host-managed login state, domain acceptance, and real-host qualification under consumer ownership.
 
 **Upgrade Notes**
 
-The five-host check exercises the existing candidate API and does not turn a fixture or test result into real-host qualification. Consumers still own domain assertions and host authorization.
+Pin all three Foundation packages to exactly 0.17.0. CodeBuddy and WorkBuddy are separate host routes even when they consume the same plugin payload. Baseline comparison is read-only and opt-in; the baseline provider still owns rule semantics and publication.
 <!-- release-skill:managed:end id=latest-release -->
 
 ### Foundation 0.15.0 candidate qualification entries
@@ -50,7 +56,7 @@ Kit is the "engineering stage" layer, depending on the Harness and Contracts. It
 
 ## Installation and Minimal Example
 
-Version 0.16.0 is a local candidate. Build all three tarballs into one temporary directory and install those exact files for a candidate check:
+Version 0.17.0 is a local candidate. Build all three tarballs into one temporary directory and install those exact files for a candidate check:
 
 ```sh
 pack_dir="$(mktemp -d)"
@@ -58,21 +64,21 @@ pack_dir="$(mktemp -d)"
 (cd packages/skill-family-harness-node && pnpm pack --pack-destination "$pack_dir")
 (cd packages/skill-family-engineering-kit && pnpm pack --pack-destination "$pack_dir")
 mkdir "$pack_dir/consumer" && (cd "$pack_dir/consumer" && npm init -y)
-(cd "$pack_dir/consumer" && npm install "$pack_dir/skill-family-contracts-0.16.0.tgz" "$pack_dir/skill-family-harness-node-0.16.0.tgz" "$pack_dir/skill-family-engineering-kit-0.16.0.tgz")
+(cd "$pack_dir/consumer" && npm install "$pack_dir/skill-family-contracts-0.17.0.tgz" "$pack_dir/skill-family-harness-node-0.17.0.tgz" "$pack_dir/skill-family-engineering-kit-0.17.0.tgz")
 ```
 
 After publication, use the registry coordinate:
 
 ```sh
-npm install --save-dev skill-family-engineering-kit@0.16.0
-npm exec --package=skill-family-engineering-kit@0.16.0 -- skill-family-kit --help
-npm exec --package=skill-family-engineering-kit@0.16.0 -- skill-family-kit scaffold --root <empty-dir> --project-id my-project
-npm exec --package=skill-family-engineering-kit@0.16.0 -- skill-family-kit adopt-plan --root <repo> --list-capabilities --all --scope all --locale en --uses ./uses.json
-npm exec --package=skill-family-engineering-kit@0.16.0 -- skill-family-kit projection --root <repo>
-npm exec --package=skill-family-engineering-kit@0.16.0 -- skill-family-kit check --root <repo>
+npm install --save-dev skill-family-engineering-kit@0.17.0
+npm exec --package=skill-family-engineering-kit@0.17.0 -- skill-family-kit --help
+npm exec --package=skill-family-engineering-kit@0.17.0 -- skill-family-kit scaffold --root <empty-dir> --project-id my-project
+npm exec --package=skill-family-engineering-kit@0.17.0 -- skill-family-kit adopt-plan --root <repo> --list-capabilities --all --scope all --locale en --uses ./uses.json
+npm exec --package=skill-family-engineering-kit@0.17.0 -- skill-family-kit projection --root <repo>
+npm exec --package=skill-family-engineering-kit@0.17.0 -- skill-family-kit check --root <repo>
 ```
 
-The four commands above cover skeleton generation, read-only inventory, managed projection, and diagnostics respectively; a zero-install form is available via `npm exec --package=skill-family-engineering-kit@0.16.0 -- skill-family-kit --help`.
+The four commands above cover skeleton generation, read-only inventory, managed projection, and diagnostics respectively; a zero-install form is available via `npm exec --package=skill-family-engineering-kit@0.17.0 -- skill-family-kit --help`.
 
 ### Three adoption journeys
 
@@ -291,4 +297,4 @@ The candidate `runPluginVerification({ request, bindings, hostsRoot })` preserve
 
 The separate `runSkillFamilyDirectoryVerification({ request, bindings })` entry fixes the Kimi production argv and narrow environment and rejects caller observation. Its raw parser is exercised through the production process path, but no controlled fixture event is promoted to `observed`; without an official typed mapping, the public result remains `indeterminate` and a manual candidate.
 
-Version 0.16.0 is a local source candidate and is not published. Consume the three locally verified tarballs; a version marker, unit test or successful install is not complete contract integration, migration completion, or real-host qualification.
+Version 0.17.0 is a local source candidate and is not published. Consume the three locally verified tarballs; a version marker, unit test or successful install is not complete contract integration, migration completion, or real-host qualification.

package/README.zh-CN.md

@@ -5,23 +5,29 @@
 
 # skill-family-engineering-kit
 
-<!-- release-skill:release-version: 0.16.0 -->
+<!-- release-skill:release-version: 0.17.0 -->
 
 开发与 CI 阶段使用的工程工具包。**恰好四个**顶层命令，没有第五个：
 
 <!-- release-skill:managed:start id=latest-release -->
-**0.16.0** (2026-08-31)
+**0.17.0** (2026-09-01)
 
-Engineering Kit 0.16.0 收紧五个固定 driver 的候选宿主验证回归，要求共用一个 workload 并核对消费者业务答案。
+Engineering Kit 0.17.0 将 CodeBuddy 与 WorkBuddy 的宿主验证分开，并新增按需启用的提供方工程基线结构比较。
+
+**新增**
+
+- 新增 codebuddy-print-v1 driver，按 CodeBuddy 的 .codebuddy/skills 项目目录发现技能；既有 workbuddy-codebuddy-print-v1 driver 与 WorkBuddy 布局保持不变。
+- 新增 describeSkeletonReferenceImplementation，并由 scaffoldTarget 返回该参考骨架身份。
+- adopt-plan 新增须成对使用的 --engineering-baseline 与 --compare-skeleton。结果只报告参考侧独有、目标侧独有、条目类型和文件类别差异，不裁定合规、等价、严重程度或豁免。
 
 **变更**
 
-- 通过既有 `runHostVerification` 路径核对 Claude、Codex、Kimi、Qoder 与 WorkBuddy 使用同一候选绑定，并暴露调用方的业务答案。
-- 保持宿主管理状态、领域接受规则和真实宿主资格归调用方负责；不新增 Kit 命令或生命周期能力。
+- public-plugin 骨架生成的 check 脚本新增 skill-family-kit check entries --root .；其他 Profile 的检查命令保持不变。
+- 宿主管理的登录态、领域验收和真实宿主资格继续归消费者负责。
 
 **升级说明**
 
-五宿主检查只验证现有候选 API，不会把 fixture 或测试结果升级为真实宿主资格；领域断言与宿主授权仍由消费者负责。
+三个 Foundation 包须一起精确锁定到 0.17.0。CodeBuddy 与 WorkBuddy 即使消费同一插件载荷，也必须走独立宿主路由。基线比较只读且按需启用；规则语义与基线发布仍由基线提供方负责。
 <!-- release-skill:managed:end id=latest-release -->
 
 ### Foundation 0.15.0 candidate 资格入口
@@ -51,7 +57,7 @@ Kit 是「工程阶段」层，依赖 Harness 与 Contracts。它只做四件事
 
 ## 安装和最小示例
 
-0.16.0 是本地候选版本。候选验证先把三个包分别打入同一个临时目录，再安装这三个精确 tarball：
+0.17.0 是本地候选版本。候选验证先把三个包分别打入同一个临时目录，再安装这三个精确 tarball：
 
 ```sh
 pack_dir="$(mktemp -d)"
@@ -59,21 +65,21 @@ pack_dir="$(mktemp -d)"
 (cd packages/skill-family-harness-node && pnpm pack --pack-destination "$pack_dir")
 (cd packages/skill-family-engineering-kit && pnpm pack --pack-destination "$pack_dir")
 mkdir "$pack_dir/consumer" && (cd "$pack_dir/consumer" && npm init -y)
-(cd "$pack_dir/consumer" && npm install "$pack_dir/skill-family-contracts-0.16.0.tgz" "$pack_dir/skill-family-harness-node-0.16.0.tgz" "$pack_dir/skill-family-engineering-kit-0.16.0.tgz")
+(cd "$pack_dir/consumer" && npm install "$pack_dir/skill-family-contracts-0.17.0.tgz" "$pack_dir/skill-family-harness-node-0.17.0.tgz" "$pack_dir/skill-family-engineering-kit-0.17.0.tgz")
 ```
 
 发布后再使用 registry 坐标：
 
 ```sh
-npm install --save-dev skill-family-engineering-kit@0.16.0
-npm exec --package=skill-family-engineering-kit@0.16.0 -- skill-family-kit --help
-npm exec --package=skill-family-engineering-kit@0.16.0 -- skill-family-kit scaffold --root <empty-dir> --project-id my-project
-npm exec --package=skill-family-engineering-kit@0.16.0 -- skill-family-kit adopt-plan --root <repo> --list-capabilities --all --scope all --locale zh-CN --uses ./uses.json
-npm exec --package=skill-family-engineering-kit@0.16.0 -- skill-family-kit projection --root <repo>
-npm exec --package=skill-family-engineering-kit@0.16.0 -- skill-family-kit check --root <repo>
+npm install --save-dev skill-family-engineering-kit@0.17.0
+npm exec --package=skill-family-engineering-kit@0.17.0 -- skill-family-kit --help
+npm exec --package=skill-family-engineering-kit@0.17.0 -- skill-family-kit scaffold --root <empty-dir> --project-id my-project
+npm exec --package=skill-family-engineering-kit@0.17.0 -- skill-family-kit adopt-plan --root <repo> --list-capabilities --all --scope all --locale zh-CN --uses ./uses.json
+npm exec --package=skill-family-engineering-kit@0.17.0 -- skill-family-kit projection --root <repo>
+npm exec --package=skill-family-engineering-kit@0.17.0 -- skill-family-kit check --root <repo>
 ```
 
-以上四条命令分别覆盖生成骨架、只读盘点、受管投影与诊断；零安装形式可用 `npm exec --package=skill-family-engineering-kit@0.16.0 -- skill-family-kit --help`。
+以上四条命令分别覆盖生成骨架、只读盘点、受管投影与诊断；零安装形式可用 `npm exec --package=skill-family-engineering-kit@0.17.0 -- skill-family-kit --help`。
 
 ### 三条采用旅程
 
@@ -292,4 +298,4 @@ Foundation 本身不发起网络请求，但绑定的 executable 仍可能联网
 
 独立入口 `runSkillFamilyDirectoryVerification({ request, bindings })` 固定 Kimi 生产 argv 与窄环境，并拒绝调用方 observation。原始 parser 通过生产进程路径验证，但受控 fixture 事件不会被提升为 `observed`；缺少官方 typed mapping 时，公共结果保持 `indeterminate` 和 manual candidate。
 
-0.16.0 为本地源码候选，尚未发布。消费本地已验证的三包 tarball；版本标记、单元测试或安装成功都不等于契约接入完成、迁移完成或真实宿主资格。
+0.17.0 为本地源码候选，尚未发布。消费本地已验证的三包 tarball；版本标记、单元测试或安装成功都不等于契约接入完成、迁移完成或真实宿主资格。

package/data/capability-catalog/capability-catalog.json

@@ -702,6 +702,7 @@
    "entrypoints": [
     "scaffoldTarget (packages/skill-family-engineering-kit/src/scaffold.mjs)",
     "describeSkeletonFiles (packages/skill-family-engineering-kit/src/skeleton.mjs)",
+    "describeSkeletonReferenceImplementation (packages/skill-family-engineering-kit/src/skeleton.mjs)",
     "normalizeSkeletonInputs (packages/skill-family-engineering-kit/src/skeleton.mjs)"
    ],
    "sourceRefs": [

package/data/hosts/codebuddy/host-descriptor.json

@@ -5,6 +5,11 @@
   "displayName": "CodeBuddy",
   "support": "manual",
   "maturity": "manual",
+  "verification": {
+    "driverId": "codebuddy-print-v1",
+    "authStrategy": "existing-user-state",
+    "credentialMutation": "host-managed"
+  },
   "sourceAliases": [],
   "pathCategories": [],
   "probeCapabilities": [

package/docs/agents/capability-catalog.json

@@ -702,6 +702,7 @@
    "entrypoints": [
     "scaffoldTarget (packages/skill-family-engineering-kit/src/scaffold.mjs)",
     "describeSkeletonFiles (packages/skill-family-engineering-kit/src/skeleton.mjs)",
+    "describeSkeletonReferenceImplementation (packages/skill-family-engineering-kit/src/skeleton.mjs)",
     "normalizeSkeletonInputs (packages/skill-family-engineering-kit/src/skeleton.mjs)"
    ],
    "sourceRefs": [

package/docs/architecture/index.html

@@ -1980,6 +1980,7 @@ Contracts（结构、协议、错误码、协议名登记）
 - release-skill   发布状态与全部远端写入，不进入 Foundation
 - Artifact Graph  `artifacts/` 架构制品体系，门禁为 check:artifacts
 </code></pre>
+<p>同一 Git workspace 还包含 <code>packages/foundation-adoption-review/</code>。它是一个独立的 0.1.0 Plugin release unit 和公开镜像源，使用 Foundation 的公开事实，但不属于 Contracts → Harness → Engineering Kit 依赖链，也不计作 Foundation 的第四个机制包。该 Plugin 的公开闭包由自己的 release unit 白名单限定；根目录的计划、制品、测试和其他私有文档不会进入 Plugin 镜像。</p>
 <p>箭头指向被依赖方。公共核心不得反向依赖具体 Profile 或具体技能族；新能力的依赖方向落位见 <code>artifacts/design/FND-DES-001.md</code>，逐资产归属见 FND-ADR-002。</p>
 <h2 id="职责矩阵">职责矩阵<a class="headerlink" href="#职责矩阵" title="Permanent link">&para;</a></h2>
 <p>每个分层只承担下表列出的职责，越界能力一律由外部项目或消费者拥有。</p>
@@ -1994,7 +1995,7 @@ Contracts（结构、协议、错误码、协议名登记）
 <tbody>
 <tr>
 <td>Contracts</td>
-<td>结构、协议、错误码、协议名登记；39 类顶层对象；9 条 mandatory rule</td>
+<td>结构、协议、错误码、协议名登记；46 类顶层对象；9 条 mandatory rule</td>
 <td>业务字段语义、领域审计、远端写入、模型生成</td>
 </tr>
 <tr>
@@ -2086,9 +2087,9 @@ Contracts（结构、协议、错误码、协议名登记）
 <li><strong>任务生命周期</strong>：loop-agent 拥有任务、重试、返工、验收；Foundation 不含 workflow 状态机（<code>foundation.unsupported.business-state-machine</code>）。</li>
 <li><strong>制品治理</strong>：artifact-graph 拥有 <code>artifacts/</code> 关系合同与版本锁，门禁为 <code>check:artifacts</code>。</li>
 <li><strong>领域审计</strong>：独立审计消费者拥有语义与最终接受/拒绝；Foundation 只提供确定性审计表面（<code>foundation.unsupported.domain-audit-semantics</code>）。</li>
-<li><strong>宿主应用与生命周期</strong>：有限 host identity/alias 解析、独立 probe facts 与本地 install/update 复用既有绑定读取和发布原语；uninstall 因缺少安全绑定删除原语而拒绝并转人工恢复。Qoder 仍为 unsupported，DeepSeek Harness 仅为 developer-preview 身份事实；远端发布、自动信任和消费者 smoke 不在 Foundation（<code>foundation.unsupported.qoder-driver</code>）。</li>
+<li><strong>宿主应用与生命周期</strong>：宿主拥有自身语义与生命周期行为；Foundation 只统一结构性差异，提供有限 host identity/alias 解析、受收容本地投影、绑定读取、原子写入和固定 driver 的受约束验证。只有 Descriptor 的 <code>support=supported</code> 时，<code>planHost</code> 才可能产出 <code>status=planned</code> 的 install/update 计划；Qoder 等 <code>support=manual</code> 宿主返回空的 <code>status=manual</code> 计划，<code>applyHostPlan</code> 对该计划返回 <code>rejected</code> 与 <code>publicationState=not-attempted</code>。<code>applyHostPlan</code> 只执行 <code>status=planned</code> 的计划；install/update 仍须摘要绑定、已验证 build 和显式授权，uninstall 返回 <code>manual-recovery-required</code> 且不删除文件。真实宿主验证使用六个封闭内置 driver，按固定参数执行 fresh、受约束调用，并复用 <code>existing-user-state + host-managed</code>。技能族（调用方）根据基础设施观察和业务答案解释业务结果并作最终领域验收。Qoder 的 Descriptor 为 <code>manual</code>，<code>qodercli-print-v1</code> 是 <code>candidate</code> 真实验证 driver；WorkBuddy 与 CodeBuddy 各用独立 driver 和发现布局。真实用户环境中的发布后插件发现、安装、更新、marketplace 与发布状态由 release-skill 管理。</li>
 <li><strong>同级适配器只读验证</strong>：Contracts 1.10.0 增加成熟度中立的 request/result；Harness 复用真实根绑定、路径收容、读取、闭包和 manifest，按 peer 归一化后验证共同来源与唯一 <code>SKILL.md</code> mapping；Kit 只提供薄入口。Foundation 不拥有 canonical source，不写目录，不产生 receipt，也不接管旧 manifest 的业务迁移。</li>
-<li><strong>真实宿主验证</strong>：Contracts 1.11.0 增加 <code>host-verification-request</code> 与 <code>host-verification-result</code>；Harness 在既有 <code>superviseProcess</code> 上提供原始字节 sink，Kit 实现 Kimi 与 WorkBuddy 两个内置 candidate driver（均绑定 <code>existing-user-state + host-managed</code>）的受约束执行、现有用户状态根边界与结果组合。Foundation 不拥有领域输出或发布状态，也不宣称认证状态隔离、凭证未变化、模型身份固定或宿主工具能力已关闭。</li>
+<li><strong>真实宿主验证</strong>：Contracts 1.11.0 增加 <code>host-verification-request</code> 与 <code>host-verification-result</code>；Harness 在既有 <code>superviseProcess</code> 上提供原始字节 sink，Kit 维护六个封闭内置 candidate driver：其中包含 <code>qodercli-print-v1</code>、WorkBuddy 与 CodeBuddy 各自独立的 driver，以及另外三个已登记 driver。调用方创建、提供并独占本次验证所需的 fresh roots，完成检查后清理其独占的外层 <code>temporaryRoot</code>；Foundation 只在该根下创建并保留受跟踪的 session root。Foundation 校验 canonical/fresh 路径、路径收容、根重叠隔离、摘要与 Descriptor/driver 绑定，再按固定参数执行受约束调用；这些路径检查是路径边界，不是 OS sandbox。调用方根据基础设施观察和业务答案作最终领域验收。WorkBuddy 与 CodeBuddy 的 driver、发现目录和工作目录保持独立。Foundation 返回基础设施观察结果，不拥有领域输出、发布状态或真实用户环境中的插件发布后行为，也不宣称认证状态隔离、凭证未变化、模型身份固定或宿主工具能力已关闭。</li>
 </ul>
 <h2 id="能力身份与成熟度">能力身份与成熟度<a class="headerlink" href="#能力身份与成熟度" title="Permanent link">&para;</a></h2>
 <p>能力身份和成熟度是两个维度（FND-ADR-016）。历史 <code>./candidate/**</code> 消费者迁移一次到 0.10.0 提供的规范入口；旧入口
@@ -2100,15 +2101,15 @@ operation。后续晋升 stable 只提高兼容承诺，不再触发消费者源
 <h2 id="下一阶段能力线架构-hand-off">下一阶段能力线（架构 hand-off）<a class="headerlink" href="#下一阶段能力线架构-hand-off" title="Permanent link">&para;</a></h2>
 <p>三条能力线均经 FND-ADR-001 能力纳入门裁决纳入，全部在既有分层内落位：</p>
 <ul>
-<li><strong>宿主接入线</strong>（FND-FR-001/FND-FR-002，FND-ADR-003，FND-ADR-017）：Contracts 1.10.0 在既有 stable descriptor/probe/plan/receipt 合同上补足有限成熟度、手动事实与 digest 绑定的操作约束；Harness 复用 source closure、绑定读取、严格发布和原子替换；Kit 注入有限 Profile 与两类受信 driver。0.10.0 提供 describe/build/probe/plan 及受显式授权保护的本地 install/update；uninstall 保持人工恢复拒绝。0.11.0 追加独立的真实宿主验证候选，登记 Kimi 与 WorkBuddy 两个内置 driver，复用现有登录态。</li>
+<li><strong>宿主接入线</strong>（FND-FR-001/FND-FR-002，FND-ADR-003，FND-ADR-017）：Contracts 1.10.0 在既有 stable descriptor/probe/plan/receipt 合同上补足有限成熟度、手动事实与 digest 绑定的操作约束；Harness 复用 source closure、受收容本地投影、绑定读取、严格发布和原子替换；Kit 注入有限 Profile 与六个封闭内置 driver。只有 <code>support=supported</code> 的 Descriptor 才能让 <code>planHost</code> 产出 <code>status=planned</code> 的 install/update 计划；manual 宿主得到空的 <code>status=manual</code> 计划，<code>applyHostPlan</code> 返回 <code>rejected</code> / <code>not-attempted</code>。现有公共 API 保留 <code>planHost</code> / <code>applyHostPlan</code>，planned 计划仍须摘要绑定、已验证 build 和显式授权。真实宿主验证由调用方创建并独占 fresh roots，Foundation 校验 canonical/fresh、收容、重叠隔离、摘要与 Descriptor/driver 绑定并按固定参数调用；调用方根据基础设施观察和业务答案作最终领域验收。Qoder 的 Descriptor 为 <code>manual</code>，<code>qodercli-print-v1</code> 为 <code>candidate</code> 真实验证 driver；WorkBuddy 与 CodeBuddy 使用独立 driver 和发现布局。真实用户环境的发布后插件发现、安装、更新、marketplace 与发布状态由 release-skill 管理。</li>
 <li><strong>持久状态底座线</strong>（FND-FR-003，FND-ADR-004）：append-only 事件、hash chain、快照与校验恢复；只提供状态底座，状态机、任务节点、重试、终态、记忆等业务语义不纳入 Foundation。</li>
 <li><strong>人类报告线</strong>（FND-FR-004，FND-ADR-005）：双层合同——机器结果是唯一真源，人类报告由机器结果确定性渲染（Markdown + digest 绑定 + 分级检查），不自由撰写。</li>
 <li><strong>有限封闭语义工具线</strong>（FND-ADR-009）：基线物化 + contentGuard（摘要不符、物化中途变化、守卫检出均失败关闭）、通用只读 chokepoint（允许根集合 + 可选身份谓词）、策略化表面扫描（策略契约 + 注入式自测）、token 上界估算（确定性领域估算原语，无模型/网络/tokenizer 依赖）、通用上限守卫（复用 state-store 事件账与 token-lock，上限与超限策略由消费者配置）。</li>
 </ul>
-<p>三包结构保持、不拆第四包（FND-ADR-007）；制品治理采用 artifact-graph CLI 与版本锁（FND-ADR-006）。</p>
+<p>三包机制结构保持、不拆第四个机制包（FND-ADR-007）；同一 workspace 内的独立 Plugin release unit 不改变这条依赖链。制品治理采用 artifact-graph CLI 与版本锁（FND-ADR-006）。</p>
 <h2 id="首版预算">首版预算<a class="headerlink" href="#首版预算" title="Permanent link">&para;</a></h2>
 <ul>
-<li>顶层 Contracts 对象：45 类（完整清单以 <code>packages/skill-family-contracts/src/registry.json</code> 为唯一真源）：project-manifest、profile-descriptor、project-profile（FND-ADR-013，1.7.0 纳入）、managed-file-lock、operation-request、operation-result、migration-manifest、adapter-source、report-model、report-binding、host-descriptor、host-registry、host-capability-fact、host-probe-result、adapter-build-manifest、host-operation-plan、host-operation-receipt、state-event-envelope、state-snapshot-metadata、token-estimate-result、surface-scan-policy、declared-read-surface-result、structured-scan-policy（FND-ADR-010/011）、timeout-policy、watchdog-termination-envelope（FND-ADR-012，append-only 保持 1.5.0）、public-boundary-declaration、platform-difference-registry、observation-scope、profile-adoption-declaration、audit-baseline-pin、token-estimate-record（审计规则裁决与整改 1.6.0 纳入）、source-authority-receipt（1.8.0 纳入）、filesystem-root-binding、fixed-set-publication-manifest、fixed-set-publication-receipt（1.9.0 纳入）、adapter-peer-verification-request、adapter-peer-verification-result（FND-ADR-018，1.10.0 纳入）、host-verification-request、host-verification-result（FND-ADR-019，1.11.0 纳入）、plugin-verification-request、plugin-verification-result、filesystem-tree-observation（FND-ADR-021，1.13.0 纳入）、executable-identity-observation、skill-family-directory-verification-request、skill-family-directory-verification-result；</li>
+<li>顶层 Contracts 对象：46 类（完整清单以 <code>packages/skill-family-contracts/src/registry.json</code> 为唯一真源）：project-manifest、profile-descriptor、project-profile（FND-ADR-013，1.7.0 纳入）、managed-file-lock、operation-request、operation-result、migration-manifest、adapter-source、report-model、report-binding、host-descriptor、host-registry、host-capability-fact、host-probe-result、adapter-build-manifest、host-operation-plan、host-operation-receipt、state-event-envelope、state-snapshot-metadata、token-estimate-result、surface-scan-policy、declared-read-surface-result、structured-scan-policy（FND-ADR-010/011）、timeout-policy、watchdog-termination-envelope（FND-ADR-012，append-only 保持 1.5.0）、public-boundary-declaration、platform-difference-registry、observation-scope、profile-adoption-declaration、audit-baseline-pin、token-estimate-record（审计规则裁决与整改 1.6.0 纳入）、source-authority-receipt（1.8.0 纳入）、filesystem-root-binding、fixed-set-publication-manifest、fixed-set-publication-receipt（1.9.0 纳入）、adapter-peer-verification-request、adapter-peer-verification-result（FND-ADR-018，1.10.0 纳入）、host-verification-request、host-verification-result（FND-ADR-019，1.11.0 纳入）、plugin-verification-request、plugin-verification-result、filesystem-tree-observation（FND-ADR-021，1.13.0 纳入）、executable-identity-observation、skill-family-directory-verification-request、skill-family-directory-verification-result、engineering-baseline；</li>
 <li>Kit 顶层命令：4 个（scaffold、adopt-plan、projection、check）；</li>
 <li>强制机械规则：当前 9 条，预算不超过 20 条，绝对上限 30 条；CR-001 对登记表内全部 Schema 做统一编译；</li>
 <li>叶子包：3 个（skill-family-contracts、skill-family-harness-node、skill-family-engineering-kit）；</li>

package/docs/en/architecture/index.html

@@ -1980,6 +1980,7 @@ Horizontal (attachment surfaces, no new vertical layers):
 - release-skill   release state and all remote writes; does not enter Foundation
 - Artifact Graph  the `artifacts/` architecture artifact system; its gate is check:artifacts
 </code></pre>
+<p>The same Git workspace also contains <code>packages/foundation-adoption-review/</code>. It is an independent 0.1.0 Plugin release unit and public-mirror source. It consumes Foundation's public facts, but it is not part of the Contracts → Harness → Engineering Kit dependency chain and does not count as a fourth Foundation mechanism package. Its public closure is restricted by that release unit's own allowlist; the root's private plans, artifacts, tests, and other documents do not enter the Plugin mirror.</p>
 <p>Arrows point to the depended-upon party. The public core must not depend in reverse on a concrete Profile or a concrete skill family; where a new capability's dependency direction lands is specified in <code>artifacts/design/FND-DES-001.md</code>, and asset-by-asset ownership is in FND-ADR-002.</p>
 <h2 id="Responsibility-Matrix">Responsibility Matrix<a class="headerlink" href="#Responsibility-Matrix" title="Permanent link">&para;</a></h2>
 <p>Each layer assumes only the responsibilities listed below; out-of-scope capabilities are owned by external projects or consumers.</p>
@@ -1994,7 +1995,7 @@ Horizontal (attachment surfaces, no new vertical layers):
 <tbody>
 <tr>
 <td>Contracts</td>
-<td>Structure, protocols, error codes, protocol-name registry; 37 top-level object kinds; 9 mandatory rules</td>
+<td>Structure, protocols, error codes, protocol-name registry; 46 top-level object kinds; 9 mandatory rules</td>
 <td>Business-field semantics, domain auditing, remote writes, model generation</td>
 </tr>
 <tr>
@@ -2088,7 +2089,7 @@ Carries limited domain semantics? ──yes──▶ finite closed semantics: co
 <li><strong>Task lifecycle</strong>: owned by loop-agent (tasks, retries, rework, acceptance); Foundation contains no workflow state machine (<code>foundation.unsupported.business-state-machine</code>).</li>
 <li><strong>Artifact governance</strong>: artifact-graph owns the <code>artifacts/</code> relationship contract and version-lock; its gate is <code>check:artifacts</code>.</li>
 <li><strong>Domain auditing</strong>: an independent audit consumer owns the semantics and final accept/reject; Foundation provides only a deterministic audit surface (<code>foundation.unsupported.domain-audit-semantics</code>).</li>
-<li><strong>Host apply and lifecycle</strong>: the package API <code>applyHostPlan</code> supports digest-bound local install/update for registered supported hosts. Executing an uninstall plan returns <code>manual-recovery-required</code> without deleting files. The four-command Kit CLI, generic or remote apply, and the full Qoder driver remain unsupported (<code>foundation.unsupported.host-apply</code>, <code>foundation.unsupported.host-install-update-uninstall</code>, <code>foundation.unsupported.qoder-driver</code>).</li>
+<li><strong>Host application and lifecycle</strong>: Hosts own their semantics and lifecycle behavior. Foundation only unifies structural differences through bounded host identity/alias resolution, contained local projection, bound reads, atomic writes, and fixed-driver constrained verification. Only a Descriptor with <code>support=supported</code> can make <code>planHost</code> produce an install/update plan with <code>status=planned</code>; a <code>support=manual</code> host such as Qoder receives an empty <code>status=manual</code> plan, and <code>applyHostPlan</code> returns <code>rejected</code> with <code>publicationState=not-attempted</code> for it. <code>applyHostPlan</code> executes only <code>status=planned</code> plans; install/update still requires digest binding, a verified build, and explicit authorization, while uninstall returns <code>manual-recovery-required</code> without deleting files. Real-host verification uses six closed built-in drivers with fixed-argument, fresh, constrained calls and <code>existing-user-state + host-managed</code>. The skill family (caller) interprets business results and performs final domain acceptance from infrastructure observations and business answers. Qoder's Descriptor is <code>manual</code>, and <code>qodercli-print-v1</code> is a <code>candidate</code> real-verification driver. WorkBuddy and CodeBuddy use separate drivers and discovery layouts. Post-publish plugin discovery, installation, updates, marketplace operations, and release state in real user environments are managed by release-skill.</li>
 </ul>
 <h2 id="Capability-Identity-and-Maturity">Capability Identity and Maturity<a class="headerlink" href="#Capability-Identity-and-Maturity" title="Permanent link">&para;</a></h2>
 <p>Capability identity and maturity are separate dimensions (FND-ADR-016). Consumers of historical <code>./candidate/**</code> entrypoints migrate once to the canonical entrypoints introduced in 0.10.0, while the old entrypoints remain same-source compatibility surfaces during deprecation. Capabilities introduced from 0.10.0 onward use their final canonical entrypoint, Schema <code>$id</code>, and operation from the first candidate release. Stable promotion changes the compatibility promise only and does not trigger another source or contract-identity migration. A consumer must still update all three exact package pins to obtain a newly published stable promise. Existing package-identity, source-digest, and provenance bindings continue to determine whether a Bundle rebuild is required; the maturity label does not add a separate rebuild condition.</p>
@@ -2096,15 +2097,15 @@ Carries limited domain semantics? ──yes──▶ finite closed semantics: co
 <h2 id="Next-Phase-Capability-Lines-Architecture-Hand-off">Next-Phase Capability Lines (Architecture Hand-off)<a class="headerlink" href="#Next-Phase-Capability-Lines-Architecture-Hand-off" title="Permanent link">&para;</a></h2>
 <p>All three capability lines were included via the FND-ADR-001 capability admission-gate adjudication and all land within the existing layers:</p>
 <ul>
-<li><strong>Host-access line</strong> (FND-FR-001/FND-FR-002/FND-FR-008/FND-FR-009): Contracts registers descriptor/source/manifest/probe/plan/receipt and peer-verification request/result; Harness implements generic source closure, atomic build/materialize, probe classification, and read-only peer verification; Kit injects the concrete Profile and trusted driver. The package API supports bounded local install/update through <code>applyHostPlan</code>; uninstall execution remains non-destructive and requires manual recovery. Kit CLI apply and generic or remote apply remain refused.</li>
+<li><strong>Host-access line</strong> (FND-FR-001/FND-FR-002/FND-FR-008/FND-FR-009): Contracts registers descriptor/source/manifest/probe/plan/receipt and peer-verification request/result; Harness implements generic source closure, contained local projection, atomic build/materialize, probe classification, and read-only peer verification; Kit injects the concrete Profile and six closed built-in drivers, including <code>qodercli-print-v1</code>, separate WorkBuddy and CodeBuddy drivers, and three other registered drivers. Only a Descriptor with <code>support=supported</code> can yield an install/update plan with <code>status=planned</code>; manual hosts receive an empty <code>status=manual</code> plan, and <code>applyHostPlan</code> returns <code>rejected</code> / <code>not-attempted</code>. The public API retains <code>planHost</code> / <code>applyHostPlan</code>; a planned install/update still requires digest binding, a verified build, and explicit authorization, while uninstall remains non-destructive and requires manual recovery. Callers create, provide, and exclusively own the fresh roots and clean up their outer <code>temporaryRoot</code>; Foundation creates and retains only the tracked session root beneath it. Foundation validates canonical/fresh paths, containment, overlap isolation, digest and Descriptor/driver binding, then runs the fixed-argument constrained call. These path checks are boundaries, not an OS sandbox. Callers use the infrastructure observations and business answers for final domain acceptance. Qoder's Descriptor is <code>manual</code>, and <code>qodercli-print-v1</code> is a <code>candidate</code> real-verification driver; WorkBuddy and CodeBuddy keep separate drivers and discovery layouts. Post-publish plugin discovery, installation, updates, marketplace operations, and release state in real user environments remain release-skill responsibilities.</li>
 <li><strong>Durable state-substrate line</strong> (FND-FR-003, FND-ADR-004): append-only events, hash chain, snapshots, and verification recovery; provides only the state substrate, not business semantics such as state machines, task nodes, retries, terminal states, or memory.</li>
 <li><strong>Human-report line</strong> (FND-FR-004, FND-ADR-005): a two-layer contract — machine results are the sole source of truth, and the human report is deterministically rendered from machine results (Markdown + digest binding + graded checks), not freely authored.</li>
 <li><strong>Finite-closed-semantics tools line</strong> (FND-ADR-009): baseline materialization + contentGuard (digest mismatch, mid-materialization change, and guard rejection all fail closed), generic read chokepoint (allowed-root set + optional identity predicate), strategy-driven surface scan (policy contract + injection self-test), token upper-bound estimation (deterministic estimation primitive with no model/network/tokenizer dependency), and a generic upper-bound guard (reusing the state-store event ledger and token-lock; the bound and over-limit policy are consumer-configured).</li>
 </ul>
-<p>The three-package structure is preserved and a fourth package is not split out (FND-ADR-007); artifact governance uses the artifact-graph CLI and version-lock (FND-ADR-006).</p>
+<p>The three mechanism-package structure is preserved and a fourth mechanism package is not split out (FND-ADR-007); the independent Plugin release unit in the same workspace does not change this dependency chain. Artifact governance uses the artifact-graph CLI and version-lock (FND-ADR-006).</p>
 <h2 id="First-Version-Budget">First-Version Budget<a class="headerlink" href="#First-Version-Budget" title="Permanent link">&para;</a></h2>
 <ul>
-<li>Top-level Contracts objects: 42 kinds, including the three 1.13.0 candidate objects <code>plugin-verification-request</code>, <code>plugin-verification-result</code>, and <code>filesystem-tree-observation</code>, with <code>packages/skill-family-contracts/src/registry.json</code> as the sole source of truth;</li>
+<li>Top-level Contracts objects: 46 kinds, including <code>plugin-verification-request</code>, <code>plugin-verification-result</code>, <code>filesystem-tree-observation</code>, <code>executable-identity-observation</code>, <code>skill-family-directory-verification-request</code>, <code>skill-family-directory-verification-result</code>, and <code>engineering-baseline</code>, with <code>packages/skill-family-contracts/src/registry.json</code> as the sole source of truth;</li>
 <li>Kit top-level commands: 4 (scaffold, adopt-plan, projection, check);</li>
 <li>Mandatory mechanical rules: currently 9, budget not exceeding 20, absolute ceiling 30; CR-001 uniformly compiles all Schemas within the registry;</li>
 <li>Leaf packages: 3 (skill-family-contracts, skill-family-harness-node, skill-family-engineering-kit);</li>

package/docs/public/status/index.html

@@ -1792,17 +1792,17 @@
 <tbody>
 <tr>
 <td><code>skill-family-contracts</code></td>
-<td>0.16.0</td>
+<td>0.17.0</td>
 <td><a href="https://github.com/ifoohoo/skill-family-contracts">ifoohoo/skill-family-contracts</a></td>
 </tr>
 <tr>
 <td><code>skill-family-harness-node</code></td>
-<td>0.16.0</td>
+<td>0.17.0</td>
 <td><a href="https://github.com/ifoohoo/skill-family-harness-node">ifoohoo/skill-family-harness-node</a></td>
 </tr>
 <tr>
 <td><code>skill-family-engineering-kit</code></td>
-<td>0.16.0</td>
+<td>0.17.0</td>
 <td><a href="https://github.com/ifoohoo/skill-family-engineering-kit">ifoohoo/skill-family-engineering-kit</a></td>
 </tr>
 </tbody>

package/docs/reference/api/contracts/index.html

@@ -933,6 +933,34 @@
       </ul>
     </nav>
 
+</li>
+
+        <li class="md-nav__item">
+  <a href="#工程基线-foundationcontractsengineering-baseline" class="md-nav__link">
+    <span class="md-ellipsis">
+
+        工程基线 (foundation.contracts.engineering-baseline)
+
+    </span>
+  </a>
+
+    <nav class="md-nav" aria-label="工程基线 (foundation.contracts.engineering-baseline)">
+      <ul class="md-nav__list">
+
+          <li class="md-nav__item">
+  <a href="#validateEngineeringBaseline--describeEngineeringBaseline" class="md-nav__link">
+    <span class="md-ellipsis">
+
+        validateEngineeringBaseline / describeEngineeringBaseline
+
+    </span>
+  </a>
+
+</li>
+
+      </ul>
+    </nav>
+
 </li>
 
         <li class="md-nav__item">
@@ -2295,6 +2323,34 @@
       </ul>
     </nav>
 
+</li>
+
+        <li class="md-nav__item">
+  <a href="#工程基线-foundationcontractsengineering-baseline" class="md-nav__link">
+    <span class="md-ellipsis">
+
+        工程基线 (foundation.contracts.engineering-baseline)
+
+    </span>
+  </a>
+
+    <nav class="md-nav" aria-label="工程基线 (foundation.contracts.engineering-baseline)">
+      <ul class="md-nav__list">
+
+          <li class="md-nav__item">
+  <a href="#validateEngineeringBaseline--describeEngineeringBaseline" class="md-nav__link">
+    <span class="md-ellipsis">
+
+        validateEngineeringBaseline / describeEngineeringBaseline
+
+    </span>
+  </a>
+
+</li>
+
+      </ul>
+    </nav>
+
 </li>
 
         <li class="md-nav__item">
@@ -2415,12 +2471,13 @@
 <li><a href="#fixture-校验-foundationcontractsfixture-verification">fixture 校验</a> → <code>listFixtures</code> / <code>verifyFixture</code> / <code>verifyAllFixtures</code></li>
 <li><a href="#错误码-foundationcontractserror-codes">错误码</a> → <code>ContractsError</code> / <code>isRegisteredErrorCode</code> / <code>stableError</code></li>
 <li><a href="#审计表面-foundationcontractsaudit-surface">审计表面</a> → <code>canonicalJson</code> / <code>digestDocument</code> / <code>digestAuditSurface</code></li>
+<li><a href="#工程基线-foundationcontractsengineering-baseline">工程基线</a> → <code>validateEngineeringBaseline</code> / <code>describeEngineeringBaseline</code></li>
 <li><a href="#同级适配器验证合同-foundationcontractspeer-adapter-verification">同级适配器验证合同</a> → request/result Schema</li>
 <li><a href="#真实宿主验证合同-foundationcontractshost-verification">真实宿主验证合同</a> → request/result Schema</li>
 <li><a href="#完整插件验证合同-foundationcontractsplugin-verification">完整插件验证合同</a> → request/result Schema</li>
 <li><a href="#技能族目录验证合同-foundationcontractsskill-family-directory-verification">技能族目录验证合同</a> → request/result Schema</li>
 </ul>
-<p>包级常量（冻结，仅作事实投影，不另立权威）：<code>CONTRACT_OBJECTS</code>（45 类顶层对象，闭集）、<code>CONTRACT_BOUNDARY</code>、<code>CONTRACTS_VERSION = "1.15.0"</code>、<code>SUPPORTED_DIALECTS</code>、<code>VALIDATION_POLICIES</code>、<code>CHECK_TYPES</code>（9 类机械检查）、<code>MANDATORY_RULES</code>、<code>RULE_BUDGET</code>、<code>ERROR_CODES</code>。</p>
+<p>包级常量（冻结，仅作事实投影，不另立权威）：<code>CONTRACT_OBJECTS</code>（46 类顶层对象，闭集）、<code>CONTRACT_BOUNDARY</code>、<code>CONTRACTS_VERSION = "1.16.0"</code>、<code>SUPPORTED_DIALECTS</code>、<code>VALIDATION_POLICIES</code>、<code>CHECK_TYPES</code>（9 类机械检查）、<code>MANDATORY_RULES</code>、<code>RULE_BUDGET</code>、<code>ERROR_CODES</code>。</p>
 <hr />
 <h2 id="对象校验-foundationcontractsobject-validation">对象校验 (foundation.contracts.object-validation)<a class="headerlink" href="#对象校验-foundationcontractsobject-validation" title="Permanent link">&para;</a></h2>
 <h3 id="validateDocument">validateDocument<a class="headerlink" href="#validateDocument" title="Permanent link">&para;</a></h3>
@@ -2505,7 +2562,7 @@
 <li>纯函数：是。</li>
 <li>副作用：无。</li>
 <li>稳定错误码与 <code>details.kind</code>：登记类冲突经 <code>registerSchema</code> / <code>registerProtocol</code> 抛 <code>SFC1003</code>（<code>DUPLICATE_SCHEMA_ID</code>）/ <code>SFC1004</code>（<code>DUPLICATE_PROTOCOL_NAME</code>）。</li>
-<li>前置条件与信任锚：<code>registry.json</code> 随包发布；<code>schemaVersion=1</code>、<code>contractsVersion=1.15.0</code> 为唯一权威；登记表含 45 类 Schema 与 1 个 Kernel Protocol，新增需 ADR。</li>
+<li>前置条件与信任锚：<code>registry.json</code> 随包发布；<code>schemaVersion=1</code>、<code>contractsVersion=1.16.0</code> 为唯一权威；登记表含 46 类 Schema 与 1 个 Kernel Protocol，新增需 ADR。</li>
 <li><code>since</code> / <code>stability</code>：<code>0.2.0</code> / <code>stable</code>。</li>
 <li>源文件：<code>packages/skill-family-contracts/src/registry.mjs</code>、<code>registry.json</code>。</li>
 <li>正例/负例测试：<code>packages/skill-family-contracts/test/registry.test.mjs</code>。</li>
@@ -2521,7 +2578,7 @@
 <li>纯函数：是（仅返回复制后的内存对象）。</li>
 <li>副作用：无文件、进程、Git、网络或持久化副作用。</li>
 <li>稳定错误码与 <code>details.kind</code>：<code>SFC1003</code>（重复 <code>$id</code>）、<code>SFC1004</code>（重复协议名）。</li>
-<li>前置条件与信任锚：登记表含 45 类 Schema 与 1 个 Kernel Protocol，新增需 ADR。</li>
+<li>前置条件与信任锚：登记表含 46 类 Schema 与 1 个 Kernel Protocol，新增需 ADR。</li>
 <li><code>since</code> / <code>stability</code>：<code>0.2.0</code> / <code>stable</code>。</li>
 <li>源文件：同上。</li>
 <li>正例/负例测试：同上。</li>
@@ -2733,6 +2790,22 @@
 <li>正例/负例测试：<code>packages/skill-family-contracts/test/audit-surface.test.mjs</code>。</li>
 <li>调用方仍拥有的业务语义：审计语义结论（接受/拒绝属外部独立审阅）。</li>
 </ul>
+<hr />
+<h2 id="工程基线-foundationcontractsengineering-baseline">工程基线 (foundation.contracts.engineering-baseline)<a class="headerlink" href="#工程基线-foundationcontractsengineering-baseline" title="Permanent link">&para;</a></h2>
+<h3 id="validateEngineeringBaseline--describeEngineeringBaseline">validateEngineeringBaseline / describeEngineeringBaseline<a class="headerlink" href="#validateEngineeringBaseline--describeEngineeringBaseline" title="Permanent link">&para;</a></h3>
+<ul>
+<li>签名：<code>validateEngineeringBaseline(baseline)</code>；<code>describeEngineeringBaseline({ provider, id, version, canonicalRuleRefs, referenceImplementation })</code>。</li>
+<li>输入：闭合的 <code>skill-family.engineering-baseline</code> 文档，或构造该文档所需的提供方身份、已排序规则谱系引用和 Foundation 参考骨架身份。<code>referenceImplementation</code> 只含 <code>foundationVersion</code>、<code>profile</code> 与 <code>skeletonDigest</code>。</li>
+<li>输出：校验入口返回既有 <code>{ valid, errorCode, errors, data }</code> 结果；构造入口按规则 ID 排序、计算去掉 <code>digest</code> 字段后的规范 JSON 摘要，并返回深度冻结的文档。</li>
+<li>纯函数：是。只复用 Contracts 的 Schema 校验、惰性 JSON 预检、<code>digestDocument()</code> 与进程内编译缓存。</li>
+<li>副作用：无文件、进程、Git 或网络副作用；不读取基线提供方的包、仓库或规则文件。</li>
+<li>稳定错误码与 <code>details.kind</code>：结构、重复规则 ID、非确定性顺序或摘要不一致返回或抛出 <code>SFC1001</code>；未知 Schema 仍按通用校验规则返回 <code>SFC1002</code>。</li>
+<li>前置条件与信任锚：Schema <code>$id</code> 为 <code>https://contracts.skill-family.example/v1/engineering-baseline.json</code>；<code>canonicalRuleRefs</code> 至少一项，按 <code>id</code> 唯一且升序；<code>digest</code> 必须绑定文档自身。</li>
+<li><code>since</code> / <code>stability</code>：<code>0.17.0</code> / <code>stable</code>。</li>
+<li>源文件：<code>packages/skill-family-contracts/src/engineering-baseline.mjs</code>、<code>src/schemas/engineering-baseline.schema.json</code>。</li>
+<li>正例/负例测试：<code>packages/skill-family-contracts/test/engineering-baseline.test.mjs</code>、<code>schemas.test.mjs</code>。</li>
+<li>调用方仍拥有的业务语义：基线提供方负责规则正文、规则效果、等价关系、豁免和正式基线发布。Foundation 不解释这些语义，也不宣称 Audit 已经发布正式基线；依赖方向保持为基线提供方依赖 Foundation。</li>
+</ul>
 <h2 id="同级适配器验证合同-foundationcontractspeer-adapter-verification">同级适配器验证合同 (foundation.contracts.peer-adapter-verification)<a class="headerlink" href="#同级适配器验证合同-foundationcontractspeer-adapter-verification" title="Permanent link">&para;</a></h2>
 <p>Contracts 1.10.0 登记 <code>adapter-peer-verification-request</code> 与
 <code>adapter-peer-verification-result</code> 两个稳定 Schema。request 至少包含两个显式 peer；每个 peer
@@ -2758,7 +2831,9 @@ peer 顺序不得改变共同闭包摘要或结论；未知字段、重复/缺
   stream 或 durable receipt；<code>observed</code> 只表示基础设施观察完整，不表示消费者领域 PASS。<code>requiredActions</code> 只允许
   <code>manual-temporary-root-inspection-required</code>。</li>
 <li>request auth 必须精确对应已登记 Descriptor 的单值 <code>driverId/authStrategy/credentialMutation</code>；Descriptor 是认证组合的
-  唯一事实源，Schema 同时机械绑定 <code>kimi-code → kimi-code-print-v1</code> 与 <code>workbuddy → workbuddy-codebuddy-print-v1</code>。
+  唯一事实源。Schema 分别绑定 <code>kimi-code → kimi-code-print-v1</code>、<code>workbuddy → workbuddy-codebuddy-print-v1</code>、
+  <code>codebuddy → codebuddy-print-v1</code>、<code>claude → claude-code-print-v1</code>、<code>codex → codex-exec-v1</code> 与
+  <code>qoder → qodercli-print-v1</code>，CodeBuddy 与 WorkBuddy 的路由不可互换。
   Schema 不提供通用 driver Registry 或认证 SPI。</li>
 <li><code>since</code> / <code>stability</code>：<code>0.11.0</code> / <code>candidate</code>。Schema 文件：
   <code>packages/skill-family-contracts/src/schemas/host-verification-request.schema.json</code>、