🤖 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: 27113978861
• Triggered: schedule

---

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

[claude]

Automated Benchmark Update — Review

This is a routine automated PR updating mock benchmark data and documentation from the latest CI run (2026-06-08). The changes are purely data-driven: timestamps, numeric benchmark results, chart axis ranges, and JSON payloads.

What Changed

• Timestamps updated across all benchmark .md files and JSON data files from 2026-06-06 to 2026-06-08.
• Benchmark numbers updated for all 6 categories (Callback, CombinedWorkflow, Invocation, MockCreation, Setup, Verification) across all compared libraries (TUnit.Mocks, Imposter, Mockolate, Moq, NSubstitute, FakeItEasy).
• Mermaid chart y-axis ranges automatically scaled to reflect the new data ranges.

Notable Observations

• TUnit.Mocks holds its relative position across all categories — it continues to lead or be competitive in most benchmark scenarios. No regressions evident.
• Moq's Callback times increased notably (~141k ns → ~188k ns), which is an external library variance, not a TUnit concern.
• The automation pipeline correctly generates, formats, and commits both the Markdown docs and the backing JSON data files in sync — no drift between latest.json and the rendered .md tables.

Assessment

The PR is mechanically correct and well-structured. The automated workflow handles timestamp propagation, data formatting, and chart scaling consistently. No issues found.