skill-family-harness-node 0.1.0

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,131 @@
+# 贡献者公约（Contributor Covenant Code of Conduct）
+
+本行为准则采用 Contributor Covenant 2.1 标准文本，来源明确：
+`https://www.contributor-covenant.org/version/2/1/code_of_conduct/`。
+译文与解读以英文原文为准；执行联系方式见文末。
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement through the
+source repository's private channels (see SECURITY.md for private reporting).
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+`https://www.contributor-covenant.org/version/2/1/code_of_conduct/`.
+
+Community Impact Guidelines were inspired by Mozilla's code of conduct
+enforcement ladder.
+
+For answers to common questions about this code of conduct, see the FAQ at
+`https://www.contributor-covenant.org/faq`.
+
+[homepage]: https://www.contributor-covenant.org

package/CONTRIBUTING.md

@@ -0,0 +1,69 @@
+# 贡献指南（Contributing）
+
+感谢关注 `skill-family-foundation-workspace`。本文件说明本地开发环境、
+验证流程与 PR 规则。行为准则见 [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md)，
+Git 写操作的授权边界见仓库内文档站的生命周期指南（`docs/git-lifecycle.md`）。
+
+拓扑说明：本工作区仓永久 private，是唯一开发真源；三个 public 仓
+（`skill-family-contracts`、`skill-family-harness-node`、
+`skill-family-engineering-kit`）是版本化发布镜像，不承载完整开发历史与
+测试，也不接受直接 PR 或 issue。本指南描述的是私有工作区内经授权的开发
+流程；消费坐标与发布状态唯一见 `docs/status/current.md`。
+
+## 本地安装
+
+必需工具（精确版本见仓库内 `docs/setup.md` 的安装合同）：
+
+- Node.js：`>=22.22.2 <23`（版本取自 `.node-version`）
+- pnpm：10.30.0（`packageManager` 精确锁定）
+- Python：3.10 或更高（仅文档站构建需要）
+
+```bash
+pnpm install
+pnpm synth
+pnpm check
+```
+
+- `pnpm synth` 再生成 projen 受管文件。受管文件只能通过修改
+  `.projenrc.js` 间接变更；手写源码、文档和 fixture 不会被 synth 覆盖。
+- `pnpm check` 是统一根门禁：10 个稳定门禁 ID 按固定顺序串联执行，
+  任一步骤非 0 即整体失败。
+
+## 提交 PR 前必须做到
+
+1. 只修改当前任务授权的文件，不顺手改动无关文件；
+2. 修改 `.projenrc.js` 后运行 `pnpm synth`，并保证连续两次 synth 零漂移；
+3. 本地完整通过根门禁：
+
+   ```bash
+   pnpm check
+   ```
+
+4. 涉及文档时额外运行文档事实与链接检查：
+
+   ```bash
+   node scripts/docs/fact-check.mjs
+   node scripts/docs/link-check.mjs
+   ```
+
+5. 涉及三个叶子包时，确认发布字节合同仍然成立：
+
+   ```bash
+   pnpm run release-artifacts:build -- --output .artifacts/publish-candidates
+   pnpm run release-artifacts:verify -- --root .artifacts/publish-candidates --manifest .artifacts/publish-candidates/release-artifacts.manifest.json
+   ```
+
+## PR 规则
+
+- PR 描述须包含：动机、变更面、本地门禁结果（退出码）与剩余风险；
+- 不得为转绿而弱化任何产品门禁、Action pin、权限、泄漏策略或 tarball 合同；
+- 不新增运行时依赖，除非先经评审并显式修订泄漏策略中的公开依赖清单；
+- 不提交生成物与本地状态：`node_modules`、`site/`、`.artifacts/`、缓存、
+  日志、凭据或本机绝对路径一律不进入提交；
+- 受管投影必须与产生它的源变更在同一 PR 内提交，禁止手改受管文件；
+- 动态状态（实时发布状态、远端对象状态）不写入版本化文档，唯一产品状态
+  口径见 `docs/status/current.md`。
+
+## 安全报告
+
+漏洞报告渠道与支持版本见 [SECURITY.md](SECURITY.md)。

