docs: sweep em dashes out of the active published surface
Em dashes crept back into examples, docs/platform-native.md, several READMEs,
the ponytail-debt skill, and a command file since 88431de. Replaced with plain
punctuation (commas, matching the house convention), .openclaw mirror
regenerated. Follows 88431de's scope: leaves untouched the vendored caveman
SKILL.md and the dated benchmarks/results/ writeups (historical records).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 4.8
parent
bd6176a9b3
commit
426ffd0b36
@@ -92,11 +92,11 @@ python judge.py --run runs/<stamp> # score every workspace's source
|
||||
|
||||
Fewer lines only counts as a win if the code still does the job. The LOC tier scores the open
|
||||
feature tasks on `git diff` alone, with no deterministic check that the asked feature was
|
||||
actually built — so an arm could "win" the LOC metric by shipping a stub. This pass closes that
|
||||
actually built, so an arm could "win" the LOC metric by shipping a stub. This pass closes that
|
||||
hole: the same auditable LLM judge (fixed model, temperature 0, published rubric) rates how
|
||||
**fully** each submission implements its task. Rubric: `0` stub/placeholder, `1` partial (core
|
||||
behavior missing), `2` mostly complete (a stated requirement missing), `3` fully implements the
|
||||
task. Read it **alongside** the LOC table — a low-LOC arm whose completeness also drops is doing
|
||||
task. Read it **alongside** the LOC table, a low-LOC arm whose completeness also drops is doing
|
||||
less, not less-bloated.
|
||||
|
||||
Validated like the over-engineering judge: `--selftest` requires the judge to rank a complete
|
||||
|
||||
Reference in New Issue
Block a user