Empirical Proof Benchmark — the measuring instrument (ruler)
Harvest the benchmark harness/scorer from the never-deploy `feature/devday-scan`
branch onto `main` as a **deterministic A/B measuring instrument** — a "ruler"
that takes two Claude Code session transcripts (one produced with Anatomia, one
vanilla) and emits a tamper-evident, reproducible comparison: tokens, tool calls,
cost, and the reliability metrics that carry the product's "verified over trusted"
claim.
Dead export `totalTokens` — defined with full JSDoc, never called anywhere (cost uses derived.tokens; the edit-token walk inlines its own input+output sum)
aggregate treats 'lower is better' for every numeric metric, including distinctFilesRead/inputTokens/turns — an arm that reads fewer files (even by missing relevant ones) scores a 'win'. Spec-endorsed simplification, but a semantic foot-gun for the next reader.
AC7 guard (A036/A037) is a textual substring assertion on scorer.ts source — a future read of a best-effort field via destructuring-rename or computed key would slip past. Legitimate enforcement test, but textual not semantic.
The three to-first-correct-edit metrics can disagree on null-ness: wallClockMsToFirstCorrectEdit is null when the editing line lacks a parseable timestamp, even while turnsToResolution/tokensToFirstCorrectEdit are populated. Latent inconsistency; not triggered by the committed fixtures.
Determinism test (A034) only asserts same-input idempotence, not stability across input permutations. Implementation genuinely sorts by (task,metric,arm) so cross-permutation determinism holds, but the test would pass even if the explicit sort were removed.