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

---

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

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[claude]

Automated Benchmark Documentation Update

This PR is a routine automated update of mock benchmark documentation — date stamps, performance numbers, chart axis scales, and JSON data files all look consistent and correctly generated.

What was checked:

• Date timestamps updated from 2026-06-08 to 2026-06-09 across all benchmark Markdown files — consistent.
• Benchmark numbers in tables match the bar chart data arrays and y-axis scale values in the Mermaid diagrams — consistent within each file.
• Allocation figures (KB/B) are unchanged where expected (same workloads), confirming only timing measurements shifted between runs — this is expected variance.
• Performance trends are directionally stable: TUnit.Mocks, Imposter, and Mockolate remain significantly faster than Moq, NSubstitute, and FakeItEasy across all scenarios.

One observation worth noting (not blocking):

The Invocation benchmarks show relatively high error margins compared to mean values for some libraries (e.g., NSubstitute "Invocation (100 calls)" has error of 19,475 ns on a mean of 71,919 ns — roughly 27%). This suggests some benchmark runs may have variance from environment noise. This is not introduced by this PR — it appears to be a pre-existing characteristic of those particular benchmarks. It may be worth reviewing the BenchmarkDotNet warmup/iteration settings for the Invocation (100 calls) scenario to reduce noise in future runs.

No issues with the update itself. The automated generation pipeline is working correctly.