Release Benchmark Audit Trail

One entry per release, comparing each develop prerelease against the previous publicly published release on the corefast grid (10 config cells × 3 ≤100-row docs, extraction model held at a shared control both versions can run). Each entry is written once and never overwritten — this table is the durable history.

Generate a new entry with make benchmark-release VERSION=<new> PREV=<published> (see the Benchmarking Guide).

Release	vs (published)	Accuracy	Cost	Notable	Report
v0.6.0	v0.5.16	flat (0.917 = 0.917)	−32.5% total (advanced −44–55%)	cacheRead −95%; one integrated-confidence completeness regression on long lists; v0.6 fixes v0.5.16 advanced-assessment timeouts	v0.6.0.md

What each entry contains

TL;DR — safe-to-upgrade verdict + the headline accuracy/cost/latency deltas.
Methodology notes — the control model, disabled steps, doc set, and any cross-version config-compatibility handling (so the A/B is apples-to-apples).
Per-cell table — cost/recall/latency per config cell, both versions.
Regressions & improvements — anything past the aggregate.py --compare thresholds, with root cause verified from S3 output + metering.
Reproduce — the exact commands, plus honesty caveats (n, pricing estimate date).

Raw scored data for each side lives (unpublished) under benchmarks/results/<release>/summary.{json,csv} + meta.json.