skill-family-engineering-kit 0.17.0 → 0.19.0

package/CHANGELOG.md

@@ -1,5 +1,44 @@
 # Changelog
 
+<!-- release-skill:changelog:start version=0.19.0 locale=en baseline=sha256:d3b79ce1564df3e0dc0f0abc1af616817550044de73f9b05b57a5dd65fd47dae -->
+## [0.19.0] - 2026-09-07
+
+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.
+
+### 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.
+
+### 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.
+<!-- release-skill:changelog:end version=0.19.0 locale=en -->
+
+
+<!-- release-skill:changelog:start version=0.18.0 locale=en baseline=sha256:9c6fe9859fb75316937790054ae7d45bfc21d38ce97d8e650d7da18757a462c5 -->
+## [0.18.0] - 2026-09-05
+
+Engineering Kit 0.18.0 projects the stable Harness replaceFixedSetAtomic export into the existing offline Quickstart Bundle.
+
+### Added
+
+- The existing candidate Bundle now carries the stable fixed-set replacement source, loader, native closure, and replaceFixedSetAtomic export without adding a parallel implementation or a new Kit command.
+
+### Changed
+
+- Moves the package version to 0.18.0 together with Contracts and Harness while preserving runProjection as the Bundle write and authorization boundary.
+
+### Upgrade Notes
+
+Pin all three Foundation packages to exactly 0.18.0 and rebuild managed Bundles from those exact installed package bytes. Bundle consumers receive the same non-idempotent replacement semantics and must not retry post-commit or indeterminate outcomes blindly.
+<!-- release-skill:changelog:end version=0.18.0 locale=en -->
+
+
 <!-- release-skill:changelog:start version=0.17.0 locale=en baseline=sha256:c09a3edaeab4e9f29527900bff5baaa7f7be185a9270ce81f450fab8ec9fb16f -->
 ## [0.17.0] - 2026-09-01
 

package/CHANGELOG.zh-CN.md

@@ -1,5 +1,44 @@
 # 变更日志
 
+<!-- release-skill:changelog:start version=0.19.0 locale=zh-CN baseline=sha256:f000b13d13ce11660aaa4c5a1b450af39f99cb62a5177467783d863e7f411296 -->
+## [0.19.0] - 2026-09-07
+
+Engineering Kit 0.19.0 把新批量传输投影进官方离线 Bundle，并在内置能力目录登记 mechanism-batch 能力。
+
+### 新增
+
+- 官方 Bundle 投影携带 runMechanismCliBatch、--batch CLI 模式、两个机制批量 Schema 与冻结的批量容量政策，来源身份、摘要与完整性处理不变。
+- 能力目录新增 foundation.harness.mechanism-batch：since 0.19.0、stability candidate，并登记意图、失败语义与直接测试引用。
+
+### 变更
+
+- 采用指导补充批量选择规则：同进程调用保留既有对象入口；跨进程、相互独立且容量允许的 canonical-json 请求可作为批量候选；有依赖或超限请求保留原路径。
+
+### 升级说明
+
+三个 Foundation 包须一起精确锁定到 0.19.0，升级后按既有包身份与 provenance 规则重建官方 Bundle。该目录条目为候选能力：目录命中不构成稳定采用声明。
+<!-- release-skill:changelog:end version=0.19.0 locale=zh-CN -->
+
+
+<!-- release-skill:changelog:start version=0.18.0 locale=zh-CN baseline=sha256:c8c2891b64fc31e1fb3754715da04d6ec0727b31e36e011d38735e45795cdd53 -->
+## [0.18.0] - 2026-09-05
+
+Engineering Kit 0.18.0 将 Harness 稳定的 replaceFixedSetAtomic 导出投影到既有离线 Quickstart Bundle。
+
+### 新增
+
+- 既有 candidate Bundle 携带稳定的固定集合替换源码、加载器、原生闭包与 replaceFixedSetAtomic 导出；不新增平行实现，也不增加 Kit 命令。
+
+### 变更
+
+- 包版本与 Contracts、Harness 一同升至 0.18.0，runProjection 继续作为 Bundle 的写入与授权边界。
+
+### 升级说明
+
+三个 Foundation 包须一起精确锁定到 0.18.0，并从这些已安装包的精确字节重建受管 Bundle。Bundle 消费者获得相同的非幂等替换语义，不得盲目重试提交后或不确定结果。
+<!-- release-skill:changelog:end version=0.18.0 locale=zh-CN -->
+
+
 <!-- release-skill:changelog:start version=0.17.0 locale=zh-CN baseline=sha256:7c413da3ad02837bdd63a1b49a5dc78cefe15a9779a05ce070876f817d09ae65 -->
 ## [0.17.0] - 2026-09-01
 