package/LICENSE

@@ -0,0 +1,202 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright (c) 2026 skill-family-foundation-workspace contributors
+   Copyright (c) 2026 广州市风荷科技有限公司
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,64 @@
+<!-- release-skill:safe-first-command -->
+<!-- release-skill:external-write-boundary -->
+
+# skill-family-harness-node
+
+Contracts 机制协议的**唯一默认 Node 实现**。这是一个薄运行时（thin runtime）：只实现机制协议，不引入业务语义，不做第二语言实现。
+
+## 边界
+
+- 消费 `skill-family-contracts`（工作区依赖），复用其方言路由的 Ajv validator、Kernel Protocol、冻结错误码与 fixture；不复制协议定义，不重新解释 Schema。
+- 只实现机制：Schema 校验、原子写、路径收容、临时工作区、资源闭包、operation-request → operation-result 管道。
+- 明确排除：业务语义、任务编排、Git 写入、模型调用、远程网络、发布状态。见 `HARNESS_EXCLUSIONS`。
+
+## 公共 API
+
+| 导出 | 职责 |
+| --- | --- |
+| `HARNESS_CAPABILITIES` / `HARNESS_EXCLUSIONS` | 能力与排除清单（冻结常量）。 |
+| `HarnessError` / `HARNESS_ERROR_KINDS` / `mechanismError` | 机制失败统一携带注册错误码 `SFC2004`，`details.kind` 给出稳定细分。 |
+| `validateContractDocument` / `getValidator` / `resolveSchemaContext` / `validatorCacheSize` | 按 Schema 方言路由并缓存 validator；复用 Contracts 的 Ajv 实例与 dialect/policy 语义。 |
+| `classifyPathInput` / `resolveContained` / `readFileContained` | 路径收容：拦截路径越界、符号链接逃逸、真实路径逃逸。 |
+| `writeFileAtomic` | 原子写：失败不留半成品（临时文件 + fsync + rename）。 |
+| `TemporaryWorkspace` / `createTemporaryWorkspace` / `withTemporaryWorkspace` | 自动清理的临时工作区，异常路径也清理。 |
+| `digestBytes` / `computeResourceClosure` / `closureContains` | 资源闭包与确定性 sha256 摘要。 |
+| `parseRequest` / `processRequest` | 解析 `operation-request`，输出终态 `operation-result`。 |
+
+## 稳定错误码
+
+全部复用 Contracts 冻结登记表，不新增未登记码。机制失败统一为 `SFC2004`（EXECUTION_FAILED），`details.kind` 取 `HARNESS_ERROR_KINDS` 中的稳定值，例如 `path-traversal`、`symlink-escape`、`realpath-escape`、`atomic-write-failed`、`missing-resource`、`workspace-disposed`。
+
+新增一个全新的 SFC 码属于 Contracts 变更（登记表在 contracts 包内），超出本包写集；因此用「`SFC2004` + 稳定 `details.kind`」组合保持对外语义稳定。
+
+## 路径收容模型
+
+`resolveContained(root, rel)` 是所有文件系统访问的唯一入口，按序拒绝：
+
+1. 输入分级（`classifyPathInput`，纯函数可测）：拒绝绝对路径、Windows 盘符/UNC 路径、POSIX 上的反斜杠路径、空输入、NUL 字节。
+2. 词法收容：`path.resolve` 后离开根 → `path-traversal`。
+3. 符号链接逃逸：末位组件是指向根外的符号链接（或断链）→ `symlink-escape`。
+4. 真实路径逃逸：任一中间符号链接链的规范化结果离开根 → `realpath-escape`。
+
+比较基于 `realpath` 之后的规范根，避免 macOS `/var → /private/var` 一类系统级符号链接造成误判。
+
+## 测试
+
+`node --test` 覆盖：Contracts fixture 全量回放、安全反例（三类逃逸均被拦截且零越界写）、原子性失败路径无残留、临时工作区异常清理、闭包确定性、Windows 路径/整数/正则/`format` 边界。
+
+## 安装
+
+```sh
+npm install skill-family-harness-node
+```
+
+## 最小示例
+
+```js
+// release-skill: harness runtime validation
+import { validateContractDocument } from "skill-family-harness-node";
+const result = validateContractDocument(doc, { schemaId: "project-manifest" });
+```
+
+## 故障诊断
+
+机制失败统一抛出 `SFC2004`（EXECUTION_FAILED），`details.kind` 给出稳定细分（如 `path-traversal`、`atomic-write-failed`）。如失败，检查 root 路径是否正确且目标文件未被锁定。

