e670788eeeb3e33d6d935d9bac0d76cbdb684c7b
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.
Description
No description provided
Languages
Nim
73.7%
Python
18%
Shell
3.7%
Java
3.5%
HTML
1%
Other
0.1%