Skip to content

Official Codebase of 3DCodeVerse

Python

docs: SKILLS and SKILLS_LEDGER name the prompt manifest as the pin of scene skills delivery — test_delivery_reaches_the_session.py went

gaoypengd0d4e92b5632
diff --git a/harness/docs/SKILLS.md b/harness/docs/SKILLS.md
index 762359ec..9df52262 100644
--- a/harness/docs/SKILLS.md
+++ b/harness/docs/SKILLS.md
@@ -648,9 +648,8 @@ so; the rest are live.
`baseline_tasks` returned `[]`, so round 0 listed four bundles to a session that did not
exist. Measured at **0 opens / 30 listings**. The generating stages now attach and record with
their own kind (`scene.js` is assembled without a session since the compose fallback went,
- 2026-09-22). `tests/skills/test_delivery_reaches_the_session.py` runs a real
- two-zone-session scene and proves env/zone attach exactly once, before generation,
- with matching telemetry. **The scene bundles' read rate against working delivery
+ 2026-09-22). The prompt manifest's scene scenarios pin each stage's `skills.attached`
+ event and its routed bundles. **The scene bundles' read rate against working delivery
is UNMEASURED — that is the next wave's first experiment.**
* ~~**`api-agent` has no skill affordance.**~~ **FIXED earlier**, and re-measured here: with
`read_skill` it opens **58%** of listed bundles (51/88) across sessions that are offered
diff --git a/harness/docs/SKILLS_LEDGER.md b/harness/docs/SKILLS_LEDGER.md
index 11239059..ea7d27e8 100644
--- a/harness/docs/SKILLS_LEDGER.md
+++ b/harness/docs/SKILLS_LEDGER.md
@@ -273,8 +273,9 @@ two effect owners independently found the right one in the code:
`_deliver_skills` (attach + inline) and `_record_skills` (telemetry), attaching with their
own kind so the router's rows fire as written. The zone fan-out attaches **once**, outside
the worker, because three parallel sessions share one workspace and would race the same
-`AGENTS.md`. `tests/skills/test_delivery_reaches_the_session.py` now holds every
-agent-driving module to the hook, pins the per-stage kinds, and pins the fan-out placement.
+`AGENTS.md`. The prompt manifest's scene scenarios (`tests/prompts/manifest.py`) now pin
+each stage's `skills.attached` event and the bundles it routed (the dedicated
+`test_delivery_reaches_the_session.py` went in the 2026-09-23 test cut).
(Since D70 the zones stage is ONE session; the fan-out arm was removed 2026-09-21 and the
test now pins one attach before that one session. Since 2026-09-22 env and zones share one
wrapper, `SceneTrack._stage_session`, in place of `_deliver_skills` / `_record_skills`.)