skill-family-engineering-kit 0.19.0 → 0.19.2

package/CHANGELOG.md

@@ -1,5 +1,36 @@
 # Changelog
 
+<!-- release-skill:changelog:start version=0.19.2 locale=en baseline=sha256:b4a9f795a1264bc28c9d37378a1d92eb4fd8c1e023506fbe6f5752b08842e2f0 -->
+## [0.19.2] - 2026-09-08
+
+Engineering Kit 0.19.2 aligns its package version and generated projections with the Foundation Adoption Review distribution patch. Public commands and behavior are unchanged.
+
+### Changed
+
+- Aligns the package version, release documentation, and necessary generated projections with Foundation 0.19.2 without adding a command, capability, or adapter path.
+
+### Upgrade Notes
+
+Pin all three Foundation packages to exactly 0.19.2 and rebuild official Bundles under the existing source-identity and integrity rules. The capability catalog, host descriptors, drivers, since values, and maturity are unchanged.
+<!-- release-skill:changelog:end version=0.19.2 locale=en -->
+
+
+<!-- release-skill:changelog:start version=0.19.1 locale=en baseline=sha256:199e48a82f8d08629d98f1286a964cbf98ba5850efe65183adfc353cfe9f3610 -->
+## [0.19.1] - 2026-09-08
+
+Engineering Kit 0.19.1 projects the compatible batch stream and result-contract fixes into the existing official Bundle.
+
+### Fixed
+
+- Carries the corrected Harness transfer behavior and Contracts result Schema without adding a second implementation or a new Kit command.
+- Clarifies in the bundled capability catalog that preflight rejection invokes no mechanism, output-capacity rejection may follow execution of the current item, and output-channel failure may leave partial bytes sent.
+
+### Upgrade Notes
+
+Pin all three Foundation packages to exactly 0.19.1 and rebuild official Bundles under the existing source-identity and integrity rules. The capability remains candidate with since 0.19.0; a catalog match is not a stable adoption declaration.
+<!-- release-skill:changelog:end version=0.19.1 locale=en -->
+
+
 <!-- release-skill:changelog:start version=0.19.0 locale=en baseline=sha256:d3b79ce1564df3e0dc0f0abc1af616817550044de73f9b05b57a5dd65fd47dae -->
 ## [0.19.0] - 2026-09-07
 

package/CHANGELOG.zh-CN.md

@@ -1,5 +1,36 @@
 # 变更日志
 
+<!-- release-skill:changelog:start version=0.19.2 locale=zh-CN baseline=sha256:bd0cbfd935e7b9751f6311f3d1114df2db5066448d1830f27b7c92aa3aca9687 -->
+## [0.19.2] - 2026-09-08
+
+Engineering Kit 0.19.2 将包版本和生成投影与 Foundation Adoption Review 分发补丁对齐。公开命令和行为保持不变。
+
+### 变更
+
+- 包版本、发布说明和必要生成投影与 Foundation 0.19.2 数值对齐，不增加命令、能力或 adapter 路径。
+
+### 升级说明
+
+三个 Foundation 包须一起精确锁定到 0.19.2，并按既有来源身份与完整性规则重建官方 Bundle。能力目录、宿主 descriptor、driver、since 字段和成熟度均不变。
+<!-- release-skill:changelog:end version=0.19.2 locale=zh-CN -->
+
+
+<!-- release-skill:changelog:start version=0.19.1 locale=zh-CN baseline=sha256:832a8dfa16c41d6381cd2b0f00f58b096f45715332d42b7be11595976ab15e1e -->
+## [0.19.1] - 2026-09-08
+
+Engineering Kit 0.19.1 将兼容的批量流与结果合同修复投影到既有官方 Bundle。
+
+### 修复
+
+- 携带修正后的 Harness 传输行为和 Contracts 结果 Schema，不增加第二份实现或新的 Kit 命令。
+- 内置能力目录区分三类失败阶段：预检拒绝不会调用机制；输出容量拒绝可能发生在当前项执行后；输出通道失败可能已有部分字节送出。
+
+### 升级说明
+
+三个 Foundation 包须一起精确锁定到 0.19.1，并按既有来源身份与完整性规则重建官方 Bundle。能力仍为 candidate，since 0.19.0 保持不变；目录命中不构成稳定采用声明。
+<!-- release-skill:changelog:end version=0.19.1 locale=zh-CN -->
+
+
 <!-- release-skill:changelog:start version=0.19.0 locale=zh-CN baseline=sha256:f000b13d13ce11660aaa4c5a1b450af39f99cb62a5177467783d863e7f411296 -->
 ## [0.19.0] - 2026-09-07
 

