# Legacy Local Benchmark Summaries
This directory preserves historical local measurement summaries across
`just clean`. The retained v0.4.6 report and README chart used these inputs.
The current v0.5.0-versus-v0.4.6 report and chart use shared complete-run evidence
under [`docs/performance-runs/`](../performance-runs/README.md). New measurements
use that complete-run format; the [Benchmarking guide](../BENCHMARKING.md)
owns the current workflow.
## Contents
- [Saved runs](#saved-runs)
- [Reading retained reports](#reading-retained-reports)
- [Comparing measurements](#comparing-measurements)
- [Historical availability](#historical-availability)
## Saved runs
Historical comparisons were saved under
`<current>-vs-<baseline>/<run-digest>/`. The digest identifies the snapshot's
contents. These files retain their original schemas and hashes; new runs do not
write this format.
Each snapshot contains:
| `performance.full.csv` | Every recorded baseline and current benchmark, including diagnostic and peer cases outside the report selection |
| `performance.full.provenance.json` | Full-summary schema, CSV digest, phase counts, and the source, harness, dependency, CPU, OS, toolchain, command, and validation provenance |
| `performance.csv` | Selected report inputs, including peer context |
| `performance.provenance.json` | Validated metadata and digest for the selected report inputs |
The full CSV stores the Criterion benchmark ID, measurement phase, mean and
median in nanoseconds, their 95% confidence intervals, and sample count. Numbers
retain floating-point precision rather than the rounded values displayed in
Markdown. Each recorded case must have valid metadata, estimates, and 100 raw
samples before publication. Baseline-only peers remain explicitly baseline
measurements; missing current measurements are never filled from an older run.
`latest.json` identifies the last saved legacy snapshot. New complete-run
publication maintains its own shared index and latest pointer instead.
## Reading retained reports
Read these original CSV/JSON records and the
[archived Markdown reports](../archive/performance/README.md) directly.
Their writers, custom renderer and conversion declaration are retired.
`performance-doc` and `performance-readme` require shared complete-run evidence;
they do not consume these summaries. Unsupported legacy scratch inputs block
fallback to older history, so archive or remove those scratch files first.
Legacy summaries cannot be converted losslessly into complete-run evidence:
they retain aggregate statistics and sample counts, but not the raw samples.
The [Benchmarking guide](../BENCHMARKING.md) owns current report and README
publication, including source freshness and measured-asset checks.
## Comparing measurements
Compare rows by benchmark identity and measurement phase, with the recorded
environment and harness held comparable. Baseline and current rows come from
separate executions. New cases can have only a current measurement, and peer
measurements reused by the report can have only a baseline measurement.
These CSVs support comparisons of recorded point estimates and intervals.
Recomputing Criterion statistics requires the raw samples, which are not stored
here. The GitHub release workflow separately publishes full raw Criterion
archives from its hosted runner; those are a different measurement environment
and do not substitute for local results.
## Historical availability
This retention workflow cannot recover measurements previously discarded with
temporary worktrees. If `latest.json` is absent, no complete local snapshot has
been promoted yet. Existing [archived Markdown reports](../archive/performance/README.md)
retain their selected summaries, but do not establish complete historical
coverage. A new authorized measurement run is required to fill that gap.
Completed optimization investigations and decisions are in
[archived studies](../archive/performance/studies/README.md).
The [Benchmarking guide](../BENCHMARKING.md) owns execution procedures.