🤖 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: 26350537178
• 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 Update — Review

This is a clean, automated benchmark data refresh. No code changes — only documentation and JSON data updated. No previous review comments to track.

What changed

All 15 files are docs-only updates under docs/:

• Dates bumped from 2026-05-23 → 2026-05-24
• Raw benchmark numbers refreshed across all categories
• Mermaid chart Y-axis limits correctly adjusted to match new max values
• JSON data files kept in sync with Markdown

Notable data observations

Moq regression worth watching: Moq's Callback benchmark jumped ~35% slower (134K → 182K ns) and Verification's 'Never' scenario jumped ~42% (63K → 89K ns). This is a significant run-to-run swing — could be noise from a busy CI runner, or a genuine Moq regression. Not a TUnit concern, but worth flagging if trends continue across future runs.

TUnit.Mocks CombinedWorkflow: Slightly slower this run (1.75 → 2.024 μs, ~15%). Within plausible CI variance but is the largest relative change for TUnit itself.

Everything else is within normal benchmark noise.

Verdict

✅ LGTM — data, charts, and timestamps are all consistently updated across all related files. The automation is working correctly.