fix: add autorestart to supervisord and healthcheck to docker-compose

[okwn]

Summary

• Add autorestart=true to both [program:base-consensus] and [program:execution] in supervisord.conf
• Add healthcheck blocks to both execution and node services in docker-compose.yml

Problem

If the consensus client or execution client crashes, supervisord will not restart it automatically — the node stays down until an operator manually intervenes. Additionally, docker-compose shows services as "healthy" even if the process has exited.

Solution

Two-part fix: supervisord auto-restart ensures process resilience within the container; docker healthcheck enables container-level observability via docker compose ps.

Tests

docker compose config — verify YAML is valid and healthcheck is recognized

Risk / Compatibility

• Risk: LOW
• Affects: configuration only; no chain sync or consensus behavior changed
• Healthcheck uses lightweight HTTP check on port 8545 — standard RPC port
• autorestart=true is standard supervisord configuration

[cb-heimdall]

🟡 Heimdall Review Status

Requirement	Status	More Info
Reviews	🟡 0/1	Denominator calculation Show calculation 1 if user is bot 0 1 if user is external 0 2 if repo is sensitive 0 From .codeflow.yml 1 Additional review requirements Show calculation Max 0 0 From CODEOWNERS 0 Global minimum 0 Max 1 1 1 if commit is unverified 1 Sum 2