package/SECURITY.md

@@ -0,0 +1,34 @@
+# 安全策略（Security Policy）
+
+## 支持的版本
+
+| 版本 | 安全支持状态 |
+| --- | --- |
+| 0.1.x | 当前维护线：接受安全报告 |
+| 0.0.0 | 未发布的内部骨架版本，不在公开支持范围 |
+
+安全修复只承诺在最新的 0.1.x 线上提供；更早版本不回移修复。
+
+## 报告漏洞
+
+请勿通过公开 issue 直接披露未修复的安全漏洞。private workspace 仓永久
+private，不是公开报告渠道；请通过任一 public 发布镜像仓（例如
+`https://github.com/ifoohoo/skill-family-engineering-kit`）在 GitHub 上使用
+**Private vulnerability reporting**（仓库 Security 页签的
+"Report a vulnerability"）私下报告；如该通道不可用，再通过仓库维护者
+提供的私下联系方式报告。
+
+报告时请尽量提供：
+
+- 受影响的包与版本（`skill-family-contracts`、`skill-family-harness-node`、
+  `skill-family-engineering-kit`）；
+- 可复现的最小步骤或概念验证；
+- 影响范围与利用前提。
+
+## 处置承诺
+
+- 收到报告后先确认受理，再按影响面排期修复；
+- 修复发布前不公开披露细节；
+- 修复随下一个补丁版本发布，并在该版本的变更记录中说明。
+
+本文件只描述漏洞报告渠道与支持版本；实时发布状态不属于本文件范围。

package/package.json

@@ -0,0 +1,35 @@
+{
+  "name": "skill-family-harness-node",
+  "version": "0.1.0",
+  "private": false,
+  "description": "Thin Node.js mechanism runtime for Skill Family engineering contracts.",
+  "author": "广州市风荷科技有限公司",
+  "license": "Apache-2.0",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/ifoohoo/skill-family-harness-node.git"
+  },
+  "homepage": "https://github.com/ifoohoo/skill-family-harness-node",
+  "bugs": {
+    "url": "https://github.com/ifoohoo/skill-family-harness-node/issues"
+  },
+  "type": "module",
+  "engines": {
+    "node": ">=22.22.2 <23"
+  },
+  "exports": "./src/index.mjs",
+  "dependencies": {
+    "skill-family-contracts": "0.1.0"
+  },
+  "files": [
+    "src",
+    "SECURITY.md",
+    "CONTRIBUTING.md",
+    "CODE_OF_CONDUCT.md"
+  ],
+  "//": "~~ Generated by projen. To modify, edit .projenrc.js and run \"npx projen\".",
+  "scripts": {
+    "check": "node --test",
+    "test": "node --test"
+  }
+}

package/src/atomic.mjs

