A deploy no longer kills live work, and you can watch a run

When the kernel starts, it looks for jobs that were interrupted and cleans them up. That is right when there is one process. We run several. So any container booting — a deploy, a scale-up, one health check restarting one task — marked every job in flight failed, across every customer, with "interrupted by a restart".

Found by running a real job twice and getting that error both times on a settled deployment. The second one was killed by our own probe container.

Cleanup now only touches jobs that have gone quiet for ten minutes. A live run writes constantly, so silence is the difference between a run whose process is gone and one another machine is still driving.

And there is a run page. A to-scale waterfall of what the agent actually did, drawn on the server so it works without JavaScript, then live over the stream: tool results, cost per step with the model and token count behind it, and where it drifted. Failure is treated as the normal case, because it is — "ran out of time" and "an approval was never answered" used to read identically, and now say which. The step where a run died stays amber and open, because nothing is running there.