🤖 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: 25473991379
• 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]

Review: Automated Mock Benchmark Update

This is a clean, automated data refresh — docs-only changes with no code modifications. Everything looks well-structured.

What's here

All 15 files changed are in docs/ and fall into two categories:

• JSON data files (docs/static/benchmarks/mocks/) — raw benchmark results updated from the 2026-05-07 CI run
• Generated markdown (docs/docs/benchmarks/mocks/) — docs regenerated from the JSON, including chart axis ranges, tables, and timestamps

Diffs are mechanically consistent: every timestamp, table value, and chart scale updated in lockstep across .json and .md files.

Notable result changes

Most deltas are within normal benchmark noise (~1–5%). One result stands out:

Benchmark	Before	After	Change
CombinedWorkflow — Moq	313 μs	406 μs	+30%
CombinedWorkflow — TUnit.Mocks	1.94 μs	1.68 μs	-13% (improvement)

The Moq CombinedWorkflow regression is notable (~30%) but is almost certainly CI environmental variance on a single run rather than a real regression — single-run benchmarks on shared CI infrastructure frequently show this kind of outlier. If this pattern recurs across consecutive runs it may be worth flagging, but nothing actionable here.

No issues found

The automation is working correctly. Changes are properly scoped, consistently applied across all related files, and the generated output matches the source data. Good to merge once CI passes.