@@ -0,0 +1,114 @@
+import { lstat, mkdir, open, realpath, rename, rm } from "node:fs/promises";
+import { randomBytes } from "node:crypto";
+import path from "node:path";
+import process from "node:process";
+import { HARNESS_ERROR_KINDS, mechanismError } from "./errors.mjs";
+import { resolveContained } from "./paths.mjs";
+
+/**
+ * Atomic contained writes.
+ *
+ * Guarantees:
+ * - The target path is containment-checked first (path traversal, symlink
+ *   escape, realpath escape all reject before any write happens).
+ * - Content is written to a fresh temporary file in the target's own
+ *   directory (same filesystem), fsynced, then renamed over the target.
+ *   rename is atomic on POSIX, so readers observe either the complete old
+ *   content or the complete new content, never a partial file.
+ * - On any failure the temporary file is removed and the target keeps its
+ *   previous content (or stays absent). A failed write never leaves a
+ *   half-written target behind.
+ */
+
+function assertWritableData(data) {
+  const ok =
+    typeof data === "string" ||
+    Buffer.isBuffer(data) ||
+    ArrayBuffer.isView(data) ||
+    data instanceof ArrayBuffer;
+  if (!ok) {
+    throw new TypeError(
+      "writeFileAtomic: data must be a string, Buffer, TypedArray, DataView, or ArrayBuffer",
+    );
+  }
+}
+
+async function removeQuiet(candidate) {
+  try {
+    await rm(candidate, { force: true });
+  } catch {
+    // Cleanup is best-effort; the original failure is the one that counts.
+  }
+}
+
+/**
+ * Atomically writes `data` to `relPath` inside `root`.
+ * Options: { mode } (file mode for a newly created target, default 0o644).
+ * Returns the absolute contained target path that was written.
+ * Throws HarnessError (SFC2004) with a stable details.kind on failure.
+ */
+export async function writeFileAtomic(root, relPath, data, { mode = 0o644 } = {}) {
+  assertWritableData(data);
+  let target = await resolveContained(root, relPath);
+  // When the final component is a symlink to a contained target, write to the
+  // real target: rename would otherwise replace the link itself instead of
+  // updating the resource it points at. resolveContained already proved the
+  // real target stays inside the root.
+  try {
+    const finalStat = await lstat(target);
+    if (finalStat.isSymbolicLink()) {
+      target = await realpath(target);
+    }
+  } catch {
+    // Not yet existing: the lexical target is the write destination.
+  }
+  const dir = path.dirname(target);
+  try {
+    await mkdir(dir, { recursive: true });
+  } catch (cause) {
+    throw mechanismError(
+      HARNESS_ERROR_KINDS.ATOMIC_WRITE_FAILED,
+      `cannot prepare contained directory: ${cause && cause.code ? cause.code : "unknown"}`,
+      { input: relPath },
+    );
+  }
+  const tmpName = `.${path.basename(target)}.${process.pid}.${randomBytes(8).toString("hex")}.tmp`;
+  const tmpPath = path.join(dir, tmpName);
+  let handle = null;
+  try {
+    // wx => O_CREAT|O_EXCL: the temporary name is fresh and never clobbers.
+    handle = await open(tmpPath, "wx", mode);
+    await handle.writeFile(data);
+    await handle.sync();
+    await handle.close();
+    handle = null;
+    await rename(tmpPath, target);
+  } catch (cause) {
+    if (handle) {
+      try {
+        await handle.close();
+      } catch {
+        // Closing on the error path is best-effort.
+      }
+    }
+    await removeQuiet(tmpPath);
+    throw mechanismError(
+      HARNESS_ERROR_KINDS.ATOMIC_WRITE_FAILED,
+      `atomic write failed: ${cause && cause.code ? cause.code : "unknown"}`,
+      { input: relPath },
+    );
+  }
+  // Best-effort directory fsync so the rename itself is durable; platforms
+  // without directory fsync simply skip it.
+  try {
+    const dirHandle = await open(dir, "r");
+    try {
+      await dirHandle.sync();
+    } finally {
+      await dirHandle.close();
+    }
+  } catch {
+    // Durability hardening only; the atomicity guarantee already holds.
+  }
+  return target;
+}