Function timed_owner_join_step 

pub async fn timed_owner_join_step<T>(
    step: &'static str,
    requests: Option<Arc<dyn ProviderRequests>>,
    work: impl Future<Output = T>,
) -> T

Time one owner-side device-join step and report it the way every other staged run reports.

Each of these is one transition in the Add-a-device flow — approve the provider access, accept the registration, activate — and each is one or more provider round trips, which is what requests counts. Two flows reach them: the discrete command API a host drives itself, and the pairing driver’s drive_once. They share this function so a run through either one reads the same in the log, and each passes the counter of the home it drives.