The torque driver names a job on its queued event, but jobs can enter
through other drivers (a classic queue:work draining a legacy redis list
during a migration to torque): their per-job stream then begins at the
started event and the dashboard showed them as (unknown). The presenter
already reads the name from the first available event, so carrying it on
started names any job regardless of which driver enqueued it.