package/README.md

@@ -4,29 +4,27 @@
 
 # skill-family-engineering-kit
 
-<!-- release-skill:release-version: 0.17.0 -->
+<!-- release-skill:release-version: 0.19.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.17.0** (2026-09-01)
+**0.19.0** (2026-09-07)
 
-Engineering Kit 0.17.0 separates CodeBuddy from WorkBuddy host verification and adds an opt-in structural comparison against a provider-owned engineering baseline.
+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**
 
-- 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.
+- 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.
 
 **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.
+- 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.
 
 **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.
+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.
 <!-- release-skill:managed:end id=latest-release -->
 
 ### Foundation 0.15.0 candidate qualification entries
@@ -56,7 +54,7 @@ Kit is the "engineering stage" layer, depending on the Harness and Contracts. It
 
 ## Installation and Minimal Example
 
-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:
+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:
 
 ```sh
 pack_dir="$(mktemp -d)"
@@ -64,21 +62,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.17.0.tgz" "$pack_dir/skill-family-harness-node-0.17.0.tgz" "$pack_dir/skill-family-engineering-kit-0.17.0.tgz")
+(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")
 ```
 
 After publication, use the registry coordinate:
 
 ```sh
-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>
+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>
 ```
 
-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`.
+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`.
 
 ### Three adoption journeys
 
@@ -297,4 +295,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.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.
+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.

package/README.zh-CN.md

@@ -5,29 +5,27 @@
 
 # skill-family-engineering-kit
 
-<!-- release-skill:release-version: 0.17.0 -->
+<!-- release-skill:release-version: 0.19.0 -->
 
 开发与 CI 阶段使用的工程工具包。**恰好四个**顶层命令，没有第五个：
 
 <!-- release-skill:managed:start id=latest-release -->
-**0.17.0** (2026-09-01)
+**0.19.0** (2026-09-07)
 
-Engineering Kit 0.17.0 将 CodeBuddy 与 WorkBuddy 的宿主验证分开，并新增按需启用的提供方工程基线结构比较。
+Engineering Kit 0.19.0 把新批量传输投影进官方离线 Bundle，并在内置能力目录登记 mechanism-batch 能力。
 
 **新增**
 
-- 新增 codebuddy-print-v1 driver，按 CodeBuddy 的 .codebuddy/skills 项目目录发现技能；既有 workbuddy-codebuddy-print-v1 driver 与 WorkBuddy 布局保持不变。
-- 新增 describeSkeletonReferenceImplementation，并由 scaffoldTarget 返回该参考骨架身份。
-- adopt-plan 新增须成对使用的 --engineering-baseline 与 --compare-skeleton。结果只报告参考侧独有、目标侧独有、条目类型和文件类别差异，不裁定合规、等价、严重程度或豁免。
+- 官方 Bundle 投影携带 runMechanismCliBatch、--batch CLI 模式、两个机制批量 Schema 与冻结的批量容量政策，来源身份、摘要与完整性处理不变。
+- 能力目录新增 foundation.harness.mechanism-batch：since 0.19.0、stability candidate，并登记意图、失败语义与直接测试引用。
 
 **变更**
 
-- public-plugin 骨架生成的 check 脚本新增 skill-family-kit check entries --root .；其他 Profile 的检查命令保持不变。
-- 宿主管理的登录态、领域验收和真实宿主资格继续归消费者负责。
+- 采用指导补充批量选择规则：同进程调用保留既有对象入口；跨进程、相互独立且容量允许的 canonical-json 请求可作为批量候选；有依赖或超限请求保留原路径。
 
 **升级说明**
 
-三个 Foundation 包须一起精确锁定到 0.17.0。CodeBuddy 与 WorkBuddy 即使消费同一插件载荷，也必须走独立宿主路由。基线比较只读且按需启用；规则语义与基线发布仍由基线提供方负责。
+三个 Foundation 包须一起精确锁定到 0.19.0，升级后按既有包身份与 provenance 规则重建官方 Bundle。该目录条目为候选能力：目录命中不构成稳定采用声明。
 <!-- release-skill:managed:end id=latest-release -->
 
 ### Foundation 0.15.0 candidate 资格入口