package/README.md

@@ -4,27 +4,22 @@
 
 # skill-family-engineering-kit
 
-<!-- release-skill:release-version: 0.19.0 -->
+<!-- release-skill:release-version: 0.19.2 -->
 
 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.19.0** (2026-09-07)
+**0.19.2** (2026-09-08)
 
-Engineering Kit 0.19.0 projects the new batch transport into the official offline Bundle and registers the mechanism-batch capability in the built-in catalog.
-
-**Added**
-
-- The official Bundle projection now carries runMechanismCliBatch, the --batch CLI mode, the two mechanism-batch Schemas, and the frozen batch capacity policy with unchanged source identity, digest, and integrity handling.
-- The capability catalog adds foundation.harness.mechanism-batch with since 0.19.0 and stability candidate, together with intent, failure semantics, and direct test references.
+Engineering Kit 0.19.2 aligns its package version and generated projections with the Foundation Adoption Review distribution patch. Public commands and behavior are unchanged.
 
 **Changed**
 
-- Adoption guidance documents batch selection rules: same-process calls keep the existing object entry; independent cross-process canonical-json requests within capacity are batch candidates; dependent or oversized requests keep the original path.
+- Aligns the package version, release documentation, and necessary generated projections with Foundation 0.19.2 without adding a command, capability, or adapter path.
 
 **Upgrade Notes**
 
-Pin all three Foundation packages to exactly 0.19.0 and rebuild official Bundles after upgrading per the existing package identity and provenance rules. The catalog entry is candidate: a catalog match is not a stable adoption declaration.
+Pin all three Foundation packages to exactly 0.19.2 and rebuild official Bundles under the existing source-identity and integrity rules. The capability catalog, host descriptors, drivers, since values, and maturity are unchanged.
 <!-- release-skill:managed:end id=latest-release -->
 
 ### Foundation 0.15.0 candidate qualification entries
@@ -54,7 +49,7 @@ Kit is the "engineering stage" layer, depending on the Harness and Contracts. It
 
 ## Installation and Minimal Example
 
-Version 0.18.0 is a local candidate. Build all three tarballs into one temporary directory and install those exact files for a candidate check:
+Version 0.19.2 is the local source candidate. Build all three tarballs into one temporary directory and install those exact files for a candidate check:
 
 ```sh
 pack_dir="$(mktemp -d)"
@@ -62,21 +57,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.18.0.tgz" "$pack_dir/skill-family-harness-node-0.18.0.tgz" "$pack_dir/skill-family-engineering-kit-0.18.0.tgz")
+(cd "$pack_dir/consumer" && npm install "$pack_dir/skill-family-contracts-0.19.2.tgz" "$pack_dir/skill-family-harness-node-0.19.2.tgz" "$pack_dir/skill-family-engineering-kit-0.19.2.tgz")
 ```
 
 After publication, use the registry coordinate:
 
 ```sh
-npm install --save-dev skill-family-engineering-kit@0.19.0
-npm exec --package=skill-family-engineering-kit@0.19.0 -- skill-family-kit --help
-npm exec --package=skill-family-engineering-kit@0.19.0 -- skill-family-kit scaffold --root <empty-dir> --project-id my-project
-npm exec --package=skill-family-engineering-kit@0.19.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.19.0 -- skill-family-kit projection --root <repo>
-npm exec --package=skill-family-engineering-kit@0.19.0 -- skill-family-kit check --root <repo>
+npm install --save-dev skill-family-engineering-kit@0.19.2
+npm exec --package=skill-family-engineering-kit@0.19.2 -- skill-family-kit --help
+npm exec --package=skill-family-engineering-kit@0.19.2 -- skill-family-kit scaffold --root <empty-dir> --project-id my-project
+npm exec --package=skill-family-engineering-kit@0.19.2 -- 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.19.2 -- skill-family-kit projection --root <repo>
+npm exec --package=skill-family-engineering-kit@0.19.2 -- 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.19.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.19.2 -- skill-family-kit --help`.
 
 ### Three adoption journeys
 
