**Depends on:** #26 ## What to build After each benchmark run, generate a machine-readable `benchmarks/latest.json` summarizing current results for fast PR checks and tooling. ## Acceptance criteria - [ ] `benchmarks/latest.json` created/updated after each `deno task bench` run - [ ] JSON schema includes: timestamp, gitCommit, results[] (workspace, functionName, canonicalName, fixtureSize, stats) - [ ] File is stable (safe to diff in git) - [ ] Tooling can read latest results without scanning full history - [ ] Latest.json is generated in both normal and --baseline modes ## Out of scope - HTML rendering
Depends on: #26
What to build
After each benchmark run, generate a machine-readable
benchmarks/latest.jsonsummarizing current results for fast PR checks and tooling.Acceptance criteria
benchmarks/latest.jsoncreated/updated after eachdeno task benchrunOut of scope