089d802f1d
- 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
599 B
599 B
openspec/changes/fix-container-status-false-positive (index)
dir: openspec/changes/fix-container-status-false-positive
role
Documents a bug fix for correcting container status false positives where failed containers incorrectly appeared as running in a dashboard/monitoring system.
parent
index: openspec/changes/.pi-map.index.md map: openspec/changes/.pi-map.md
children
files
- change.md
- tasks.md
links
index: openspec/changes/fix-container-status-false-positive/.pi-map.index.md map: openspec/changes/fix-container-status-false-positive/.pi-map.md