@@ -295,4 +290,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.18.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.19.2 is the local source candidate. Remote availability must be established by the corresponding release-skill post-release evidence. Consume the three locally verified tarballs for candidate checks; 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,27 +5,22 @@
 
 # skill-family-engineering-kit
 
-<!-- release-skill:release-version: 0.19.0 -->
+<!-- release-skill:release-version: 0.19.2 -->
 
 开发与 CI 阶段使用的工程工具包。**恰好四个**顶层命令，没有第五个：
 
 <!-- release-skill:managed:start id=latest-release -->
-**0.19.0** (2026-09-07)
+**0.19.2** (2026-09-08)
 
-Engineering Kit 0.19.0 把新批量传输投影进官方离线 Bundle，并在内置能力目录登记 mechanism-batch 能力。
-
-**新增**
-
-- 官方 Bundle 投影携带 runMechanismCliBatch、--batch CLI 模式、两个机制批量 Schema 与冻结的批量容量政策，来源身份、摘要与完整性处理不变。
-- 能力目录新增 foundation.harness.mechanism-batch：since 0.19.0、stability candidate，并登记意图、失败语义与直接测试引用。
+Engineering Kit 0.19.2 将包版本和生成投影与 Foundation Adoption Review 分发补丁对齐。公开命令和行为保持不变。
 
 **变更**
 
-- 采用指导补充批量选择规则：同进程调用保留既有对象入口；跨进程、相互独立且容量允许的 canonical-json 请求可作为批量候选；有依赖或超限请求保留原路径。
+- 包版本、发布说明和必要生成投影与 Foundation 0.19.2 数值对齐，不增加命令、能力或 adapter 路径。
 
 **升级说明**
 
-三个 Foundation 包须一起精确锁定到 0.19.0，升级后按既有包身份与 provenance 规则重建官方 Bundle。该目录条目为候选能力：目录命中不构成稳定采用声明。
+三个 Foundation 包须一起精确锁定到 0.19.2，并按既有来源身份与完整性规则重建官方 Bundle。能力目录、宿主 descriptor、driver、since 字段和成熟度均不变。
 <!-- release-skill:managed:end id=latest-release -->
 
 ### Foundation 0.15.0 candidate 资格入口
@@ -55,7 +50,7 @@ Kit 是「工程阶段」层，依赖 Harness 与 Contracts。它只做四件事
 
 ## 安装和最小示例
 
-0.18.0 是本地候选版本。候选验证先把三个包分别打入同一个临时目录，再安装这三个精确 tarball：
+0.19.2 是本地源码候选。候选验证先把三个包分别打入同一个临时目录，再安装这三个精确 tarball：
 
 ```sh
 pack_dir="$(mktemp -d)"
@@ -63,21 +58,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.18.0.tgz" "$pack_dir/skill-family-harness-node-0.18.0.tgz" "$pack_dir/skill-family-engineering-kit-0.18.0.tgz")
+(cd "$pack_dir/consumer" && npm install "$pack_dir/skill-family-contracts-0.19.2.tgz" "$pack_dir/skill-family-harness-node-0.19.2.tgz" "$pack_dir/skill-family-engineering-kit-0.19.2.tgz")
 ```
 
 发布后再使用 registry 坐标：
 
 ```sh
-npm install --save-dev skill-family-engineering-kit@0.19.0
-npm exec --package=skill-family-engineering-kit@0.19.0 -- skill-family-kit --help
-npm exec --package=skill-family-engineering-kit@0.19.0 -- skill-family-kit scaffold --root <empty-dir> --project-id my-project
-npm exec --package=skill-family-engineering-kit@0.19.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.19.0 -- skill-family-kit projection --root <repo>
-npm exec --package=skill-family-engineering-kit@0.19.0 -- skill-family-kit check --root <repo>
+npm install --save-dev skill-family-engineering-kit@0.19.2
+npm exec --package=skill-family-engineering-kit@0.19.2 -- skill-family-kit --help
+npm exec --package=skill-family-engineering-kit@0.19.2 -- skill-family-kit scaffold --root <empty-dir> --project-id my-project
+npm exec --package=skill-family-engineering-kit@0.19.2 -- 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.19.2 -- skill-family-kit projection --root <repo>
+npm exec --package=skill-family-engineering-kit@0.19.2 -- skill-family-kit check --root <repo>
 ```
 
