[Benchmark]: Measure governed execution orchestration

[rian-be]

Summary

Benchmark the governed execution orchestration path so the cost of resolving approved requests, executing through the core runtime, and recording terminal governance outcomes stays visible over time.

Goal

Measure the overhead of the governed execution manager path that closes the loop from approved governance request to core mutation execution and terminal request outcome.

Problem

Governance already models request lifecycle, approval workflow, version resolution, and governed execution primitives, but that orchestration path is not benchmarked as a dedicated runtime surface.

Without a benchmark for governed execution orchestration, changes in request resolution, approval handoff, execution, or terminal outcome recording can quietly add overhead without being visible in broader runtime measurements.

Scope

• Benchmark request-to-execution orchestration for approved governance requests
• Benchmark version resolution cost before governed execution starts
• Benchmark terminal outcome recording for executed and stale requests
• Keep the benchmark focused on governance orchestration rather than provider persistence details
• Reuse existing governance benchmark helpers where they already exist
• Make scenario names explicit about which governed execution path is being measured

Design Expectations

• The benchmark should measure a real governed execution flow rather than a toy loop.
• Version resolution and execution handoff should remain visible as separate costs where possible.
• Helper code should stay local to the benchmark project.
• Scenario names should make the governed execution path obvious.

Suggested Measurements

• approved request executed through governed orchestration
• approved request rejected as stale before execution
• approved request revalidated and then executed

Acceptance Criteria

• Governed execution orchestration is benchmarked as a distinct governance scenario
• Version resolution cost is visible in the benchmark results
• Terminal governance outcome recording is visible in the benchmark results
• The benchmark remains centered on governance runtime behavior

Non-Goals

• This issue does not change governance runtime behavior
• This issue does not add provider-specific persistence benchmarks
• This issue does not optimize governed execution prematurely
• This issue does not add full integration or load testing

Notes

This issue is a child of the governance benchmark umbrella #73.