fix: prevent failed containers from showing as running on dashboard

- Add final get_container_status check in start_tool_instance before
  writing status=running; mark as error and return logs if container stopped
- Treat restarting as error in HealthMonitor when DB status was already
  running, so crash loops are surfaced instead of preserved
- Disable auto-restart (restart: unless-stopped -> restart: no) for tool
  instances in manifest compiler, legacy dockerfile path, and built-in seeds

Quality gates:
- pytest tests/unit: 210 passed
- ruff: clean on changed files
- mypy: clean on changed files

apps/api/src/services/instance/health_monitor.py

@@ -203,6 +203,11 @@ class HealthMonitor:
         # Transient states (created, restarting) — preserve current status
         # instead of treating them as an error. The next poll will resolve.
         if snapshot.container_status in ("created", "restarting"):
+            # A container that was already running and is now restarting has
+            # crashed (e.g. entrypoint failure / restart loop). Mark it failed
+            # so the dashboard does not keep showing it as running.
+            if current_status == "running":
+                return "error"
             return current_status or "starting"
 
         # Unknown/unexpected state (paused, etc.)