-以上四条命令分别覆盖生成骨架、只读盘点、受管投影与诊断；零安装形式可用 `npm exec --package=skill-family-engineering-kit@0.19.0 -- skill-family-kit --help`。
+以上四条命令分别覆盖生成骨架、只读盘点、受管投影与诊断；零安装形式可用 `npm exec --package=skill-family-engineering-kit@0.19.2 -- skill-family-kit --help`。
 
 ### 三条采用旅程
 
@@ -296,4 +291,4 @@ Foundation 本身不发起网络请求，但绑定的 executable 仍可能联网
 
 独立入口 `runSkillFamilyDirectoryVerification({ request, bindings })` 固定 Kimi 生产 argv 与窄环境，并拒绝调用方 observation。原始 parser 通过生产进程路径验证，但受控 fixture 事件不会被提升为 `observed`；缺少官方 typed mapping 时，公共结果保持 `indeterminate` 和 manual candidate。
 
-0.18.0 为本地源码候选，尚未发布。消费本地已验证的三包 tarball；版本标记、单元测试或安装成功都不等于契约接入完成、迁移完成或真实宿主资格。
+0.19.2 是本地源码候选，远端可用性须由对应的 release-skill 发布后证据证明。候选检查使用本地已验证的三包 tarball；版本标记、单元测试或安装成功都不等于契约接入完成、迁移完成或真实宿主资格。

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

