🤖 Update Mock Benchmark Results

[thomhurst]

Automated Mock Benchmark Update

This PR updates the mock benchmark documentation with the latest results from the Mock Benchmarks workflow.

Benchmarks Produced

Individual benchmark artifacts are available for download:

• mock-benchmark-MockCreation
• mock-benchmark-Setup
• mock-benchmark-Invocation
• mock-benchmark-Verification
• mock-benchmark-Callback
• mock-benchmark-CombinedWorkflow
• mock-benchmark-summary (aggregated overview)

Libraries Compared

Libraries are discovered dynamically from the benchmark output. See the generated summary.json for the full list.

Changes

• Updated mock benchmark data in docs/static/benchmarks/mocks/latest.json
• Regenerated mock benchmark documentation in docs/docs/benchmarks/mocks/
• Updated mock benchmark summary in docs/static/benchmarks/mocks/summary.json

Workflow Run

• Run ID: 26381291785
• Triggered: schedule

---

🤖 This PR was automatically created and will be merged automatically once CI checks pass.

[claude]

Code Review: Automated Mock Benchmark Update

This is a purely automated, documentation-only PR — no logic changes, no source code touched. The review is brief by design.

What Changed

• Benchmark timestamps advanced from 2026-05-24 → 2026-05-25
• Performance numbers refreshed across all six benchmark categories (Callback, CombinedWorkflow, Invocation, MockCreation, Setup, Verification)
• Chart Y-axis ranges updated to match new result maxima
• latest.json and summary.json data files regenerated

Observations

Results look plausible. The numeric deltas are within expected run-to-run variance (mostly ≤5%). No benchmark flipped its relative ordering between libraries, which is the main sanity-check signal.

One notable data point: CombinedWorkflow shows TUnit.Mocks dropping from ~2.024 μs → ~1.459 μs (~28% improvement). That's larger than typical noise and worth a quick eye on the next few daily runs to confirm it's a real gain and not a one-off outlier (warm cache, reduced GC pressure on the CI runner, etc.).

JSON consistency: latest.json ends without a trailing newline (\ No newline at end of file in the diff). That's pre-existing and not introduced here, but it's worth noting in case the generator can be updated to emit a trailing newline for cleaner diffs.

Verdict

No issues with the automated update itself. The workflow, data format, and documentation generation all look correct. ✅