@@ -57,7 +55,7 @@ Kit 是「工程阶段」层，依赖 Harness 与 Contracts。它只做四件事
 
 ## 安装和最小示例
 
-0.17.0 是本地候选版本。候选验证先把三个包分别打入同一个临时目录，再安装这三个精确 tarball：
+0.18.0 是本地候选版本。候选验证先把三个包分别打入同一个临时目录，再安装这三个精确 tarball：
 
 ```sh
 pack_dir="$(mktemp -d)"
@@ -65,21 +63,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.17.0.tgz" "$pack_dir/skill-family-harness-node-0.17.0.tgz" "$pack_dir/skill-family-engineering-kit-0.17.0.tgz")
+(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")
 ```
 
 发布后再使用 registry 坐标：
 
 ```sh
-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 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 exec --package=skill-family-engineering-kit@0.17.0 -- skill-family-kit --help`。
+以上四条命令分别覆盖生成骨架、只读盘点、受管投影与诊断；零安装形式可用 `npm exec --package=skill-family-engineering-kit@0.19.0 -- skill-family-kit --help`。
 
 ### 三条采用旅程
 
@@ -298,4 +296,4 @@ Foundation 本身不发起网络请求，但绑定的 executable 仍可能联网
 
 独立入口 `runSkillFamilyDirectoryVerification({ request, bindings })` 固定 Kimi 生产 argv 与窄环境，并拒绝调用方 observation。原始 parser 通过生产进程路径验证，但受控 fixture 事件不会被提升为 `observed`；缺少官方 typed mapping 时，公共结果保持 `indeterminate` 和 manual candidate。
 
-0.17.0 为本地源码候选，尚未发布。消费本地已验证的三包 tarball；版本标记、单元测试或安装成功都不等于契约接入完成、迁移完成或真实宿主资格。
+0.18.0 为本地源码候选，尚未发布。消费本地已验证的三包 tarball；版本标记、单元测试或安装成功都不等于契约接入完成、迁移完成或真实宿主资格。

package/candidate/profile-bundle.mjs