@@ -2243,12 +2243,14 @@
     "None (items execute through the existing pure-function dispatcher; only the caller-provided output/error streams are written; no file, network, process, or residual-state side effects)"
    ],
    "failureSemantics": [
-    "Whole-batch shape or capacity refusals write one batch error object to the error stream and exit 2 (TypeError projection; details.kind is closed to batch-structure-invalid, batch-item-limit, batch-input-limit, batch-output-limit)",
-    "Per-item mechanism failures are projected into that item's response and later items still run; at least one failure exits 2; partial batch results are never delivered"
+    "Request-byte, item-count, or structure preflight rejection invokes no mechanism and leaves stdout empty; the error stream receives one TypeError-projected batch error with details.kind batch-input-limit, batch-item-limit, or batch-structure-invalid respectively, and the batch exits 2",
+    "Output-capacity rejection occurs after the current item returns; that item may already have executed, later items stop, stdout remains empty, details.kind is batch-output-limit, and the batch exits 2",
+    "An output-channel failure exits 2 but may leave partial bytes sent; if the error channel also fails, delivery of the error object is not guaranteed",
+    "Per-item mechanism failures are projected into that item's response and later items still run; at least one failure exits 2"
    ],
    "invariants": [
     "Outer shape checks for every item complete before the first item runs; item order, duplicates, and the per-item invocation count stay unchanged",
-    "The complete response bytes are not sent until confirmed within the output limit; error objects are neither reordered nor normalized"
+    "The complete response bytes are not sent until confirmed within the output limit; after writing starts, bytes already sent cannot be withdrawn if the output channel fails; error objects are neither reordered nor normalized"
    ],
    "ownedByCaller": [
     "Domain grouping and capacity splitting, and judging dependencies between requests",

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

@@ -2242,12 +2242,14 @@
     "无（逐项经既有纯函数分派器执行；只写调用方提供的 output/error 流；无文件、网络、进程或残余状态副作用）"
    ],
    "failureSemantics": [
-    "整批结构或容量拒绝向 error 流写一个批次错误对象并整体退出 2（TypeError 投影；details.kind 封闭为 batch-structure-invalid、batch-item-limit、batch-input-limit、batch-output-limit）",
-    "单项机制失败按原 CLI 错误投影写入该项 response 并继续执行后续项；至少一项失败整体退出 2；不交付部分批次结果"
+    "请求字节、输入项数或结构预检拒绝不会调用机制，stdout 为空；error 流接收一个 TypeError 投影的批次错误对象，details.kind 分别为 batch-input-limit、batch-item-limit 或 batch-structure-invalid，整体退出 2",
+    "输出容量拒绝发生在当前项返回后；该项可能已经执行，后续项停止，stdout 为空；details.kind 为 batch-output-limit，整体退出 2",
+    "输出通道失败整体退出 2，但可能已有部分字节送出；若错误通道也失败，错误对象不保证能够交付",
+    "单项机制失败按原 CLI 错误投影写入该项 response 并继续执行后续项；至少一项失败整体退出 2"
    ],
    "invariants": [
     "全部项的外层形状检查先于第一项执行；项顺序、重复项与逐项调用次数保持不变",
-    "完整响应字节在确认未超输出上限前不发送；错误对象不重新排序或规范化"
+    "完整响应字节在确认未超输出上限前不发送；开始写入后发生输出通道失败时，已发送字节无法撤回；错误对象不重新排序或规范化"
    ],
    "ownedByCaller": [
     "领域分组与容量切分、请求间依赖关系的判断",

package/docs/agents/capability-catalog.en.json

@@ -2243,12 +2243,14 @@
     "None (items execute through the existing pure-function dispatcher; only the caller-provided output/error streams are written; no file, network, process, or residual-state side effects)"
    ],
    "failureSemantics": [
-    "Whole-batch shape or capacity refusals write one batch error object to the error stream and exit 2 (TypeError projection; details.kind is closed to batch-structure-invalid, batch-item-limit, batch-input-limit, batch-output-limit)",
-    "Per-item mechanism failures are projected into that item's response and later items still run; at least one failure exits 2; partial batch results are never delivered"
+    "Request-byte, item-count, or structure preflight rejection invokes no mechanism and leaves stdout empty; the error stream receives one TypeError-projected batch error with details.kind batch-input-limit, batch-item-limit, or batch-structure-invalid respectively, and the batch exits 2",
+    "Output-capacity rejection occurs after the current item returns; that item may already have executed, later items stop, stdout remains empty, details.kind is batch-output-limit, and the batch exits 2",
+    "An output-channel failure exits 2 but may leave partial bytes sent; if the error channel also fails, delivery of the error object is not guaranteed",
+    "Per-item mechanism failures are projected into that item's response and later items still run; at least one failure exits 2"
    ],
    "invariants": [
     "Outer shape checks for every item complete before the first item runs; item order, duplicates, and the per-item invocation count stay unchanged",
-    "The complete response bytes are not sent until confirmed within the output limit; error objects are neither reordered nor normalized"
+    "The complete response bytes are not sent until confirmed within the output limit; after writing starts, bytes already sent cannot be withdrawn if the output channel fails; error objects are neither reordered nor normalized"
    ],
    "ownedByCaller": [
     "Domain grouping and capacity splitting, and judging dependencies between requests",

package/docs/agents/capability-catalog.zh-CN.json

@@ -2242,12 +2242,14 @@
     "无（逐项经既有纯函数分派器执行；只写调用方提供的 output/error 流；无文件、网络、进程或残余状态副作用）"
    ],
    "failureSemantics": [
-    "整批结构或容量拒绝向 error 流写一个批次错误对象并整体退出 2（TypeError 投影；details.kind 封闭为 batch-structure-invalid、batch-item-limit、batch-input-limit、batch-output-limit）",
-    "单项机制失败按原 CLI 错误投影写入该项 response 并继续执行后续项；至少一项失败整体退出 2；不交付部分批次结果"
+    "请求字节、输入项数或结构预检拒绝不会调用机制，stdout 为空；error 流接收一个 TypeError 投影的批次错误对象，details.kind 分别为 batch-input-limit、batch-item-limit 或 batch-structure-invalid，整体退出 2",
+    "输出容量拒绝发生在当前项返回后；该项可能已经执行，后续项停止，stdout 为空；details.kind 为 batch-output-limit，整体退出 2",
+    "输出通道失败整体退出 2，但可能已有部分字节送出；若错误通道也失败，错误对象不保证能够交付",
+    "单项机制失败按原 CLI 错误投影写入该项 response 并继续执行后续项；至少一项失败整体退出 2"
    ],
    "invariants": [
     "全部项的外层形状检查先于第一项执行；项顺序、重复项与逐项调用次数保持不变",
-    "完整响应字节在确认未超输出上限前不发送；错误对象不重新排序或规范化"
+    "完整响应字节在确认未超输出上限前不发送；开始写入后发生输出通道失败时，已发送字节无法撤回；错误对象不重新排序或规范化"
    ],
    "ownedByCaller": [
     "领域分组与容量切分、请求间依赖关系的判断",

package/docs/en/reference/failure-and-side-effect-matrix/index.html

@@ -2032,7 +2032,7 @@
 <td><code>SFC2004</code></td>
 </tr>
 <tr>
-<td><code>runMechanismCliBatch</code> / <code>mechanisms-cli.mjs --batch</code> (0.19.0 candidate)</td>
+<td><code>runMechanismCliBatch</code> / <code>mechanisms-cli.mjs --batch</code> (since 0.19.0, candidate)</td>
 <td>no</td>
 <td>no</td>
 <td>no</td>
@@ -2043,6 +2043,7 @@
 </tr>
 </tbody>
 </table>
+<p>The failure stage determines the observable effects of the batch entry point. Request-byte, item-count, and structure preflight rejection invokes no mechanism and leaves stdout empty. Output capacity can be checked only after the current item returns, so that item may already have executed; later items are not executed and stdout remains empty. An output-channel failure may leave partial bytes sent and returns 2. If the error channel also fails, delivery of the error object is not guaranteed.</p>
 <p>Harness's <code>HARNESS_EXCLUSIONS</code> explicitly excludes release-state, remote-network-access, business-semantics, workflow-orchestration, model-calls, git-writes.</p>
 <h2 id="Engineering-Kit-Engineering-Command-Layer">Engineering Kit (Engineering Command Layer)<a class="headerlink" href="#Engineering-Kit-Engineering-Command-Layer" title="Permanent link">&para;</a></h2>
 <table>

package/docs/public/status/index.html

@@ -1792,17 +1792,17 @@
 <tbody>
 <tr>
 <td><code>skill-family-contracts</code></td>
-<td>0.19.0</td>
+<td>0.19.2</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.19.0</td>
+<td>0.19.2</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.19.0</td>
+<td>0.19.2</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/harness/index.html

@@ -3699,10 +3699,10 @@ stable 承诺，Bundle 是否重建由既有包字节与 provenance 绑定输入
 </tbody>
 </table>
 <ul>
-<li>失败语义：整批结构或容量拒绝在 <code>error</code> 流写一个批次错误对象并整体退出 2，不执行任何项、不交付部分结果；错误为 <code>TypeError</code> 投影，<code>details.kind</code> 封闭为 <code>batch-structure-invalid</code>、<code>batch-item-limit</code>、<code>batch-input-limit</code>、<code>batch-output-limit</code>，不新增 SFC 错误码。畸形 UTF-8、畸形 JSON 与输入流错误属传输失败，保留原异常投影，不伪装为机制业务失败、不伪造某个 <code>inputIndex</code>。单项机制失败（含 unsafe integer 等留给原分派器按项判断的约束）经原 CLI 错误投影写入该项 <code>response</code> 并继续执行后续项。输出流写入失败时已发送字节无法撤回，消费者必须把截断 JSON、通道错误或进程无正常完成结果判为传输失败，不能从前缀认定批次成功。</li>
-<li>整体退出码三分支：所有机制项成功 → 0，stdout 为完整批次结果加一个换行、stderr 空；至少一个机制项失败 → 2，stdout 仍为完整批次结果、stderr 空；输入/结构/容量/传输检查失败 → 2，stdout 空、stderr 为一个批次错误对象与换行。</li>
+<li>失败语义：请求字节、输入项数或结构的预检拒绝在任何机制调用前发生，stdout 为空，<code>error</code> 流写一个批次错误对象并整体退出 2。输出容量只能在当前项已经返回后确认；超限时停止后续项，stdout 仍为空，<code>error</code> 流写批次错误对象并退出 2。错误为 <code>TypeError</code> 投影，<code>details.kind</code> 封闭为 <code>batch-structure-invalid</code>、<code>batch-item-limit</code>、<code>batch-input-limit</code>、<code>batch-output-limit</code>，不新增 SFC 错误码。畸形 UTF-8、畸形 JSON 与输入流错误属传输失败，保留原异常投影，不伪装为机制业务失败、不伪造某个 <code>inputIndex</code>。单项机制失败（含 unsafe integer 等留给原分派器按项判断的约束）经原 CLI 错误投影写入该项 <code>response</code> 并继续执行后续项。输出通道失败时可能已有部分字节送出；整体退出 2，消费者必须把截断 JSON、通道错误或进程无正常完成结果判为传输失败，不能从前缀认定批次成功。若连错误通道也写入失败，错误对象可能无法交付。</li>
+<li>整体退出码三分支：所有机制项成功 → 0，stdout 为完整批次结果加一个换行、stderr 空；至少一个机制项失败 → 2，stdout 仍为完整批次结果、stderr 空；批次预检、输出容量或传输失败 → 2。预检与输出容量失败时 stdout 空、stderr 为一个批次错误对象与换行；输出通道失败时不承诺收回已经发送的字节。</li>
 <li>前置条件与信任锚：Contracts、Harness 与 Engineering Kit 精确锁定同一版本；程序化函数与 CLI 都经调用方已安装并验证来源的官方 Bundle 消费（Bundle 由同版本三包生成，保留来源身份、摘要与完整性检查），不从 Foundation 工作树导入源码；调用方提供 input/output/error 流。已有 Schema 批量校验（<code>validate-many-by-schema-id</code>）继续使用原入口，不嵌套、不重新包装。</li>
-<li><code>since</code> / <code>stability</code>：<code>0.19.0</code> / <code>candidate</code>。尚未发布、尚未 stable；候选测试通过不自动产生 stable 承诺，任何文档不得把该能力写成已发布稳定能力。</li>
+<li><code>since</code> / <code>stability</code>：<code>0.19.0</code> / <code>candidate</code>。<code>candidate</code> 不等于 <code>stable</code>，本地候选测试通过也不改变成熟度；是否发布须查对应版本的发布后验证证据，不能从 <code>stability</code> 推断。</li>
 <li>源文件：Contracts 新 Schema <code>packages/skill-family-contracts/candidate/foundation-mechanisms/mechanism-batch-request.schema.json</code>、<code>mechanism-batch-result.schema.json</code> 与容量权威 <code>mechanism-batch-policy.json</code>；Harness <code>packages/skill-family-harness-node/candidate/mechanisms-cli.mjs</code>；Kit 离线 Bundle 投影 <code>packages/skill-family-engineering-kit/candidate/profile-bundle.mjs</code>。</li>
 <li>正例/负例测试：<code>packages/skill-family-contracts/test/quickstart-profile.test.mjs</code>、<code>packages/skill-family-harness-node/test/quickstart-profile.test.mjs</code>、<code>packages/skill-family-engineering-kit/test/candidate-mechanisms-cli.test.mjs</code>、<code>packages/skill-family-engineering-kit/test/candidate-profile-bundle.test.mjs</code>。</li>
 <li>调用方仍拥有的业务语义：领域分组与容量切分、请求间依赖关系判断、精确 pin 与来源身份绑定、批次采用完成与领域回归判定。逐项迁移示例：把若干 <code>{ "operation": "canonical-json", "params": { "document": ... } }</code> 单请求合并为 <code>{ "operation": "canonical-json", "inputs": [{ "document": ... }, ...] }</code>，再按 <code>results[i].inputIndex</code> 读回逐项 <code>response</code> 与 <code>exitCode</code>；同一 Node 进程内的直接调用继续使用 <code>invokeFoundationMechanism</code>，不被强制改成批量。</li>

package/docs/reference/failure-and-side-effect-matrix/index.html

@@ -2022,7 +2022,7 @@
 <td><code>SFC2004</code></td>
 </tr>
 <tr>
-<td><code>runMechanismCliBatch</code> / <code>mechanisms-cli.mjs --batch</code>（0.19.0 candidate）</td>
+<td><code>runMechanismCliBatch</code> / <code>mechanisms-cli.mjs --batch</code>（since 0.19.0，candidate）</td>
 <td>否</td>
 <td>否</td>
 <td>否</td>
@@ -2033,6 +2033,7 @@
 </tr>
 </tbody>
 </table>
+<p>批量入口的失败阶段决定可观察副作用。请求字节、输入项数或结构的预检拒绝不会调用机制，stdout 为空；输出容量只能在当前项返回后确认，因此该项可能已经执行，但后续项不会再执行，stdout 仍为空。输出通道失败时可能已有部分字节送出，整体退出 2；若错误通道也失败，错误对象不保证能够交付。</p>
 <p>Harness 的 <code>HARNESS_EXCLUSIONS</code> 明确排除 release-state、remote-network-access、business-semantics、workflow-orchestration、model-calls、git-writes。</p>
 <h2 id="Engineering-Kit工程命令层">Engineering Kit（工程命令层）<a class="headerlink" href="#Engineering-Kit工程命令层" title="Permanent link">&para;</a></h2>
 <table>