pipecat eval suitemanifests take aworker_timeout:(seconds), overridden by-w/--worker-timeout, capping how long a run's harness worker may take before the suite kills it and reports the run as an error. It used to be fixed at 600 s, which a long scripted scenario could legitimately exceed, losing the whole run. Left unset, the cap is now derived from the scenario: a scripted scenario's turn budgets summed (each turn's largestwithin_ms, or the default timeout), or a simulation'smax_duration_s, with a floor of 600 s and 60 s on top for the judge and teardown.