When a stack restart or network prune removes a bot's network, its
stopped computer keeps pointing at the old network id. Starting it fails
with "network ... not found", the supervisor returned 500 on every
provision, and runs for that bot retried setup forever while staying
queued. The supervisor now recognizes that error and recreates the
container on a fresh network with the same home, as it already does for
an outdated image.
Claude-Session: https://claude.ai/code/session_01QAiXRe1FLMAJT9jkvwFZFq
Co-authored-by: Claude <noreply@anthropic.com>
679b90a667