@@ -76,6 +76,16 @@ const ADDITIONAL_FOUNDATION_SCHEMA_FILES = Object.freeze([
   ["fixed-set-publication-receipt.schema.json", "src/schemas/fixed-set-publication-receipt.schema.json", "schemas/foundation/fixed-set-publication-receipt.schema.json"],
   ["schema-validation-batch-request.schema.json", "candidate/foundation-mechanisms/schema-validation-batch-request.schema.json", "schemas/foundation/schema-validation-batch-request.schema.json"],
   ["schema-validation-batch-result.schema.json", "candidate/foundation-mechanisms/schema-validation-batch-result.schema.json", "schemas/foundation/schema-validation-batch-result.schema.json"],
+  ["mechanism-batch-request.schema.json", "candidate/foundation-mechanisms/mechanism-batch-request.schema.json", "schemas/foundation/mechanism-batch-request.schema.json"],
+  ["mechanism-batch-result.schema.json", "candidate/foundation-mechanisms/mechanism-batch-result.schema.json", "schemas/foundation/mechanism-batch-result.schema.json"],
+]);
+
+// Non-Schema Foundation assets projected verbatim. They are deliberately kept
+// out of ADDITIONAL_FOUNDATION_SCHEMA_FILES: the schema graph claims a
+// document.$id for every schema row, while the capacity policy is a plain
+// JSON authority with no Schema identity.
+const ADDITIONAL_FOUNDATION_ASSET_FILES = Object.freeze([
+  ["mechanism-batch-policy.json", "candidate/foundation-mechanisms/mechanism-batch-policy.json", "schemas/foundation/mechanism-batch-policy.json"],
 ]);
 
 const HARNESS_IMPORT_MAP = new Map([
@@ -96,6 +106,7 @@ const HARNESS_STRICT_READ_IMPORT_MAP = new Map([
 
 const HARNESS_CLI_IMPORT_MAP = new Map([
   ["./quickstart-profile.mjs", "./runner.mjs"],
+  ["skill-family-contracts/quickstart-profile", "./runtime/contracts-candidate/index.mjs"],
 ]);
 
 const HARNESS_ATOMIC_IMPORT_MAP = new Map([
@@ -980,13 +991,22 @@ function projectContractsCandidateIndex(sourceText) {
       `schema load path ${fileName}`,
     );
   }
-  for (const [fileName] of ADDITIONAL_FOUNDATION_SCHEMA_FILES.filter(([name]) => name.startsWith("schema-validation-batch-"))) {
+  for (const [fileName] of ADDITIONAL_FOUNDATION_SCHEMA_FILES.filter(
+    ([name]) => name.startsWith("schema-validation-batch-") || name.startsWith("mechanism-batch-"),
+  )) {
     applyOnce(
       `load(new URL("../foundation-mechanisms/${fileName}", import.meta.url))`,
       `load(new URL("../../schemas/foundation/${fileName}", import.meta.url))`,
       `schema load path ${fileName}`,
     );
   }
+  for (const [fileName] of ADDITIONAL_FOUNDATION_ASSET_FILES) {
+    applyOnce(
+      `load(new URL("../foundation-mechanisms/${fileName}", import.meta.url))`,
+      `load(new URL("../../schemas/foundation/${fileName}", import.meta.url))`,
+      `asset load path ${fileName}`,
+    );
+  }
 
   const getCollectionMarker = "function getCollection(";
   const getCollectionHits = projected.split(getCollectionMarker).length - 1;
@@ -1124,7 +1144,7 @@ function runnerSource() {
     'export { validateQuickstartProfileDocument } from "./runtime/contracts-candidate/index.mjs";',
     'export { validateBySchemaId } from "./validators.mjs";',
     'export { createFilesystemRootBinding, readFileBound } from "./runtime/harness/bound-read.mjs";',
-    'export { createFixedSetPublicationManifest, publishFixedSet } from "./runtime/harness/fixed-set-publication.mjs";',
+    'export { createFixedSetPublicationManifest, publishFixedSet, replaceFixedSetAtomic } from "./runtime/harness/fixed-set-publication.mjs";',
     'export { publishFileExclusive, publishFileOrReplace, replaceFileAtomic } from "./runtime/harness/atomic.mjs";',
     'export { acquireFilesystemLock, inspectFilesystemLock, releaseFilesystemLock, recoverFilesystemLock } from "./runtime/harness/token-lock.mjs";',
     'import { invokeFoundationMechanism as invokeHarnessMechanism } from "./runtime/harness/quickstart-profile.mjs";',
@@ -1238,6 +1258,10 @@ export async function buildQuickstartProfileProjection({
   for (const [fileName, sourcePath] of ADDITIONAL_FOUNDATION_SCHEMA_FILES) {
     additionalSchemaTexts[fileName] = await readSourceText(contractsRoot, sourcePath);
   }
+  const additionalAssetTexts = {};
+  for (const [fileName, sourcePath] of ADDITIONAL_FOUNDATION_ASSET_FILES) {
+    additionalAssetTexts[fileName] = await readSourceText(contractsRoot, sourcePath);
+  }
   sources.harnessIndex = await readSourceText(harnessRoot, "src/index.mjs");
   sources.harnessCandidate = await readSourceText(harnessRoot, "candidate/quickstart-profile.mjs");
   sources.harnessMechanismsCli = await readSourceText(harnessRoot, "candidate/mechanisms-cli.mjs");
@@ -1453,6 +1477,9 @@ export async function buildQuickstartProfileProjection({
   for (const [fileName, , bundlePath] of ADDITIONAL_FOUNDATION_SCHEMA_FILES) {
     setText(bundlePath, additionalSchemaTexts[fileName]);
   }
+  for (const [fileName, , bundlePath] of ADDITIONAL_FOUNDATION_ASSET_FILES) {
+    setText(bundlePath, additionalAssetTexts[fileName]);
+  }
   setText("schemas/foundation/operation-request.schema.json", sources.operationRequest);
   setText("schemas/foundation/operation-result.schema.json", sources.operationResult);
   setText("schemas/foundation/migration-manifest.schema.json", sources.migrationManifestSchema);
@@ -1591,6 +1618,11 @@ export async function buildQuickstartProfileProjection({
       additionalSchemaTexts[fileName],
       "projected",
     ]),
+    ...ADDITIONAL_FOUNDATION_ASSET_FILES.map(([fileName, sourcePath]) => [
+      `packages/skill-family-contracts/${sourcePath}`,
+      additionalAssetTexts[fileName],
+      "projected",
+    ]),
     ["packages/skill-family-contracts/candidate/quickstart-profile/index.mjs", sources.candidateIndex, "extraction-input"],
     ["packages/skill-family-harness-node/package.json", harnessPackageJsonText, "identity"],
     ["packages/skill-family-harness-node/src/index.mjs", sources.harnessIndex, "imported-surface"],

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

@@ -2128,6 +2128,53 @@
     "Return malicious-concurrency threats to Foundation as a minimal capability gap; do not copy a walker, native addon, Harness, schema, Registry, runner or receipt chain locally"
    ]
   },
+  {
+   "id": "foundation.harness.fixed-set-publication",
+   "intent": "Publish one complete fixed set without replacement, or atomically exchange one complete staged sibling with an existing target directory",
+   "useWhen": [
+    "Need to publish a complete directory only when the target is absent",
+    "Need to replace one existing directory with a complete staged sibling under the same canonical parent"
+   ],
+   "doNotUseWhen": [
+    "Source and target cannot be real sibling directories under one canonical parent",
+    "Need a copy, merge, backup, automatic rollback or retry workflow"
+   ],
+   "prerequisites": [
+    "Install exact matching versions of all three Foundation packages on a packaged Darwin or Linux GNU platform",
+    "Source and target trees contain only real directories and single-link regular files",
+    "The caller exclusively controls both directory names for the duration of the call"
+   ],
+   "inputs": [
+    "createFixedSetPublicationManifest and publishFixedSet take a complete source, target parent, safe target segment and frozen manifest",
+    "replaceFixedSetAtomic takes { sourceRoot, targetParent, targetSegment } for an existing target sibling"
+   ],
+   "outputs": [
+    "No-replace publication returns a structured publication receipt",
+    "Verified replacement returns both paths, published and displaced closure digests, and published, committed, verified, namespace-synced state"
+   ],
+   "sideEffects": [
+    "No-replace publication moves the source directory to an absent target after verification",
+    "Replacement performs one native directory exchange and leaves the displaced target at sourceRoot; Foundation deletes neither side"
+   ],
+   "failureSemantics": [
+    "Supported pre-commit replacement failure preserves the original target path and bytes",
+    "Replacement mechanism failures use SFC2004 with atomic-replace-failed and a phase, publication, commit, verification and durability tuple",
+    "Unsupported replacement platforms use SFC2004 with unsupported-platform"
+   ],
+   "invariants": [
+    "Neither path falls back to a JavaScript check-then-rename sequence",
+    "Replacement commits through one Darwin RENAME_SWAP or Linux RENAME_EXCHANGE under one verified parent handle",
+    "Replacement is not idempotent; the same call exchanges the directories back"
+   ],
+   "ownedByCaller": [
+    "Meaning and acceptance of the directory contents",
+    "Staging lifecycle, cleanup of the displaced target after verified success, and recovery decisions after post-commit or indeterminate failure"
+   ],
+   "routeElsewhere": [
+    "Remote release authorization and publication: route to release-skill",
+    "Directory rendering and payload selection: keep in the consuming product"
+   ]
+  },
   {
    "id": "foundation.harness.executable-identity-observation",
    "intent": "Observe an explicitly bound executable entry, symlink chain, interpreter and launch bytes as a read-only point-in-time fact for an immediately pre-launch re-observation",
@@ -2170,6 +2217,49 @@
     "Malicious-concurrency, kernel-image or signature-proof gaps return to Foundation; do not copy a walker, native addon, Harness, schema, Registry, runner or receipt chain locally"
    ]
   },
+  {
+   "id": "foundation.harness.mechanism-batch",
+   "intent": "Combine mutually independent canonical-json requests that would otherwise need one cross-process invocation each into a single bounded, same-operation, ordered batch transport, reducing repeated process starts and transfer overhead",
+   "useWhen": [
+    "Multiple mutually independent canonical-json requests need per-item cross-process invocation (one process start and transfer each) and item count plus request/response bytes fit the capacity recorded in the capability catalog",
+    "The caller has the same-version official Bundle with a verified source and takes on the caller responsibility of domain grouping and batch splitting"
+   ],
+   "doNotUseWhen": [
+    "Requests already live in the same Node process (reuse the existing invokeFoundationMechanism object entry point; do not introduce a wrapper with no benefit)",
+    "A later item depends on an earlier item's result, or concurrency, caching, retry, automatic splitting, or cross-item references are needed",
+    "The request exceeds the batch capacity, or contains operations outside this batch (such as schema batch validation, self-check, or fixed-set publication writes)"
+   ],
+   "prerequisites": [
+    "Contracts, Harness, and Engineering Kit are pinned to exactly the same version; the official Bundle is generated from same-version packages and keeps source identity, digest, and integrity checks",
+    "The caller supplies the input/output/error streams (process standard streams by default); domain grouping, capacity splitting, and stream acceptance stay with the caller"
+   ],
+   "inputs": [
+    "One JSON document with exactly operation (canonical-json) and inputs (non-empty ordered array; each item is {document}); NDJSON, session protocols, and automatic array detection are unsupported"
+   ],
+   "outputs": [
+    "{results:[{inputIndex,exitCode,response}]}; successful items carry the original mechanism response and failed items the original CLI error object, in input order"
+   ],
+   "sideEffects": [
+    "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"
+   ],
+   "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"
+   ],
+   "ownedByCaller": [
+    "Domain grouping and capacity splitting, and judging dependencies between requests",
+    "Version availability and maturity judgment (since 0.19.0 and candidate status live in the catalog and API documentation), the exact pin, and source-identity binding",
+    "Batch adoption completion and domain acceptance judgment"
+   ],
+   "routeElsewhere": [
+    "Concurrency, caching, retry, cross-item references, or automatic splitting: keep them on the original consumer path, or return a real common gap to Foundation as a minimal capability contract",
+    "Mechanisms outside this batch (schema batch validation, self-check, fixed-set publication writes, and so on) keep their existing public entry points"
+   ]
+  },
   {
    "id": "foundation.kit.plugin-verification",
    "intent": "Preserve the complete plugin layout and add dedicated Qoder and WorkBuddy production lifecycle drivers while keeping structure and host semantics separate",

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

@@ -1395,6 +1395,32 @@
    "migration": "none",
    "promotionPolicy": "consumer-transparent"
   },
+  {
+   "id": "foundation.harness.fixed-set-publication",
+   "package": "skill-family-harness-node",
+   "layer": "harness",
+   "since": "0.9.0",
+   "stability": "stable",
+   "adoptionScopes": ["harness", "engineering-kit"],
+   "entrypoints": [
+    "skill-family-harness-node: createFixedSetPublicationManifest, publishFixedSet, replaceFixedSetAtomic (packages/skill-family-harness-node/src/fixed-set-publication.mjs)",
+    "skill-family-harness-node/fixed-set-publication: createFixedSetPublicationManifest, publishFixedSet, replaceFixedSetAtomic (packages/skill-family-harness-node/src/fixed-set-publication.mjs)"
+   ],
+   "sourceRefs": [
+    "packages/skill-family-harness-node/src/fixed-set-publication.mjs",
+    "packages/skill-family-harness-node/src/fixed-set-publication-loader.mjs",
+    "packages/skill-family-harness-node/src/native/bound_read.c",
+    "packages/skill-family-engineering-kit/candidate/profile-bundle.mjs"
+   ],
+   "positiveTestRefs": [
+    "packages/skill-family-harness-node/test/stable-filesystem-operations.test.mjs",
+    "packages/skill-family-engineering-kit/test/candidate-profile-bundle.test.mjs"
+   ],
+   "negativeTestRefs": [
+    "packages/skill-family-harness-node/test/stable-filesystem-operations.test.mjs",
+    "packages/skill-family-engineering-kit/test/candidate-profile-bundle.test.mjs"
+   ]
+  },
   {
    "id": "foundation.harness.executable-identity-observation",
    "package": "skill-family-harness-node",
@@ -1418,6 +1444,39 @@
    "migration": "none",
    "promotionPolicy": "consumer-transparent"
   },
+  {
+   "id": "foundation.harness.mechanism-batch",
+   "package": "skill-family-harness-node",
+   "layer": "harness",
+   "since": "0.19.0",
+   "stability": "candidate",
+   "adoptionScopes": ["harness"],
+   "entrypoints": [
+    "runMechanismCliBatch (packages/skill-family-harness-node/candidate/mechanisms-cli.mjs)",
+    "mechanisms-cli.mjs --batch (packages/skill-family-harness-node/candidate/mechanisms-cli.mjs)"
+   ],
+   "sourceRefs": [
+    "packages/skill-family-contracts/candidate/foundation-mechanisms/mechanism-batch-policy.json",
+    "packages/skill-family-contracts/candidate/foundation-mechanisms/mechanism-batch-request.schema.json",
+    "packages/skill-family-contracts/candidate/foundation-mechanisms/mechanism-batch-result.schema.json",
+    "packages/skill-family-harness-node/candidate/mechanisms-cli.mjs",
+    "packages/skill-family-engineering-kit/candidate/profile-bundle.mjs"
+   ],
+   "positiveTestRefs": [
+    "packages/skill-family-contracts/test/quickstart-profile.test.mjs",
+    "packages/skill-family-harness-node/test/quickstart-profile.test.mjs",
+    "packages/skill-family-engineering-kit/test/candidate-mechanisms-cli.test.mjs",
+    "packages/skill-family-engineering-kit/test/candidate-profile-bundle.test.mjs"
+   ],
+   "negativeTestRefs": [
+    "packages/skill-family-contracts/test/quickstart-profile.test.mjs",
+    "packages/skill-family-harness-node/test/quickstart-profile.test.mjs",
+    "packages/skill-family-engineering-kit/test/candidate-mechanisms-cli.test.mjs",
+    "packages/skill-family-engineering-kit/test/candidate-profile-bundle.test.mjs"
+   ],
+   "migration": "none",
+   "promotionPolicy": "consumer-transparent"
+  },
   {
    "id": "foundation.kit.plugin-verification",
    "package": "skill-family-engineering-kit",

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

@@ -2127,6 +2127,53 @@
     "恶意并发威胁交回 Foundation 形成最小能力缺口；不得本地复制 walker、native addon、Harness、schema、Registry、runner 或 receipt 链"
    ]
   },
+  {
+   "id": "foundation.harness.fixed-set-publication",
+   "intent": "在目标缺失时发布一个完整固定集合，或把一个完整暂存兄弟目录与既有目标目录原子交换",
+   "useWhen": [
+    "只在目标缺失时发布一棵完整目录树",
+    "用同一规范父目录下的完整暂存兄弟目录替换一个既有目录"
+   ],
+   "doNotUseWhen": [
+    "源目录和目标目录无法成为同一规范父目录下的真实兄弟目录",
+    "需要复制、合并、备份、自动回滚或重试流程"
+   ],
+   "prerequisites": [
+    "在带有固定预构建闭包的 Darwin 或 Linux GNU 平台安装精确匹配的三个 Foundation 包版本",
+    "源树和目标树只含真实目录与单链接普通文件",
+    "调用期间由调用方独占两个目录名称"
+   ],
+   "inputs": [
+    "createFixedSetPublicationManifest 与 publishFixedSet 接收完整源目录、目标父目录、安全目标段和冻结 manifest",
+    "replaceFixedSetAtomic 为既有兄弟目标接收 { sourceRoot, targetParent, targetSegment }"
+   ],
+   "outputs": [
+    "不替换发布返回结构化 publication receipt",
+    "确认替换成功后返回两个路径、发布与被置换闭包摘要，以及 published、committed、verified、namespace-synced 状态"
+   ],
+   "sideEffects": [
+    "不替换发布经验证后，把源目录移动到不存在的目标路径",
+    "替换执行一次原生目录交换，被置换的旧目标留在 sourceRoot；Foundation 不删除任一侧"
+   ],
+   "failureSemantics": [
+    "受支持的提交前替换失败保留原目标路径和字节",
+    "替换机制失败使用 SFC2004 与 atomic-replace-failed，并携带阶段、发布、提交、验证和持久化状态 tuple",
+    "不支持替换的平台使用 SFC2004 与 unsupported-platform"
+   ],
+   "invariants": [
+    "两条路径都不降级到 JavaScript 检查后改名序列",
+    "替换在一个已验证父目录句柄下，通过一次 Darwin RENAME_SWAP 或 Linux RENAME_EXCHANGE 提交",
+    "替换不是幂等操作；相同调用会把两个目录交换回去"
+   ],
+   "ownedByCaller": [
+    "目录内容的含义与接受策略",
+    "暂存目录生命周期、确认成功后的旧目标清理，以及提交后或不确定失败的恢复决定"
+   ],
+   "routeElsewhere": [
+    "远程发布授权与发布动作交给 release-skill",
+    "目录渲染与载荷选择留在消费产品"
+   ]
+  },
   {
    "id": "foundation.harness.executable-identity-observation",
    "intent": "逐次只读观察显式绑定根中的可执行入口、符号链接链、脚本解释器与启动字节，供消费者在启动前紧邻重观察",
@@ -2169,6 +2216,49 @@
     "恶意并发、内核映像或签名证明缺口交回 Foundation；不得复制 walker、native addon、Harness、schema、Registry、runner 或 receipt 链"
    ]
   },
+  {
+   "id": "foundation.harness.mechanism-batch",
+   "intent": "把相互独立、需逐项跨进程调用的 canonical-json 请求合并为一次有界、同操作、顺序执行的批量传输，减少重复进程启动与传输开销",
+   "useWhen": [
+    "多个相互独立的 canonical-json 请求需要逐项跨进程调用（每项一次进程启动与传输），且项数与请求/响应字节落在能力目录登记的容量内",
+    "调用方已安装来源明确的同版本官方 Bundle，并承担领域分组与批次切分的调用方责任"
+   ],
+   "doNotUseWhen": [
+    "请求已位于同一 Node 进程内（优先复用既有 invokeFoundationMechanism 对象入口，不引入无收益的流包装）",
+    "后项输入依赖前项结果，或需要并发、缓存、重试、自动拆批或跨项引用",
+    "请求超过批次容量，或包含本批未支持的操作（如 schema 批量校验、self-check、固定集合写入）"
+   ],
+   "prerequisites": [
+    "Contracts、Harness 与 Engineering Kit 精确锁定同一版本；官方 Bundle 由同版本三包生成并保留来源身份、摘要与完整性检查",
+    "调用方提供 input/output/error 流（默认进程标准流）；领域分组、容量切分与流接收责任归调用方"
+   ],
+   "inputs": [
+    "恰好包含 operation（canonical-json）与 inputs（非空有序数组，每项 {document}）的一个 JSON 文档；不支持 NDJSON、会话协议或数组自动探测"
+   ],
+   "outputs": [
+    "{results:[{inputIndex,exitCode,response}]}；成功项 response 为原机制结果，失败项为原 CLI 错误对象，顺序与输入一致"
+   ],
+   "sideEffects": [
+    "无（逐项经既有纯函数分派器执行；只写调用方提供的 output/error 流；无文件、网络、进程或残余状态副作用）"
+   ],
+   "failureSemantics": [
+    "整批结构或容量拒绝向 error 流写一个批次错误对象并整体退出 2（TypeError 投影；details.kind 封闭为 batch-structure-invalid、batch-item-limit、batch-input-limit、batch-output-limit）",
+    "单项机制失败按原 CLI 错误投影写入该项 response 并继续执行后续项；至少一项失败整体退出 2；不交付部分批次结果"
+   ],
+   "invariants": [
+    "全部项的外层形状检查先于第一项执行；项顺序、重复项与逐项调用次数保持不变",
+    "完整响应字节在确认未超输出上限前不发送；错误对象不重新排序或规范化"
+   ],
+   "ownedByCaller": [
+    "领域分组与容量切分、请求间依赖关系的判断",
+    "版本可用性与成熟度判断（since 0.19.0、candidate 由目录与 API 文档携带）、精确 pin 与来源身份绑定",
+    "批次采用完成与领域验收判定"
+   ],
+   "routeElsewhere": [
+    "需要并发、缓存、重试、跨项引用或自动拆分：由消费者保留原路径处理，或把真实共性缺口交回 Foundation 形成最小能力合同",
+    "本批未支持的机制（schema 批量校验、self-check、固定集合写入等）保留各自既有公共入口"
+   ]
+  },
   {
    "id": "foundation.kit.plugin-verification",
    "intent": "保留完整插件布局，增加 Qoder 与 WorkBuddy 专属生产生命周期 driver，并把结构合同与宿主语义分开",