Thermos observer process timings are confusing for processes that have restarted

Example:

name	 run	 status	 started	 finished	 cpu	 ram
fetch	 0	 SUCCESS	 12/03 07:39:54	 12/03 07:39:57
unzip	 0	 SUCCESS	 12/03 07:39:57	 12/03 07:39:57
run_server	 1	 FAILED	 12/03 08:44:03	 12/03 08:44:08

At a glance, it looks like 'run_server' didn't start for an hour after unzip finished. As it turns out, gimlet ran twice, and the first started right away. Drilling into 'run_server' reveals:

run	 status	 started	 finished
1	 FAILED	 12/03 08:44:03	 12/03 08:44:08
0	 SUCCESS	 12/03 07:39:58	 12/03 08:43:58

It might be more natural for the top-level page to report the start time of the first process, and the finish time of the last process.