(I was sure I had filed this bug but I can't find it anywhere)

In short, task_runner could mark a task as completed, which would make it so the client can be unblocked, but task_runner would continue with cleanup operations, only later marking the task as sealed once the performance metadata is uploaded.

That requires a fair update to task_scheduler.bot_update_task() and a new task state.