🤖 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: 31988134232
• 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: 11 minutes

Limit details: You’ve used all 3 included reviews currently available under your plan.

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: ac7eb55a-1558-45dc-93ae-9c0eb467c363

📥 Commits

Reviewing files that changed from the base of the PR and between 501a246 and b217f35.

📒 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

The PR refreshes the generated TUnit.Mocks benchmark artifacts with results from the 2026-08-17 scheduled run.

• Updates all six scenario JSON datasets and their aggregate latest.json and summary.json files.
• Regenerates the corresponding benchmark documentation, tables, charts, timestamps, and environment metadata.

Confidence Score: 5/5

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

The refresh preserves the existing data schemas and category coverage while keeping scenario files, aggregate metadata, documentation tables, and chart values aligned.

Important Files Changed

Filename	Overview
docs/static/benchmarks/mocks/latest.json	Refreshes the aggregate dataset while preserving its schema, six-category coverage, and 78-entry benchmark count.
docs/static/benchmarks/mocks/summary.json	Advances the summary date while retaining the complete six-category and six-library lists.
docs/docs/benchmarks/mocks/index.md	Updates generated timestamps without changing navigation, methodology, or documented benchmark coverage.
docs/docs/benchmarks/mocks/Callback.md	Updates callback tables and charts consistently with the corresponding refreshed JSON data.
docs/docs/benchmarks/mocks/CombinedWorkflow.md	Updates combined-workflow tables and charts consistently with the corresponding refreshed JSON data.
docs/docs/benchmarks/mocks/Invocation.md	Updates invocation benchmark variants and matching Mermaid series with the latest measurements.
docs/docs/benchmarks/mocks/MockCreation.md	Updates mock-creation benchmark variants and matching Mermaid series with the latest measurements.
docs/docs/benchmarks/mocks/Setup.md	Updates setup tables and charts consistently with the corresponding refreshed JSON data.
docs/docs/benchmarks/mocks/Verification.md	Updates verification benchmark variants and matching Mermaid series with the latest measurements.

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

[claude]

Code Review

Scope: This PR is an automated refresh of the TUnit.Mocks benchmark artifacts (scheduled CI run, 2026-08-17). All 15 changed files are generated benchmark data and documentation — docs/static/benchmarks/mocks/*.json and docs/docs/benchmarks/mocks/*.md (tables, Mermaid charts, timestamps).

Findings: None. There is no application code, logic, or test changes to review — every diff is regenerated numeric/timestamp data produced by the benchmark workflow, consistent with the schema and category coverage of the previous run. This aligns with the existing automated summaries on this PR (Greptile confidence 5/5).

No architectural or design concerns apply here since nothing hand-authored changed. Looks good to merge as-is.