Skip to content

Official Codebase of 3DCodeVerse

Python

sections: the front-back judge slice says "front right" — +Z (the front) is drawn on the right

gaoypeng715fc069811a
diff --git a/harness/CLAUDE.md b/harness/CLAUDE.md
index 79055bfc..09672ac0 100644
--- a/harness/CLAUDE.md
+++ b/harness/CLAUDE.md
@@ -47,7 +47,7 @@ push, with `set -o pipefail` so a `| tail` cannot swallow a red exit. The versi
`tests/core/test_portability.py`. Details: `docs/INSTALL.md` §2.1.
## Environment (this machine)
-- Gemini keys: `~/.config/astra3d/gemini_keys.env` (21 keys) → `get_settings().gemini_api_keys`
+- Gemini keys: `~/.config/astra3d/gemini_keys.env` (15 keys, the owner's list of 2026-09-22) → `get_settings().gemini_api_keys`
(or `GEMINI_API_KEYS` / `GEMINI_API_KEY` env). Settings: `~/.config/3dcodeverse/config.yaml`
or `./3dcodeverse.yaml`, env prefix `C3D_` (the pre-D78 `CV3D_*` names are still read) (`C3D_RENDER__GPU=off`, `C3D_RUNS_DIR=…`,
`C3D_DEFAULT_CANDIDATES=2`). Every `C3D_*` switch is a `Settings` field read through `get_settings()`
diff --git a/harness/codeverse3d/spatial/sections.py b/harness/codeverse3d/spatial/sections.py
index 08790297..b17e1a7b 100644
--- a/harness/codeverse3d/spatial/sections.py
+++ b/harness/codeverse3d/spatial/sections.py
@@ -94,7 +94,7 @@ def cross_section(
#: horizontal axis index, human title, axes note). Vertical is Y (up) on both.
JUDGE_SLICE_PLANES: dict[str, tuple[int, int, str, str]] = {
"front_back": (0, 2, "front-back",
- "horizontal = front-back (Z, front left), vertical = up (Y); cut at centre x"),
+ "horizontal = front-back (Z, front right), vertical = up (Y); cut at centre x"),
"left_right": (2, 0, "left-right",
"horizontal = left-right (X), vertical = up (Y); cut at centre z"),
}
diff --git a/harness/docs/DECISIONS.md b/harness/docs/DECISIONS.md
index 482b062a..310f0978 100644
--- a/harness/docs/DECISIONS.md
+++ b/harness/docs/DECISIONS.md
@@ -934,7 +934,8 @@ Pointers: EVAL, PAPER_WRITING = `eval/docs/*.md`; COST, RUNBOOK, ARCHITECTURE, I
(`build_last.json` gone). JS syntax: one node process per lint, a content-hash cache (scene lint
2.4–2.7 s → 0.01–0.24 s), `node --check` confirms any rejection. One section renderer: the
`cross_section` tool draws through the D48 judge path, whose slices are pinned to the pixel.
- KNOWN, not fixed (owner's call): the front_back slice says "front left", the front is drawn right.
+ The front_back slice's note said "front left" while +Z (front) is drawn on the right; the note
+ now says "front right" (owner: the label must match the image the judge gets).
* **D89 Evaluation states uncertainty one way (2026-09-22).** `eval/bench/stats.py`: the paired 95 %
Student-t interval ("separated" = excludes zero; 2·SE understated it by 15–38 % at n = 4–8), the
exact sign test, `statistics.correlation`. Every journal is read through `_jsonl.read_jsonl`
diff --git a/harness/tests/spatial_tools/data/judge_slices/slice_front_back.png b/harness/tests/spatial_tools/data/judge_slices/slice_front_back.png
index 60e3c39e..8346005b 100644
Binary files a/harness/tests/spatial_tools/data/judge_slices/slice_front_back.png and b/harness/tests/spatial_tools/data/judge_slices/slice_front_back.png differ