//! The protocol seam: anything that can perform one request.
use Future;
use crateOutcome;
/// Performs a single request and reports what happened.
///
/// The engine owns timing, scheduling, concurrency and timeouts; an executor
/// only talks to the target. That keeps protocol support (HTTP today, gRPC or
/// WebSocket later) independent of the measurement logic.
///
/// Implementations are shared across all in-flight requests, so `execute`
/// takes `&self` and must be safe to call concurrently.