harbor-rayrun 0.1.0__tar.gz

harbor_rayrun-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,62 @@
+name: release
+
+on:
+  push:
+    tags:
+      - "v*"
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Install package and test dependencies
+        run: |
+          python -m pip install --upgrade pip
+          python -m pip install -e '.[test]'
+      - name: Run tests
+        run: python -m pytest tests -q
+
+  pypi:
+    needs: test
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      contents: read
+      id-token: write
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.13"
+      - name: Verify tag matches package version
+        run: |
+          python - <<'PY'
+          import os
+          import tomllib
+
+          version = tomllib.load(open("pyproject.toml", "rb"))["project"]["version"]
+          tag = os.environ["GITHUB_REF_NAME"]
+          assert tag == f"v{version}", f"tag {tag} != v{version}"
+          PY
+      - name: Build sdist and wheel
+        run: |
+          python -m pip install --upgrade pip build twine
+          python -m build
+          python -m twine check dist/*
+      - name: Smoke import from the built wheel
+        run: |
+          python -m pip install dist/*.whl
+          python -c "import harbor_rayrun; print(harbor_rayrun.RayrunEnvironment.__name__)"
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

harbor_rayrun-0.1.0/.gitignore

@@ -0,0 +1,7 @@
+# Python 工程的生成物
+.venv/
+__pycache__/
+.pytest_cache/
+*.egg-info/
+dist/
+build/

harbor_rayrun-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 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 [yyyy] [name of copyright owner]
+
+   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.

harbor_rayrun-0.1.0/Makefile

@@ -0,0 +1,28 @@
+# harbor-rayrun —— 构建配方（仓库根：make <target>）
+#
+# 本仓库只有 provider 这一个 Python 包，所以它的「构建」= 建 venv + 装依赖，
+# 「测试」= pytest。依赖网络与 PyPI 镜像，显式跑 `make test`。
+
+VENV     ?= .venv
+PYTHON   ?= python3
+# 与仓库其它地方一致：国内直连 PyPI 不稳，走清华镜像（可用 PIP_INDEX 覆盖）。
+PIP_INDEX ?= https://pypi.tuna.tsinghua.edu.cn/simple
+
+.PHONY: venv test lint clean
+
+venv: $(VENV)/.installed
+
+$(VENV)/.installed: pyproject.toml src/harbor_rayrun/*.py
+	$(PYTHON) -m venv $(VENV)
+	$(VENV)/bin/pip install -q -i $(PIP_INDEX) -e '.[test]'
+	@touch $@
+
+test: venv ## 单测（httpx.MockTransport 打桩，不打真网络）
+	$(VENV)/bin/python -m pytest tests -q
+
+lint: venv ## 语法/导入自检（没有引入 ruff：不为一个包加新工具链）
+	$(VENV)/bin/python -m compileall -q src tests
+	$(VENV)/bin/python -c "import harbor_rayrun; print('import OK:', harbor_rayrun.RayrunEnvironment.__name__)"
+
+clean:
+	rm -rf $(VENV) .pytest_cache src/*.egg-info src/harbor_rayrun/__pycache__ tests/__pycache__

harbor_rayrun-0.1.0/PKG-INFO

@@ -0,0 +1,124 @@
+Metadata-Version: 2.5
+Name: harbor-rayrun
+Version: 0.1.0
+Summary: Harbor provider：把 Rayrun 沙箱云接成 Harbor 的评测环境
+Project-URL: Homepage, https://github.com/RayrunOS/harbor-rayrun
+Project-URL: Repository, https://github.com/RayrunOS/harbor-rayrun
+License: Apache-2.0
+License-File: LICENSE
+Requires-Python: >=3.12
+Requires-Dist: harbor<0.24,>=0.23.0
+Requires-Dist: httpx>=0.27
+Provides-Extra: test
+Requires-Dist: pytest-asyncio>=0.24; extra == 'test'
+Requires-Dist: pytest>=8; extra == 'test'
+Description-Content-Type: text/markdown
+
+# harbor-rayrun —— Rayrun 的 Harbor provider
+
+把 **Rayrun 沙箱云**接成 [Harbor](https://docs.harborframework.com) 的评测环境：Harbor 每个
+trial 的隔离环境由 provider 实现，本包把它落到 Rayrun 的 HTTP API 上。
+
+本仓库是 **独立仓库**（2026-11-15 从 Rayrun 主仓库的 `integrations/harbor-rayrun/` 拆出）。
+下文出现的 `docs/...`、`images/...`、`CLAUDE.md` 都指
+[Rayrun 主仓库](https://github.com/RayrunOS/RayrunOS) 内的路径：设计真相源
+`docs/plans/harbor-integration.md`（M3），外部契约取证见 `docs/15` §2.1。
+
+## 它负责什么
+
+| Harbor 契约 | 落到 Rayrun |
+|---|---|
+| `start(force_build)` | 校验镜像在宿主机上 → `POST /v1/sandboxes`（201 即 Running） |
+| `stop(delete=True/False)` | `DELETE /sandboxes/{id}` / `POST …/stop`（**ADR-005 冷停**：留盘、停表、IP 不变） |
+| `exec(command, cwd, env, timeout_sec, user)` | `POST /sandboxes/{id}/exec`（**同步**；M1 新落的原语，ADR-007） |
+| `upload_file` / `upload_dir` | `PUT /sandboxes/{id}/files/{path}`（先 `mkdir -p` —— guestd 写文件不建父目录） |
+| `download_file` / `download_dir` | `GET …/files/{path}`；列目录是**单层**的，provider 自己走递归 |
+| `is_dir` / `is_file` | 用基类默认实现（走 `exec` 的 `test -d/-f`），不覆写 |
+
+**它不负责什么**：不构建镜像（镜像由平台 builder `POST /v1/builds` 或离线 builder 产出，见下）、
+不做 SSH/流式（`stream` 档位未开）、不支持 GPU / TPU / Windows / docker-compose。
+
+## 用法
+
+```bash
+# 1. 装（Harbor 与 provider 在同一个 Python 环境里）
+uv pip install harbor-rayrun
+# 或从源码：uv pip install git+ssh://git@github.com/RayrunOS/harbor-rayrun.git
+# 或在本仓库根目录：uv pip install .
+
+# 2. 凭证（沿用 CLI 的 env 名，docs/07 §2.5）
+# 托管环境（2026-10-28 起）：https://api.rayrunos.com/v1
+# 自托管 / dev：           http://<daemon 主机>:8080/v1
+# ⚠️ dashboard.rayrunos.com/v1 已 410，不是 API 入口
+export RAYRUN_API_URL=https://api.rayrunos.com/v1
+export RAYRUN_TOKEN=rayrun_<token_id>_<secret>
+
+# 3. 跑（provider 用 --env 的 module:Class 入口，不需要改 Harbor 上游）
+harbor run -t <task> -a oracle -e harbor_rayrun:RayrunEnvironment
+```
+
+镜像名默认取 `<environment_name>@1`，可用两个环境变量覆盖：
+`RAYRUN_IMAGE_PREFIX`（前缀，例如 `tb-`）与 `RAYRUN_IMAGE_VERSION`。
+
+## 两条必须先知道的前提
+
+**1. 镜像要先在目标 Rayrun 环境里备好。** 两条路：
+
+- **线上/托管**：用平台 builder 现场构建（`POST /v1/builds`，ADR-024），产物是
+  `<name>@<version>`，跑完删除。**不要把本地 `rootfs.ext4` / 镜像目录传到线上**
+  （`docs/howto/harbor-on-rayrun.md` §1.2；CLAUDE.md §6）。
+- **本地 dev**：用离线 builder `images/build-task-image.sh` 产出到本机
+  `RAYRUN_IMAGES_DIR`，见 `docs/plans/harbor-integration.md` §10。
+
+镜像缺失时 `start()` 会直接报错并附一条**可直接复制**的构建命令，不猜、不静默。
+
+**构建时带 `--root-writable`**（旧的「三个 `--writable-dir`」方案已被它取代）：
+
+```bash
+images/build-task-image.sh --dockerfile <任务的 Dockerfile> \
+    --name <name> --version 1 --out /tmp/task-images --root-writable
+```
+
+这不是可选优化。沙箱里**清单外的目录一律只读**（ADR-006：可写面是固定 7 个子树
+`/usr /etc /var /opt /root /home /srv` + `/workspace` 盘），而 Harbor 的
+`/logs`（reward 写在这里）`/tests` `/solution` 全在清单外 ⇒ 少了可写面，verifier 连
+`/logs/verifier/reward.txt` 都写不出来，症状只是「reward 文件不存在」。`--root-writable`
+用 overlay + pivot_root 让 `/` 与 docker 语义一致；任务镜像自己的 `WORKDIR`（典型 `/app`）
+也由 guestd 按 manifest 的 `[run].workdir` 自动补挂。见 `docs/plans/harbor-integration.md`
+§13.3 / §13.11 与 ADR-006 修订。
+
+**2. 网络策略的映射是精确的**（2026-09-27 起）：
+
+| Harbor `NetworkPolicy` | Rayrun `egress` |
+|---|---|
+| `no-network` | `allow: []`（完全断网） |
+| `allowlist` | `allow: [...]`（域名精确匹配 + IPv4 CIDR） |
+| `public`（**Harbor 的默认**） | `allow_all: true`（显式档位，Rayrun 侧会进审计） |
+
+三者都**精确执行**、不做静默近似。`public` 那一档曾经只能被拒绝（Rayrun 当时没有「允许
+全部」），为此产品侧补了 `egress.allow_all`（`06` §4.3）—— 于是默认任务也能跑，而「这台
+沙箱开了全出网」在 Rayrun 的 journal（`sandbox.created.payload.egress.allow_all`）里看得见。
+
+## 依赖
+
+- 运行时：`harbor>=0.23,<0.24`（提供 `BaseEnvironment` 抽象面）+ `httpx`（打 Rayrun API）。
+  **刻意不引 Rayrun 的生成式 SDK** —— provider 只用 8 个端点，薄客户端足够；SDK 生成是独立
+  立项（`docs/15` §10-Q7），将来若落地，换掉 `client.py` 即可、provider 契约不变。
+- 开发/测试：`pytest` + `pytest-asyncio`（见 `[project.optional-dependencies]`）。
+
+## 测试
+
+```bash
+make test        # 首次会建 .venv 并从 PyPI 镜像装依赖（需要网络）
+```
+
+单测用 `httpx.MockTransport` 打桩，覆盖的都是**会静默出错**的地方：能力虚报、PUBLIC 被悄悄
+降级、镜像缺失没有可操作提示、超时没有可判定退出码、写文件不建父目录。基线用**真**
+`BaseEnvironment`（不是 stub），所以能力声明的字段名是**对着装好的 harbor 版本**核过的 ——
+`main` 分支与 0.23.0 的 `EnvironmentCapabilities` 字段并不相同（0.23.0 没有 `stream`），
+pydantic 会静默忽略未知字段，写错不会报错。
+
+## 与真机验收的分工
+
+单测钉 provider 的判断；**真沙箱链路**（建沙箱 → exec → 文件 → 销毁）归
+`docs/plans/harbor-integration.md` 的 **M4**（Harbor 端到端 reward 比对）。

harbor_rayrun-0.1.0/README.md

@@ -0,0 +1,108 @@
+# harbor-rayrun —— Rayrun 的 Harbor provider
+
+把 **Rayrun 沙箱云**接成 [Harbor](https://docs.harborframework.com) 的评测环境：Harbor 每个
+trial 的隔离环境由 provider 实现，本包把它落到 Rayrun 的 HTTP API 上。
+
+本仓库是 **独立仓库**（2026-11-15 从 Rayrun 主仓库的 `integrations/harbor-rayrun/` 拆出）。
+下文出现的 `docs/...`、`images/...`、`CLAUDE.md` 都指
+[Rayrun 主仓库](https://github.com/RayrunOS/RayrunOS) 内的路径：设计真相源
+`docs/plans/harbor-integration.md`（M3），外部契约取证见 `docs/15` §2.1。
+
+## 它负责什么
+
+| Harbor 契约 | 落到 Rayrun |
+|---|---|
+| `start(force_build)` | 校验镜像在宿主机上 → `POST /v1/sandboxes`（201 即 Running） |
+| `stop(delete=True/False)` | `DELETE /sandboxes/{id}` / `POST …/stop`（**ADR-005 冷停**：留盘、停表、IP 不变） |
+| `exec(command, cwd, env, timeout_sec, user)` | `POST /sandboxes/{id}/exec`（**同步**；M1 新落的原语，ADR-007） |
+| `upload_file` / `upload_dir` | `PUT /sandboxes/{id}/files/{path}`（先 `mkdir -p` —— guestd 写文件不建父目录） |
+| `download_file` / `download_dir` | `GET …/files/{path}`；列目录是**单层**的，provider 自己走递归 |
+| `is_dir` / `is_file` | 用基类默认实现（走 `exec` 的 `test -d/-f`），不覆写 |
+
+**它不负责什么**：不构建镜像（镜像由平台 builder `POST /v1/builds` 或离线 builder 产出，见下）、
+不做 SSH/流式（`stream` 档位未开）、不支持 GPU / TPU / Windows / docker-compose。
+
+## 用法
+
+```bash
+# 1. 装（Harbor 与 provider 在同一个 Python 环境里）
+uv pip install harbor-rayrun
+# 或从源码：uv pip install git+ssh://git@github.com/RayrunOS/harbor-rayrun.git
+# 或在本仓库根目录：uv pip install .
+
+# 2. 凭证（沿用 CLI 的 env 名，docs/07 §2.5）
+# 托管环境（2026-10-28 起）：https://api.rayrunos.com/v1
+# 自托管 / dev：           http://<daemon 主机>:8080/v1
+# ⚠️ dashboard.rayrunos.com/v1 已 410，不是 API 入口
+export RAYRUN_API_URL=https://api.rayrunos.com/v1
+export RAYRUN_TOKEN=rayrun_<token_id>_<secret>
+
+# 3. 跑（provider 用 --env 的 module:Class 入口，不需要改 Harbor 上游）
+harbor run -t <task> -a oracle -e harbor_rayrun:RayrunEnvironment
+```
+
+镜像名默认取 `<environment_name>@1`，可用两个环境变量覆盖：
+`RAYRUN_IMAGE_PREFIX`（前缀，例如 `tb-`）与 `RAYRUN_IMAGE_VERSION`。
+
+## 两条必须先知道的前提
+
+**1. 镜像要先在目标 Rayrun 环境里备好。** 两条路：
+
+- **线上/托管**：用平台 builder 现场构建（`POST /v1/builds`，ADR-024），产物是
+  `<name>@<version>`，跑完删除。**不要把本地 `rootfs.ext4` / 镜像目录传到线上**
+  （`docs/howto/harbor-on-rayrun.md` §1.2；CLAUDE.md §6）。
+- **本地 dev**：用离线 builder `images/build-task-image.sh` 产出到本机
+  `RAYRUN_IMAGES_DIR`，见 `docs/plans/harbor-integration.md` §10。
+
+镜像缺失时 `start()` 会直接报错并附一条**可直接复制**的构建命令，不猜、不静默。
+
+**构建时带 `--root-writable`**（旧的「三个 `--writable-dir`」方案已被它取代）：
+
+```bash
+images/build-task-image.sh --dockerfile <任务的 Dockerfile> \
+    --name <name> --version 1 --out /tmp/task-images --root-writable
+```
+
+这不是可选优化。沙箱里**清单外的目录一律只读**（ADR-006：可写面是固定 7 个子树
+`/usr /etc /var /opt /root /home /srv` + `/workspace` 盘），而 Harbor 的
+`/logs`（reward 写在这里）`/tests` `/solution` 全在清单外 ⇒ 少了可写面，verifier 连
+`/logs/verifier/reward.txt` 都写不出来，症状只是「reward 文件不存在」。`--root-writable`
+用 overlay + pivot_root 让 `/` 与 docker 语义一致；任务镜像自己的 `WORKDIR`（典型 `/app`）
+也由 guestd 按 manifest 的 `[run].workdir` 自动补挂。见 `docs/plans/harbor-integration.md`
+§13.3 / §13.11 与 ADR-006 修订。
+
+**2. 网络策略的映射是精确的**（2026-09-27 起）：
+
+| Harbor `NetworkPolicy` | Rayrun `egress` |
+|---|---|
+| `no-network` | `allow: []`（完全断网） |
+| `allowlist` | `allow: [...]`（域名精确匹配 + IPv4 CIDR） |
+| `public`（**Harbor 的默认**） | `allow_all: true`（显式档位，Rayrun 侧会进审计） |
+
+三者都**精确执行**、不做静默近似。`public` 那一档曾经只能被拒绝（Rayrun 当时没有「允许
+全部」），为此产品侧补了 `egress.allow_all`（`06` §4.3）—— 于是默认任务也能跑，而「这台
+沙箱开了全出网」在 Rayrun 的 journal（`sandbox.created.payload.egress.allow_all`）里看得见。
+
+## 依赖
+
+- 运行时：`harbor>=0.23,<0.24`（提供 `BaseEnvironment` 抽象面）+ `httpx`（打 Rayrun API）。
+  **刻意不引 Rayrun 的生成式 SDK** —— provider 只用 8 个端点，薄客户端足够；SDK 生成是独立
+  立项（`docs/15` §10-Q7），将来若落地，换掉 `client.py` 即可、provider 契约不变。
+- 开发/测试：`pytest` + `pytest-asyncio`（见 `[project.optional-dependencies]`）。
+
+## 测试
+
+```bash
+make test        # 首次会建 .venv 并从 PyPI 镜像装依赖（需要网络）
+```
+
+单测用 `httpx.MockTransport` 打桩，覆盖的都是**会静默出错**的地方：能力虚报、PUBLIC 被悄悄
+降级、镜像缺失没有可操作提示、超时没有可判定退出码、写文件不建父目录。基线用**真**
+`BaseEnvironment`（不是 stub），所以能力声明的字段名是**对着装好的 harbor 版本**核过的 ——
+`main` 分支与 0.23.0 的 `EnvironmentCapabilities` 字段并不相同（0.23.0 没有 `stream`），
+pydantic 会静默忽略未知字段，写错不会报错。
+
+## 与真机验收的分工
+
+单测钉 provider 的判断；**真沙箱链路**（建沙箱 → exec → 文件 → 销毁）归
+`docs/plans/harbor-integration.md` 的 **M4**（Harbor 端到端 reward 比对）。

harbor_rayrun-0.1.0/pyproject.toml

@@ -0,0 +1,33 @@
+[project]
+name = "harbor-rayrun"
+version = "0.1.0"
+description = "Harbor provider：把 Rayrun 沙箱云接成 Harbor 的评测环境"
+readme = "README.md"
+license = { text = "Apache-2.0" }
+requires-python = ">=3.12"
+# 依赖只有两个：Harbor 本体（提供 BaseEnvironment 抽象面）与 httpx（打 Rayrun 的
+# HTTP API）。**刻意不引 Rayrun 的生成式 SDK** —— provider 只用 8 个端点，薄客户端
+# 足够，且 SDK 生成是独立立项（15 §10-Q7）。将来若 SDK 落地，换掉 client.py 即可，
+# provider 的契约不变。
+dependencies = [
+    "harbor>=0.23.0,<0.24",
+    "httpx>=0.27",
+]
+
+[project.optional-dependencies]
+test = ["pytest>=8", "pytest-asyncio>=0.24"]
+
+[project.urls]
+Homepage = "https://github.com/RayrunOS/harbor-rayrun"
+Repository = "https://github.com/RayrunOS/harbor-rayrun"
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/harbor_rayrun"]
+
+[tool.pytest.ini_options]
+asyncio_mode = "auto"
+testpaths = ["tests"]

harbor_rayrun-0.1.0/src/harbor_rayrun/__init__.py

@@ -0,0 +1,17 @@
+"""harbor-rayrun —— 把 Rayrun 沙箱云接成 Harbor 的评测环境。
+
+Harbor 的 `BaseEnvironment.type()` 显式允许返回任意字符串（它的注释写明是为了让
+仓库之外的第三方环境不必改 `EnvironmentType` 枚举），所以本 provider **不需要**
+Harbor 上游改动即可用 `--env` 入口加载：
+
+    uv pip install ./integrations/harbor-rayrun
+    export RAYRUN_API_URL=https://api.rayrunos.com/v1   # 自托管：http://<daemon>:8080/v1
+    export RAYRUN_TOKEN=rayrun_<token_id>_<secret>
+    harbor run -t <task> -a oracle -e harbor_rayrun:RayrunEnvironment
+
+环境变量沿用 CLI 的同名约定（`07` §2.5），不新造一套 key 体系。
+"""
+
+from harbor_rayrun.environment import RayrunEnvironment
+
+__all__ = ["RayrunEnvironment"]