skill-family-engineering-kit 0.17.0 → 0.18.0

package/CHANGELOG.md

@@ -1,5 +1,24 @@
 # Changelog
 
+<!-- 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,24 @@
 # 变更日志
 
+<!-- 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,26 @@
 
 # skill-family-engineering-kit
 
-<!-- release-skill:release-version: 0.17.0 -->
+<!-- release-skill:release-version: 0.18.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.18.0** (2026-09-05)
 
-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.18.0 projects the stable Harness replaceFixedSetAtomic export into the existing offline Quickstart Bundle.
 
 **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 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**
 
-- 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.
+- 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.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.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:managed:end id=latest-release -->
 
 ### Foundation 0.15.0 candidate qualification entries
@@ -56,7 +53,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 +61,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.18.0
+npm exec --package=skill-family-engineering-kit@0.18.0 -- skill-family-kit --help
+npm exec --package=skill-family-engineering-kit@0.18.0 -- skill-family-kit scaffold --root <empty-dir> --project-id my-project
+npm exec --package=skill-family-engineering-kit@0.18.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.18.0 -- skill-family-kit projection --root <repo>
+npm exec --package=skill-family-engineering-kit@0.18.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.18.0 -- skill-family-kit --help`.
 
 ### Three adoption journeys
 
@@ -297,4 +294,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,26 @@
 
 # skill-family-engineering-kit
 
-<!-- release-skill:release-version: 0.17.0 -->
+<!-- release-skill:release-version: 0.18.0 -->
 
 开发与 CI 阶段使用的工程工具包。**恰好四个**顶层命令，没有第五个：
 
 <!-- release-skill:managed:start id=latest-release -->
-**0.17.0** (2026-09-01)
+**0.18.0** (2026-09-05)
 
-Engineering Kit 0.17.0 将 CodeBuddy 与 WorkBuddy 的宿主验证分开，并新增按需启用的提供方工程基线结构比较。
+Engineering Kit 0.18.0 将 Harness 稳定的 replaceFixedSetAtomic 导出投影到既有离线 Quickstart Bundle。
 
 **新增**
 
-- 新增 codebuddy-print-v1 driver，按 CodeBuddy 的 .codebuddy/skills 项目目录发现技能；既有 workbuddy-codebuddy-print-v1 driver 与 WorkBuddy 布局保持不变。
-- 新增 describeSkeletonReferenceImplementation，并由 scaffoldTarget 返回该参考骨架身份。
-- adopt-plan 新增须成对使用的 --engineering-baseline 与 --compare-skeleton。结果只报告参考侧独有、目标侧独有、条目类型和文件类别差异，不裁定合规、等价、严重程度或豁免。
+- 既有 candidate Bundle 携带稳定的固定集合替换源码、加载器、原生闭包与 replaceFixedSetAtomic 导出；不新增平行实现，也不增加 Kit 命令。
 
 **变更**
 
-- public-plugin 骨架生成的 check 脚本新增 skill-family-kit check entries --root .；其他 Profile 的检查命令保持不变。
-- 宿主管理的登录态、领域验收和真实宿主资格继续归消费者负责。
+- 包版本与 Contracts、Harness 一同升至 0.18.0，runProjection 继续作为 Bundle 的写入与授权边界。
 
 **升级说明**
 
-三个 Foundation 包须一起精确锁定到 0.17.0。CodeBuddy 与 WorkBuddy 即使消费同一插件载荷，也必须走独立宿主路由。基线比较只读且按需启用；规则语义与基线发布仍由基线提供方负责。
+三个 Foundation 包须一起精确锁定到 0.18.0，并从这些已安装包的精确字节重建受管 Bundle。Bundle 消费者获得相同的非幂等替换语义，不得盲目重试提交后或不确定结果。
 <!-- release-skill:managed:end id=latest-release -->
 
 ### Foundation 0.15.0 candidate 资格入口
@@ -57,7 +54,7 @@ Kit 是「工程阶段」层，依赖 Harness 与 Contracts。它只做四件事
 
 ## 安装和最小示例
 
-0.17.0 是本地候选版本。候选验证先把三个包分别打入同一个临时目录，再安装这三个精确 tarball：
+0.18.0 是本地候选版本。候选验证先把三个包分别打入同一个临时目录，再安装这三个精确 tarball：
 
 ```sh
 pack_dir="$(mktemp -d)"
@@ -65,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")
 ```
 
 发布后再使用 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.18.0
+npm exec --package=skill-family-engineering-kit@0.18.0 -- skill-family-kit --help
+npm exec --package=skill-family-engineering-kit@0.18.0 -- skill-family-kit scaffold --root <empty-dir> --project-id my-project
+npm exec --package=skill-family-engineering-kit@0.18.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.18.0 -- skill-family-kit projection --root <repo>
+npm exec --package=skill-family-engineering-kit@0.18.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.18.0 -- skill-family-kit --help`。
 
 ### 三条采用旅程
 
@@ -298,4 +295,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

@@ -1124,7 +1124,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";',

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",

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",

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": "逐次只读观察显式绑定根中的可执行入口、符号链接链、脚本解释器与启动字节，供消费者在启动前紧邻重观察",

package/docs/agents/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",

package/docs/agents/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",

package/docs/agents/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": "逐次只读观察显式绑定根中的可执行入口、符号链接链、脚本解释器与启动字节，供消费者在启动前紧邻重观察",

package/docs/architecture/index.html

@@ -1980,7 +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>同一 Git workspace 还包含 <code>packages/foundation-adoption-review/</code>。它是独立的 Plugin release unit 和公开镜像源，从 0.17.0 起与 Foundation 数值对齐，历史 0.1.0 发布保持不变。它使用 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>

package/docs/en/architecture/index.html

@@ -1980,7 +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>The same Git workspace also contains <code>packages/foundation-adoption-review/</code>. It is an independent Plugin release unit and public-mirror source. Starting with 0.17.0, its version number aligns with Foundation while the historical 0.1.0 release remains unchanged. 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>

package/docs/public/status/index.html

@@ -1792,17 +1792,17 @@
 <tbody>
 <tr>
 <td><code>skill-family-contracts</code></td>
-<td>0.17.0</td>
+<td>0.18.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.17.0</td>
+<td>0.18.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.17.0</td>
+<td>0.18.0</td>
 <td><a href="https://github.com/ifoohoo/skill-family-engineering-kit">ifoohoo/skill-family-engineering-kit</a></td>
 </tr>
 </tbody>