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

---

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

[coderabbitai]

Warning

Review limit reached

@thomhurst, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 49 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 4624e88b-5884-4100-a031-bfa4556942f5

📥 Commits

Reviewing files that changed from the base of the PR and between d5ec51a and b8d646c.

📒 Files selected for processing (15)

• docs/docs/benchmarks/mocks/Callback.md
• docs/docs/benchmarks/mocks/CombinedWorkflow.md
• docs/docs/benchmarks/mocks/Invocation.md
• docs/docs/benchmarks/mocks/MockCreation.md
• docs/docs/benchmarks/mocks/Setup.md
• docs/docs/benchmarks/mocks/Verification.md
• docs/docs/benchmarks/mocks/index.md
• docs/static/benchmarks/mocks/Callback.json
• docs/static/benchmarks/mocks/CombinedWorkflow.json
• docs/static/benchmarks/mocks/Invocation.json
• docs/static/benchmarks/mocks/MockCreation.json
• docs/static/benchmarks/mocks/Setup.json
• docs/static/benchmarks/mocks/Verification.json
• docs/static/benchmarks/mocks/latest.json
• docs/static/benchmarks/mocks/summary.json

---

_{Comment @coderabbitai help to get the list of available commands.}

[greptile-apps]

Greptile Summary

This automated refresh publishes the latest TUnit.Mocks benchmark run across the raw JSON artifacts and generated documentation.

• Updates all six benchmark scenarios with results from the 2026-08-09 run.
• Synchronizes tables, Mermaid charts, timestamps, runtime environment details, aggregate data, and summary metadata.
• Preserves the existing generated artifact schemas and scenario coverage.

Confidence Score: 5/5

The PR appears safe to merge because the generated benchmark documentation and JSON artifacts remain structurally and internally consistent.

The changes only refresh generated benchmark values, timestamps, charts, and environment metadata, with no accepted functional, rendering, data-consistency, or security failures.

Important Files Changed

Filename	Overview
docs/static/benchmarks/mocks/latest.json	Refreshes the aggregate benchmark dataset, environment metadata, timestamp, and statistics without changing its schema.
docs/static/benchmarks/mocks/summary.json	Advances the generated benchmark summary date while retaining the existing category, environment, and library metadata.
docs/docs/benchmarks/mocks/index.md	Updates the benchmark overview date, generation timestamp, and reported runtime architecture.
docs/docs/benchmarks/mocks/MockCreation.md	Regenerates MockCreation tables and charts consistently with the corresponding JSON results.
docs/docs/benchmarks/mocks/Invocation.md	Regenerates all Invocation variants and charts consistently with the refreshed raw data.
docs/docs/benchmarks/mocks/Verification.md	Regenerates all Verification variants and charts consistently with the refreshed raw data.

_{Reviews (1): Last reviewed commit: "chore: update mock benchmark results" | Re-trigger Greptile}

[claude]

Code review

No issues found. This PR is fully automated — it only regenerates benchmark data/docs (docs/static/benchmarks/mocks/*.json and the corresponding docs/docs/benchmarks/mocks/*.md) with updated timing numbers and a refreshed date from the latest Mock Benchmarks CI run. There is no hand-written logic in the diff to review, and the PR has already been merged automatically per its own description.