env_reference: the ring mover was NEVER measured offline - correct a false label

The offline-harness audit (`e40c849`, `docs/offline_harness_trust.md`) found that the
claim "best offline hit rate of anything measured" for the ring mover was false.

The 20.28% figure is a LIVE number: `docs/feature_ab_results.md` and commit `bfdcdf8`
record 35 real-DrussGT bridge battles with a server-side event sidecar as the ground
truth, and the 6/49 round wins is likewise live. There is no offline measurement of
the ring mover anywhere - the offline harness scores GUNS, not movements, and has no
movement driver at all.

So this was NOT an offline-vs-live calibration failure, which is how it has been
described repeatedly (including by the orchestrator). It was a METRIC MISMATCH: a
movement arm judged on hit rate instead of damage/run and round wins - and hit rate is
precisely the metric that concealed its collapse.

The lesson previously attached to this result was therefore the wrong one. The
paragraph now says what actually happened and points at the audit.

Docs-only; no code touched.
This commit is contained in:
2026-09-24 21:44:17 +02:00
parent e40c8493a6
commit e670788eee
+11 -3
View File
@@ -338,9 +338,17 @@ Defaults read in `the_floor_is_lava_ring.nim:116-133`.
the **code defaults are `10.0` / `15.0`** (commit `7f6ccfb`). The code is the
truth.
**Ring mover is NOT the default and should not be shipped as-is:** it had the best
offline hit rate of anything measured, but it halves engagement range and **halves
survival** (round wins 16/49 → 6/49, p=0.012) — a glass cannon.
**Ring mover is NOT the default and should not be shipped as-is.** It had the best
**LIVE** hit rate of anything measured (20.28%, server-side event sidecar ground truth), but it
halves engagement range and **halves survival** (round wins 16/49 → 6/49, p=0.012) — a glass
cannon.
**CORRECTION (see `docs/offline_harness_trust.md`):** this line previously claimed the ring mover
had "the best offline hit rate". That was **wrong — the ring mover was never measured offline at
all**; the offline harness scores *guns*, and has no movement driver. So this was **not** an
offline-vs-live calibration failure (which is how it was repeatedly described). It was a **metric
mismatch**: a movement arm judged on hit rate instead of damage/run and round wins — and hit rate
is exactly the metric that hid its collapse.
## 5. Ramming